I have two Catalyst 6513 (with redundant Supervisor Engine 720) forming the core of the network. They are connected to each other over an 802.1Q trunk, passing all VLANs by default. They run CatOS 8.3(4) and MSFC IOS 12.2(17d)SXB6.
Each switch has a NAM-2 (WS-SVC-NAM-2) installed in slot 5. NAM software version is 3.4(1a). The NAM management port is automatically synchronized to the VLAN assigned to interface sc0 on the supervisor engine, which on both switches is VLAN 2.
Both switches' MSFC have SVI on VLAN 2 and form a HSRP address. I configured each NAM with an IP address on VLAN 2 and point their default gateway to the HSRP address. Everything is fine. The NAMs are reachable from anywhere in the network.
A week ago the switches were converted to native IOS version 12.2(18)SXF12. The migration was successful. It's been running fine thus far.
I added the command "analysis module 5 management-port access-vlan 2" on both switches to connect back to the NAMs' management port. No config modification done on the NAMs.
Issues start to arise, as follows:
1. First switch can ping to both NAMs directly (i.e. sourcing from int vlan2).
2. Second switch can ping to its NAM but can't ping the NAM on the first switch, though it can resolve its ARP.
3. The NAM on the first switch can ping to any IP address of the first switch but can't ping to any other remote IP addresses. Thus it is now no longer reachable everywhere.
I swapped both NAMs. The second NAM (now in the first switch) experienced the same issue. I have no idea what else to troubleshoot. It is supposed to be a very simple thing.
I plan to upgrade both NAMs to version 3.5(1b). I can't find a very good upgrade guide on cisco.com. Can anyone advise me:
1. How to upgrade a NAM-2 from version 3.4(1a) to 3.5(1b). Kindly point me to a technote.
2. What will happen to the NAMs' config after the upgrade? Will they remain?
3. What other patches do I need to apply?