NEC AMERICA, INC. Product Development Evaluation Division NEAX IPX /NEAX IPS. SNMP Implementation

Transcription

1 NEC AMERICA, INC. Product Development Evaluation Division NEAX IPX /NEAX IPS SNMP Implementation

2 PRODUCT DEVELOPMENT EVALUATION DIVISION IPX/IPS SNMP Implementation NEC America, Inc N. State Highway 161 Irving, Texas Phone (800)

3 Table of Contents Introduction i CHAPTER 1 SNMP Basics 1 The SNMP Model 2 Manageable Objects 2 The SNMP Protocol 3 SNMP Message Format 4 ASN.1 and BER 6 Structure of Management Information 7 Object Identifier 8 Management Information Base 10 SNMP Traps 13 CHAPTER 2 NEAX IPX SNMP Configuration 14 NEAX IPS SNMP Configuration 27 Address Translation Group 39 IP Group 40 ip Inbound Counters 40 ip Outbound Counters 41 Fragmentation Counters 41 ip Address Table 42 ip Route Table 43 Net to Media Table 44 ICMP Group 44 ICMP Inbound Counters 44 ICMP Variation Outbound Counters 45 ICMP Diagnostic Outbound Counters 45 TCP Group 46 TCP Connection Objects 47 TCP Segment Counters 47 TCP Connection Table 48 TCP MIB-II additions 48 CHAPTER 3 MIB Groups 35 System Group 36 Interface Group 37 iftypes 37 if Troubleshooting 38 if Inbound Counters 38 if Outbound Counters 39 UDP Group 49 UDP Table 49 EGP Group 49 EGP I/O Counters 49 EGP Neighbor Table 50 EGP Neighbor Table I/O Counters 50 EGP Group Completion 50 SNMP Group 51 SNMP Inbound Errors 51 SNMP Inbound Activity Counters 51 SNMP Outbound Errors 52 SNMP Outbound PDU Counter 52

4 CHAPTER 4 Supported MIB Groups by Platform 53 NEAX IPX 54 NEAX IPS 54 NEAX IPX Specific OID S 55 NEAX IPS Specific OID S 55 APPENDIX A 57 Security Issues 58 APPENDIX B 61 PBX-MIB File 61 References 65

5 INTRODUCTION With the release of the NEAX 2400IPX and the NEAX IPS systems, managing each platform on a network environment has become a MUST know aspect of maintenance. It must be understood that a negative impact on the network by any of the two platforms must be rectified as soon as possible. As a shared environment, we must assure that our VoIP implementation does not cause any degradation to the network. In the event that it does, we must be prepared to identify the problem as quickly as possible. Both platforms incorporate, Translation through time-division multiplexing (TDM), where it uses either TDM equipment or VoIP gateways to translate from one protocol to another (TDM no.1 <-> VoIP <-> TDM no.2) or (VoIP no.1 <-> TDM <-> VoIP no. 2). It is the protocol side of the equation that SNMP relies on to gather information. SNMP (Simple Network Management Protocol) is widely used throughout the IT field, for the purpose of managing network devices such as routers, bridges, switches, hubs, Network Interface cards (NIC s), and now the PBX. The IAB (Internet Activities Board) recommends that all IP and TCP implementations be network manageable (RFC 1155). In its simplest form, network management is actually managing networked systems (devices) and the resources that tie them together. In the following chapters, we will attempt to give you the necessary tools for managing and troubleshooting the IPX / IPS as part of the network. It is assumed that the reader has general networking knowledge. I

6 SNMP FOR NEAX2000IPS/NEAX2400IPX Chapter 1 SNMP Basics This chapter is designed to familiarize the reader with SNMP terms, concepts and a description of Managers, Agents, SNMP and how they work. 1

7 The SNMP Model Simple Network Management Protocol (SNMP) uses a manager/agent communications concept. Vendors develop the manager software for retrieving the information from an agent. The manager, also known as the NMS (Network Management Station) requests the information in a certain format and the agent then makes the information available, or a reason why is not available. The communication can be two way: the manager asking the agent for a specific value ( the size of the largest datagram which can be sent/received on the interface ), or the agent telling the manager that something has gone wrong ( the current operational state of the interface ). The manager should also be able to change or set variables in the agent ( change the value of the default IP TTL to 64 ), in addition to reading them. Manageable Objects The Network Management Software uses the Manageable Objects Database (MOD) as a data dictionary of information it can retrieve from each managed device or agent. User Interface Management Application Managed System / Device (PBX) Network Management Engine Agent MOD MOD UDP IP SNMP IPX DDP UDP IP SNMP IPX DDP Network Interface Network Interface Figure 1-1 SNMP Model 2

8 Usually, the network administrator maintains the database by compiling one or more MIB s into the MOD. A MIB is a virtual database that identifies each manageable device on the network by its name, syntax, accessibility, status, a text description and a unique manageable-object Identifier (OID). These MIB s can be identified as either public, experimental or Private Enterprise. Details on MIB and OID will be discussed later on this chapter. The SNMP Protocol SNMP defines five types of messages that are exchanged between the manager and the agent. 1. get-request / fetch the value of one or more variables. 2. get-next-request / Fetch the next variable after one or more specified variables. 3. set-request / Set the value of one or more variables. 4. get-response / Return the value of one or more variables. The agent returns this message to the manager in response to the get-request, get-next-request and the setrequest. 5. trap / Notify the manager when something of significance happens on the agent. SNMP Manager SNMP Agent (PBX) get-request UDP port 161 get-response get-next-request UDP port 161 get-response set-request UDP port 161 get-response UDP port 162 trap Figure 1-2.Five SNMP operators 3

