After upgrading to Spectrum 22.2.6 we are seeing these VPN Discovery messages in VNM.OUT
search cancel

After upgrading to Spectrum 22.2.6 we are seeing these VPN Discovery messages in VNM.OUT

book

Article ID: 263549

calendar_today

Updated On:

Products

DX NetOps

Issue/Introduction

We are seeing these VpnPPVPNDiscovery messages in VNM.OUT after upgrading to Spectrum 22.2.6.

 

 

Mar 29 12:20:18 VPN DISC:  TRACE at VpnPPVPNDiscovery.cc(315): VrfIfUpTrap :: App model 0x537576744 for VRF SIB,ifIndex 3ea. Discovering VRF instance

Mar 29 12:21:05 VPN DISC:  TRACE at VpnPPVPNDiscovery.cc(315): VrfIfUpTrap :: App model 0x537576744 for VRF VR63a2500,ifIndex 2d4. Discovering VRF instance

Mar 29 12:24:46 VPN DISC:  TRACE at VpnPPVPNDiscovery.cc(315): VrfIfUpTrap :: App model 0x537576744 for VRF Axad_1,ifIndex 1a3. Discovering VRF instance

Mar 29 12:26:49 VPN DISC:  TRACE at VpnPPVPNDiscovery.cc(315): VrfIfUpTrap :: App model 0x537576744 for VRF SIB,ifIndex 2f0. Discovering VRF instance

Mar 29 12:27:48 VPN DISC:  TRACE at VpnPPVPNDiscovery.cc(315): VrfIfUpTrap :: App model 0x537576744 for VRF AxeLdI_1,ifIndex 253. Discovering VRF instance

Mar 29 12:28:16 VPN DISC:  TRACE at VpnPPVPNDiscovery.cc(315): VrfIfUpTrap :: App model 0x537576744 for VRF QIB,ifIndex 312. Discovering VRF instance

Mar 29 12:29:23 VPN DISC:  TRACE at VpnPPVPNDiscovery.cc(315): VrfIfUpTrap :: App model 0x537576744 for VRF QIB,ifIndex 270. Discovering VRF instance

Mar 29 12:31:04 VPN DISC:  TRACE at VpnPPVPNDiscovery.cc(315): VrfIfUpTrap :: App model 0x537576744 for VRF MIS,ifIndex 3af. Discovering VRF instance

Mar 29 12:32:37 VPN DISC:  TRACE at VpnPPVPNDiscovery.cc(315): VrfIfUpTrap :: App model 0x537576744 for VRF MIS,ifIndex 270. Discovering VRF instance

Mar 29 12:37:10 VPN DISC:  TRACE at VpnPPVPNDiscovery.cc(315): VrfIfUpTrap :: App model 0x537576744 for VRF VR637910,ifIndex f3. Discovering VRF instance

Environment

Release : 22.2.6

Cause

VPN Discovery debug is enabled by default

Resolution

If there are no performance issues this can be safely ignored.

This is scheduled to be addressed in a future Spectrum release.