User Manual SNMP for NEW-NMS

B4026 Rev. A

Neras

NEW-NMS

This page is intentionally left blank.

2
B4026 Rev. A

SNMP

List of Revisions
Rev.
A

Date
03-02-10

What is changed
The content of Rev. A of this manual is identical to Section VII of B1091 Rev. G.

B4026 Rev. A

NEW-NMS

This page is intentionally left blank.

4
B4026 Rev. A

SNMP

Table of Contents
1.0 2.0 General ......................................................................... 7 Introduction to SNMP for NEW-NMS .......................... 2.1 SNMP Agent .................................................... 2.2 Installation of SNMP Service and Extension Agents 2.2.1 TCP/IP ............................................................. 2.2.2 SNMP EMANATE Master Agent Service.......... 2.2.3 SNMP Agent .................................................... 2.2.3.1 Support for MIB-II and existing Microsoft Extension Agents ................. 2.3 Configuration of SNMP service ........................ 2.3.1 Agent Property Page ........................................ 2.3.2 Security Property Page .................................... 2.3.3 Traps Property Page ....................................... 2.3.4 NERA Traps PropertyPage .............................. 2.4 Starting or Stopping the SNMP service ............ 2.5 Troubleshooting ............................................... Management Information Base (MIB) ........................ 3.1 MIB Overview .................................................. 3.1.1 Network Tables ............................................... 3.1.1.1 netConfigTable ................................................ 3.1.1.2 netStatusTable ................................................ 3.1.2 Network Element Drill Down ............................ 3.1.2.1 CurrentElement ................................................ 3.1.2.2 ConfigMgmt ..................................................... 3.1.2.3 FaultMgmt ........................................................ 3.1.2.4 PerfMgmt ......................................................... 3.1.3 Traps ............................................................... 3.1.3.1 Trap Config table ............................................. 3.1.3.2 Nera Specific Traps ......................................... 3.1.4 Environment ..................................................... 3.2 MIB variables supported by Nera Radios ......... 3.4 Radios Supported by NEW-NMS release ........ 3.3 MIB variables supported by different NEW-NMS release ............................. 7 7 9 9 9 9 9 10 11 12 14 16 17 19 22 22 23 23 24 25 25 26 29 30 33 33 34 36 37 38 38

3.0

4.0
B4026 Rev. A

Getting Started ............................................................ 39

5

NEW-NMS

This page is intentionally left blank.

6
B4026 Rev. A

SNMP

1.0

General
(SNMP is available as an option for NEW-NMS) The SNMP architecture is based on the very simple concept of the Query/ Response model. The client, which sends out Queries, is generally described as the manager. The SNMP Server (the device that answers the queries) is referred to as the agent. The SNMP protocol enables a network management station to read and to change (or to write) an agents parameters according to the rules of SNMP. SNMP also allows the agents to send an unsolicited message to the management station under certain circumstances (a trap).

2.0

Introduction to SNMP for NEW-NMS

The NEW-NMS SNMP agent makes it possible for any SNMP based management system to perform efficient and cost effective configuration-, performance-, and fault management of any NEW-NMS managed network. The agent provides the current state of the network through a multitude of different values and tables, while state changes are communicated efficiently to the manager/client through extensive use of SNMP traps. Configuration changes of the managed equipment are not permitted, as the NEW-NMS/Configurator is best suited for this task. The size of the managed network is constrained by the NEW-NMS license. The license has to have SNMP enabled. The agent supports version SNMPv1 and SNMPv2c of the SNMP protocol.

2.1

SNMP Agent
SNMP Research EMANTE Run-time Extensible Agent System (version 15.1.0.7) is used for implementing the agent. The EMANTE architecture uses a Master/Subagent paradigm. The Master Agent is the agent protocol engine and performs the authentication, authorization, access control, and privacy functions. The Master Agent is multi-threaded and communicates asynchronously with Subagents. The Master Agent directs the retrieval and write processing and deenrolment of Subagents when they connect or disconnect. When requests arrive, it determines which Subagent(s) should receive the request. In other words, as much of the complicated processing as possible is put within the master agent.

B4026 Rev. A