9 The first, three messages are sent by the manager to the agent, and the last two from the agent to the manager. These are typically referred to as the get, get-next, and set operators. Since four of the five SNMP messages are simple request-reply protocols, SNMP uses UDP as its transport protocol. Being that UDP is a connectionless protocol, therefore unreliable, a request from the manager may not arrive at the agent, and the agent s reply may not make it to the manager. As seen on figure 1-2., the manager sends its three requests to UDP port 161 and traps on UDP port 162. By using two different port numbers, a system can run both a manager and an agent. SNMP Message Format As stated earlier, SNMP uses UDP as its transport protocol. Therefore all five SNMP messages are encapsulated in a UDP datagram. This information can be captured and viewed using a network analyzer. Figure 1-3. shows the format of the five SNMP messages. IP datagram UDP datagram SNMP Message common SNMP header get / set header variables to get / set IP UDP version PDU type request error error community header header (0) type ID status index name value name value (0-3) (0-5) 20 bytes 8 bytes PDU agent trap specific time name type enterprise addr type code stamp value (4) (0-6) trap header interesting variables Figure 1-3. SNMP message format 4

10 The version is 0. This value is the version number minus one, the version of datagram being described in figure 1-3., is called SNMPv1. Other versions are SNMPv2 and SNMPv3. The community is a clear text password used between the manager and the agent. A common value used is the 6-character string public. Most SNMP software defaults to this community name. For security purposes, it is recommended that it be changed. Table 1-1. Shows the different values for the PDU type. PDU stands for Protocol Data Unit, another word for packet. PDU type PDU name 0 get-request 1 get-next-request 2 set-request 3 get-response 4 trap Table 1-1. PDU types for SNMP messages. The request ID is set by the manager when a get, get-next, and set are sent to the agent. The agent then responds with the get-response message, using the same request ID. The error status is an integer that the agent may return specifying an error. See Table 1-2 for values. error status 0 Name noerror toobig nosuchname badvalue readonly generr Description all is OK agent could not fit reply into a single SNMP message operation specified a nonexistent variable a set operation specified an invalid value or syntax manager tried to modify a read-only variable some other error Table 1-2. SNMP error status values The error index is an integer offset that specifies which variable was in error. It is only set by the agent for the nosuchname, badvalue and readonly errors. Note: The trap message format will be discussed later in the chapter. 5

11 ASN.1 and BER The details of ANS.1 and BER are only important to software developers of SNMP. They are not critical to the understanding of network management. It is included in the chapter for the purpose of understanding where the actual translation occurs. ASN.1 is a language that describes data and the properties of the data. It does not tell you how the data is stored or encoded. Fields in the MIB and SNMP messages are described using ASN.1. As an example, the definition for the data type IpAddress from the SMI (Structure of Management Information, RFC 1155), looks like this: IpAddress ::= {APPLICATION 0} -- in network-byte order IMPLICIT OCTET STRING (SIZE (4)) From the MIB (Management Information Base, RFC 1156) the definition of a simple variable looks like this: UdpNoPorts OBJECT-TYPE SYNTAX Counter ACCESS Read-Only STATUS Mandatory DESCRIPTION The total number of received UDP datagrams for which there was no application at the destination port. :: = { udp 2 } Note: See SMI (Structure of Management Information) and MIB (Management Information Base), sections for details. 6

12 Structure of Management Information Structure of Management Information (SMI) identifies the type of data in the message and the database. ASN.1 is used to encode the information into a proper request and response. SNMP uses different data types. They are listed here without the ASN.1 encoding. INTEGER- Some variables are declared as an integer with no restrictions (e.g., the MTU of an interface), some are defined with specific values (e.g., the IP forwarding flag is 1 if forwarding is enabled, 2 if forwarding is disable). Others can be defined with a minimum and a maximum value (e.g., UDP and TCP ports numbers are between 0 and 65535). OCTET STRING- A string of 0 or more 8-bit bytes. Each byte has a value between 0 and 255. DisplayString- A string of 0 or more 8-bit bytes. OBJECT IDENTIFIER- See OID (Object Identifier) in this chapter. NULL- This indicates that the corresponding variable has no value. It is used as the value of all the variables in a get and get-next request. IpAddress- An OCTET STRING of length 4, with 1 byte for each byte of the IP address. PhysAddress- An OCTET STRING specifying a physical address (e.g., a 6-byte Ethernet Address). Counter- A nonnegative integer whose value increases monotonically from 0 to (4,294,967,295), and then wraps back to 0. Gauge- A nonnegative integer between 0 and , whose value can increase or decrease, but latches at its maximum value. If the value increments to , it stays there until it is reset. The MIB variable tcpcurrestab is an example: it is the number of TCP connections currently in the ESTABLISHED or CLOSE_WAIT state. TimeTicks- A counter that counts the time in hundredths of a second since some epoch. For example, the variable sysuptime is the number of hundredths of a second that the agent has been up. SEQUENCE- This is similar to a structure in the C programming language. For example, the MIB defines a SEQUENCE named UdpEntry containing information about an agent s active UDP end points. Two entries are in the structure: 1. udplocaladdress, of type Ipaddress, containing the local IP address. 2. udplocalport. Of type INTEGER, in the range 0 through 65535, specifying the local port number. SEQUENCE OF- This is the definition of a vector, with all the elements having the same data type. 7

