20180808-094533113 - OL-SNMP - ADMIN - FOR - EC27572-02 Draft 003

OL-27572-02
SNMP Administration Guide for the

Explorer Controller
Draft 003 May 29, 2014

Please Read
Important
Read this entire guide. If this guide provides installation or operation instructions,
give particular attention to all safety statements included in this guide.
Notices
Trademark Acknowledgments
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its
affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this
URL: www.cisco.com/go/trademarks.
Third party trademarks mentioned are the property of their respective owners.
The use of the word partner does not imply a partnership relationship between
Cisco and any other company. (1110R)
Publication Disclaimer
Cisco Systems, Inc. assumes no responsibility for errors or omissions that may
appear in this publication. We reserve the right to change this publication at any
time without notice. This document is not to be construed as conferring by
implication, estoppel, or otherwise any license or right under any copyright or
patent, whether or not the use of any information in this document employs an
invention claimed in any existing or later issued patent.
Copyright
© 2014 Cisco and/or its affiliates. All rights reserved.
Information in this publication is subject to change without notice. No part of this
publication may be reproduced or transmitted in any form, by photocopy,
microfilm, xerography, or any other means, or incorporated into any information
retrieval system, electronic or mechanical, for any purpose, without the express
permission of Cisco Systems, Inc.
Contents
About This Guide v
Chapter 1 MIBs 1
Application MIBs ..................................................................................................................... 2
Base MIBs .................................................................................................................................. 4
Master Agent MIB Information ............................................................................................. 5
MIB Location and Compilation.............................................................................................. 6
Object Descriptions .................................................................................................................. 8
SNMP Access and Security ..................................................................................................... 9
Chapter 2 SNMP Access for the Network 11

Define the Network SNMP Listening Interface ................................................................. 12
Configure net-snmp to Monitor dncsInitd ......................................................................... 14
Create an SNMPv3 User ....................................................................................................... 17
Create SNMP Communities for the Network .................................................................... 20
Define SNMPv3 Trap Destination Configuration ............................................................. 22
Chapter 3 Filters in Net-SNMP 25

SNMP Trap Filters in Net-SNMP ........................................................................................ 26
How to Configure SNMP Trap Filters in Net-SNMP ....................................................... 27
Configuring SNMP Trap Filters in Net-SNMP for RepDB and other EC Traps ........... 29
Chapter 4 SNMP Access for the RNCS 35

Define the RNCS SNMP Listening Interface ...................................................................... 36
Create an SNMPv3 User ....................................................................................................... 38
SNMP Communities for the RNCS ..................................................................................... 41
SNMP Traps for the RNCS ................................................................................................... 43
Chapter 5 nbiAgent Configuration 45

Changing the NBI SNMP Object Cache Refresh Interval ................................................ 46
Chapter 6 EC and RNCS Infrastructure SNMP References 49

CIMC........................................................................................................................................ 50
Chapter 7 Customer Information 53
OL-27572-02 iii
Contents
Appendix A SNMP Trap Definitions for Event Logging 55

Application Trap Definitions ............................................................................................... 56
EC RepDB Alarm Definitions............................................................................................... 57
EC Application Alarm Definitions ...................................................................................... 59
RNCS Application Alarm Definitions................................................................................. 60
DNCS-LEGACYNMI Alarm Definition ............................................................................. 61
iv OL-27572-02
About This Guide
About This Guide

Introduction
This guide provides instructions to configure the Explorer Controller (EC) and
Remote Network Control Server (RNCS) for interoperation with a Simple Network
Management Protocol- (SNMP) based network management system (NMS). The
following topics are included in this document:
 Supported Management Information Base (MIB) modules
 SNMP Configuration
- SNMP Listening Interface
- SNMP User/Community Management
- Trap Destination Configuration
 Trap/Alarm Definitions
 Northbound Interface (NBI) Object Refresh Interval
 Hardware and Virtual Machine SNMP References
New in System Release 6.0, the EC and RNCS applications run inside a virtual
machine (VM), as shown in the following figure, using the EC as an example. The
left side of the figure shows a conceptual view of the three layers that together
compose the EC product:
1 Server hardware (for example, the Cisco UCS server)
2 VM Hypervisor (for example, VMWare ESXi)
3 EC VM
The EC VM is shown in more detail on the right side of the figure. The EC VM is
composed of the guest OS, for example Solaris x86, and the EC application that runs
on Solaris x86. The EC SNMP master agent, which is currently Net-SNMP, and the
SNMP sub-agents, provide the SNMP resources for the EC application and network
elements that are provisioned by the EC. In terms of this figure, the RNCS VM is the
same as the EC, except there are different sub-agents running on the RNCS as
explained later in this section.
OL-27572-02 v
About This Guide
In addition to EC or RNCS application-specific information, the guest Solaris x86 OS

running in the EC or RNCS VM supports the SUN-FM-MIB which provides SNMP
objects and notifications pertaining to the OS. The Solaris OS fault manager
architecture (FMA) provides automated diagnosis of faulty hardware and takes
proactive measures when and where appropriate (for example, offline a CPU). In the
VM environment, the FMA handles virtual hardware instead of physical hardware.
The SUN-FM-MIB, therefore, provides SNMP capabilities for FMA and can send
traps out for fault conditions. In some cases, the Cisco UCS’s CIMC, VMware, and
Solaris OS FMA could all be sending out traps for the same hardware issue.
The following lists the EC SNMP sub-agents and the SNMP information for which
they provide:
 Solaris Systems Management Agent (SMA): This is Sun’s implementation of
Net-SNMP and provides SNMP query objects and notifications pertaining to
virtual hardware assigned to the guest OS (Solaris) running in the VM.
 RepDB Agent: Provides SNMP query objects and notifications pertaining to EC
redundancy configuration.
 North Bound Interface Agent (nbiAgent): Provides SNMP query objects
pertaining to the EC database. In addition, nbiagent sends notifications
pertaining to EC processes and also the status of EC communications with the
network elements.
 dncsSNMPAgent: Converts RPC alarms to SNMP traps on behalf of Cisco
network elements provisioned by the EC, such as the Netcrypt, GQAM, MQAM,
CA QAM, and DAVIC QPSK modulator/demodulator.
 dncs-snmpd Agent: The DNCS suite of SNMPD processes is a proxy that is used
by the network management system to query these legacy RF network devices.
The implementation of NBI has not altered the functionality of these processes
and proxies, and the latest DNCS releases continue to support them.
vi OL-27572-02
About This Guide
The following is a list of the RNCS SNMP sub-agents and the SNMP information for
which they provide:
 Solaris Systems Management Agent (SMA): Same function as EC.
 North Bound Interface - Remote (nbiAgentRemote): Similar function as EC
nbiAgent. Provides SNMP query objects pertaining to the RNCS database and
notifications pertaining to the RNCS processes.
 snmpRemote: Provides SNMP notifications pertaining to RNCS process status.
Purpose
The purpose of this guide is to help system administrators compile Cisco MIBs,
implement event logging, and set up SNMP on the EC and RNCS to integrate with
an NMS.
Scope
This guide is not intended to be comprehensive; it focuses on the EC and RNCS VM.
However, chapter 5 does provide references to assist operators in configuring the
server hardware and hypervisor layers to interoperate with a NMS using SNMP. If
you have questions about network elements, applications, or MIB variables, contact
Cisco Services or your account representative.
Document Version
This is the second formal release of this document. This document was modified to
include a description of Net-SNMP trap filters. See Filters in Net-SNMP (on page
25).
OL-27572-02 vii
1 Chapter 1
MIBs
Introduction
Application and Base MIBs have been specified by Cisco Systems for
the network elements so that the devices can be managed with an
SNMP-based NMS. The MIB files are supplied with the network
elements and must be compiled in a specific order on the NMS. These
MIBs, their directory locations on the network elements, and the
compilation dependencies are described in this chapter.
Note: Also referenced are Standard MIBs, which are MIB modules that
have been approved by the Internet Architecture Board (IAB) and exist
under the mib-2 node. The NMS should have the Standard MIBs by
default.
In This Chapter
 Application MIBs .................................................................................... 2
 Base MIBs ................................................................................................. 4
 Master Agent MIB Information ............................................................ 5
 MIB Location and Compilation ............................................................ 6
 Object Descriptions ................................................................................. 8
 SNMP Access and Security.................................................................... 9
OL-27572-02 1
Chapter 1 MIBs
Application MIBs
Application MIBs define the application objects for the respective network elements.
EC MIBs Purpose
SA-ALARM-MIB, Ver. 0.3 This MIB contains the notification object used to
generate alarms (traps).
SA-CONAPP-MIB, Ver. 0.3 This MIB is for network identity and hub
identity information.
SA-CONAPPPERF-MIB, Ver. 02 This MIB provides performance information
including DSM (Digital Session Manager), DRM
(Digital Resource Manager), Signon, DHCT
UNConfig, DHCT IP Provisioning, and the CA
billing interface.
Most of the objects are event counters.
SA-CONAPPSTATUS-MIB, Ver. 0.7 This MIB is for general status information such
as general application running state, general log
level state, and existence of core files.
SA-CONAPPSTATUSBFS-MIB, Ver. 0.4 This MIB is for BFS (Broadcast File System)
status objects.
SA-CONAPPSTATUSCOMMS-MIB Ver. 0.2 This MIB is for network element
communication status with the EC.
SA-CONAPPSTATUSELEM-MIB, Ver. 0.7 This MIB is for information about network
elements and devices managed by the EC.
Information includes identity, address,
initialization states, image download status and
source/session statistics. Examples of elements
include set-tops and edge devices.
SA-CONAPPSTATUSIPG-MIB Ver. 0.1 This MIB is for IPG (Interactive Program Guide)
status objects.
SA-CONNAPPSTATUSPPV-MIB, Ver. 0.4 This MIB is for PPV (Pay-Per-View) status
objects.
SA-CONAPPSTATUSSAM-MIB Ver. 0.2 This MIB is for CSM (Channel Service Manager)
status objects.
SA-CONAPPSTATUSSI-MIB Ver. 0.4 This MIB is for service information (SI) status
objects such as rate measurements and delivery
of STM (System Time Message).
SA-CONNAPPSTATUSTIME-MIB, Ver. 0.5 This MIB provides information about the
Network Time Protocol (NTP) process and
source, and also provides daylight saving
information for hubs and set-tops.
2 OL-27572-02
Application MIBs
EC MIBs Purpose
SA-CONHOSTRESOURCES-MIB This MIB is for the extended version of the
standard Host Resources MIB, for the
Controller. It has items specific to the SA
platform, items that may differ slightly
compared to the standard semantics and a
summary of pertinent resources.
Note: Only the following OIDs from the MIB
are implemented.
saChrSystemUptimeDate
saChrSystemPlatformDescr
saChrSwRunPerfCpuController
saChrSwRunPerfCpuDbase
SA-DNCS-LEGACYNMI-MIB Ver 3.0 This legacy MIB is a proxy for RPC alarm
messages generated by various devices, such as
a QPSK, GQAM, MQAM, CAQAM, or
NetCrypt.
RNCS MIBs Purpose

