On Sun, Nov 2, 2008 at 6:20 AM, Jeffrey Denton <[EMAIL PROTECTED]> wrote: > > Nothing elegant... > > You could always shutdown the port and wait for someone to complain. > > If it's not randomly generating traffic, then it's not a windows box. > Switches tend to be noisy with layer 2 protocols. Firewall or > UNIX/Linux based system? Does the duplex and speed show up as > auto-negotiated (a-full, a-100)? > > You could try "no switchport" and the "ip add dhcp" on the interface > to see if you can generate a response that way. Set an IP on the > interface so that you can "ping 192.168.1.255 source ...". Pinging > broadcast addresses might speed up the process. > > Setting up a SPAN or RSPAN might help you capture some traffic. > > "test cable-diagnostics tdr interface ..." would at least tell you how > long the cable is. > > Setup the port as a trunk or port-channel or .... with > auto-negotiation and see what happens. > > Set the switch up as a management cluster and then run "show cluster members". > > Use the other suggestions.... >
SNMP sweeps.... _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