13 Object Identifier Object Identifiers (OID s) represent each manageable object with a unique sequence of numbers and names. RFC 1155 describes it as: a sequence of integers which traverse a global tree. OID s can also be described as a sequence of integers separated by decimal points. See Figure 1-4. These Identifiers are not assigned randomly, but are allocated by some organization that has responsibility for a group of identifiers. MIB (1) Enterprise (1) Directory (1) Management (2) Experimental (3) Private (4) Internet (1) DOD (6) Standard (0) Registration-Authority (1) Member-Body (2) Identified-Org (3) ITU-T (0) ISO (1) Joint-ISO-ITU-T (2) Root Figure 1-4. Object Identifiers in the Management Information Base. Each MIB starts with the Object Identifier of , and each of the nodes in the tree is also given a textual name. For example, the name that corresponds to Object Identifier is iso.org.dod.internet.management.mib. The names are for ease of readability. In addition to the MIB Object Identifier shown in figure 1-4, we can also see one named, iso.org.dod.internet.private.enterprise ( ). This is where vendor-specific MIB s (RFC 1700) are located. 8

14 Looking at figure 1-5., we can see that the NEC Corporation Private Enterprise code is (iso.org.dod.internet.private.enterprise.nec Corporation). The private enterprise code then branches out to identify objects within the NEC Corporation private MIB. As figure 1-5., shows, the Object Identifiers (OID s) for the NEAX 2400 IPX and the NEAX IPS systems are as follows: (iso.org.dod.internet.private.enterprise.neccorporation.1.pbx.ipx) note that the first branch within NEC Corporation is not identified (iso.org.dod.internet.private.enterprise.neccorporation.1.pbx.ips) note that the first branch within NEC Corporation is not identified. A network administrator would be able to identify these devices on the network as PBX s and each respective platform via the Network Management Station (NMS). IPX (2) IPS (3) PBX (76) Not Identified by NEC/J (1) NEC (119) MIB (1) Enterprise (1) Directory (1) Management (2) Experimental (3) Private (4) Internet (1) DOD (6) Standard (0) Registration-Authority (1) Member-Body (2) Identified-Org (3) ITU-T (0) ISO (1) Joint-ISO-ITU-T (2) Root Figure 1-5. NEC Corporation Private Enterprise Code 9

15 Management Information Base The Management Information Base (MIB) is the database of information maintained by the agent (IPX/IPS systems) that the SNMP manager (NMS) can query or set. The MIB is divided into groups such as system, interface, at (address translation), ip, icmp, tcp, udp, and so on. See figure 1-6. IPX (2) IPS (3) system (1) at (3) icmp (5) udp (7) interfaces (2) ip (4) tcp (6) PBX (76) Not Identified by NEC/J (1) NEC (119) MIB (1) Enterprise (1) Directory (1) Management (2) Experimental (3) Private (4) Internet (1) DOD (6) Standard (0) Registration-Authority (1) Member-Body (2) Identified-Org (3) ITU-T (0) ISO (1) Joint-ISO-ITU-T (2) Root Figure 1-6. Tree Structure We will use RFC 1213 MIB-II as an example for explanation. 10

16 By looking at figure 1-7., we can see that the UDP Group has four variables and a table containing two variables. udplocaladdress (1) udplocalport (2) udpentry (1) udpindatagrams (1) udpnoports (2) udpinerrors (3) udpoutdatagrams (4) udptable (5) MIB II udp (7) mib (1) Figure 1-7. Tree Structure of the UDP Group RFC 1156 (MIB I) defines the first four variables as: udpindatagrams The total number of UDP datagrams delivered to UDP users. udpnoports The total number of received UDP datagrams for which there was no application at the destination port. UdpInErrors The number of UDP datagrams that could not be delivered for reasons other than the lack of an application at the destination port. UdpOutDatagrams The total number of UDP datagrams sent from this entity. RFC 1213 (MIB II), adds a table and two variables, they are described as: UdpTable A table containing UDP listener information. UdpEntry Information about a particular current UDP listener. UdpLocalAddress The local IP address for this UDP listener. In the case of a UDP listener, which is willing to accept datagrams for any interface associated with the node, the value is used. UdpLocalPort The local port number used for this UDP listener. Note: The IPX and the IPS support MIB II. MIB authors must define every managed object and its correct position in the MIB. 11

17 From the MIB (Management Information Base, RFC 1156) the definition of a simple variable looks like this: UdpNoPorts OBJECT-TYPE SYNTAX Counter ACCESS Read-Only STATUS Mandatory DESCRIPTION The total number of received UDP datagrams for which there was no application at the destination port. :: = { udp 2 } Where as: OBJECT-TYPE - gives a name to the manageable object, table or table-entry. SYNTAX The ANSI.1 type ObjectSyntax defines the different syntaxes, which may be used in defining an object type. (RFC 1155) ACCESS This field may be one of read-only, read-write, write-only or not accessible. STATUS This field may contain mandatory, optional or obsolete. DESCRIPTION A textual description of the semantics of the object type. In the example above, the UdpNoPorts is the second item in the MIB II UDP group at

18 SNMP Traps RFC 1157 As we saw on Figure 1-2., SNMP Traps are sent to the manager via UDP Port 162. This message is sent to the manager when something has happened on the agent. Six specific traps are defined in RFC XXXX with a seventh one allowing vendors to implement an enterprise-specific trap. Figure 8. describes the values for the trap type in the trap message format in Figure 1-9. trap type Name coldstart warmstart linkdown linkup Description Agent is initializing itself. Agent is reinitializing itself. An interface has changed from the up to the down state. An interface has changed from thedown to the up state. authenticationfailure A message was received from an SNMP manager with an invalid community. egpneighborloss An EGP peer has changed to the down state. enterprisespecific Look in the specific code field for information on the trap. Figure 1-8. Trap types PDU agent trap specific time name type enterprise addr type code stamp value (4) (0-6) trap header interesting variables Figure 1-9. SNMP Trap message format PDU type field =4 (trap) See Table 1-1. Enterprise field= sysobjectid Agent addr field= Agents IP Address Specific code field= enterprise specific code. This field is 0 on non-enterprise-specific traps Time stamp field= This is a TimeTicks value, representing the number of hundredths of a second since the start of an event. 13