SA-CONAPP-MIB, Ver. 0.3 This MIB is for network identity and hub
identity information.
SA-CONAPPSTATUS-MIB, Ver. 0.7 This MIB is for general status information
related to applications handled by the
controller.
SA-CONNAPPSTATUSTIME-MIB, Ver. 0.5 This MIB provides information about the
Network Time Protocol (NTP) process and
source, and also provides daylight saving
information for hubs and set-tops.
SA-CONAPPSTATUSSAM-MIB Ver. 0.2 This MIB is for CSM (Channel Service Manager)
status objects.
InformixRepDB MIBs Purpose

Cisco-RepDbHdr-MIB This MIB actively monitors Informix HDR and
generates traps. It also facilitates passive
monitoring by populating MIB objects.
Cisco-RepDbFilesync-MIB This MIB actively monitors rsync functionality
and generates traps. It also facilitates passive
monitoring by populating MIB objects.
OL-27572-02 3
Chapter 1 MIBs
Base MIBs
Base MIBs are required for other MIBs to function.
Base MIBs Purpose

SCIATL-COMMON-MIB, Ver. 1.0 This MIB defines the root for the network MIB
tree and is a core system requirement.
This MIB is required for all applications and
should be compiled first.
There are no objects to manage.
SA-DBDSPROD-MIB, Ver. 1.3 This MIB defines the part of the network MIB
tree where product-specific items are placed. It
is a core system requirement.
This MIB is required for all applications and
should be compiled after the SCIATL-
COMMON-MIB and before any Application
MIB(s).
SA-DBDSGEN-MIB, Ver. 1.2 This MIB defines the part of the network MIB
tree where general items are placed.
This MIB should be compiled after the SCIATL-
COMMON-MIB and before any Application
MIB(s).
SA-CONAPPTC-MIB Dev 0.2 This MIB defines textual conventions for
controller application monitoring.
4 OL-27572-02
Master Agent MIB Information
Master Agent MIB Information

Descriptions
The EC and RNCS SNMP master agent running in the guest OS of the VM
implements a standard set of SNMP MIBs. The operator can obtain a list of the
supported MIBs from this URL: http://net-snmp.sourceforge.net/docs/mibs.
OL-27572-02 5
Chapter 1 MIBs
MIB Location and Compilation

Application and Base MIBs are delivered in specific directories on the EC and RNCS.
To integrate the MIB objects into your NMS, you must compile the MIBs in the
specified order and in accordance with the compilation procedures for your NMS
software.
Location of standard MIBs: dvs/tools/net-snmp/share/snmp/mibs
Note: The RNCS Application MIBs are a subset of the EC Application MIBs. For that
reason, no Application MIB files exist on the RNCS.
EC
Location: /dvs/dncs/mibs
MIB dependencies and compilation order:
1 SCIATL-COMMON-MIB
2 SA-DBDSPROD-MIB
3 SA-DBDSGEN-MIB
4 SA-CONAPPTC-MIB
5 Install these MIBs as needed in any order:
 SA-ALARM-MIB
 SA-CONAPPPERF-MIB
 SA-CONAPPSTATUSBFS-MIB
 SA-CONAPPSTATUSCOMMS-MIB
 SA-CONAPPSTATUSELEM-MIB
 SA-CONAPPSTATUSIPG-MIB
 SA-CONNAPPSTATUSPPV-MIB
 SA-CONAPPSTATUSSI-MIB
RNCS
Location: /dvs/dncs/mibs (on the EC)
1 SCIATL-COMMON-MIB
2 SA-DBDSPROD-MIB
3 SA-DBDSGEN-MIB
4 Install these MIBs as needed in any order:
 SA-CONAPP-MIB
 SA-CONAPPSTATUS-MIB
 SA-CONAPPSTATUSSAM-MIB
 SA-CONNAPPSTATUSTIME-MIB
6 OL-27572-02
MIB Location and Compilation
RepDB
Location: /opt/SAIrepdb/mibs
1 Cisco-RepDbFilesync-MIB.mib
2 Cisco-RepDbHdr-MIB.mib
Guest OS MIBs
Location (SUN-FM-MIB): /etc/sma/snmp/mibs
MIB dependencies and compilation order: The Guest OS MIBs can be installed
before or after the Base MIBs and Application MIBs are installed.
OL-27572-02 7
Chapter 1 MIBs
Object Descriptions
Objects are listed by OID (Object Identifier) in the system tree for each MIB on your
NMS. The documentation for each object is embedded in the MIB and the text will
display when you select the OID.
An understanding of the product is key to determining how to manage the objects.
Please read the relevant product guides before integrating objects into your NMS.
8 OL-27572-02
SNMP Access and Security
SNMP Access and Security

Introduction
For security purposes, the SNMP agent on network elements is configured by
default not to listen on external network interfaces. Additionally, no default SNMP
communities or SNMPv3 usernames are configured by default. The system
administrator must use the instructions within this guide to configure the SNMP
agent to listen on external interfaces and create SNMP communities or SNMPv3
users on each network element.
Cisco recommends using only SNMPv3 users and no SNMP communities to
maintain the highest level of security. SNMPv3 provides security via user
authentication and packet encryption. Authentication verifies the sender and packet
encryption prevents snooping. Together, these features ensure that messages have
not been tampered with.
Procedures to utilize SNMPv2c for queries and notifications are included in the
SNMP Access chapters for each network element if SNMPv3 is not supported or
desired on your SNMP management system.
Message Security
SNMPv3 provides message security with a SecurityName, AuthPassphrase and
PrivacyPassphrase. The AuthPassphrase provides authentication with a secret key
known only to the sender and receiver that is used to verify the SNMP message
source. The PrivacyPassphrase is used to encrypt the SNMP message contents.
OL-27572-02 9
2 Chapter 2
SNMP Access for the Network
Introduction
This chapter describes how to change the SNMP configuration on the
network to define trap destinations and enable queries.
To make these changes, you will need the following information.
Network Interface Network interface name used for SNMP queries.
Name Note: All network interfaces can be configured to
support SNMP.
SNMP port Default SNMP port is 161.
SecurityName The desired SNMPv3 username, authentication
AuthPassphrase passphrase and privacy passphrase.
PrivacyPassphrase Notes:
 The passphrases can be a common value.
 Passphrases must have at least 8 characters.
Community Name The desired SNMP community name.
Note: For security purposes, SNMP version 1 and 2c
are not recommended.
Trap Destination IP address of the SNMP Network Management System
to receive traps from the EC.
Trap Destination Port of the SNMP Network Management System to
Port receive traps from the network. Default SNMP trap
port is 162.
In This Chapter
 Define the Network SNMP Listening Interface ................................ 12
 Configure net-snmp to monitor dncsInitd ........................................ 14
 Create an SNMPv3 User ...................................................................... 17
 Create SNMP Communities for the Network ................................... 20
 Define SNMPv3 Trap Destination Configuration ............................ 22
OL-27572-02 11
Chapter 2 SNMP Access for the Network
Define the Network SNMP Listening Interface

Complete this procedure to define the network interface that the Network
Management System(s) will use to query network SNMP objects.
Notes:
 The SNMP listening interface can be one single network interface or all network
interfaces.
 Defining the SNMP listening interface is required only once after an initial
installation of the network software. The configuration will persist through
System Release upgrades.
Log on to the EC
1 Open an xterm window on the EC.
2 Complete the following steps to log on as the root user.
a Type su - and press Enter. The password prompt appears.
b Type the root password and press Enter.
Edit the SNMP Startup Script

1 Stop the network SNMP agent.
/etc/rc2.d/S98net-snmp stop
2 Open the net-snmp startup script with a text editor.
vi /etc/init.d/net-snmp
3 Remove "127.0.0.1:161" from the following line.
${SNMP_HOME}/sbin/snmpd -Lf /var/log/net-snmpd.log -p
${PID_FILE} 127.0.0.1:161
Example:
${PID_FILE}
4 Save and close the net-snmp file.
wq!
12 OL-27572-02
Define the Network SNMP Listening Interface
Define the Listening Address

Note: Skip this procedure to allow net-snmp to listen on port 161 of all network
interfaces.
1 Open the net-snmp configuration file with a text editor.
vi /dvs/tools/net-snmp/share/snmp/snmpd.conf
2 Add the following lines to the end of the file.
agentaddress localhost:<portnumber>
agentaddress <hostname>:<portnumber>
Note: Replace <hostname> with the hostname of the interface required for
SNMP queries.
Example Output:
agentaddress localhost:161
agentaddress dncseth:161
3 Save and close the net-snmp configuration file.
wq!
Restart Agent and Verify EC SNMP Operation

1 Start the network SNMP agent.
/etc/rc2.d/S98net-snmp start
2 Display the status of the net-snmp process to verify the master agent started
successfully.
ps -ef | grep net-snmp
Example Output:
root 14560 1 0 09:56:20 ? 0:02 /dvs/tools/net-
snmp/sbin/snmpd -Lf /var/log/net-snmpd.log -p /dvs/tools/net-snm
3 Display the process listening on the SNMP query port to verify the master agent
is listening on the correct interface.
lsof -i :161
Single Network Interface Example Output:
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
snmpd 15246 root 8u IPv4 0x30101ace280 0t0 UDP
localhost:snmpd
snmpd 14560 root 8u IPv4 0x60034814840 0t0 UDP dncseth:snmpd
Listen on All Interfaces Example Output:
snmpd 17456 root 8u IPv4 0x30108cc5d00 0t0 UDP *:snmpd
4 Type exit and press Enter to logout as the root user.
OL-27572-02 13
Configure net-snmp to Monitor dncsInitd

Complete this procedure to configure net-snmp to monitor dncsInitd.
Log on to the EC
Edit the prTable of UCDAVIS mib

Follow these instructions to add an entry to the prTable of UCDAVIS mib so that it
can be monitored.
1 Add the following directive to the /dvs/tools/net-
snmp/share/snmp/snmpd.conf file, which allows you to monitor dncsInitd.
proc dncsInitd
2 Type the following command and press Enter to stop the net-snmp master agent.
3 Type the following command and press Enter to start the net-snmp master agent.
4 Type the following command to query the prTable table.
Note: If the password contains any spaces, place the password in double-quotes
in the command. For example, if your password is I Can Read, you would
replace <password> with “I Can Read,”
/<snmp user> -v 3 -u snmpUser -l authNoPriv -a MD5 -A
<password> -M /dvs/tools/net-snmp/share/snmp/mibs -Ci
localhost UCD-SNMP-MIB::prTable
Note: If the password contains any spaces, place the password in double-quotes.
For example, if your password is I Can Read, you would replace <password>
with “I Can Read” in the command example shown below.
Expected Result: The following entry should appear in the prTable:
SNMP table: UCD-SNMP-MIB::prTable
index prIndex prNames prMin prMax prCount prErrorFlag prErrMessage
prErrFix prErrFixCmd
1 1 dncsInitd 0 0 1 noError noError
14 OL-27572-02
Configure net-snmp to Monitor dncsInitd
Monitor the dncsInitd Process

