It's not clear that IDU 13 is contributing to the inability to manage this device.
I guess standard troubleshooting processes apply.
1) Does 'show mod' on the switch show a good status for the FWSM?
2) Is the sysObjectID of the FWSM still coming up as .188.8.131.52.184.108.40.206.522 when you poll it directly from some other SNMPget utility - use something other than CiscoWorks to give a different perspective - like NetSNMP.
3) Is it possible that the management access to the FWSM is using different credentials than what the NMS (CiscoWorks) is using?
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...