|Osmius Agent Avaya Media Server|
|Agent name: osm_ag_AVAYAMSV||Agent Code: AVAYAMSV|
|Contenido:||User manual for Osmius Agent gor Avaya Media Servers|
|Date Created: 26/04/2010||Date Reviewed:|
This is a generic Agent that is able to monitor all Avaya Media Servers Series (specially S8730 Media Servers) and their Media gateways (specially G650 gateways). It can monitor several parameters device collecting events through snmp pooling (“Pool Events”) and through traps reception (“Trap Events”).
Like other Osmius agents this one has been developed using ACE C++ libraries that provides general features like superior performance, real multiplatform capabilities and robustness, so you need to install ACE properly in order to install and run this agent in case you want to compile it your self (You can forget this if you install Osmius agents using the wizard installer). More about installation here.
This agent also needs the Net-SNMP fantastic libraries Net-SNMP.
The Osmius AVAYAMSV agent offers several basic events and up to ten customizable events using configuration parameters such as the OID, to allow the user to create new events and adapt this agent to a particular Avaya Media Server. The basic events have been chosen by network experts with the idea of develop an generic Avaya Media Server Agent.
Using the Osmius Web Console the users access to a MIB Navigator to load MIBS and to search for the appropriate snmp oid to create their own events.
Osmius also has an agent to receive and process **SNMP Traps** and to redirect them into the event correlation system as they were Osmius “normal” events. For each Agent Type (Instance Type) we can configure several “Trap Events” and in this Avaya Media Server Agent we have chosen the most interesting with the idea, again, of developing an generic Avaya Media Server Agent.
In this agent all the provided events are non-intrusive events, this is remote events, so they can be retrieved from the network outside of the Instance being monitored. Events are build upon the versions 1 and 2 (2c) of SNMP protocol.
Here you can find a good SNMP C API programming guide.
As a general rule each Osmius agent can monitor only one Instance Type. If you are not familiar with these concepts please review the Concepts Glossary. Each Instance is defined in the configuration file (more information in agents & instances) and depending on the agent we need to provide the Instance Connection INFO.
The connection information or connection_info is data that the agent needs to know to connect to the instance. (See more about the connection_info)
In the particular case of Avaya agent the CONNECTION_INFO field has no information needs as it uses the generic SNMP fields like Nodename, read community and snmp port.
In this case:
|EVENT||DESCRIPTION||c||tsegundos||w||a||Return values||Extra Parameters / Observations|
|AVOSVERS||Operating system running on the server||1||86400||0||0||-1 o 0: Error. 1: Ok||Silent mode ( -s) recommended. “info” Event don't configurable with the console|
|AVOSBDAT||Operation system build date||1||86400||0||0||-1 o 0: Error. 1: Ok||Silent mode ( -s) recommended. “info” Event don't configurable with the console|
|AVCMLONM||CM load number||1||86400||0||0||-1 o 0: Error. 1: Ok||Silent mode ( -s) recommended. “info” Event don't configurable with the console|
|AVCMRLNM||CM release number||1||86400||0||0||-1 o 0: Error. 1: Ok||Silent mode ( -s) recommended. “info” Event don't configurable with the console|
|AVCMRLST||CM release string||1||86400||0||0||-1 o 0: Error. 1: Ok||Silent mode ( -s) recommended. “info” Event don't configurable with the console|
|AVCMTRDT||Translation date||1||86400||0||0||-1 o 0: Error. 1: Ok||Silent mode ( -s) recommended. “info” Event don't configurable with the console|
|AVCMLCDT||License installation date||1||86400||0||0||-1 o 0: Error. 1: Ok||Silent mode ( -s) recommended. “info” Event don't configurable with the console|
|AVOSCPUF||Porcentage of free cpu. Instance availability event||1||300||10||5||-1: Error N: valor||Interesant parameter for capacity plannings|
|AVOSCPUF||Number of gateways with H248 link down. Instance availability event||0||300||1||2||-1: Error N: valor||Interesant parameter for capacity plannings|
|AVUS0001 a AVUS0010||These are user events prepared to read the oid parameter and send it back to the Osmius process.||0||600||1||1||-1,0: Error. 1: ok string returned. N: ok value returned.||-O “oid” [-N nodename] [-K community_name] [-P port] [-Q timeout] [-V 1,2]|
|AVOSVERS||Operating system running on the server||.188.8.131.52.4.1.68184.108.40.206.25.1.0|
|AVOSBDAT||Operation system build date||.220.127.116.11.4.1.6818.104.22.168.25.2.0|
|AVCMLONM||CM load number||.22.214.171.124.4.1.68126.96.36.199.25.3.0|
|AVCMRLNM||CM release number||.188.8.131.52.4.1.68184.108.40.206.25.4.0|
|AVCMRLST||CM release string||.220.127.116.11.4.1.6818.104.22.168.25.5.0|
|AVCMLCDT||License installation date||.22.214.171.124.4.1.68126.96.36.199.25.7.0|
|AVOSCPUF||Porcentage of free cpu. Evento de disponibilidad||.188.8.131.52.4.1.68184.108.40.206.6.14.0|
|AVOSCPUF||Number of gateways with H248 link down. Evento de disponibilidad||.220.127.116.11.4.1.6818.104.22.168.106.10.0|
Here is briefly the capabilities of this agent about its trap events, further down on this page we will describe each of the trap events in more detail.
|AVTRAPGN||Generic Event Trap|
This Agent only need one trap event because all Avaya Media Server alarms use these same three traps: alarmMajor, alarmMinor, alarmWarning and alarmResolved.
In order to compile, this agent requires a set of prerequisites, which are generic to compile any Osmius agent, you can see these prerequisites.
This agent needs also the Net-SNMP libraries and includes ( “libsnmp” in Ubuntu ) usually found here: http://net-snmp.sourceforge.net/.
From the agent directory using console or terminal.
%ACE_ROOT%\bin\mpc.pl -type gnuace osm_ag_avayamsv.mpc
gmake -f Osm_Ag_Avayamsv_Osmius
Binaries are automatically installed in the bin directory of OSM_ROOT base directory.
Teh Osmius AVAYAMSV agent have the same running features of the other Osmius agents. You can check it out int he section Start and Stop Agents.
To run the AVAYAMSV agent without Osmius web console:
|osm_ag_AVAYAMSV -c osm_ag_AVAYAMSV.ini -m MASTERAG -p 1950 -d [>> osm_ag_AVAYAMSV1.log]1)|
This Osmius agent, like the others Osmius agents, allows the execution in standalone mode. This option may be particularly useful when developing a new agent or to perform specific agent tests, but in AVAYAMSV agent stand alone mode we only can test “pool events” because “trap events” are received by Osmius SNMPTRAP Agent.
Basically you have to add a new value, called SNDCMD, to the Osmius agent configuration file (osm_ag_AVAYAMSV.ini) as shown here.
Then you must run the agent setting the Master Agent and communications port to zero, for example:
|osm_ag_AVAYAMSV.exe -c osm_ag_AVAYAMSV.ini -m 00000000 -p 0 -d|
|Creating an instance with all its events in silent mode||N/A|
|Creating an instance with all its events with custom text||N/A|
|Creating an instance with all its events but no custom text||N/A|
|Declaration of 3 instances with all its events to 5 seconds and keep it |
running for 48 hours
|Declare 2 instances, cause a disconnect and then reconnect||it can't be do in this agent||N/A|
|Declare 1 instance and test each event||OK||N/A|
|Elimination of general parameter and check unbootable||OK||Delete RECONN|
|Elimination of instance CONN_INFO and check unbootable||OK||AVAYAMSV Instances don't need connection info|