Metrodata LM1100 User Manual Version 3.9x

LM1100 User Manual www.metrodata.co.uk Metrodata LM1100 User Manual Version 3.9x Metrodata Ltd Fortune House Crabtree Office Village Eversley Way Egham Surrey TW20 8RY United Kingdom tel: +44 (0) 1784 744700 fax:+44 (0) 1784 744730 email: support@metrodata.co.uk website: www.metrodata.co.uk Part No: 76-02-003D

Metrodata Ltd No part of this publication may be reproduced, transmitted, transcribed, stored in a retrieval system, or translated into any language or computer language, in any form or by any means, electronic, mechanical, magnetic, optical, chemical, manual or otherwise, without the prior written permission of Metrodata Ltd, Fortune House, Crabtree Office Village, Eversley Way, Egham, Surrey, TW20 8RY, United Kingdom. Tel: +44 (0) 1784 744700 Fax: +44 (0) 1784 744730 e-mail: support@metrodata.co.uk www: http://www.metrodata.co.uk ftp://ftp.metrodata.co.uk Disclaimer Metrodata Ltd makes no representations or warranties with respect to the contents hereof and specifically disclaims any implied warranties or merchantability or fitness for any particular purpose. Further, Metrodata Ltd reserves the right to revise this publication and to make changes from time to time in the content hereof without obligation of Metrodata Ltd to notify any person of such revision or changes. Trademarks The Trademarks of other Corporations which may be used in this manual are hereby acknowledged. Copyright 2003 by Metrodata Ltd All Rights Reserved

CONTENTS 1 INTRODUCTION 1 1. 1 About this manual 2 1. 2 Metrodata products by MIB 3 1. 3 Conventions 4 2 SNMP MANAGEMENT CONCEPTS 5 2. 1 Management Overview 5 2. 2 Object Management 5 2. 3 MIB Definitions 5 2. 4 Traps 6 3 INITIAL SET-UP 7 3. 1 LAN Connection 7 4 CONFIGURATION 9 4. 1 Management Access 9 4. 2 WAN Port Set-up menus 10 4. 3 Remote Logon 11 4. 4 Datalink 12 4. 5 Management menu 13 4. 6 Ethernet 14 4. 6. 1 The Address Translation (AT) table 15 4. 6. 2 Interface Statistics 16 4. 7 IP 18 4. 7. 1 The IP Routing Table 19 4. 7. 2 IP Statistics 23 4. 8 UDP 26 4. 8. 1 UDP Statistics 26 4. 9 SNMP 28 4. 9. 1 SNMP Statistics 30 4. 10 TCP 33 4. 10. 1 TCP Statistics 33 4. 10. 2 TCP Connection table 35 4. 11 Telnet 36 4. 12 TFTP 37 4. 13 Ping 37 5 RFC1213 STANDARD MIB (MIB II) 39 5. 1 RFC1213 System Group 40 5. 2 RFC1213 Interfaces Group 41 5. 3 RFC1213 Address Translation (AT) Group 43 5. 4 RFC1213 IP Group 44 5. 4. 1 IP Forwarding 45 5. 4. 2 IP Addressing 45 5. 4. 3 IP Routing 46 5. 4. 4 IP Address Translation & Discards 48 5. 5 RFC1213 The ICMP Group 49 5. 6 RFC1213 TCP Group 50 5. 6. 1 TCP Connection table 52 5. 7 RFC1213 UDP Group 53 5. 8 RFC1213 EGP Group 53 5. 9 RFC1213 Transmission Group 53 5. 10 RFC1213 SNMP Group 54

6 RFC1406 MIB NEAR END GROUP 55 6. 1 Introduction to RFC1406 55 6. 2 RFC1406 Near End Config Table 57 6. 2. 1 RFC1406 Near End Config Entries 57 6. 2. 2 Near End Config Entry - Line Type 58 6. 2. 3 Near End Config Entry - Line Coding 59 6. 2. 4 Near End Config Entry - Send Codes 60 6. 2. 5 Near End Config Entry - Circuit Identifier 60 6. 2. 6 Near End Config Entry - Loopback Config 61 6. 2. 7 Near End Config Entry - Line Status 62 6. 2. 8 Near End Config Entry - Signal Mode 63 6. 2. 9 Near End Config Entry - Transmit Clock Source 63 6. 2. 10 Near End Config Entry - Datalink 64 6. 2. 11 RFC1406 Config Table Entries for E1 & E2 ATM DSU s 66 6. 3 RFC1406 Near End Current Table 67 6. 3. 1 RFC1406 Near End Current Table for E1 & E2 Non-ATM DSU s 68 6. 3. 2 RFC1406 Near End Current table for E1 & E2 ATM DSU s 69 6. 4 RFC1406 Near End Interval Table 70 6. 4. 1 RFC1406 Near End Interval Table for E1 & E2 Non-ATM DSU s 71 6. 4. 2 RFC1406 Near End Interval Table for E1 & E2 ATM DSU s 72 6. 5 RFC1406 Near End Total Table 73 6. 5. 1 RFC1406 Near End Total Table for Non-ATM E1 & E2 DSU s 74 6. 5. 2 RFC1406 Near End Total Table for E1 & E2 ATM DSU s 75 7 RFC 1406 MIB FAR-END GROUP 77 7. 1 RFC1406 Far End Current Table for E1 & E2 Interfaces 78 7. 1. 1 RFC 1406 Far End Current Table for E1 & E2 Non-ATM DSU s 79 7. 1. 2 RFC 1406 Far End Current Table for E1 & E2 ATM DSU s 80 7. 2 RFC1406 Far End Interval Table for E1 & E2 Interfaces 81 7. 2. 1 RFC1406 Far End Interval Table for E1 & E2 Non-ATM DSU s 82 7. 2. 2 RFC1406 Far End Interval Table for E1 & E2 ATM DSU s 83 7. 3 RFC 1406 Far End Total table for E1 & E2 interfaces 84 7. 3. 1 RFC1406 Far End Total Table for E1 & E2 Non-ATM DSU s 85 7. 3. 2 RFC1406 Far End Total Table for E1 & E2 ATM DSU s 86 8 RFC1406 FRACTIONAL GROUP 87 8. 1 Introduction to RFC1406 Fractional Group 87 8. 2 RFC1406 Fractional Tables 88 8. 2. 1 RFC1406 Fractional Tables 88 9 RFC1407 MIB NEAR END GROUP 89 9. 1 RFC1407 Near End Config Table 90 9. 1. 1 RFC1407 Near End Config Entries 90 9. 1. 2 Near End Config Entry - Line Type 92 9. 1. 3 Near End Config Entry - Line Coding 92 9. 1. 4 Near End Config Entry - Send Codes 93 9. 1. 5 Near End Config Entry - Circuit Identifier 93 9. 1. 6 Near End Config Entry - Loopback Config 94 9. 1. 7 Near End Config Entry - Line Status 95 9. 1. 8 Near End Config Entry - Transmit Clock Source 95 9. 1. 9 RFC1407 Near End Config Table for Non-ATM DS3/E3 DSU s 96 9. 1. 10 RFC1407 Near End Config Table for ATM DS3/E3 DSU s 97 9. 2 RFC1407 Near End Current Table 98 9. 2. 1 RFC1407 Near End Current Table for DS3/E3 DSU s 99 9. 3 RFC1407 Near End Interval Table 100 9. 3. 1 RFC1407 Near End Interval Table for DS3/E3 DSU s 102 9. 4 RFC1407 Near End Total Table 103 9. 4. 1 RFC1407 Near End Total Table for Metrodata DS3/E3 DSU s 104