NEW-NMS
Subagents are on the other hand, as simple as possible. They perform little more than the specific functions that collect or calculate the values for the MIB variable and pass that information to the Master Agent for sending the requesting manager. An example of the EMANTE architecture is shown below. The following items are copied during the installation of SNMP for NEWNMS.

Figure 1

EMANTE Architecture

SNMP EMANTE Master Agent Service SNMP EMANTE Adapter for NT Service. SNMP Agents supporting the newMIBR1 MIB. SnmpForNEWNMS.exe - Dialog based tool for starting, stopping and configuring the EMANTE SNMP service. newMIBR1.MIB - The information model for NEW-NMS (Written in SMIv2). newMIBR1-SMIv1.MIB - The information model for NEW-NMS (Written in SMIv1).

B4026 Rev. A

SNMP 2.2 Installation of SNMP Service and Extension Agents

In order for the SNMP agent to function a TCP/IP protocol stack and SNMP EMANATE Master Agent Service must be installed.

2.2.1

TCP/IP
The Microsoft TCP/IP-32 protocol is included with Windows NT. Please refer to the Windows manual or third party TCP/IP stack documentation for information on how to install TCP/IP.

2.2.2

SNMP EMANATE Master Agent Service

The SNMP service should automatically be installed when running the setup.exe. If not, you can use the following from the command line: snmpdm.exe -install To uninstall the SNMP service: From the command line: snmpdm.exe -remove

2.2.3

SNMP Agent
1.Place the NEW-NMS CD in the CD-drive (E:) 2.Choose Run from Windows Start Menu 3.Type E:\Setup.exe and press Enter. The installation Wizard will guide you through the installation. 4. Select NEW-NMS standalone or NEW-NMS server and click next. 5.Choose Custom Installation and select NEW-NMS Components. By clicking the change button the different components are displayed. 6.Select SNMP for NEW-NMS and click continue. Click next and the installation wizard will continue. Restart your computer.

2.2.3.1

Support for MIB-II and existing Microsoft Extension Agents

RFC1213 defines a set of MIB objects to report statistics about TCP/IP network operations, which take place on a particular system. In EMANATE part of MIB-II is contained in the master agent and part is contained in a subagent. Specifically, the system and snmp groups are contained in the Master Agent, and all other supported groups are in the subagent.

B4026 Rev. A

NEW-NMS
On Microsoft Windows NT, the MIB-II instrumentation is accessed through a Microsoft Windows NT SNMP Agent Extension provided by Microsoft. To make this information available to the Master agent the EMANTE Native Subagent Adapter for Microsoft Windows NT SNMP Agent Extensions must be installed. The Native adapter will look in the registry for entries under HKEY_LOCAL_MACHINE\ SYSTEM\CurrentControlSet\Services\SNMP\Parameters\ExtensionAgents for the Microsoft Windows NT SNMP Agent Extensions to load. Please see Microsoft documentation on how to install the Microsoft SNMP service. It is not necessary to use the Microsoft SNMP service it is only the extension agents that are used. The topic Starting and Stopping SNMP service covers how to disable a service. In order to install the Native Subagent Adapter as a service: msnsaagt.exe -install To run the native subagent as a system service: From the command line: msnsaagt.exe -start To stop the running native subagent adapter: From the command line: msnsaagt.exe -stop Before attempting to run the Native Subagent Adapter System Service, make sure that the SNMP EMANATE Master Agent is already running as a system service. To uninstall the service EMANTE Native Subagent Adapter for Microsoft Windows NT SNMP Agent Extensions: msnsaagt.exe -remove

2.3

Configuration of SNMP service

In order to configure the SNMP service on your computer you need to know the following information: Community names in your network. Trap destinations for each community. IP addresses for SNMP management hosts. Please note that for the changes made in the Agent tab, Security tab, and Traps tab to be effective, the SNMP service needs to be stopped and started again.

10

B4026 Rev. A

SNMP 2.3.1 Agent Property Page

The Agent page allows you to specify some of the entries in the MIB-II system objects.

Figure 2

Agent page

Fields