19 Chapter 2 PBX SNMP Configuration This chapter takes the reader through the SNMP set up in the IPX and IPS systems. 14

20 NEAX IPX SNMP Configuration The NEAX IPX platform supports SNMP in R12 or higher. MIB-II is supported based on RFC 1158 and RFC Programming ASYD Index 86 bit 4 - Fault Info Automatic Printout Services (This bit reversed in some software) 0/1 Out of Service / In Service ASYDL Index 965 bit 0 - SNMP Activation 0/1= Out of Service / In Service Index 965 bit 5 - System Message automatic output to = 0/1 Out of Service/ In Service. Note 1 Index 965 bit 7 System Message automatic output to SNMP-Trap 0/1 Out of Service / In Service. Note 1 Note 1: The same system message cannot be output to MAT, System Printer, and SNMP-Trap simultaneously. When both bits in ASYDL, Index 965 bit 5 and bit 7 are assigned to 1, system message is output to prior to SNMP-Trap. Table 3. System Message Output Method Note 2: The asterisk ( * ), on table 3 indicates that other output methods will not be affected if the bit is set or not. 15

21 ADTM: Assignment of Data for TCP/IP Module This command is used to assign/delete the TCP/IP module data, such as IP address, default gateway, NIC card data and SNMP configuration. Figure 2-1. ADTM Command. Step 1. From the main menu type ADTM and press enter. Select the OPTIONS tab, highlight Configure SNMP and click on Execute. Step 2. The Configure SNMP window appears. Under Data to assign, select SNMP Activation from the pull down menu and click on Execute. Figure 2-2. Configure SNMP window 16

22 Step 3. The SNMP Activation window appears. Under Activate SNMP select, Yes and click Set. Figure 2-3. SNMP Activation window Step 4. A message box appears In order to confirm change of port number, please re-start TCP/IP module. Click OK. Clicking OK does not activate SNMP. This is just a reminder. Figure 2-4. Message Box Step 5. The Configure SNMP window appears. Select, System Group Information from the pull down menu and click on Execute. Figure 2-5. Configure SNMP window. 17

23 Step 6. The System Group Information window appears. Under System Description, enter how you would like the system to be described when the NMS fetches for the description of the device (PBX). This can be up to 128 characters in length. The following characters can be used: alpha (both capital and small letters), numeric #, $, %, &, *, (, ), -, _, =, +, {, [, ], },, \, :, ;, <, >,, (comma),. (period),?, /. A maximum of 32 Object ID s can be entered (each ID is distinguished by a period). The range of one Object ID is This is fixed to No entry is needed in the text box. See Chapter 1 Object Identifier for details. Click on Set. Figure 2-6. System Group Information window Step 7. The Configure SNMP window appears. Click on the drop down menu and select System, SNMP Group Information. Click on, Execute. Figure 2-7. Configure SNMP window 18

24 Step 8. The System, SNMP Group Information window appears. In the Contact Address text box, enter the name of a person, company, department etc., along with phone numbers, of who to contact in the event of an emergency or maintenance issues. Up to 64 characters. In the System Name text box, enter a name you want to give the device (PBX). This is useful when multiple systems are networked (IPTRK CCIS). Up to 64 characters. In the Location text box, enter the physical location where the system resides. This can be a bldg. Number within a campus, etc. If trap, is to be used, select Enable and click on Set. Figure 2-8. System, SNMP Group Information window Step 9. The Configure SNMP window appears. Select Community Information from the pull down menu and click on Execute. Figure 2-9. Configure SNMP window 19

25 Step 10. The Community Information window appears. Click, on Add. Figure Community Information window Step 11. The Community Information sub menu appears. In the Community Name text box, enter the name of the SNMP manager. Up to 25 characters. Note: For security reasons, it is highly recommended that the Community Name be unique. Look at this as the PASSWORD between the SNMP manager and the agent (the PBX). Most SNMP manager software, default with the Community Name of public. In the IP Address of SNMP Manager text box, enter the IP Address of the SNMP manager. If trap was selected, this could be a different IP Address. 20

26 Under mode, select READ-ONLY or WRITING-ALLOWED. Note: Careful consideration should be given when granting WRITING-ALLOWED permission to personnel in the field. If not used properly, PBX performance can be compromised. Click OK. Figure Community Information sub menu window Step 12. The Configure SNMP window appears. Select Trap Information from the pull down menu and click on Execute. Figure Configure SNMP window. 21

27 Step 13. The Trap Information window appears. In the Trap text box, enter the Trap community name where the trap message is to be sent. In the IP Address of SNMP text box, enter the IP Address of the SNMP Manager and, click OK. Figure Trap Information window. Step 14. The Trap information window appears, click on Set. Figure Trap Information window. Note: The maximum number of trap destinations is four. Follow steps 12 through 14 to add additional destinations. 22

28 Step 15. The Configure SNMP window appears. Click on Close. Figure Configure SNMP window. Step 16. The ADTM (Assignment of Data for TCP/IP Module) window appears. On the Options tab highlight, TCP/IP Module Control and click on Execute. Figure ADTM (Assignment of Data for TCP/IP Module) window. 23

29 Step 17. The TCP/IP Module Control window appears. On the pull down menu select Restart and click on Execute. Figure TCP/IP Module Control window Step 18. The message box below appears. Click OK. The TCP/IP protocol software will restart. Figure ADTM Message Box. Note: In a dual system configuration, it is recommended that TCP/IP be restarted on the STD-BY side first, as TCP/IP services will be disrupted. All applications communicating with the PBX via TCP/IP will loose connectivity. This process opens UDP ports 161 and