10 RFC1407 MIB FAR-END GROUP 105 10. 1 RFC1407 Far End Config Table for DS3/E3 Interfaces 106 10. 1. 1 RFC1407 Far End Config Entries 106 10. 2 RFC1407 Far End Current Table 108 10. 2. 1 RFC1407 Far End Current Table for Metrodata DS3/E3 DSU s 109 10. 3 RFC1407 Far End Interval Table 110 10. 3. 1 RFC1407 Far End Interval Table for Metrodata DS3/E3 DSU s 111 10. 3. 2 RFC1407 Far End Total Table for Metrodata DS3/E3 DSU s 113 11 RFC1407 MIB FRACTIONAL GROUP FOR DS3/E3 INTERFACES 115 11. 1 RFC1407 Fractional Tables for DS3/E3 Interfaces 116 11. 2 RFC1407 Fractional Tables for Metrodata DS3/E3 DSU s 116 12 RFC1595 Sonet/SDH MIB 117 12. 1 Metrodata Sonet Products 117 12. 2 RFC1595 Structure 117 12. 3 Sonet/SDH Medium Group 118 12. 3. 1 Medium Table for Sonet/SDH Interfaces 119 12. 4 Sonet/SDH Section Group 120 12. 4. 1 Sonet/SDH Section Current table 120 12. 4. 2 Section Current Table for Sonet/SDH Interfaces 121 12. 4. 3 Sonet/SDH Section Interval table 121 12. 4. 4 Section Interval Table for Sonet/SDH Interfaces 122 12. 5 Sonet/SDH Line Group 123 12. 5. 1 Sonet/SDH Line Current table 123 12. 5. 2 Line Current Table for Sonet/SDH Interfaces 124 12. 5. 3 Sonet/SDH Line Interval table 124 12. 5. 4 Line Interval Table for Sonet/SDH Interfaces 125 12. 6 Sonet/SDH Far End Line Group 126 12. 6. 1 Sonet/SDH Far End Line Current table 126 12. 6. 2 Far End Line Current Table for Sonet/SDH Interfaces 127 12. 6. 3 Sonet/SDH Far End Line Interval table 128 12. 6. 4 Far End Line Interval Table for Sonet/SDH interfaces 129 12. 7 Sonet/SDH Path Group 130 12. 7. 1 Sonet/SDH Path Current table 130 12. 7. 2 Path Current Table for Sonet/SDH Interfaces 131 12. 7. 3 Sonet/SDH Path Interval table 132 12. 7. 4 Path Interval Table for Sonet/SDH Interfaces 133 12. 8 Sonet/SDH Far End Path Group 134 12. 8. 1 Sonet/SDH Far End Path Current table 134 12. 8. 2 Far End Path Current Table for Sonet/SDH Interfaces 134 12. 8. 3 Sonet/SDH Far End Path Interval table 135 12. 8. 4 Far End Path Interval Table for Sonet/SDH Interfaces 136 12. 9 Sonet/SDH Virtual Tributary Group 137 12. 9. 1 Sonet/SDH Virtual Tributary Current table 137 12. 9. 2 Sonet/SDH Virtual Tributary Interval table 139 12. 10 Sonet/SDH Far End Virtual Tributary Group 140 12. 10. 1Sonet/SDH Far End Virtual Tributary Current table 140 12. 10. 2Sonet/SDH Far End Virtual Tributary Interval table 141

13 METRODTE MIB (metrodte) for DTE and DCE INTERFACES 143 13. 1 Metrodata Products 143 13. 2 Initial definitions 143 13. 3 The metrodte Table for DTE and DCE interfaces 144 13. 3. 1 metrodteifindex 145 13. 3. 2 metrodteline type 145 13. 3. 3 metrodtespeed 146 13. 3. 4 metrodte Circuit ID 146 13. 3. 5 metrodte Loops 146 13. 3. 6 metrodte Status 147 13. 3. 7 metrodtetxclock 147 13. 3. 8 metrodtelinemode 148 13. 3. 9 metrodterxlinetype 148 13. 3. 10metroDteRxSpeed 148 13. 4 The metrodte Input Signal table 149 13. 4. 1 metrodte Input Signal Name 149 13. 4. 2 Inward Signal State 150 13. 5 The metrodte Output Signal table 150 13. 5. 1 metrodte Output Signal Name 151 13. 5. 2 metrodte Output Signal State 151 13. 5. 3 metrodte Output Signal Control 152 14 ATM FORUM MIB 153 14. 1 Metrodata ATM Products 153 14. 2 Introduction to ATM Forum definitions 153 14. 3 ATM Object Identifier Definitions 155 14. 3. 1 ATM Object Identifier definitions - Transmission type 155 14. 3. 2 ATM Object Identifier definitions - Media type 155 14. 3. 3 ATM Object Identifier definitions -Traffic Descriptor type 156 14. 4 ATM MIB UNI Groups 157 14. 4. 1 The Physical Port Group 157 14. 4. 2 The ATM Layer Group 158 14. 4. 3 The ATM Statistics Group 159 14. 4. 4 The Virtual Path Group 160 14. 4. 5 The Virtual Channel Group 162 15 TRAPS 165 15. 1 Overview 165 15. 2 RFC1215 Standard Traps 166 15. 2. 1 Standard Trap definitions 166 15. 2. 2 Standard Trap status 166 15. 3 METROTR2 Enterprise Traps 167 15. 3. 1 METROTR2 Enterprise Trap list 168 16 SNMP TROUBLESHOOTING TIPS & FAQ s 171

