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).
Hi allI have a issue when configure on Cisco 3850In 3850, I created 6 SVI to routing on local and I apply ACL for 5 SVI as bellow:ACL 100 have 155 rulesACL 150 have 259 rulesACL 107 have 188 rulesACL 111 have 155 rulesACL 112 have 290 rules When I ap...
How can I make Cisco Prime CLI Template for SubInterface?
For example "Interface GigabitEthernet2.100"
I have two variables: $ISP1-Interface-Name (GigabiEthernet2), $ISP1-VLAN-Number (100)
How to insert a point (".") between the&...
Hi Community, Having issues installing a demo license for my CSR100v. I have already copied the license file to the VM, but can't install it, the command: cme-01#license ? smart Smart licensingcme-01#license I only have the option to ...
Hi Please see the below config, are these four commands making sense? Can we use one command to replace the four command? Thank you R1(config)#do sh run | i snmpsnmp-server community abc1 RO 1snmp-server community abc2 RO 2snmp-server community abc3 ...