30 Step 19. A message box appears showing the progress of the TCP/IP restart. Figure ADTM Progress Message Box Note: In a dual configuration system, switch over CPU s via the CMOD command or via the EMA card and follow steps 17 through 19 for the STD-BY CPU. Step 20. Backup the PBX using MEM_HDD command. Step 21. Reset the PBX for changes to take effect. Note: With MAT Version R15 and above, the ADTM command consolidates some entries as follows: 25

31 Figure 2-20 ADTM command in MAT Version R PROCEDURE COMPLETE

32 Figure Configuration of SNMP Agent and SNMP Manager NEAX IPS SNMP Configuration The NEAX IPS platform supports SNMP in PN-CP24-A (3100) or higher. MIB-II is supported based on RFC 1158 and RFC Traps are not supported. Programming Step 1. SNMP Port Open CM0B YY=03 1 st Data = 00 2 nd Data = 0 :SNMP Port Open 1 (default) : SNMP Port not Open 27

33 Note: This opens UDP Port 161 ONLY. Step 2. System Data Backup CMEC Y=6 1 st Data = 0 2 nd Data = 0 Exe Step 3. Initialize PBX. Step 4. Permission to use the community name, ADMIN. Phase1 only. See Note below. CM0B YY=03 1 st Data = 01 2 nd Data = 0 :Allowed 1 (default) :Not allowed Note: The community name ADMIN cannot be changed. For the moment (for security purposes), it is recommended that this information only be given out to those in the field on a need to know basis i.e., Network Administrators etc. Proper steps have been taking to have this changed. (Phase 2) The NEAX IPS system sets the following MIB-II system information to fixed. SysDescr SysObjectID IPS Unlike the NEAX IPX system, the NEAX IPS relies on the SNMP Manager to set the following variables: syscontact 28

34 sysname syslocation Programming Phase 2 (R6.2) When the system does not provide the Remote PIM over IP feature, only do the following programming. 29

35 30

36 31

37 PROCEDURE COMPLETE

38 33

39 Table 3-33 Alarm Trap Information Table 3-33 Alarm Trap Information, cont. Figure Configuration of SNMP Agent and SNMP Manager 34

40 Chapter 3 MIB Groups This chapter describes the different groups within MIB-II. 35

41 The System Group RFC 1213 The system group consists of seven variables and no tables. NAME OID SYNTAX ACCESS STATUS Description System (sys) Group None mandatory Information about the SNMP Agent's System sysdescr String to 255 RO mandatory A textual description of the system supported by this agent. sysobjectid Object Id RO mandatory The vendor's OID of the agent in the system sysuptime Time Ticks RO mandatory The hundred's of a second since agent was reinitialized. syscontact String to 255 RW mandatory The contact person for this managed node and how to contact this person sysname String to 255 RW mandatory Administrator assigned name for this node syslocation String to 255 RW mandatory Physical location of node. sysservices see Table Interger to 127 RO mandatory A value that indicates the set of services this system offers. Table 3-1 System Group NEAX IPX sysobjectid = Fixed (Actual output: nec ) NEAX IPS sysobjectid = Fixed (Actual output: nec ) ISO Layer Functionality Value 1 physical (repeaters) 1 2 datalink/subnetwork (bridges) 2 3 internet (IP routers) 4 4 end-to-end (TCP support) 8 7 applications (SMTP, etc.) 64 Table Services The variable sysservices indicates the set of services that the particular system offers. A system supporting TCP applications would have a sysservices value of 72 (8+64). The same system acting as a router would have a value of 76 (4+8+64). NEAX IPX sysservices = 72 Default NEAX IPS sysservices = 72 Default 36

42 The Interface Group RFC 1213 This group consists of one variable and one large table. NAME OID SYNTAX ACCESS STATUS Description Interfaces (if) Group None mandatory Information about the logical I/O ports. ifnumber Integer RO mandatory The number of network interfaces present on this system. iftable Sequence of None mandatory A list of interface entries. The number of entries is IfEntry given by the value of ifnumber. ifentry IfEntry None mandatory A row of the iftable containing objects for a logical interface. ifindex Integer RO mandatory A unique value for each interface. The key to the table. ifdescr String to 255 RO mandatory A textual string containing information about the interface. (As provided by the MIB writer) iftype Integer RO mandatory The type of physical or link interface protocol see Table immediately below the network layer in the stack. ifmtu Integer RO mandatory The largest datagram which can be sent/received on the interface, in octets. Table 3-2 Interface Group iftypes Value Meaning Value Meaning Value Meaning 1 none of the following 2 regular hdh ddn-x25 5 rfc 877-x25 6 ethernet - csmacd 7 iso88023-csmacd 8 iso token Bus 9 iso tokenring 10 iso88026-man 11 starlan 12 proteon - 10Mbit 13 proteon-80mbit 14 hyperchannel 15 fddi 16 lapb 17 sdlc 18 ds 1 [T-1] 19 e1 [Europe/S.A. T-1] 20 basic ISDN 21 primary ISDN 22 proppointtopointserial 23 PPP 24 software Loopback 25 eon [CLNP over IP] 26 ethernet-3mbit 27 nsip [XNS over IP] 28 slip [generic SLIP] 29 ultra 30 ds 3 [T-3] 31 sip [SMDS] 32 frame-relay Table iftype Object Most standard interfaces have values in the iftype object. NEAX IPX iftype = ethernet-csmacd (6) NEAX IPS iftype = ethernet-csmacd (6) 37