INTRODUCTION 1 INTRODUCTION The LM1100 SNMP Enabler is an optional interface card which may be fitted to Metrodata DSU s. It provides the capability to control and monitor the DSU via a 10BaseT Ethernet interface. A typical application for the LM1100 would be the control and management of a WAN (Wide Area Network) from a LAN (Local Area Network) link using a SNMP (Simple Network Management Protocol) NMS (Network Management System). The LM1100 SNMP Enabler supports a variety of Management Information Bases (MIB s) which must be provided to the User s Network Management System (NMS) to provide the NMS with a database of managed objects. The MIB s supported by the LM1100 SNMP Enabler are listed in Figure 1.1. The MIB s have been developed over periods of time under the aegis of the IETF (Internet Engineering Task Force) as RFC s (Request For Comment). The RFC process is an evolutionary one, and hence the MIB structures are correspondingly evolutionary. The MIB s therefore differ in their structures and the hierarchy of their contents. The MIB tables in this manual have been presented in such a way as to try to indicate the MIB structure. Where appropriate, control and configuration variables are shaded to distinguish them from data variables when they appear together in the same tables. This will become obvious as you read the manual. In addition to SNMP statistics which are obtained by polling round the network, SNMP also provides Traps which enable important unsolicited messages relating to the system to be handled on an interrupt basis. The Traps are described in Section 15 of the manual. The LM1100 SNMP Enabler in combination with a Metrodata DSU gives the Network Manager or Administrator extensive visibility and control of the Wide Area link. The ability to monitor performance statistics and network errors from a centralised point enables quick corrective action to be taken thereby enhancing network efficiency, and providing information which can help to diagnose problems and manage even the most complex networks. 76-02-003D 1

INTRODUCTION 1. 1 About this manual This user manual describes the installation, commissioning and Management Information Bases (MIB s) of the Metrodata LM1100 SNMP Enabler option. The manual assumes a certain level of knowledge on the part of the reader, especially a familiarity with SNMP. The manual is organised into sections describing each MIB in turn. The parts of the MIB applicable to Metrodata products are tabulated at the rear of each section where this is appropriate, and the information can be presented in an easy to read tabulated form. Section 2 introduces SNMP Management, MIB definitions and Traps. Section 3 describes the initial set-up of the LM1100, together with important safety information. Section 4, describes the configuration and commissioning sequence, with example menu screens to assist you in the procedures. Section 5 defines the RFC1213 Standard MIB (MIBII) which is the basis for all other MIB s in this manual. Sections 6,7 and 8 define the RFC1406 MIB for E1 & E2 Non-ATM DSUs and for some models of ATM SW and ATM CE DSU s. Sections 9,10 and 11 define the RFC1407 MIB for E3 DSU s including the FM4900, ATM SW DSU and ATM CE DSU families. Section 12 defines the RFC1595 MIB for the SONET/SDH interfaces Section 13 defines the metrodte MIB for DTE and DCE interfaces and for asymmetric operation on Metrodata DSU s. Section 14 defines the ATM Forum MIB for ATM UNI interfaces. Section 15 defines the METROTR2 Traps applicable to Metrodata products. Section 16 contains a list of Troubleshooting tips and FAQ s (frequently asked questions) which may be helpful when problems arise commissioning systems. This list is also maintained and updated regularly on the Metrodata Website. 2 76-02-003D

INTRODUCTION 1. 2 Metrodata products by MIB The table below lists the MIB s described in this manual and relates the Metrodata products to the appropriate MIB. MIB No Section Interface Type Metrodata Product RFC1213 5 ALL: This MIB is a basic standard RFC1406 6,7,8 E1 E2 LINE RFC1407 9,10,11 E2 UNI DS3/E3 FM4000, FM4500,FM4800, FM4850, ATMSW DSU, ATMCE DSU FM4900, ATMSW DSU, ATMCE DSU RFC1595 12 SONET/SDH ATMSW DSU, ATMCE DSU metrodte 13 V.35, X.21 RS449 ATMUNI V3.0 14 SONET/SDH DS3/E3 RFC1215, metrotr2 15 DS1/E1 DS3/E3 SONET/SDH FM4000,FM4200, FM4500, FM4800, FM4850, FM4900, PA1000, L3DSU ATMSW DSU, ATMCE DSU ALL Figure 1. 1 MIB support for Metrodata products Note that there is no MIB for E4 interfaces at present (1998). The basis for an E4 MIB will be MIBII, but there is no further support for E4 available. Section 15.5 defines the handling of Enterprise Traps for E4 interfaces, pending further progress with an E4 MIB. 76-02-003D 3

INTRODUCTION 1. 3 Conventions Notes are used to provide the reader with either statutory information which must be observed for safety reasons, or additional information which may increase the LM1100's effectiveness. The following conventions are used in the manual and in the screen examples. A pair of arrows around a word indicates a key on the keyboard, such as <space> or <escape>.there are two exceptions to this, which appear on some of the menus: <display> indicates that selecting the option will lead to data being displayed on the screen. <menu> indicates that the option leads to another menu, from which further options may be chosen. Screen displays which contain variable information, such as the current date or time, show the variable in italics, surrounded by square brackets, i.e. [time], or [nodename]. The speechmarks indicate data which is specified by the user when installing the LM1100. Screen examples. The DSU and its associated SNMP Enabler allow you to use one of three options for displaying the menus on a terminal - ANSI, VT100/VT220 or TTY. The screen examples in this manual use VT100/VT220 and are shaded to allow easy identification by the reader. MIB Objects have catalogue labels from RFC1407 onwards. These are shown in { } brackets in the tables. 4 76-02-003D

