Re: [Netdisco] Fujitsu XG2000 10GB switches and other questions

[Ingen S. J. v. (ICTS) <j.v...@ut...>]

Matthew,

> I have the manual topo file set up in the way you suggest.   The
> router is defined by it's management 1GB interface IP and all links
> 10GB and aggregated 10GB interfaces  are defined under that router.  

OK, sounds good.

>  When I view the device through the web front end it will tell me what
> speed, duplex, port state  and I will see the manually defined uplinks
> on ports  but nothing else for that device.     Any other device in
> the topo works as it should.    Heres the debug  for macsuck and
> arpnip.   FYI I'm runing the FreeBSD VM  and I've updated through
> ports net-snmp.


> netdisco# ./netdisco -D -M backbonenorth 
> n e t  d i s c o

> SNMP::Info::specify() - Changed Class to SNMP::Info::Layer2.
> SNMP::Info::_global layers : sysServices.0
> [192.168.46.123]  Device Type : SNMP::Info::Layer2
> SNMP::Info::_load_attr i_index : ifIndex
> SNMP::Info::_load_attr i_description : ifDescr
> SNMP::Info::_load_attr fw_mac : dot1dTpFdbAddress
> SNMP::Info::_load_attr fw_port : dot1dTpFdbPort
> SNMP::Info::_load_attr bp_index : dot1dBasePortIfIndex
>  Saw : 0 forwarding table entries.  Took 1 seconds.

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")

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.


>  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?


Regards,

Jeroen van Ingen
ICT Service Centre
University of Twente, P.O.Box 217, 7500 AE Enschede, The Netherlands