43 if Troubleshooting The ifadminstatus and ifoperstatus variables work together to offer control of each identified interface. NAME OID SYNTAX ACCESS STATUS Description ifspeed Gauge RO mandatory An estimate of the interface's current bandwidth in bits per second. ifphysaddress Physical RO mandatory The interface's address at the protocol layer immediately Address below the network layer in the protocol stack. ifadminstatus Integer RW mandatory The desired state of the interface. ifoperstatus Integer RO mandatory The current operational state of the interface. iflastchange TimeTicks RO mandatory The value of sysuptime at the time the interface entered its current operational state. Table 3-3 if Inbound Counters These are inbound event occurrences in the agent s referenced interface. NAME OID SYNTAX ACCESS STATUS Description ifinoctets Counter RO mandatory The total number of octets received on the interface, including framing characters. ifinucastpkts Counter RO mandatory The number of subnetwork-unicast packets delivered to a higher-layer protocol. ifinnucastpkts Counter RO mandatory The number of non-unicast packets delivered to a higher-layer protocol. ifindiscards Counter RO mandatory The number of inbound packets which were chosen to be discarded even though no errors had been detected to prevent their being deliverable to a higher-layer protocol. One possible reason for discarding such a packet could be to free up buffer space. ifinerrors Counter RO mandatory The number of inbound packets that contained errors that make them undeliverable to a higher-layer protocol. ifinunknownprotos Counter RO mandatory The number of packets received via the interface which were discarded because of an unknown or unsupported protocol. Table 3-4 Inbound Counters 38

44 if Outbound Counters The ifoutqlen can tell us how many packets have lined up at the interface waiting to leave. This is easier than retrieving the ifindiscards and ifoutdiscards and comparing them to previous values. NAME OID SYNTAX ACCESS STATUS Description ifoutoctets Counter RO mandatory The total number of octets transmmitted out of the interface including framing characters. ifoutucastpkts Counter RO mandatory The total number of packets that higher-level protocols requested be sent to a subnetwork-unicast address. ifoutnucastpkts Counter RO mandatory The total number of packets that higher-level protocols requested be sent to a non-unicast address. ifoutdiscards Counter RO mandatory The number of inbound packets which were chosen to be discarded even though no errors had been detected to prevent their being deliverable to a higher-layer protocol. One possible reason for discarding such a packet could be to free up buffer space. ifouterrors Counter RO mandatory The number of outbound packets that could not be transmitted because of errors. ifoutqlen Gauge RO mandatory The length of the output packet queue (in packets). ifspecific Object Id RO mandatory A reference to MIB definitions specific to the particular media being used for the interface. Table 3-5 Outbound Counters The Address Translation Group RFC 1213 The Address Translation tables contain the NetworkAddress to physical address equivalences. Some interfaces do not use translation tables for determining address equivalences, if all interfaces are of this type, then the Address Translation table is empty, i.e., has zero entries. NAME OID SYNTAX ACCESS STATUS Description Address Translation (at) Group None deprecated Information from the ARP cache. attable Sequence of None deprecated The Address Translation tables contain the NetworkAddress AtEntry to physical address match. atentry AtEntry None deprecated Each entry contains one NetworkAddress to physical address match. atifindex Integer RW deprecated The interface on which this entry's equivalence is effective. atphysaddress PhysAddress RW deprecated The media-dependent physical address. atnetaddress Network- RW deprecated The NetworkAddress corresponding to the media-dependent Address physical address. Table 3-6 Address Translation Group 39

45 The IP Group RFC 1213 This group provides information on the functions of the Internet Protocol entity in the agent s system. NEAX IPX ipforwarding = 2: do not forward NEAX IPS ipforwarding = 2: do not forward A value of 1 on a get-request response of ipforwarding indicates that the system can forward datagrams. NEAX IPX ipdefaultttl = 64 NEAX IPS ipdefaultttl = 64 NAME OID SYNTAX ACCESS STATUS Description Internet Protocol (ip) Group None Information about the Internet Protocol. ipforwarding Integer RW mandatory The indicator that this system can forward datagrams received by (but not addressed to) it. ipdefaultttl Integer RW mandatory The default value in the Time-to-Live field of the IP datagrams originated at this system. Table 3-7 IP Group ip Inbound Counters NAME OID SYNTAX ACCESS STATUS Description ipinreceives Counter RO mandatory The total number of input datagrams received from interfaces, including those received in error. ipinhdrerrors Counter RO mandatory The number of input datagrams discarded due to errors in their IP headers. ipinaddrerrors Counter RO mandatory The number of datagrams discarded when their IP header's destination field was not this system. ipforwdatagrams Counter RO mandatory The number of datagrams that this system attempted to find a route to forward. ipinunknownprotos Counter RO mandatory The number of datagrams received but discarded because of an unknown or unsupported protocol. ipindiscards Counter RO mandatory The number of input IP datagrams for which no problems were encountered to prevent their continued processing, but which were discarded (e.g., for lack of buffer space). ipindelivers Counter RO mandatory The total number of input datagrams successfully delivered to IP user-protocols. Table 3-8 IP Inbound Counters 40

46 ip Outbound Counters NAME OID SYNTAX ACCESS STATUS Description ipoutrequests Counter RO mandatory The total number of IP datagrams which local protocols passed to IP for sending out, except the number of ipforwdatagrams ipoutdiscards Counter RO mandatory The number of output IP datagrams with no problems that the system discarded. ipoutnoroutes Counter RO mandatory The number of IP datagrams discarded because the system could find no route to their destination. Table 3-9 IP Outbound Counters Fragmentation Counters NEAX IPX ipreasmtimeout = 64 seconds NEAX IPS ipreasmtimeout = 64 seconds NAME OID SYNTAX ACCESS STATUS Description ipreasmtimeout Integer RO mandatory The maximum number of seconds IP holds received fragments awaiting reassembly. ipreasmreqds Counter RO mandatory The number of IP fragments received needing reassembly at this system. ipreasmoks Counter RO mandatory The number of IP datagrams successfully reassembled. ipreasmfails Counter RO mandatory The number of failures detected by the IP reassembly algorithm. ipfragoks Counter RO mandatory The number of IP datagrams that IP has successfully fragmented at this system. ipfragfails Counter RO mandatory The number of IP datagrams that IP has discarded because it could not fragment them. ipfragcreates Counter RO mandatory The number of IP datagram fragments that IP has generated at this system. Table 3-10 Fragmentation Counters 41