Follow these instructions to monitor the dncsInitd process using the monitor
directive. For additional information on monitoring processes go to this URL:
http://net-snmp.sourceforge.net/docs/man/snmpd.examples.html#lbAP.
1 Add the following directive to the /dvs/tools/net-
snmp/share/snmp/snmpd.conf file to generate a trap when the prErrorFlag
(.1.3.6.1.4.1.2021.2.1.100) for the above instance changes (when it is equal to 0 and
not equal to 0) .
Notes:
 The argument -o allows you to specify the other objects to be part of this
varbind.
 The argument –r5 allows you to specify that the entry is checked every 5
seconds.
When not equal to 0:
monitor -r 5 -u <snmp user> -i -o .1.3.6.1.4.1.2021.2.1.2.1 -o
.1.3.6.1.4.1.2021.2.1.101.1 "dncsInitd has stopped." -o
.1.3.6.1.4.1.2021.2.1.100.1 .1.3.6.1.4.1.2021.2.1.100.1 != 0
/dvs/tools/net-snmp/share/snmpd.conf
When equal to 0:
monitor -r 5 -u <snmp user> -i -o .1.3.6.1.4.1.2021.2.1.2.1 -o
.1.3.6.1.4.1.2021.2.1.101.1 "dncsInitd is up." -o
.1.3.6.1.4.1.2021.2.1.100.1 .1.3.6.1.4.1.2021.2.1.100.1 == 0
/dvs/tools/net-snmp/share/snmpd.conf
Expected Result: Where a trap destination is provided, traps are generated. In
this instance, when the dncsInitd process is stopped, the following trap is
generated:
Trap received from 10.90.176.205/59650, Trap = DISMAN-EVENT-
MIB::mteTriggerFired
Trap Info:
DISMAN-EVENT-MIB::mteHotTrigger.0 => dncsInitd has stopped.
DISMAN-EVENT-MIB::mteHotTargetName.0 =>
DISMAN-EVENT-MIB::mteHotContextName.0 =>
DISMAN-EVENT-MIB::mteHotOID.0 => 1.3.6.1.4.1.2021.2.1.100.1
DISMAN-EVENT-MIB::mteHotValue.0 => 1
UCD-SNMP-MIB::prNames.1 => dncsInitd
UCD-SNMP-MIB::prErrMessage.1 => No dncsInitd process running.
UCD-SNMP-MIB::prErrorFlag.1 => 1
OL-27572-02 15
When the dncsInitd process is started, the following trap is generated:

Trap received from 10.90.176.205/59650, Trap = DISMAN-EVENT-
MIB::mteTriggerFired
Trap Info:
DISMAN-EVENT-MIB::mteHotTrigger.0 => dncsInitd is up.
DISMAN-EVENT-MIB::mteHotTargetName.0 =>
DISMAN-EVENT-MIB::mteHotContextName.0 =>
DISMAN-EVENT-MIB::mteHotOID.0 => 1.3.6.1.4.1.2021.2.1.100.1
DISMAN-EVENT-MIB::mteHotValue.0 => 0
UCD-SNMP-MIB::prNames.1 => dncsInitd
UCD-SNMP-MIB::prErrMessage.1 =>
UCD-SNMP-MIB::prErrorFlag.1 => 0
16 OL-27572-02
Create an SNMPv3 User

Complete this procedure to create an SNMPv3 user on the EC. Network
Management Systems can use the SNMPv3 user to query EC SNMP objects. The
SNMPv3 user can also be used for sending SNMPv3 traps to Network Management
Systems. The same user or unique users can be used for the two SNMP functions.
Log on to the EC
Create the SNMPv3 User

Note: Refer to this URL for SNMPv3 username and passphrase constraints:
http://net-snmp.sourceforge.net/docs/man/snmpd.conf.html.
1 Stop the network SNMP agents.
2 Execute the create SNMPv3 user script.
/dvs/tools/net-snmp/bin/net-snmp-create-v3-user -A
"<authPass>" -X "<privPass>" -a <authProt> -x <privProt>
<username>
Notes:
 This is a single command.
 Replace <username> with the SNMPv3 username.
 Replace <authPass> with the authentication passphrase.
 Replace <privPass> with the privacy passphrase.
 Replace <authProt> with the authentication protocol: MD5 or SHA
 Replace <privProt> with the encryption (privacy) protocol: DES or AES
 For more details on SNMPv3 user creation, go to this URL: http://net-
snmp.sourceforge.net/docs/FAQ.html
Result: The new user information is added to the two SNMP agent
configuration files.
3 Make note of the username and associated passphrases. The passphrases cannot
be recovered after creating the user.
4 Did you use a privacy passphrase that is different from the authentication
passphrase and did the privacy passphrase include spaces?
 If no, skip to the next procedure.
 If yes, continue with the next step.
OL-27572-02 17
5 Open the /var/net-snmp/snmpd.conf file with a text editor.

vi /var/net-snmp/snmpd.conf
6 At the end of the file, place quotation marks around privacy passphrase.
Note: The privacy passphrase appears after “DES” or “AES”.
Example:
createUser v3SnmpUser MD5 "Auth Passphrase" DES “Priv
Passphrase”
7 Save and close the snmpd.conf file.
wq!
Change SNMPv3 User Options

Complete the following steps to enforce the use of both authentication and
encryption for SNMPv3 queries and change the write privileges for the newly
created user. Both of these changes are optional but recommended for security
purposes.
Note: Cisco recommends enforcing the use of both authentication and encryption for
the SNMPv3 user.
1 Open the master agent configuration file.
2 At the end of the file, add "authPriv" after the new username entry to enforce the
use of both authentication and encryption.
Example:
rwuser v3SnmpUser authPriv
3 At the end of the file, change "rwuser" to "rouser" before the new username entry
to allow read-only SNMP operations.
Example:
rouser v3SnmpUser authPriv
wq!
Restart the SNMP Agent and Verify Operation

successfully.
Example Output:
18 OL-27572-02
3 Query the sysName object to verify the new SNMPv3 user is functional.
snmpwalk -v3 -u <username> -l authPriv -a <authProt> -A
"<authPass>" -x <privProt> -X "<privPass>" -M
/etc/sma/snmp/mibs/ localhost sysName
Notes:
 Replace <username> with the new SNMPv3 username.
Example:
snmpwalk -v3 -u v3SnmpUser -l authPriv -a MD5 -A "Auth
Passphrase" -x DES -X "Priv Passphrase" -M /etc/sma/snmp/mibs/
localhost sysName
Result:
SNMPv2-MIB::sysName.0 = STRING: dncs
4 Type exit and press Enter to log out as the root user.
OL-27572-02 19
Create SNMP Communities for the Network

SNMP communities can be created on the network to allow SNMPv1 and v2c access
to EC MIB objects.
Note: For security purposes, Cisco does not recommend creating SNMP
communities on the system.
Log on to the EC
Edit the Net-SNMP snmpd.conf File

1 Type the following command and press Enter to stop the Net-SNMP process.
2 Using a text editor, open the /dvs/tools/net-snmp/share/snmp/snmpd.conf
file.
3 Replace public with the desired SNMPv2c read only community name in the
following line: rocommunity public
4 Uncomment the line, if necessary, by deleting the pound sign at the beginning of
the line.
5 Save and close the file.
20 OL-27572-02
Create SNMP Communities for the Network

1 Type the following command and press Enter to start the Net-SNMP process.
2 Type the following command and press Enter to verify that the Net-SNMP
process has started.
Example Output:
root 14452 1 0 Jan 07 ? 8:28
/dvs/tools/net-snmp/sbin/snmpd -Lf /var/log/net-snmpd.log -p
/dvs/tools/net-snm
3 Query the sysName object to verify the new SNMP community is functional.
snmpwalk -v2c -c <commName> -M /etc/sma/snmp/mibs/ localhost
sysName
Notes: Replace <commName> with the new SNMP community name.
Example:
snmpwalk -v2c -c public -M /etc/sma/snmp/mibs/ localhost
sysName
Result:
OL-27572-02 21
Define SNMPv3 Trap Destination Configuration

Trap destinations can be defined using SNMPv3 or SNMPv2c.
The EC may forward SNMP traps to your network management system (NMS) or
any other component running an SNMP trap listening process. This section describes
procedures to configure the trap destination IP address(es) on the EC in order for the
traps to be sent to these destinations. This section does not include procedures for
traps generated by the server hardware or the virtual machine in which the EC
application is running.
Before You Begin

Ensure that the EC is configured with an IP route to the trap destination(s) covered
in this section, regardless of the SNMP version used.
SNMPv3 Traps Destination Configuration

Execute the following commands to define SNMPv3 trap destination(s).
Note: An SNMPv3 user must exist on the EC prior to creating an SNMPv3 trap
destination. See Create the SNMPv3 User for instructions.
Log on to the EC
Define the SNMPv3 Trap Destination

1 Stop the network SNMP agent.
3 At the end of the file, add the following line.
trapsess -v3 -u <username> -l authPriv -a <authProt> -x
<privProt> <trapDestIP>:<trapDestPort>
Notes:
 Replace <trapDestIP> with the IP address of the SNMP trap receiver.
 Replace <trapDestPort> with the port number of the SNMP trap receiver.
This is typically 162.
 The -l option can be set to noAuthNoPriv, authNoPriv, or authPriv; however,
authPriv is the recommended setting.
22 OL-27572-02
Define SNMPv3 Trap Destination Configuration
 Replace <authProt> with the authentication protocol defined for the

SNMPv3 user: MD5 or SHA.
 Replace <privProt> with the encryption (privacy) protocol defined for the
SNMPv3 user: DES or AES.
 For more details on SNMPv3 trap destination, go to this URL: http://net-
snmp.sourceforge.net/docs/man/snmpd.conf.html.
Example:
trapsess -v3 -u v3SnmpUser -l authPriv -a MD5 -x DES
172.16.0.1:162
4 To configure additional trap destinations, repeat this procedure from step 3.
wq!
Restart Network SNMP Agent

successfully.
Example Output:
3 Type exit and press Enter to logout of the root user.
Note: Ensure that NMS is configured to accept the above credentials.
SNMPv2 Traps for the Network