SNMP MANAGEMENT CONCEPTS 2 SNMP MANAGEMENT CONCEPTS 2. 1 Management Overview Management of products is important in reducing maintenance costs in terms of predicting down-time, identifying a fault when it has occurred and minimising the need to dispatch a maintenance engineer to site to maintain a potentially faulty device. With networks becoming increasingly complex the need for effective management is becoming highly significant. SNMP is used to manage systems so that product management may be standardised. Independent vendors of NMS s, networking equipment and SNMP managed products can develop and supply devices with a very high confidence of successful inter-working between the devices. 2. 2 Object Management SNMP management is achieved by making an SNMP call to the managed device in order to access a managed object. A managed object may be regarded as a value in a database of managed objects in the device. This database is maintained by the device and is filled with manageable items relevant to the device status, performance and configuration. The SNMP manager must know several things in order to access a managed object in the device: The type of product which is being accessed (usually by model number) so that it can identify : a) whether the product has available the managed object being requested. b) the type of information that the managed object contains. This information is held in the NMS in databases for use when the product is managed. Usually the NMS presents a map to the Network Manager with icons representing the managed objects. When the Manager clicks on the icon the Manager is prompted to define the managed object being requested. Therefore associated with the icon are the device's IP address and the product type. At the point that the Manager requests information from the product the NMS examines a definition of all of the managed objects that may be retrieved from that product type in order to prompt the Network Manager. 2. 3 MIB Definitions The database definition is called an MIB (Management Information Base) and is a definition of the format of the database of managed objects within the device. MIB definitions are written using ASN.1 (standard program definition syntax) so that the definitions are standardised. The NMS is usually provided with a copy of the MIB at configuration time so that it has a definition of the database for all product types that will be managed (workstations, file servers, routers and Metrodata multiplexers or DSU s). At the same time the managed device uses a copy of the MIB to provide the managed object information upon request. In the case of the managed device the firmware is coded so that 76-02-003D 5

SNMP MANAGEMENT CONCEPTS management information collected from different parts of the product is concentrated in to a database that is formatted according to the MIB definition. In many cases MIBS for some products or functions are predefined as a result of work performed by a consortia of vendors and placed in the public domain. This activity is supervised by the IETF (Internet Engineering Task Force) who release MIB definitions as RFC s (Request For Comment). RFC s are available from several servers connected to the Internet. MIB s relating to Metrodata products are available from Metrodata if required for parsing into a NMS. Contact Metrodata technical support dept for more information. Product specific support for HP OpenView, Sun NetManager and Castlerock SNMPc is also available. Consult your product supplier for further information. To summarise, the NMS uses a MIB to identify the nature of a managed object within a class of managed device. This information is then used to fetch the contents of the managed object from a specific instance of the managed device found in a given network. The managed device also uses the MIB to present the contents of the managed object upon request. All transactions between NMS and managed device are on the basis of a masterslave relationship where the managed device is not able to issue unsolicited information except in the case of traps. 2. 4 Traps Normally transactions between an NMS and a managed device are made where the NMS originates the request and the managed device responds. This strategy is satisfactory where the NMS is obtaining management information periodically on a need to know basis. However there are certain conditions where the managed device must inform the NMS of management information - for example in the case of faults or alarm conditions. It would be possible for the NMS to poll all devices for this information but this is usually unsatisfactory. Apart from the fact that latency is long (and increases in proportion to the number of devices on the network that are being polled) the result is to overload the network with management traffic that is polling devices which for the majority of the time have no useful information to give. SNMP uses a mechanism called a TRAP to accommodate the propagating of unsolicited management information between the managed device and the NMS. In certain predefined conditions the managed device will issue a TRAP to the manager announcing that the given condition has arisen. This process operates similarly to the servicing of CPU interrupts from peripheral devices in a computer system. Standard traps are numbered 0-5 and represent predefined conditions within the managed device. TRAP 6 is reserved for product-specific traps known as ENTERPRISE TRAPS and is used for all other trap activity. 6 76-02-003D

INITIAL SET-UP 3 INITIAL SET-UP The SNMP Enabler card is mounted in Metrodata DSU products during manufacture. It may be field fitted as an upgrade by qualified service personnel only, when working in accordance with the appropriate Metrodata Application Notes. Safety Notes: Excessive voltages are present inside the DSU unit. There are no user serviceable parts inside the unit, and the cover should not be removed by unqualified personnel. The DSU and SNMP Enabler must not be exposed to damp or condensing conditions 3. 1 LAN Connection Connection to the LAN is made via the RJ45 connector at the back of the DSU marked MAN PORT. An example rear panel showing this port on an FM series DSU is shown in Figure 2.1 below. Note that if an LM1100 is not fitted in the DSU, the MAN PORT will be covered by a blanking plug. 100-250VAC/50-400Hz MAN. Metrodata Ltd MANAGED PDH DSU PORT HAZARD WARNING! DO NOT OPEN WITH POWER CONNECTED ALARM EXT. TERMINAL DTE PORT RX LINE TX Figure 3. 1 Metrodata DSU rear panel - 240 VAC power supply Note: The Management port is designated SELV (Safety Extra Low Voltage) within the scope of EN41003. This port should only be connected to SELV ports on other equipment in accordance with EN60950 Clause 2.3. 76-02-003D 7

INITIAL SET-UP TheManagement port RJ45 pinouts are as follows : Pin No Signal 1 Tx Data +ve 2 Tx Data -ve 3 Rx Data +ve 4 Not connected 5 Not connected 6 Rx Data -ve 7 Not connected 8 Not connected Figure 3. 2 RJ45 Pinouts The pin numbering for an RJ45 connector is shown below 8 7 6 5 4 3 2 1 LOCKING TAB Figure 3. 3 RJ45 Pin numbering Pin 1 may be identified by holding the connector with the locking tab down and the front of the connector facing towards from you when Pin 1 will be on the right. 8 76-02-003D

