Retrieving alarms using OSSI?

[drsprite]

Hi there, another OSSI question.

My understanding is that Avaya's SNMP gets its data from OSSI. We are using Nagios to poll our systems for Alarms, and Avaya's SNMP likes to time out a lot. I'd rather poll ossi with telnet if possible. Is there a way to grab major alarms using OSSI?

I can view the alarms we have using cdisplay alarms, but it's showing me all my non-critical station-level alarms.

Curious if there's a field that will only show the major alarms (like SNMP OIDs '1.3.6.1.4.1.6889.2.8.1.21.1.1.1' and '1.3.6.1.4.1.6889.2.8.1.4.6.1.6')

Thanks

 

[drsprite]

Actually, I guess I could automatically SSH into the server, run command almdisplay, then parse the data that way. This might be easiest for this scenario.

Unless someone can think of another way?

Thanks

 

[AvayaTier3]

There are several ways to accomplish this. Contact me if you want to discuss.

A great teacher, does not provide answers, but methods to teach others "How and where to find the answers"

bsh

40 years Bell, AT&T, Lucent, Avaya
Tier 3 for 30 years and counting
[URL unfurl="true"]http://bshtele.com[/url]

 

[kyle555]

just a guess - perhaps you have to pass the values of the fields active, resolved, major, minor, warning, date, time, and optional stuff underneath if you want to customize beyond the default view of "show me all active major minor or warning" that populates the form when you "display alarms

 

[drsprite]

Thanks for the replies.

Right now I'm using an expect script which telnet's in and runs almdisplay. If the string contains "EvtID", then it'll report to Nagios that we have an alarm. EvtID is a column header that only shows up if there's events to show. If there's events, then we have an alarm. As of right now, this will work for our needs to give us a heads up to log into the web interface to get more details on what the alarm is.

 

[AvayaTier3]

cdisp alarm
f0001ff00       0003ff00        0004ff00
dy      y       y
t

cdisp ala
                ALARM REPORT
                The following options control which alarms will be displayed.
                ALARM TYPES
 0001ff00 Active?       1
        n(o)    y(es)
 0002ff00 Resolved?     1
        n(o)    y(es)
 0003ff00 Major?        1
        n(o)    y(es)
 0004ff00 Minor?        1
        n(o)    y(es)
 0005ff00 Warning?      1
        n(o)    y(es)
                REPORT PERIOD
 0010ff00 Interval:     1
        h(our)  d(ay)   w(eek)  m(onth) a(ll)

You can do this from linux with expect


A great teacher, does not provide answers, but methods to teach others "How and where to find the answers"

bsh

40 years Bell, AT&T, Lucent, Avaya
Tier 3 for 30 years and counting
[URL unfurl="true"]http://bshtele.com[/url]

 

[drsprite]

Would you happen to know how to handle Expect on a standby server? Standby's hangup telnet after login, and expect just exits. Trying to figure out how to have expect tell the script that it hung up because of standby server, and not because of a problem.

 

[kyle555]

maybe you can trigger off the messages of "SAT cannot run on standby server" and "this server going active" when an interchange happens?

 

[drsprite]

That's what I thought. I saw it once, but haven't seen it since. Now I'm getting "Connection closed by foreign host". Perhaps I trigger off that for the standby server.

 

[kyle555]

Well, you'd probably have to go in on ports 22/23 at the Linux shell to wait for those messages to be echoed to your terminal. 5022/5023 are directly into the Avaya SAT, so unless its running, you'll get "SAT can't run on standby server" and evidently "connection closed by foreign host

 

[drsprite]

Ah, yes. I'm going in on 5023 which is why I'm seeing the connection closed. I'm losing it with these scripts today. Thanks for the 23/5023 verbiage reminder