Execute the following commands to define SNMPv2c trap destination(s).

1 Log on to the EC as the root user.
3 Using a text editor, open the snmpd.conf file.
4 Add the following line to the end of the file:
trapsess -v 2c -c <communityName>
<snmp_trap_listener_host:port>
 Replace <communityName> with the desired SNMP read only community
name.
 Replace <snmp_trap_listener_host:port> with the IP address and port of the
SNMP trap listener (e.g., 192.168.0.1:162).
OL-27572-02 23
5 To configure additional trap destinations, repeat this procedure from step 4.

Restart the Net-SNMP Process

/etc/init.d/net-snmp start
2 Type the following command and press Enter to verify the Net-SNMP processes
started.
Example Output:
root 14452 1 0 Jan 07 ? 8:28 /dvs/tools/net-
24 OL-27572-02
3 Chapter 3
Filters in Net-SNMP
Introduction
Use the information in this chapter to configure filters in Net-SNMP.
In This Chapter
 SNMP Trap Filters in Net-SNMP ....................................................... 26
 How to Configure SNMP Trap Filters in Net-SNMP ...................... 27
 Configuring SNMP Trap Filters in Net-SNMP for RepDB and
other EC Traps....................................................................................... 29
OL-27572-02 25
Chapter 3 Filters in Net-SNMP
SNMP Trap Filters in Net-SNMP

This feature facilitates the configuring of distinct trap destinations for different traps.
For example, we could have one trap destination for all the traps generated by the
nbiAgent process and a second trap destination for all the traps generated by the
dncsSnmpAgent process.
This feature is valuable when the EC is regionalized. We do not want some of the
monitoring traps to be dependent upon any of the EC processes, such as traps
generated by RepDB Monitoring agents (Hdr and FileSync). Therefore, these traps
need a different trap destination.
We can create one profile for delivering all the traps generated by the
dncsSnmpAgent and nbiAgent to localhost, so that the snmpTrapHandler process
can process them further before they publish those traps as XMPP messages to the
management node.
We can create another profile for delivering all the traps generated by RepDB
monitoring agents to deliver those traps directly to the management node.
26 OL-27572-02
How to Configure SNMP Trap Filters in Net-SNMP
How to Configure SNMP Trap Filters in Net-SNMP

1 Be certain that a trapsess entry, which provides the trap destination, exists in the
/dvs/tools/net-snmp/share/snmp/snmpd.conf file.
Example: trapsess -v 2c -c cisco1 localhost:162
Notes:
 Upon startup, the master agents populate some of the standard SNMP tables.
Examples:
– snmpwalk -m ALL -M /dvs/tools/net-snmp/share/snmp/mibs
-v 2c -c ciscopriv localhost snmpTargetAddrTable
Sample output:
SNMP-TARGET-MIB::snmpTargetAddrTDomain.'internal0' = OID: SNMPv2-
TM::snmpUDPDomain
SNMP-TARGET-MIB::snmpTargetAddrTAddress.'internal0' = Hex-STRING:
7F 00 00 01 00 A2
SNMP-TARGET-MIB::snmpTargetAddrTimeout.'internal0' = INTEGER: 1000
SNMP-TARGET-MIB::snmpTargetAddrRetryCount.'internal0' = INTEGER: 5
SNMP-TARGET-MIB::snmpTargetAddrTagList.'internal0' = STRING:
internal0
SNMP-TARGET-MIB::snmpTargetAddrParams.'internal0' = STRING:
internal0
SNMP-TARGET-MIB::snmpTargetAddrStorageType.'internal0' = INTEGER:
readOnly(5)
SNMP-TARGET-MIB::snmpTargetAddrRowStatus.'internal0' = INTEGER:
active(1)
-v 2c -c ciscopriv localhost snmpNotifyTable
Sample output:
SNMP table: SNMP-NOTIFICATION-MIB::snmpNotifyTable
index snmpNotifyTag snmpNotifyType snmpNotifyStorageType

snmpNotifyRowStatus
'internal0' internal0 trap readOnly active
-v 2c -c ciscopriv localhost snmpTargetParamsTable
Sample output:
SNMP table: SNMP-TARGET-MIB::snmpTargetParamsTable
index snmpTargetParamsMPModel snmpTargetParamsSecurityModel

snmpTargetParamsSecurityName snmpTargetParamsSecurityLevel
snmpTargetParamsStorageType snmpTargetParamsRowStatus
'internal0' 1 2
cisco1 noAuthNoPriv readOnly
active
OL-27572-02 27
2 Populate the two tables (snmpNotifyFilterProfileTable and

snmpNotifyFilterTable) using the snmpset command.
a snmpNotifyFilterProfileTable - one record
Example:
snmpset -v2c -c cisco -m ALL -M /dvs/tools/net-
snmp/share/snmp/mibs localhost
\snmpNotifyFilterProfileName.\'internal0\' s ExpController
\ snmpNotifyFilterProfileRowStatus.\'internal0\' i
createAndGo
Result: This command creates one profile for the EC.
b snmpNotifyFilterTable - two records
Notes:
– This example is to portray that all traps from nbiAgent be included in the
traps generated by the net-snmp master agent and all the traps from
dncsSnmpAgent be excluded in the traps generated by net-snmp master
agent.
– Command 1, which follows, includes traps from nbiAgent: (trap oid of
nbiAgent is: 1.3.6.1.4.1.1429.9.1.18.3.0.2)
– Command 2, which follows command 1, excludes traps from
dncsSnmpAgent: (trap oid of dncsSnmpAgent is:
1.3.6.1.4.1.1429.5.1.45.1.1.6.0.2)
Examples:
– snmpset -v2c -c cisco -m ALL -M /dvs/tools/net-
snmp/share/snmp/mibs localhost \
snmpNotifyFilterRowStatus.\"ExpController\".1.3.6.1.4.1.1429.9.1.18.3.0.2
i createAndGo \
snmpNotifyFilterType.\"ExpController\".1.3.6.1.4.1.1429.9.1.18.3.0.2 i
included
– snmpset -v2c -c cisco -m ALL -M /dvs/tools/net-
snmpNotifyFilterRowStatus.\"ExpController\".1.3.6.1.4.1.1429.5.1.45.1.1.6.0.2
i createAndGo \
snmpNotifyFilterType.\"ExpController\".1.3.6.1.4.1.1429.5.1.45.1.1.6.0.2 i
excluded
Result: dncsSnmpAgent generated traps are not sent to localhost. However,
nbiAgent generated traps are sent to localhost.
28 OL-27572-02
Configuring SNMP Trap Filters in Net-SNMP for RepDB and other EC Traps
Configuring SNMP Trap Filters in Net-SNMP for

RepDB and other EC Traps
In this procedure, we will configure SNMP trap filters so that only RepDB (Hdr and
FileSync) traps go to the CMC (Active CMC) and only nbiAgent and
dncsSnmpAgent traps go to localhost (so that snmpTrapHandler processes them).
1 Edit the /dvs/tools/net-snmp/share/snmp/snmpd.conf file to add a trapsess
entry with v2c with the destination of the active CMC's IP address.
## add the CMC IP as one of the trap destination
trapsess -v 2c -c public <IP of Active CMC>:162
2 Add a community to help you configure and query various aspects.
rwcommunity cisco
3 Bounce net snmp master agent.
a /etc/rc2.d/S98net-snmp stop
b /etc/rc2.d/S98net-snmp start#
Result: Upon startup, the master agents populate some of the standard SNMP
tables.
4 Query the tables for examples.
 snmpwalk -m ALL -M /dvs/tools/net-snmp/share/snmp/mibs -v
2c -c cisco localhost snmpTargetAddrTable
Sample output:
TM::snmpUDPDomain
TM::snmpUDPDomain
SNMP-TARGET-MIB::snmpTargetAddrTAddress.'internal0' = Hex-STRING: 7F
00 00 01 00 A2
SNMP-TARGET-MIB::snmpTargetAddrTAddress.'internal1' = Hex-STRING: 0A
5A B1 2C 00 A2
internal0
internal1
SNMP-TARGET-MIB::snmpTargetAddrParams.'internal0' = STRING: internal0
SNMP-TARGET-MIB::snmpTargetAddrParams.'internal1' = STRING: internal1
readOnly(5)
readOnly(5)
active(1)
OL-27572-02 29
active(1)The keywords are ‘internal0’ and 'internal1' in the
snmpNotifyTag in the snmpNotifyTable.
 snmpwalk -m ALL -M /dvs/tools/net-snmp/share/snmp/mibs -
v 2c -c cisco localhost snmpNotifyTable
Sample output:
index snmpNotifyTag snmpNotifyType snmpNotifyStorageType
snmpNotifyRowStatus
'internal0' internal0 trap readOnly
active
'internal1' internal1 trap readOnly
active
 snmpwalk -m ALL -M /dvs/tools/net-snmp/share/snmp/mibs -v
2c -c cisco localhost snmpTargetParamsTable
Sample output:
index snmpTargetParamsMPModel snmpTargetParamsSecurityModel
snmpTargetParamsSecurityName snmpTargetParamsSecurityLevel
snmpTargetParamsStorageType snmpTargetParamsRowStatus
'internal0' 1 2
ciscointernalcomm noAuthNoPriv
readOnly active
'internal1' 1 2
public noAuthNoPriv readOnly
active
5 Create the profile ExpController - Include dncsSnmpAgent and nbiAgent
generated SNMP traps and exclude RepDB generated SNMP traps.
a Create the profile ExpController:
> snmpNotifyFilterProfileName.\'internal0\' s
ExpController \
> snmpNotifyFilterProfileRowStatus.\'internal0\' i
createAndGo
SNMP-NOTIFICATION-
MIB::snmpNotifyFilterProfileName.'internal0' = STRING:
ExpController
SNMP-NOTIFICATION-
MIB::snmpNotifyFilterProfileRowStatus.'internal0' =
INTEGER: createAndGo(4)
b Create the profile RepDB:
snmpNotifyFilterProfileName.\'internal1\' s RepDb
snmpNotifyFilterProfileRowStatus.\'internal1\' i
createAndGo
SNMP-NOTIFICATION-
MIB::snmpNotifyFilterProfileName.'internal1' = STRING:
RepDb
SNMP-NOTIFICATION-
MIB::snmpNotifyFilterProfileRowStatus.'internal1' =
INTEGER: createAndGo(4)
30 OL-27572-02
c Include nbiAgent traps in profile ExpController.

