ExtremeSwitching (VSP)

 View Only
  • 1.  SNMP monitoring of Fabric Extend tunnel

    Posted 01-04-2022 07:11


    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?

  • 2.  RE: SNMP monitoring of Fabric Extend tunnel

    Posted 01-10-2022 10:05

    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?

  • 3.  RE: SNMP monitoring of Fabric Extend tunnel

    Posted 01-11-2022 11:20
    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 .
    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"

    Then find the index number of that ifIndex in the ISIS interface table:
    lstevens@toolbox:~$ snmpwalk -v 2c -c public .
    RFC1155-SMI::experimental. = INTEGER: 192
    RFC1155-SMI::experimental. = INTEGER: 193
    RFC1155-SMI::experimental. = INTEGER: 194
    RFC1155-SMI::experimental. = INTEGER: 198
    RFC1155-SMI::experimental. = INTEGER: 232
    RFC1155-SMI::experimental. = INTEGER: 236
    RFC1155-SMI::experimental. = INTEGER: 296
    RFC1155-SMI::experimental. = INTEGER: 300
    RFC1155-SMI::experimental. = INTEGER: 1600
    RFC1155-SMI::experimental. = INTEGER: 1601
    RFC1155-SMI::experimental. = INTEGER: 1602
    RFC1155-SMI::experimental. = INTEGER: 1603
    RFC1155-SMI::experimental. = INTEGER: 1604

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

    Good luck!

  • 4.  RE: SNMP monitoring of Fabric Extend tunnel

    Posted 01-13-2022 04:21
    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