For any network infrastructure, one should baseline and periodically evaluate the running software. Consistency across like platforms and being on a supported current release are two good criterion one should meet (besides the obvious of having a release that meets your needs). Any inconsistency should be for validated reasons that are documented and revisited at the next review cycle.
New releases include not just bug fixes, but also features (the whole purpose of Cisco "T" (technology) train software releases).
One other thing to consider in the specific situation you describe is the possibility of moving off of hybrid (CatOS on the Sup + IOS on the MSFC) to a native IOS image. Many folks find the native integration of the switchs layer 2 and layer 3 functionality to be a more intuitive configuration.
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 ...