OpenView with MXOne (MD110 on Suse Linux) 1

[ehe]

Hi,

I'm an IT management expert, and I need some information about SNNP supervision with MXOne ericsson (I understood it is a MD110 on Suse Linux) :
1) How can I enable SMMP suppervision on this suse box (which module do I need to use or to enable)?
2) Is it possible to use EVM with an old HP OpenView (Network Node Mamager module) release 6.41?
3) If I don't use EVM which objects I could see on the OpenView Map and which objects I could not see and supervise?
4) Could someone give me some documentation about this 3 previous questions?

Thanks.

 

[whosrdaddy]

Ericsson uses BMC patrol with his own agent. Though enabling SNMP on the suse platform should be no problem, I am not sure for the TS software though...

-----------------------------------------------------
What You See Is What You Get
Never underestimate tha powah of tha google!

 

[ehe]

Hi whosrdaddy,

In fact, my client upgraded his MD110 to MX-One. And they already used HP OpenView NNM (release 6.41) maps to supervise these MD110. Now, they use BMC patrol (with MX-ONE MANAGER AVAILABILITY) to supervise these MX-One, but they would like to have MX-One objects on a HP OpenView NNM map.
So I’m looking for a HP OpenView plug-in or another solution to use with MX-One.
If there are no plug-in, I would like to know how I could use the SNMP Bridge module from BMC patrol (MANAGER AVAILABILITY. Could someone send me documentation about this SNMP Bridge module and send me SNMP MIBs? I would like to know how to activate this module and which data could I collect with it (SNMP trap and/or polling).
Do I necessary have to use this SNMP Bridge module, or could I receive SNMP traps and make SNMP polling directly from these Linux MX-One SUSE systems?

Thanks.

 

[whosrdaddy]

this is what I could find about SNMP in Alex:

[tt]
OPERATIONAL DIRECTIONS 69/154 31-ANF 901 14 Uen E

Telephony Server SNMP Support and Alarm Notification
Copyright

Ericsson AB 2006 - All Rights Reserved

Disclaimer

No part of this document may be reproduced in any form without the written permission of the copyright owner.

The contents of this document are subject to revision without notice due to continued progress in methodology, design and manufacturing. Ericsson shall have no liability for any error or damage of any kind resulting from the use of this document.

Abstract


Contents

1 General

2
SNMP Management Support

3
Supported Ericsson MD110 SNMP MIB Objects

4
Supported Ericsson MD110 SNMP Traps

5
Configuration
5.1 General Configuration
5.2 Configuration of the SNMP Daemon
5.3 Alarm Notification Using E-mail and SMS
5.4 Using net-snmp Tools to Verify the Installation


--------------------------------------------------------------------------------

1 General
The Telephony Server can be managed from a Simple Network Management Protocol (SNMP) management system and configured to send alarm notifications by e-mail or text messaging using Short Messaging Service (SMS).

This document describes the Telephony Server SNMP support and how to configure alarm notification.

2 SNMP Management Support
The Telephony Server can be monitored from an SNMP management system, if desired. The SNMP implementation in the Telephony Server is based on net-snmp . More documentation can be found in the / usr/share/doc/packages/net-snmp directory or at

http://www.net-snmp.org.

Net-snmp is one of the packages installed along with the operating system on the MX-ONE Telephony Server. During installation, the net-snmp daemon is configured to use the AGENT_X protocol.

The program ALSNMP in the MX-ONE Telephony Systems communicates with the net-snmp daemon to add support for parts of the Ericsson-MD110 SNMP MIB. It also supports alarm detection and supervision, and querying of the revision of the MX-ONE Telephony System.

The following MIBs are supported:

MIB-2 - General network statistics (RFC 1213)
Net-snmp agent extensions - Processes, disks, memory, load average, shell commands, and error handling
SNMPv3 MIBS (RFC 2571-6)
Alarm handling and version query as per Ericsson-MD110-SNMP-MIB
Additional MIBs may also be added by the administrator, but must be configured separately.

The snmp daemon (snmpd) is installed in each LIM node of the MX_ONE Telephony System. Consequently, the network management system monitors nodes individully as well as the entire system view.

3 Supported Ericsson MD110 SNMP MIB Objects
In the current Telephony Server version, only the following objects in the Ericsson MD110 SNMP MIB are supported with read-only access:

md110Release - Reading of release information for the Telephony Server OID = .1.3.6.1.4.1.193.8.1.1
mdAlarmStatus - Reading of alarm status for the Telephony Server OID = .1.3.6.1.4.1.193.8.1.3.1.2
activeAlarms - Reading of active alarms in the Telephony Server OID = .1.3.6.1.4.1.193.8.1.3.2.1.1.1.1-10000
4 Supported Ericsson MD110 SNMP Traps
The following traps may be sent from the Ericsson MD110 SNMP MIB to the trap2sinks as defined in the /etc/snmpd.conf file.

mdAlarmStatusChange - Information sent, and the alarm level changed to that indicated
OID = .1.3.6.1.4.1.193.8.1.0.2000

mdAlarmCritical - Information about a new critical alarm OID = .1.3.6.1.4.1.193.8.1.0.1
mdAlarmMajor - Information about a new major alarm OID = .1.3.6.1.4.1.193.8.1.0.2
mdAlarmMinor - Information about a new minor alarm OID = .1.3.6.1.4.1.193.8.1.0.3
mdAlarmWarning - Information about a new warning alarm OID = .1.3.6.1.4.1.193.8.1.0.4
mdAlarmCease - Information about a removed alarm or an alarm cleared by the system OID = .1.3.6.1.4.1.193.8.1.0.5

5 Configuration
SNMP can be configured by the tools provided in the distribution (/usr/bin/snmpconf) or by editing the configuration files in the /etc directory.

5.1 General Configuration
Information on which mibs are supported to translate by tools in the distribution is stored in the /etc/snmp.conf. The following two entries are used:

mibdirs - Points to the directory where mib files are stored (/usr/share/snmp/mibs)

mibs - Lists mibs to be parsed by the tools as default (+Ericsson-DNA-SNMP-MIB:Ericsson-MD110-SNMP-MIB)
5.2 Configuration of the SNMP Daemon
The SNMP agent used in the Telephony Server is a daemon called snmpd ; the associated configuration file is /etc/snmpd.conf.

The snmpd agent must be forced to reread the configuration file after it has been updated by typing /etc/init.d/snmpd reload .

Configuration information for the MIB-2 can be found in the /usr/share/doc/packages/net-snmp directory or at

http://www.net-snmp.org

.

5.2.1 System Information
The agent is configured to fit the installation by editing the configuration file. At a minimum, the following entries should be updated in every LIM:

syslocation - Physical location of the system
syscontact - Contact information for the administrator of the system
5.2.2 Community Settings
In most cases the default community settings should be changed to prevent easy access to the net-snmp agent.

rwcommunity - The community name to allow write access
rocommunity - The community name to allow read access
5.2.3 Additional Trap-Sending Configuration
If external trap monitoring is required, change the configuration file as follows:

trap2sink - More than one trap monitoring system can be defined (one per line).
trapcommunityname - The community name that will accompany the sent trap
At installation the default trap2sink is defined to "localhost", thus, sending all traps to the snmptrapd running on the same MX-ONE Telephony System.

More trap2sinks may be added to send information to additional trap monitors or management systems. This is done by adding one line for each new trap monitor or management system.

If the snmptrapd functionality to send mail or SMS is not required (as mentioned below), then delete the default line containing "localhost".

5.2.4 Other SNMP Traps
The default setup of the net-snmp daemon will send a trap at startup (cold start), and traps if authentication fails.

Other traps like disk monitoring can be enabled by changing the configuration by editing the /etc/snmpd.conf file, see manpages "man snmpd.conf".

The snmpd agent must be forced to reread the configuration file after it has been updated by typing /etc/init.d/snmpd reload .

5.3 Alarm Notification Using E-mail and SMS
The Telephony Server can be configured to send alarm notifications by e-mail or Short Messaging Service (SMS), or both. The notices are based on the SNMP application snmptrapd . The application receives and logs SNMP TRAP messages, then translates them into an e-mail format. A public e-mail-to-SMS server can be used to send the notification to a mobile phone using SMS.

Notification is configured by editing the /etc/opt/eri_sn/snmp/snmptrapd.conf file. Enter the destination e-mail address or addresses for the notifications as indicated in the following lines:


Example 1

#traphandle Ericsson-MD110-SNMP-MIB::mdAlarmStatusChangeExample 2

${MD_ROOT}/bin/snmpAction.pl <e-mailaddress>Example 3

#traphandle Ericsson-MD110-SNMP-MIB::mdAlarmCriticalExample 4

${MD_ROOT}/bin/snmpAction.pl <e-mail address>Example 5

#traphandle Ericsson-MD110-SNMP-MIB::mdAlarmMajorExample 6

${MD_ROOT}/bin/snmpAction.pl <e-mail address>Example 7

#traphandle Ericsson-MD110-SNMP-MIB::mdAlarmMinorExample 8

${MD_ROOT}/bin/snmpAction.pl <e-mail address>Note:
To send SMS notifications, enter the e-mail address of the public e-mail-to-SMS server.


The snmptrapd application must be forced to reread the configuration file if it is updated by typing killproc -HUP snmptrapd .

After a reboot, perform the following procedure to get the snmptrapd application up and running:

Table 1 >/home/mduser # cd /usr/share/doc/packages/net-snmp/

>/usr/share/doc/packages/net-snmp # cp rc.snmptrapd /etc/init.d/snmptrap

>/usr/share/doc/packages/net-snmp # chmod 555 /etc/init.d/snmptrap

>/usr/share/doc/packages/net-snmp # chkconfig snmptrap on

insserv: script eri_om_old: service eri_om already provided!

: script eri_om_old: service eri_om already provided!

>/usr/share/doc/packages/net-snmp # chkconfig snmptrap

snmptrap on


For additional information regarding configuration of this feature, type: man snmptrapd.conf

5.4 Using net-snmp Tools to Verify the Installation
By use the command snmpwalk, a check is performed that the daemon is running and in contact with the ALSNM --P program .

snmpwalk -v 2c -c public -m all localhost 1.3.6.1.4.1.193.8

At least the "md110Release" and "mdAlarmStatus" objects should be printed, and optionally any "activeAlarms" object.

See also the commands: snmpget , snmpgetnext , and snmptable .

[/tt]

-----------------------------------------------------
What You See Is What You Get
Never underestimate tha powah of tha google!