Preview Tool

Cisco Bug: CSCsz00600 - cipSecTunnelStart/Stop trap should include cipSecTunLocal/RemoteAddr

Last Modified

Feb 21, 2018

Products (1)

  • Cisco ASA 5500-X Series Firewalls

Known Affected Releases


Description (partial)

CU is requesting, instead of cipSecTunnelStart/Stop trap sending the tunnel index(cipSecTunIndex), it can also include cipSecTunRemoteAddr and cipSecTunLocalAddr to identify the tunnel that has gone down or up.

cipSecTunIndex is assigned by the snmp engine, and it is meaningless to the user. Currently, the user needs to poll the device again to map the cipSecTunIndex to more meaningful identifier such as cipSecTunRemoteAddr and cipSecTunLocalAddr in order to find out which tunnel the trap is refering to.

CU would like to have the cipSecTunLocalAddr and cipSecTunRemoteAddr  included in the trap so that he does not have to go through the polling process.

Bug details contain sensitive information and therefore require a account to be viewed.

Bug Details Include

  • Full Description (including symptoms, conditions and workarounds)
  • Status
  • Severity
  • Known Fixed Releases
  • Related Community Discussions
  • Number of Related Support Cases
Bug information is viewable for customers and partners who have a service contract. Registered users can view up to 200 bugs per month without a service contract.