CONFIGURATION 4 CONFIGURATION 4. 1 Management Access The MAIN MENU screen and subsequent MANAGEMENT screen are shown below. MANAGEMENT appears as a menu item if the DSU has been fitted with an LM1100 SNMP Enabler. Management via a LAN is configured through the MANAGEMENT option. Options available are described in sub-section 4.5 and onwards. MAIN SET-UP alarm extension General set-up WAN port set-up DTE set-up <menu> <menu> <menu> <menu> V.24 set-up <menu> Management <menu> Remote logon <display> Testing <menu> Special <menu> Performance data <menu> MANAGEMENT Ethernet Data-link IP UDP tcp Snmp Telnet tftp Ping <menu> <menu> <menu> <menu> <menu> <menu> <display> <menu> Figure 4. 1 Main & Management menus REMOTE LOGON is available between two FM4000, FM4200 and FM4500 units and can be used to communicate between two DSUs that are not fitted with LM1100 SNMP Enablers. REMOTE LOGON facilities available are described here for the sake of completeness. Note that the REMOTE LOGON menu item only appears after: Either: a MANAGEMENT TIMESLOT has been allocated from the WAN PORT SET-UP menu for FM4000, FM4200, or FM4500. Or: if the item DATALINK on the WAN PORT SET-UP menu has been set to ON for FM4850 and FM4900. 76-02-003D 9

CONFIGURATION 4. 2 WAN Port Set-up menus The menus used for the physical set-up of the MANAGEMENT TIMESLOT and DATALINK are shown below. The path from the MAIN SET-UP menu to WAN PORT SET-UP menu may vary from model to model with the insertion of an intermediate screen (FM4200/4500) to select either the DTE E1 port or the LINE E1 port (WAN port) for set-up action. FM4200/4500 WAN PORT SET-UP FM4000 WAN PORT SET-UP DTE E1 port <menu> Framing G.704(CRC4) Line E1 port <menu> Line coding HDB3 FM4200/4500 Signalling Enabled LINE E1 PORT Timing DTE Framing G.704 (No CRC4) Mgmt timeslot 12 Line coding HDB3 AIS Forwarding Never Signalling Disabled RAI Forwarding Never Timing DTE FM4850/4900 Mgmt timeslot 31 WAN PORT SET-UP AIS Forwarding Never Framing G.742/G.751 RAI Forwarding Never Line coding HDB3 Timing datalink Internal On HIGHLIGHTED letter - select item <escape> - exit menu Figure 4. 2 Management timeslot/datalink set-up paths The set-up options are summarised in the table below: DSU Model Menu item LINE E1 or WAN PORT FM4000 FM4200 FM4500 MGEMT TIMESLOT DSUs must be in framed mode Enter number 1-31, 0=none Setting the item permits REMOTE LOGON to appear on the screen and be used.. FM4850 FM4900 DATALINK DSUs must be in framed mode. Set item to ON. Setting the item permits REMOTE LOGON to appear on the screen and be used. Figure 4. 3 Set-up options for Remote logon 10 76-02-003D

CONFIGURATION 4. 3 Remote Logon On each DSU, the same (number) MANAGEMENT TIMESLOT must be enabled and the DSU must be operating in framed mode. The Management terminal connected to the local unit can then logon to the remote unit via the in-band connection defined by the MANAGEMENT TIMESLOT. Logon is achieved simply by selecting the REMOTE LOGON menu item on the MAIN SET-UP screen. The console telnets to the remote unit and has full acess to all menu screens and set-up functions on the remote unit. The MANAGEMENT TIMESLOT can be set-up on any timeslot providing that it has not been assigned to carry payload. The timeslot is allocated from the WAN PORT SET-UP menu. If the timeslot is already assigned to payload, an attempt to set it up for Management will result in an INVALID ENTRY message on the console screen. If a timeslot has been successfully allocated and subsequently it is re-allocated to payload using the DTE SET-UP menu, then payload will take priority and the MANAGEMENT TIMESLOT will disappear and will need to be set up again using a vacant timeslot.. Timeslot reset action would also need to be taken on the other DSU in order to maintain the same timeslot at each end of the link.. When the REMOTE LOGON is in use, the display will show as below: Metrodata FM4500: Remote connection to [nodename] Figure 4.4 Datalink messages It is advisable to give each unit an unique nodename to make identification easier. To log out of the remote unit and return to the local unit, press: <CTRL> and <]> 76-02-003D 11

CONFIGURATION 4. 4 Datalink This item is described separately to the rest of the MANAGEMENT menu, which follows in the next sub-section. If an LM1100 SNMP Enabler is fitted to each unit, then DATALINK can be exploited. Note that the DATALINK facility can only be used between two Metrodata DSU units, and that a MANAGEMENT TIMESLOT must be set-up (via the DTE SET-UP menu) on both the local and the remote units before communication can be established. Selecting the item MANAGEMENT from the MAIN SET-UP screen leads to the MANAGEMENT menu screen, and then to the DATA-LINK screen as seen in the sequence below. The DATALINK screen is used to set up the link between two Metrodata DSUs. In the case of the FM4850/FM4900, the link must be in the UP state for communication to be established. For FM4850 and FM4900, the item DATALINK on the WAN SET-UP menu switches the Datalink STATE as shown on the DATALINK menu to UP or DOWN, as appropriate. MANAGEMENT Ethernet Data-link IP UDP tcp Snmp Telnet tftp Ping <menu> <menu> <menu> <menu> <menu> <menu> <display> <menu> DATA-LINK State Up Far-end IP address 255.255.255.255 stats <display> HIGHLIGHTED letter - select item <escape> - exit menu Figure 4. 5 Management menu The DATA-LINK menu permits the IP adress of the remote unit (FAR-END IP ADDRESS) to be entered. The default value of 255.255.255.255 is a broadcast address. The item STATS allows access to link statistics, which are shown in the table below. See section 4.6.2 for interface statistics definitions. Note that the link status must be DOWN before the FAR-END IP ADDRESS can be changed. 12 76-02-003D

CONFIGURATION INTERFACE STATISTICS ifinoctets ifinucastpkts ifinnucastpkts ifindiscards ifinerrors ifinunknownprotos ifoutoctets ifoutucastpkts ifoutnucastpkts ifoutdiscards ifouterrors ifoutqlen press any key to continue: Figure 4. 6 Interface statistics 4. 5 Management menu The Management menu provides access to a variety of tools which are essential for integrating Metrodata products into a Network Management System. The network will usually comprise a variety of devices from a variety of suppliers, and the Metrodata items will therefore be only a part of the entire network. The Management menu permit configuration of the items and provides access to relevant statistics associated with those items, as is described in the following subsections. MANAGEMENT Ethernet Data-link IP UDP tcp Snmp Telnet tftp Ping <menu> <menu> <menu> <menu> <menu> <menu> <display> <menu> Figure 4. 7 Management menu 76-02-003D 13

