Simple Network Management Protocol in the Avaya Media Processing Server Environment

Simple Network Management Protocol in the Avaya Media Processing Server Environment Release 4.1 NN44100-126 Issue 01.02 October 2014

2014 Avaya Inc. All Rights Reserved. Notice While reasonable efforts have been made to ensure that the information in this document is complete and accurate at the time of printing, Avaya assumes no liability for any errors. Avaya reserves the right to make changes and corrections to the information in this document without the obligation to notify any person or organization of such changes. Documentation disclaimer Documentation means information published by Avaya in varying mediums which may include product information, operating instructions and performance specifications that Avaya may generally make available to users of its products and Hosted Services. Documentation does not include marketing materials. Avaya shall not be responsible for any modifications, additions, or deletions to the original published version of documentation unless such modifications, additions, or deletions were performed by Avaya. End User agrees to indemnify and hold harmless Avaya, Avaya's agents, servants and employees against all claims, lawsuits, demands and judgments arising out of, or in connection with, subsequent modifications, additions or deletions to this documentation, to the extent made by End User. Link disclaimer Avaya is not responsible for the contents or reliability of any linked websites referenced within this site or documentation provided by Avaya. Avaya is not responsible for the accuracy of any information, statement or content provided on these sites and does not necessarily endorse the products, services, or information described or offered within them. Avaya does not guarantee that these links will work all the time and has no control over the availability of the linked pages. Warranty Avaya provides a limited warranty on Avaya hardware and software. Refer to your sales agreement to establish the terms of the limited warranty. In addition, Avaya s standard warranty language, as well as information regarding support for this product while under warranty is available to Avaya customers and other parties through the Avaya Support website: http://support.avaya.com or such successor site as designated by Avaya. Please note that if you acquired the product(s) from an authorized Avaya Channel Partner outside of the United States and Canada, the warranty is provided to you by said Avaya Channel Partner and not by Avaya. Licenses THE SOFTWARE LICENSE TERMS AVAILABLE ON THE AVAYA WEBSITE, HTTP://SUPPORT.AVAYA.COM/LICENSEINFO OR SUCH SUCCESSOR SITE AS DESIGNATED BY AVAYA, ARE APPLICABLE TO ANYONE WHO DOWNLOADS, USES AND/OR INSTALLS AVAYA SOFTWARE, PURCHASED FROM AVAYA INC., ANY AVAYA AFFILIATE, OR AN AVAYA CHANNEL PARTNER (AS APPLICABLE) UNDER A COMMERCIAL AGREEMENT WITH AVAYA OR AN AVAYA CHANNEL PARTNER. UNLESS OTHERWISE AGREED TO BY AVAYA IN WRITING, AVAYA DOES NOT EXTEND THIS LICENSE IF THE SOFTWARE WAS OBTAINED FROM ANYONE OTHER THAN AVAYA, AN AVAYA AFFILIATE OR AN AVAYA CHANNEL PARTNER; AVAYA RESERVES THE RIGHT TO TAKE LEGAL ACTION AGAINST YOU AND ANYONE ELSE USING OR SELLING THE SOFTWARE WITHOUT A LICENSE. BY INSTALLING, DOWNLOADING OR USING THE SOFTWARE, OR AUTHORIZING OTHERS TO DO SO, YOU, ON BEHALF OF YOURSELF AND THE ENTITY FOR WHOM YOU ARE INSTALLING, DOWNLOADING OR USING THE SOFTWARE (HEREINAFTER REFERRED TO INTERCHANGEABLY AS YOU AND END USER ), AGREE TO THESE TERMS AND CONDITIONS AND CREATE A BINDING CONTRACT BETWEEN YOU AND AVAYA INC. OR THE APPLICABLE AVAYA AFFILIATE ( AVAYA ). Copyright Except where expressly stated otherwise, no use should be made of materials on this site, the Documentation, Software, Hosted Service, or hardware provided by Avaya. All content on this site, the documentation, Hosted Service, and the Product provided by Avaya including the selection, arrangement and design of the content is owned either by Avaya or its licensors and is protected by copyright and other intellectual property laws including the sui generis rights relating to the protection of databases. You may not modify, copy, reproduce, republish, upload, post, transmit or distribute in any way any content, in whole or in part, including any code and software unless expressly authorized by Avaya. Unauthorized reproduction, transmission, dissemination, storage, and or use without the express written consent of Avaya can be a criminal, as well as a civil offense under the applicable law. Third Party Components Third Party Components mean certain software programs or portions thereof included in the Software or Hosted Service may contain software (including open source software) distributed under third party agreements ( Third Party Components ), which contain terms regarding the rights to use certain portions of the Software ( Third Party Terms ). As required, information regarding distributed Linux OS source code (for those Products that have distributed Linux OS source code) and identifying the copyright holders of the Third Party Components and the Third Party Terms that apply is available in the Documentation or on Avaya s website at: http:// support.avaya.com/copyright or such successor site as designated by Avaya. You agree to the Third Party Terms for any such Third Party Components. Trademarks The trademarks, logos and service marks ( Marks ) displayed in this site, the Documentation, Hosted Service(s), and Product(s) provided by Avaya are the registered or unregistered Marks of Avaya, its affiliates, or other third parties. Users are not permitted to use such Marks without prior written consent from Avaya or such third party which may own the Mark. Nothing contained in this site, the Documentation, Hosted Service(s) and Product(s) should be construed as granting, by implication, estoppel, or otherwise, any license or right in and to the Marks without the express written permission of Avaya or the applicable third party. Avaya is a registered trademark of Avaya Inc. All non-avaya trademarks are the property of their respective owners. Linux is the registered trademark of Linus Torvalds in the U.S. and other countries. Downloading Documentation For the most versions of Documentation, see the Avaya Support website: http://support.avaya.com, or such successor site as designated by Avaya. Contact Avaya Support See the Avaya Support website: http://support.avaya.com for Product or Hosted Service notices and articles, or to report a problem with your Avaya Product or Hosted Service. For a list of support telephone numbers and contact addresses, go to the Avaya Support website: http://support.avaya.com (or such successor site as designated by Avaya), scroll to the bottom of the page, and select Contact Avaya Support.

Contents Chapter 1: Introduction... 6 Overview... 6 SNMP Protocol Stack Replacement... 6 Simple Network Management Protocol... 7 Network Management Concepts... 7 Management Information Base (MIB)... 7 Structure of Management Information... 9 Protocol... 10 Sample Manager and Agent Interaction... 11 get-request Message... 11 get-next-request Message... 11 set-request Message... 12 get-bulk-request Message... 12 get-response Message... 12 inform-request Message... 13 trap Message... 13 SNMP and MPS Integration... 14 Periphonics MIB... 14 MPS Manager and SNMP Integrations... 14 Understanding Components... 15 Chapter 2: Installation and Configuration... 16 SNMP Installation... 16 Package Licensing... 16 Defining Trap Destinations Automatically... 17 In Solaris... 17 In Windows... 18 Verify Agents Response... 19 Installation Upgrades... 20 Solaris Upgrade... 20 SNMP System Startup... 20 Solaris Systems... 21 Windows Systems... 21 MIB Files... 23 Configuration Files... 24 Environment Variables... 25 Editing... 25 In Solaris... 26 In Windows... 26 Master/Subagent Related... 28 Command Line Options... 29 October 2014 Simple Network Management Protocol in the Avaya Media Processing Server Environment 3

Contents In Solaris... 29 In Windows... 29 Configuring snmpd.conf... 29 Configuring Trap Destinations... 30 Modifying Security Access Rights... 30 Default MIB-II Values... 30 Security Access Rights... 31 Assigning a Security Name to a Community... 31 Defining Security Groups... 32 Defining View Subtrees... 33 Configuring Group Access Rights... 33 Defining Trap Destinations... 34 Defining the Default Trap Community... 35 Converting SNMP configuration to Net-SNMP... 36 Converting community strings/group associations... 36 Converting View Subtrees... 37 Converting Group Access Rights... 37 Converting Trap Destinations... 38 Error Logging... 39 Executables... 39 Agents... 39 SNMP Command Line Utilities... 40 Chapter 3: MPS Functions and Administration... 41 Overview... 41 SNMP Utilization... 42 Communication... 42 System Architecture... 42 MIB Variables... 43 Access... 43 Status... 44 Types... 44 Instance Identification... 45 Direct Referencing... 45 Table Referencing... 45 SNMP Applied... 47 Getting a Value... 47 Setting a Value... 48 Viewing Traps... 48 The MIB Applied... 50 Subtrees... 50 Events Group Notifications Subtree... 50 Component Events Alarms Subtree... 51 VRU Subtree... 52 4 Simple Network Management Protocol in the Avaya Media Processing Server Environment October 2014

Contents Line Subtree... 53 Span Table Subtree... 54 Applications Subtree... 55 Applications Stats Subtree... 55 Host Subtree... 56 LU Subtree... 57 Components Subtree... 57 Chapter 4: MPS Manager and SNMP Mappings... 59 Overview... 59 Mappings... 59 MIB-II... 59 Enterprise MIB... 60 Events Group Notifications Subtree... 60 Component Events Alarms Subtree... 61 VRU Subtree... 62 Line Subtree... 63 Span Table Subtree... 65 Applications Subtree... 66 Applications Stats Subtree... 67 Host Subtree... 67 LU Subtree... 68 Components Subtree... 68 Chapter 5: Troubleshooting/FAQs... 70 Overview... 70 Troubleshooting... 70 Frequently Asked Questions (FAQs)... 74 Chapter 6: Periphonics MIB Reference... 78 Overview... 78 Basic Tree Structure... 78 Detailed Component Structure... 81 Chapter 7: Request For Comment (RFC)... 116 Access to RFCs... 116 Tables of RFC... 116 October 2014 Simple Network Management Protocol in the Avaya Media Processing Server Environment 5

Chapter 1: Introduction This chapter covers: 1. Simple Network Management Protocol 2. SNMP and MPS Integration Overview The Simple Network Management Protocol (SNMP) provides a uniform method for managing a network of different products from multiple vendors. An Avaya Media Processing Server (MPS) system with the Periphonics Management Information Base (MIB) can be integrated into existing TCP/IP networks and controlled by third-party management tools. In addition, the Periphonics MIB can be used to develop custom MPS management applications. SNMP Protocol Stack Replacement In the PERIsnmp package, the SMNP protocol software is replaced with Net-SNMP software. The change applies to MPS 3.5 and later releases, beginning with MPS 3.5 patch snmp6.5.0.7 (MPS 3.5-Patchbundle 6); and with MPS 4.1 patch snmp7.1.0.1 (MPS4.1-Patchbundle 1). All new systems and existing systems that have applied the aforementioned patch levels or higher will have the Net- SNMP protocol stack replacement take effect. The change to Net-SNMP impacts: Configuration of Trap Destinations and Group Access Rights Names of SNMP executables on Solaris and Windows Names of SNMP services on Windows SNMP Manager command line utilities (former getone, getmany, gettab, traprcv, etc) SNMP Environment Variables on Solaris and Windows This document is written for the Net-SNMP implementation. The MPS 3.5 release of this document can be referred to for those installations that continue to use earlier patch levels of PERIsnmp. The change to Net-SNMP necessitates that any site-specific configuration of trap destinations and group access rights (in $MPSHOME/common/etc/snmpd.cnf) must be reproduced using the new 6 Simple Network Management Protocol in the Avaya Media Processing Server Environment October 2014

Simple Network Management Protocol syntax of the Net-SNMP master agent configuration file ($MPSHOME/common/etc/snmpd.conf). For more information, see Converting SNMP configuration to Net-SNMP on page 36. Simple Network Management Protocol Network Management Concepts To manage networks, management personnel communicate with, monitor or control one or more network elements through a workstation. Network management architecture has four core components: Management Station: Network management personnel monitor and control the network from the network management station. The management station communicates with network elements to perform tasks such as data analysis and fault recovery. The management station generates requests and receives responses and event reports. In SNMP, the management station is referred to as the manager. In client/server architecture, the manager is a client. In MPS, the manager is analogous to an MPS Manager workstation. Management Agent: A management agent receives and processes management station requests for information about network elements and for event reports. In SNMP, a management agent is referred to as an agent. In client/server architecture terms, the agent is a server. Management Information Base (MIB): An MIB is a collection of objects that describe one or more network elements. An MIB is a form of database schema containing a set of system components that can be queried or controlled. For additional information, see Management Information Base (MIB) on page 7. Network Management Protocol: Network Management Protocol is the format for transmitting data between the management station and agents. SNMP provides a network management protocol for allowing managers (clients) to perform status and control functions by querying agents (servers) about the network elements described in various MIBs (databases). Management Information Base (MIB) The Periphonics MIB specifies variables that describe an MPS network element. Variables are recognized by both the management station and agents because the MIB is specified in a standard syntax called Abstract Syntax Notation One (ASN.1). October 2014 Simple Network Management Protocol in the Avaya Media Processing Server Environment 7

