In case the issue manifest the following data collection plan can be executed while the issue is happening before opening case to GTAC :
- "show fulltech"
- "show ip route vrfids 1-511"
- "show io l2-tables"
- "show io l3-tables"
- in addition BGP related traces could be activated : within the ‘router bgp’ option, BGP event debugging could be enabled with command ‘neighbor <x.x.x.x> neighbor-debug-mask event enable’ and also enable printing to the telnet/SSH session with command ‘debug-screen on’ (‘debug-screen off’ disables this again). There are further debug options such as ‘none,all,error,packet,event,trace,warning,state,init,filter,update’ but better to start with ‘event’ to see what is captured as regards a potential problem peer with the ‘event’ flag first (the ‘no neighbor <x.x.x.x> neighbor-debug-mask’ format should disable the debug again).