Double-bit ECC error causes LC reboot as soon as the error is seen, hence we do not have sufficient time to capture all the logs whenever Double-bit ECC error is seen. In eXR system the issue is more severe as the logs captured after Double-bit ECC error is stored in LC disk. The logs are lost incase the LC is replaced with a different LC.
The current solution is only for eXR based system. We can use an EEM script to make sure that all the logs are captured as soon as Double-bit ECC error is hit. Sample script is attached to this document(File Name: ecc_capture.tcp.zip).
The script does following:
1. Disable LC reload
2. Capture all the logs(NP datalog/show tech NP etc).
On Cisco 3850 switches, when configuring a port for Cisco IP phone, the built-in Auto-QoS is used. It's composed of service policies for input: AutoQos-4.0-Cisco-Phone-Input-Policy and for output: AutoQos-4.0-Output-Policy. So, when we wan...
I got the problem when deploying 2 vEdge at HQ Site with VRRP and 1 vEdge at Branch site, Everything can work via SD-WAN tunnel except some application etc. SAP cannot work. I tried to down 1 vEdge (VRRP Standby) at HQ Site. The result shows tha...
Hi all C3850# sho processes cpu sortedCPU utilization for five seconds: 95%/39%; one minute: 95%; five minutes: 94%PID Runtime(ms) Invoked uSecs 5Sec 1Min 5Min TTY Process140 4086466 627425 6513 43.00% 47.00% 46.65% 0 NGWC L2M233 87104868 126847578 6...
I've set Stackwise Virtual with different priority value(each 15 and 14) for aiming to keep one switch always-be active.
The switch that I set priority 15 didn't become active when I later turned it on after first booting the switch with priority...