Introduction A management station queries MIB variables to determine information about a network element. The management station may also change a MIB variable to modify a property or state of the network element. By modifying MIB variables, the management station exerts control over network elements. The MIB is a database of objects that work in attribute/value pairs and whose hierarchy is a tree-like structure. SNMP is defined using a single standard MIB that can be extended by vendors to include product-specific subtrees. MIB-II is the standard subtree that must be implemented in all internet-managed networks. The MIB- II standard subtree is defined in Request for Comments 1213 (http://tools.ietf.org/html/rfc1213) For additional information, see Access to RFCs on page 116. MIB-II is the core branch of SNMP, where information about attributes can be set, queried, or both. MIB-II is divided into the following groups: system: Overall system information interfaces: Information about the interfaces from the system to an attached subnetwork at: Address-translation table for internet-to-subnet address mapping ip: Information about the Internet Protocol on this system icmp: Information about the Internet Control Message Protocol on this system tcp: Information about the Transmission Control Protocol on this system udp: Information about the User Datagram Protocol on this system egp: Information about External Gateway Protocol on this system transmission: Information about transmission schemes and access protocols at each system interface snmp: Information about the Simple Network Management Protocol on this system. In addition to MIB-II, there is a subtree called enterprises. This subtree allows vendors to extend the MIB to support their products. +---internet(1) +--- mgmt(2) +---mib-2(1) +--- system(1) : +--- interfaces(2) : +--- at(3) : +--- ip(4) : +--- icmp(5) : 8 Simple Network Management Protocol in the Avaya Media Processing Server Environment October 2014

Structure of Management Information +--- tcp(6) : +--- udp(7) : +--- egp(8) : +--- transmission(10) : +--- snmp(11) : : +--- private(4) +--- enterprises(1) : Vendors can define their own products by extending the MIB at the enterprise branch. After vendor products are defined, they are recognized by the management tools. Structure of Management Information The Structure of Management Information (SMI) defines an identification scheme and a set of common structures used to reference variables within the MIB. SNMP allows for two simple data types: scalar and two dimensional arrays of scalar (tables). SMI data types can be divided into two main components: Universal Types and Application Types. In turn, each SMI data type encompasses the following: Universal Types: INTEGER: May or may not have restrictions. These restrictions include ranges (for example, TCP/IP port numbers are between 0 and 65535) or enumerated types (for example, state of a system unknown(1), up(2), down(3), and so on). OCTECT STRING: String of 0 or more 8-bit bytes. These strings are not NULL terminated. OBJECT IDENTIFIER: Sequence of decimal-separated integers used to identify a variable within the MIB. NULL: Used to indicate that the variable has no value. SEQUENCE: Similar to a structure in C. SEQUENCE OF: Defines a vector whose elements are a simple data type. This is used to define tables within SNMP. Application Types: DisplayString: String of 0 or more 8-bit bytes where each byte must be a character from NVT ASCII set. The string length must be [0...255]. IpAddress: Octect string of length 4 specifying the IP address. Each byte represents a byte of the IP address. October 2014 Simple Network Management Protocol in the Avaya Media Processing Server Environment 9

Introduction Counter: Non-negative integer whose value increases from 0 to 2 32-1. When the maximum value is reached, it resets to zero. Gauge: Non-negative integer which can increase or decrease. The range of values is 0 to 2 32-1. TimeTicks: Counter representing the time in hundredths of seconds since a specific event. SMI also specifies how MIB variables are referenced. MIB variables are arranged in a tree structure. An MIB variable is referenced by its individual branch (node) names separated by periods. The node names are arranged in order from the root of the tree traversing the path to the object being referenced. For example, the reference (or object identifier) for the enterprises MIB variable is: iso.org.dod.internet.private.enterprises. Each object identifier also has a numeric representation. The numeric representation of the above the enterprise MIB variable is 1.3.6.1.4.1. Both the manager and agent use this sequence of integers to identify MIB variables. Protocol The SNMP protocol is the format that managers and agents use to transmit data to each other. MPS agents support SNMPv1 and SNMPv2c. The following example describes a typical use of SNMP protocol by manager and agents: The manager sends a request to the agent to get or modify the value of a variable defined in the MIB. The SNMP agent in the MPS implementation supports SNMPv1 and SNMPv2c. The agent detects the version of SNMP stipulated by the manager and automatically replies in kind. The manager receives responses from the agent as well as process event reports generated by the agent. SNMPv1 defines five types of messages that are exchanged between the manager and agent: get-request: Message sent from the manager to the agent asking for the value of one or more variables. get-next-request: Message sent from the manager to the agent asking for the value of the next variable after one or more variables. set-request: Message sent from the manager to the agent asking to change the value of one or more variables. get-response: Message sent from the agent to the manager in response to a get-request, getnext-request, or set-request. trap: Unsolicited message sent from the agent to the manager to notify the occurrence of some asynchronous event. SNMPv1 defines six traps: coldstart, warmstart, linkdown, linkup, authenticationfailure, egpneighborloss, and enterprisespecific. The enterprisespecific allows organizations to define their own traps. Traps are analogous to alarms in the MPS environment. 10 Simple Network Management Protocol in the Avaya Media Processing Server Environment October 2014

Sample Manager and Agent Interaction In addition, SNMPv2c extends the SNMPv1 message types to include: get-bulk-request: Allows retrieval of large numbers of variables at one time (similar to numerous individual iterations of get-next-requests). inform-request: Used for manager-to-manager communications. Sample Manager and Agent Interaction A typical MIB-II system subtree is defined as: system(mib-2) (1) +--- sysdescr(1) +--- sysobjectid(2) +--- sysuptime(3) +--- syscontact(4) +--- sysname(5) +--- syslocation(6) +--- sysservices(7) get-request Message To get a description of the network entity, the network manager sends a get-request message on the variable: iso.org.dod.internet.mgmt.mib-2.system.sysdescr.0 The agent sends a get-response message indicating that this variable contains the value Avaya MPS Network. get-next-request Message To determine what variable comes after the variable syscontact, the Network manager sends a getnext-request message on the variable: iso.org.dod.internet.mgmt.mib-2.system.syscontact.0 The agent sends a get-response message indicating the next variable after syscontact is iso.org.dod.internet.mgmt.mib2.system.sysname.0 October 2014 Simple Network Management Protocol in the Avaya Media Processing Server Environment 11

Introduction Its value is peri.com. An SNMP manager can use a get-next-request to iterate through MIB tables. MIB tables are much like arrays; they allow the specification of sets of similarly defined elements. An SNMP manager can also use a get-next-request to iterate through the list of variables supported by an SNMP agent to see if a particular facility is available. set-request Message A network manager can update the value of a variable by sending a set-request message on the variable. For example, if the location of the MPS network moves from the eighth to the second floor, the network manager must update the value of the syslocation variable. The network manager would indicate the new value is 4000 Vets Hwy 2nd Floor by sending a set-request message on the variable: iso.org.dod.internet.mgmt.mib-2.system.syslocation.0 The agent sends a get-response message indicating that the value of syslocation is changed to 4000 Vets Hwy 2nd Floor. An agent can invoke actions when a variable is modified. For example, if an MIB contained a variable called sysstate with enumerated values sysup(1) and sysdown(2), the agent uses a setrequest message to bring the system up or down depending on the value set by the manager. It is this mechanism that the Avaya SNMP implementation uses to control MPS systems through the Periphonics MIB. get-bulk-request Message A get-bulk-request message allows the network manager to efficiently poll for large blocks of data. A get-bulk-request option is available only when using SNMPv2c. To search the MIB-II system subtree for a particular set of data, the network manager issues a get-bulk-request on the variable: iso.org.dod.internet.mgmt.mib-2.system The agent returns all the variables on this subtree in one response. The network manager then determines if the necessary information is available and at what variable. get-response Message A get-response message is the generic reply sent by the agent to the network manager in response to any get-request, get-next-request, or set-request message. 12 Simple Network Management Protocol in the Avaya Media Processing Server Environment October 2014

inform-request Message Figure 1: Sample request-response interaction inform-request Message Available only when using SNMPv2c, the inform-request message is used for manager-to-manager communications. Figure 2: Sample inform-request interaction trap Message Trap messages are unsolicited messages sent by the agent to the network manager. Trap messages are generated in response to unexpected internal conditions that need attention. SNMP defines the trap message for this purpose. No formal mechanism exists in SNMPv1 for managers to request traps to be sent. Trap destinations are set automatically in the trapcfg.pl portion of the installation script (see SNMP Installation on page 16 and Defining Trap Destinations Automatically on page 17). If trap destinations are not automatically set during installation, the configuration file (snmpd.conf) must be edited to add, delete, or change the destination manager parameters (see Configuring snmpd.conf on page 29). Figure 3: Sample generation of trap Note: Manager requests are sent from a different port (port 161) than the one that receives the traps generated by the agent (port 162). October 2014 Simple Network Management Protocol in the Avaya Media Processing Server Environment 13

Introduction SNMP and MPS Integration Periphonics MIB The Periphonics MIB was created by Avaya to manage the MPS network. The Periphonics MIB is registered with the Internet Assigned Numbers Authority (IANA) and has the number 1357 assigned to it. The Periphonics MIB object identifier is iso.org.dod.internet.private.enterprises.periphonics (. 1.3.6.1.4.1.1357). The Periphonics MIB allows network managers to determine the status and have control of the following components: Voice Response Unit (VRU) systems telephony ports IVR applications external host interfaces digital telephony interfaces (T1 spans) In addition, the Avaya SNMP agent sends enterprise-specific traps when one of the following events occurs: system and component alarms user defined application alarms real time updates regarding component status. For more information on the Periphonics MIB, see Overview on page 78. MPS Manager and SNMP Integrations In a standard MPS system, the MPS Manager is configured on network nodes as the management application. It communicates directly with the MPS network to monitor and control network nodes through proprietary protocol. This means workstations that are not configured to run MPS Manager can not normally communicate with the MPS network and components. SNMP acts as a translator between management stations that are not configured for the MPS Manager and the MPS network. The Periphonics MIB offers the basis for items that can be monitored and controlled. For additional information, see SNMP Utilization on page 42. The following illustration offers a basic view of this comparison: 14 Simple Network Management Protocol in the Avaya Media Processing Server Environment October 2014

Understanding Components Understanding Components Components are software-driven elements of the MPS network that reside on nodes and provide functionality to the network. Nodes, in turn, provide the central point of control for its resident components. MPS components include, but are not limited to: MPS (enables phone lines to interact with applications to process calls) VAS (enables node to run ASE processes on behalf of an MPS component residing on another node) Speech Server (enables both large vocabulary and text-to-speech processing). Each component generates alarms specific to its own processes. SNMP also monitors the status of each component through the MIB. October 2014 Simple Network Management Protocol in the Avaya Media Processing Server Environment 15

Chapter 2: Installation and Configuration This chapter covers: 1. SNMP Installation 2. SNMP System Startup 3. MIB Files 4. Configuration Files 5. Environment Variables 6. Configuring snmpd.conf 7. Converting SNMP Configuration to Net-SNMP 8. Error Logging 9. Executables SNMP Installation Installation steps are outlined in the applicable guides for both the Solaris and Windows operating systems. This chapter covers related topics that should be used in conjunction with the Windows and Solaris installation guides. To verify installation on either system, use the perirev command. To verify that agents are responding, use the snmpwalk command. Refer to Verify Agents Response on page 19. Package Licensing This Avaya PERIsnmp package requires a license. See the Solaris and Windows installation guides for details on installing and configuring the license file and server. 16 Simple Network Management Protocol in the Avaya Media Processing Server Environment October 2014

Defining Trap Destinations Automatically Defining Trap Destinations Automatically Trap destinations are set automatically using the trapcfg.pl portion of the installation script (see Defining Trap Destinations on page 34 and the script examples below). This section outlines the procedures necessary to set trap destinations automatically in each operating system. In Solaris During the installation of the SNMP package, the user is prompted to automatically process trap destinations. Enter y to proceed with automated processing of trap destinations,? for more information, or q to quit the installation. To configure traps at a later time, select n. If configuration trap destinations during installation, enter the trap type (v1, v2 or i), the community name used in trap messages, and the IP address of any management station trap destinations. Configure traps during install [y,n,?,q] y Traps will be configured during postinstall phase... Enter SNMP trap type v1, v2, or inform [v1,v2,i]: v1 You have selected trap type: v1 Is this correct [y,n,?,q] y Enter a community name [periadmin]: periadmin You have entered the following community periadmin Is this correct [y,n,?,q] y Enter IP address(s) of Management Station(s) in a space separated list: 10.130.156.152 10.130.153.125 You have entered the following for IP addresses 10.130.156.152 10.130.153.125 Is this correct [y,n,?,q] y The responses are recorded and trap destinations are configured later in the installation process after all of the package files are installed. Note: Traps can be configured post-installation by either entering trapcfg.pl from a command line to run the script and configure traps automatically, or by manually editing the configuration file see Configuring snmpd.conf on page 29. October 2014 Simple Network Management Protocol in the Avaya Media Processing Server Environment 17

Installation and Configuration Note: IP addresses must be entered (i.e. nnn.nnn.nnn.nnn). Do not use a management station name in lieu of a numerical octet string IP address. An exception may be made if traps are sent to the local host. The name localhost may be used rather than the IP address, provided localhost is defined as 127.0.0.1 in the /etc/hosts file. Towards the end of the installation process the installer runs the trapcfg.pl script to configure trap destinations based on the information previously provided. Stopping all SNMP processes. Backing up /opt/vps/common/etc/snmp/snmpd.conf to /opt/vps/common/etc/snmp/snmpd.conf.bak Configure trap destination 10.130.156.152 trapsink has been configured for 10.130.156.152. Configure trap destination 10.130.153.125 trapsink has been configured for 10.130.153.125. Starting all SNMP processes. Starting PERIsnmp processes... Installation of <PERIsnmp> was successful. Once the information is processed for each SNMP agent IP address entered, the stations can receive traps generated from the node where the SNMP agents are located. In Windows After the installation reboot process and the logon are complete, you must start the trapcfg.pl portion of the installation manually in Windows, by typing trapcfg.pl at a command prompt. Enter the trap type (v1, v2 or i), the community name, and one or more management station IP addresses in a space separated list. The traps are then sent to these stations. The script automatically configures the required files (for additional information, see Defining Trap Destinations on page 34 ). Note: IP addresses must be entered (i.e. nnn.nnn.nnn.nnn). Do not use a management station name in lieu of a numerical octet string IP address. An exception may be made if traps are sent to the local host. The name localhost may be used rather than the IP address, provided localhost is defined as 127.0.0.1 in the %SYSTEMROOT%\System32\drivers\etc\hosts file. 18 Simple Network Management Protocol in the Avaya Media Processing Server Environment October 2014

Verify Agents Response After the trap configuration is completed, the window disappears. Management stations can be added as trap destinations at a later time. To do this automatically, simply enter trapcfg.pl at a command line to run the script, and then follow the above steps. This process can also be accomplished manually by editing the configuration file see Configuring snmpd.conf on page 29. Verify Agents Response Use the snmpwalk command to verify agent response. October 2014 Simple Network Management Protocol in the Avaya Media Processing Server Environment 19

Installation and Configuration Table 1: snmpwalk Command Example: $ snmpwalk localhost vrunetwork alrmlogmax.0 = INTEGER: 1024 alrmlognumber.0 = INTEGER: 136 vruipaddress.152 = IpAddress: 10.7.151.152 vrudescr.152 = STRING: vrulinecnt.152 = INTEGER: 192 vruspancnt.152 = INTEGER: 8 vruhostcnt.152 = INTEGER: 1 vruadminstate.152 = INTEGER: other(1) vrustate.152 = INTEGER: up(4)... Installation Upgrades The following conditions must be followed when upgrading from pre-5.4 SNMP releases or using Solaris 2.8 or higher. Solaris Upgrade The SNMP package conflicts with the Solaris SNMP agent found on systems running Solaris 2.8 or higher. Executing the following commands, in order, disables the Solaris SNMP agent: mv /etc/rc3.d/s76snmpdx /etc/rc3.d/old.s76snmpdx mv /etc/rc3.d/s77dmi /etc/rc3.d/old.s77dmi Caution: You must reboot your Solaris workstation subsequent to issuing these commands for the changes to take effect. SNMP System Startup Note: If an MPS component is added to an already running system, then you must stop SNMP and then restart it so that the system recognizes this new MPS component. 20 Simple Network Management Protocol in the Avaya Media Processing Server Environment October 2014

Solaris Systems Solaris Systems The script S19snmp.startup is located in the /etc/rc3.d subdirectory, and is responsible for starting/stopping the MPS master SNMP agent (snmpd) and the MPS-components subagent (vrsnmpd). To start the agents, use the command /etc/rc3.d/s19snmp.startup start To stop the agents, use the command /etc/rc3.d/s19snmp.startup stop Modify the snmp.sh file found in $MPSHOME/common/etc/snmp whenever changes to any of the command line options for snmpd or vrsnmpd are needed (see Command Line Options on page 29). Note: You should also edit the file snmp.csh in C shell found at $MPSHOME/common/etc/snmp/ snmp.csh. Windows Systems There are two methods of starting and stopping the SNMP agents on your Windows system. The Services window can be used to individually stop and start SNMP services. The services are the Avaya VPS/MPS SNMP Daemon (vrsnmpd.exe), the Net-SNMP Agent (snmpd.exe), and the SNMP Trap service (snmptrap.exe). Click the Start button on the taskbar, then go to Control Panel > Administrative Tools > Services. Double-click the Services icon to display the Services window. October 2014 Simple Network Management Protocol in the Avaya Media Processing Server Environment 21

Installation and Configuration By default, the SNMP services start automatically when you install the package. If you wish to stop the services at some point, manually, right-click over the service name and choose stop or start from the pull-down menu. To stop and start all SNMP processes at one time, use the snmpstop or snmpstart command from a command prompt. The command prompt returns when the directive is successfully executed. 22 Simple Network Management Protocol in the Avaya Media Processing Server Environment October 2014

MIB Files MIB Files The Periphonics MIB files are contained in $MPSHOME/common/etc/snmp. Currently, Avaya provides its MIB in both SMIv1 and SMIv2 formats. The following information defines these files, their contents, and their use: Periphonicsv1.mib and Periphonicsv2.mib Defines Avaya enterprise in SMIv1 or SMIv2 format. VRU_Networkv1.mib andvru_networkv2.mib Defines Avaya VRU Network in SMIv1 or SMIv2 format. Prior to loading the MIB into network management software, determine whether the software supports SMIv1 or SMIv2. If the software supports SMIv1, load the Periphonicsv1.mib file, followed by the VRU_Networkv1.mib file. Conversely, if the software supports SMIv2, load the Periphonicsv2.mib file, followed by the VRU_Networkv2.mib file. Caution: The order in which the MIB files are installed is mandatory. In addition, only one SMI version should be loaded and used at a time. October 2014 Simple Network Management Protocol in the Avaya Media Processing Server Environment 23

Installation and Configuration Configuration Files The SNMP configuration files are located in $MPSHOME/common/etc/snmp. The following information defines these files and their contents: snmp.conf Configuration file for applications built using the Net-SNMP libraries, having common settings for all SNMP applications. This file must be owned by root and have read permission for that owner only. This is accomplished by setting the root permission mode to 400. snmpd.conf This file is installed as a read-only file. In order for changes to take effect, deselect the read-only attribute to allow for writing. To do this, launch the Windows Explorer tool. Locate this file, place your cursor over it, and <RIGHT> click to display the file menu. Scroll down to Properties and click. Go to the bottom of the snmp.conf Properties window, click on the Readonly box to deselect it (no check mark), then click on APPLY then OK. Configuration file containing information for community strings, default MIB-II values, access rights, traps, and notifications. This file is used by the Net- SNMP Agent daemon. Refer to Configuring snmpd.conf on page 29. This file must be owned by root and have read permission for that owner only. This is accomplished by setting the root permission mode to 400. vrsnmpd.conf This file is installed as a read-only file. In order for changes to take effect, deselect the read-only attribute to allow for writing. To do this, launch the Windows Explorer tool. Locate this file, place your cursor over it, and <RIGHT> click to display the file menu. Scroll down to Properties and click. Go to the bottom of the snmpd.conf Properties window, click on the Readonly box to deselect it (no check mark), then click on APPLY then OK. Configuration file for the MPS-components subagent (vrsnmpd). It contains the parameters for the AgentX connection to the Net-SNMP daemon(snmpd). This file should not be modified. This file must be owned by root and have read permission for that owner only. This is accomplished by setting the root permission mode to 400. This file is installed as a read-only file. snmptrapd.conf Configuration file for the Net-SNMPD trap receiver daemon (snmptrapd). It contains community names recognized by the trap receiver. The trap 24 Simple Network Management Protocol in the Avaya Media Processing Server Environment October 2014

Environment Variables daemon will only process notifications (traps) carrying the community strings named in this file. This file must be owned by root and have read permission for that owner only. This is accomplished by setting the root permission mode to 400. This file is installed as a read-only file. snmp.sh Contains environment variables and command line options. For the newly entered information to take effect, you must source this file after installing the SNMP package for the first time, or after editing the file. Note: To source snmp.sh, run. $MPSHOME/common/etc/snmp/snmp.sh in a Bash shell. snmp.csh Contains environment variables and command line options. For the newly entered information to take effect, you must source this file after installing the SNMP package for the first time, or after editing the file. Note: To source snmp.csh, run source $MPSHOME/common/etc/snmp/ snmp.csh in a C shell. Environment Variables Editing Caution: The user should never edit the MIBDIRS, SNMPCONFPATH, and SNMP_PERISISTENT_DIR environment variables created when the PERIsnmp package is installed. October 2014 Simple Network Management Protocol in the Avaya Media Processing Server Environment 25

Installation and Configuration In Solaris These variables can be changed by editing the file $MPSHOME/common/etc/snmp/snmp.sh. However, you must have write permission to do so. Changes to the environment variables are seldom, if ever, necessary and should be done only at the advice of Avaya support personnel. Note: You should also edit the smnp.csh variables by editing the file$mpshome/common/etc/snmp/ snmp.csh in a C shell. If changing environment variables, identical changes to environment variables should be made to both snmp.sh and snmp.csh before the SNMP processes are restarted and the environment variable changes take effect. In Windows The environment variables can be changed by editing the lines in the System Properties window; however, you must have administrative privileges to perform these edits. To view a list of all system and user variables: 1. Open the Control Panel and double-click the System icon. 2. In the System window, click Advanced System Settings to open the System Properties window. 3. In the System Properties window, select the Advanced tab and click the Environment Variables button. 26 Simple Network Management Protocol in the Avaya Media Processing Server Environment October 2014

In Windows October 2014 Simple Network Management Protocol in the Avaya Media Processing Server Environment 27

Installation and Configuration To change the parameters of a variable, select the desired variable from the System Variables list. Click the Edit button to open the Edit System Variable window, then modify the value and click OK. Similarly, you can select other variables and edit them. When done editing variables, click OK in the Environment Variables window to save the environment changes. Master/Subagent Related MIBDIRS Specifies a colon separated list of directories to search for MIB definitions in ASN.1 text files. This overrides (or augments) the default directory hardcoded into the Net-SNMP library. On Windows, the paths in the list are separated by semicolons. This should be set to $MPSHOME/ common/etc/snmp:$mpshome/perisnmp/mibs. SNMPCONFPATH Specifies a colon-separated list of directories to search for the configuration files, specifically snmp.conf, snmpd.conf, vrsnmpd.conf, and snmptrapd.conf. On Windows the paths in the list are separated by semicolons. This should be set to $MPSHOME/common/etc/snmp. SNMP_PERSISTENT_DIR 28 Simple Network Management Protocol in the Avaya Media Processing Server Environment October 2014

Command Line Options The path location where Net-SNMP applications cache persistent data used to facilitate repeated access to MIB data. This variable should be set to $MPSHOME/PERIsnmp/misc. Command Line Options In Solaris The following command line options are set by editing the file $MPSHOME/common/etc/snmp/ snmp.sh. Note: You can also edit the file smnp.csh in a C shell. SNMPD_CMDLINEARGS Command line arguments for snmpd VRSNMPD_CMDLINEARGS Command line arguments for vrsnmpd Note: If environment variables are edited, enclose the arguments within double quotes ( arguments ). In Windows To set options for any of the SNMP agents, use the Start Up Parameters field at the bottom of the Control Panel Services window. You must have administrative privileges and stop the service prior to entering the options as startup parameters. Restart the service for these choices take effect. The following services affect the corresponding SNMP agents: Net-SNMP Agent (snmpd.exe) Avaya VPS/MPS SNMP Daemon (vrsnmpd.exe) For further information on accessing and using the Services window, see Windows Systems on page 21. Configuring snmpd.conf Most customers can use the snmpd.conf file as shipped. The following sections describe how to customize SNMP daemon configuration in the snmpd.conf file when necessary. October 2014 Simple Network Management Protocol in the Avaya Media Processing Server Environment 29

Installation and Configuration Configuring Trap Destinations If the trapcfg.pl portion of the installation script is not used during installation of the PERIsnmp package, trapcfg.pl can be run from the command line, or snmpd.conf can be manually edited to configure trap destinations. To configure trap destinations by editing the snmpd.conf file, modify the Trap Destinations section, adding or removing trapsink, trap2sink, or informsink fields as required (see Defining Trap Destinations on page 34). Alternatively, users may execute the trapcfg.pl script (see SNMP Installation on page 16). The script can only be used to add trap destinations. If trap receivers are to be removed, the snmpd.conf file must be edited in a text editor such as vi on Solaris or notepad on Windows. Modifying Security Access Rights To modify security access rights, edit the snmpd.conf, default MIB-II values, or master agent performance parameters. Caution: The snmpd.conf file must be edited when the master agent is not running. Stop the master agent, use any text editor to modify the fields and then restart the agent after the editing is done. For additional information on starting and stopping the agents, see SNMP System Startup on page 20. Default MIB-II Values In the System Information Setup section of snmpd.conf, the MIB-II object values sysdescr, syscontact, sysname, and syslocation may be changed to suit individual site preferences. To customize object values, change the strings next to the applicable keywords, defined as follows: sysname sysdescr syscontact syslocation Contains the fully-qualified domain name. The initial value, -, means this information is not initialized and not available to network managers through SNMP. Contains a textual description of the system. Contains the name of a contact person or entity and how they may be contacted. Contains the physical location of the node where SNMP is installed. 30 Simple Network Management Protocol in the Avaya Media Processing Server Environment October 2014

Security Access Rights By default, Avaya SNMP package is shipped with the following values: sysname - sysdescr Avaya Inc. MPS Network syscontact Avaya - 1-800-242-2121 syslocation TBD Do not modify the sysobjectid (1.3.6.1.4.1.1357) and sysservices (72) entries in this section. The initial values for these settings must be preserved. Security Access Rights This section describes how the SNMP agent is configured to establish views (subtrees) within the SNMP object space and to restrict rights of different user communities to access views. One or more principles (communities) are assigned security names, security names are aggregated into security groups, views are defined, and then the rights of security groups to access view are configured. Assigning a Security Name to a Community This section specifies the configuration of security names. A security name links a community with a range of network IP addresses (sources) from which access will be allowed for that community. Add or delete mapping by adding or deleting the respective com2sec tags in snmpd.conf. By default, the Avaya SNMP agents are configured with the following security names: Public Periadmin Periuser Maps the public community to any network address. Maps the periadmin community to any network address. Maps the periuser community to any network address. Security names are configured with the tag com2sec followed by the fields: name source community Text label used to reference the community-to-source mapping. Can be a hostname, a subnet, or the word default for any source. A subnet can be specified as IP/MASK (192.168.1.0/255.255.255.0) or IP/BITS (192.168.2.0/24). The first source/ community combination that matches an incoming packet is selected. October 2014 Simple Network Management Protocol in the Avaya Media Processing Server Environment 31

Installation and Configuration This is a community string as it appears in an incoming SNMP request. For example, the default community strings public, periadmin, and periuser have the following security name entries in the snmpd.conf file: com2sec Public default public com2sec Periadmin default periadmin com2sec Periuser default periuser Defining Security Groups This section specifies the configuration of security groups. Each security group maps one or more security names into a security model. Security model options are v1 (for SNMP v1) or v2 (for SNMP v2). The default Avaya SNMP agent configuration uses security groups matching the security names: Anyone Periadmin Periuser Group including the Public security name. Group including the Periadmin security name. Group including the Periuser security name. Security names are configured with the tag group followed by the fields: name model security-name Text label used to reference the security group. The security model to use with this group, v1, or v2c. This is a previously defined security name from a com2sec command. For example, the default security names (Public, Periadmin and Periuser) are mapped one-to-one to security group names in the snmpd.conf file: group Anyone v1 Public group Anyone v2c Public group Periadmin v1 Periadmin group Periadmin v2c Periadmin group Periuser v1 Periuser group Periuser v2c Periuser 32 Simple Network Management Protocol in the Avaya Media Processing Server Environment October 2014

Defining View Subtrees Defining View Subtrees A view sub-tree defines object instances included in or excluded from a particular party of users. Add or delete View subtrees by adding or deleting the respective view tag. By default, Avaya SNMP agents are configured with the following view subtrees: Public includes 0.0 and iso subtrees. Network includes mib_2, snmptrap, and snmptraps subtrees. Periphonics includes 0.0 and iso subtrees. The view subtrees format consists of the tag view followed by the fields: name type subtree Textual name for the view, it may be defined to include or exclude many subtrees by having multiple view tags use the same text string for the view name. Type is either included or excluded. Subtrees are assumed excluded unless otherwise included. The excluded option is therefore used when a portion of an included subtree needs to be excluded. The object identifier, numeric or symbolic, of the root of the subtree to be included or excluded from the view. For example, the default views Public, Network, and Periphonics have the following entries in the snmpd.conf file: view Public included iso view Public included 0.0 view Network included mib_2 view Network included snmptrap view Network included snmptraps view Periphonics included iso view Periphonics included 0.0 Configuring Group Access Rights This section describes how to permit groups to have their associated access rights. Add or delete group and access rights by adding or deleting the respective access tag. By default, Avaya SNMP agents are configured with the following access rights: Anyone SNMPv1/SNMPv2c read-only access to Public view. Periuser SNMPv1/SNMPv2c read-only access to Periphonics view. October 2014 Simple Network Management Protocol in the Avaya Media Processing Server Environment 33

Installation and Configuration Periadmin SNMPv1/SNMPv2c read-write access to Periphonics view. The access rights format consists of the tag access followed by the fields: group context Textual name for the group associated with these access rights, taken from a previous group entry. See Defining Security Groups on page 32. Context is not supported, use double quotes ( ). security model level prefix read write notify The security model to use with this access can be any, v1 or v2c. To default to the security model from group command, use any. See Defining Security Groups on page 32. Security authorization level, must be noauth. The context matching rule, not supported, must be exact. The view allowed read access. The view allowed write access. The inform/trap view, not ly used, enter the word none. For example, the default access rights groups Anyone, Periuser, and Periadmin have the following entries in the snmpd.conf file: Access Anyone any noauth exact Public none none access Periuser any noauth exact Periphonics none none access Periadmin any noauth exact Periphonics Periphonics none Defining Trap Destinations This section explains the configuration of network destinations to receive notifications. The MPS SNMP agent can generate notifications as SNMPv1 traps, SNMPv2 traps, or SNMPv2 informrequest notifications (informs). Destinations that receive notifications can be added or deleted by adding or deleting trapsink, trap2sink, or informsink tags for the three notification types, respectively. The default configuration includes localhost as a destination for SNMPv1 traps. If desired, destinations are added after the PERIsnmp package is installed. The trapcfg.pl script can be used to 34 Simple Network Management Protocol in the Avaya Media Processing Server Environment October 2014

Defining the Default Trap Community add destinations for the first time. The snmpd.conf file must be edited manually to remove or change a trap destination. The notification configuration uses one of three tags: trapsink trap2sink informsink A destination for SNMPv1 traps. A destination for SNMPv2 traps. A destination for SNMPv2 informs. The configuration of a destination consists of one of the three tags followed by these fields: host An IP address where the notifications will be sent (i.e. 10.7.200.12), or localhost if the destination is the SNMP agent host itself and localhost is defined as the loopback address in /etc/hosts. community (optional) A community string that will be used in the community field of notification PDUs sent to this destination. If this is not provided the community will be the default community. See Defining the Default Trap Community on page 35. portnum (optional, deprecated) Port 162 is used for notifications. A port number can placed at the end of the line, but this argument is deprecated and will be ignored. For example, these lines configure a destination of each type using the community string periadmin: trapsink localhost periadmin trap2sink 10.7.200.35 periadmin informsink 10.130.156.152 periadmin The same destination should not be used with multiple notification types, for example: trapsink localhost periadmin trap2sink localhost periadmin This would send multiple copies of each trap to same trap receiver, and could negatively impact system performance. Defining the Default Trap Community This section explains the configuration of the default trap community. The default trap community specifies the trap community of any trap destination without the optional community argument on a trapsink, trap2sink or informsink tag line (See Defining Trap Destinations on page 34). The default October 2014 Simple Network Management Protocol in the Avaya Media Processing Server Environment 35

Installation and Configuration community should be set before any destinations are configured. Once set, the default community applies to trapsink, trap2sink and informsink tags that follow. If the default trap community is then set to another community, the most recently configured default community that appears before a trapsink, trap2sink or inform tag destination in the snmpd.conf file applies. The default trap community configuration uses trapcommunity tag with the community argument: community A textual name for the community, used in the community field of notification PDUs. For example, these lines demonstrate how to change the default community and configure destinations to use each default community: trapcommunity periadmin trapsink localhost trap2sink 10.7.200.20 trapcommunity public trapsink 10.7.150.12 informsink 10.7.200.35 informsink 10.130.156.152 periadmin In the examples above, destinations localhost, 10.7.200.20, 10.130.156.152 will receive notifcations with community string periadmin, and destinations 10.7.150.12 and 10.7.200.35 will receive notifications with community string public. Converting SNMP configuration to Net-SNMP The following sections describe how to convert the SNMP master agent configuration to Net-SNMP on systems that were upgraded to the Net-SNMP-based PERIsnmp package by the application of patches. For more information, see SNMP Protocol Stack Replacement on page 6. The default configuration files that come with the Net-SNMP patches do not need to be modified unless there were trap destinations configured in the snmpd.cnf file prior to the patches being applied, and/or the default group access rights for the public, periadmin, and periuser communities were modified. If that is the case, constructs configured in snmpd.cnf ($MPSHOME/common/etc/ snmp/snmpd.cnf) before the change to Net-SNMP must be converted to corresponding constructs in the Net-SNMP master agent configuration file ($MPSHOME/common/etc/snmp/snmpd.conf). Converting community strings/group associations A community string is associated with a security name for the community in snmpd.cnf using the snmpcommunityentry tag, as follows: snmpcommunityentry t001 mycommunity mycommunity localsnmpid - - nonvolatile 36 Simple Network Management Protocol in the Avaya Media Processing Server Environment October 2014

Converting View Subtrees The community name which matches the community string (mycommunity) is then associated with a security model (snmpv1) and security group name (MyGroup), using the vacmsecuritytogroupentry tag: vacmsecuritytogroupentry snmpv1 mycommunity MyGroup nonvolatile The corresponding configuration is performed in snmpd.conf with the com2sec and group tags. The security name from the com2sec tag (MyCommunity) is used as the last argument in the group tag, and the security model (snmpv1) is changed simply to v1: com2sec MyCommunity default mycommunity group MyGroup v1 MyCommunity Converting View Subtrees A user-defined view with two sub-trees is configured in snmpd.cnf using vacmviewtreefamilyentry tags, as follows: vacmviewtreefamilyentry MyView iso - included nonvolatile vacmviewtreefamilyentry MyVoew 0.0 - included nonvolatile The view name and view subtree arguments are what need to be preserved in the conversion to Net-SNMP. To create the same view in snmpd.conf, use two view tags, preserving the view name (MyView) and sub-tree arguments (iso and 0.0): view MyView included iso view MyView included 0.0 Converting Group Access Rights Access rights for a security group are assigned using the vacmaccessentry tag in snmpd.cnf: vacmaccessentry MyGroup - snmpv1 noauthnopriv exact MyView - MyView nonvolatile The corresponding configuration is performed in snmpd.conf with the access tag. The group name (MyGroup) and view names are carried forward from previous group and view tags. The protocol type is inherited from the group tag, so any can be used as the access tag. In this example the group MyGroup is given read access to view MyView, but not given write access: access MyGroup any noauth exact MyView none none October 2014 Simple Network Management Protocol in the Avaya Media Processing Server Environment 37

Installation and Configuration Converting Trap Destinations In snmpd.cnf, several tags used to configure trap destinations, snmpnotifyentry, snmptargetaddrentry, snmptargetparamsentry, and snmpnotifyfilterprofileentry tags, to name a few. These tags specify a number of parameters (such as inform response timeout, number of inform retries, target address domain, and trap filters) that are not configurable in the Net-SNMP implementation. In the Net-SNMP configuration, only the trap type (security model), trap community string, and trap destination IP address are configurable. For simplicity, this example shows only the relevant tags from snmpd.cnf, without discussing related snmpd.cnf tags that have no analogs in Net-SNMP configuration. Relevant tags for a single trap destination in snmpd.cnf are: snmpnotifyentry Traps TrapTag trap nonvolatile snmpcommunityentry t003 public public localsnmpid - - nonvolatile snmptargetaddrentry localhostv1 snmpudpdomain 127.0.0.1:0 100 3 TrapTag \ v1exampleparams nonvolatile 255.255.255.255:0 2048 snmptargetparamsentry v1exampleparams 0 snmpv1 public noauthnopriv \ nonvolatile The snmptargetaddrentry and snmptargetparamsentry tags are linked by their snmptargetparamsname arguments (v1examplparams). The IP address from the snmptargetaddrentry (127.0.0.1) and the snmptargetparamssecuritymodel argument from the snmptargetparamsentry (snmpv1) form two of the three arguments needed to define a Net-SNMP trap destination. The third argument is the trap community string used in the trap or inform PDU. The community string comes from the snmpcommunityentry tag with same snmpcommunitysecurityname as the snmptargetparamsentry (public). The community string is the snmpcommunityname (second) argument from the snmpcommunityentry, not the snmpcommunitysecurityname (third) argument, which in the typical snmpd.cnf file, and this example, is also public. To create the same trap destination in snmpd.conf, use the trapsink tag, with the same IP address and community string: trapsink 127.0.0.1 public If the security model is snmpv2 in the snmptargetparamsentry, the tag used in snmpd.conf should be trap2sink intead of trapsink: trap2sink 127.0.0.1 public If the snmpnotifytype is inform (not trap) in the snmpnotify entry with the same snmpnotifytag as the snmptargetaddrentry (traptag), the tag used in snmpd.conf should be informsink instead of trapsink. informsink 127.0.0.1 public 38 Simple Network Management Protocol in the Avaya Media Processing Server Environment October 2014

Error Logging Error Logging The error log files are located in $MPSHOME/common/log, and can be read with any text-based application or command. These log files are identified as follows: File Name Logs Errors for the Whose Executable is On Windows On Solaris vrsnmpd.log MPS components subagent vrsnmpd.exe vrsnmpd snmpd.log Net-SNMP (master agent) snmpd.exe snmpd You should also check /var/admin for logged error messages (specifically with respect to licensing problems). Executables The following executables are integral components of your SNMP package and are responsible for its functionality. On Solaris systems, these files are located in $MPSHOME/PERIsnmp/bin; on Windows systems, they are located in %MPSHOME%\bin. Agents Note: In the following listing, Windows agents are identified as those appended with the.exe extension. snmpd/ snmpd.exe SNMP master agent. This agent is responsible for authenticating formatting, security, access, and ownership parameters of requests, replies, and notifications. Acts as an intermediary between the management station and the subagents. This agent also provides the information for the MIB-II subtree. vrsnmpd /vrsnmpd.exe MPS components subagent for Avaya vrunetwork subtree. This agent acts as a proxy for the MPS network, using data in the Periphonics MIB to construct replies to queries. It also sends requests to and receives replies from resource daemons outside the SNMP agents when requested data is not available internally. October 2014 Simple Network Management Protocol in the Avaya Media Processing Server Environment 39

Installation and Configuration SNMP Command Line Utilities For examples of command line utilities in use, see SNMP Applied on page 47. snmpbulkget Gets as many MIB variables as possible in one request. snmpwalk Gets the MIB variables in the specified MIB subtree. snmpgetnext Gets the MIB variables that are lexicographically next after the specified MIB variables. snmpget Gets the specified MIB variables. snmptable Gets MIB variables from a specified table and displays it in tabular form. snmpset Sets one or more MIB variables to specified values. snmptrapd Displays the contents of the received trap. 40 Simple Network Management Protocol in the Avaya Media Processing Server Environment October 2014

Chapter 3: MPS Functions and Administration This chapter covers: 1. SNMP Utilization 2. MIB Variables 3. Instance Identification 4. SNMP Applied 5. The MIB Applied Overview This chapter discusses functions (primarily administrative and maintenance) that are controlled and monitored using SNMP in the MPS environment. This chapter refers to Periphonics MIB variables that are: monitor-only; both monitored and controlled; and indexes to tables within the MIB. In addition, notifications generated by the agent and sent to the manager for disposition are also discussed. For a detailed description of each variable and its associated data, see Overview on page 78. October 2014 Simple Network Management Protocol in the Avaya Media Processing Server Environment 41

MPS Functions and Administration SNMP Utilization Communication SNMP uses five types of messages for processing information: 1. Get-request 2. Get-next-request 3. Set-request 4. Get-response 5. Trap These messages are exchanged between the manager and the agent. Three messages getrequest, get-next-request, and set-request are sent directly from the manager to the agent. The remaining two get-response and the trap are sent from the agent to the manager. The "get-" and "set-" messages are simply request-reply protocols. The trap is initiated directly by the agent and sent to the manager's station. SNMPv2c includes a get-bulk request message that is sent from the manager to the agent. For additional information on these messages, see Protocol on page 10. For details on changing destinations for traps, see Configuring snmpd.conf on page 29. The Avaya SNMP product also contains a group of command line utilities that bundle many functions into small, self-contained programs, allowing the user to quickly manipulate and retrieve data. Using these utilities results in the generation of a Protocol Data Unit (PDU). These utilities can be broken down into three main areas: "get-", "set-" and trap designations. It is these utilities that the SNMP manager uses when querying or posting variables within the MIB. For a further definition of each command line utility, see SNMP Command Line Utilities on page 40. System Architecture Note: In the following discussion, Windows agents are identified as those appended with the.exe extension. When the network management station issues an SNMP request, it is sent to the Net-SNMP Agent (also known as master agent, snmpd/snmpd.exe). The master agent then confirms that the request is formatted properly and contains the proper security and community strings. If the data is not accurate, the agent returns a response to the manager with an appropriate message indicating the problem. If the request is properly configured, the agent forwards the request to the applicable subagents. 42 Simple Network Management Protocol in the Avaya Media Processing Server Environment October 2014

MIB Variables For MIB-II items, the master agent handles the request itself and returns a response. For information concerning the MPS system, the master agent forwards the request on to the MPScomponents subagent vrsnmpd/vrsnmpd.exe. The MPS subagent then acts as a proxy for the MPS network. The MPS subagent uses the data in the Periphonics MIB to formulate a reply. The information from the MPS subagent travels the reverse route from the subagent to the master agent, and ultimately back to the management station that originally issued the request. Traps travel in the same manner along this return path changes in status in the MPS are monitored by the subagent vrsnmpd/vrsnmpd.exe. The subagent formulates the appropriate data and issues it to the master agent. The master agent builds the trap and then passes it on to the designated management station. The graphic below illustrates the context of the MPS management architecture. MIB Variables Access Many variables in the Periphonics MIB database contain access information that stipulate the characteristics of querying and control. These levels of access are defined as follows: read-write - indicates variable can be both read and written to by the manager read-only - indicates variable can only be read by the manager accessible-for-notify - indicates variable can only appear in notification not-accessible - indicates variable can not be directly read or written to. October 2014 Simple Network Management Protocol in the Avaya Media Processing Server Environment 43

MPS Functions and Administration If a request is made on a variable for which there is no access, an error message is generated and returned to the manager. If the manager attempts to set a value on a variable which has read-only access, an error message is also returned. Several variables with not-accessible status are used as indexes to tables in this MIB. Status The status of MIB objects is usually, meaning the objects are supported by the SNMP product. Objects with a deprecated label still exist in MPS; however, they are no longer supported by the SNMP product. The following table lists deprecated objects, as well as the objects that supersede them. For a full listing of all MIB objects and their states, see Overview on page 78. Deprecated Object and OID Replaced by this Object and OID vrunetworkmibcompliance.1.3.6.1.4.1.1357.1.1.1. vrunetworkmibcomplianceby Component. 1.3.6.1.4.1.1357.1.1.1.2 vrunetworkmibcomplianceby Component. 1.3.6.1.4.1.1357.1.1.1.2 vrunetworkmibcomplianceby Component2. 1.3.6.1.4.1.1357.1.1.1.3 vrunotificationsgroup.1.3.6.1.4.1.1357.1.1.2.1 componentnotificationsgroup. 1.3.6.1.4.1.1357.1.1.2.8 componentnotificationsgroup. 1.3.6.1.4.1.1357.1.1.2.8 componentnotificationsgroup2. 1.3.6.1.4.1.1357.1.1.2.10 vrueventsgroup.1.3.6.1.4.1.1357.1.1.2.2 componenteventsgroup.1.3.6.1.4.1.1357.1.1.2.9 componenteventsgroup.1.3.6.1.4.1.1357.1.1.2.9 componenteventsgroup2.1.3.6.1.4.1.1357.1.1.2.11 notifyalarm.1.3.6.1.4.1.1357.1.2.2.1 notifyalarmbycomponent.1.3.6.1.4.1.1357.1.2.2.9 notifyalarmbycomponent.1.3.6.1.4.1.1357.1.2.2.9 notifyalarmbycomponentex. 1.3.6.1.4.1.1357.1.2.2.10 notifyvrustatechg.1.3.6.1.4.1.1357.1.2.2.2 notifycomponentstatechg.1.3.6.1.4.1.1357.1.2.2.8 alrmlogvruid.1.3.6.1.4.1.1357.1.2.3.6.1.4 alrmlogcomponentid.1.3.6.1.4.1.1357.1.2.3.6.1.11 Types The Periphonics MIB has two -type entries: notification-type and object-type. The notification-type generates traps in response to an event. These traps are forwarded to the manager. While this entry cannot be directly controlled by the manager, traps can alert the user to an instance that needs further attention through other means. 44 Simple Network Management Protocol in the Avaya Media Processing Server Environment October 2014

Instance Identification The object-type is accessible to the manager within the constraints of the assigned values, as discussed in Access on page 43. The manager uses object-type variables to control or monitor the status of the MPS systems. Instance Identification Direct Referencing There are variables in the Periphonics MIB that can be queried directly (that is, an instance does not have to be specified). A command can be issued on the variable and its value returned by simply appending a.0 to the object identifier (OID). These are termed scalar requests because no further instance identification is required (see Getting a Value on page 47 for an example of this type of transaction). Table Referencing Object values are sometimes maintained in tabular form in the MIB, particularly when there may be multiple instances of a managed entity with multiple attributes. Tables can be built in the MIB by sequencing variables that act as indexes into the rows and columns of data (Periphonics MIB Reference on page 78). The variables that specify an instance are the row indexes, and are not directly accessible. Instead, they act as a reference to the set (or row) of attributes for one instance. The attributes, individually, are the table columns. The combination of the variable and its index forms the object identifier (OID) for that row. The tables are built in much the same fashion as a spreadsheet. When the Avaya MPS-components subagent starts up, it uses proprietary APIs to determine the components present on the system and the makeup of those components. It uses this topological configuration to assign the data to and structure the tables. Values specific to a particular index are maintained in that row of the table. Since tables are built lexicographically (entries ordered by their object identifiers), the snmpgetnext command allows the manager to search through tables to find the desired data. To iterate through a table to find specific information, start with the object name that defines the table (no instance is applicable in these cases) and use the snmpgetnext command. Repeat the snmpgetnext command and substitute the previous reply's object and instance until you obtain the desired information. When the object name changes, you have reached the end of the table you are accessing. October 2014 Simple Network Management Protocol in the Avaya Media Processing Server Environment 45

MPS Functions and Administration Note: If a table is empty (contains no data), the OID returned on a get-next request is that of the next lexicographical table variable that does contain data (even though that returned value may not seem to apply to your original snmpgetnext command). The snmpwalk command extracts all the data in the specified subtree at one time. The snmptable command displays blocks of data extracted from tables. In SNMPv2c, the snmpbulkget command can obtain large amounts of information by replicating several snmpwalk requests at one time. If more than one variable is used to index the table, these instances are appended one after the other, separated by periods. For example, the vrutable is built from the following sequence of variables: vruid, vruipaddress, vrudescr, vrulinecnt, vruspancnt, vruhostcnt, vruadminstate, vrustate, and vrustatelastchange. The first variable is a unique value that is used as an index into the table, and the remaining variables are values associated with this index. Note that the vrudescr variable has not been implemented at the present time. Conceptually then, this table might look like this: Table 2: vrutable vruid vruip Address 1 192.84.160.2 27 2 192.85.160.2 28 vru Desc vru Line Cnt vru Span Cnt vru Host Cnt vru Admin State vru State vru State Last Change VRU1 48 2 1 other(1) up(4) 07 cd 05 08 0c 14 07 00 VRU2 48 4 1 other(1) up(4) 07 cd 05 08 0c 14 08 00 An snmpgetnext request on this table would return an OID including the instance in the first column of the table. Depending on the variable queried, its value for that line is also returned. For example, if the manager sends an snmpgetnext nodename vrutable request, the agent responds with vruipaddress.1 = 192.84.160.227, where.1 is the instance which identifies the VRU the information is related to. If the manager then sends an snmpgetnext nodename vruipaddress.1 request, the agent responds with vruipaddress.2 = 192.85.160.228. If the manager issues snmpgetnext nodename vruipaddress.2, the agent sends a reply of vrudesc.1 = VRU1, and so on. The syntax shown is the default, where nodename is the actual name of your management station, and the vrudesc variable is not used. This example serves to show how indexing and tables work within SNMP. The manager can continue polling through the table until the desired results are obtained. If the exact index into the table is known, the manager can use it to directly query the variable in question (i.e., snmpget nodename vrulinecnt.2 ==> vrulinecnt.2 = 48). For a further applied example of indexing, see Setting a Value on page 48. 46 Simple Network Management Protocol in the Avaya Media Processing Server Environment October 2014

SNMP Applied SNMP Applied Getting a Value With these criteria in mind, the user can manage the MPS using SNMP. The user structures a basic command line request as follows: snmpget -v [ 1 2c ] -c <community> <hostname> <object(s)> To query a single MIB variable, enter the command snmpget. Next, stipulate the version of SNMP that you are using (-v 1 or -v 2c). The community is set to periuser (-c periuser). The hostname argument is the exact name of the host where the agent is located. The last argument is the object being queried. The snmpget command generates a get-request PDU containing all the OIDs stipulated for that line. The system sends the get-request PDU to the agent on the hostname entry. The management station waits for a response from the agent. The agent sends a get-response PDU containing the values of the variable queried, along with the OID data originally issued on the command line. This result is then outputted at the command line on the manager's station. If no response is received from the agent within a specified time, the command times out. At this point, if an answer is still desired, reissue the request. For example, to know the maximum number of alarms that can be logged into the alarm log table at one time, use the command line utilities to enter the following at the management station: snmpget -v 1 -c periuser hostname alrmlogmax.0 The manager receives the following command line output as a result of the agent generating a getresponse PDU: alrmlogmax.0 = INTEGER: 1024 The numerical value shown above is the default value. Also, remember to include the instance.0 with all scalar requests. However, if a user makes a request on a table with a known index, the user can enter the known table index in place of the zero. By default, the SNMP package is set up so that command line requests will use SNMP Version 1, and the community string 'periuser'. Commands can be issued without the -v and -c arguments: snmpget hostname alrmlogmax.0 The default SNMP version and community string are set in the $SNMPCONFPATH/snmp.conf file, by the defversion and defcommunity configuration entries: defversion 1 defcommunity periuser If the defversion and/or defcommunity lines are omitted from the snmp.conf file, or if one wishes to change the SNMP version or community string in an SNMP request, then the -v and/or -c argument(s) must be provided on the command line. October 2014 Simple Network Management Protocol in the Avaya Media Processing Server Environment 47

MPS Functions and Administration Setting a Value Setting a value in a variable is similarly executed. For instance, to start an application on a particular line, enter the following command line at the prompt: snmpset -v 1 -c periadmin localhost lineappadminstate.152.1 i softterm The manager receives the following result: lineappadminstate.152.1 = INTEGER: softterm(3) The above example specifies that SNMPv1 (you can also use -v 2c) is used to address a single MIB variable. The entry hostname is the name of the host where the agent is located. The community is set to periadmin to allow for reading/writing permissions. The object to be set is listed next. In this case, the numerical representation appended to the variable (.2.1) dictates that line number one on MPS number two be addressed (because the variables linevruid and lineid act as indexes into the object linetable). The entry 'i startapp' indicates that the item that follows has an integer value, though for ease of use to the manager, named integer values as defined in the MIB ASN.1 definition file can be represented in a textual format. The integer indicates that the manager wishes to start an application on the indicated line and MPS. The agent sends a get-response PDU indicating the location and value of the variable that was set. This tells the manager that the execution to start an application on MPS 2, line 1 was successful. The defversion and defcommunity defaults apply to all command line requests; however, MPS SNMP variables are defined as read-only for the 'periuser' community. The -c periadmin argument is required for a set operation, and only the -v argument may be left off the command line: snmpset -c periadmin hostname lineappadminstate.2.1 i startapp Viewing Traps As stated previously (see trap Message on page 13), traps are unsolicited messages sent from the agent to the manager in the event of unexpected internal conditions within the MPS system. These traps can consist of SNMPv1-defined events as well as enterprise-specific events (see Protocol on page 10. Enterprise-specific traps are predefined, and include notifications of alarms generated by the MPS system (for definitions of these traps, see Events Group Notifications Subtree on page 50). The alarmd process must run on the MPS node in order for the SNMP agent to generate and forward the notifyalarmbycomponentex trap to the management station. Each node contains one alarmd daemon. To verify that the node is connected to the alarmd daemon, enter alarm at any command line to receive a response indicating that you are connected: <<< alarm: Connected to [alarmd#common.0,gen/pc105r@pc105r:1034] >>> To view traps, enter the following snmptrapd command at the command line of any management station designated to receive traps (for related information, see Configuring snmpd.conf on page 29): 48 Simple Network Management Protocol in the Avaya Media Processing Server Environment October 2014

Viewing Traps snmptrapd -Lo If more than one management station is configured to receive traps, each individual management station shows the traps generated by the nodes that include that particular management station during configuration. Note: No more than one snmptrapd process should be started per management station. For example, if node A, node B, and node C are all configured to receive traps, but node A also has the IP addresses for nodes B and C in its snmpd.conf file, then nodes B and C also receive traps generated by node A. To verify that both commands are working properly: Leave both the alarm and snmptrapd command windows open. Stop and start SRP on the node that you wish to check. Issue the commands: /etc/rc3.d/s20vps.startup stop and /etc/rc3.d/s20vps.startup start in order. Stop and start the Avaya MPS Service in the Control Panel Services window (for generalized information on stopping and starting services, see Windows Systems on page 21). You see alarms generated in the alarm window, followed immediately thereafter by traps generated in the snmptrapd window. The windows can then be closed, minimized, or left open. Alarms and traps continue to be generated no matter what the condition of the respective window. Note: Starting and stopping SRP can have other consequences. Be aware that running this test can affect overall system performance. All other predefined enterprise-specific traps are generated as they occur. For additional information regarding starting and stopping SRP and using System Services, consult the system operator's guide for the appropriate operating system. October 2014 Simple Network Management Protocol in the Avaya Media Processing Server Environment 49

MPS Functions and Administration The MIB Applied Subtrees There are several subtrees in the MIB that are used to monitor or control the MPS network. Each subtree contains variables particular to certain aspects of the network. This section discusses each subtree and any variables that are implemented and that fall into the monitor/control disposition. In addition, this section identifies variables used as indexes into tables. The OID for each variable is provided for further consideration. For a complete definition of the MIB, see Periphonics MIB Reference on page 78. Events Group Notifications Subtree The Events Group Notification subtree defines traps that are sent to network management stations. These traps are generated by the MPS agent directly and sent to the manager. As a result, the manager could, for example, write a script that runs when a trap is received (for example, notifyalarmbycomponentex causes a script to run that pages the network administrator). Variable OID Condition notifylineappstatechg.1.3.6.1.4.1.1357.1.2.2.3 This trap is forwarded when an application associated with a VRU line changes state. notifyspanstatechg.1.3.6.1.4.1.1357.1.2.2.4 This trap is forwarded when a VRU span changes state. notifyhoststatechg.1.3.6.1.4.1.1357.1.2.2.5 This trap is forwarded when a VRU host changes state. notifylustatechg.1.3.6.1.4.1.1357.1.2.2.6 This trap is forwarded when a VRU host LU changes state. notifytopologychg.1.3.6.1.4.1.1357.1.2.2.7 This trap is forwarded when a VRU network object topology status changes. notifycomponentstatechg.1.3.6.1.4.1.1357.1.2.2.8 This trap is forwarded when a network component changes state. notifyalarmbycomponentex.1.3.6.1.4.1.1357.1.2.2.10 This trap forwards alarms generated by an exceptional condition occurring in a component in the MPS network, and includes the IP address of the component generating the alarm. 50 Simple Network Management Protocol in the Avaya Media Processing Server Environment October 2014

Component Events Alarms Subtree Note: Although the objects notifyalarm, notifyalarmbycomponent, and notifyvrustatechg are still present in the MIB, each has a deprecated status and is no longer supported. Component Events Alarms Subtree This subtree defines the component alarms that are recorded (through the notifyalarmbycomponentex trap) and the number of alarms that are kept. The variables described (other than indexing variables) are all monitor status variables (read-only). Requests of the table in this subtree must include the instance identification provided by alrmlogidx. Caution: If the Avaya MPS-components subagent is stopped and restarted for any reason, the contents of the alrmlogtable is cleared. Note: The connection, or lack thereof, between the MPS resources subagent and alarmd affects the alarms actually recorded in the alrmlogtable. Variable OID Condition alrmlogmax.1.3.6.1.4.1.1357.1.2.3.4 Specifies the maximum number of alarms that may be logged into the alarm log table at one time. When this number is reached, the initial alarms are deleted as new ones are added. alrmlognumber.1.3.6.1.4.1.1357.1.2.3.5 The number of log entries. alrmlogidx.1.3.6.1.4.1.1357.1.2.3.6.1.1 Serves as an index into alrmlogtable, and is a number between 1 and alrmlognumber (inclusive). alrmlogseverity.1.3.6.1.4.1.1357.1.2.3.6.1.2 Integer describing how severe the alarm is. The higher the value, the higher the severity; a value of 0 indicates that no severity is assigned. alrmlogcode.1.3.6.1.4.1.1357.1.2.3.6.1.3 Code assigned to identify the alarm. alrmloglineid.1.3.6.1.4.1.1357.1.2.3.6.1.5 The phone line associated with the alarm; a value of 0 indicates no phone line. October 2014 Simple Network Management Protocol in the Avaya Media Processing Server Environment 51

MPS Functions and Administration Variable OID Condition alrmloghostid.1.3.6.1.4.1.1357.1.2.3.6.1.6 Identifies the host associated with the alarm; a value of 0 indicates no host association. alrmlogprocname.1.3.6.1.4.1.1357.1.2.3.6.1.7 The name of the process that generated the alarm. alrmlogmessage.1.3.6.1.4.1.1357.1.2.3.6.1.8 A textual message describing the alarm that occurred. alrmlogtime.1.3.6.1.4.1.1357.1.2.3.6.1.9 The time that the alarm was generated. alrmlogcomponenttype.1.3.6.1.4.1.1357.1.2.3.6.1.10 Component type that generated the alarm. alrmlogcomponentid.1.3.6.1.4.1.1357.1.2.3.6.1.11 Component identifier of the component that generated the alarm. alrmlogcomponentipaddre ss Note:.1.3.6.1.4.1.1357.1.2.3.6.1.12 IP address of the component that generated the alarm. Although the object alrmlogvruid is still present in the MIB, it has a status of deprecated and is no longer supported. Note: The component type name and its corresponding component type ID are determined by accessing the objects in the Component Type Table on page 57. VRU Subtree The VRU subtree defines the parameters of the VRU system. The variables can both monitor and control the VRU. Requests on the table in this subtree must include the instance identification provided by vruid. Variable OID Condition Index vruid.1.3.6.1.4.1.1357.1.3.1.1 The VRU number assigned to a particular VRU. This number is unique within the VRU network, and is used as an index into vrutable. Monitor vruipaddress.1.3.6.1.4.1.1357.1.3.1.2 VRU network IP address. vrulinecnt.1.3.6.1.4.1.1357.1.3.1.4 Number of physical phone lines on the system. 52 Simple Network Management Protocol in the Avaya Media Processing Server Environment October 2014

Line Subtree Variable OID Condition vruspancnt.1.3.6.1.4.1.1357.1.3.1.5 Number of spans on the system. Also indicates number of rows in the spantable for the VRU. vruhostcnt.1.3.6.1.4.1.1357.1.3.1.6 Number of hosts defined for the system. Also indicates number of rows in the hosttable for the VRU. vrustate.1.3.6.1.4.1.1357.1.3.1.8 The status of the VRU entity. vrustatelastchange.1.3.6.1.4.1.1357.1.3.1.9 Date and time the VRU entity last changed state. Control vruadminstate.1.3.6.1.4.1.1357.1.3.1.7 Allows the network manager to bring the VRU system up or down. Note: The objects vruid, vruipaddress, vrustate, and vrustatelastchange, though still supported, are similarly represented by the objects componentid, componentipaddress, componentstate, and componentstatelastchange, respectively, when the component is an MPS. Line Subtree The Line subtree defines the parameters of the lines on the system. The variables can both monitor and control the lines. Requests on the table in this subtree must include the instance identification provided by both linevruid and lineid. Variable OID Condition Indexes linevruid.1.3.6.1.4.1.1357.1.4.1.1 Identifies the VRU that the phone line is associated with. Serves as the initial index into linetable. lineid.1.3.6.1.4.1.1357.1.4.1.2 Identifies the line number of this phone line, and serves as the second index into linetable. Monitor linetype.1.3.6.1.4.1.1357.1.4.1.3 Specifies whether the line is a logical or physical phone line or whether this is unknown. A value of unknown indicates that the agent is unable to connect October 2014 Simple Network Management Protocol in the Avaya Media Processing Server Environment 53

MPS Functions and Administration Variable OID Condition to the VRU to determine the line type. lineprotocol.1.3.6.1.4.1.1357.1.4.1.4 A value which indicates the set of protocols the phone line supports, presented as a sum. linestate.1.3.6.1.4.1.1357.1.4.1.5 Current state of the line. A value of unknown indicates that the agent is unable to connect to the VRU to determine the line state. A logical line always has a value of unknown. lineappoverlay.1.3.6.1.4.1.1357.1.4.1.7 The name of the application linked to the line. lineappstate.1.3.6.1.4.1.1357.1.4.1.9 Current state of the application assigned to the logical line. lineappstatelastchange.1.3.6.1.4.1.1357.1.4.1.10 Date and time the application assigned to the line last changed state. lineappcfglastchange.1.3.6.1.4.1.1357.1.4.1.11 Date and time of last application configure or unconfigure on the line. Control lineappname.1.3.6.1.4.1.1357.1.4.1.6 The name of the application ly assigned to the line, returned by any response PDU on this object. This variable can only be set by setting lineappadminstate to assign and this object to the application name. lineappadminstate.1.3.6.1.4.1.1357.1.4.1.8 Allows the network manager to set the desired state of the application. Span Table Subtree The Span Table subtree defines the parameters of the spans on the system. The variables described (other than indexing variables) are all of monitor status variables (read-only). Requests on the table in this subtree must include the instance identification provided by both spanvruid and spanid. 54 Simple Network Management Protocol in the Avaya Media Processing Server Environment October 2014

Applications Subtree Variable OID Condition spanvruid.1.3.6.1.4.1.1357.1.5.1.1 Identifies the VRU associated with the span. Serves as the initial index into spantable. spanid.1.3.6.1.4.1.1357.1.5.1.2 Identifier of this span, and serves as the second index into spantable. spanlineidstart.1.3.6.1.4.1.1357.1.5.1.3 Line identification of the first line in the span. spanlinenumber.1.3.6.1.4.1.1357.1.5.1.4 Number of lines in the span. spanenabled.1.3.6.1.4.1.1357.1.5.1.5 Indicates whether span is enabled or disabled. spanstate.1.3.6.1.4.1.1357.1.5.1.6 Current state of the span. spanstatelastchange.1.3.6.1.4.1.1357.1.5.1.7 Date and time the span last changed state. Applications Subtree The Application subtree describes the applications associated with the VRU entity. Two variables are used for monitoring these conditions. Requests on the table in this subtree must include the instance identification provided by both appvruid and appname. Variable OID Condition appvruid.1.3.6.1.4.1.1357.1.6.1.1 VRU that the application is assigned to. Serves as the initial index into apptable. appname.1.3.6.1.4.1.1357.1.6.1.2 The name of an the application that can be assigned to the VRU. Serves as the second index into apptable. appoptions.1.3.6.1.4.1.1357.1.6.1.4 The options that are used during application startup. applinecnt.1.3.6.1.4.1.1357.1.6.1.5 The number of lines the application is ly assigned to. Applications Stats Subtree The Application Stats subtree describes the application statistic associated with an application. Two variables are used for monitoring only. Requests of the table in this subtree must include the instance identification provided by both appstatsvruid and appstatsname. October 2014 Simple Network Management Protocol in the Avaya Media Processing Server Environment 55

MPS Functions and Administration Variable OID Condition appstatsvruid.1.3.6.1.4.1.1357.1.7.1.1 Identifies the VRU associated with the application statistic. Serves as the initial index into appstatstable. appstatsname.1.3.6.1.4.1.1357.1.7.1.2 Terminology which identifies this application statistic. Serves as the second index into the appstatstable. appstatsvalue.1.3.6.1.4.1.1357.1.7.1.3 An application stats value, which is gathered in 15 minute intervals. appstatslastchange.1.3.6.1.4.1.1357.1.7.1.4 Date and time when the application stat was recorded. Host Subtree The Host subtree describes and defines the parameters of the host associated with the VRU entity. The variables can both monitor and control these parameters. Requests on the table in this subtree must include the instance identification provided by both hostvruid and hostid. Variable OID Condition Indexes hostvruid.1.3.6.1.4.1.1357.1.8.1.1 Identifies the VRU associated with the host. Serves as the initial index into hosttable. hostid.1.3.6.1.4.1.1357.1.8.1.2 Identifier of this host, and serves as the second index into hosttable. Monitor hostlucnt.1.3.6.1.4.1.1357.1.8.1.4 Number of LUs defined for the host. Also indicates the number of rows in the lutable for the host. hostprotocol.1.3.6.1.4.1.1357.1.8.1.5 Protocol used for host communication. hostmedia.1.3.6.1.4.1.1357.1.8.1.6 Media used for communicating with the host. hoststate.1.3.6.1.4.1.1357.1.8.1.9 Current state of the host. hoststatelastchange.1.3.6.1.4.1.1357.1.8.1.10 Date and time host last changed state. Control hostadminstate.1.3.6.1.4.1.1357.1.8.1.8 Allows the network manager to set the desired state of the host for 56 Simple Network Management Protocol in the Avaya Media Processing Server Environment October 2014

LU Subtree Variable OID Condition hardware based hosts only (when hostmedia= hardwarebased). LU Subtree The LU subtree describes and defines the parameters of the LU associated with the system. The variables described are all of monitor status variables (read-only). Requests of the table in this subtree must include the instance identification provided by the variables luvruid, luhostid, and luid. Variable OID Condition luvruid.1.3.6.1.4.1.1357.1.9.1.1 Identifies the VRU associated with the LU. Serves as the initial index into lutable. luhostid.1.3.6.1.4.1.1357.1.9.1.2 Identifies the host that the LU is associated with. Serves as the second index into lutable. luid.1.3.6.1.4.1.1357.1.9.1.3 Identifier of this LU, and serves as the subsequent index into lutable. lupoolname.1.3.6.1.4.1.1357.1.9.1.5 Pool name that the LU is assigned to. lustate.1.3.6.1.4.1.1357.1.9.1.6 Current state of the LU. lustatelastchange.1.3.6.1.4.1.1357.1.9.1.7 Date and time LU last changed state. Components Subtree This subtree contains two tables that describe and define the components and their presence on the MPS network. Component Type Table The Component Type Table defines all the known component types. Requests on the read-only object in this table must be made using the instance identification provided by the variable componenttypeid. Variable OID Condition componenttypeid.1.3.6.1.4.1.1357.1.10.1.1.1 Identifier for the component type. Acts as the index into componenttypetable. October 2014 Simple Network Management Protocol in the Avaya Media Processing Server Environment 57

MPS Functions and Administration Variable OID Condition componenttypename.1.3.6.1.4.1.1357.1.10.1.1.2 Common name of the component type. Component Table The Component Table defines and describes all the components on the system that the agent has identified. Requests of the read-only variables in this table must include the instance identification provided by the variables componenttype and componentid. Variable OID Condition componenttype.1.3.6.1.4.1.1357.1.10.3.1.1 Identifies the component type. Acts as the initial index into componenttable. componentid.1.3.6.1.4.1.1357.1.10.3.1.2 Identifier of the component, and the second index into componenttable. a componentipaddress.1.3.6.1.4.1.1357.1.10.3.1.3 IP address of the component. componentstate.1.3.6.1.4.1.1357.1.10.3.1.4 Current state of the component. componentstatelastchan ge Note:.1.3.6.1.4.1.1357.1.10.3.1.5 Date and time the component last changed state. To avoid possible problems, each component of a specific type on a particular network must be assigned a unique component ID. The objects componentid, componentipaddress, componentstate, and componentstatelastchange contains the same data as the objects vruid, vruipaddress, vrustate, and vrustatelastchange, respectively, when the component is an MPS. 58 Simple Network Management Protocol in the Avaya Media Processing Server Environment October 2014

Chapter 4: MPS Manager and SNMP Mappings This chapter covers: 1. Mappings Overview This chapter provides the SNMP manager a cross-reference to tools and functions available in MPS Manager similar to those used in the Periphonics MIB ( See Chapter 3 MPS Functions and Administration on page 41). This is not a learning guide or instructional tool for MPS Manager. The chapter is organized to correspond with MIB group order for ease of use by the MPS Manager and includes only those variables for which an analogous MPS Manager function exists. For definitions of individual MIB objects, refer to the applicable table in The MIB Applied on page 50. For a detailed view of this MIB, see Overview on page 78. For specific controls and functions beyond those discussed here, and a more detailed explanation and graphical representation of MPS Manager usage (including instructions on accessing tools and windows), refer to the Media Processing Server Manager Reference Manual. Mappings MIB-II While the intention of this chapter is to provide information particular to Avaya MPS products, there are a few items that fall within the parameters of the system portion of MIB-II that may be of interest to the user. These variables are used to describe in strictly textual form certain aspects of the MPS system. These variables are: sysdescr - describes the workstation in use; October 2014 Simple Network Management Protocol in the Avaya Media Processing Server Environment 59

MPS Manager and SNMP Mappings syslocation - indicates the physical location of the workstation; sysname - textual description of the MPS network; and syscontact - gives information pertaining to personal contact available with regard to the station. Enterprise MIB Events Group Notifications Subtree This group defines the traps sent to the network management station. Traps are analogous to alarms in the MPS Manager. As such, particular objects themselves are not directly supported by the MPS Manager, but there are certain indications in the MPS Manager that can be tied into the issuance of a trap. They are as follows: This MIB Object Is analogues to this representation notifyalarmbycomponentex a Alarm Icon Alarm Viewer notifycomponentstatechg b notifylineappstatechg c notifyspanstatechg d notifyhoststatechg e notifylustatechg f 1) MPS, Speech Server icons (change in color). 2) MPS icons (change in color). 3) Failure of graph to update, or beeping/ flashing graph icon. Application icon (change in color). Span state symbology (change of symbol). Host state symbology (change of symbol). VT state symbology (change in symbol). VTs in the MPS Manager are equivalent to LUs in MIB. 1) Tree In this MPS Manager tool 2) APPMAN 3) Line Status (also displayed in Tree). APPMAN (also displayed in Tree) Span Status (also displayed in Tree) Host Status Host Status (when indexed by VT) a. The alarms themselves are detailed and defined in the Component Events Alarms Subtree (see Component Events Alarms Subtree on page 61). 60 Simple Network Management Protocol in the Avaya Media Processing Server Environment October 2014

