On Wed, 11 Feb 2009 13:05:33 +0100 (CET) sergemueller@gmail.com wrote:
Hi everyone, i've got some strange issues with the network explorer in nav 3.5: it shows only the root node (our coreswitch) and its vlan interfaces. The Problem might occur because the coreswitch is a h3c switch, and h3c tends to index their physical interfaces starting from .4227614 going to 4228033 (52 ports) (for the first stack member and ports of the second stack are indexed from 503316505 to 503316913 the rest looks like this: IF-MIB::ifName.14 = STRING: NULL0 IF-MIB::ifName.16 = STRING: InLoopBack0 IF-MIB::ifName.31 = STRING: Vlan-interface1 IF-MIB::ifName.2431 = STRING: Vlan-interface301 IF-MIB::ifName.4023 = STRING: Vlan-interface500 IF-MIB::ifName.4031 = STRING: Vlan-interface501 IF-MIB::ifName.4227614 = STRING: Aux1/0/0 IF-MIB::ifName.4227625 = STRING: GigabitEthernet1/0/1
the last thing shown in the netexplorer is vlan-interface 501 then the whole tree is cut of. But in the network map you can see the topology, with some switches connected to our coreswitch (uplinks detected correctly)
any suggestions where to look for this problem/how to fix?
I remember discussing this with you on IRC just around the time you posted this, which is why I never answered this mail.
Anway, if I remember correctly, we concluded on IRC that NAV is unable to pull information about the VLANs of switch ports on your H3C devices. The Network Explorer is a pure VLAN topology explorer, which is why you can't see as much topology info in it as you do on the Netmap. The Netmap is based both on layer 2 and layer 3 topology.
Hopefully, we will gain better support for H3C devices (and other vendors) as we implement Q-BRIDGE-MIB support in the new SNMP polling engine.