System Description A textual description of the entity, this value should include the full name and version, identification of the systems hardware type, software operating system, and networking software. System Location The physical location of this node (e.g., telephone closet, 3rd floor). System Contact The textual identification of the contact person for this managed node, together with information on how to contact this person. System Name An administratively assigned name for this managed node. By convention, this is the nodes fully qualified domain name.
B4026 Rev. A

Description

11

NEW-NMS 2.3.2 Security Property Page

The Security page allows you to specify the communities and hosts a computer will accept requests from, and to specify whether to send an authentication trap when an unauthorized community or host requests information.

Figure 3

Security page

12

B4026 Rev. A

SNMP Fields:
Send Authentication Traps

Decription:
Indicates whether the SNMP agent process is permitted to generate authentication-failure traps.

Accepted Community Names Lists the community names from which you will accept requests. Accept SNMP packets from any host Select this if SNMP packets are to be accepted from any IP address.

Only Accept SNMP packets Select this if SNMP packets are to be from specific hosts accepted only from specific IP addresses. Specific Host list Lists the accepted IP addresses from which you will accept SNMP packets.

Changing the Settings:

To make changes to an entry in a list; double click it and type in the changes.

Buttons:
Community Name: Add Adds a community name to the Accepted Community name list. Remove Removes the selected community name from the Accepted Community Names list. Manager Address: Add Adds an IP address to the Only Accept SNMP packets from Specific Hosts list. Remove Removes the host selected from the Only Accept SNMP packets from Specific Hosts list.

B4026 Rev. A

13

NEW-NMS 2.3.3 Traps Property Page

The Traps page allows the user to specify where to send traps. For each community name specify trap destination(s).

Figure 4

Traps page

14

B4026 Rev. A

SNMP
Fields: Description: Community Name Identifies a community to which you want to send traps. Security Model The security model for selected community name, SNMPv1 or SNMPv2c. Notification Type The type of notification: SNMPv1 trap. SNMPv2c trap or inform. Address IP address of manager that will receive notification.

Changing the Settings:

To make changes to an entry in a list; double click it and type in the changes.

Buttons:
Add Remove Adds the name you typed to the Trap Community Names List. Removes the selected Community Name from the Community Names List.

B4026 Rev. A

15

NEW-NMS 2.3.4 NERA Traps PropertyPage

The NERA Traps page allows you to specify which Nera specific traps you want to receive. Please note that it is not possible to disable trap no. 7.

Figure 5

Nera traps page

16

B4026 Rev. A

SNMP 2.4 Starting or Stopping the SNMP service

When the SNMP configurator program (SNMPforNEWNMS.exe) has been started an icon is added to the system tray. Depending on the status of the SNMP service, the following icons are displayed: Emanate SNMP service is running. Emanate SNMP service is not running. Emanate SNMP service is not installed.

To Start the SNMP service:

In order to start the SNMP service right-click the SNMP configurator icon in the system tray and select the popup menu item Start SNMP.

Figure 6

Popup menu start SNMP

To Stop the SNMP service:

Right-click on the SNMP configurator icon and select the popup menu item Stop SNMP.

Figure 7

Popup menu stop SNMP

B4026 Rev. A

17

NEW-NMS
To configure service startup, you must be logged on to a user account that has membership in the Administrators local group. As default a Service is set to automatically start when the system starts. If you do not want automatic start you must change the settings for the Service in question. The following startup options are available: Automatic Specifies whether the service should start automatically when the system starts. This service will start only if the computer has 12MB or more of random access memory (RAM). Manual Allows the service to be started by a user or a dependent service. Disabled Prevents the service from being started by a user or a dependent service. To change the Service settings for the SNMP EMANTE Master Agent: 1.Click StartSettingsControl Panel. The control panel is now displayed 2.Click the Services icon. The Services dialog is now displayed. 3.Go down the list of installed Services until you find SNMP EMANATE Master Agent. If you dont see it in the list the service is not installed. Please see the instructions for installing the SNMP service.

Automatic or Manual Start of Service

Figure 8

Services Dialogbox

18

B4026 Rev. A

SNMP
4. Select this service and click Startup. The Startup dialog is now displayed

Figure 9

Service Startup Dialogbox

