There's actually no problem with the GBIC ports but I'd like to know if this kind of status is normal or not. I also have the same results with 16-port GBIC modules but all of them seems to work properly.
Hi and thanks for your quick reply. Do you know any CCO document (URL) that I can read to understand this better? I mean I'd like to know (or learn) how this works or simply why this does not apply to legacy GBICs, even if it requires me to go back to the basics of GBICs, fiber, copper, etc.
"WDM, copper, and SFP GBIC's all include a GBIC EEPROM "code" that certifies the GBIC as coming from Cisco. New versions of IOS/CatOS check this code to verify the GBIC - if the code is not found, or is not valid, the software will disable the port in software and will not allow traffic to pass. Older GBIC's (5484/5486/5487) were manufactured before this feature was introduced, and do not contain this feature. Regardless, TAC will not troubleshoot a GBIC that was not purchased from Cisco, the same policy as Flash/DRAM memory."
Question We run asr9001 with XR 6.1.3, and we have a very long delay to
login w/ SSH 1 or 2 to the device compare to IOS device. After
investigation, the there is 1s delay between the client KEXDH_INIT and
the server (XR) KEXDH_REPLY. After debug ssh serv...
Introduction The purpose of this document is to demonstrate the Open
Shortest Path First (OSPF) behavior when the V-bit (Virtual-link bit) is
present in a non-backbone area. The V-bit is signaled in Type-1 LSA only
if the router is the endpoint of one or ...
Hi, I am seeing quite a few issues with patch install and wanted to
share my experience and workaround to this. Login to admin via CLI, then
access root with the “shell” command Issue “df –h” and you’ll probably
see the following directory full or nearly ...