>
snmpNotifyFilterRowStatus.\"ExpController\".1.3.6.1.4.1.142
9.9.1.18.3.0.2 i createAndGo \
>
snmpNotifyFilterType.\"ExpController\".1.3.6.1.4.1.1429.9.1
.18.3.0.2 i included
SNMP-NOTIFICATION-
MIB::snmpNotifyFilterRowStatus."ExpController".1.3.6.1.4.1.
1429.9.1.18.3.0.2 = INTEGER: createAndGo(4)
SNMP-NOTIFICATION-
MIB::snmpNotifyFilterType."ExpController".1.3.6.1.4.1.1429.
9.1.18.3.0.2 = INTEGER: included(1)
d Include dncsSnmpAgent traps in profile ExpController.
>
9.5.1.45.1.1.6.0.2 i createAndGo \
>
.45.1.1.6.0.2 i included
SNMP-NOTIFICATION-
1429.5.1.45.1.1.6.0.2 = INTEGER: createAndGo(4)
SNMP-NOTIFICATION-
5.1.45.1.1.6.0.2 = INTEGER: included(1)
e Exclude HDR (RepDB) traps in profile ExpController:
9.5.1.24.2.0.1 i createAndGo
.24.2.0.1 i excluded
SNMP-NOTIFICATION-
1429.5.1.24.2.0.1 = INTEGER: createAndGo(4)
SNMP-NOTIFICATION-
5.1.24.2.0.1 = INTEGER: excluded(2)
OL-27572-02 31
f Exclude FileSync (RepDB) traps in profile ExpController:

snmpNotifyFilterRowStatus.\"RepDb\".1.3.6.1.4.1.1429.5.1.25
.2.0.1 i createAndGo
snmpNotifyFilterType.\"RepDb\".1.3.6.1.4.1.1429.5.1.25.2.0.
1 i included
SNMP-NOTIFICATION-
MIB::snmpNotifyFilterRowStatus."RepDb".1.3.6.1.4.1.1429.5.1
.25.2.0.1 = INTEGER: createAndGo(4)
SNMP-NOTIFICATION-
MIB::snmpNotifyFilterType."RepDb".1.3.6.1.4.1.1429.5.1.25.2
.0.1 = INTEGER: included(1)
g Include RepDB HDR traps in profile RepDb:
1 i included
SNMP-NOTIFICATION-
SNMP-NOTIFICATION-
.0.1 = INTEGER: included(1)
h Exclude dncsSnmpAgent traps in profile RepDb:
.1.1.6.0.2 i createAndGo
6.0.2 i excluded
SNMP-NOTIFICATION-
.45.1.1.6.0.2 = INTEGER: createAndGo(4)
SNMP-NOTIFICATION-
.1.6.0.2 = INTEGER: excluded(2)
32 OL-27572-02
i Exclude nbiAgent traps in profile RepDb:

2 i excluded
SNMP-NOTIFICATION-
SNMP-NOTIFICATION-
.0.2 = INTEGER: excluded(2)
6 Remove the rwcommunity that was added (cisco) in Step 2 by deleting that entry
from the /dvs/tools/net-snmp/share/snmp/snmpd.conf file.
7 Bounce net snmp master agent.
a /etc/rc2.d/S98net-snmp stop
b /etc/rc2.d/S98net-snmp start
OL-27572-02 33
4 Chapter 4
SNMP Access for the RNCS
Introduction
This chapter describes how to change the SNMP configuration file on
the RNCS to define trap destinations and enable queries.
To make these changes, you will need the following information.
Network Interface RNCS network interface name used for SNMP queries.
Name Note: All network interfaces on the RNCS can be
configured to support SNMP.
SNMP port Default SNMP port is 161.
SecurityName The desired SNMPv3 username, authentication
AuthPassphrase passphrase and privacy passphrase.
PrivacyPassphrase Notes:
 The passphrases can be a common value.
 Passphrases must have at least 8 characters.
Community Name The desired SNMP community name.
Note: For security purposes, SNMP version 1 and 2c
are not recommended.
Trap Destination IP address of the SNMP Network Management System
to receive traps from the RNCS.
Trap Destination Port of the SNMP Network Management System to
Port receive traps from the RNCS. Default SNMP trap port
is 162.
In This Chapter
 Define the RNCS SNMP Listening Interface..................................... 36
 Create an SNMPv3 User ...................................................................... 38
 SNMP Communities for the RNCS .................................................... 41
 SNMP Traps for the RNCS .................................................................. 43
OL-27572-02 35
Chapter 4 SNMP Access for the RNCS
Define the RNCS SNMP Listening Interface

Complete this procedure to define the network interface on the RNCS that the
Network Management System(s) will use to query RNCS SNMP objects.
Notes:
 The SNMP listening interface can be one single network interface or all network
interfaces on the RNCS.
 Defining the SNMP listening interface on the RNCS is required only once after
an initial installation of the RNCS software. The configuration will persist
through System Release upgrades.
Log on to the RNCS

1 Open an xterm window on the RNCS.
Edit the SNMP Startup Script

1 Stop the RNCS SNMP agent.
2 Open the net-snmp startup script with a text editor.
vi /etc/init.d/net-snmp
3 Remove “127.0.0.1:161” from the following line.
${PID_FILE} 127.0.0.1:161
4 Save and close the net-snmp file.
wq!
Define the Listening Address

Important: Skip this procedure to allow net-snmp to listen on port 161 of all network
interfaces.
1 Open the net-snmp configuration file with a text editor.
2 Add the following lines to the end of the file.
agentaddress <hostname>:161
Note: Replace <hostname> with the hostname of the interface required for
SNMP queries.
Example Output:
agentaddress lionn:161
36 OL-27572-02
Define the RNCS SNMP Listening Interface
3 Save and close the net-snmp configuration file.

wq!
Restart the RNCS SNMP Agent and Verify Operation

1 Start the RNCS SNMP agent.
successfully.
Example Output:
3 Display the process listening on the SNMP query port to verify the master agent
is listening on the correct interface.
lsof -i :161
Single Network Interface Example Output:
snmpd 15246 root 8u IPv4 0x30101ace280 0t0 UDP
localhost:snmpd
snmpd 14560 root 8u IPv4 0x60034814840 0t0 UDP lionn:snmpd
Listen on All Interfaces Example Output:
snmpd 17456 root 8u IPv4 0x30108cc5d00 0t0 UDP *:snmpd
OL-27572-02 37

Complete this procedure to create an SNMPv3 user on the RNCS. Network
Management Systems can use the SNMPv3 user to query RNCS SNMP objects. The
SNMPv3 user can also be used for sending SNMPv3 traps to Network Management
Systems. The same user or unique users can be used for the two SNMP functions.
Log on to the RNCS

Create the SNMPv3 User

Refer to the SNMP RFCs in the following URL for SNMPv3 username and
passphrase constraints: http://net-
snmp.sourceforge.net/docs/man/snmpd.conf.html.
2 Execute the create SNMPv3 user script.
/dvs/tools/net-snmp/bin/net-snmp-create-v3-user -A
"<authPass>" -X "<privPass>" -a <authProt> -x <privProt>
<username>
Notes:
 This is a single command.
Result: The new user information is added to the two SNMP agent
configuration files.
3 Make note of the username and associated passphrases. The passphrases cannot
be recovered after creating the user.
4 Did you use a privacy passphrase that is different from the authentication
passphrase and did the privacy passphrase include spaces?
 If no, skip to the next procedure.
 If yes, continue with the next step.
5 Open the /var/net-snmp/snmpd.conf file with a text editor.
vi /var/net-snmp/snmpd.conf
38 OL-27572-02
6 At the end of the file, place quotation marks around privacy passphrase.
Note: The privacy passphrase appears after “DES” or “AES”.
Example:
createUser v3SnmpUser MD5 "Auth Passphrase" DES “Priv
Passphrase”
wq!
Change SNMPv3 User Options

Complete the following steps to enforce the use of both authentication and
encryption for SNMPv3 queries and change the write privileges for the newly
created user. Both of these changes are optional but recommended for security
purposes.
Important: An SNMP credential with write privileges is required to complete the
procedure Configure the Download Server SNMP Agent. If the SNMPv3 user you
are creating will be used for this procedure, then leave the write privilege enabled.
We recommend disabling the write privilege after completing the procedure
Configure the Download Server SNMP Agent.
Note: Cisco recommends enforcing the use of both authentication and encryption for
the SNMPv3 user.
vi /usr/share/snmp/snmpd.conf
2 At the end of the file, add "authPriv" after the new username entry to enforce the
use of both authentication and encryption.
Example:
rwuser v3SnmpUser authPriv
3 At the end of the file, change "rwuser" to "rouser" before the new username entry
to allow read-only SNMP operations.
Example:
rouser v3SnmpUser authPriv
wq!
Restart the RNCS SNMP Agent and Verify Operation

successfully.
Example Output:
OL-27572-02 39
3 Query the sysName object to verify the new SNMPv3 user is functional.
snmpwalk -v3 -u <username> -l authPriv -a <authProt> -A
"<authPass>" -x <privProt> -X "<privPass>" -M
/etc/sma/snmp/mibs/ localhost sysName
Notes:
 Replace <username> with the new SNMPv3 username.
Example:
snmpwalk -v3 -u v3SnmpUser -l authPriv -a MD5 -A "Auth
Passphrase" -x DES -X "Priv Passphrase" -M /etc/sma/snmp/mibs/
localhost sysName
Result:
4 Type exit and press Enter to log out the root user.
40 OL-27572-02
SNMP Communities for the RNCS
SNMP Communities for the RNCS

SNMP communities can be created on the RNCS to allow SNMPv1 and v2c access to
RNCS MIB objects.
Note: For security purposes, Cisco does not recommend creating SNMP
communities on the system.
Log on to the RNCS


2 Using a text editor, open the /dvs/tools/net-snmp/share/snmp/snmpd.conf
file.
3 Replace public with the desired SNMPv2c read only community name in the
following line: rocommunity public
4 Uncomment the line, if necessary, by deleting the pound sign at the beginning of
the line.

2 Type the following command and press Enter to verify that the Net-SNMP
process has started.
Example Output:
root 14452 1 0 Jan 07 ? 8:28
/dvs/tools/net-snmp/sbin/snmpd -Lf /var/log/net-snmpd.log -p
/dvs/tools/net-snm
OL-27572-02 41
3 Query the sysName object to verify the new SNMP community is functional.
snmpwalk -v2c -c <commName> -M /etc/sma/snmp/mibs/ localhost
sysName
Notes: Replace <commName> with the new SNMP community name.
Example:
snmpwalk -v2c -c public -M /etc/sma/snmp/mibs/ localhost
sysName
Result:
42 OL-27572-02
SNMP Traps for the RNCS
SNMP Traps for the RNCS

This section describes how to define SNMPv3 trap destinations on the RNCS.
SNMPv3 Traps for the RNCS

Execute the following commands to define SNMPv3 trap destinations on the RNCS.
Note: An SNMPv3 user must exist on the RNCS prior to creating an SNMPv3 trap
destination. See Create the SNMPv3 User for instructions.
Log on to the RNCS