CONFIGURATION 4. 6 Ethernet The ETHERNET option enables the user to configure and control the Ethernet port and allows access to the port statistics. ETHERNET State Up Phys. address C2:00:C0:81: 00: 08 IP address 193.114.254.5 Network mask 255.255.255.0 Broadcast address from bit 1 AT table <display> stats <display> HIGHLIGHTED letter - select item <escape> - exit menu Figure 4. 8 Ethernet menu When in the UP STATE the port is active and in the DOWN STATE the port is disabled. Note that the IP address, Network mask and Broadcast address parameters may only be configured when the Ethernet state is DOWN. The PHYSICAL ADDRESS is the Ethernet address of the Ethernet interface incorporated in the SNMP Enabler. This address is an unique hexadecimal number for every Ethernet interface in the world, and is assigned to an NIC by the manufacturer. The IP ADDRESS of the Ethernet port is configured using the IP option. IP Addresses consist of four groups of decimal numbers with values between 0 and 255, which define the node network address. The NETWORK MASK option defines the mask for the network to which the Ethernet port is connected. The mask is used for the IP address recognition process for incoming messages. BROADCAST ADDRESS defines the first bit of an Ethernet packet header that is used to identify broadcast packets. The AT TABLE and STATISTICS items follow immediately below. 14 76-02-003D

CONFIGURATION 4. 6. 1 The Address Translation (AT) table The Address Translation (AT) table is accessed through the AT option. This table shows address mapping between IP and Ethernet addresses. IP address Ethernet address 193.114.254.5 0:C0:810:3:1:C 128.83.112.95 9C:43:76:00::H7 press any key to continue Figure 4. 9 AT table Note that communication cannot be established between two Ethernet devices until the AT table of each is complete for those devices. A message from the IP layer cannot be transmitted unless the AT table contains the appropriate Ethernet address for the IP address being called. If the physical address is absent from the AT table, an ARP (Address Resolution Protocol) process is initiated. ARP is a low level TCP/IP protocol which is used to get a node s physical address when only its logical IP address is known. The ARP sends an Ethernet broadcast packet and awaits a response containing the Ethernet address from the unit which possesses the broadcast IP address. Products with firmware Version 3.xx or higher have a decaying AT table, whereby the AT table contents decay over a period of approximately 4 hours. This decay process has the effect of causing the AT table to be updated regularly, since an empty AT table (or an absent entry) will cause an ARP to be initiated. Note: Replacing a system object in a network (e.g. a router, DSU or a Network management workstation) will cause an interruption in network communications until the device AT table has been restored. 76-02-003D 15

CONFIGURATION 4. 6. 2 Interface Statistics INTERFACE STATISTICS provides a dump of packet throughput at the Ethernet driver level of the stack referenced by the SNMP variable name. INTERFACE STATISTICS ifinoctets ifinucastpkts ifinnucastpkts ifindiscards ifinerrors ifinunknownprotos ifoutoctets ifoutucastpkts ifoutnucastpkts ifoutdiscards ifouterrors ifoutqlen press any key to continue: Figure 4. 10 Interface statistics The data variables definitions are listed below. The items on this page do not appear on Metrodata products: Variable ifmtu ifspeed ifphysaddress ifadminstatus IfOperStatus iflastchange Definition The size of the largest datagram which can be sent/received on the interface, specified in octets. An estimate of the interface s current bandwidth in bits/second. The interface s address at the protocol layer immediately below the network layer in the protocol stack. The desired state of the interface. Testing state does not permit operational packets to be passed. The current state of the interface. Testing state does not permit operational packets to be passed. The value of sysuptime at the time the interface entered its current operational state. If the current state was entered before the last system initialisation, the object contains zero value. 16 76-02-003D

CONFIGURATION The items below do appear on Metrodata products: Variable ifinoctets ifinucastpkts ifinnucastpkts ifindiscards ifinerrors ifinunknownprotos ifoutoctets ifoutucastpkts ifoutnucastpkts ifoutdiscards ifouterrors ifoutqlen Definition The total number of octets received on the interface, including framing characters. The number of subnetwork-unicast packets delivered to a higher layer protocol. The number of non-unicast packets delivered to a higher-layer protocol. Typically, these may be ARP packets (and IPX packets for mixed IP/IPX environments). The number of inbound packets which were chosen to be discarded even though no errors had been detected to prevent their delivery to a higher-layer protocol. The number of inbound packets that contained errors preventing their delivery to a higher-layer protocol. The number of packets received by the interface which were discarded because of an unknown or unsupported protocol. The total number of octets transmitted from the interface, including framing characters. The total number of packets that higher-level protocols requested to be transmitted to a subnetwork-unicast address, including those that were discarded or not sent. The total number of packets that higher-level protocols requested to be transmitted to a non-unicast address, including those that were discarded or not sent. The number of outbound packets which were chosen to be discarded even though no errors had been detected to prevent their being transmitted. The number of outbound packets that could not be transmitted because of errors. The length of the outbound packet queue (in packets). The following item, which is part of the MIB definitions, is not implemented in Metrodata products: ifspecific A reference to MIB definitions specific to the particular media being used to realise the interface. For example, if the interface is realised by an ethernet, the value of this object refers to a document defining Ethernet-specific objects. 76-02-003D 17

CONFIGURATION 4. 7 IP The IP menu is used to configure the stack Level 2 settings and view statistics for the packet activity at that level. IP default TTL 32 Max reassy time Routing table Forwarding Stats 5 sec <display> Disabled <display> Figure 4. 11 IP Menu DEFAULT TTL defines the IP packet TIME TO LIVE value in number of hops. If the value is exceeded, the packet will be destroyed on the assumption that it has become lost. MAXIMUM REASSEMBLY TIME defines the maximum time permitted for re-assembly of IP message fragments being received at the interface. The ROUTING TABLE and its use is described in Section 3.3.1 below FORWARDING is either enabled or disabled. In the disabled state, which is usually selected, the node will simply discard IP messages which are not addressed to it. In the enabled state, the node will attempt to forward IP messages which it cannot process. 18 76-02-003D

