This error message is displayed in the show version output of your switch.
In some cases, the show test1 command output possibly shows the NVRAM:F.
The global checksum error means that the next time the box is reloaded, the nvram most likely is lost due to a crc checksum that failed while it read the configuration. This is not usually a hardware error, but it corrects itself.
This does not have any impact to an operational switch unless configuration changes are made while the switch is in this condition. But most of the times, a reset resolves the checksum failure as it is re-calculated.
This problem is identified as per Cisco bug ID CSCdx87646.
At this point, you need to back up the configuration and schedule a downtime in order to reboot the box and copy the configuration, if the configuration is erased.
If the switch is reset, it is possible that some configuration data is lost. Hence, before the switch is reset, make sure that you have a current copy of your configuration stored on another device. Issue the show config, then copy and paste it to a text file in order to accomplish this. After the reset, check the show version and the show test 1 output to ensure your switch is back to normal.
Hello,I have a cisco 2960 plus series switch and an SFP module. When I plug SFP in port the port goes in err-disable. After a shut, no shut the port's LED blink for once and it goes down again and the following message appears on the terminal. ...
Facing a PING issue as described:A router has 2 IPs on its 2 interfaces :(1)192.168.1.1/24 & (2)18.104.22.168/30;Now when pinging an external IP from the router, which will be the source IP, the router will add in the packet ?192.168.1.1/24 or 22.214.171.124/30 ?b...
What are some “gotchas” with hsrp and spanning tree? I have read that you should use a layer 3 link between the hsrp routers but I can’t seem to wrap my brain around that. How does that work? Also your active router should have its vlans set for active se...
Hi - basic question, but I am rusty...can one have two physical BGP peerings between two routers? I know one can LAG them up and use a loopback address, but what if one wanted to maintain two separate physical peering links?