Component Events Alarms Subtree This MIB Object Is analogues to this representation In this MPS Manager tool b. Generated when a change in either vrustate (see vrustate on page 63) or componentstate (see componentstate on page 69) is detected. Both vrustate and componentstate contain the same data for MPSs. c. Generated when a change in lineappstate is detected (see lineappstate on page 64). d. Generated when a change in spanstate is detected (see spanstate on page 66). e. Generated when a change in hoststate is detected (see hoststate on page 68). f. Generated when a change in lustate is detected (see lustate on page 68). Component Events Alarms Subtree The Component Events Alarms subtree describes the aspects of component-generated alarms and the parameters for maintaining them in the database. The Periphonics MIB variables shown below are used to define the contents of the notifyalarmbycomponentex trap. Most of the Periphonics MIB variables in this group have comparable indications in the MPS Manager Alarm Viewer. The following illustration is a snapshot of the MPS Manager alarm viewer. In the upper half of the illustration, there is a list of alarms. In the lower half, the alarm detail for a single alarm from the summary is expanded: Using the illustration, compare the following MIB variables to their equivalent MPS Manager representations. alrmlogseverity: Indication of how severe an alarm is considered. There are three severity types - Info, Warning and Alarms. alrmlogcode: Individual code assigned to particular alarms. The example entry shows this as 12001. October 2014 Simple Network Management Protocol in the Avaya Media Processing Server Environment 61

