topic RE: SNMP monitoring of Fabric Extend tunnel in ExtremeSwitching (VSP/Fabric Engine)

SNMP monitoring of Fabric Extend tunnel

Jon_P — Tue, 04 Jan 2022 15:11:00 GMT

Hi,

We have a L3 fabric extend tunnel to between a VSP at our main site, and another at a remote facility.
We would like to monitor the status of the tunnel via SNMP.

As we have service provided equipment in between our VSPs, both the physical port, and the VLAN used for the FE tunnel may stay up even if connectivity between the devices is lost. As far as I can see, the ISIS logical interface does not seem to be visible to our monitoring software.

Any suggestions as to how can I monitor the tunnel status, or be alerted when it goes down?

RE: SNMP monitoring of Fabric Extend tunnel

Jon_P — Mon, 10 Jan 2022 18:05:00 GMT

To expand on this slightly, we're currently monitoring these VSPs with both Statseeker & Castlerock SNMPc, and we also have Extreme Management Center. Ideally we'd like the ISIS logical interface to be visible as an SNMP object, but any way of creating an alert when either the logical interface or ISIS adjacency goes down would be a big help.

If I go to 'Device view' in EMC I can see the link that we need to monitor on the IS-IS tab, both under 'ISIS interfaces' and 'ISIS adjacencies'. Is there any way to create an alert based on the status of these?

RE: SNMP monitoring of Fabric Extend tunnel

Ludovico_Steven — Tue, 11 Jan 2022 19:20:00 GMT

I think the only way is to monitor the Up-Adj value of the ISIS interface; if at 0, the adjacency is down; if at 1 the adjacency is up.
(the op-state is up even if the adjacency is down, so won't help...)
(an adjacency in Init state, will have Adj = 1 but Up-Adj = 0)

To pull that that value from the MIB, first find the ifIndex of the logical interface:

lstevens@toolbox:~$ snmpwalk -v 2c -c public 10.8.4.28 .1.3.6.1.4.1.2272.1.63.26

RAPID-CITY::rcIsisLogicalInterfaceIfIndex.1 = INTEGER: 1600

RAPID-CITY::rcIsisLogicalInterfaceIfIndex.2 = INTEGER: 1601

RAPID-CITY::rcIsisLogicalInterfaceIfIndex.3 = INTEGER: 1602

RAPID-CITY::rcIsisLogicalInterfaceIfIndex.4 = INTEGER: 1603

RAPID-CITY::rcIsisLogicalInterfaceIfIndex.5 = INTEGER: 1604

[...]

RAPID-CITY::rcIsisLogicalInterfaceName.1 = STRING: "Site1-VSP4450-1"

RAPID-CITY::rcIsisLogicalInterfaceName.2 = STRING: "Site2-VSP4450-3"

RAPID-CITY::rcIsisLogicalInterfaceName.3 = STRING: "Site3-VSP4900-4"

RAPID-CITY::rcIsisLogicalInterfaceName.4 = STRING: "Site4-XA1480-2"

RAPID-CITY::rcIsisLogicalInterfaceName.5 = STRING: "Site5-XA1480-1"

[...]

lstevens@toolbox:~$abc

Then find the index number of that ifIndex in the ISIS interface table:

lstevens@toolbox:~$ snmpwalk -v 2c -c public 10.8.4.28 .1.3.6.1.3.37.1.3.2.1.2

RFC1155-SMI::experimental.37.1.3.2.1.2.1 = INTEGER: 192

RFC1155-SMI::experimental.37.1.3.2.1.2.2 = INTEGER: 193

RFC1155-SMI::experimental.37.1.3.2.1.2.3 = INTEGER: 194

RFC1155-SMI::experimental.37.1.3.2.1.2.4 = INTEGER: 198

RFC1155-SMI::experimental.37.1.3.2.1.2.5 = INTEGER: 232

RFC1155-SMI::experimental.37.1.3.2.1.2.6 = INTEGER: 236

RFC1155-SMI::experimental.37.1.3.2.1.2.7 = INTEGER: 296

RFC1155-SMI::experimental.37.1.3.2.1.2.8 = INTEGER: 300

RFC1155-SMI::experimental.37.1.3.2.1.2.9 = INTEGER: 1600

RFC1155-SMI::experimental.37.1.3.2.1.2.10 = INTEGER: 1601

RFC1155-SMI::experimental.37.1.3.2.1.2.11 = INTEGER: 1602

RFC1155-SMI::experimental.37.1.3.2.1.2.12 = INTEGER: 1603

RFC1155-SMI::experimental.37.1.3.2.1.2.13 = INTEGER: 1604

lstevens@toolbox:~$

In the above, ifIndex 1600 is index 9 in the table; 1601 ==> 10, etc..

Then you can poll the Up-Adj counters:

lstevens@toolbox:~$ snmpwalk -v 2c -c public 10.8.4.28 .1.3.6.1.4.1.2272.1.63.2.1.10

RAPID-CITY::rcIsisCircuitNumUpAdj.1 = INTEGER: 0

RAPID-CITY::rcIsisCircuitNumUpAdj.2 = INTEGER: 0

RAPID-CITY::rcIsisCircuitNumUpAdj.3 = INTEGER: 1

RAPID-CITY::rcIsisCircuitNumUpAdj.4 = INTEGER: 0

RAPID-CITY::rcIsisCircuitNumUpAdj.5 = INTEGER: 0

RAPID-CITY::rcIsisCircuitNumUpAdj.6 = INTEGER: 0

RAPID-CITY::rcIsisCircuitNumUpAdj.7 = INTEGER: 1

RAPID-CITY::rcIsisCircuitNumUpAdj.8 = INTEGER: 1

RAPID-CITY::rcIsisCircuitNumUpAdj.9 = INTEGER: 1

RAPID-CITY::rcIsisCircuitNumUpAdj.10 = INTEGER: 1

RAPID-CITY::rcIsisCircuitNumUpAdj.11 = INTEGER: 1

RAPID-CITY::rcIsisCircuitNumUpAdj.12 = INTEGER: 1

RAPID-CITY::rcIsisCircuitNumUpAdj.13 = INTEGER: 1

lstevens@toolbox:~$

Good luck!

RE: SNMP monitoring of Fabric Extend tunnel

Jon_P — Thu, 13 Jan 2022 12:21:00 GMT

Thanks for pointing me in the right direction. I was finally able to find the right object in our SNMP software's MIB browser by drilling down to
experimental/isisMIB/isisObjects/isisCounters/isisCircuitCountertable/isisCicNumAdj