Define the SNMPv3 Trap Destination

3 At the end of the file, add the following line.
trapsess -v3 -u <username> -l authPriv -a <authProt> -x
<privProt> <trapDestIP>:<trapDestPort>
Notes:
 Replace <trapDestIP> with the IP address of the SNMP trap receiver.
 Replace <trapDestPort> with the port number of the SNMP trap receiver.
This is typically 162.
 The -l option can be set to noAuthNoPriv, authNoPriv, or authPriv; however,
authPriv is the recommended setting.
 Replace <authProt> with the authentication protocol defined for the
SNMPv3 user: MD5 or SHA.
 Replace <privProt> with the encryption (privacy) protocol defined for the
SNMPv3 user: DES or AES.
Example:
trapsess -v3 -u v3SnmpUser -l authPriv -a MD5 -x DES
172.16.0.1:162
wq!
OL-27572-02 43
Restart the RNCS SNMP Agent

successfully.
Example Output:
SNMPv2c Traps for the RNCS

Execute the following commands to define SNMPv2c trap destination(s).

1 Log on to the RNCS as the root user.
3 Using a text editor, open the snmpd.conf file.
4 Add the following line to the end of the file:
trapsess -v 2c -c <communityName>
<snmp_trap_listener_host:port>
 Replace <communityName> with the desired SNMP read only community
name.
 Replace <snmp_trap_listener_host:port> with the IP address and port of the
SNMP trap listener (e.g., 192.168.0.1:162).
Restart the Net-SNMP Process

/etc/init.d/net-snmp start
2 Type the following command and press Enter to verify the Net-SNMP processes
started.
Example Output:
root 14452 1 0 Jan 07 ? 8:28 /dvs/tools/net-
44 OL-27572-02
5 Chapter 5
nbiAgent Configuration
Introduction
The EC nbiAgent periodically refreshes its cached data from the
source. In most cases, the source is the EC database. But the source of
the data can be a result of the nbiAgent polling a network element via
ping or rpc to refresh its cache about the communication status
(pingable or not pingable) of the network element. In both cases, this
refresh interval is configurable. These are defined in the file
~dncs/.saConfApp.conf on the EC. For example,
saConAppStatusCommsTable refreshInterval, is defined in the
saConApp.conf file on the EC and set to six hours by default. The
minimum supported refresh interval is one minute.
For most cases, the default refresh intervals assigned to each MIB will
typically suffice. If the operator chooses to change the interval, refer to
the procedure in this chapter.
In This Chapter
 Changing the NBI SNMP Object Cache Refresh Interval ............... 46
OL-27572-02 45
Chapter 5 nbiAgent Configuration
Changing the NBI SNMP Object Cache Refresh

Interval
Complete the following steps to change the NBI SNMP Object Cache Refresh
Interval.
1 Log on to the EC as the dncs role.
a Open an xterm window on the EC as a DNCS Administrator or root.
b Type su - dncs and press Enter to switch to the dncs role.
c Enter the dncs role password when prompted.
2 Open the /export/home/dncs/.snmp/saConApp.conf file with a text editor.
3 Search for the MIB table whose interval you are interested in updating. An
example is saConAppConTable_refresInterval as shown in the below sample
default configuration file.
4 Update the interval for the selected table in step 3 to the desired communications
test interval (in seconds).
Important:
 The interval range is 60 seconds to 12 hours. Recommended intervals for each
MIB table are different and are provided in ~dncs/.saConfApp.conf.
Therefore, before making any changes to this file, maintain a copy of the
default configuration file for future reference in case you want to return to
the defaults.
 We recommend that you conduct testing on a non-production system before
reducing an interval, especially if the differences from the defaults are large.
Sample default configuration file:
# 1 minute = 60
# 30 minutes = 60 * 30 = 1800
# 1 Hour = 60 * 60 = 3600
# 2 Hour = 2 * 60 * 60 = 7200
# 6 Hours = 60 * 60 * 6 = 21600
# 12 Hours = 60 * 60 * 12 = 43200
# Following are the thresholds for
saConAppStatusTimeDstHubTable
# Avoid short intervals to avoid load on the system
# If values less than 60 seconds are given, it will consider
60 seconds
saCasPpvEutUpdatedIntervalThreshold 3600
saConAppSizeMaxRows 100
# Following are the refresh Intervals for tables in the MIB

saConApp
saConAppConTable_refreshInterval 21600.0
46 OL-27572-02
Changing the NBI SNMP Object Cache Refresh Interval
saConAppEdgeHubTable_refreshInterval 21600.0
# Following are the refresh Intervals for tables in the MIB

saConAppStatusTime
saConAppStatusTimeDstHubCountTable_refreshInterval 21600.0
----
The naming convention followed is mibtable name followed by
"_refreshInterval"
Followed by the variable name is the space then the refresh
interval.
5 Type dncsControl -stop nbiAgent and press Enter to stop the nbiAgent process.
The system returns the following once the process has stopped.
new state = stopped(1)
6 Type dncsControl -start nbiAgent and press Enter to start the nbiAgent process.
The system returns the following once the process has started.
new state = running(2)
7 Type exit and press Enter to log out of the dncs role.
OL-27572-02 47
6 Chapter 6
EC and RNCS Infrastructure
SNMP References
Introduction
Cisco Unified Computing System (UCS) servers, which host the EC
and RNCS virtual machines, use Cisco Integrated Management
Controller (CIMC) that operates independently from the operating
system. CIMC provides a dedicated, out-of-band management channel
that allows a system administrator to monitor and manage servers
remotely, even when they are powered down. Additionally, CIMC
includes support for SNMP queries and traps for hardware-related
objects.
VMware vSphere ESXi is the hypervisor that runs on physical
hardware and provides necessary virtualization infrastructure for EC
and RNCS. vSphere ESXi includes an SNMP agent that can perform
both SNMP queries and traps.
This chapter provides information and references to allow the
operator to configure the UCS hardware and ESXi hypervisor layer for
SNMP.
In This Chapter
 CIMC ...................................................................................................... 50
OL-27572-02 49
Chapter 6 EC and RNCS Infrastructure SNMP References
CIMC
The CIMC can be accessed using an SSH client, web browser, and/or SNMP through
the dedicated Ethernet management port.
While it is not part of the network application, the CIMC is a valuable tool for
maintaining the health of server hardware. For that reason, system administrators
are encouraged to read the documentation provided by Cisco and use the CIMC as
needed.
CIMC Documentation
Cisco provides configuration guides for CIMC on its website at:
http://www.cisco.com/en/US/products/ps10739/products_installation_and_confi
guraiton_guides_list.htm.
The configuration guides describe the various tasks you can perform in CIMC.
CIMC can be used to perform some typical management tasks, such as the
following:
 Power on, power off
 Configure boot order
 Update CIMC firmware
 Monitor faults, alarms, and server status
These documents may be of particular interest:
 GUI Configuration:
http://www.cisco.com/en/US/docs/unified_computing/ucs/c/sw/gui/confi
g/guide/1.4.1/b_Cisco_UCS_C-Series_GUI_Configuration_Guide_141.html.
 CLI Configuration:
http://www.cisco.com/en/US/docs/unified_computing/ucs/sw/cli/config/g
uide/1.4.1/b_Cisco_UCS_C-Series_CLI_Configuration_Guide_141.html
50 OL-27572-02
CIMC
VMware vSphere Documentation

vSphere 5 documents are available at: http://pubs.vmware.com/vsphere-
50/index.jsp?topic=%2Fcom.vmware.vsphere.monitoring.doc_50%2FGUID-
8EF36D7D-59B6-4C74-B1AA-4A9D18AB6250.html
The document Monitoring Networked Devices with SNMP and vSphere under
“ESXi and vCenter Server 5 Documentation” collection provides instructions to
configure SNMP on ESXi.
The following VMware knowledgebase article provides instructions for configuring
SNMP traps:
http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=d
isplayKC&externalId=1008065
OL-27572-02 51
7 Chapter 7
Customer Information
If You Have Questions
If you have technical questions, call Cisco Services for assistance.
Follow the menu options to speak with a service engineer.
Access your company's extranet site to view or order additional
technical publications. For accessing instructions, contact the
representative who handles your account. Check your extranet site
often as the information is updated frequently.
OL-27572-02 53
A
Appendix A
Appx auto letter
SNMP Trap Definitions for

Event Logging
Application and RepDB trap definitions and alarms are defined in this
appendix.
Note: Alarm definitions for network element alarms that are
forwarded by the EC are not included in this guide. Refer to the
network element installation and operation guide for this information.
In This Appendix
 Application Trap Definitions .............................................................. 56
 EC RepDB Alarm Definitions.............................................................. 57
 EC Application Alarm Definitions ..................................................... 59
 RNCS Application Alarm Definitions ............................................... 60
 DNCS-LEGACYNMI Alarm Definition ............................................ 61
OL-27572-02 55
Appendix A
SNMP Trap Definitions for Event Logging
Application Trap Definitions

The EC and RNCS application trap definitions and corresponding MIB are defined
in the following table:
Element and MIB Trap OID and Definition

MIB Type
EC SA-ALARM-MIB saAlarmEventInfo2—This is the notification

object (Trap) used for all application-related
Application
alarms generated by the EC. See EC Application
Traps
Alarm Definitions (on page 59) for more
information.
RNCS SA-ALARM-MIB saAlarmEventInfo2—This is the notification
Application object (Trap) used for all application-related
Traps alarms generated by the RNCS. See RNCS
Application Alarm Definitions (on page 60) for
more information.
EC RepDB RepDbHdr ciscoRepDbHdrNotification and
Traps RepDbFilesync ciscoRepDbFilesyncNotification - These two
trapOIDs are the notification objects used for
RepDB alarms generated by the primary EC.
See EC Application Alarm Definitions (on page
59) for more information.
Traps from DNCS-LEGACYNM-MIB saLegTrapEvent–This notification object is used
Edge Devices for proxying all the RPC alarms from various
edge devices as Traps.
56 OL-27572-02
EC RepDB Alarm Definitions

There are two trap OIDs that collectively provide alarm notifications pertaining to
the EC RepDB status. The first section describes the alarm definitions for the
Informix High Availability Data Replication and the second section describes the
alarm definitions for the file synchronization.

The following is a list of alarms that generate a ciscoRepDbHdrNotification trap by
the EC.
Note: The Alarm ID identified in the following table corresponds to the
repDbHdrAlarmID object provided in the ciscoRepDbHdrNotification trap.
Unique Trap :The following objects in this trap together uniquely identify the trap:
repDbHdrAlarmID, repDbHdrServerName, repDbHdrPairedServerName.
Alarm ID Description
101 The EC primary server was not able to connect to the database.
102 The EC primary server is not configured to operate with an EC secondary server.
103 The EC primary server has lost synchronization with the EC secondary server.
104 The EC primary server was not enabled for HDR successfully.
OL-27572-02 57
Appendix A
EC File Synchronization Alarm Definitions