CONFIGURATION 4. 7. 1 The IP Routing Table The ROUTING TABLE is used to determine the optimum route to be taken by IP packets arriving for transmission at the IP layer. The screen display shows the IP destination and next hop addresses, IP address mask and protocol/connection information. A typical routing table is shown below. The routes shown are known as NORMAL, SPECIFIC and DEFAULT routes. These will be explained later. Destination Next hop I/face Type Prot Age Mask Route type 193.114.254.0 193.114.112.0 Enet direct local 4589 255.255.255.128 Normal direct 193.114.254.128 193.114.254.30 Enet indirect local 5576 255.255.255.128 Normal indirect 193.114.254.132 193.114.254.40 Enet direct local 7643 255.255.255.255 Specific 0. 0. 0. 0 193.114.254.50 Enet indirect local 45673 0. 0. 0. 0 Default Figure 4. 12 Routing table display Definitions of the table contents are: Destination is the IP address of the route s ultimate Destination. Next Hop is the IP address of the next node on the route to the Destination. I/f is the interface that this route uses. Type describes the type of connection needed to pass the message to the next hop location. Protocol is a description of the protocol used. Age is the age in seconds of this route on the system. Mask is a pattern of bits used as a tool to match IP addresses and hence to define routes for messages. 76-02-003D 19

CONFIGURATION The routing table is shown again below, and is processed in the sequence described: Destination Next hop I/face Type Prot Age Mask Route type 193.114.254.0 193.114.112.0 Enet direct local 4589 255.255.255.128 Normal direct 193.114.254.128 193.114.254.30 Enet indirect local 5576 255.255.255.128 Normal indirect 193.114.254.132 193.114.254.40 Enet direct local 7643 255.255.255.255 Specific 0. 0. 0. 0 193.114.254.50 Enet indirect local 45673 0. 0. 0. 0 Default Figure 4. 13 Routing table display An incoming IP packet carries an IP destination address. This Packet Address and the routing table Destination addresses are ANDed in turn against the mask. In this case let us assume that the packet IP address is 193.114.254.132. A match exists if the AND results are the same for the Packet address and the Table address. Routing Table first row: a) Let us examine and AND the numbers in the IP packet address and the first row mask: 193.114.254.132 11000001.01110010.11111110.10000100 255.255.255.128 11111111.11111111.11111111.10000000 AND result 11000001.01110010.11111110.10000000 b) Now let us do the same for the first Table address in the routing table and the first row mask: 193.114.254.0 11000001.01110010.11111110.00000000 255.255.255.128 11111111.11111111.11111111.10000000 AND result 11000001.01110010.11111110.00000000 The AND produces non-matching results, and therefore this is not an acceptable route. In fact only IP addresses between 0 and 127 will be passed by this mask, and IP addresses between 128 and 255 exist on a different sub-network. 20 76-02-003D

CONFIGURATION Routing Table second row: a) Let us examine and AND the numbers in the IP packet address and the second row mask: 193.114.254.132 11000001.01110010.11111110.10000100 255.255.255.128 11111111.11111111.11111111.10000000 AND result 11000001.01110010.11111110.10000000 b) Now let us do the same for the second Table address in the routing table: 193.114.254.128 11000001.01110010.11111110.10000000 255.255.255.128 11111111.11111111.11111111.10000000 AND result 11000001.01110010.11111110.10000000 d) The AND returns the same (matching) result for both the IP Packet address and the Table address. Therefore the route with destination 193.114.254.128 is a feasible route for the packet. e) Further examination of the AND indicates that the mask being used will pass addresses from 193.114.254.128.to 193.114.254.255 The implication of this is that we have a NORMAL route for a range of IP packet addresses. Routing Table third row: Let us now do the same for the third row of the routing table, with the same IP packet address as previously, but with the mask from the third row: a) Let us examine and AND the numbers in the IP packet address: 193.114.254.132 11000001.01110010.11111110.10000100 255.255.255.255 11111111.11111111.11111111.11111111 AND result 11000001.01110010.11111110.10000100 b) Now let us do the same for the third Table address in the routing table: 193.114.254.132 11000001.01110010.11111110.10000100 255.255.255.255 11111111.11111111.11111111.11111111 AND result 11000001.01110010.11111110.10000100 The AND results match, and therefore we have an acceptable route. c) Further examination of the AND indicates that the mask being used will pass only the address 193.114.254.132. This is known as a SPECIFIC route, which will pass only a single packet address. 76-02-003D 21

CONFIGURATION Routing Table fourth row: Let us now do the same for the fourth row of the routing table, with the same IP packet address as previously, but with the mask from the fourth row: a) Let us examine and AND the numbers in the IP packet address with the fourth row mask: 193.114.254.132 11000001.01110010.11111110.10000100 0.0.0.0 00000000.00000000.00000000.00000000 AND result 00000000.00000000.00000000.00000000 b) Now let us do the same for the fourth Table address in the routing table: 0.0.0.0 00000000.00000000.00000000.00000000 0.0.0.0 00000000.00000000.00000000.00000000 AND result 00000000.00000000.00000000.00000000 The AND results match, and therefore we have an acceptable route. Further examination of the AND indicates that the mask being used will pass all IP packet addresses. This is known as a DEFAULT route Most Specific Route: It is common for the AND to pass several Table addresses, thus producing several possible routes. In this case, the associated masks are compared in order to select the most specific matching route, which is then used for the IP packet. The most specific route is defined as the mask which has the first zero in the least significant bit position. The next task is to select the Most Specific matching route, which should be the most efficient way to the ultimate destination. From the examples above for the packet IP address 193.114.254.132, a match was produced from the AND for the following masks: Table Address Mask Mask Binary 193.114.254.128 255.255.255.128 11111111.11111111.11111111.10000000 193.114.254.132 255.255.255.255 11111111.11111111.11111111.11111111 0.0.0.0 0.0.0.0 00000000.00000000.00000000.00000000 The Most Specific route is defined as the route with the mask which has the first zero in the least significant position. In this case, it is mask 255.255.255.255, since this has no zeros. Note that this mask passes only IP messages which are the Table IP address. Mask 255.255.255.128 is a NORMAL route, which passes a range of IP addresses, and mask 0.0.0.0 is a DEFAULT route which passes all IP addresses. Notes: 1) If there is no match with any of the Table Destination address entries, an ipnoroute situation exists, and the packet is discarded. The ipnoroute counter is then incremented to log the occurrence. A NO MATCH situation implies that the routing table does not have a default route in it. 2) If only a single match is found, the packet is forwarded to the next hop destination without further processing to determine the most specific route. 22 76-02-003D

