Snmp Implementaion Doc

SDP Implementation Instruction - SNMPSDP 5

16/154 31-FAM 901 107/5 Uen G

Copyright

Ericsson AB 2010. All rights reserved. No part of this document may bereproduced in any form without the written permission of the copyright owner.

Disclaimer

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

Trademark List

Ericsson is the trademark or registered trademark of Telefonaktiebolaget LMEricsson. All other products or service names mentioned in this document aretrademarks of their respective companies.

16/154 31-FAM 901 107/5 Uen G | 2013-05-08

Contents

Contents

1 Introduction 11.1 Purpose and Scope 11.2 Typographic Conventions 1

2 Prerequisites 32.1 Prerequisites for the User 32.2 Prerequisites for the System 3

3 Workflows for RHEL 53.1 Activate the SNMP Solution 5

4 Workflows for Solaris 74.1 Activate the SNMP Solution 74.2 Disable the Legacy solution 74.3 Fallback to the Legacy solution 74.4 Finalize the SNMP solution 8

5 Sequences 95.1 Configuring the NMS 95.2 Enable HW and System Alarms via SNMP 95.3 Enable Application Alarms via SNMP 105.4 Disable Application Alarms via TXF 105.5 Re-enable HW and System Alarms via SunMC 105.6 Re-enable Application Alarms via TXF 115.7 Disable Application Alarms via SNMP 115.8 Finalize the disabling of HW and System Alarms via SunMC 115.9 Finalize the disabling of Application alarms via TXF 11

Glossary 13

Reference List 15

16/154 31-FAM 901 107/5 Uen G | 2013-05-08

SDP Implementation Instruction - SNMP

16/154 31-FAM 901 107/5 Uen G | 2013-05-08

Introduction

1 Introduction

1.1 Purpose and ScopeThis document contains the implementation instructions for using SNMP forfault management.

The target groups for this document are as follows:

System Administrator

Installation Personnel

For more information regarding the target groups, see SDP Customer ProductInformation Overview, Reference [1].

1.2 Typographic ConventionsThis document follows a set of typographic rules that make the documentconsistent and easy to read. The typographic conventions can be found in theSDP Customer Product Information Overview, Reference [1].

116/154 31-FAM 901 107/5 Uen G | 2013-05-08


2 16/154 31-FAM 901 107/5 Uen G | 2013-05-08

Prerequisites

2 Prerequisites

2.1 Prerequisites for the UserThe team that will perform the implementation described in this document musthave good knowledge about Solaris or RHEL, SDP and how to configure theused NMS.

2.2 Prerequisites for the SystemThis instruction is applicable for any newly installed or upgraded SDP. SDPuses ESA (a common SNMP agent within Ericsson) to handle SNMP. The ESASW is fully bundled in the SDP SW and shall not be downloaded or installedseparately.

SNMP Alarms for System and Application is supported for any HW where theSDP is supported.

The HW and application alarms are supported for the following list of HW.

Sun Fire V440 (V440) Sun Netra 440 (N440) Sun Fire V445 (V445) Sun Netra T2000 (N2000) Sun Enterprise T5220 (T5220) Sun Fire X4270 (X86 M2) HP ProLiant G7 (X86 DL380) HP ProLiant Gen8 (X86 DL360)For these hardware only application alarms are available.

Sun Fire E2900 (E2900) Sun 4800 (SF4800)

316/154 31-FAM 901 107/5 Uen G | 2013-05-08


4 16/154 31-FAM 901 107/5 Uen G | 2013-05-08

Workflows for RHEL

3 Workflows for RHEL

Following workflow describes the way to integrate the SDP alarm handlingtowards an NMS.

3.1 Activate the SNMP SolutionAfter these steps the NMS will receive and monitor the SNMP Traps from theSDP.

Table 1 Activate the SNMP Solution

Sequence Number Chapter Number/Title1 Section 5.1 Configuring the NMS on page 9

516/154 31-FAM 901 107/5 Uen G | 2013-05-08