The following is a list of alarms that generate a ciscoRepDbFilesynchNotification trap by the
EC.
Note: The Alarm ID identified in the following table corresponds to the object provided in
the ciscoRepDbFilesyncNotification trap.
Unique Trap: The following objects in this trap together uniquely identify the trap:
repDbFilesyncAlarmID, repDbFilesyncSource, repDbFilesyncDestination
Alarm ID Description
201 The EC primary server was not able to synchronize a file with the EC secondary
server. The file name is indicated in the trap.
202 The EC primary server file synchronization process is disabled, which means no
files are being synchronized with the EC secondary server
203 The EC primary server file synchronization process is not properly configured,
which means no files are being synchronized with the EC secondary server. This
alarm may occur during EC software maintenance whereby the file
synchronization configuration is altered.
58 OL-27572-02
EC Application Alarm Definitions
EC Application Alarm Definitions

The following is a list of alarms that generate an saAlarmEventInfo2 trap by the EC.
Note: The Alarm ID identified in the table below corresponds to the
saAlarmProvAlarmID object provided in the saAlarmEventInfo2 notification (trap).
saAlarmProvAlarmID, saAlarmEventType, saAlarmAlarmCategory,
saAlarmEventDeviceClass, saAlarmEventObjectName, saAlarmEventInstance
Alarm ID Alarm Category Description
0 Communication EC was unable to communicate to a remote network element.

1 Process EC process was unable to communicate to a process on a remote
network element.
10 Process One or more required EC processes are not running
11 Process One or more corefiles were created on the EC over the last two days.
OL-27572-02 59
Appendix A
RNCS Application Alarm Definitions

The following is a list of alarms that generate an saAlarmEventInfo2 notification by
the RNCS.
Note: The Alarm ID identified in the table below corresponds to the
saAlarmProvAlarmID object provided in the saAlarmEventInfo2 notification (trap).
Alarm ID Alarm Category Description
0 Communication RNCS was unable to communicate to a remote

network element.
10 Process One or more required RNCS processes are not
running.
11 Process One or more corefiles were created on the
RNCS over the last two days.
60 OL-27572-02
DNCS-LEGACYNMI Alarm Definition

This MIB provides alarm notifications pertaining to Edge Devices, such as the
GQAM, MQAM, CAQAM, NetCrypt and QPSK. Essentially, this is mapping of RPC
alarms to SNMP traps. There are two kinds of traps that are generated from the
devices GQAM, MQAM, CAQAM and NetCrypts. The discrete traps which are at
the device level (not associated with any session) like Excessive Temperature, Power
Supply Failure, and so on, as well as session traps, which are associated with
sessions.
saltAlarmId, saltProbableCause, saltDeviceInstance, saltDeviceClassString and, in
some instances, saltProbableCause and saltAlarmType can help in identifying the
details of the error.
QAM-Discrete Alarms
The following is a list of discrete alarms that generate a saLegTrapEvent trap by the
EC.
Note: The Alarm ID identified in the following list corresponds to the saltAlarmId
object provided in the saLegTrapEvent trap.
AlarmID Description
1 GQAM Modulator RF1
Communication Error
2 GQAM Modulator RF1 Excessive
Temperature
3 GQAM Modulator RF1 Power Supply
Failure
4 GQAM Modulator RF1 DC Lock
Detect Error
5 GQAM Modulator RF1 DC PLL
Unlocked Error
7 GQAM Modulator RF1 Calibration
Error
8 GQAM Modulator RF1 UC Lock
Detect Error
9 GQAM Modulator RF1 UC PLL
Unlocked Error
10 GQAM Modulator RF1 EEPROM
Failure
OL-27572-02 61
Appendix A
AlarmID Description
Communication Error
Temperature
Failure
Detect Error
Unlocked Error
Error
Detect Error
Unlocked Error.
Failure.
Communication Error.
Temperature.
Failure.
Detect Error.
Unlocked Error.
Error.
Detect Error.
Unlocked Error.
Failure.
Communication Error.
62 OL-27572-02
AlarmID Description
Temperature.
Failure.
Detect Error.
Unlocked Error.
Error.
Detect Error
Unlocked Error.
Failure.
41 GQAM Modulator Reset Detected.
42 GQAM Modulator Input 1 MPEG
Continuity Error.
Transport Error.
Continuity Error.
Transport Error.
Continuity Error.
Transport Error.
Continuity Error.
Transport Error.
Continuity Error.
Transport Error.
OL-27572-02 63
Appendix A
AlarmID Description
52 GQAM Modulator Input 1 Loss of
Signal Error.
Packets Error.
54 GQAM Modulator Input 1 FIFO
Overflow Error.
55 GQAM Modulator Input 1 Excess
Packets Dumped.
Signal Error.
Packets Error.
Overflow Error.
Packets Dumped.
Signal Error.
Packets Error.
Overflow Error.
Packets Dumped.
Signal Error.
Packets Error.
Overflow Error.
Packets Dumped.
Signal Error.
Packets Error.
Overflow Error.
64 OL-27572-02
AlarmID Description
Packets Dumped.
72-87 GQAM Modulator Output (1-16)
Packets Dropped.
88 GQAM Modulator Hardware Failure.
89 GQAM Modulator Software Runtime
Error.
90 GQAM Modulator Craft Port Activity.
91 GQAM Modulator Front Panel
Changed.
92-107 GQAM Modulator Output (1-16) FIFO
Overflow.
108 Dual Port GQAM Modulator Input
GIGE Port Switch.
109-124 TSR Output De-Jitter Failure.
125-130 GQAM Modulator Fan Failure.
131-146 GQAM Modulator Degraded Output
Video.
GQAM-Session Alarms
The following is a list of session alarms that generate an saLegTrapEvent trap by the
EC. The range in the alarm ID column corresponds to the alarm IDs for various
sessions.
Note: The Alarm ID identified in the following table corresponds to the saltAlarmId
AlarmID Description
256 - 1247 GQAM Modulator Session Data Error
1280 - 2271 GQAM Modulator Session Program Error
2304 - 3295 GQAM Modulator Session Conditional
Access Error
3328 - 4319 GQAM Modulator Session NP Gigabit
Ethernet Error
OL-27572-02 65
Appendix A
MQAM - Discrete Alarms

The following is a list of discrete alarms that generate an saLegTrapEvent trap by the
EC.
AlarmID Description
1 MQAM Modulator RF1 Communication
Error.
2 MQAM Modulator RF1 Excessive
Temperature.
3 MQAM Modulator RF1 Power Supply
Failure.
4 MQAM Modulator RF1 DC Lock Detect
Error
5 MQAM Modulator RF1 DC PLL
Unlocked Error
6 MQAM Modulator RF1 ASIC
Initialization Error
7 MQAM Modulator RF1 Calibration Error
8 MQAM Modulator RF1 UC Lock Detect
Error
9 MQAM Modulator RF1 UC PLL
Unlocked Error
10 MQAM Modulator RF1 EEPROM
Failure
11 MQAM Modulator RF1 Output Load
Error.
Error.
Temperature.
Failure
Error
Unlocked Error
66 OL-27572-02

Error
Unlocked Error.
Failure.
Error
Error.
Temperature.
Failure.
Error.
Unlocked Error.
Initialization Error.
31 MQAM Modulator RF3 Calibration
Error.
Error.
Unlocked Error.
Failure
Error
Error.
Temperature
Failure
OL-27572-02 67
Appendix A

Error
Unlocked Error
Error
Unlocked Error
Failure
Error
49 MQAM Modulator Reset Detected
50 MQAM Modulator MPEG Continuity
Error
51 MQAM Modulator MPEG Transport
Error
52 MQAM Modulator ASI1 Loss of Signal
Error
53 MQAM Modulator ASI1 MPEG Packets
Error
54 MQAM Modulator ASI1 FIFO Overflow
Error
55 MQAM Modulator ASI1 Excess Packets
Dumped
56 MQAM Modulator ASI2 Loss of Signal
Error
57 MQAM Modulator ASI2 MPEG Packets
Error
58 MQAM Modulator ASI2 FIFO Overflow
Error
59 MQAM Modulator ASI2 Excess Packets
Dumped
60 - 63 MQAM Modulator RF OUT (1-4) Low
Priority Packets Dropped
64 MQAM Modulator Hardware Failure
68 OL-27572-02
65 MQAM Modulator Software Runtime

Error
66 MQAM Modulator Craft Port Activity
67 MQAM Modulator Front Panel Changed
68 - 71 MQAM Modulator RF OUT (1-4) FIFO
Overflow
72 MQAM Modulator 3rd Party CA Not
Provisioned
73 MQAM Modulator Primary EIS Not
Connected
74 MQAM Modulator Secondary EIS Not
Connected
75 MQAM Modulator Primary ECMG Not
Connected
76 MQAM Modulator Secondary ECMG
Not Connected
77 MQAM Modulator EIS Link Lost
78 MQAM Modulator ECMG Link Lost
79 MQAM Modulator ECM Received For
Non- Existent Session
MQAM-Session Alarms
The following is a list of session alarms that generate a saLegTrapEvent trap by the
sessions.
AlarmID Description
128 - 1151 MQAM Modulator Session Data
Error.
1152 - 2175 MQAM Modulator Session
Program Error.
2176 - 3199 MQAM Modulator Session
Conditional Access Error.
OL-27572-02 69
Appendix A
QAM - Discrete Alarms

EC.
object provided in the saLegTrapEvent trap. QAMs do not have session alarms
AlarmID Description
0 QAM Modulator SMC Communication
Failure.
1 QAM Modulator Excessive Temperature.
2 QAM Modulator Power Supply Failure.
3 QAM Modulator Lock Detect Failure.
4 QAM Modulator PLL Unlocked.
5 QAM Modulator RAM Self-Test Failure.
7 QAM Modulator ASIC Initialization Failure.
8 QAM Modulator Power Supply Low.
9 QAM Modulator Calibration Error.
10 QAM Modulator SMC Communication Error
11 QAM Modulator Front Panel Changed
12 QAM Modulator Loss of Signal Error
13 QAM Modulator MPEG Packets Error
14 QAM Modulator FIFO Overflow Error
15 QAM Modulator Interface Error
16 QAM Modulator Excess Packets Dumped
17 QAM Modulator Reset Detected
18 QAM Modulator Hardware Error
19 QAM Modulator Runtime Error
20 QAM Modulator Craft Port Activity
21 QAM Modulator MPEG Continuity Error
22 QAM Modulator Transport Error
23 QAM Modulator Control Word Server Error
24 QAM Modulator ECM Bandwidth Error
25 QAM Modulator ECM Not Found Error
70 OL-27572-02
AlarmID Description
26 QAM Modulator Continuity Counter Error
27 QAM Modulator Transport Error Indicator
Error
GoQAM - Discrete Alarms