47 ip Address Table The IP Address table contains this entity s IP addressing information. NEAX IPX ipadentaddr = IP Address set in ASYDL/ADTM NEAX IPS ipadentaddr = IP Address set in CM0B Y=00 (1) 00 NEAX IPX ipadentifindex = LoopBack NEAX IPS ipadentifindex = LoopBack NEAX IPX ipadentnetmask = Subnetmask set in ASYDL /ADTM NEAX IPS ipadentnetmask = Subnetmask set in CM0B Y=00 (1) 01 NEAX IPX ipadentbcastaddr = 1 NEAX IPS ipadentbcastaddr = 1 NEAX IPX ipadentreasmmaxsize = 1500 NEAX IPS ipadentreasmmaxsize = 1500 NAME OID SYNTAX ACCESS STATUS Description ipaddrtable Sequence None mandatory The table of addressing information relevant to this IpAddrEntry system's IP addresses. ipaddrentry IpAddrEntr None mandatory Information for one of this system's IP addresses. ipadentaddr IpAddress RO mandatory The IP address to which this entry's addressing information pertains. ipadentifindex Integer RO mandatory The index value that uniquely identifies the interface to which this entry is applicable. ipadentnetmask IpAddress RO mandatory The subnet mask associated with the IP address of this entry. ipadentbcastaddr Integer RO mandatory The value of the least significant bit in the IP broadcast address used on the (logical) interface. ipadentreasmmaxsize Integer to RO mandatory The size of the largest IP datagram that this system can re-asemble from IP fragments. Table 3-11 IP Address table 42

48 ip Route Table The IP routing table contains an entry for each route presently known to this entity. NEAX IPX iproutenexthop = Gateway address set in ASYDL/ADTM NEAX IPS iproutenexthop = Gateway address set in XXXXXXX NAME OID SYNTAX ACCESS STATUS Description iproutetable Sequence of None mandatory This system's IP Routing table. IpRouteEntry iprouteentry IpRouteEntry None mandatory A route to a particular destination. iproutedest IpAddress RW mandatory The destination IP address of this route. iprouteifindex Integer RW mandatory The value that identifies the local interface through which the datagram should reach the next hop. iproutemetric Integer RW mandatory The primary routing metric for this route. iproutemetric Integer RW mandatory An alternate routing metric for this route. iproutemetric Integer RW mandatory An alternate routing metric for this route. iproutemetric Integer RW mandatory An alternate routing metric for this route. iproutenexthop IpAddress RW mandatory The IP address of the next hop of this route. iproutetype Integer RW mandatory The type of route: other(1), invalid(2), direct(3) or indirect(4). iprouteproto Integer RO mandatory The way (usually protocol) this system learned the route. iprouteage Integer RW mandatory The number of seconds since IP last updated this route or otherwise determined it correct. iproutemask IpAddress RW mandatory The mask to be logically-anded with the destination for comparing to the iproutedest field. iproutemetric Integer RW mandatory An alternate routing metric for this route. iprouteinfo Object Id RO mandatory A reference to MIB definitions specific to the routing protocol responsible for this route. Table 3-12 IP Route Table iprouteproto possible integer values other (1) unknown local (2) direct netmgmt (3) icmp (4) egp (5) ggp (6) hello (7) rip (8) is-is (9) es-is (10) ciscoigrp (11) bbnspfigp (12) ospf (13) bgp (14) Table iprouteproto values 43

49 Net to Media Table This table is used for mapping from IP addresses to physical addresses. This table takes the place of the Address Translation Table since it was deprecated. ipnettomediatable Sequence of None mandatory The IP Address Translation table for mapping IP to physical ipnettomediaentry addresses. ipnettomediaentry ipnettomediaenone mandatory Each entry contains one IPAddress to physical address equivalence. ipnettomediaifindex Integer RW mandatory The interface on which this entry's equivalence is effective. ipnettomediaphysaddress PhysAddress RW mandatory The media-dependent physical address. ipnettomedianetaddress IpAddress RW mandatory The IpAdress corresponding to the media-dependent physical address. ipnettomediatype Integer RW mandatory The type of mapping. iproutingdiscards Counter RO mandatory The number of routing entries that IP discarded even though they are valid. Table 3-13 Net to Media Table The ICMP Group RFC 1213 The Internet Control Message Protocol as specified in RFC 792, provides a number of diagnostics functions and can send error packets to hosts. ICMP Inbound Counters NAME OID SYNTAX ACCESS STATUS Description ICMP (In) Group None mandatory Internet Control Message Protocol information. icmpinmsgs Counter RO mandatory The total number of ICMP messages which the system received. icmpinerrors Counter RO mandatory The number of ICMP messages which the system received that had ICMP-specific errors. icmpindestunreachs Counter RO mandatory The number of ICMP Destination Unreachable messages received. icmpintimeexcds Counter RO mandatory The number of ICMP Time Exceeded messages received. icmpinparmprobs Counter RO mandatory The number of ICMP Parameter Problem messages received icmpinsrcquenchs Counter RO mandatory The number of ICMP Source Quench messages received. icmpinredirects Counter RO mandatory The number of ICMP Redirect messages received. icmpinechos Counter RO mandatory The number of ICMP Echo (request) messages. icmpinechoreps Counter RO mandatory The number of ICMP Echo Reply messages received. icmpintimestamps Counter RO mandatory The number of ICMP Timestamp (request) messages received. icmpintimestampreps Counter RO mandatory The number of ICMP Timestamp Reply messages received. icmpinaddrmasks Counter RO mandatory The number of ICMP Adress Mask Request messages received. icmpinaddrmaskreps Counter RO mandatory The number of ICMP Adress Mask Reply messages received Table 3-14 ICMP Inbound Counters 44

