When we check the device attributes for model 3550 switches, telnet shows up as "not supported" even though we can telnet into the switch with no problem and the telnet password is set correctly in Ciscoworks. Has anyone else encountered this problem? If you know of a solution to this please let me know. Thank you.
I would ensure that I had the latest IDU for RME. Also many of the quirky problems I had in LMS went away with version 2.2. No more Java Virtual Machine to deal with. =) If you upgrade you can perform a rediscovery of the devices which should help. If that doesn't work I would put a Sniffer on the wire and look at what the packets are doing.
I think Device Attributes never worked right. I am still getting a lot of bogus checks on all of my devices. All my patches are up-to-date on CW2K and I am on RME 3.5(LMS2.2) yet I still get a lot of device attribute errors all the time.
I have been having similar problems with the latest version of CW2K LMS (2.2, RME 3.5). I have reinstalled the application and the OS many times, and RME continues to report many device attribute errors.
If I install CD One 5th Edition and RME 3.4 with IDU 5, I have no problems at all. TAC seems to be unable to assist me as well.
[toc:faq]The ProblemOn traditional switches whenever we have a trunk
interface we use the VLAN tag to demultiplex the VLANs. The switch needs
to determine which MAC Address table to look in for a forwarding
decision. To do this we require the switch to do...
[toc:faq]Introduction:Netdr is a tool available on a RSP720, Sup720 or
Sup32 that allows one to capture packets on the RP or SP inband. The
netdr command can be used to capture both Tx and Rx packets in the
software switching path. This is not a substitut...
IntroductionOSPF, being a link-state protocol, allows for every router
in the network to know of every link and OSPF speaker in the entire
network. From this picture each router independently runs the Shortest
Path First (SPF) algorithm to determine the b...