Router 3
View the firewall filter counter to continue verifying that matched traffic is being diverted to the bidirectional IPSec tunnel. After you issue the
pingcommand from Router 1 (three packets), thees-trafficfirewall filter counter looks like this:user@R3>show firewall filter es-trafficFilter: es-trafficCounters:Name Bytes Packetsipsec-tunnel 252 3After you issue the
pingcommand from both Router 1 (three packets) and Router 4 (two packets), thees-trafficfirewall filter counter looks like this:user@R3>show firewall filter es-trafficFilter: es-trafficCounters:Name Bytes Packetsipsec-tunnel 420 5To verify that the IPSec security association is active, issue the
show ipsec security-associations detailcommand. Notice that the SA on Router 3 contains the same settings you specified on Router 2.user@R3>show ipsec security-associations detailSecurity association: sa-manual, Interface family: UpLocal gateway: 10.1.15.2, Remote gateway: 10.1.15.1Local identity: ipv4_subnet(any:0,[0..7]=0.0.0.0/0)Remote identity: ipv4_subnet(any:0,[0..7]=0.0.0.0/0)Direction: inbound, SPI: 400, AUX-SPI: 0Mode: tunnel, Type: manual, State: InstalledProtocol: AH, Authentication: hmac-md5-96, Encryption: NoneAnti-replay service: DisabledDirection: outbound, SPI: 400, AUX-SPI: 0Mode: tunnel, Type: manual, State: InstalledProtocol: AH, Authentication: hmac-md5-96, Encryption: NoneAnti-replay service: Disabled