|
From: Matthew B. <mat...@gm...> - 2011-01-10 18:38:11
|
>
>
> Looks like the switch didn't return any of its forwarding tables. Since
> Netdisco has no specific device class for Fujitsu switches, it used the
> most generic method.
>
> Perhaps this switch uses a different MIB for the forwarding tables.
> According to our friend Google it supports the Q-BRIDGE-MIB... could you
> do either one of the following:
>
> a) snmpwalk the device for dot1qTpFdbPort ("snmpwalk -c <community> -v2c
> 192.168.46.123 dot1qTpFdbPort")
>
>
This returned nothing....
> b) walk the device for all supported mibs using the walk_all script in
> the netdisco/mibs directory ("/usr/local/netdisco/mibs/walk_all -c
> <community> -d 192.168.46.123")
> The second option returns *a lot* more data and might contain sensitive
> information; OTOH, it could be very useful to add a specific Fujitsu
> device class.
>
Tried this and looking through the results showed nothing like a MAC address
(except for the switches own ports). My feeling is that on this switch I
can't get the MAC table via snmp. how do I add a device class?...I will
google...
>
>
> > netdisco# ./netdisco -D -A backbonenorth
> > n e t d i s c o
> > $)
> > SNMP::Info::device_type() layers:00000011 id:211 sysDescr:"'E14L10'
> > 'Z01' '2008/11/04-07:07:04'"
> > SNMP::Info::specify() - Changed Class to SNMP::Info::Layer2.
> > [backbonenorth] Processed 0 ARP Cache entries.
> > SNMP::Info::_load_attr ip_netmask : ipAdEntNetMask
> > netdisco#
>
> The device doesn't present itself as being Layer3 capable. Usually you
> only need to run "arpnip" against Layer 3 devices which are actually
> performing a routing function.
>
> According to the datasheet I found, the XG2000 is a Layer 2 switch. Are
> you sure that it's doing routing as well as switching?
>
>
>
No its not doing routing. None of my switches are doing routing in this
lab. I thought that that wouldn't matter..... I'm fairly new to Netdisco
so if I'm doing something wrong sorry...
|