phoneguy55
Programmer
Curious what everyone is doing for SNMP with Avaya 7/8 with AVP? Moving from Avaya 6 to 7 and all i can find is this which hasn't been that helpful.
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!
Avaya 7/8 with AVP and SNMP
- Thread starter phoneguy55
- Start date
- Status
It only traps via the Utility Server.
AVP is a special VMware offer called VMware Essentials. It's what you or I would use if we had a software application and we wanted to pack it up as a OVA and sell someone a piece of hardware as an appliance to run the thing, we get the cheap VMware.
You'll see in the AVP kickstart file that the Utility Server has a sub-interface to do the services port stuff. There is also a syslog destination from ESXi to the Utility Server. The Utility Server's SPIRIT Agent receives the syslog and when it sees stuff it recognizes, it'll convert that to an SNMP trap.
If you want to see what they are, you can go into Inventory and Manage Serviceability Agents in SMGR and look at "Notification Filter Profile". That's something that lets you say "I want this device to trap to this NMS but only with these specific traps". So, you can pick Utility Services/AVP Utilities and see there's about a dozen traps or so available on it. PSU died, HDD died, that sort of thing.
Otherwise, can you enable SNMPv3 access on the machine via SMGR and as well via a CLI script on the machine if you happened to not have a SMGR in your environment, but it does mention that where a SMGR exists, it's mandatory to configure SNMP for US/AVP Utilities that way.
You can setup a SNMPv3 account that can poll the basic Linux net-snmp stuff.
AVP is a special VMware offer called VMware Essentials. It's what you or I would use if we had a software application and we wanted to pack it up as a OVA and sell someone a piece of hardware as an appliance to run the thing, we get the cheap VMware.
You'll see in the AVP kickstart file that the Utility Server has a sub-interface to do the services port stuff. There is also a syslog destination from ESXi to the Utility Server. The Utility Server's SPIRIT Agent receives the syslog and when it sees stuff it recognizes, it'll convert that to an SNMP trap.
If you want to see what they are, you can go into Inventory and Manage Serviceability Agents in SMGR and look at "Notification Filter Profile". That's something that lets you say "I want this device to trap to this NMS but only with these specific traps". So, you can pick Utility Services/AVP Utilities and see there's about a dozen traps or so available on it. PSU died, HDD died, that sort of thing.
Otherwise, can you enable SNMPv3 access on the machine via SMGR and as well via a CLI script on the machine if you happened to not have a SMGR in your environment, but it does mention that where a SMGR exists, it's mandatory to configure SNMP for US/AVP Utilities that way.
You can setup a SNMPv3 account that can poll the basic Linux net-snmp stuff.
- Status
Similar threads
- Locked
- Question
