• June 22, 2018, 04:19:38 PM
Welcome, Guest. Please login or register. Registration is free.
Did you miss your activation email?

Author Topic: SNMP monitoring of SPB interfaces  (Read 1094 times)

0 Members and 1 Guest are viewing this topic.

Offline evangottlieb

  • Rookie
  • **
  • Posts: 1
SNMP monitoring of SPB interfaces
« on: January 19, 2016, 10:05:37 AM »
Wondering if anyone has ever looked, or had any luck with, monitoring ISIS interfaces and SPB adjacencies on the VSP platforms using SNMP?   I'm trying to use PRTG to monitor the links between my switches and would like to know when my adjacencies fail or are otherwise unusable, however it seems as if the switches don't reply to the MIB OID's that are provided by Avaya.  I've done SNMP walks on various models including the VSP4K, VSP7K, and even ERS4850 and can't seem to pull the right data.   

The furthest I have gotten, was being able to monitor the ISIS ADJ STATE (OID 1.3.6.1.3.37.1.6.1.1.1.<index>.1, and when it is up is it great, but when it goes down the OID actually disappears and PRTG reports it as a snmp error #223 (OID not found).

I know there has to be some way of monitoring this, otherwise how is EDM and moving forward AFO supposed to be able to pull the data?   

Any thought from anyone would be greatly appreciated.

Thanks!!


Offline justmacs

  • Rookie
  • **
  • Posts: 10
Re: SNMP monitoring of SPB interfaces
« Reply #1 on: January 20, 2016, 07:00:32 PM »
I use syslog for this currently. The VSP logs when adjacencies go up or down. I then have a script that alerts based on the message. It would be neat to use SNMP but probably better to use syslog or SNMP traps.

Offline krc

  • Rookie
  • **
  • Posts: 10
Re: SNMP monitoring of SPB interfaces
« Reply #2 on: December 06, 2017, 03:51:13 PM »
I have a script which runs every minute and basically grabs the adjacency list as well as do a count, then save that to compare to the next poll and post that to our monitoring system.

Snippet from script (two vars):
adjcount=`snmpwalk -t8 -v2c -Ov -c <snmp-string> <host> .1.3.6.1.4.1.2272.1.63.10.1.3 | wc -l`
adjs=`snmpwalk -t8 -v2c -Ov -c <snmp-string> <host> .1.3.6.1.4.1.2272.1.63.10.1.3`

I compare the count and if it's lower, bells go off and the "diff" is also noted/shown, if the count increases then nothing happens.

I also watch the SPB adjacency "up-timer", low count (timeticks) sets bells off.
OIDs:
spbnames        : 1.3.6.1.4.1.2272.1.63.10.1.3 : branch
circuituptime   : .1.3.6.1.3.37.1.6.1.1.11 : branch