EC.
AlarmID Description
0 GoQAM Modulator System Alarm.
1 GoQAM Modulator RF1 Communication
Error.
2 GoQAM Modulator RF1 Excessive
Temperature.
3 GoQAM Modulator RF1 Power Supply
Failure.
4 GoQAM Modulator RF1 DC Lock Detect
Error.
5 GoQAM Modulator RF1 DC PLL Unlocked
Error.
7 GoQAM Modulator RF1 Calibration Error.
8 GoQAM Modulator RF1 UC Lock Detect
Error
9 GoQAM Modulator RF1 UC PLL Unlocked
Error.
10 GoQAM Modulator RF1 EEPROM Failure
21 GoQAM Modulator RF3 Communication
Error.
22 GoQAM Modulator RF3 Excessive
Temperature.
23 GoQAM Modulator RF3 Power Supply
Failure.
24 GoQAM Modulator RF3 DC Lock Detect
Error.
OL-27572-02 71
Appendix A
AlarmID Description
25 GoQAM Modulator RF3 DC PLL Unlocked
Error.
27 GoQAM Modulator RF3 Calibration Error.
28 GoQAM Modulator RF3 UC Lock Detect
Error.
29 GoQAM Modulator RF3 UC PLL Unlocked
Error.
30 GoQAM Modulator RF3 EEPROM Failure.
41 GoQAM Modulator Reset Detected.
42 GoQAM Modulator Input 1 MPEG
Continuity Error.
Transport Error.
Continuity Error.
Transport Error.
Continuity Error.
Transport Error.
Continuity Error.
Transport Error.
52 GoQAM Modulator Input 1 Loss of Signal
Error.
53 GoQAM Modulator Input 1 MPEG Packets
Error.
54 GoQAM Modulator Input 1 FIFO Overflow
Error.
55 GoQAM Modulator Input 1 Excess Packets
Dumped.
Error.
Error.
72 OL-27572-02
AlarmID Description
Error.
Dumped.
Error
Error
Error
Dumped
Error
Error.
Error
Dumped
72 - 74 GoQAM Modulator Output (1-3) Dropped
Packets
76 GoQAM Modulator Hardware Failure
77 GoQAM Modulator Software Runtime Error
78 GoQAM Modulator Craft Port Activity
79 GoQAM Modulator Front Panel Changed
80 - 82 GoQAM Modulator Output (1-3) FIFO
Overflow
84 - 87 GoQAM Modulator Input (1-4) Program
Conflict Error
88 - 91 GoQAM Modulator Input (1-4) PID Conflict
Error.
92 - 95 GoQAM Modulator PAT Update
96 - 99 GoQAM Modulator PMT Update
108 - 113 GoQAM Modulator Fan (1-6) Failure
120 GoQAM Modulator Encrypted Packets on
Clear Port 1 Alarm
OL-27572-02 73
Appendix A
AlarmID Description
121 GoQAM Modulator Encrypted Packets on
Clear Port 3 Alarm
122 - 137 GoQAM ASIC PLL Unlocked Error
GoQAM - Session Alarms

sessions.
AlarmID Description
256 - 1247 GoQAM Modulator Session Data Error
1280 - 2271 GoQAM Modulator Session Program Error
2304 - 3296 GoQAM Modulator Session Conditional
Access Error
NetCrypt - Discrete Alarms

EC.
AlarmID Description
0 Netcrypt Exceeded Max Temperature
1 Netcrypt Input 1 MPEG Continuity Error
2 Netcrypt Input 1 MPEG Transport Error
74 OL-27572-02
AlarmID Description
13 Netcrypt Input 7 MPEG Continuity Error.
17 Netcrypt Input 1 Loss of Input Signal
Synchronization
18 Netcrypt Input 1 Errored MPEG Packet.
19 Netcrypt Input 1 FIFO Overflow
20 Netcrypt Input 1 Packets Dumped.
Synchronization.
22 Netcrypt Input 2 Errored MPEG Packet
23 Netcrypt Input 2 FIFO Overflow.
Synchronization
28 Netcrypt Input 3 Packets Dumped
Synchronization
Synchronization.
36 Netcrypt Input 5 Packets Dumped
OL-27572-02 75
Appendix A
AlarmID Description
Synchronization.
Synchronization.
Synchronization.
49 Netcrypt Ethernet 1 Loss of Input Signal.
51 Netcrypt Ethernet 3 Loss of Input Signal
57 Netcrypt Output 1 FIFO Overflow
58 Netcrypt Output 1 Packets Dumped
65 Netcrypt Output 5 FIFO Overflow.
76 OL-27572-02
AlarmID Description
73 Netcrypt Reset Detected
74 Netcrypt General Purpose Hardware Error.
75 Netcrypt General Purpose Software Error
(runtime).
76 Netcrypt Craft Port Event Change
77 Netcrypt Front Panel Event Change
78 Netcrypt Third-Party CA Parameters Not
Provisioned
79 Netcrypt CA EIS Link Lost
80 Netcrypt Application Layer Connection to
EIS Failed
81 Netcrypt TCP Layer Connection to ECMG 1
Failed
Failed
Failed
Failed
ECMG 1 Failed
ECMG 2 Failed
ECMG 3 Failed
ECMG 4 Failed
89 Netcrypt Received ECM for Non-Existent
Session
OL-27572-02 77
Appendix A
AlarmID Description
90 Netcrypt SCG Refused PID
91 Netcrypt Input 1 ECM PID Conflict
99 Netcrypt Input 1 Gigabit Ethernet
Autonegotiate Failure
Autonegotiate Failure.
107 This alarm is not yet configured.
108 Netcrypt Input 1 PAT Update
78 OL-27572-02
AlarmID Description
116 Netcrypt Input 1 PMT Update
124 Fan 1 Failure
125 Fan 2 Failure
126 Fan 3 Failure
127 Fan 4 Failure
128 Fan 5 Failure
129 Power Supply Failure.
130 Netcrypt Egress Queue Failure.
131 Netcrypt bootp Server Failure
132 Netcrypt Ping Failure.
133 Netcrypt SNMP Failure.
134 Netcrypt Provision Trap ID.
135 Netcrypt Egress SDRAM Parity Failure.
136 Netcrypt Ingress SDRAM Parity Failure.
137 - 176 Netcrypt Reserved Alarms
177 Netcrypt Ingress Big Buffers Depleted
178 Netcrypt Ingress Big Buffers Depleted
179 Netcrypt Ingress Packet Descriptors
Depleted
180 Netcrypt Ingress Packet Descriptors
Depleted
181 Netcrypt Secondary Source Active
182 Netcrypt Output 0 Insert Bandwidth Failure
OL-27572-02 79
Appendix A
AlarmID Description
190 - 255 Netcrypt Reserved Alarms
NetCrypt - Session Alarms

sessions.
AlarmID Description
256 - 4255 Netcrypt Session Data Error
4256 - 8255 Netcrypt Session Program Error
8256 - 12255 Session Conditional Access Error
12256 - 16255 Session Gigabit Ethernet Error
80 OL-27572-02
Americas Headquarters http://www.cisco.com
Cisco Systems, Inc. Tel: 408 526-4000
170 West Tasman Drive 800 553-6387
San Jose, CA 95134-1706 Fax: 408 527-0883
USA
This document includes various trademarks of Cisco Systems, Inc. Please see the Notices
section of this document for a list of the Cisco Systems, Inc., trademarks used in this
document.
Product and service availability are subject to change without notice.
© 2014 Cisco and/or its affiliates. All rights reserved.
May 2014 Part Number OL-27572-02

20180808-094533113 - OL-SNMP - ADMIN - FOR - EC27572-02 Draft 003

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

20180808-094533113 - OL-SNMP - ADMIN - FOR - EC27572-02 Draft 003

Uploaded by

Copyright:

Available Formats

OL-27572-02

SNMP Administration Guide for the

Draft 003 May 29, 2014

Chapter 2 SNMP Access for the Network 11

Chapter 3 Filters in Net-SNMP 25

Chapter 4 SNMP Access for the RNCS 35

Chapter 5 nbiAgent Configuration 45

Chapter 6 EC and RNCS Infrastructure SNMP References 49

Chapter 7 Customer Information 53

Appendix A SNMP Trap Definitions for Event Logging 55

About This Guide

In addition to EC or RNCS application-specific information, the guest Solaris x86 OS

RNCS MIBs Purpose

InformixRepDB MIBs Purpose

Base MIBs Purpose

Master Agent MIB Information

MIB Location and Compilation

SNMP Access and Security

Define the Network SNMP Listening Interface

Edit the SNMP Startup Script

Define the Listening Address

Restart Agent and Verify EC SNMP Operation

Configure net-snmp to Monitor dncsInitd

Edit the prTable of UCDAVIS mib

Monitor the dncsInitd Process

When the dncsInitd process is started, the following trap is generated:

Create an SNMPv3 User

Create the SNMPv3 User

5 Open the /var/net-snmp/snmpd.conf file with a text editor.

Change SNMPv3 User Options

Restart the SNMP Agent and Verify Operation

Create SNMP Communities for the Network

Edit the Net-SNMP snmpd.conf File

Restart the SNMP Agent and Verify Operation

Define SNMPv3 Trap Destination Configuration

Before You Begin

SNMPv3 Traps Destination Configuration

Define the SNMPv3 Trap Destination

 Replace <authProt> with the authentication protocol defined for the

Restart Network SNMP Agent

SNMPv2 Traps for the Network

Edit the Net-SNMP snmpd.conf File

5 To configure additional trap destinations, repeat this procedure from step 4.

Restart the Net-SNMP Process

SNMP Trap Filters in Net-SNMP

How to Configure SNMP Trap Filters in Net-SNMP

index snmpNotifyTag snmpNotifyType snmpNotifyStorageType

index snmpTargetParamsMPModel snmpTargetParamsSecurityModel

2 Populate the two tables (snmpNotifyFilterProfileTable and

Configuring SNMP Trap Filters in Net-SNMP for

c Include nbiAgent traps in profile ExpController.

f Exclude FileSync (RepDB) traps in profile ExpController:

i Exclude nbiAgent traps in profile RepDb:

Define the RNCS SNMP Listening Interface

Log on to the RNCS

Edit the SNMP Startup Script

Define the Listening Address

3 Save and close the net-snmp configuration file.

Restart the RNCS SNMP Agent and Verify Operation

Create an SNMPv3 User

Log on to the RNCS

Create the SNMPv3 User

Change SNMPv3 User Options