Avaya G430 - Page 504

To Next Page

To Previous Page

2. Use the set logging session condition ISAKMP command to view all

ISAKMP messages of Info level and above.

For example:

Gxxx-001# set logging session condition ISAKMP Info

Done!

CLI-Notification: write: set logging session condition ISAKMP Info

3. Use the set logging session condition IPSEC command to view all IPSec

messages of Info level and above.

For example:

Gxxx-001# set logging session condition IPSEC Info

Done!

CLI-Notification: write: set logging session condition IPSEC Info

4. Initiate a session by pinging the peer device.

For example.

Gxxx-001# ping 135.64.102.109

Result

The logging information details the IKE negotiations, including the ISAKMP SA and IPSec SA

configuration of the peers.

Example

IPSEC-Informational: Call IKE negotiation for outgoing SPD entry 901_20:

Peers 149.49.77.202<->135.64.102.109

ISAKMP-Informational: Initiating IKE phase 1 negotiation:

Peers 149.49.77.202<->135.64.102.109

ISAKMP-Informational: Finished IKE phase 1 negotiation, creating ISAKMP

SA:

Peers 149.49.77.202<->135.64.102.109

Icookie - 0e2fb5ac12ec04b2, Rcookie - 541b912b0a30085d

esp-des, esp-sha-hmac, DH group 1, Lifetime 86400 seconds

ISAKMP-Informational: Initiating IKE phase 2 negotiation:

Peers 149.49.77.202<->135.64.102.109

ISAKMP-Informational: Finished IKE phase 2, creating outbound IPSEC SA:

SPI 0x4d706e3, Peers 149.49.77.202<->135.64.102.109

Identities: 149.49.77.0/255.255.255.0->135.64.102.0/255.255.255.0

esp-des, esp-md5-hmac, 3600 seconds, 4608000 KB

ISAKMP-Informational: Finished IKE phase 2, creating inbound IPSEC SA:

SPI 0x6798, Peers 135.64.102.109<->149.49.77.202

Identities: 135.64.102.0/255.255.255.0->149.49.77.0/255.255.255.0

esp-des, esp-md5-hmac, 3600 seconds, 4608000 KB

Typical installations for IPSec VPN

Included in the typical installations, are examples of installing VPN hub and spokes, full or

partial mesh, and a hub-and-spoke with VPN for data and VoIP control backup.

Other manuals for Avaya G430