MPS Manager and SNMP Mappings alrmloglineid: The phone line associated with the alarm. In the MIB, if no line is associated, the value is set to 0. In the MPS Manager illustration, the line identification in the alarm summaries and the expanded alarm text is 0. Note: Note that the line numbers in the MPS Manager are indicative of the logical line with which the physical line is associated. For additional information pertaining to this logical-to-physical line mapping, refer to the Avaya Media Processing Server Manager Reference Manual. alrmloghostid: Identifies the host associated with the alarm. The MIB has an assigned value of 0 for this variable if no host is related to the alarm. For the MPS Manager, the entry Host 1, for example, would indicate the host association. In the sample MPS Manager illustration above there is no host associated, so the alarm appears with host number zero (0). alrmlogprocname: The name of the process that generated the alarm. This is indicated in brackets in the example as <srp>. alrmlogmessage: A textual description of the alarm. In the MPS Manager, this is carried on the second and subsequent line of each entry made. alrmlogtime: The date and time that the alarm was generated. In the example illustrated, this is shown by the initial entry Thu Sep 18 11:11:24. alrmlogcomponenttype: Identifies the component that generated the alarm. The example above indicates that a MPS generated the alarm. Had another component generated the alarm, it would be identified at the same location. alrmlogcomponentid: Component identifier of the component that generated the alarm. In the example, this is the number 6 following MPS (the component type) in the entry MPS 6. All of these variables are also viewable in the Alarm Viewer. However, the Alarm Viewer window shows live alarms, which are added to the Alarm Log File as they are generated. VRU Subtree The VRU subtree defines the parameters of the VRU system. In the MPS Manager environment, this is represented by the MPS system. The MIB variables and their MPS Manager counterparts are as follows: vruid vrulinecnt This MIB Object Is analogous to this representation 1) Listed under MPS number. 2) Number after colon in MPS identification 1) Total sum of represented states. In this MPS Manager tool 1) vsh vhman 2) APPMAN, Line Status, Host Status, Alarm Filter, MPS Control Center, Span Status, Tree 1) Line Status Graph (with vertical axis lines set to absolute). 62 Simple Network Management Protocol in the Avaya Media Processing Server Environment October 2014