5.Under Startup Type, click a startup type (Automatic, Manual, or Disabled) .

2.5

Troubleshooting
If no information is available from the NERA agent, do the following: 1.Check that the community name configured in the agent is matching the one used by the SNMP manager. 2.In the SNMP configurator verify that either the option Accept SNMP packets from anyhost is checked, or that the SNMP Manager used is listed in the Only accept SNMP packets from these host box. 3.Using a SNMP manager query the SNMP service for the MIB-II system group. If no response, check if the SNMP service is running by clicking the Services icon in the control panel. If the service is not started try to start it again.

B4026 Rev. A

19

NEW-NMS

Figure 10

Services Dialogbox

4.Open the file snmpd.cnf located in the SNMP for NEW-NMS directory and make sure the following entries are found in the file. At startup the Master Agent reads this configuration file for which subagents to load. subagent c:/winNT/system32/newMibR1.dll subagent c:/winNT/system32/newMibR1traps.dll Please note that the directory separators in the subagents path name must be forward slashes. 5.Run the Event Viewer from the start menu /program/administrative tools. Click on the log menu in the Event Viewer and select Applications.

Figure 11

Event Viewer

Event 1 If the extension DLLs have been successfully loaded by the SNMP. By double clicking the event entry a more detailed description is available.

20

B4026 Rev. A

SNMP

Figure 12

Event Details

Event 2 SNMP agent is closing. If newMIBR1.dll or newMIBRTraps.dll have failed to load the error message will describe the reason for not loading. The following might be the problem: Event 3 The Hardware-key is not plugged in or Sentinel Driver is not installed/ running !! Nera Extension Agent is not loaded. Event 4 The Hardware-key is not licensed for SNMP !! Nera Extension Agent is not loaded. Event 5 NEW-NMS is not installed !! Nera Extension Agent is not loaded.

B4026 Rev. A

21

NEW-NMS

3.0

Management Information Base (MIB)

All the information that is available from the Agent is presented in an information module, Management Information Base (MIB). MIB modules are built as trees and information is presented at the leafs of the tree. The MIBs are written according to the Structure of Management Information version 2(SMIv2). In order for a private company to write their own MIBs, they have to request a node under the enterprise branch of the private sub-tree from IANA to register its management objects. The node assigned to Nera is 2378 and all present and future NERA MIBs will be located under this node.

3.1

MIB Overview
The NERA NEW-NMS MIB is comprised of four parts; the network part, the network element drill down part, where current network status is available, the traps part, where the agent is configured to send specific traps, and environment part. All state changes are communicated to the manager via optional traps, and under specific circumstances some of the traps might use considerable bandwidth.
iso(1).org(3).dod(6).internett(1).private(4).enterprises(1)

nera(2378)

neraProducts(1)

transmissionNetworks(1)

new(1)

newMibR1(1)

netStatus(2)

element(3)

traps(4)

environment(5)

currentElement(1) configMgmt(2) faultMgmt(3) perfMgmt(4)

trapsConfig(1) trapsCommonObjects(2) trapsFaultObjects(3) trapsConfigObjects(4) trapsPerfObjects(5)

Figure 13 22

newMibR1 Overview.
B4026 Rev. A

SNMP 3.1.1 Network Tables

The network part contains two tables, netConfigTable (1.3.6.1.4.1.2378.1.1.1.1.1.1) and netStatusTable (1.3.6.1.4.1.2378.1.1.1.1.2.1), that gives a general overview of the network. Both tables are indexed with section address and station address, and thereby have a row for each element in the network.

3.1.1.1

netConfigTable
The network configuration table consists, in addition to the index (section, station), of link type, station type, serial number and station name.

netConfig(1)

netConfigTable(1)

netConfigEntry(1)

secAdr(1) staAdr(2) linkType(3) stationType(4) serialNumber(5) stationName(6)

Figure 14

netConfigTable

B4026 Rev. A

23

NEW-NMS 3.1.1.2 netStatusTable

The status table (netStatusTable) consists, in addition to the index (section, station), of number of alarms, and highest severity on element.

netStatus(2)

netStatusTable(1)

netStatusEntry(1)

secAdr(1) staAdr(2) numberOfAlarms(3) severity(4)

