Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
SNMP between G430s and CM?
- Thread starter smitj11
- Start date
It can send them anywhere you want. I don't know why you'd want to send them to CM though. SMGR has a SNMP receiver to get traps and see them there. That's where you'd typically point it.
What are you expecting to happen if you send SNMP to CM?
What are you expecting to happen if you send SNMP to CM?
- Thread starter
- #3
Thank you for your reply. Apologies if my questions seem uninformed--my Avaya system was installed about a decade ago by contract and comes with little-to-no documentation of that installation nor do I have any coworkers that were around during the install that I can ask questions of. It's all self-discovery at this point.
I have 5 G430's in remote buildings on my complex, so my hope is that I'd be able to have them send just some sort of alarming to a centralized location--which I thought would be CM because I've got the alarm contacts on my G650's IPSI card wired out to a different alarm aggregator that gets monitored internally. Maybe I'm wrong to think that alarms coming into CM would fire those IPSI alarm contacts?
I defaulted to CM because--and here's the dumb part--I don't know how to access SMGR on my system and we've only ever really interacted with CM for administrative tasks. I have an address for SM--though I have no idea what the logins are--but no idea how to get into SMGR. If you have any direction on that at all, that would be wonderful.
I have 5 G430's in remote buildings on my complex, so my hope is that I'd be able to have them send just some sort of alarming to a centralized location--which I thought would be CM because I've got the alarm contacts on my G650's IPSI card wired out to a different alarm aggregator that gets monitored internally. Maybe I'm wrong to think that alarms coming into CM would fire those IPSI alarm contacts?
I defaulted to CM because--and here's the dumb part--I don't know how to access SMGR on my system and we've only ever really interacted with CM for administrative tasks. I have an address for SM--though I have no idea what the logins are--but no idea how to get into SMGR. If you have any direction on that at all, that would be wonderful.
CM controls the gateways and the gateways can alarm to CM. CM can send SNMP traps to an NMS, so if a gateway had some kind of a problem you could get notification that way.
Or you can just 'display alarms' in CM to see them.
Do you want to login once a day and see? Do you have an NMS you can send the traps to? If you do, and assuming you have SSH access to the gateways, you could point the gateways to SNMP trap to your NMS or you could just do CM. You'd get more info if it was from the gateways themselves, but CM's maintenance routines have enough in there that even just CM sending traps would get you some indication if a gateway was having trouble.
Do you know what release of CM you're on? I'd imagine 6.0/6.2/6.3
Or you can just 'display alarms' in CM to see them.
Do you want to login once a day and see? Do you have an NMS you can send the traps to? If you do, and assuming you have SSH access to the gateways, you could point the gateways to SNMP trap to your NMS or you could just do CM. You'd get more info if it was from the gateways themselves, but CM's maintenance routines have enough in there that even just CM sending traps would get you some indication if a gateway was having trouble.
Do you know what release of CM you're on? I'd imagine 6.0/6.2/6.3
- Thread starter
- #5
Yea I believe it's CM 6.3. Honestly, I'd prefer not to manually log in once a day and check--that's not really how things work here. We have a separate alarm aggregating device that many things wire into, and then that aggregator is monitored 24/7 by our internal network operations center. We'd get a call or a morning report that says somethings in alarm. So my hope was to have all of my G430's just funnel their alarms into a single place like CM over our network, and then I have the IPSI contacts physically wired to my aggregator (again, though, if the IPSI card provides that kind of functionality I'm not sure).
Do you have a recommendation on the best way to achieve that?
Do you have a recommendation on the best way to achieve that?
I'm curious as to how your IPSI contacts are alarming. I don't believe IPSIs send any alarming information.
What is this aggregator you're talking about? Typically it would be done by SNMP and CM would send the SNMP traps.
Can you login to the CM webpage in the maintenance web interface and look at the SNMP trap configuration? There might already be something there.
What is this aggregator you're talking about? Typically it would be done by SNMP and CM would send the SNMP traps.
Can you login to the CM webpage in the maintenance web interface and look at the SNMP trap configuration? There might already be something there.
- Thread starter
- #7
Yea the IPSI contacts are a gray area for me. I wired them out to my alarm aggregator and within the CM interface I issued a test trap and it does appear to fire those IPSI contacts. But that was only me testing from the CM interface. I'm not sure if any G430 traps coming into CM would generate the same condition?
On my CM--> SNMP Agents page, I've got Any IP Address chosen under "IP Addresses for SNMP Access" (this is all on a closed network and really only the G430s I have the ability to talk to CM) and SNMP v2c enabled.
On my CM--> SNMP Traps page, I've got my G430s listed but I'm sure that I'm doing that wrong and I've been trying to delete them but whenever I click those checkboxes to delete them, the page reloads and says nothing was chosen for deletion. Not sure what that's all about.
Anyways, I work for a utility so it's not just these G430s I care about alarming. We have an alarm aggregator box from another manufacturer that we place on-site and then hardwire everything's alarms into that. Those become alarm points in the aggregator and then the aggregator sends those traps via SNMP to another aggregator in our control centers. For my part, it was my goal to have it such that the G430s SNMP traps to CM, then CM (via IPSI contacts?) hardwires into our alarm aggregator.
On my CM--> SNMP Agents page, I've got Any IP Address chosen under "IP Addresses for SNMP Access" (this is all on a closed network and really only the G430s I have the ability to talk to CM) and SNMP v2c enabled.
On my CM--> SNMP Traps page, I've got my G430s listed but I'm sure that I'm doing that wrong and I've been trying to delete them but whenever I click those checkboxes to delete them, the page reloads and says nothing was chosen for deletion. Not sure what that's all about.
Anyways, I work for a utility so it's not just these G430s I care about alarming. We have an alarm aggregator box from another manufacturer that we place on-site and then hardwire everything's alarms into that. Those become alarm points in the aggregator and then the aggregator sends those traps via SNMP to another aggregator in our control centers. For my part, it was my goal to have it such that the G430s SNMP traps to CM, then CM (via IPSI contacts?) hardwires into our alarm aggregator.
On the SNMP agents page, you're seeing what IPs CM will allow to poll CM. So if you had an SNMP tool on your machine and added your machine's IP to that page you'd be able to snmpwalk -v 2c -c avaya etc etc to poll CM for stuff.
On the SNMP traps page, that's where CM is sending its own alarming.
I'm not sure what you mean by "hardwire" relative to your aggregator box.
An IPSI in a G650 is a little dumber than a G430. You can't configure SNMP polls/traps on an IPSI but you can on a G430.
What you see in the CM webpage has no bearing on what the G430s allow for polling or trapping - that's configured via CLI on the G430s
Can you ssh into your g430s? There's a backdoor password for root that's ggdaseuaimhrke. It was disabled on later firmwares of G430 and you can only access it physically on the services port which is an ethernet port on the box itself. It's 192.11.13.6 and you're 192.11.13.5 with mask 255.255.255.252. It's similar but not exactly like a cisco router, so "show run" will let you know what's programmed on it.
Otherwise, I think I get the idea of your NMS where you have local collectors that phone everything up to the mothership, and I'd imagine it's mainly SNMP based.
On the SNMP access page there's a link to download the SNMP MIB - what exactly is in the text of that link? Avaya changed their SNMP for CM in the 6.3 release. So, there's 2 releases of CM 6.3. From memory, it's the 124 and 143 load. If you did a "list conf soft" in ASA/CM terminal you'd know which version you have. The older version was the G3 MIB (The platform used to be called G3). The newer version should say "Avaya CM MIB" or something like that. It's a lot easier to understand.
I'd imagine that this MIB would need to be loaded up on your NMS. If you pointed your gateways SNMP traps at your collector then you'd want to load the G430 MIB in the monitoring system as well. That's what defines what the messages mean, their severity and stuff like that so you can have rules that say "if you get an SNMP trap from such and such a device and field XYZ says 'minor' then leave it for the morning but if it says 'major' then open a case or email the nightshift NOC to get them on top of it right away".
I'd look into what that aggregator/collector thing is doing because the only contacts on the G650 are for an emergency transfer relay with an 808A panel.
In plain English that means if the IPSI can't talk to CM anymore then the cabinet is down. The contact provided by the 808A is meant for, when the IPSI is offline, to bridge a single analog line to an emergency phone. I suppose you could use that as an indicator of whether the IPSI is up or down, but you'd get far more using SNMP from CM.
On the SNMP traps page, that's where CM is sending its own alarming.
I'm not sure what you mean by "hardwire" relative to your aggregator box.
An IPSI in a G650 is a little dumber than a G430. You can't configure SNMP polls/traps on an IPSI but you can on a G430.
What you see in the CM webpage has no bearing on what the G430s allow for polling or trapping - that's configured via CLI on the G430s
Can you ssh into your g430s? There's a backdoor password for root that's ggdaseuaimhrke. It was disabled on later firmwares of G430 and you can only access it physically on the services port which is an ethernet port on the box itself. It's 192.11.13.6 and you're 192.11.13.5 with mask 255.255.255.252. It's similar but not exactly like a cisco router, so "show run" will let you know what's programmed on it.
Otherwise, I think I get the idea of your NMS where you have local collectors that phone everything up to the mothership, and I'd imagine it's mainly SNMP based.
On the SNMP access page there's a link to download the SNMP MIB - what exactly is in the text of that link? Avaya changed their SNMP for CM in the 6.3 release. So, there's 2 releases of CM 6.3. From memory, it's the 124 and 143 load. If you did a "list conf soft" in ASA/CM terminal you'd know which version you have. The older version was the G3 MIB (The platform used to be called G3). The newer version should say "Avaya CM MIB" or something like that. It's a lot easier to understand.
I'd imagine that this MIB would need to be loaded up on your NMS. If you pointed your gateways SNMP traps at your collector then you'd want to load the G430 MIB in the monitoring system as well. That's what defines what the messages mean, their severity and stuff like that so you can have rules that say "if you get an SNMP trap from such and such a device and field XYZ says 'minor' then leave it for the morning but if it says 'major' then open a case or email the nightshift NOC to get them on top of it right away".
I'd look into what that aggregator/collector thing is doing because the only contacts on the G650 are for an emergency transfer relay with an 808A panel.
In plain English that means if the IPSI can't talk to CM anymore then the cabinet is down. The contact provided by the 808A is meant for, when the IPSI is offline, to bridge a single analog line to an emergency phone. I suppose you could use that as an indicator of whether the IPSI is up or down, but you'd get far more using SNMP from CM.
- Thread starter
- #9
Thanks again for the detailed responses.
I'd need it to be physically wired from something in my G650 to my alarm aggregating box. Nothing else is doable--I can't tell the G430s to send SNMP traps directly to the mothership, they have to hit this aggregator box first. The aggregator box (IMCI Open-I...but a discontinued version) is itself a bunch of contact closures that fire based on contact closures on the end equipment. The aggregator sends that to the mothership via SNMP.
I wired out from the IPSI card based on this guide (see page 189): Link Figure 85 notes pins 4 and 5 as a single alarm pair triggered by a contact closure in the IPSI card itself. I do see the 808A noted there as well, but those are on different pins. What fires that contact closure in the IPSI card then?
I'd need it to be physically wired from something in my G650 to my alarm aggregating box. Nothing else is doable--I can't tell the G430s to send SNMP traps directly to the mothership, they have to hit this aggregator box first. The aggregator box (IMCI Open-I...but a discontinued version) is itself a bunch of contact closures that fire based on contact closures on the end equipment. The aggregator sends that to the mothership via SNMP.
I wired out from the IPSI card based on this guide (see page 189): Link Figure 85 notes pins 4 and 5 as a single alarm pair triggered by a contact closure in the IPSI card itself. I do see the 808A noted there as well, but those are on different pins. What fires that contact closure in the IPSI card then?
I don't think it's doing what you want. What I read is that pins 6/7 and 3/8 can move major/minor alarms from external sources - like your UPS - to the G650.
I read it as the only thing that makes 4/5 close is external equipment on 6/7 and 3/8.
The G650 would close the contact on pins 4/5 to alarm/light/bell or most probably your aggregator box.
The G650's IPSI would also send that up to CM as an external alarm.
You're still not getting any alarms from CM or the gateways to feed down to the IPSI to make pins 4/5 open/close for your aggregator box.
A quick google search on your IMCI stuff leads me to believe it does SNMP. The particular box with the relay contacts on pins 4/5 might be just for more industrial applications with a relay contact for a true/false signal but that particular box must phone up to the mothership somehow and I think the mothership would probably talk SNMP and the right way to get alarming for CM and your gateways would be via SNMP to that mothership
I read it as the only thing that makes 4/5 close is external equipment on 6/7 and 3/8.
The G650 would close the contact on pins 4/5 to alarm/light/bell or most probably your aggregator box.
The G650's IPSI would also send that up to CM as an external alarm.
You're still not getting any alarms from CM or the gateways to feed down to the IPSI to make pins 4/5 open/close for your aggregator box.
A quick google search on your IMCI stuff leads me to believe it does SNMP. The particular box with the relay contacts on pins 4/5 might be just for more industrial applications with a relay contact for a true/false signal but that particular box must phone up to the mothership somehow and I think the mothership would probably talk SNMP and the right way to get alarming for CM and your gateways would be via SNMP to that mothership
- Thread starter
- #11
Shoot, that's what I was afraid of. Truth be told, I wasn't really sure if I'd get what I wanted out of those IPSI contacts. Still not sure if I can have the G430s SNMP direct to the IMCI. I know it communicates SNMP to mothership, but I haven't looked too hard at that aspect. Anyways, thanks for all of the tips.
- Status
Similar threads
- Question