Line Subtree This MIB Object Is analogous to this representation 2) Sum of physical phone line icons; cursor placement over last physical phone line icon (line number representation); line number representation in right margin. a 3) Line count. In this MPS Manager tool 2) Line Status window. 3) vsh Phone Line Status report (system-wide). b vruspancnt Quantity of indicated spans. Span Status (also displayed in Tree) vruhostcnt Quantity of indicated hosts. Host Status vrustate c 1) MPS icons (color of). 1) APPMAN, Tree vrustatelastchange 2) MPS state symbology (type of symbol). Time and date stamp in the MPS command line status report. d 2) Span Status and Host Status (also displayed in Tree) vsh SRP Status and SRP Group Status reports. a. Second and third items assume all applicable rows of table are completely covered with physical phone line icons; otherwise, appropriate adjustments should be made. Note that although this icon represents a physical line, the line numbers in the table are indicative of the logical line with which the physical line is associated. For additional information pertaining to this logical-to-physical line mapping, refer to Avaya Media Processing Server Manager Reference Manual. b. The quantity of lines shown in the report is indicative of the total number of physical phone lines on the system. However, the actual phone line number indicated at each entry within the body of the report is the logical phone line location on the MPS. Though the physical-to-logical phone line mapping is most often on a one-to-one basis, it should not be assumed that the report line numbers indicate the actual location of the physical phone line on the MPS. For additional information, refer to Avaya Media Processing Server Manager Reference Manual. c. Any change to this particular data is analogous to one of the reasons for the notifycomponentstatechg trap being generated see notifycomponentstatechgb. d. The time displayed in the report differs by a few seconds from the actual time the change took place. This is due to the delay between the time the report is initiated (data queried) and the time the data is received by the management station. Line Subtree The Line subtree defines the parameters of the lines on the system. This is handled in the MPS Manager through the tools and windows that follow. Note: The representation of lines shown in the MPS Manager is indicative of the physical phone lines on the system. However, the actual phone line number indicated at each entry is the logical October 2014 Simple Network Management Protocol in the Avaya Media Processing Server Environment 63

MPS Manager and SNMP Mappings phone line location on the MPS. Though the physical-to-logical phone line mapping is most often on a one-to-one basis, do not assume that the line numbers indicate the actual location of the physical phone line on the MPS. For additional, specific information, refer to Avaya Media Processing Server Manager Reference Manual. linevruid lineid This MIB Object Is analogous to this representation 1) MPS number at command line request. 2) Listed as MPS at command line prompt. 3) Number after colon in MPS identification 1) Listed under LINE column. 2) Listed in body of report by line number. 3) Listed in windows by line number. In this MPS Manager tool 1) vsh SRP Status report. 2) vsh CCM Status report. 3) APPMAN, Span Status, Host Status, Line Status, Tree 1) vsh SRP Status report. 2) vsh CCM Status report. 3) APPMAN, Line Status linetype Phone line icon. APPMAN, Tree linestate lineappname lineappoverlay lineappadminstate lineappstate a Listed in body of report next to line number. 1) Textual representation of application name and line number. 2) Textual representation of application name with corresponding unique color resident on phone lines to which it applies. Not directly correlated on a per line basis: linked applications are displayed in this tool on a per-component basis. Window names imply the functions managed by these tools. 1) Phone line icon (by color). 2) Presence or absence of applications listed on phone lines shown. vsh CCM Status report; Activity Monitor CCM Status graphs. 1) APPMAN 2) APPMAN, Span Status, Host Status (when indexed by line), Tree Linked APP graph. APPMAN 1) APPMAN, Tree 2) Span Status 64 Simple Network Management Protocol in the Avaya Media Processing Server Environment October 2014

Span Table Subtree This MIB Object lineappstatelastchange lineappcfglastchange Is analogous to this representation Application name listed in right-most column, use time and date stamp in report. b Entry under STATE of RUNNING indicates configure, EXITED indicates unconfigure; use time and date stamp in report. c In this MPS Manager tool vsh SRP Status report. vsh SRP Status report. a. Any change to this particular data is analogous to the reason for the notifylineappstatechg trap being generated see notifylineappstatechgc. b. The time displayed in the report differs by a few seconds from the actual time the change took place. This is due to the delay between the time the report is initiated (data queried) and the time the data is received by the management station. c. The results of the SRP Status Report are generated at the time the report is called by the user. Each time the user repeats the procedure, a new set of data is generated. By using the scroll bar along the right side of the screen, comparisons can be made amongst the reports generated. By leaving the screen active and generating reports by choice, a running tabulation can be kept, and the above information extrapolated for the applications (for example, the addition or deletion of applications can be determined). Span Table Subtree The Span Table subtree defines the parameters of the spans on the system. These parameters are all displayed by the MPS Manager in the Span Status tool. Note: The line numbers in the MPS Manager are indicative of the logical line with which the physical line is associated. For additional information pertaining to this logical-to-physical line mapping, refer to Avaya Media Processing Server Manager Reference Manual. spanvruid This MIB Object Is analogous to this representation Number after colon in MPS identification In this MPS Manager tool Span Status. spanid Listed by span name. Span Status. spanlineidstart spanlinenumber First number under Line Range next to each span listing. Number of lines listed under Line Range. This information becomes cumulative when Span Status. Span Status. October 2014 Simple Network Management Protocol in the Avaya Media Processing Server Environment 65

MPS Manager and SNMP Mappings spanenabled spanstate a This MIB Object Is analogous to this representation more than one span exists: simple mathematics for those spans above the first yields the desired result. Alternatively, add up number of lines per span shown in Lines: field. Span state symbology (type of symbol). Span state symbology (type of symbol). In this MPS Manager tool Span Status. Span Status. a. Any change to this particular data is analogous to the reason for the notifyspanstatechg trap being generated see notifyspanstatechgd. Applications Subtree This subtree describes the applications that are associated with a VRU. MPS Manager APPMAN functions handle the analogous relationships. Note: Note that the line numbers in the MPS Manager are indicative of the logical line with which the physical line is associated. For additional information pertaining to this logical-to-physical line mapping, refer to Avaya Media Processing Server Manager Reference Manual. This MIB Object appvruid appname appoptions applinecnt Is analogous to this representation Number after colon in MPS identification. 1) Textual representation of application name. 2) Textual representation of application name with corresponding unique color. Options listed when launched from an application object. 1) Textual representation of application name and line number. Quantities of each application assignment can be counted up. APPMAN In this MPS Manager tool 1) APPMAN 2) APPMAN, Span Status, Host Status APPMAN, Application Configuration 1)APPMAN 2) APPMAN (configurations only) Host Status(when indexed by line). 3) Line Status bar graph (set to Absolute and launched on an application object). 66 Simple Network Management Protocol in the Avaya Media Processing Server Environment October 2014

Applications Stats Subtree This MIB Object Is analogous to this representation 2) Textual representation of application name with corresponding unique color resident on phone lines to which it applies. Quantities of each application assignment can be counted up. 3) Sum of all states of application shown. In this MPS Manager tool Applications Stats Subtree This subtree describes the application statistic associated with an application. In the MPS Manager, this data is presented in the form of an application report through the MPS Reporter Tools. These tools generate user-defined application and system reports. For detailed information on using these tools, refer to Avaya Media Processing Server Reporter User's Guide. This MIB Object is analogous to appstatsvruid This representation Can be identified by checking the column mapping menu. In this MPS Manager tool MPS Reporter. appstatsname Defined at top of each column. MPS Reporter. appstatsvalue appstatslastchange Listed in columns if application statistics is selected in the Data Mapping window. Shown in Date column of report based on date and time constraints set up in Schedule Statistics Report tool. MPS Reporter. MPS Reporter. Host Subtree This subtree describes and defines the parameters of the host associated with the VRU. In MPS Manager, this is accomplished in the Host Status tool. The MIB variables and their MPS Manager counterparts are discussed below. This MIB Object Is analogous to this representation In this MPS Manager tool hostvruid Number after colon in MPS identification. Host Status October 2014 Simple Network Management Protocol in the Avaya Media Processing Server Environment 67

MPS Manager and SNMP Mappings This MIB Object Is analogous to this representation In this MPS Manager tool hostid Listed by host name. Host Status hostlucnt Symbology when tool is indexed by VT (MPS Manager identifies LUs as VTs). Count up the number of symbols in the VTs: field other than that of unassigned. Host Status hostprotocol The tool has a specific entry for this. Host Status hoststate a Host state symbology (type of symbol). Host Status a. Any change to this particular data is analogous to the reason for the notifyhoststatechg trap being generated see notifyhoststatechge. LU Subtree This subtree describes and defines the parameters of the LU associated with the system. MPS Manager equates LU with VT. The status of LU can be determined in the MPS Manager through the use of the Host Status tool. The tool must be indexed by VT to access this information. luvruid This MIB Object Is analogous to this representation Number after colon in MPS identification In this MPS Manager tool Host Status luhostid Host name selected. Host Status luid lustate a Numbers along right side of tool adjacent to symbolic representation of VTs. VT state symbology (type of symbol) in VTs: field. Host Status Host Status a. Any change to this particular data is analogous to the reason for the notifylustatechg trap being generated see notifylustatechgf. Components Subtree This subtree contains two tables that describe and define the components and their presence on the MPS network. 68 Simple Network Management Protocol in the Avaya Media Processing Server Environment October 2014

Components Subtree Component Type Table The only MIB object in this table that has a comparable representation in the MPS Manager is componenttypename. This object contains the common noun name (acronym) associated with each component type (for example, MPS and Speech Server). Component Table This table defines and describes all the components on the network that the SNMP agent knows about. componentid This MIB Object componentstate a componentstatelastchange Is analogous to this representation Number after colon in component identification 1) MPS, Speech Server icons (color of icon). 2) MPS state symbology (type of symbol). Time and date stamp in report of component command line. b In this MPS Manager tool APPMAN, Line Status, Span Status, Host Status, MPS Control Center, Alarm Filter, Tree 1) APPMAN, Tree 2) NA vsh SRP Status and SRP Group Status reports. a. Any change to this particular data is analogous to the reason for the notifycomponentstatechg trap being generated see notifycomponentstatechgb. b. The time displayed in the report differs by a few seconds from the actual time the change took place. This is due to the delay between the time the report is initiated (data queried) and the time the data is received by the management station. October 2014 Simple Network Management Protocol in the Avaya Media Processing Server Environment 69