Figure 15

netStatusTable

24

B4026 Rev. A

SNMP 3.1.2 Network Element Drill Down

The element part (1.3.6.1.4.1.2378.1.1.1.1.3) is split into configuration-, fault- and performance-management sub trees. In addition, it has a node called currentElement that is used to choose which element to explore. In NEW-NMS, the elements are modelled as trees. This tree-model forms the basis of the MIB. Information is broken down under element (consist of section- and station-number), channel and port.

3.1.2.1

CurrentElement
In order to get element specific information the current section and current station must be set.

Figure 16

Current Element

B4026 Rev. A

25

NEW-NMS 3.1.2.2 ConfigMgmt

Information found under the configMgmt node (1.3.6.1.4.1.2378. 1.1.1.1.3.2) is data which is generic to different types of Nera-links. The configuration data gives an overview, not a complete picture of the configuration. The configuration node (1.3.6.1.4.1.2378.1.1.1.1.3.2) has the following information presented in its leafs: linkType - Link type (could be NL-code group, e.g. NL29x). stationType - Station type (Terminal, repeater, etc.). serialNumber - Serial number. stationName - Station name. numberOfAAU - Number of AAUs (Alarm Adapter Units). regChannels - Number of regular channels. protChannels - Number of protection channels. currentChannel - Attribute used for selecting which channel to collect channel-specific information from. ports - Available ports represented in a string. Include ports on currentChannel. currentPort - Attribute to select which port to collect port-specific information from. spaceDiversity - Shows if the current port has space diversity. hotStandby - Shows if the current port has Hot Standby. atpc - Shows if the current port has ATPC. coChannel - Shows if the current port has CoChannel. txFrequency - Shows transmit frequency of current channel. rxFrequency - Shows receive frequency of current channel. protSwitching - Enables the manager to perform manual protection switching. inventoryTable - Overview of production data. softwareTable - Overview of software installed on the unit. description - Text string that can be used for additional site information like: site description, site contact person, description of site access etc.

26

B4026 Rev. A

SNMP 3.1.2.2.1 softwareTable

Overview of software installed on selected element is presented in the softwareTable (1.3.6.1.4.1.2378.1.1.1.1.3.2.19). This feature is currently not supported.

element(3)

configMgmt(2)

softwareTable(17)

softwareEntry(1)

sotwareIndex(1) softwareName(2) softwareVersion(3) softwareDate(4) softwareStatus(5) softwareBank(6)

Figure 17

softwareTable Index of table. Name of software. Software version. Date of software (is currently not implemented). Status of software. Software location

SoftwareIndex SoftwareName SoftwareVersion SoftwareDate SoftwareStatus SoftwareBank

B4026 Rev. A

27

NEW-NMS 3.1.2.2.2 inventoryTable

Overview of HW-units of selected element is presented in the inventoryTable (1.3.6.1.4.1.2378.1.1.1.1.3.2.18). This feature is currently not supported.

element(3)

configMgmt(2)

elementInventoryTable(18)

elementInventoryTableEntry(1)

inventoryIndex(1) inventoryName(2) inventorySerialNumber(3) inventoryVersion(4)

Figure 18 InventoryIndex

Inventory table

Index of table, from 1 up to number of units present. InventoryName Article name of HW unit. InventorySerialNumber Serial number of HW unit. InventoryVersion Version of HW unit.

28

B4026 Rev. A

SNMP 3.1.2.3 3.1.2.3.1 FaultMgmt severity

The status of each element is identified by the severity of the alarms reported from the element to NEW-NMS. The leaf severity (1.3.6.1.4.1.2378.1.1.1.1.3.3.1) shows the highest severity of selected element.

3.1.2.3.2

alarmTable
In the new release there will be no longer support for the table alarmTable (1.3.6.1.4.1.2378.1.1.1.1.3.3.2). The table and all its entries are marked obsolete.

3.1.2.3.3

faultTable
The alarm list for current network element is presented in faultTable (1.3.6.1.4.1.2378.1.1.1.1.3.3.3).
element(3)

faultMgmt(3)

faultTable(2)

faultTableEntry(1)