6 16/154 31-FAM 901 107/5 Uen G | 2013-05-08

Workflows for Solaris

4 Workflows for Solaris

Following workflows describes the way to change the alarm handling from alegacy solution where TXF is used for application alarms and SunMC is usedfor System and HW alarms to an SNMP solution used for all alarms. Theworkflows will give a time frame where both solutions are active simultaneously(except for HW and System alarms, where the SNMP solution will be used)to avoid downtime. If a legacy solution does not exist or looks different theworkflows have to be adapted, mainly by skipping some sequences.

4.1 Activate the SNMP SolutionAfter these steps the NMS will receive and monitor the SNMP Traps from theSDP together with the eventual Legacy solution (except for HW and Systemrelated alarms).Table 2 Activate the SNMP Solution

Sequence Number Chapter Number/Title1 Section 5.1 Configuring the NMS on page 92 Section 5.2 Enable HW and System Alarms via

SNMP on page 93 Section 5.3 Enable Application Alarms via

SNMP on page 10

4.2 Disable the Legacy solutionAfter these steps the NMS will only receive and monitor the SNMP Traps fromthe SDP.

Table 3 Disable the Legacy solution

Sequence Number Chapter Number/Title1 Section 5.4 Disable Application Alarms via TXF

on page 10

4.3 Fallback to the Legacy solutionThis is an exceptional workflow only to be performed if the SNMP solutiondoes not meet the expectations.

716/154 31-FAM 901 107/5 Uen G | 2013-05-08


Table 4 Fallback to the Legacy solution

Sequence Number Chapter Number/Title1 Section 5.5 Re-enable HW and

System Alarms via SunMC on page10

2 Section 5.6 Re-enable ApplicationAlarms via TXF on page 11

3 Section 5.7 Disable ApplicationAlarms via SNMP on page 11

4.4 Finalize the SNMP solutionPerform this workflow when the SNMP solution meets the expectations. Afterthis the Fallback is not possible to perform.

Table 5 Finalize the SNMP solution

Sequence Number Chapter Number/Title1 Section 5.8 Finalize the disabling of HW and

System Alarms via SunMC on page 112 Section 5.9 Finalize the disabling of Application

alarms via TXF on page 11

8 16/154 31-FAM 901 107/5 Uen G | 2013-05-08

Sequences

5 Sequences

Following are the sequences used in the workflows above. Do not run thesequences from top to bottom but follow the workflows above.

5.1 Configuring the NMSHow to configure the NMS is of cource specific for each NMS. Following showswhich resources the SDP provides for the configuration.

5.1.1 Import the MIBs used by ESA

These steps covers where the MIBs ESA uses can be found on an SDP. Thisimport does only have to be done once for the first System using ESA for FaultManagement

1. List the MIB files:

# ls -l /opt/esa/mibs/

2. Copy and import the MIBs into the NMS.

3. Copy topology file to NMS (if applicable), it can be found here./var/opt/www/

5.2 Enable HW and System Alarms via SNMPThe steps should not need to be performed if ESA/SNMP was enabled duringinstallation.

The steps needs to be repeated on both sides of the cluster.

1. Run the configuration script for the PostSolaris part:

# ChSysSetup

2. Enter the name of the SunMC host:

Enter '-' and press Return.

3. Enter the destination for ESA Traps:

Enter the IP address of the trap destination and press Return.

4. Start ESA

916/154 31-FAM 901 107/5 Uen G | 2013-05-08


# /var/tmp/playlist/bin/esa start

5.3 Enable Application Alarms via SNMPThe steps should not need to be performed if ESA/SNMP was enabled duringinstallation.

The steps shall only be performed at the Host1 server.

1. Re-generate the create requests.

# /opt/EABfds/comproot/PSC-createrequest/0/bin/getCurrentConfig > /tmp/esa-no

# cat /tmp/esa-no | sed 'sUseEsa;noUseEsa;yesg' >/tmp/esa-yes