Chapter 5: Troubleshooting/FAQs This chapter covers: 1. Troubleshooting 2. Frequently Asked Questions (FAQs) Overview This appendix is divided into two sections designed to help you use your SNMP package. The first section covers problems you might encounter during use of SNMP, their causes, and solutions (see Troubleshooting on page 70. The second section lists some Frequently Asked Questions and their answers (see Frequently Asked Questions (FAQs) on page 74. Troubleshooting This section presents some common fault conditions, their causes, and suggested actions. Try using these entries prior to contacting Avaya technical support. Condition: The following message is found in the vrsnmpd.log file (see Error Logging on page 39): Tue Aug 18 08:51:00 1998 Problem with license. Cannot talk to the LicenseServ server on host >>scrubjay<< Server not running?. FILE: vpsresources/vrsnmp_license.c LINE: 198 Cause: Action: 1. No license exists for Avaya SNMP agent. 2. License server is not running or is configured incorrectly. 3. LSHOST is not set to the correct node running the license server. 1. Make sure you have obtained and properly installed the license file (see Package Licensing on page 16). 2. Check if you have a properly configured and running license server (consult your systems administrator for assistance if necessary). 70 Simple Network Management Protocol in the Avaya Media Processing Server Environment October 2014

Troubleshooting 3. Make sure the environment variable LSHOST contains the name of the node running the license server. Condition: The following message is found in the vrsnmpd.log file (see Error Logging on page 39): Tue Aug 25 09:35:00 1998 Error on master agent file descriptor, attempt to reconnect. FILE: vpsresources/vrsnmp_ipc.c LINE: 1438 Cause: Avaya MPS-components subagent is unable to connect to the master agent (see Agents on page 39). Action: Verify that the master agent is running (see Verify Agents Response on page 19). Condition: When trying to run snmpstart, you receive the following message: ERROR: Unable to start service Peri_vrsnmpd Cause: Avaya MPS-components subagent (see Agents on page 39) could not be started. Action: Make sure that the service is not already running. Use snmpstop or the Services Control Panel to stop the service, then repeat the snmpstart command (see Windows Systems on page 21). Note: This scenario can apply to any of the Avaya Windows SNMP agents. Condition: When trying to run snmpstop, you receive the following message: ERROR: Unable to stop service Peri_vrsnmpd Cause: Avaya MPS components subagent (see Agents on page 39) could not be stopped. Action: Check to make sure that the service was not already stopped. Use snmpstart or the Services Control Panel to start the service, then repeat the snmpstop command (see Windows Systems on page 21). Note: This scenario can apply to any of the Avaya Windows SNMP agents. October 2014 Simple Network Management Protocol in the Avaya Media Processing Server Environment 71

Troubleshooting/FAQs Condition: When trying to run snmpstop or snmpstart, you receive the following message: ERROR: Unable to connect to service control manager Cause: The process responsible for managing services is unavailable. Action: Try stopping/starting the services through the Services Control Panel (see Windows Systems on page 21). Otherwise, reboot the system to re-establish contact with the service control manager. Condition: When trying to run snmpget or snmpset command line utilities, you receive the following message: No Such Instance ly exists at this OID Cause: Action: 1. The SNMP agent(s) are not running. 2. There is no information available for the requested object. 3. You have failed to append.0 to a scalar request. 1. Make sure the agents (particularly the MPS components subagent) are running (see Windows Systems on page 21). 2. Perform a snmpgetnext, snmpwalk, or snmptable command on the object table to see if the information you are requesting exists at that time (see Table Referencing on page 45). 3. Re-enter the command with a.0 following the object name (for example, alrmlogmax.0) (see Direct Referencing on page 45). Condition: When running an snmpget command line utility, you receive the following message: <variable_name>: Unknown Object Identifier (Sub-id not found: (top) -> <variable_name>) where <variable_name> is the object on which you performed the snmpget command. Cause: You entered an incorrect object name. Action: Be sure that you have correctly entered the object name, including case-dependency, no spaces, and abbreviated portions within the object name. (For example, in alrmlogmax, alrm is the abbreviated version of the word alarm and the L in Log and and M in Max need to be upper-case. (See Overview on page 78). Condition: 72 Simple Network Management Protocol in the Avaya Media Processing Server Environment October 2014

Troubleshooting Traps are not being generated or received. Cause: Action: 1. MPS-components subagent is not running. 2. The management station you are on was not configured to receive traps. 1. Make sure the MPS components subagent is running (see Windows Systems on page 21). 2. Run the trapcfg.pl script or edit the snmpd.conf file to enable the management station to receive traps. Condition: trapcfg.pl does not run. You receive the following message when trying to run trapcfg.pl: ERROR: Environment variable SNMPCONFPATH not set Cause: The environment variable specifying the location of snmpd.conf was not set, or does not point to the proper location. Action: Make sure SNMPCONFPATH is properly configured (see Master/Subagent Related on page 28). Condition: Cannot view traps. Cause: Action: 1. You have not run snmptrapd executable, or have run snmptrapd without the -Lo command line option. 2. You are not configured as a station allowed to receive traps. 1. Enter snmptrapd -Lo at a command line (see Viewing Traps on page 48). 2. Run the trapcfg.pl script or edit the snmpd.conf file to enable the management station to receive traps. Condition: trapcfg.pl does not configure the station you entered. Cause: You did not enter a valid IP address. Action: Enter a proper numerical IP address (see Defining Trap Destinations on page 34). October 2014 Simple Network Management Protocol in the Avaya Media Processing Server Environment 73

Troubleshooting/FAQs Condition: An OID is received that does not seem to coincide with the request sent. Cause: The object table that you performed the request on is empty. Action: Check the Periphonics MIB to see if the returned value follows that of the one you requested. If a request is made on an "empty" table, the next available object containing information is normally returned (see Table Referencing on page 45). Condition: A request on the alrmlogtable does not return any results even though alarms are generated. Cause: The table that you performed the request on is empty. Action: This occurs if the MPS-components subagent is stopped: each time that occurs, the table is emptied. The alrmlogtable begins collecting alarms generated subsequent to a restart of the subagent (see Component Events Alarms Subtree on page 51). Condition: An alarm message longer than 255 characters (6 lines) is truncated. Cause: This is a physical limitation within the program. Action: There should be adequate information available to you based on the number of characters allowable in the alarm. If additional information is needed, first try performing a get-request on the object alrmlogmessage (see Getting a Value on page 47). If this still does not meet your needs, contact your Avaya support personnel. Frequently Asked Questions (FAQs) This section presents the answers to some frequently asked questions regarding SNMP and its relationship to the MPS environment. Question: What is SNMP? Answer: 74 Simple Network Management Protocol in the Avaya Media Processing Server Environment October 2014

Frequently Asked Questions (FAQs) SNMP is a network management protocol by which management stations and agents communicate. In summary, SNMP provides a network management protocol for allowing managers (clients) to perform status and control functions by querying agents (servers) about the network elements described in various MIBs (databases) (see Simple Network Management Protocol on page 7). Question: What is the MIB and what changes would customers make? Answer: The Management Information Base (MIB) is a collection of objects that describe one or more network elements. An MIB is considered a form of database schema that contains the set of system components that can be queried or controlled (see Management Information Base (MIB) on page 7). Note: Customers should never make any changes to the MIB. Question: How do I use SNMP on an MPS system? Answer: This question has numerous parts to its answer, all of which are covered throughout this manual. The basic requirements, besides licensing and installation, are: Configure traps to specify which management stations receive them. Make sure agents are running (see Verify Agents Response on page 19) Understand the Periphonics MIB (see The MIB Applied on page 50) Use command line utilities to monitor and control the MPS environment (see Instance Identification on page 45) and SNMP Applied on page 47). Question: What is the difference between SNMP and TCP as protocols? Answer: SNMP lives on UDP and integrates MPS control and monitoring into existing management software (see Management Information Base (MIB) on page 7). Question: Does SNMP run over the same network structure as TCP, and does it use the same configuration files that the system normally uses? Answer: SNMP uses UDP ports 161 and 162, and has its own configuration files (see Configuration Files on page 24). Port 162 is used to receive traps on the management station, and port 161 is used by the SNMP master agent to receive get- and set- requests. October 2014 Simple Network Management Protocol in the Avaya Media Processing Server Environment 75

Troubleshooting/FAQs Question: How can I tell that the SNMP package is installed and running on my machine? Answer: Under the MPSHOME directory, find the package name PERIsnmp, or use the perirev command to find the listing (see the Avaya Media Processing Server Series Solaris System Operator's Guide and Avaya Media Processing Server Series Windows System Operator's Guide for information related to these procedures). To determine if the package is running, use the snmpwalk command (see Verify Agents Response on page 19). Question: How would SNMP packets be identified when using Snoop? Answer: Snoop ports 161, 162, or both. Question: Does SNMP need to be licensed? Answer: Yes. You must properly install and modify the license package and file as applicable (see Package Licensing on page 16). If the license does not exist, a message error is logged to the vrsnmpd.log (see Error Logging on page 39). Question: What are some of the possible problems and conflicts I may encounter when using the product? Answer: Review Troubleshooting on page 70. You might also want to see Installation Upgrades on page 20. Question: If I encounter problems, is there somewhere I can look to see what might have happened? Answer: Yes. Error logging is now part of your SNMP package. To find out more, see Error Logging on page 39. Question: What impact might the package have on processor overhead and network traffic? Answer: Using command line utilities has a small impact on a processor's overhead. The greatest impact on both the processor and the network occurs when multiple management stations are designated as 76 Simple Network Management Protocol in the Avaya Media Processing Server Environment October 2014

Frequently Asked Questions (FAQs) trap recipients. The more stations designated as trap recipients, the greater the traffic and demand on processor power. Question: What are traps? How do I know if they are being generated, and how can I see them? Answer: Traps are unsolicited messages sent from the agent to the manager in the event of unexpected internal conditions within the MPS system. To test traps, stop and start SRP to purposely generate a trap. To view traps, enter the 'snmptrapd -Lo' command at the command line of any management station designated to receive traps. For important information related to these procedures, see Viewing Traps on page 48. Question: What happens if I add a component to a system that is already running SNMP? Answer: Stop and restart SNMP so that it recognizes the new component (see SNMP System Startup on page 20). Question: Why do I need SNMP if I already have the MPS Manager? Answer: MPS Manager communicates directly with the MPS network for monitoring and control through proprietary protocol. Workstations that are not configured to run the MPS Manager cannot communicate with the MPS network and components without SNMP. SNMP acts as a translator between management stations that are not configured for MPS Manager and the MPS network. SNMP translates both command line inputs and communications through third-party tools that are SNMP-compliant (see SNMP and MPS Integration on page 14). October 2014 Simple Network Management Protocol in the Avaya Media Processing Server Environment 77

Chapter 6: Periphonics MIB Reference This chapter covers: 1. Basic Tree Structure 2. Detailed Component Structure Overview The Avaya MPS uses the Periphonics MIB. The Periphonics MIB is registered with the IANA and is assigned the number 1357. The Periphonics MIB OID is: iso.org.dod.internet.private.enterprises.periphonics 1.3.6.1.4.1.1357 This appendix shows the objects that make up the Periphonics MIB. It includes both a graphical hierarchy in tree form for easy reference, and a more comprehensive view detailing the structure of each entry in the enterprise MIB. It is provided for those people who desire a better understanding of the function of these items as they apply to the MPS environments. Basic Tree Structure This figure provides a simple way to navigate through the MIB and determine the relationship of objects within it. Note: The following variables, though present, have not been implemented for use at this time: vrudescr, appdescr, hostdescr, and ludescr.in addition, the objects vrunetworkmibcompliance, vrunetworkmibcompliancebycomponent, vrunotificationsgroup, vrueventsgroup, componentnotificationsgroup, componenteventsgroup, notifyalarm, notifyalarmbycomponent, notifyvrustatechg, and alrmlogvruid, though still present in the MIB, have a status of deprecated and are no longer supported. periphonics (1357) +-- vrunetwork(1) +-- vrunetworkmibconformance(1) 78 Simple Network Management Protocol in the Avaya Media Processing Server Environment October 2014

Basic Tree Structure +-- vrunetworkmibcompliances(1) +-- vrunetworkmibcompliance(1) +-- vrunetworkmibcompliancebycomponent (2) +-- vrunetworkmibcompliancebycomponent2 (3) +--vrunetworkmibgroups(2) +-- vrunotificationsgroup(1) +-- vrueventsgroup(2) +-- vrugroup(3) +-- linegroup(4) +-- applicationgroup(5) +-- hostgroup(6) +-- componentgroup(7) +-- componentnotificationsgroup(8) +-- componenteventsgroup(9) +-- componentnotificationsgroup2(10) +-- componentseventsgroup2(11) +-- vruevents(2) +-- vrueventvars(1) +-- -N- Object evobjectid(1) +-- -N- EnumVal evchange(2) +-- vrunotifications(2) +-- notifyalarm(1) +-- notifyvrustatechg(2) +-- notifylineappstatechg(3) +-- notifyspanstatechg(4) +-- notifyhoststatechg(5) +-- notifylustatechg(6) +-- notifytopologychg(7) +-- notifycomponentstatechg(8) +-- notifyalarmbycomponent(9) +-- notifyalarmbycomponentex(10) +-- alarms(3) +-- -R- Integer alrmlogmax(4) +-- -R- Integer alrmlognumber(5) +-- alrmlogtable(6) +-- alrmlogtableentry(1) +-- -N- Integer alrmlogidx(1) +-- -R- Integer alrmlogseverity(2) +-- -R- Integer alrmlogcode(3) +-- -R- Integer alrmlogvruid(4) +-- -R- Integer alrmloglineid(5) +-- -R- Integer alrmloghostid(6) +-- -R- TextVal alrmlogprocname(7) +-- -R- TextVal alrmlogmessage(8) +-- -R- Object alrmlogtime(9) +-- -R- Integer alrmlogcomponenttype(10) +-- -R- Integer alrmlogcomponentid(11) +-- -R- IPAddr alrmlogcomponentipaddress(12) +-- vrutable(3) +-- vrutableentry(1) +-- -N- Integer vruid(1) October 2014 Simple Network Management Protocol in the Avaya Media Processing Server Environment 79

Periphonics MIB Reference +-- -R- IPAddr vruipaddress(2) +-- -RW TextVal vrudescr(3) +-- -R- Integer vrulinecnt(4) +-- -R- Integer vruspancnt(5) +-- -R- Integer vruhostcnt(6) +-- -RW EnumVal vruadminstate(7) +-- -R- EnumVal vrustate(8) +-- -R- Object vrustatelastchange(9) +-- linetable(4) +-- linetableentry(1) +-- -N- Integer linevruid(1) +-- -N- Integer lineid(2) +-- -R- EnumVal linetype(3) +-- -R- Integer lineprotocol(4) +-- -R- EnumVal linestate(5) +-- -RW TextVal lineappname(6) +-- -R- TextVal lineappoverlay(7) +-- -RW EnumVal lineappadminstate(8) +-- -R- EnumVal lineappstate(9) +-- -R- Object lineappstatelastchange(10) +-- -R- Object lineappcfglastchange(11) +-- spantable(5) +-- spantableentry(1) +-- -N- Integer spanvruid(1) +-- -N- Integer spanid(2) +-- -R- Integer spanlineidstart(3) +-- -R- EnumVal spanlinenumber(4) +-- -R- EnumVal spanenabled(5) +-- -R- EnumVal spanstate(6) +-- -R- Object spanstatelastchange(7) +-- apptable(6) +-- apptableentry(1) +-- -N- Integer appvruid(1) +-- -N- TextVal appname(2) +-- -RW TextVal appdescr(3) +-- -R- TextVal appoptions(4) +-- -R- Integer applinecnt(5) +-- appstatstable(7) +-- appstatstableentry(1) +-- -N- Integer appstatsvruid(1) +-- -N- TextVal appstatsname(2) +-- -R- Integer appstatsvalue(3) +-- -R- Object appstatslastchange(4) +-- hosttable(8) +-- hosttableentry(1) +-- -N- Integer hostvruid(1) +-- -N- Integer hostid(2) +-- -RW TextVal hostdescr(3) +-- -R- Integer hostlucnt(4) 80 Simple Network Management Protocol in the Avaya Media Processing Server Environment October 2014

Detailed Component Structure +-- -R- EnumVal hostprotocol(5) +-- -R- EnumVal hostmedia(6) +-- -RW EnumVal hostadminstate(8) +-- -R- EnumVal hoststate(9) +-- -R- Object hoststatelastchange(10) +-- lutable(9) +-- lutableentry(1) +-- -N- Integer luvruid(1) +-- -N- Integer luhostid(2) +-- -N- Integer luid(3) +-- -R- TextVal ludescr(4) +-- -R- TextVal lupoolname(5) +-- -R- EnumVal lustate(6) +-- -R- Object lustatelastchange(7) +-- components(10) +-- componenttypetable(1) +-- componenttypetableentry(1) +-- -N- Integer componenttypeid(1) +-- -R- TextVal componenttypename(2) +-- componenttable(3) +-- componenttableentry(1) +-- -N- Integer componenttype(1) +-- -N- Integer componentid(2) +-- -R- IPAddr componentipaddress(3) +-- -R- EnumVal componentstate(4) +-- -R- Object componentstatelastchange(5) Detailed Component Structure This section provides more defined references to each component of the Periphonics MIB. The following variables, though present, have not been implemented for use at this time: vrudescr, appdescr, hostdescr, and ludescr. In addition, the objects vrunetworkmibcompliance, vrunetworkmibcompliancebycomponent, vrunotificationsgroup, vrueventsgroup, componentnotificationsgroup, componenteventsgroup, notifyalarm, notifyalarmbycomponent, notifyvrustatechg, and alrmlogvruid, though still present in the MIB, have a status of deprecated and are no longer supported. vrunetwork MODULE-IDENTITY LAST-UPDATED "9808050000Z" ORGANIZATION "Avaya Corporation" CONTACT-INFO October 2014 Simple Network Management Protocol in the Avaya Media Processing Server Environment 81

Periphonics MIB Reference "" "SNMP MIB module for a VRU Network." ::= { periphonics 1 } -- -- Conformance Information -- vrunetworkmibconformance OBJECT IDENTIFIER ::= { vrunetwork 1 } vrunetworkmibcompliances OBJECT IDENTIFIER ::={ vrunetworkmibconformance 1} vrunetworkmibgroups OBJECT IDENTIFIER ::= { vrunetworkmibconformance 2} -- -- Compliance Statements -- vrunetworkmibcompliance MODULE-COMPLIANCE deprecated "The compliance statement for SNMPv2 entities which implement the VRU-NETWORK MIB." MODULE -- this module MANDATORY-GROUPS { vrunotificationsgroup, vrueventsgroup, ::= { vrunetworkmibcompliances 1 } vrugroup,linegroup, applicationgroup, hostgroup } vrunetworkmibcompliancebycomponent MODULE-COMPLIANCE deprecated "The compliance statement for SNMPv2 entities which implement the VRU-NETWORK MIB." MODULE -- this module MANDATORY-GROUPS { vrugroup, linegroup, applicationgroup, ::= { vrunetworkmibcompliances 2 } hostgroup, componentgroup, componentnotificationsgroup, componenteventsgroup } vrunetworkmibcompliancebycomponent2 MODULE-COMPLIANCE "The compliance statement for SNMPv2 entities which implement the VRU-NETWORK MIB." 82 Simple Network Management Protocol in the Avaya Media Processing Server Environment October 2014

Detailed Component Structure MODULE -- this module MANDATORY-GROUPS { vrugroup, linegroup, applicationgroup, ::= { vrunetworkmibcompliances 3 } -- -- units of conformance -- hostgroup, componentgroup, componentnotificationsgroup2, componenteventsgroup2 } vrunotificationsgroup NOTIFICATION-GROUP NOTIFICATIONS { notifyalarm, notifyvrustatechg, notifylineappstatechg, notifyspanstatechg, notifyhoststatechg, notifylustatechg, notifytopologychg } deprecated "A collection of notifications related to a Voice Response Unit (VRU)." ::= { vrunetworkmibgroups 1 } vrueventsgroup OBJECT-GROUP OBJECTS { evobjectid, evchange, alrmlogmax, alrmlognumber, alrmlogseverity, alrmlogcode, alrmlogvruid, alrmloglineid, alrmloghostid, alrmlogprocname, alrmlogmessage, alrmlogtime } deprecated "A collection of objects related to a VRU." ::= { vrunetworkmibgroups 2 } vrugroup OBJECT-GROUP OBJECTS { vruipaddress, vrudescr, vrulinecnt, vruspancnt,vruhostcnt, vruadminstate, vrustate, vrustatelastchange} "A collection of objects related to a VRU." ::= { vrunetworkmibgroups 3 } linegroup OBJECT-GROUP OBJECTS { linetype, lineprotocol, linestate, lineappname, lineappoverlay, lineappadminstate, lineappstate, lineappstatelastchange, October 2014 Simple Network Management Protocol in the Avaya Media Processing Server Environment 83

Periphonics MIB Reference lineappcfglastchange, spanlineidstart, spanlinenumber, spanenabled, spanstate, spanstatelastchange } "A collection of objects related to a line on a VRU." ::= { vrunetworkmibgroups 4 } applicationgroup OBJECT-GROUP OBJECTS { appdescr, appoptions, applinecnt, appstatsvalue, appstatslastchange } "A collection of objects related to a VRU application." ::= { vrunetworkmibgroups 5 } hostgroup OBJECT-GROUP OBJECTS { hostdescr, hostlucnt, hostprotocol, hostmedia, hostadminstate, hoststate, hoststatelastchange, ludescr, lupoolname, lustate, lustatelastchange } "A collection of objects related to a VRU host." ::= { vrunetworkmibgroups 6 } componentgroup OBJECT-GROUP OBJECTS { componenttypename, componentipaddress, componentstate, componentstatelastchange } "A collection of objects related to components." ::= { vrunetworkmibgroups 7 } componentnotificationsgroup NOTIFICATION-GROUP NOTIFICATIONS { notifylineappstatechg, notifyspanstatechg,notifyhoststatechg, notifylustatechg, notifytopologychg, notifycomponentstatechg, notifyalarmbycomponent } deprecated 84 Simple Network Management Protocol in the Avaya Media Processing Server Environment October 2014

Detailed Component Structure "A collection of notifications related to the MPS network." ::= { vrunetworkmibgroups 8 } componenteventsgroup OBJECT-GROUP OBJECTS { evobjectid, evchange, alrmlogmax, alrmlognumberalrmlogseverity, alrmlogcode, alrmloglineid, alrmloghostid, alrmlogprocname, alrmlogmessage, alrmlogtime, alrmlogcomponenttype, alrmlogcomponentid } deprecated "A collection of objects related to a VRU." ::= { vrunetworkmibgroups 9 } componentnotificationsgroup2 NOTIFICATION-GROUP NOTIFICATIONS { notifylineappstatechg, notifyspanstatechg, notifyhoststatechg, notifylustatechg, notifytopologychg, notifycomponentstatechg, notifyalarmbycomponentex } "A collection of notifications related to the MPS network." ::= { vrunetworkmibgroups 10 } componenteventsgroup2 OBJECT-GROUP OBJECTS { evobjectid, evchange, alrmlogmax, alrmlognumber alrmlogseverity, alrmlogcode, alrmloglineid, alrmloghostid, alrmlogprocname, alrmlogmessage, alrmlogtime, alrmlogcomponenttype, alrmlogcomponentid, alrmlogcomponentipaddress } "A collection of objects related to a VRU." ::= { vrunetworkmibgroups 11 } -- -- VRU Events Subtree -- vruevents OBJECT IDENTIFIER ::= { vrunetwork 2 } -- -- VRU Events Variables Subtree -- -- Defines variables that can be included within a VRU Network trap. These -- object IDs cannot be retrieved from the SNMP agent. Defining them here -- October 2014 Simple Network Management Protocol in the Avaya Media Processing Server Environment 85

Periphonics MIB Reference serves as documentation for the contents of NMS traps. --- vrueventvars OBJECT IDENTIFIER ::= { vruevents 1 } EI evobjectid OBJECT-TYPE SYNTAX OBJECT IDENTIFIER accessible-for-notify "Object identifier associated with the source of the trap. This object cannot be retrieved from the SNMP agent." ::= { vrueventvars 1 } evchange OBJECT-TYPE SYNTAX } other(1), add(2), del(3), mod(4) INTEGER{ accessible-for-notify "Describes the type of change which just occurred. This object cannot be retrieved from the SNMP agent." ::= { vrueventvars 2 } -- -- Events Group Notifications Subtree -- -- Defines traps that are sent to Network management stations. -- vrunotifications OBJECT IDENTIFIER ::= { vruevents 2 } notifyalarm NOTIFICATION-TYPE OBJECTS { alrmlogseverity, alrmlogcode, alrmlogvruid, alrmloglineid, alrmloghostid, alrmlogprocname, alrmlogmessage, alrmlogtime } deprecated "When a exceptional condition occurs the VRU system generates an alarm. This trap forwards these alarms to the Network Management Station. **NOTE: this trap is deprecated and replaced by notifyalarmbycomponent trap." ::= { vrunotifications 1 } 86 Simple Network Management Protocol in the Avaya Media Processing Server Environment October 2014

Detailed Component Structure notifyvrustatechg NOTIFICATION-TYPE OBJECTS { vrustate } deprecated "This trap is forwarded to the Network Management Station when the VRU changes its state. **NOTE: this trap is deprecated and replaced by the notifycomponentstatechg trap." ::= { vrunotifications 2 } notifylineappstatechg NOTIFICATION-TYPE OBJECTS { lineappstate, lineappname, lineappoverlay } "This trap is forwarded to the Network Management Station when an application attached to a VRU line changes its state." ::= { vrunotifications 3 } notifyspanstatechg NOTIFICATION-TYPE OBJECTS { spanstate } "This trap is forwarded to the Network Management Station when a VRU span changes its state." ::= { vrunotifications 4 } notifyhoststatechg NOTIFICATION-TYPE OBJECTS { hoststate } "This trap is forwarded to the Network Management Station when a VRU host changes its state." ::= { vrunotifications 5 } notifylustatechg NOTIFICATION-TYPE OBJECTS { lustate } October 2014 Simple Network Management Protocol in the Avaya Media Processing Server Environment 87

Periphonics MIB Reference "This trap is forwarded to the Network Management Station when a VRU host lu changes its state." ::= { vrunotifications 6 } notifytopologychg NOTIFICATION-TYPE OBJECTS { evobjectid, evchange } "This trap is forwarded to the Network Management Station when a VRU Network object topology status has changed." ::= { vrunotifications 7 } notifycomponentstatechg NOTIFICATION-TYPE OBJECTS { componentstate } "This trap is forwarded to the Network Management Station when a VRU Network component changes its state." ::= { vrunotifications 8 } notifyalarmbycomponent NOTIFICATION-TYPE OBJECTS { alrmlogcomponenttype, alrmlogcomponentid, alrmlogseverity, alrmlogcode, alrmloglineid, alrmloghostid, alrmlogprocname, alrmlogmessage, alrmlogtime } deprecated "When an exceptional condition occurs in the MPS network a component generates an alarm. This trap forwards these alarms to the Network Management Station." **NOTE: this trap is deprecated and replaced by the notify AlarmByComponentEx trap." ::= { vrunotifications 9 } notifyalarmbycomponentex NOTIFICATION-TYPE OBJECTS { alrmlogcomponenttype, alrmlogcomponentid, alrmlogseverity, alrmlogcode, alrmloglineid, alrmloghostid, alrmlogprocname, alrmlogmessage, alrmlogtime, alrmlogcomponentipaddress } 88 Simple Network Management Protocol in the Avaya Media Processing Server Environment October 2014

Detailed Component Structure "When an exceptional condition occurs in the MPS network a component generates an alarm. This trap forwards these alarms to the Network Management Station. This is an extended version of notifyalarmbycomponent and includes the IP address of the component generating the alarm." ::= { vrunotifications 10 } -- -- Component Events Alarms Subtree -- -- Defines what component alarms are recorded and for how long. --alarms OBJECT IDENTIFIER ::= { vruevents 3 } alrmlogmax OBJECT-TYPE SYNTAX INTEGER (1..2147483647) ::= { alarms 4 } read-only "Specifies the maximum number of alarms that can be logged in the alarm log table at once. When alrmlognumber is equivalent to alrmlogmax, the first alarm in the table is removed when the next alarm is added" alrmlognumber OBJECT-TYPE SYNTAX INTEGER (1..2147483647) read-only "The number of log entries ly defined." ::= { alarms 5 } alrmlogtable OBJECT-TYPE SYNTAX SEQUENCE OF AlrmLogTableEntry ::= { alarms 6 } not-accessible "A list of alarm entries. The number of entries is given by alrmlognumber. This list is a queue. When the component generates an alarm, it is added to the end of the list. If the number of entries reaches alrmlogmax then the first entry is deleted before a new one is added." October 2014 Simple Network Management Protocol in the Avaya Media Processing Server Environment 89

Periphonics MIB Reference alrmlogtableentry OBJECT-TYPE SYNTAX AlrmLogTableEntry not-accessible "An alarm entry containing objects that describe the alarm." INDEX { alrmlogidx } ::= { alrmlogtable 1 } AlrmLogTableEntry ::= SEQUENCE { alrmlogidx alrmlogseverity alrmlogcode alrmlogvruid alrmloglineid alrmloghostid alrmlogprocname alrmlogmessage alrmlogtime alrmlogcomponenttype alrmlogcomponentid alrmlogcomponentipaddress } INTEGER, INTEGER, INTEGER, INTEGER, INTEGER, INTEGER, DisplayString, DisplayString, DateAndTime, INTEGER, INTEGER, IPAddress alrmlogidx OBJECT-TYPE SYNTAX INTEGER (1..2147483647) not-accessible "Index to the alarm log table between one and alrmlognumber." ::= { alrmlogtableentry 1 } alrmlogseverity OBJECT-TYPE SYNTAX INTEGER (0..9) read-only 90 Simple Network Management Protocol in the Avaya Media Processing Server Environment October 2014

Detailed Component Structure "Integer describing how severe this alarm is. The lower the value, the lower the severity. A severity value of 0 indicates that no severity is assigned to this alarm." ::= { alrmlogtableentry 2 } alrmlogcode OBJECT-TYPE SYNTAX INTEGER (0..2147483647) read-only "Code assigned to identify this alarm." ::= { alrmlogtableentry 3 } alrmlogvruid OBJECT-TYPE SYNTAX INTEGER (0..2147483647) read-only deprecated "VRU identifier that generated this alarm. A value of 0 is used to indicate no VRU is associated with this alarm. **NOTE: this object is deprecated and is replaced by alrmlogcomponentid object." ::= { alrmlogtableentry 4 } alrmloglineid OBJECT-TYPE SYNTAX INTEGER (0..2147483647) read-only "The phone line number associated with this alarm. A value of 0 indicates no phone line." ::= { alrmlogtableentry 5 } alrmloghostid OBJECT-TYPE SYNTAX INTEGER (0..2147483647) read-only October 2014 Simple Network Management Protocol in the Avaya Media Processing Server Environment 91

Periphonics MIB Reference "The host identifier associated with this alarm. A value of 0 indicates that no host is associated with this alarm." ::= { alrmlogtableentry 6 } alrmlogprocname OBJECT-TYPE SYNTAX DisplayString read-only "The name of the process that generated this alarm." ::= { alrmlogtableentry 7 } alrmlogmessage OBJECT-TYPE SYNTAX DisplayString read-only "A message describing the alarm that occurred." ::= { alrmlogtableentry 8 } alrmlogtime OBJECT-TYPE SYNTAX DateAndTime read-only "The time that this alarm was generated." ::= { alrmlogtableentry 9 } alrmlogcomponenttype OBJECT-TYPE SYNTAX INTEGER (0..2147483647) read-only "Component type of the MPS component that generated this alarm." 92 Simple Network Management Protocol in the Avaya Media Processing Server Environment October 2014

Detailed Component Structure ::= { alrmlogtableentry 10 } alrmlogcomponentid OBJECT-TYPE SYNTAX INTEGER (0..2147483647) read-only "Component identifier of the MPS component that generated this alarm." ::= { alrmlogtableentry 11 } alrmlogcomponentipaddress OBJECT-TYPE SYNTAX IPAddress read-only "Component IP address of the MPS component that generated this alarm." ::= { alrmlogtableentry 12 } -- -- VRU Subtree -- vrutable OBJECT-TYPE SYNTAX SEQUENCE OF VruTableEntry not-accessible "All Voice Response Units (VRU) that are known by an agent" ::= { vrunetwork 3 } vrutableentry OBJECT-TYPE SYNTAX VruTableEntry not-accessible "A (conceptual) row entry for one VRU." INDEX { vruid } ::= { vrutable 1 } October 2014 Simple Network Management Protocol in the Avaya Media Processing Server Environment 93

Periphonics MIB Reference VruTableEntry ::= SEQUENCE { vruid vruipaddress vrudescr vrulinecnt vruspancnt vruhostcnt vruadminstate vrustate vrustatelastchange } INTEGER, IpAddress DisplayString INTEGER, INTEGER, INTEGER, INTEGER, INTEGER, DateAndTime vruid OBJECT-TYPE SYNTAX INTEGER (1..2147483647) not-accessible "The VRU number associated with this VRU entity. Note this is a unique number within the VRU network." ::= { vrutableentry 1 } vruipaddress OBJECT-TYPE SYNTAX IpAddress read-only "VRU network ip address." ::= { vrutableentry 2 } vrudescr OBJECT-TYPE SYNTAX DisplayString read-write "A textual description of this VRU entity. It is mandatory that this contain only printable ASCII characters." 94 Simple Network Management Protocol in the Avaya Media Processing Server Environment October 2014

Detailed Component Structure ::= { vrutableentry 3 } vrulinecnt OBJECT-TYPE SYNTAX INTEGER (0..2147483647) read-only "Number of physical phone lines on this system." ::= { vrutableentry 4 } vruspancnt OBJECT-TYPE SYNTAX INTEGER (0..2147483647) read-only "Number of spans on this system. This also indicates the number of rows in the spantable(4) for this VRU." ::= { vrutableentry 5 } vruhostcnt OBJECT-TYPE SYNTAX INTEGER (0..2147483647) read-only "Number of hosts defined for this system. This also indicates the number of rows in the hosttable(6) for this VRU." ::= { vrutableentry 6 } vruadminstate OBJECT-TYPE SYNTAX INTEGER { } other(1), startup(2), shutdown(3), recycle(4), selftest(5), checkpoint(6)-- save any dynamic info to disk read-write October 2014 Simple Network Management Protocol in the Avaya Media Processing Server Environment 95

Periphonics MIB Reference "The network managers desired state of this VRU entity." ::= { vrutableentry 7 } vrustate OBJECT-TYPE SYNTAX INTEGER { other(1), unknown(2), init(3), up(4), down(5), selftest(6) } read-only "The status of the VRU entity." ::= { vrutableentry 8 } vrustatelastchange OBJECT-TYPE SYNTAX DateAndTime read-only "Date and time that this VRU entity changed its state." ::= { vrutableentry 9 } -- -- Line Subtree -- linetable OBJECT-TYPE SYNTAX SEQUENCE OF LineTableEntry not-accessible "All physical and logical lines that are attached to a Voice Response Unit (VRU)." ::= { vrunetwork 4 } linetableentry OBJECT-TYPE SYNTAX LineTableEntry not-accessible 96 Simple Network Management Protocol in the Avaya Media Processing Server Environment October 2014

Detailed Component Structure "A (conceptual) entry for one physical or logical line." INDEX { linevruid, lineid } ::= { linetable 1 } LineTableEntry ::= SEQUENCE { linevruid lineid linetype lineprotocol linestate lineappname lineappoverlay lineappadminstate lineappstate lineappstatelastchange lineappcfglastchange } INTEGER, INTEGER, INTEGER, INTEGER, INTEGER, DisplayString, DisplayString, INTEGER, INTEGER, DateAndTime, DateAndTime linevruid OBJECT-TYPE SYNTAX INTEGER (1..2147483647) not-accessible "The VRU identifier that this phone line is associated with." ::= { linetableentry 1 } lineid OBJECT-TYPE SYNTAX INTEGER (1..2147483647) not-accessible "The line number of this phone line. This number is unique for each VRU." ::= { linetableentry 2 } linetype OBJECT-TYPE October 2014 Simple Network Management Protocol in the Avaya Media Processing Server Environment 97

Periphonics MIB Reference SYNTAX INTEGER { other(1), unknown(2), virtual(3), analog(4), digital(5) } read-only "Specifies whether this line is a logical(3) or a physical(4) phone line. A line type of unknown(2) indicates that you cannot determine the line type at this moment." ::= { linetableentry 3 } lineprotocol OBJECT-TYPE SYNTAX INTEGER (1..2147483647) read-only "A value that indicates the set of protocols offered by this phone line. The value is a sum. This value initially takes the value of zero indicating that the protocol is unknown. Then, for each protocol that this line supports, its protocol value is added to the sum. Value 0x00001 0x00002 0x00004 0x00008 0x00010 0x00020 0x00040 0x00080 0x00100 0x00200 0x00400 0x00800 0x01000 0x02000 0x04000 0x08000 0x10000 0x20000 Functionality Uses some other type of protocol Some analog protocol AT&T Bell release British Paging (BTUK/MCP) Channel bank with 2 wire option Channel bank with 2 wire FXOR else FXO Channel bank with 4 wire E&M Channel bank FSX[r] else FXO[R] Channel bank loop start else ground Channel bank standard access Common channel signalling (SS7) Galaxy 5/2 ACD ISDN Loop hangup supervision Mercury CAS signalling Network side protocol R1 signaling system R2 signaling with DTMF outdial 98 Simple Network Management Protocol in the Avaya Media Processing Server Environment October 2014

Detailed Component Structure ::= { linetableentry 4 } 0x40000 " R2 signaling system linestate OBJECT-TYPE SYNTAX INTEGER { } other(1), unknown(2), connected(3), idle(4), busy(5), referral(6), down(7) read-only "Current state of this line. The line may be ly servicing a call (connected), in service but not in a call service or referral state (idle), not in service nor down (busy), referral (referral), or down (down). If we are unable to connect to the VRU than the line state is unknown (unknown). A logical line (line) state is always unknown." ::= { linetableentry 5 } lineappname OBJECT-TYPE SYNTAX DisplayString read-write "The name of the application that is ly assigned to this line. Any response PDU on this object returns the name of the application assigned to this line. If there is no application assigned to this line, a 0 length string is returned. Assigning a new application to this line is achieved by setting lineappadminstate to assign and this object to the applications name." ::= { linetableentry 6 } lineappoverlay OBJECT-TYPE SYNTAX DisplayString read-only "The name of the application that is linked to this line." ::= { linetableentry 7 } October 2014 Simple Network Management Protocol in the Avaya Media Processing Server Environment 99

Periphonics MIB Reference lineappadminstate OBJECT-TYPE SYNTAX INTEGER { } other(1), startapp(2), softterm(3), hardterm(4), assign(5), unassign(6), hardrestart(7), softrestart(8) read-write "Desired state that Network Manager wants the application in." ::= { linetableentry 8 } lineappstate OBJECT-TYPE SYNTAX INTEGER { } other(1), unknown(2), noapp(3), init(4), up(5), down(6), config(7), exit(8) read-only "Current state of the application that is assigned to this logical line. If no applications are assigned this entry it is noapp(3)." ::= { linetableentry 9 } lineappstatelastchange OBJECT-TYPE SYNTAX DateAndTime read-only "Date and time that the application assigned to this line last changed its state." ::= { linetableentry 10 } lineappcfglastchange OBJECT-TYPE SYNTAX DateAndTime read-only "Date and time of last application configure or reconfigure on this line." 100 Simple Network Management Protocol in the Avaya Media Processing Server Environment October 2014

Detailed Component Structure ::= { linetableentry 11 } --- --- Span Table --- spantable OBJECT-TYPE SYNTAX SEQUENCE OF SpanTableEntry not-accessible "All spans which are attached to a Voice Response Unit (VRU)." ::= { vrunetwork 5 } spantableentry OBJECT-TYPE SYNTAX SpanTableEntry not-accessible "A (conceptual) entry for one span." INDEX { spanvruid, spanid } ::= { spantable 1 } SpanTableEntry ::= SEQUENCE { spanvruid spanid spanlineidstart spanlinenumber spanenabled spanstate spanstatelastchange } INTEGER, INTEGER, INTEGER, INTEGER, TruthValue, INTEGER, DateAndTime spanvruid OBJECT-TYPE SYNTAX INTEGER (1..2147483647) not-accessible "VRU identifier that this span is associated with." October 2014 Simple Network Management Protocol in the Avaya Media Processing Server Environment 101

Periphonics MIB Reference ::= { spantableentry 1 } spanid OBJECT-TYPE SYNTAX INTEGER (1..2147483647) not-accessible "Identifier of this span." ::= { spantableentry 2 } spanlineidstart OBJECT-TYPE SYNTAX INTEGER (1..2147483647) read-only "Line id of the first line in this span." ::= { spantableentry 3 } spanlinenumber OBJECT-TYPE SYNTAX INTEGER { europalinenumber(30), usalinenumber(24) } read-only "Number of lines in this span." ::= { spantableentry 4 } spanenabled OBJECT-TYPE SYNTAX TruthValue read-only "Indicates whether span is enabled or disabled. A value of true(1) indicates span is enabled and a value of false(2) indicates span is disabled." 102 Simple Network Management Protocol in the Avaya Media Processing Server Environment October 2014

Detailed Component Structure ::= { spantableentry 5 } spanstate OBJECT-TYPE SYNTAX INTEGER { } other(1), unknown(2),-- span state can not be determined init(3),-- span is in an initial state green(4),-- span is online and ready fatal(5),-- span entered failed signal state yellow(6),-- span is in yellow state red(7)-- span is in red state read-only "Current state of this span." ::= { spantableentry 6 } spanstatelastchange OBJECT-TYPE SYNTAX DateAndTime read-only "Date and time that the span last changed its state." ::= { spantableentry 7 } -- -- Applications Subtree -- apptable OBJECT-TYPE SYNTAX SEQUENCE OF AppTableEntry not-accessible "All applications that VRU ly knows about." ::= { vrunetwork 6 } apptableentry OBJECT-TYPE SYNTAX AppTableEntry not-accessible October 2014 Simple Network Management Protocol in the Avaya Media Processing Server Environment 103

Periphonics MIB Reference "A (conceptual) entry for one VRU application" INDEX { appvruid, IMPLIED appname } ::= { apptable 1 } AppTableEntry ::= SEQUENCE { appvruid appname appdescr appoptions applinecnt } INTEGER, DisplayString, DisplayString, DisplayString, INTEGER appvruid OBJECT-TYPE SYNTAX INTEGER(1..2147483647) not-accessible "VRU id that this application is assigned to." ::= { apptableentry 1 } appname OBJECT-TYPE SYNTAX DisplayString ( SIZE(1..255) ) not-accessible "The name of the application that can been assigned to a line. This name must be unique for each VRU." ::= { apptableentry 2 } appdescr OBJECT-TYPE SYNTAX DisplayString read-write 104 Simple Network Management Protocol in the Avaya Media Processing Server Environment October 2014

Detailed Component Structure "A textual description of this application. It is mandatory that this contain only printable ASCII characters." ::= { apptableentry 3 } appoptions OBJECT-TYPE SYNTAX DisplayString read-only "The options that are needed during this applications startup." ::= { apptableentry 4 } applinecnt OBJECT-TYPE SYNTAX INTEGER(0..2147483647) read-only "The number of lines that this application is assigned to." ::= { apptableentry 5 } -- -- Applications Stats Subtree -- appstatstable OBJECT-TYPE SYNTAX SEQUENCE OF AppStatsTableEntry not-accessible "All application specific stats that are collected." ::= { vrunetwork 7 } appstatstableentry OBJECT-TYPE SYNTAX AppStatsTableEntry not-accessible "A (conceptual) entry for one application stat." October 2014 Simple Network Management Protocol in the Avaya Media Processing Server Environment 105

Periphonics MIB Reference INDEX { appstatsvruid, IMPLIED appstatsname ::= { appstatstable 1 } AppStatsTableEntry ::= SEQUENCE { appstatsvruid appstatsname appstatsvalue appstatslastchange } INTEGER, DisplayString, INTEGER, DateAndTime appstatsvruid OBJECT-TYPE SYNTAX INTEGER (1..2147483647) not-accessible "The VRU identifier that this application statistic is associated with." ::= { appstatstableentry 1 } appstatsname OBJECT-TYPE SYNTAX DisplayString ( SIZE(1..255) ) not-accessible "Name which identifies this application stat." ::= { appstatstableentry 2 } appstatsvalue OBJECT-TYPE SYNTAX INTEGER (1..2147483647) read-only "An application stats value. This value is gathered on 15-minute intervals." ::= { appstatstableentry 3 } 106 Simple Network Management Protocol in the Avaya Media Processing Server Environment October 2014

Detailed Component Structure appstatslastchange OBJECT-TYPE SYNTAX DateAndTime read-only "Date and time when this application stat was recorded." ::= { appstatstableentry 4 } -- -- Host Subtree -- hosttable OBJECT-TYPE SYNTAX SEQUENCE OF HostTableEntry not-accessible "All hosts defined for a VRU." ::= { vrunetwork 8 } hosttableentry OBJECT-TYPE SYNTAX HostTableEntry not-accessible "A (conceptual) entry for one VRU host." INDEX { hostvruid, hostid } ::= { hosttable 1 } HostTableEntry ::= SEQUENCE { hostvruid hostid hostdescr hostlucnt hostprotocol hostmedia hostadminstate hoststate hoststatelastchange INTEGER, INTEGER, DisplayString, INTEGER, INTEGER, INTEGER, INTEGER, INTEGER, DateAndTime October 2014 Simple Network Management Protocol in the Avaya Media Processing Server Environment 107

Periphonics MIB Reference } hostvruid OBJECT-TYPE SYNTAX INTEGER (1..2147483647) not-accessible "The VRU identifier that this host is associated with." ::= { hosttableentry 1 } hostid OBJECT-TYPE SYNTAX INTEGER (1..2147483647) not-accessible "Unique identifier associated with this host." ::= { hosttableentry 2 } hostdescr OBJECT-TYPE SYNTAX DisplayString read-write "A textual description of this host. It is mandatory that this contain only printable ASCII characters." ::= { hosttableentry 3 } hostlucnt OBJECT-TYPE SYNTAX INTEGER (0..2147483647) read-only "Number of logical units (LU) defined for this host. This also indicates the number of rows in the lutable(7) for this host." ::= { hosttableentry 4 } 108 Simple Network Management Protocol in the Avaya Media Processing Server Environment October 2014

Detailed Component Structure hostprotocol OBJECT-TYPE SYNTAX INTEGER { other(1), unknown(2), atte(3), async(4), lu62(5), sna3270(6), sdlcexp(7), vpstn3270(8) } read-only "Protocol which is used for host communications." ::= { hosttableentry 5 } hostmedia OBJECT-TYPE SYNTAX INTEGER { other(1), unknown(2), hardwarebased(3), softwarebased(4) } read-only "Media used for communicating with the host." ::= { hosttableentry 6 } hostadminstate OBJECT-TYPE SYNTAX INTEGER { other(1), init(2), up(3), down(4), recycle(5), selftest(6) } read-write "Desired state that Network Manager wants the host in." ::= { hosttableentry 8 } hoststate OBJECT-TYPE SYNTAX INTEGER { other(1), unknown(2), init(3), up(4), down(5), selftest(6) } read-only October 2014 Simple Network Management Protocol in the Avaya Media Processing Server Environment 109

Periphonics MIB Reference "Current state of the host." ::= { hosttableentry 9 } hoststatelastchange OBJECT-TYPE SYNTAX DateAndTime read-only "Date and time this host last changed it state." ::= { hosttableentry 10 } -- -- LU Subtree -- lutable OBJECT-TYPE SYNTAX SEQUENCE OF LuTableEntry not-accessible "All LU defined for hosts on a VRU." ::= { vrunetwork 9 } lutableentry OBJECT-TYPE SYNTAX LuTableEntry not-accessible "A (conceptual) entry for one LU." INDEX { luvruid, luhostid, luid } ::= { lutable 1 } LuTableEntry ::= SEQUENCE { luvruid luhostid luid ludescr INTEGER, INTEGER, INTEGER, DisplayString, 110 Simple Network Management Protocol in the Avaya Media Processing Server Environment October 2014

Detailed Component Structure } lupoolname lustate lustatelastchange DisplayString, INTEGER, DateAndTime luvruid OBJECT-TYPE SYNTAX INTEGER (1..2147483647) not-accessible "VRU entity that this LU is associated with." ::= { lutableentry 1 } luhostid OBJECT-TYPE SYNTAX INTEGER (1..2147483647) not-accessible "Host entity that this LU is associated with." ::= { lutableentry 2 } luid OBJECT-TYPE SYNTAX INTEGER (1..2147483647) not-accessible "LU identifier that is associated with this LU." ::= { lutableentry 3 } ludescr OBJECT-TYPE SYNTAX DisplayString read-only October 2014 Simple Network Management Protocol in the Avaya Media Processing Server Environment 111

Periphonics MIB Reference "A textual description of this LU. It is mandatory that this contain only printable ASCII characters." ::= { lutableentry 4 } lupoolname OBJECT-TYPE SYNTAX DisplayString read-only "Pool name that this LU is assigned to." ::= { lutableentry 5 } lustate OBJECT-TYPE SYNTAX INTEGER { other(1), unknown(2), init(3), up(4), down(5) } read-only "Current state of this LU." ::= { lutableentry 6 } lustatelastchange OBJECT-TYPE SYNTAX DateAndTime read-only "Date and time this LU last changed its state." ::= { lutableentry 7 } -- -- Component Subtree -- components OBJECT IDENTIFIER ::= { vrunetwork 10 } -- --Table of all defined component types -- componenttypetable OBJECT-TYPE 112 Simple Network Management Protocol in the Avaya Media Processing Server Environment October 2014

Detailed Component Structure SYNTAX SEQUENCE OF ComponentTypeTableEntry not-accessible "All defined component types." ::= { components 1 } componenttypetableentry OBJECT-TYPE SYNTAX ComponentTypeTableEntry not-accessible "A (conceptual) entry for one component type." INDEX { componenttypeid } ::= { componenttypetable 1 } ComponentTypeTableEntry ::= SEQUENCE { componenttypeid INTEGER, componenttypename DisplayString } componenttypeid OBJECT-TYPE SYNTAX INTEGER (1..2147483647) not-accessible "Identifier for this component type." ::= { componenttypetableentry 1 } componenttypename OBJECT-TYPE SYNTAX DisplayString read-only "Name of this component type." October 2014 Simple Network Management Protocol in the Avaya Media Processing Server Environment 113

Periphonics MIB Reference ::= { componenttypetableentry 2 } -- --Table of all components an agent knows about. -- componenttable OBJECT-TYPE SYNTAX SEQUENCE OF ComponentTableEntry not-accessible "All components found in the system." ::= { components 3 } componenttableentry OBJECT-TYPE SYNTAX ComponentTableEntry not-accessible "A (conceptual) entry for one component." INDEX { componenttype, componentid } ::= { componenttable 1 } ComponentTableEntry ::= SEQUENCE { componenttype componentid componentipaddress componentstate componentstatelastchange } INTEGER, INTEGER, IpAddress, INTEGER, DateAndTime componenttype OBJECT-TYPE SYNTAX INTEGER (1..2147483647) not-accessible "Type of this component." ::= { componenttableentry 1 } 114 Simple Network Management Protocol in the Avaya Media Processing Server Environment October 2014

Detailed Component Structure componentid OBJECT-TYPE SYNTAX INTEGER (1..2147483647) not-accessible "Identifier of this component." ::= { componenttableentry 2 } componentipaddress OBJECT-TYPE SYNTAX IpAddress read-only "IP address of this component." ::= { componenttableentry 3 } componentstate OBJECT-TYPE SYNTAX INTEGER { other (1) unknown (2) init (3) up (4) down (5) } read-only "Current state of this component." ::= { componenttableentry 4 } componentstatelastchange OBJECT-TYPE SYNTAX DateAndTime read-only "Date and time this component last changed its state." ::= { componenttableentry 5 } END October 2014 Simple Network Management Protocol in the Avaya Media Processing Server Environment 115

Chapter 7: Request For Comment (RFC) This chapter covers: 1. Access to RFCs 2. Table of RFC Access to RFCs RFCs are available from http://tools.ietf.org. An RFC can be viewed or downloaded by web browser in plain text, HTML or PDF formats, using the following URLs, where XXXX is the RFC number: TEXT: http://tools.ietf.org/rfc/rfcxxxx HTML: http://tools.ietf.org/html/rfcxxxx PDF: http://tools.ietf.org/pdf/rfcxxxx Tables of RFC The following table lists topic RFC that are of relevance with regard to SNMPv1. RFC Number RFC 1155 RFC 1156 RFC 1157 RFC 1212 RFC 1213 RFC 1215 RFC Title Structure of Management Information Management Information Base for Network Management of TCP/IP-Based Internets SNMP V1 Protocol Concise MIB Definitions Management Information Base II A Convention for Defining Traps for use with the SNMP The following table lists topic RFC that are of relevance with regard to SNMPv2c. 116 Simple Network Management Protocol in the Avaya Media Processing Server Environment October 2014

Tables of RFC RFC Number RFC 1901 RFC 1902 RFC 1903 RFC 1904 RFC 1905 RFC 1906 RFC 1907 RFC 1908 RFC Title Community Based SNMPv2c MIB for SNMPv2c Textual Conventions for SNMPv2c Conformance Statements for SNMPv2c Protocol Operations for SNMPv2c Transport Mappings for SNMPv2c MIB for SNMPv2c Coexistence Between SNMPv1 and SNMPv2c October 2014 Simple Network Management Protocol in the Avaya Media Processing Server Environment 117

Index A Abstract Syntax Notation One... 7 access control...24 access rights...33 fields... 33 format... 33 tag...33 agent...7, 39 alarms Periphonics MIB... 51 alrmlogcode... 51, 61 alrmlogcomponentid... 44, 51, 61 alrmlogcomponentipaddress... 51 alrmlogcomponenttype... 51, 61 alrmloghostid... 51, 61 alrmlogidx... 51 alrmloglineid... 51, 61 alrmlogmax... 51 alrmlogmessage... 51, 61 alrmlognumber... 51 alrmlogprocname...51, 61 alrmlogseverity...51, 61 alrmlogtable...51 alrmlogtime...51, 61 alrmlogvruid... 44 applications...55 defining parameters of...66 applications statistics... 55, 67 application types... 9 applinecnt... 55, 66 appname... 55, 66 appoptions... 55, 66 appstatslastchange... 55, 67 appstatsname... 55, 67 appstatstable...55 appstatsvalue... 55, 67 appstatsvruid... 55, 67 apptable...55 appvruid... 55, 66 architecture... 42 architecture;mps (VPS/is) environment illustration... 42 ASN.1... 7 assigning security name to a community...31 automatically configuring trap destinations...17 automatically defining trap destinations...17 Avaya MIB; tree structure... 78 Avaya MPS/VPS Resources Daemon... 29 C client... 7 client/server architecture...7 command snmpbulkget... 40 command line options...29 command line utilities... 40 commands alarm command...48 alarmd:and the MPS (VPS/is) components subagent.. 51 alarmd:process and daemon... 48, 51 snmpget...40 snmpgetnext... 40 snmpset... 40 snmptable... 40 snmptrapd...40, 48 snmptrapd to view... 48 snmpwalk...40 commands:s19snmp.startup... 21 community strings...24 componenteventsgroup... 44 componenteventsgroup2... 44 componentid... 57, 68 componentipaddress...57 componentnotificationsgroup... 44 componentnotificationsgroup2... 44 componentstate...57 componentstatelastchange... 57, 68 componenttable... 57 componenttype... 57 componenttypeid... 57 componenttypename... 57 component types, defining...57 componenttypetable... 57 configuration files...24 converting community strings...36 group access rights... 37 group associations...36 SNMP configuration to Net-SNMP... 36 trap destinations... 38 view subtrees...37 D default trap community... 35 defining alarms...61 default trap community... 35 security groups... 32 trap destinations... 34 view subtrees...33 defining components...68 defining component types...57 deprecated objects (and their replacements)... 44 118 Simple Network Management Protocol in the Avaya Media Processing Server Environment October 2014

Index E environment variables...25, 29 establishing subtrees...31 views...31 Events Group Notifications... 60 executables...39 G get-bulk-request...10, 12, 33 get-next-request...11, 33 get-request...10, 11, 33 get-response...12 H host... 56 hostadminstate... 56 hostid... 56, 67 hostlucnt... 56, 67 hostmedia... 56 hostprotocol...56, 67 hoststate...56, 67, 68 hoststatelastchange... 56 hosttable... 56 hostvruid... 56, 67 I inform-request...10, 13, 33 installing the PERIsnmp package... 16 interaction, manager and agent... 11, 13 IP address...50 L lineappadminstate... 53 lineappname... 53, 63 lineappoverlay... 53, 63 lineappstate... 53, 63 lineappstatecfgchange... 53, 63 lineappstatelastchange... 53, 63 lineid... 53, 63 line mapping phone...63 lineprotocol... 53 lines... 63 linestate...53, 63 linetable... 53 linetype... 53, 63 linevruid...53, 63 linked applications... 53, 63 logical unit...57 LU... 57 luhostid...57, 68 luid... 57, 68 lupoolname... 57 lustate...57 lustatelastchange... 57 lutable... 57 luvruid... 57, 68 M management agent...7 Management Information Base...7 management station... 7 master agent...21 MIB... 7 Components... 68 Host... 67 subtrees...67, 68 MIB;tree illustration... 7 mib2agt... 21, 39 MIB2AGT_CMDLINEARGS...29 MIB-II illustration... 7 MIB variables... 43 MPS (VPS/is) environment... 42, 52 MPS environment... 62 MPS Manager...68 MPS Host Status... 67, 68 MPS Processing Server Manager MPS Span Status... 65 MPS Reporter... 67 msnsaagt.exe... 29, 39 N network elements...7 network management components...7 node names... 9 notifyalarm...44 notifyalarmbycomponent... 44, 61 notifyalarmbycomponentex...44, 48, 60 notifycomponentstatechg...44, 50, 60 notifyhoststatechg...50, 60 notifylineappstatechg... 50, 60 notifylustatechg... 50 notifyspanstatechg...50, 60 notifytopologychg...50 notifyvrustatechg...44 O Object Identifier...9 objects:deprecated and replacements...44 objects:status information... 44 OID... 9, 24, 50, 57 OID translations... 24 October 2014 Simple Network Management Protocol in the Avaya Media Processing Server Environment 119

Index P Periphonics Enterprise MIB; detailed component structure. 81 Periphonicsv1.mib... 23 Periphonicsv2.mib... 23 PeriView ActivityMonitor... 60 Activity Monitor... 62, 68 alarm viewers... 60 Application Status...60, 63, 66 APPMAN... 60, 62, 63, 66, 68 Assign/(Re)Start Lines...63, 66 Configure Application... 66 Host Status... 63, 66 Launcher...60, 62, 66, 68 Line Start Order During Reboot...63, 66 MPS Host Status... 60 MPS Span Status... 60, 62, 65 PLM Line Status Bar Graph...62 PLM Status Report... 63 Span Status... 63, 66 SRP Group Status Report... 68 SRP Status Report... 62, 63, 68 Terminate/Un-Assign Lines... 63, 66 VPS/VAS Status... 63, 66 VSH Tool... 62, 63, 68 PeriView:Line Start Order During Reboot...63, 66 PeriView:Span Status... 63, 66 PeriView:VPS/VAS Status... 63, 66 PeriView:workstation... 7 phone line mapping... 63 principles of components... 15 private enterprises... 7, 9 protocol... 7 host...56, 67 protocol;line... 53 protocol;see also SNMP[protocol;zzz]... 7 protocol:host... 56, 67 R rebooting workstation...16 Request For Comment... 116 RFC... 116 S scalar... 9 server...7 set-request...12, 33 setting a value...48 SMI... 9 SMIv1...23 SMIv2...23 SNMP... 7, 13 SNMP_PERSISTENT_DIR...28 SNMP;and MPS (VPS/is) integration...14 snmp.sh... 21 SNMP and MPS (VPS/is) integration...42 SNMPCONFPATH...28 snmpd.conf... 13, 24, 28 snmpdm... 21, 28, 39 SNMPDM_CMDLINEARGS... 29 snmpdm.exe... 29, 39 SNMP EMANATE Adapter for NT... 29 SNMP EMANATE Master Agent...29 snmpinfo.dat... 24 SNMP protocol stack replacement... 6 SNMPv1...10 SNMPv2c...10 SNMP versus PeriView...14 snmpwalk command example... 19 spanenabled...54, 65 spanid... 54, 65 spanlineidstart...54, 65 spanlinenumber... 54, 65 spans... 54 spanstate...54, 65 spanstatelastchange... 54 spantable... 54 spanvruid... 54, 65 SRP starting and stopping... 48 starting agent... 16 starting and stopping SRP... 48 Structure of Management Information... 9 subagent... 20, 39 subtree...7, 53 Applications... 66 Components... 68 Events Group Notifications... 60 Host... 67 Line...53, 63 VRU... 62 subtree:line... 53, 63 syscontact... 30, 59 sysdescr... 30, 59 syslocation...30, 59 sysname...30, 59 system tree illustration... 11 T tables alarm log...51 tables:applications... 55 tables:application statistics... 55 tables:component... 57 tables:component type...57 tables:host... 56 tables:line...53 tables:lu...57 tables:span... 54 120 Simple Network Management Protocol in the Avaya Media Processing Server Environment October 2014

Index transports...24 trapcfg.pl... 13, 17 trap destinations... 34 trap messages... 33 traprcv...74 traps...10, 13, 24, 50, 60 multiple configuration example... 48 using... 48 viewing...48 U using MIB variables... 50, 57 using SNMP messages... 11, 13 using SNMP with the MIB... 10 V variables analogies to MPS Manager... 68 as used in MIB...50, 68 enterprise MIB... 60 OIDs... 50 setting a value... 48 variables:querying directly... 45 variables:table querying...45 verifying agent response...19 vrsnmpd... 39 VRSNMPD_CMDLINEARGS... 29 vrsnmpd.exe... 29, 39 VRU... 45, 62 VRU_Networkv1.mib... 23 VRU_Networkv2.mib... 23 vruadminstate... 52 vrueventsgroup...44 vruhostcnt...52, 62 vruid...52, 62 vruipaddress...52 vrulinecnt... 52, 62 VRU Network... 23, 52, 62 vrunetworkmibcompliance... 44 vrunetworkmibcompliancebycomponent... 44 vrunetworkmibcompliancebycomponent2... 44 vrunotificationsgroup... 44 vruspancnt...52, 62 vrustate... 62 vrustatelastchange... 52, 62 vrutable...45, 52 VT... 57 W workstation...7 October 2014 Simple Network Management Protocol in the Avaya Media Processing Server Environment 121