I have a few devices (all happen to be on one subnet ... suspicious) that always come up as " Not responding" . These are 2950's with IOS 12.1. I have chked the community strings, the passwds, management stn to device (all ok except for http and tftp as they are disabled) . I have also deleted the device and added it manually, but no luck. The ping responses to the device are normal.
Anyone have any clues on why this could be the case?
In the Import Status screen, select one of these 'Not Responding' device and under the Device Actions selcted 'Show Details' and click Finish. See what RME shows under the Not Responding Reason as the cause.
Show details gives me the reason as "Could not conect to host a.b.c.d" I am using Ip not dns names. Also on this subnet Ihave 14 switches of which I see (or are responding to rme) only 5 devices. So ther is no acl or any of that to stop it even.
It could be due to that RME is timiing out while trying to connect to this device. If you want you can install the JET Packet Capture Tool for CW2K from: http://sourceforge.net/projects/cosi-nms and capture a trace while adding the device again to see where exactly it's failing. Assuming that device credentials etc are all correct.
[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...