-
Notifications
You must be signed in to change notification settings - Fork 23
Compatibility with equipments
Wiremaps uses SNMP to gather information on various equipments of your network. While most information retrieved are available from a standardized MIB, many equipments don’t respect those MIB, use proprietary MIB or just don’t deliver the information. Some standard MIB were also written while some concepts were not available (for example VLAN) and their usage in presence of those new concepts can vary from one equipment to another.
Therefore, Wiremaps does not contain a generic collector able to retrieve all information from all equipments. Instead, it contains a serie of generic collectors that are combined with specific collectors to build a collector for each kind of equipments. The following table contains the equipments and features supported by Wiremaps.
| Basic | Port information | Duplex/Autoneg | LLDP | FDB | ARP | SONMP | CDP | EDP | VLAN | Trunk | |
|---|---|---|---|---|---|---|---|---|---|---|---|
| Linux with lldpd | ✓ | ✓ | ✓ | ✓ | ✗ | ✓ | - | - | - | ✓ | - |
| Linux w/o lldpd | ✓ | ✓ | ✗ | - | ✗ | ✓ | - | - | - | ✗ | - |
| Nortel 55x0 | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | - | - | ✓ | - |
| Nortel ERS 8600 | ✓ | ✓ | ✓ | - | ✗ | ✓ | ✓ | - | - | ✓ | - |
| Alteon | ✓ | ✓ | ✓ | - | ✓ | ✓ | ✓ | - | - | ✓ | - |
| Cisco 2900, 6500, 7200, … | ✓ | ✓ | ✗ | ✗ | ✓ | ✓ | - | ✓ | - | ✓ | ✓ |
| 3Com Superstack | ✓ | ✓ | ✗ | - | ✓ | ✓ | - | - | - | ✓ | - |
| ArrowPoint | ✓ | ✓ | ✗ | - | - | ✓ | - | - | - | ✗ | - |
| Nortel Blade network switchs | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | - | - | - | ✓ | - |
| Extreme | ✓ | ✓ | ✗ | ✓ | ✓ | ✓ | - | - | ✓ | ✓ | - |
| Netscreen ISG | ✓ | ✓ | ✗ | - | - | ✓ | - | - | - | ✗ | - |
| HP Procurve | ✓ | ✓ | ✗ | ✓ | ✓ | ✓ | - | - | - | ✓ | ✗ |
| F5 BigIp | ✓ | ✓ | ✓ | ✗ | ✗ | ✓ | - | - | - | ✓ | ✓ |
To get most useful information, you really need an LLDP daemon that exports information with SNMP. Actually, only lldpd seems to be available.
LLDP is not supported at all on this kind of equipment. This is quite odd to support it on more low level switches like 55x0 series…
On recent releases (12.2(18)SXH or more), Cisco supports LLDP. However, the support does not include LLDP MIB. Therefore, LLDP information is only available through the CLI. This is a long standing problem and Cisco seems not being eager to fix this
(2009-08-25: I’ve got some 3750s and 3560s running IOS 12.2(50)SE1 or thereabouts - LLDP-MIB is indeed supported on them. Cheers, Cos.)
Those switches support LLDP since 5.x version. Since they are running AlteonOS, maybe this will become supported for Alteon too. They don’t support SONMP while this is supported for Alteon.
Missing trunk information is a problem since trunk contains information not available on physical interfaces.
This information contains IP, name (from sysName), base OID (from sysObjectID), description (from sysDescr). This kind of information is retrieved even for unknown equipments.
This information contains port name, port description, port state (up or down), mac address and speed.
This includes the basic port information but also duplex and autonegociation.
This is the forwarding database. This means that we are able to retrieve for each port the mac addresses that are visible from it. If the equipment provides an FDB for each VLAN, we mix everything into one table.
Retrieving ARP permit to match IP with MAC address. Associated interfaces are not kept since this is usually difficult to match real physical interfaces.
For each VLAN, we can get the VLAN name and the ports tagged or untagged with this VLAN. Tagging information is not kept.
On some equipments, trunk are like physical interfaces and may have their own VLAN and FDB. For example, on HP, VLAN information is only available on the trunk, not the physical interfaces, while on Nortel, the trunk (MLT or SMLT) is not seen in the list of physical interfaces and VLAN information are attached to physical interfaces.
By trunk, we mean port aggregation. On Cisco, this is usually referred as etherchannel while trunk is the ability to put several VLAN on one port.