CONFIGURATION 4. 7. 2 IP Statistics The IP STATISTICS display gives a dump of the packet activity at the IP layer (layer 2) referenced by the SNMP variable name. IP Statistics ipinreceives icmpinmsgs icmpoutechos ipinhdrerrors icmpinerrors icmpoutechoreps ipinaddrerrors icmpindestunreachs icmpouttimestamps ipforwdatagrams icmpintimeexcds icmpouttimestampreps ipinunknownprotos icmpinparmprobs icmpoutaddrmasks ipindiscards icmpinsrcquenchs icmpoutaddrmaskreps ipindelivers icmpinredirects ipoutrequests icmpinechos ipoutdiscards icmpinechoreps ipoutnoroutes icmpintimestamps ipreasmreqds icmpintimestampreps ipreasmoks icmpinaddrmasks ipreasmfails icmpinaddrmaskreps ipfragoks icmpoutmsgs ipfragfails icmpouterrors ipfragcreates icmpoutdestunreachs iproutingdiscards icmpouttimeexcds icmpoutparmprobs icmpoutsrcquenchs icmpoutredirects press any key to continue: press any key to continue: press any key to continue: Figure 4. 14 IP Statistics display 76-02-003D 23

CONFIGURATION The data definitions are given below: Variable ipinreceives ipinhdrerrors ipinaddrerrors ipforwdatagrams ipinunknownprotos ipindiscards ipindelivers ipoutrequests ipoutdiscards ipoutnoroutes ipreasmtimeout ipreasmreqds ipreasmoks ipreasmfails ipfragoks ipfragfails ipfragcreates Definition The total number of input datagrams received by the IP layer, including those received in error. The number of input datagrams discarded due to errors in their IP headers. The number of input datagrams discarded because the IP address in their IP header s destination field was not a valid address to be received at this entity. The number of input datagrams for which this entity was not their final IP destination, and as a result of which an attempt was made to find a route to forward them to that final destination. The number of locally-addressed datagrams received successfully but discarded because of an unknown or unsupported protocol. The number of locally-addressed datagrams for which no problems were encountered to prevent their continued processing, but which were discarded. This counter excludes any datagrams discarded whilst awaiting re-assembly. The total number of input datagrams successfully delivered to IP user-protocols (including ICMP) The total number of IP datagrams which local IP user-protocols (incl ICMP) supplied to IP in requests for transmission. This counter excludes any counted in ipforwdatagrams. The number of output IP datagrams for which no problem was found to prevent their transmission, but which were discarded. The number of IP datagrams discarded because no route could be found to transmit them to their destination. This counter includes any packets counted in ipforwdatagrams which meet the no route criterion. The maximum number of seconds which received fragments are held while they are awaiting reassembly at this entity The number of IP fragments received which needed to be reassembled at this entity. The number of IP datagrams successfully reassembled. The number of failures detected by the IP re-assembly algorithm. This may not equal the number of discarded IP fragments because some algorithms combine fragments on receipt. The number of IP datagrams that have been successfully fragmented at this entity. The number of IP datagrams that have been discarded because they needed to be fragmented, but could not be, e.g. because their Don t fragment flag was set. The number of IP datagram fragments that have been generated as a result of fragmentation at this entity. 24 76-02-003D

CONFIGURATION Variable icmpinmsgs icmpinerrors icmpindestunreachs icmpintimeexcds icmpinparmprobs icmpinsrcquenchs icmpinredirects icmpinechos icmpinechoreps icmpintimestamps icmpintimestampreps icmpinaddrmasks icmpinaddrmaskreps icmpoutmsgs icmpouterrors icmpoutdestunreachs icmpouttimeexcds icmpoutparmprobs icmpoutredirects icmpoutechos icmpoutechoreps icmpouttimestamps Definition The total number of ICMP messages which the entity received, including those counted by icmpinerrors The number of ICMP messages which the entity received but determined as having ICMP-specific errors. The number of ICMP Destination Unreachable messages received. The number of ICMP Time Exceeded messages received. The number of ICMP Parameter Problem messages received. The number of ICMP Source Quench messages received. The number of ICMP Redirect messages received. The number of ICMP Echo Request messages received. The number of ICMP Echo Reply messages received. The number of ICMP Timestamp Request messages received. The number of ICMP Timestamp Reply messages received. The number of ICMP Address Mask Request messages received. The number of ICMP Address Mask Reply messages received. The total number of ICMP messages which this entity attempted to send, including those counted by icmpouterrors. The number of ICMP messages which this entity did not send owing to problems within ICMP such as lack of buffers. Errors arising outside ICMPare not included. The number of ICMP Destination Unreachable messages sent The number of ICMP Time Exceeded messages sent. The number of ICMP Parameter Problem messages sent. The number of ICMP Redirect messages sent The number of ICMP Echo Request messages sent. The number of ICMP Echo Reply messages sent. The number of ICMP Timestamp Request messages sent. icmpouttimestampreps The number of ICMP Timestamp Reply messages sent. icmpoutaddrmasks The number of ICMP Address Mask Request messages sent. icmpoutaddrmaskreps The number of ICMP Address Mask Reply messages sent. 76-02-003D 25

CONFIGURATION 4. 8 UDP The UDP menu gives access to the UDP stack layer. UDP Port number 161 Trap port 162 Stats Figure 4. 15 UDP menu The PORT NUMBER and TRAP PORT number are predefined by SNMP and are for information only. 4. 8. 1 UDP Statistics The UDP STATISTICS display gives access to the packet activity at this stack layer referenced by the SNMP variable name. UDP Statistics udpindatagrams udpnoports udpinerrors udpoutdatagrams press any key to continue: Figure 4. 16 UDP statistics The data definitions of items listed on the screen are: <display> Variable udpindatagrams udpnoports udpinerrors udpoutdatagrams Definition The total number of UDP datagrams delivered to UDP users. The total number of received UDP datagrams for which there was no application at the destination port. The number of received UDP datagrams that could not be delivered for reasons other than the lack of an application at the destination port. The total number of UDP datagrams sent from this entity. 26 76-02-003D