# /opt/EABsdpcfg/bin/prepareInstallationrequests -f/tmp/esa-yes -p 1

2. Create and Start the new plugin FSC-EsaAlarm

# /opt/sdp/SupportTools/bin/compctrl -u -p

Select FSC-EsaAlarm at both Members. Create and start them

5.4 Disable Application Alarms via TXFThe steps shall only be performed at the Host1 server.

1. Stop the FSC-TXFAlarm plugin:

# /opt/sdp/SupportTools/bin/compctrl -u -p, Select FSC-TXFAlarm at both Members. Unload them

5.5 Re-enable HW and System Alarms via SunMCThe steps needs to be repeated on both sides of the cluster.

1. Run the configuration script for the PostSolaris part:

# ChSysSetup

2. Enter the name of the SunMC host:

Enter the hostname of the SunMC server and press Return.

3. Enter the IP of the SunMC host:

Enter the IP address of the SunMC server and press Return.

10 16/154 31-FAM 901 107/5 Uen G | 2013-05-08

Sequences

4. Enter the destination for ESA Traps:

Enter '-' and press Return.

5.6 Re-enable Application Alarms via TXFThe steps shall only be performed at the Host1 server.

1. Start the plugin FSC-TxfAlarm


Select FSC-TxfAlarm at both Members. Start it

5.7 Disable Application Alarms via SNMPThe steps shall only be performed at the Host1 server.

1. Deleting EsaAlarm component


select FSC-EsaAlarm for both members and delete them.

2. Re-generate the create requests:

# /opt/EABsdpcfg/bin/prepareInstallationrequests -p 1

5.8 Finalize the disabling of HW and System Alarms viaSunMCThe steps needs to be repeated on both sides of the cluster.

1. Uninstall the SunMC Agent.

# /opt/SUNWsymon/sbin/es-uninst -f

2. Remove the SDP from the Sun Management Center

5.9 Finalize the disabling of Application alarms via TXFThe steps shall only be performed at the Host1 server.

1. Delete the FSC-TXFAlarm plugin at both host.


select FSC-TxfAlarm for both members and delete them.

1116/154 31-FAM 901 107/5 Uen G | 2013-05-08


2. Regenerate the create requests

# /opt/EABsdpcfg/bin/prepareInstallationrequests -p 1

12 16/154 31-FAM 901 107/5 Uen G | 2013-05-08

Glossary

Glossary

ESAEricsson SNMP Agent

NMSNetwork Management System

RHELRed Hat Enterprise Linux

SDPService Data Point

SunMCSun Management Center

SNMPSimple Network Management Protocol

TXFTMOS Text File adaptation

1316/154 31-FAM 901 107/5 Uen G | 2013-05-08


14 16/154 31-FAM 901 107/5 Uen G | 2013-05-08

Reference List

Reference List

Ericsson Documents

[1] SDP Customer Product Information Overview, 1/1551-EN/LZN 741 0126Uen

1516/154 31-FAM 901 107/5 Uen G | 2013-05-08

toc1 Introduction1.1 Purpose and Scope1.2 Typographic Conventions

2 Prerequisites2.1 Prerequisites for the User2.2 Prerequisites for the System

3 Workflows for RHEL3.1 Activate the SNMP Solution

4 Workflows for Solaris4.1 Activate the SNMP Solution4.2 Disable the Legacy solution4.3 Fallback to the Legacy solution4.4 Finalize the SNMP solution

5 Sequences5.1 Configuring the NMS5.1.1 Import the MIBs used by ESA

5.2 Enable HW and System Alarms via SNMP5.3 Enable Application Alarms via SNMP5.4 Disable Application Alarms via TXF5.5 Re-enable HW and System Alarms via SunMC5.6 Re-enable Application Alarms via TXF5.7 Disable Application Alarms via SNMP5.8 Finalize the disabling of HW and System Alarms via SunMC5.9 Finalize the disabling of Application alarms via TXF