The secondary supervisor 1a (with MSFC1 and PFC) boots up ok and a console connection shows that it is in standby mode. However if I do a show mod (in CATOS version 7.6(7)) it shows a status of other even though the msfc shows status standby. How can I determine what is going on with this module and what the other status actually means?
on switch issue " show test all " and note the output of module 2 diagnostic test status.. , could you make sure you have highavailability enabled as well as highavailability versioning enabled by "show system highavailability" and see if these are enabled.
Also take a look at the module itself STATUS LEDs and reference the tables mid way down on bellow link.
Module 2 tests all show good (see below). The status lights are all green with the exception of the active status on module 2 which is amber. My show system highavailability shows enabled but versioning is disabled. I didn't think I needed versioning unless I wanted to run differant versions on each sup. I know the software is the same on both modules, but the firmware and hardware are slightly differant versions. Do I need to enable versioning?
NPT 6509 VLT> (enable) show system highavailability
I would suggest to try off business hours to re-seat the standby module, I have see issues with standby whereby re-seating the module fixes the issue, if this does not fix the standby other status TAC case would be the next step.
I haven't come up with anything conclusive, however at this point the theory is that we somehow managed to upgrade to a CAT OS Version 7.6(7) that requires more than the 64 MB's of Dram that we have on the supervisor. It seems that the newer images (I think most if not all in 7.6 or higher all require 128 Mb's of Dram. The strange thing is that everything other than the stanby sup listing status other seem to work.
The strange thing is that we have been running this version for years and other than the status other, have not really encountered any issues.
I have not found a final solution, but a couple options are as follows none of which are really enthusing me.
1. Downgrade to an older CatOS version (not an option since all the images that support 64 MB's of DRAM do not support the IDSM2 blade we have.
2. Upgrade to 128 MB's of Dram. This would initially seem like the easiest solution, however the Sup1 with MSFC with 64 MB's of DRAM is not upgradable to 128 MB's of DRAM without replacing the MSFC with a MSFC2 at the same time). This makes this upgrade for 2 modules very expensive.
3. Switch to Native mode software. I am still waiting for confirmation on DRAM support but it seems Native software will run with only 64 MB's of DRAM, but this will require a complete rewrite of the configuration to go to native mode.
We are pleased to announce availability of Beta software for 16.6.3.
16.6.3 will be the second rebuild on the 16.6 release train targeted
towards Catalyst 9500/9400/9300/3850/3650 switching platforms. We are
looking for early feedback from customers befor...
Introduction Featured Speakers Luis Espejel is the Telecommunications
Manager of IENova, an Oil & Gas company. Currently he works with Cisco
IOS® and Cisco IOS XE platforms, and NX to some extent. He has also
worked as a Senior Engineer with the Routing P...
In this session you can learn more about Layer 3 multicast and the best
practices to identify possible threats and take security measures. It
provides an overview of basic multicast, the best security practices for
use of this technology, and recommendati...