First off, it looks like net-snmp doesn't support multiple modules in one file
when creating the .index, so we may have to rething the autogeneration for
the extreme mongo .mib file. I was able to get it to work by adding
EXTREME-EDP-MIB by hand to the .index.
Here is a walk of the two tables (extremeEdpTable and
extremeEdpNeighborTable; the first lists the neighbors and the second lists
the VLANs) on a sample device with one EDP neighbor:
the EdpNeighborTable didn't have any entries. Not sure I can explain that off
the top of my head.
It looks like we'd be dependent on entries in the EdpNeighborTable to add
neighbor addresses, since the EdpTable itself just talks about devices, with no
address info. We can know what the device is called but if there aren't any IP
addresses and if the sysName isn't the same as the DNS name then we might
not be able to find it.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I've implemented a start at EDP. The biggest blocker is that EDP reports slot and
port, and different products seem to name ports differently - I've seen "RMON
Port %d on Unit %d" and "Summit7i-Port %d" - so figuring out what to put in the
remote_port column may be tricky. I've only got one device that implements the
EDP MIB (even the guy on the other end, who is obviously speaking EDP, doesn't
implement the MIB) so I can't test it extensively. I'm targeting my code to after
the 1.0 release, although I'd welcome hearing from people interested in testing
this code specifically.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Commit 0661b13 add EDP class and added to L3::Extreme
Port / slot cross referenced to ifName similar to LLDP. EDP reports an IP address for each VLAN on the trunk. This could give the appearance initally of multiple neighbors unitl the IP's are resolved as all belonging to the same neighbor device. Netdisco seems to handle this correctly.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Logged In: YES
user_id=109593
First off, it looks like net-snmp doesn't support multiple modules in one file
when creating the .index, so we may have to rething the autogeneration for
the extreme mongo .mib file. I was able to get it to work by adding
EXTREME-EDP-MIB by hand to the .index.
Here is a walk of the two tables (extremeEdpTable and
extremeEdpNeighborTable; the first lists the neighbors and the second lists
the VLANs) on a sample device with one EDP neighbor:
EXTREME-EDP-MIB::extremeEdpNeighborName.1001.'..... .*' = STRING: "HS-
X450"
EXTREME-EDP-MIB::extremeEdpNeighborSoftwareVersion.1001.'..... .*' =
STRING: "11.3.2.6"
EXTREME-EDP-MIB::extremeEdpNeighborSlot.1001.'..... .*' = INTEGER: 1
EXTREME-EDP-MIB::extremeEdpNeighborPort.1001.'..... .*' = INTEGER: 2
EXTREME-EDP-MIB::extremeEdpEntryAge.1001.'..... .*' = INTEGER: 18
EXTREME-EDP-MIB::extremeEdpNeighborVlanId.1001.'..... .*'."backbone" =
INTEGER: 4088
EXTREME-EDP-MIB::extremeEdpNeighborVlanIpAddress.1001.'.....
.*'."backbone" = IpAddress: X.Y.Z.146
Here is the EdpTable from the other end of the same link:
EXTREME-EDP-MIB::extremeEdpNeighborName.1002.'..... .}' = STRING: "SJH-
X450"
EXTREME-EDP-MIB::extremeEdpNeighborSoftwareVersion.1002.'..... .}' =
STRING: "11.3.2.6"
EXTREME-EDP-MIB::extremeEdpNeighborSlot.1002.'..... .}' = INTEGER: 1
EXTREME-EDP-MIB::extremeEdpNeighborPort.1002.'..... .}' = INTEGER: 1
EXTREME-EDP-MIB::extremeEdpEntryAge.1002.'..... .}' = INTEGER: 25
the EdpNeighborTable didn't have any entries. Not sure I can explain that off
the top of my head.
It looks like we'd be dependent on entries in the EdpNeighborTable to add
neighbor addresses, since the EdpTable itself just talks about devices, with no
address info. We can know what the device is called but if there aren't any IP
addresses and if the sysName isn't the same as the DNS name then we might
not be able to find it.
Logged In: YES
user_id=109593
Good lord did sourceforge ever mangle that text. I've uploaded it as an
attachment so that it's a little less mangled.
Walks of two neighboring switches
Logged In: YES
user_id=109593
I've implemented a start at EDP. The biggest blocker is that EDP reports slot and
port, and different products seem to name ports differently - I've seen "RMON
Port %d on Unit %d" and "Summit7i-Port %d" - so figuring out what to put in the
remote_port column may be tricky. I've only got one device that implements the
EDP MIB (even the guy on the other end, who is obviously speaking EDP, doesn't
implement the MIB) so I can't test it extensively. I'm targeting my code to after
the 1.0 release, although I'd welcome hearing from people interested in testing
this code specifically.
Commit 0661b13 add EDP class and added to L3::Extreme
Port / slot cross referenced to ifName similar to LLDP. EDP reports an IP address for each VLAN on the trunk. This could give the appearance initally of multiple neighbors unitl the IP's are resolved as all belonging to the same neighbor device. Netdisco seems to handle this correctly.