Preview Tool

Cisco Bug: CSCsz34002 - EzVPN client does not log CONNECTION_UP msg when reconnecting to primary

Last Modified

Mar 06, 2018

Products (1)

  • Cisco IOS

Known Affected Releases


Description (partial)

With the EzVPN default primary peer feature,  when the ezvpn client reconnects 
to the default primary peer after it becomes available again, it doesn't log an
EZVPN_CONNECTION_UP notification message. This makes it difficult to know 
when the primary connection has been restored after a failure. This is only an
issue with logging and notification, and it does not affect the actual EzVPN 
failover functionality.

This is only a problem when the EzVPN client reconnects back to the default server.
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.