50 ICMP Variation Outbound Counters NAME OID SYNTAX ACCESS STATUS Description icmpoutmsgs Counter RO mandatory The total number of ICMP messages which this system attempted to send. icmpouterrors Counter RO mandatory The number of ICMP messages which this system did not send due to ICMP problems. icmpoutdestunreachs Counter RO mandatory The number of ICMP Destination Unreachable messages sent. icmpouttimeexcds Counter RO mandatory The number of ICMP Time Exceeded messages sent. icmpoutparmprobs Counter RO mandatory The number of ICMP Parameter Problem messages sent. icmpoutsrcquenchs Counter RO mandatory The number of ICMP Source Quench messages sent. icmpoutredirects Counter RO mandatory The number of ICMP Redirect messages sent. Table 3-15 ICMP Variation Outbound Counters ICMP Diagnostic Outbound Counters NAME OID SYNTAX ACCESS STATUS Description icmpoutechos Counter RO mandatory The number of ICMP Echo (request) messages sent. icmpoutechoreps Counter RO mandatory The number of ICMP Echo Reply messages sent. icmpouttimestamps Counter RO mandatory The number of ICMP Timestamp (request) messages sent. icmpouttimestampreps Counter RO mandatory The number of ICMP Timestamp Reply messages sent. icmpoutaddrmasks Counter RO mandatory The number of ICMP Address Mask Request messages sent icmpoutaddrmaskrep Counter RO mandatory The number of ICMP Address Mask Reply messages sent. Table 3-16 ICMP Diagnostic Outbound Counters 45

51 The TCP Group RFC 1213 The TCP Group focuses on server functions. NAME OID SYNTAX ACCESS STATUS Description TCP Group None mandatory Information about Transmission Control Protocol functions. tcprtoalgorithm see Table Integer RO mandatory The algorithm to determine the timeout value used for retransmitting unacknowledge octets. tcprtomin Integer RO mandatory The minimum, in milliseconds (msec), for this TCP entity's retransmission timeout. tcprtomax Integer RO mandatory The maximum, in milliseconds (msec), for this TCP implementation of the retransmission timeout. Table 3-17 Retransmission of Unacknowledged Data Table NEAX IPX tcprtoalgorithym = vanj NEAX IPS tcprtoalgorithym = vanj NEAX IPX tcprtomin = 100 NEAX IPS tcprtomin = 100 NEAX IPX tcprtomax = msec NEAX IPS tcprtomax = msec The tcprtoalgorithm identifies the formula that will be used by the agent's system to determine how long to wait before retransmitting the TCP segment. The possible integer values are: other (1) none of the following constant (2) a constant retransmit timeout rsre (3) Military Standard 1778 vanj (4) Van Jacobson's Algorithm Table tcprtoalgorithm Values 46

52 TCP Connection Objects NAME OID SYNTAX ACCESS STATUS Description tcpmaxconn Integer RO mandatory The maximum number of TCP connections the system can support. tcpactiveopens Counter RO mandatory How many TCP connections transitioned to SYN-SENT state from the CLOSED state. tcppassiveopens Counter RO mandatory How many TCP connections transitioned to the SYN-RCVD state from the LISTEN state. tcpattemptfails Counter RO mandatory How many TCP connections have not completed the SYN handshake procedure. tcpestabresets Conter RO mandatory How many TCP connections have gone to the CLOSED state from ESTABLISHED or CLOSE-WAIT. tcpcurrestab Gauge RO mandatory How many TCP connections currently in the ESTABLISHED or CLOSE-WAIT state. Table 3-18 TCP Connection Objects NEAX IPX tcpmaxconn = 4096 (-1 = unlimited ) NEAX IPS tcpmaxconn = 2048 (-1 = unlimited ) TcpActiveOpens = Step 1 of 3 step handshake TcpPassiveOpens = Step 2 of 3 step handshake TcpAttemptFails = Step 3 of 3 step handshake TCP Segment Counters NAME OID SYNTAX ACCESS STATUS Description tcpinsegs Counter RO mandatory The total number of segments received, including those received in error. tcpoutsegs Counter RO mandatory The total number of segments sent, excluding those containing only retransmitted octets. tcpretranssegs Counter RO mandatory The total number of segments retransmitted. Table 3-19 TCP Segment Counters 47

53 TCP Connection Table The tcpconntable tracks the current tcp and where in the TCP session they are at the time of the SNMP request. NAME OID SYNTAX ACCESS STATUS Description tcpconntable Seq of None mandatory A table containing TCP connection-specific information. TcpConnEntry tcpconnentry TcpConnEntryNone mandatory Information about a particular current TCP connection. tcpconnstate (see Table ) Integer RW mandatory The state of this TCP connection. tcpconnlocaladdress IpAddress RO mandatory The local IP address for this TCP connection. tcpconnlocalport Integer to 655 RO mandatory The local port number for this TCP connection. tcpconnremaddress IpAddress RO mandatory The remote IP address for this TCP connection. tcpconnremport Integer to 655 RO mandatory The remote port number for this TCP connection. Table 3-20 TCP Connection Table closed (1) listen (2) synsent (3) synreceived (4) established (5) finwait1(6) finwait2(7) closewait(8) lastack(9) closing(10) timewait(11) deletetcb(12) Table tcpconnstate Values TCP MIB-II additions NAME OID SYNTAX ACCESS STATUS Description tcpinerrs Counter RO mandatory The total number of segments received in error. tcpoutrsts Counter RO mandatory The number of TCP segments sent containing the RST flag. Table 3-21 TCP MIB-II Additions 48