faultTableAlarmIndex(1) faultTableAlarmID(2) faultTableAlarmName(3) faultTableAlarmSeverity(4) faultTableAlarmSource(5) faultTableAlarmTimeRaised(6)

Figure 19
B4026 Rev. A

faultTable. 29

NEW-NMS
The alarm list for current network element is presented in faultTable (1.3.6.1.4.1.2378.1.1.1.1.3.3.3). Alarms are fetched from NEW-NMS only once for a table retrieval. This is done because the alarmTable can change during the time the faultTable is being retrieved. The alarm list is retrieved from NEW-NMS for each getNext of faultTable.1. The agent keeps the list of active alarms until next time a getNext query is performed for faultTable.1. Note! The FaultTableTimeRaised is the time NEW-NMS registers the change in alarm and not the time the element generated it. FaultTableAlarmIndex FaultTableAlarmString FaultTableAlarmSeverity FaultTableAlarmID FaultTableAlarmSource FaultTableTimeRaised Index of table with a number starting from 1 going up to number of active alarms. Name of alarm Severity of alarm Alarm Identifier Unit responsible for alarm Time alarm was raised

3.1.2.4

PerfMgmt
In order for performance data to be available from the SNMP agent, performance logging must be enabled in NEW-NMS. Depending of the equipment type various performance data is available: CityLink has registers for storing up to the 16 latest G.826 performance measurements (B1, B2, M1 REI). NL29x radios stores the latest G.826 and G.821 measurements (B1, B2). NL24x radios stores the latest G.821 measurement (B1). NL18x radios stores the latest G.821 measurement (B1). The SNMP agent will only support the latest measurement, performance history has to be taken care of by the manager.

3.1.2.4.1

PerfTable
In the new release there will be no longer support for the perfTable(1.3.6.1.4.1.2378.1.1.1.1.3.4.1). The table and all its entries are marked obsolete.

3.1.2.4.2

PerfG826Table
G.826 performance data of current element for the last 15 minutes, 24 hours and 30 days are presented in the table perfTableG826 (1.3.6.1.4.1.2378.1.1.1.1.3.4.2).

30

B4026 Rev. A

SNMP
element(3)

perfMgmt(4)

perfG826Table(1)

perfG826Entry(1)

channel(1) port(2) ses(3) uas(4) bbe(5) es(6) period(7) source(8) startTime(9)

Figure 20

perfG826Table

G.826 performance data of current element for the last 15 minutes, 24 hours and 30 days are presented in the table perfTableG826 (1.3.6.1.4.1.2378.1.1.1.1.3.4.2). The table is indexed with channel and port. It presents four values from G.826. These values are SES, UAT, BBE and ES. Severely Errored Second (SES) One second period with >30% errored block or at least one severely disturbed period. Errored Second (ES) One or more errored blocks in one second period. Unavailable Seconds (UAS ) Degraded Minutes (DM) One block with error, not part of SES. In addition the following columns are presented in the table Period Time period for the measurement (15min, 24h, 1 month) source B1, B2, M1 REI StartTime Start of measurement: Year-Month-Day-Hour-Minute-Seconds
B4026 Rev. A

31

NEW-NMS 3.1.2.4.3 PerfG821Table

G.821 performance data of current element for the last 15 minutes, 24 hours and 30 days are presented in the table perfG821Table (1.3.6.1.4.1.2378.1.1.1.1.3.4.3).
element(3)

perfMgmt(4)

perfG826Table(1)

perfG826Entry(1)

channel(1) port(2) ses(3) uas(4) bbe(5) es(6) period(7) source(8) startTime(9)

Figure 21

perfG821Table

G.821 performance data of current element for the last 15 minutes, 24 hours and 30 days are presented in the table perfG821Table (1.3.6.1.4.1.2378.1.1.1.1.3.4.3). The table is indexed with channel and port. It presents four values from G.821. These values are SES, ES, UAT, and DM.

32

B4026 Rev. A

SNMP
Severely Errored Second (SES) A bit error ratio (BER) of 10-3 is measured with an integration time of one second Errored Second (ES) An ES is a second that contains at least one error. Unavailable Time (UAT ) Degraded Minutes (DM) A BER of 10-6 is measured with an integration time of one minute. In addition the following columns are presented in the table period Time period for the measurement (15min, 24h, 1 month) source B1, B2 StartTime Start of measurement: Year-Month-Day-Hour-MinuteSeconds

3.1.3

Traps
Purpose of the TRAP mechanism is to notify the management station of some event that has taken place that probably was not intended.

3.1.3.1

Trap Config table

The configuration is placed in a trap configuration table (trapConfigTable). Each trap may be enabled or disabled, and are enabled as default. It is not possible to disable the trapConfigChanged (trap no 7). All trap configuration is written/read to/from the registry.
traps(4)

trapsConfig(1)

trapsConfigTable(1)

trapsConfigEntry(1)

trapNumber(1) trapName(2) trapEnable(3)

Figure 22
B4026 Rev. A

trapsConfigTable. 33

NEW-NMS 3.1.3.2 Nera Specific Traps

Variables sent with the different traps are found under the nodes: commonObjects, faultObjects, configObjects, performanceObjects. NEWMIB includes 13 enterprise specific traps: 1. severityChanged. Sent when the highest severity on an element changes. Variables in the trap are trapSequenceNumber, SecAdr, StaAdr, HighestSeverityOnElement, TimeStamp 2. raisedAlarm. Sent when an alarm is raised. Variables in the trap are trapSequenceNumber, SecAdr, StaAdr, AlarmId, AlarmName, AlarmSeverity, Node, TimeStamp. 3. clearedAlarm. Sent when an alarm is cleared. Variables in the trap are trapSequenceNumber, SecAdr, trapStaAdr, AlarmId, AlarmName, AlarmSeverity, Node, TimeStamp. 4. neAdded. Sent when a network element is added to the network in NEW-NMS and not automatically generated when a network element is physically connected to the network. Variables in the trap are trapSequenceNumber, SecAdr, StaAdr, LinkType, StationType, SerialNumber, StationName, TimeStamp. 5. neRemoved. Sent when a network element is removed from the network in NEW-NMS. It is, in current NEW-NMS release, not possible to remove network elements. This trap is thereby not sent from the agent. Variables in the trap are trapSequenceNumber, SecAdr, StaAdr, LinkType, StationType, SerialNumber, StationName, TimeStamp. 6. trapOverflow. This trap is generated when NEW-NMSs eventlist is flooded with events. Currently the maximum number of events is set to 500. Variable is trap sequence number. 7. trapConfigChanged. This trap is generated when the configuration of the traps is changed. Variables sent are trap sequenceNumber, trapNumberChanged, and trapStatus (enabled/disabled). 34
B4026 Rev. A

SNMP
8. performanceDataReady. This trap is sent when new performance data is ready for an element. Variables in the trap are trapSequenceNumber, SecAdr, StaAdr, performanceType, period, startTime, timeStamp 9. performanceDataG826Changed. This trap is sent when G.826 performance data for new period is different from previous period. Variables in the trap are trapSequenceNumber, SecAdr, StaAdr, Channel, Port, SES, UAS, BBE, ES, Period, Source, StartTime, TimeStamp. 10. performanceDataG821Changed. This trap is sent when G.821 performance data for new period is different from previous period. Variables in the trap are trapSequenceNumber, SecAdr, StaAdr, Channel, Port, SES, UAT, DM, ES, Period, Source, StartTime, TimeStamp. 11. elementConfigChanged. This trap is sent when element configuration is changed. Variables in the trap are trapSequenceNumber, Description, TimeStamp 12. newnmsStarting. This trap is sent when NEW-NMS is started (when NEW-NMS is registered in ROT) Variables in the trap are trapSequenceNumber, trapTimeStamp 13. newnmsClosing. This trap is sent when NEW-NMS is closed down (when the open document in NEW-NMS is closed). Variables in the trap are trapSequenceNumber, trapTimeStamp.

B4026 Rev. A

35

NEW-NMS 3.1.4 Environment

environment(5)

environmentTimeZone(1) environmentNewStatus(2) environmentNEWNMSversion(3) environmentnewMibR1AgentVersion(4)

Figure 23 environment TimeZone Information Time zone settings for the PC running NEW-NMS. UTC = localtime TimeZone. NEW-NMS status Indicates whether NEW-NMS is currently running with an open network or not. NEWNMSversion Software version of NEW-NMS. NewMIBR1AgentVersion Software version of the running Nera SNMP agent.

36

B4026 Rev. A

SNMP 3.2 MIB variables supported by Nera Radios

Not all the information in the MIB tree is available for all types of Nera radios. The table below shows which equipment specific objects are available for the different radios. Not all the objects are supported by all releases of NEW-NMS, please see the overview of MIB variables supported by NEW-NMS releases.
0LEREMHFW 1 /[ 1/[ 1/[ &LW\/LQN

elem entLinkType elem entStationType elem entSerialNumber elem entStationNam e elem entNumberOfAAU elem entRegChannels elem entProtChannels elem entCurrentChannel elem entPorts elem entCurrentPort elem entspaceDiversity elem entHotStandby elem entAtpc elem entCoChannel elem entTxFrequency elem entRxFrequency elem entInventoryTable elem entSoftwareTable faultTable perfG826Table perfG821Table

B4026 Rev. A

37

NEW-NMS 3.3 MIB variables supported by different NEW-NMS release

The table below shows MIB objects supported by the different releases of NEW-NMS.
1(:1065HOHDVH 0LEREMHFW 5$ 5$ 5$ 5$ 5$ 5$

elementLinkType elementStationType elementSerialNumber elementStationName elementNumberOfAAU elementRegChannels elementProtChannels elementCurrentChannel elementPorts elementCurrentPort elementspaceDiversity elementHotStandby elementAtpc elementCoChannel elementTxFrequency elementRxFrequency elementInventoryTable elementSoftwareTable faultTable perfG826Table perfG821Table Specific Trap 1 Specific Trap 2 Specific Trap 3 Specific Trap 4 Specific Trap 5 Specific Trap 6 Specific Trap 8 Specific Trap 9 Specific Trap 10 Specific Trap 11

Does not support AlarmID and alarmTimeRaised. Includes AlarmID and alarmTimeRaised. Trap overflow limit set to 100 events. Trap overflow limit set to 500 events.

3.4

Radios Supported by NEW-NMS release

5DGLR 5$ 5 $ 5$!

NL18x NL24x NL29x CityLink

CityLink HotStandby support added.

38

B4026 Rev. A

SNMP

4.0

Getting Started
This tutorial will try to give a brief introduction on how information is extracted from NEW-NMS using the NEW-NMS SNMP agent and a SNMP manager. 1.Start NEW-NMS and open a network 2.Open the application SNMPforNewNms.exe. 3.Configure the SNMP service so it fits your needs by using the SNMP Configurator. 4.Start the SNMP service 5.Start a SNMP manager, in this tutorial Hewlett Packards OpenView for Windows is used. 6.Compile newMibR1.mib into the manager NOTE: This setup is for HP Openview nodemanager - other SNMPmanagers might have different implementation.

Figure 24

Add MIBs to SNMP Manager

B4026 Rev. A

39

NEW-NMS
7.Browse to the netConfig table (1.3.6.1.4.1.2378.1.1.1.1.1.1) as shown in Figure 25.

Figure 25

Define Query netConfigTable.

8.Click perform and the result will be similar to what is shown in Figure 26.

Figure 26

Result of netConfigTable Query

9.Explore a single element. Browse to the currentElement node (1.3.6.1.4.1.2378.1.1.1.1.3.1) and select currentSection and currentStation. Set the currentSection and currentStation to an element in your network. In the example shown in Figure 27.

40

B4026 Rev. A

SNMP

Figure 27

Define Query Current Element.

10. In order to see configuration data for selected element Query the node configMgmt. 11. Click perform and the result will be similar to what is shown in Figure 28.

Figure 28

Result of configMgmt Query

12. In order to see current Alarms for selected element Query the faultTable. 13. Click perform and the results will be similar to what is shown in Figure 29.

B4026 Rev. A

41

NEW-NMS

Figure 29

Result of faultTable Query

42

B4026 Rev. A