XP4 SNMPInterface Users Manual

Digital Microwave Corporation SNMP Interface User Manual
1. Change Control
Revision Date Author Comments
Draft 01 15/10/96 Neil Ross, Initial draft.
Colin Sleigh
Draft 02 Colin Sleigh
Draft 03 14/03/97 Neil Mitchell
Draft 04 01/04/97 Neil Mitchell
Draft 05 Neil Mitchell 1.3 - 1.4 upgrade
Draft 06 16/05/98 Neil Mitchell 1.4 - 2.0 upgrade
A 5/10/98 Kelly Smith Innova Released Document
B 02/11/98 Kelly Smith DMC Released Document
2. Table Of Contents
1. CHANGE CONTROL ........................................................................................................ 1
2. TABLE OF CONTENTS.................................................................................................... 1
3. OBJECTIVES AND SCOPE.............................................................................................. 6

3.1. OBJECTIVES AND SCOPE ................................................................................................... 6
3.2. INTENDED AUDIENCE ......................................................................................................... 6
3.3. DOCUMENT STRUCTURE .................................................................................................... 6
4. INTRODUCTION............................................................................................................... 7
4.1. FUNCTIONAL OVERVIEW .................................................................................................... 7
4.2. HARDWARE OVERVIEW ..................................................................................................... 8
4.2.1. Physical Description ................................................................................................. 8
4.2.2. Hardware Block Diagram........................................................................................ 10
4.2.2.1. CPU Subsystem........................................................................................................... 13
4.2.2.2. Memory Configuration .................................................................................................. 13
4.2.2.3. Flash - Non Volatile Storage......................................................................................... 13
4.2.2.4. SRAM .......................................................................................................................... 13
4.2.2.5. SPI Serial EEPROM ..................................................................................................... 13
4.2.2.6. SPI RTC (Real Time Clock).......................................................................................... 14
4.2.2.7. Dual Port RAM ............................................................................................................. 14
4.2.2.8. Memory Map ................................................................................................................ 15
4.2.2.9. CPU Interrupts ............................................................................................................. 15
4.2.2.10. RS232 VT100 Interface .............................................................................................. 15
4.2.2.11. Ethernet Interface ....................................................................................................... 16
4.2.2.12. RS232/RS422 SLIP/PPP Interface............................................................................. 16
4.2.2.13. IDU High Bandwidth Interface..................................................................................... 16
4.3. SOFTWARE OVERVIEW .................................................................................................... 16
4.4. EXAMPLE NETWORK TOPOLOGIES .................................................................................... 17
4.4.1. Management of Multiple Radios at One Site using Ethernet.................................... 17
4.4.2. Management of Multiple Radios at One Site using SLIP ......................................... 18
4.4.3. Management of Daisychained Radio Links ............................................................. 22
4.4.4. Management of Radios using Modem Dial Up ........................................................ 25
4.4.5. Management of Co-located and Non Co-located Radios......................................... 26
4.4.6. Management of Co-located and Non Co-Located Radios Via Ethernet ................... 27
4.4.7. Some Network Management Topology Design Considerations ............................... 29
510-000011-003, Rev. B Page 1 November, 1998

4.4.8. IP Routing in a 1+1 Protected Link ......................................................................... 30

4.4.8.1. Interconnecting Co-located SNMPs via Ethernet ........................................................... 31
4.4.8.2. Frequency Diversity Mode and Dual Link Mode............................................................. 31
4.4.8.3. General Rules .............................................................................................................. 32
4.4.9. Hot Standby Mode ................................................................................................. 33
4.4.9.1. General Rules .............................................................................................................. 34
4.5. MANAGING VIA SERIAL PORT ............................................................................................ 35
5. SNMP OVERVIEW.......................................................................................................... 36
5.1. NETWORK MANAGEMENT BASICS ..................................................................................... 36
HISTORICAL BACKGROUND ..................................................................................................... 36
RECENT DEVELOPMENTS ........................................................................................................ 36
TERMINOLOGY ....................................................................................................................... 36
END-USER MODEL ................................................................................................................. 36
SNMP COMPONENTS ............................................................................................................ 37
5.1.1. History of SNMP .................................................................................................... 37
5.1.2. SNMP Design Constraints...................................................................................... 38
SIMPLE NETWORK MANAGEMENT PROTOCOL ......................................................................... 38
OSI NETWORK MANAGEMENT ................................................................................................ 38
SNMP NETWORK MANAGEMENT ............................................................................................ 38
LIGHTWEIGHT TRANSPORT PROTOCOL (UDP) .......................................................................... 38
LIMITED USE OF TRAPS .......................................................................................................... 38
5.1.3. SNMPV1 Reference Documents ............................................................................ 39
STRUCTURE OF MANAGEMENT INFORMATION RFC 1155 ........................................................... 39
MANAGEMENT INFORMATION BASE- RFC1213 ......................................................................... 39
MIB STRUCTURE ................................................................................................................... 40
EXAMPLE 1............................................................................................................................ 40
EXAMPLE 2............................................................................................................................ 40
SIMPLE NETWORK MANAGEMENT PROTOCOL-RFC 1157 .......................................................... 40
BASIC OPERATIONS ............................................................................................................... 41
HOW SNMP V1 WORKS........................................................................................................ 41
REQUESTS ............................................................................................................................ 41
RESPONSES .......................................................................................................................... 41
5.1.4. ASN1 - Abstract Syntax Notation One .................................................................... 42
6. SNMP INTERFACES ...................................................................................................... 42
6.1. INTERFACE DESCRIPTION................................................................................................. 42
6.2. CONNECTOR PINOUTS ..................................................................................................... 43
6.2.1. VT100 8-WAY BERG Connector ............................................................................ 44
6.2.2. RS232 SLIP/PPP 8-WAY BERG Connector ........................................................... 45
6.2.3. RS422 SLIP/PPP 8-WAY BERG Connector ........................................................... 45
6.2.4. RS422 SLIP/PPP Connector .................................................................................. 45
6.2.5. VT100 Connector ................................................................................................... 45
6.2.6. RS232 SLIP/PPP Connector .................................................................................. 46
6.2.7. RJ45 Ethernet Unshielded Twisted Pair Connector................................................. 46
6.3. CABLES ......................................................................................................................... 48
6.3.1. RS422 SLIP/PPP Interface Cable........................................................................... 47
6.3.2. VT100 Interface Cable............................................................................................ 47
6.3.2.1. VT100 Interface Cable (Female 25 Way D Type) .......................................................... 47
6.3.2.2. VT100 Interface Cable (Female 9 Way D Type) ............................................................ 48
6.3.3. RS232 SLIP/PPP Interface Cable........................................................................... 48
6.3.3.1. RS232 SLIP/PPP Interface Cable(Female 25 Way D Type) .......................................... 48
6.3.3.2. RS232 SLIP/PPP Interface Cable (Female 9 Way D Type) ........................................... 49
6.3.4. RJ45 Ethernet Unshielded Twisted Pair Interface Cable ......................................... 49
6.3.5. Serial to serial ........................................................................................................ 49
7. VT100 USER INTERFACE OPERATION........................................................................ 50

7.1. RS232 VT100 INTERFACE OPERATION ............................................................................ 50

7.1.1. PC Terminal Link Installation. ................................................................................. 50
7.1.2. To connect a PC to the SNMP card....................................................................... 50
7.1.3. 1.1.3. To Run the VT100 emulation under Windows ............................................. 50
7.2. INITIAL LOG IN PROCEDURE ............................................................................................. 51
7.2.1. To log on for the first time:...................................................................................... 51
7.2.2. To login with user accounts configured:.................................................................. 52
7.3. MAIN MENU .................................................................................................................... 53
7.3.1. To select an option................................................................................................. 53
7.3.2. To Exit the Interface without saving changes.......................................................... 53
7.3.3. To Exit the Interface Saving changes ..................................................................... 54
7.4. EVENT LOGGER .............................................................................................................. 54
7.4.1. Navigating Through the list of Events ..................................................................... 55
7.4.1.1. Browsing the list of events ............................................................................................ 55
7.4.1.2. Examining the latest event............................................................................................ 55
7.4.1.3. Clearing the Event Log ................................................................................................. 55
7.4.1.4. Configuring Event Filter Level....................................................................................... 55
7.5. ERROR LOGGER ............................................................................................................. 56
7.5.1. Navigating Through the list of Errors....................................................................... 56
7.5.1.1. Browsing the list of errors ............................................................................................. 56
7.5.1.2. Examining the latest error............................................................................................. 57
7.5.1.3. Clearing the Error Log .................................................................................................. 57
7.5.1.4. Configuring Error Filter Level........................................................................................ 57
7.6. USER OPTIONS MENU ..................................................................................................... 58
7.6.1. Adding User Accounts............................................................................................ 58
7.6.2. Deleting User Accounts .......................................................................................... 59
7.6.3. Changing User Passwords ..................................................................................... 59
7.7. CODE DOWNLOAD MENU ................................................................................................. 60
7.7.1. Configuring TFTP Server IP Address...................................................................... 60
7.7.2. Configuring TFTP Target Port ................................................................................ 60
7.7.3. Configuring Image Filenames ................................................................................. 61
7.7.4. Configuring TFTP Inter Packet Time-out ................................................................ 61
7.7.5. Reprogramming the SNMP..................................................................................... 61
7.7.6. Reprogramming a Local/Remote IDU/ODU ............................................................ 62
7.8. NETWORK PORT CONFIGURATION MENU ........................................................................... 63
7.8.1. Ethernet Management Port Menu........................................................................... 64
7.8.1.1. Configuring Ethernet Management Port - Gateway IP Address...................................... 64
7.8.1.2. Configuring Ethernet Management Port - IP Broadcast ................................................. 65
7.8.1.3. Configuring Ethernet Management Port - Default Router IP Address ............................. 65
7.8.1.4. Configuring Ethernet Management Port - Default Router Subnet Mask.......................... 65
7.8.1.5. Configuring Ethernet Management Port - IP Address .................................................... 65
7.8.1.6. Configuring Ethernet Management Port - Subnet Mask ................................................. 66
7.8.1.7. Configuring Ethernet Management Port - Trap Destination IP Addresses ...................... 67
7.8.1.8. Configuring Ethernet Management Port - Trap Generation............................................ 68
7.8.1.9. Configuring Ethernet Management Port - PM Trap Configuration .................................. 68
7.8.1.10. Configuring Ethernet Management Port - Ethernet Connector Type............................. 69
7.8.1.11. Configuring Ethernet Management Port - Booted Indicator.......................................... 69
7.8.2. Serial Management Ports 1 & 2.............................................................................. 70
7.8.2.1. Configuring Serial Management Port - Default Router IP Address ................................. 70
7.8.2.2. Configuring Serial Management Port - Default Router Subnet Mask.............................. 71
7.8.2.3. Configuring Serial Management Port - IP Address ........................................................ 71
7.8.2.4. Configuring Serial Management Port - Subnet Mask ..................................................... 71
7.8.2.5. Configuring Serial Management Port - Trap Destination IP Address.............................. 72
7.8.2.6. Configuring Serial Management Port - Trap Generation ................................................ 72
7.8.2.7. Configuring Serial Management Port - PM Trap Configuration ...................................... 73
7.8.2.8. Configuring Serial Management Port - Baud Rate......................................................... 74
7.8.2.9. Configuring Serial Management Port - Interface Type. .................................................. 74
7.8.2.10. Configuring Serial Management Port - Booted Indicator .............................................. 74

7.8.2.11. Configuring Serial Management Port - Protocol. ......................................................... 75

7.8.3. Dial-Out Parameters Menu..................................................................................... 75
7.8.3.1. Configure Modem Type ................................................................................................ 76
7.8.3.2. Configure Alarm Trap Generation ................................................................................. 76
7.8.3.3. Configuring Robotics User String.................................................................................. 76
7.8.3.4. Configuring Motorola User String.................................................................................. 76
7.8.3.5. Resetting Robotics String ............................................................................................. 77
7.8.3.6. Resetting Motorola String ............................................................................................. 77
7.8.3.7. Configuring Dialling Prefix A ......................................................................................... 77
7.8.3.8. Configuring Dialling Prefix B ......................................................................................... 77
7.8.3.9. Configuring Number of Modem Command Retries........................................................ 77
7.8.3.10. Configuring Modem Command Time-out .................................................................... 78
7.8.3.11. Configuring Modem Connection Time-out ................................................................... 78
7.8.4. Dial-Out Parameters Sub Menu.............................................................................. 79
7.8.4.1. Configuring Daily Update.............................................................................................. 79
7.8.4.2. Configuring Daily Update Time ..................................................................................... 79
7.8.4.3. Configuring Password Authentication ........................................................................... 80
7.8.4.4. Configuring Authentication String ................................................................................. 80
7.8.4.5. Configuring User Name ................................................................................................ 80
7.8.4.6. Configuring User Password .......................................................................................... 80
7.8.4.7. Configuring No. of Authentication Retries ..................................................................... 81
7.8.4.8. Configuring Authentication Time-out............................................................................. 81
7.8.4.9. Configuring No. of Protocol Retries............................................................................... 81
7.8.4.10. Configuring Protocol Timeout ..................................................................................... 81
7.8.4.11. Configuring IP Routing ............................................................................................... 81
7.8.4.12. IP Routing Of Traps - Causing Dial-Out...................................................................... 82
7.8.5. Routed IP Messages Causing Dial-Out................................................................... 85
7.8.6. XP4 Management Menu......................................................................................... 86
7.8.6.1. Configuring XP4 Management Port - Default Router IP Address ................................... 86
7.8.6.2. Configuring XP4 Management Port - Default Router Subnet Mask ................................ 87
7.8.6.3. Configuring XP4 Management Port - IP Address........................................................... 87
7.8.6.4. Configuring XP4 Management Port - Subnet Mask ....................................................... 87
7.8.6.5. Configuring XP4 Management Port - Trap Destination IP Address ................................ 87
7.8.6.6. XP4 Management Port - Trap Generation ..................................................................... 89
7.8.6.7. XP4 Management Port - PM Trap Configuration ........................................................... 89
7.8.6.8. Configuring XP4 Management Port - Booted Indicator .................................................. 90
7.8.7. Inter-Connected Co-Located IP Address................................................................. 90
7.8.8. Co-Located XP4 Port IP Address ........................................................................... 90
7.9. SYSTEM CONFIGURATION ................................................................................................ 91
7.9.1. System Configuration General................................................................................ 92
7.9.1.1. Configuring System Name............................................................................................ 92
7.9.1.2. Configuring Automatic Logout Time.............................................................................. 92
7.9.1.3. Configuring System Time ............................................................................................. 93
7.9.1.4. Configuring System Date.............................................................................................. 93
7.9.1.5. Setting Management Port Defaults ............................................................................... 93
7.9.1.6. Node Active Configuration ............................................................................................ 94
7.9.1.6.1. Node Active Trap Configuration ............................................................................. 94
7.9.1.6.2. Daily Time ............................................................................................................. 94
7.9.1.7. Resetting the SNMP ..................................................................................................... 95
7.9.2. System Configuration - Performance Alarm Thresholds.......................................... 95
7.9.2.1. Configuring Errored Seconds and Severely Errored Seconds per Hour.......................... 96
7.9.2.2. Configuring Errored Seconds and Severely Errored Seconds per Day ........................... 96
7.9.3. System Configuration - Diagnostic Status............................................................... 96
7.9.3.1. Non Intrusive Diagnostics Menu ................................................................................... 97
7.9.3.2. Intrusive Diagnostics Menu........................................................................................... 98
7.9.3.2.1. Starting Intrusive Diagnostics ................................................................................ 98
7.9.4. System Configuration - Radio Stack Parameters .................................................... 99
7.9.4.1. Configuring Maximum Number of Transmit Retries....................................................... 99
7.9.4.2. Configuring Transmit Monitor Timer ........................................................................... 100
7.9.5. System Configuration - Software Version ............................................................. 100

7.9.6. Reset Status Menu............................................................................................... 101

7.9.6.1. Resetting While Error Count and Program Count........................................................ 102
7.9.6.2. Resetting Critical Error Count ..................................................................................... 102
7.10. SAVING MODIFICATIONS TO NON-VOLATILE MEMORY ...................................................... 102
8. SNMP NETWORK PORT CONFIGURATION ............................................................... 103
8.1. NETWORK PORT PARAMETERS....................................................................................... 103
8.1.1. Ethernet Port........................................................................................................ 103
8.1.2. Serial Management Port 1.................................................................................... 104
8.1.3. Serial Management Port 2.................................................................................... 106
8.1.4. XP4 Port .............................................................................................................. 108
8.2. NETWORK PORT CONFIGURATION EXAMPLES .................................................................. 108
8.2.1. 2 SNMPs Routing via SLIP................................................................................... 109
8.2.2. 2 SNMPs Routing via SLIP and Ethernet.............................................................. 111
8.2.3. 2 SNMPs Routing via XP4 and SLIP .................................................................... 113
8.2.4. 2 SNMPs Routing via XP4, SLIP and Ethernet ..................................................... 115
8.2.5. 3 SNMPs Routing via SLIP................................................................................... 117
8.2.6. 3 SNMPs Routing via SLIP and XP4 .................................................................... 120
8.2.7. 4 SNMPs Routing over SLIP and XP4 .................................................................. 122
8.2.8. SNMP’s Routing via SLIP, Ethernet and XP4 ....................................................... 125
8.2.9. 4 SNMPs Routing via SLIP and Ethernet.............................................................. 128
8.2.10. SNMPs Routing over SLIP, Ethernet, and XP4................................................... 130
8.2.11. Ethernet/LAN ..................................................................................................... 132
8.2.12. 1+1 Protection Switch Routing Test Configurations ............................................ 134
8.2.12.1. Single 1+1 Protected Link......................................................................................... 135
8.2.12.2. Single 1+1 Protected Link and Two 1+0 Links........................................................... 138
8.2.12.3. Two 1+1 Protected Links Connected in Series .......................................................... 143
8.2.12.4. Two 1+1 Protected Links Connected in Parallel ........................................................ 149
8.2.12.5. Two 1+1 Protected Links Connected in Parallel - Three Hubs ................................... 156
8.2.12.6. Single 1+1 Protected Link Managed via Serial Port ................................................... 162
8.2.12.7. Two 1+1 Protected Links and Three 1+0 Links.......................................................... 167
9. SNMP MIB ROADMAP ................................................................................................. 176
9.1. MIB II SUPPORT........................................................................................................... 176
9.2. MIB TOP LEVEL VIEW ................................................................................................... 178
9.3. ACCESSING RADIO AND SNMP DATA .............................................................................. 186
9.3.1. Security Levels..................................................................................................... 186
9.3.2. SNMP Community Names.................................................................................... 186
9.4. UNIFIED LOGIN TO THE SNMP AND XP4.......................................................................... 186
9.4.1. SNMP User Login ................................................................................................ 187
9.4.1.1. Unified Permission Levels .......................................................................................... 187
9.4.1.2. Unified Login with No User Accounts .......................................................................... 187
9.4.1.3. Example Unified Login Session .................................................................................. 187
9.4.2. VT100 User Login ................................................................................................ 188
9.5. RADIO DATA LOGIN ....................................................................................................... 188
9.6. SAVING DATA CHANGES TO THE XP4 .............................................................................. 188
9.6.1. Save Data Changes to the SNMP ........................................................................ 188
9.6.2. Uploading Data from the XP4 ............................................................................... 189
9.6.3. Adding User Accounts on the SNMP .................................................................... 190
9.6.4. Changing Passwords for the MIB ......................................................................... 190
9.6.5. Downloading new code to the SNMP and Radio................................................... 191
10. REFERENCE DOCUMENTS....................................................................................... 193
11. GLOSSARY ................................................................................................................ 196

APPENDIX A - EVENTS LOGGED BY THE EVENT LOGGER .......................................................... 197

APPENDIX B - ERRORS LOGGED BY THE ERROR LOGGER ......................................................... 199

APPENDIX C – ALARMS ........................................................................................................ 201
APPENDIX D - MODEM CONFIGURATION ................................................................................. 202
APPENDIX E - G.821 & G.826 PERFORMANCE MONITORING PARAMETERS ............................... 204
APPENDIX F - SNMP ATTRIBUTES CHANGE IMPLEMENTATION.................................................. 205
APPENDIX G - ATTRIBUTES AND THEIR SECURITY LEVELS ......................................................... 208
APPENDIX H - FUNCTIONAL ENHANCEMENTS FOR SNMP V2.0 SOFTWARE RELEASE ................. 215
3. Objectives and Scope
3.1. Objectives and Scope

The objective of the SNMP Interface User Manual is to equip the reader with the ability to configure and
operate the SNMP interface option module.
3.2. Intended Audience

The intended audience for this document is Digital Microwave Corporation personnel and customers.
It is assumed that the reader is already familiar with the configuration and operation of XP4 radios, has a
basic understanding of Network Management and IP Networking principles.
3.3. Document Structure

The remainder of this document is structured as follows :
• Section 4, Introduction, provides an overview of the functionality which the SNMP provides.
• Section 5, SNMP Overview, provides a brief overview of the history and functionality of SNMP.
• Section 6, SNMP Interfaces, describes the SNMP external interfaces, connector pinouts and cabling.
• Section 7, VT100 User Interface Operation, describes the features available via the VT100 User
Interfaces and how to use them.
• Section 8, Network Management Interface Configuration and Installation, describes how to set up the
SNMP IP Interfaces.
• Section 9, SNMP MIB Roadmap, provides a tour through the SNMP SNMP MIB.
• Section 10, Events Listing, lists all the events that can be logged by the event logging functionality.
• Section 11, Error Listing, lists all the errors that can be logged by the error logging functionality.
• Section 12, Alarms Listing, lists all the alarms that can be raised by the alarm management
functionality.

4. Introduction
4.1. Functional Overview

This section will briefly summarise the functionality offered by the SNMP and provide the reader with a
context for the sections that follow.
The primary function of the SNMP is to present a set of interfaces which allow the management of XP4
Radio Units via the SNMP protocol.
Note : It is not possible to hot insert an SNMP into an IDU.
A single SNMP will be connected to the local IDU and will manage both the local and remote IDUs and
ODUs. A summary of the features offered via SNMP to facilitate management of these units is as follows
:
• Radio Configuration Management
• Radio Status Monitoring
• G.826 and G.821 Radio Performance Monitoring
• Radio Code Download
• SNMP Management
• SNMP Code Download
• Alarm Management
• Event Logging
• Error Logging
• 1+1 Protection System Status/Configuration

An SNMP offers basic IP routing capability, which allows SNMP messages to be routed to other SNMPs
within the network topology. In this way a network of Radios can be managed via one central SNMP. It is
important to remember however that this routing functionality has restrictions associated with it and if
more powerful routing is required then purpose built IP routers should be deployed.
The SNMP also offers some of the management capabilities which are available via SNMP via a VT100
terminal interface. It should however be noted that these features are limited to configuration of SNMP
specific parameters.

4.2. Hardware Overview
4.2.1. Physical Description

The SNMP fits into the option board slot at the rear of the IDU as is illustrated in
Figure 4-1. The SNMP operates from a 5V DC power feed that is provided on the IDU option board
interface which is a DIN connector. The SNMP communicates with the main IDU CPU using a parallel
communications bus via the IDU option board interface.
IDU option
board Interface
SNMP
Figure 4-1- SNMP connected to IDU
The dimensions of the SNMP are as follows :

Width - 5.75 inches (146.05 mm)
Depth - 3 inches (76.2 mm)

Thickness - 0.063 inches (1.6 mm)
Component Height Top - 0.78 inches (20 mm)
Component Height Bottom - 0.079 inches (2 mm)

The different SNMP back panels and the associated radio front panels are shown below.
Figure 4-2 : Radio front panel with SNMP access
Figure 4-3 : SNMP accessed via SNMP back panel
FUSE
IN TRIB1 OUT IN TRIB2 OUT IN TRIB3 OUT IN TRIB4 OUT
ALARM RELAYS COMPUTER

POWER
ODU ODU ODU ODU ODU ODU ODU ODU
Figure 4-4 : Radio front panel with no SNMP access

4.2.2. Hardware Block Diagram

The SNMP hardware can be broken down into the blocks shown in Figure 4-5. The functionality of each
of the blocks will be described in the following sections :
Figure 4-5 : Hardware Block Diagram

Note :The BERG shorting jumper enables the 10Base 2 Ethernet BNC connector to be used. The berg
shorting jumper should not be connected when using 10Base T s this will deactivate the 10Base T
reducing the current consumption of the board by a maximum of 150mA.
Power 10Base-2/
VT100 Rese UTP Cheapernet
SLIP 2 LED
Interface
SLIP 1
BERG 5 BERG 1
shorting
connector
BERG 6
BERG 4
68360
SCC2 CPU
UTP
SCC3
VT100
RS232
Backplane
Connector
SRAM 1 SRAM 2
68160 Dual Port Flash 1 Flash 2

Ethernet RAM
Figure 4-6: Top and Bottom view on SNMP card with back panel access

Power 10Base-2/
LED Rese Cheapernet
Interface
BERG 1
shorting
connector
SCC2 UTP
SCC3
VT100
RS232
Backplane
Connector
SRAM 1 SRAM 2
68160 Dual Port Flash 1 Flash 2

Ethernet RAM
Figure 4-7: Top and Bottom view on SNMP card with front panel access

4.2.2.1.CPU Subsystem
The SNMP card CPU is a 25 MHz MC68360 Quad Integrated Communication Controller (QUICC) from
Motorola. The 68360 is an integrated microprocessor and peripheral combination that offers a wide range
of functionality (refer to the MC68380 User’s Manual).
The MC68360, and associated circuits are, designed to run at a clock speed of 25 MHz. Clock generation
comes from a 25MHz clock oscillator.
4.2.2.2. Memory Configuration

The card is designed to support both Flash and Static RAM. The card boots and runs from the Flash
memory.
Additional non-volatile storage is available by the use of a Serial EEPROM device connected to the SPI
port of the 68360.
The CPU is configured to boot from a 16 bit Flash device, the CPU default configuration pin settings are;
CONFIG2 CONFIG1 CONFIG0
1 0 1 CPU Enabled, global CS 16-bit
MBAR at $3FF00
4.2.2.3. Flash - Non Volatile Storage

The basic EPROM/FLASH memory allocation is 2Mbytes, organised as 1024k by 16 bits. This is
implemented by using two 1024Kbyte EPROM/FLASH devices with chip select CS0/ configured for 16
bits. The flash is designed to run with a maximum of 2 wait states at 25 MHz.
Flash devices used are Intel SMART 1024kx8 flash E28F008B, 120nsec in a 48 pin TSOP package.
4.2.2.4. SRAM
The SRAM is 2 Mbyte and is 16 bits wide. This is implemented using four 512K by 8 bit devices and is
designed to run with no wait states at 25 MHz.
SRAM devices used are a 512kx8, 55nsec in a 32 pin TSOP package.
4.2.2.5. SPI Serial EEPROM

A 2 Kbit serial EEPROM is connected to the SPI port of the MC68360. This allows additional non-volatile
storage on the SNMP card without having to use the on-board Flash. This device is used to store
management port configuration data such as IP Addresses.
The SPI device is connected to the SPI port of the MC68360 with the SPISEL pin being used to chipselect
the SPI device.
The use of the Serial EEPROM will allow the SNMP Card Flash device to be reprogrammed without
losing default data (i.e. IP Address).
The Serial EEPROM device used is the Xicor X25C08S in a 8 pin SOIC package.

4.2.2.6. SPI RTC (Real Time Clock)

A real time clock is supported on the SNMP card. The device is connected to the SPI port of the
MC68360.
The Real Time Clock device is connected to an onboard battery such that if the SNMP card power supply
fails the RTC will continue to operate.
The SPI RTC used is the Dallas Semi DS1305EN in a 20 pin TSOP package.
4.2.2.7.Dual Port RAM

An eight bit 8K (1Kx8) dual port RAM is supported on the SNMP card. This allows data to be transferred
between the SNMP card and the IDU module.
The right hand side of the DPR is connected to the IDU module and the left hand side to the SNMP
interface. DSACK0/ will be generated on completion of a read/write cycle.
The Dual Port RAM (DPR) used is the Integrated Device Technology IDT7130 in a 64 pin STQFP.
If the user chooses to use the interrupt function, a memory location called a mail box (Packets of
information are transferred between the SNMP and the IDU by way of mail boxes and packet buffers) is
assigned to each port of the DPR. The left port (assigned to the SNMP) interrupt flag is asserted when the
right port writes to memory location 3FE. The left port clears the interrupt by reading location 3FE.
Likewise, the right port interrupt flag is asserted when the left port writes to memory location 3FF and to
clear the interrupt flag the right port must read memory location 3FF.
Figure 4-8 : Dual Port RAM

4.2.2.8. Memory Map

The 68360 provides a memory controller which can be used to generate eight individual chipselects.
These chipselects can be programmed with the address range in which they are valid, the number of wait
states if programmed to provide DSACK/, the port size i.e. 8, 16 or 32 bit and whether the address range
is Read/Write or Read only.
The block size, to which the chip select can address to, is programmable going up in size, from its base
address, of 8K, 16K, 32K, 64K, 128K, 256K, 512K, 1M, 2M, 4M, 8M and 16M bytes.
All base address registers default to zero after a system reset, but CS0/ is the only line active, therefore
EPROM/FLASH are always addressed by CS0/. After a system reset, the bits of the DTACK field default
to 6 wait states.
The above options are programmed via the BR and OR register for each chipselect. Refer to the 68360
Users Manual. For more details see section 10.
The chipselects have been allocated in hardware as follows;
Chipselect Device Size Block Size Port Width Access

/CS0 Flash 2Mbyte 2Mbyte 16 Bit Byte Word R/W
/CS1 SRAM 1Mbyte 1Mbyte 16 Bit Byte, Word,
R/W
/CS2 Dual Port RAM 1Kbyte 8Kbyte 8 bit Byte, R/W
DSACK0/
/CS3 Spare
/CS4 Spare
/CS5 Spare
/CS6 SRAM 1Mbyte 1Mbyte 16 Bit Byte, Word,
R/W
/CS7 Spare
4.2.2.9. CPU Interrupts

The following table outlines the external interrupt mapping on the SNMP Maintenance Card.
INTERFACE INTERRUPT ACTIVITY

Spare IRQ1/
RTC IRQ2/ RTC interrupt 0
RTC IRQ3/ RTC interrupt 1
MC68360 Internal IRQ4/
Spare IRQ5/
Dual Port RAM IRQ6/ Dual Port RAM
Spare IRQ7/
4.2.2.10. RS232 VT100 Interface

The VT100 interface is RS232, configured as a DCE, with the bit rate set at 9600 baud detection and uses
a RJ45 connector. The interface is configured for 8 data bits, 1 start bit, 1 stop bit and no parity.
The VT100 interface is supported by the SMC of the MC68360.

The VT100 interface will also be connected to an 8 way BERG connector. This can then be used to allow
the interface, via a 8 way IDC cable, to be connected to the front of the IDU unit.
4.2.2.11. Ethernet Interface

The interface provides two types of Ethernet standards, 10BASE-T and 10BASE-2 which are software
selectable. The interface runs off SCC1 and is connected to a MC68160 Enhanced Ethernet Interface
Transceiver.
shorting jumper should not be connected when using 10Base T s this will deactivate the 10Base T
4.2.2.12. RS232/RS422 SLIP/PPP Interface

The interface provides two RS232/RS422 software selectable interfaces, via two separate RJ45
connectors. Each interface supports either SLIP or PPP. These interfaces are supported via SCC2 and
SCC3 of the 68360 processor.
Each bus uses a physically separate RS422 transceiver, the driver of which is controlled by the RTS pin
of the 68360. Each interface has its own RS232 driver which generates its own +/-12volts internally.
SCC2 - RS232/RS422 SLIP/PPP Interface 1
SCC3 - RS232/RS422 SLIP/PPP Interface 2
The two RS232/RS422 SLIP/PPP interface are connected to an 8 way BERG connector. This can then be
used to allow the interface, via a 8 way IDC cable, to be connected to the front of the IDU unit.
4.2.2.13. IDU High Bandwidth Interface

The IDU high bandwidth interface is connected to SCC4 of the processor. The interface is connected to
the DV1DATA, DV1CLK, MV1DATA and MV1CLK pins on the backplane connector. This interface is
synchronous at a clock rate of 72 Kbit/s. The IDU provides both the receive (DV1CLK) and transmit
(MV1CLK) clocks.
This interface is connected to the radio via the backplane 96 way DIN connector.
The IDU High Bandwidth interface will be supported by SCC4 of the MC68360. It should be noted that the
SNMP application software currently makes no use of this interface.
4.3. Software Overview

The following list provides an overview of the implementation technologies used in the SNMP Application
Software:
• Design Methodology - Booch Object Oriented Analysis and Design.

• Implementation Language - C++.
• Operating System - Kadak AMX Real Time Operating System.
• IP Stack - Pacific Softworks Fusion.

4.4. Example Network Topologies

This section provides some simple examples of deployments, to give a feel for the types of radio
networks that can be managed using SNMPs. It should be noted that the scenarios presented form only a
simple subset of the configurations that are possible.
It should also be noted that details of how to actually configure SNMPs will be provided in a later section
in this manual.
This section assumes that the reader has a basic understanding of IP Networking.
4.4.1. Management of Multiple Radios at One Site using Ethernet

The scenario represented in Figure 4-9 illustrates how a number of co-located radios can be managed
using SNMPs connected to an SNMP Management System, using either 10Base-T Ethernet or 10Base-2
Ethernet.
Note: Using Ethernet connections will result in the fastest possible message response from the SNMP.
SNMP 1 SNMP 2 SNMP 3
XPSurf
or
XPVision
Figure 4-9 : Management of co-located Radios via Ethernet
As has been mentioned already a single SNMP will be connected to the local IDU and manage both the
Local and Remote IDUs and ODUs to which it is connected. Thus in the context of the above scenario
SNMP1 will manage IDU1 and IDU2 i.e. it is not required to have an SNMP connected to IDU2 unless
network expansion dictates.
The Ethernet port of each SNMP has its own IP Address and Ethernet MAC address. In the configuration
shown in Figure 4-9, the SNMPs and the SNMP Manager will all have the same network address as they
are all connected to a single Ethernet network but will have different node addresses. The only limit on the
number of SNMPs that can be managed from the SNMP Manager using the configuration in Figure 4-9 is
the limit imposed by whether a Class A, B or C IP Network addressing scheme is chosen. Basically the
maximum number of possible nodes that can exist on the above Ethernet network is 16581375
(255*255*255) if a Class A Network address is chosen and 255 if a Class C Network address is chosen.

4.4.2. Management of Multiple Radios at One Site using SLIP

The scenario represented in Figure 4-10 below illustrates how a number of co-located radios can be
managed by using SNMPs daisychained together via SLIP and connected to an SNMP Management
System using either 10Base-T Ethernet\10Base-2 Ethernet\SLIP or PPP.
Note: Any IP addresses used in this manual are for example only. They should not be used to configure
working equipment.
SNMP 1 SNMP 2 SNMP 3 SNMP 4 SNMP 5
RS232/RS422 SLIP/PPP
XPSurf
or
XPVision
Figure 4-10 : Management of co-located SNMPs via daisychained SLIP connections

Note:
1. The daisychained SLIP/PPP connections can have mixed Baud rates. i.e. SNMP 1 to SNMP2
can be set to communicate at 9600 Baud while SNMP2 to SNMP3 can be set to communicate at
19200 Baud.
2. An Ethernet connection achieves a faster response from the SNMP than can be achieved by a
SLIP/PPP connection.
In the scenario shown in Figure 4-10, the SNMP Manager can be connected to SNMP1 via SLIP, PPP or
Ethernet. By daisychaining SNMP1, SNMP2, SNMP3, SNMP4 and SNMP5 together via SLIP connections
the SNMP Manager can manage the radio pairs connected to SNMP2, SNMP3, SNMP4 and SNMP5 via
SNMP1. This is achieved because each SNMP acts as a basic IP Router.
If the SNMP Manager sends a message to SNMP5 it will be routed to SNMP1 firstly. SNMP1 will route the
message to SNMP2 which will then route the message to SNMP3. SNMP3 will route the message to
SNMP4 which will then route the message to SNMP5.
Similarly if SNMP5 is responding to a message sent from the SNMP Manager, it will forward the response
to SNMP4 which will forward the response to SNMP3 which will forward the response to SNMP2 and so
on all the way back to the SNMP Manager.

The restriction of this configuration is that it will not be possible to manage radios more than one hop
away. In other words, if a radio was co-located with IDU6 which forms the other end of the radio pair
associated with IDU1 it will not be possible to manage it via the SNMP Manager. The configuration
shown in Figure 4-9 DOES NOT suffer from this restriction.
The aforementioned restriction becomes obvious when a brief overview of the SNMPs IP Routing
functionality is given. (see Figure 4-11 for a graphical representation)
I. There are four IP Ports on an SNMP :
- Ethernet
- Serial Management Port 1
- Serial Management Port 2
- XP4 Port (communications bus between SNMP and IDU which it is connected to)
II. Each IP Port must have a different IP Network address.
III. Each IP Port can have a single Default Router IP Address. The Network Address of a Ports
Default Router IP Address must correspond to the Network Address of one of the SNMPs other
three IP Ports. The default Router Subnet Mask must correspond to the selected SNMP IP port.
IV. The Default Routing functionality can be briefly described as follows:
A. On SNMP1 it can be seen that each IP Port has its own Network Address and have been
assigned Class C addresses as follows :
Ethernet Port - 222.0.1.0
Serial Management Port 1 - 222.0.2.0
Serial Management Port 2 - 222.0.3.0
XP4 Port - 222.0.4.0
B. On SNMP2 only the IP address of Serial Management Port 2 is shown. It can be seen that
the Network Address of Serial Management Port 2 of SNMP2 is the same as the Network
Address of Serial Management Port 2 of SNMP1. This is to be expected as both ports are
connected to each other thus they must both be on the same network. The IP node
addresses are different with SNMP1 being 222.0.3.1 and SNMP2 being 222.0.3.2.
C. The Network Address of the Default Route IP Address of SNMP1 Serial Management
Port 1 is 222.0.3.0 which matches the Network Address of SNMP1 Serial Management
Port 2 thus it is a legal route. The Default Route IP Address of SNMP1 Serial
Management Port 1 is 222.0.3.2 which is the IP Address of SNMP2 Serial Management
Port 2.
D. If an IP message arrives on SNMP1 Serial Management Port 1 and the Destination
Network Address of the message does not match the Network Address of SNMP1 Serial
Management Port 1 then the message will be forwarded out on the SNMP1 Port whose
Network Address matches that of the Default Route Network Address of SNMP1 Serial
Management Port 1. In this case it is SNMP1 Serial Management Port 2.
E. Similarly if an IP message arrives on SNMP1 Serial Management Port 2 and the
Destination Network Address of the message does not match the Network Address of
SNMP1 Serial Management Port 2 then the message will be forwarded out on the SNMP1
Port whose Network Address matches that of the Default Route Network Address of
SNMP1 Serial Management Port 2. In this case it is SNMP1 Serial Management Port 1.
As an example assume the SNMP Manager sends an IP message to Serial Management Port 2 of
SNMP2. The Destination IP address in the message could be 222.0.3.2 and the Source IP address will be
222.0.2.128.

Firstly a route needs to be added to the SNMP Managers routing table such that any messages destined
for the network 222.0.3.0 are sent out on the SNMP Managers port which has the Network Address
222.0.2.0.
The SNMP Manager will route the IP message destined for 222.0.3.2 to Serial Management Port 1 of
SNMP1. SNMP1 Serial Management Port1 will then compare the destination Network Address of
222.0.3.0 to its own network address of 222.0.2.0 and route the message out its default route which is
222.0.3.0 the Network address of SNMP1 Serial Management Port 2.
The IP message will arrive at SNMP2 Serial Management Port 2 where the destination Network Address
of 222.0.3.0 will be compared to its own and a match will be found. No attempt will be made to route the
message. Now that a Network match has been made the actual destination IP node address of the
incoming IP message (222.0.3.2) is compared to that of SNMP2 Serial Management Port 2 and again a
match is found. SNMP2 will then process this message and create a response message whose
Destination IP address will be 222.0.2.128 and the Source IP address will be 222.0.3.2. This response will
be forwarded out on the port on which the original request came in on and the response will arrive at
SNMP1 Serial Management Port 2.
SNMP1 Serial Management Port2 will then compare the destination Network Address of 222.0.2.0 to its
own network address of 222.0.3.0 and route the message out its default route which is 222.0.2.0 the
Network address of the SNMP Managers port.
The same principles can be applied to the case where the SNMP Manager shown in Figure 4-10 wants to
send IP messages to SNMP5.
The routing restrictions of daisychaining co-located SNMPs via SLIP (as shown in
Figure 4-10) becomes apparent when you consider the case in Figure 4-11, where the SNMP Manager
wishes to manage another Radio co-located with the IDU attached to the remote end of the IDU
connected to the XP4 Port of SNMP1. For this to be possible SNMP1 would have to be able to route an IP
message across its XP4 Port i.e. The Default Route for SNMP1 Serial Management Port 1 would have to
be the Network Address of the SNMP1 XP4 Port. If the Default Route for SNMP1 Serial Management Port
1 was the Network Address of the SNMP1 XP4 Port then SNMP Serial Management Port 2 would not be
able to be reached from the SNMP Manager.
The above restriction would not apply to the scenario shown in Figure 4-9 because the SNMPs are not
daisychained together via SLIP thus the default route for the Ethernet Port of each SNMP can be set to be
the Network Address of its XP4 Port, allowing management of daisychained radio links from the SNMP
Manager as is described in the following section and shown in Figure 4-12.

SNMP 1
SNMP 1
SNMP 1 SNMP 1
SNMP 1
SNMP 2
SNMP 2
Figure 4-11: SNMP IP Ports Figure Routing via SLIP

4.4.3. Management of Daisychained Radio Links

The scenario shown in Figure 4-12 shows how a number of daisychained radio links can be managed
using SNMPs.
SNMP 1 SNMP 2 SNMP 3 SNMP 4 SNMP 5
Figure 4-12 : Management of non co-located SNMPs via daisychained SLIP connections
In the context of the above scenario the SNMP Manager can be connected to SNMP1 via SLIP, PPP or
Ethernet. By daisychaining SNMP2 and SNMP3 together, SNMP4 and SNMP5 together via SLIP
connections the SNMP Manager can manage the daisychained radio pairs IDU1\IDU2, IDU3\IDU4,
IDU5\IDU6.
If the SNMP Manager sends a message to SNMP5 then this will first be sent to SNMP1. SNMP1 will route
the message across the radio link to SNMP2 which will then route the message via a SLIP connection to
SNMP3. SNMP3 will route the message to SNMP4 across the radio link which will then route the message
via a SLIP connection to SNMP5.
Similarly if SNMP5 is responding to a message sent from the SNMP Manager it will forward the response
to SNMP4 via the SLIP connection which will forward the response to SNMP3 across the radio link and so
on all the way back to the SNMP Manager.
Note: An Ethernet connection achieves a faster response from the SNMP than can be achieved by a
SLIP/PPP connection.
The Default Routing functionality associated with routing IP messages between two SNMPs across a radio
link can be briefly described as follows (see Figure 4-13).

SNMP 1
SNMP 1
SNMP 1
SNMP 2
SNMP 2
Figure 4-13 : SNMP IP Ports Routing over XP4

I. On SNMP2 only the IP address of Serial Management Port 2 is shown. It can be seen that the
Network Address of the XP4 Port of SNMP2 is the same as the Network Address of the XP4 Port
of SNMP1. This is to be expected as both ports are connected to each other thus they must both
be on the same network. The IP node addresses are of course different with that of SNMP1 being
222.0.3.1 and that of SNMP2 being 222.0.3.2.
II. The Network Address of the Default Route IP Address of SNMP1 Serial Management Port 1 is
222.0.3.0 which matches the Network Address of SNMP1 XP4 Port thus it is a legal route. The
Default Route IP Address of SNMP1 Serial Management Port 1 is 222.0.3.2 which is the IP
Address of SNMP2 XP4 Port.
III. If an IP message arrives on SNMP1 Serial Management Port 1 and the Destination Network
Address of the message does not match the Network Address of SNMP1 Serial Management Port
1 then the message will be forwarded out on the SNMP1 Port whose Network Address matches
that of the Default Route Network Address of SNMP1 Serial Management Port 1 which in this
case is SNMP1 XP4 Port.

IV. Similarly if an IP message arrives on SNMP1 XP4 Port and the Destination Network Address of
the message does not match the Network Address of SNMP1 XP4 Port then the message will be
forwarded out on the SNMP1 Port whose Network Address matches that of the Default Route
Network Address of SNMP1 XP4 Port which in this case is SNMP1 Serial Management Port 1.
As an example assume the SNMP Manager sends an IP message to the XP4 Port of SNMP2. The
Destination IP address in the message will be 222.0.3.2 and the Source IP address will be 222.0.2.128.
Firstly a route needs to be added to the SNMP Managers routing table such that any messages destined
for the network 222.0.3.0 are sent out on the SNMP Managers port which has the Network Address
222.0.2.0.
The SNMP Manager will route the IP message destined for 222.0.3.2 to Serial Management Port 1 of
SNMP1. SNMP1 Serial Management Port1 will then compare the destination Network Address of
222.0.3.0 to its own network address of 222.0.2.0 and route the message out its default route which is
222.0.3.0 the Network address of SNMP1 XP4 Port.
The IP message will arrive at SNMP2 XP4 Port whereupon the destination Network Address of 222.0.3.0
will be compared to its own and a match will be found thus no attempt will be made to route the message.
Now that a Network match has been made the actual destination IP node address of the incoming IP
message (222.0.3.2) is compared to that of SNMP2 XP4 Port and again a match is found. SNMP2 will
then process this message and create a response message whose Destination IP address will be
222.0.2.128 and the Source IP address will be 222.0.3.2. This response will be forwarded out on the port
on which the original request came in on thus the response will arrive at SNMP1 XP4 Port.
SNMP1 XP4 Port will then compare the destination Network Address of 222.0.2.0 to its own network
address of 222.0.3.0 and route the message out its default route which is 222.0.2.0 the Network address
of the SNMP Managers port.
The same principles can be applied to the case where the SNMP Manager shown in Figure 4-12 wants to
send IP messages to SNMP5.

4.4.4. Management of Radios using Modem Dial Up

The scenario represented in Figure 4-14 illustrates how a number of non co-located radios can be
managed from a centrally based SNMP Manager by using SNMPs with dial up modems attached.
SNMP 1 SNMP 2 SNMP 3 SNMP 5
XPSurf
or
XPVision
Figure 4-14 : Management of non co-located SNMPs via a dial up modem
In the context of the above scenario the SNMP Manager can be connected to SNMP1 via SLIP or PPP
via a dial up modem and can thus manage the radio pairs IDU1\IDU2 and IDU3\IDU4 or connect to
SNMP5 via SLIP/PPP via a dial-up modem and can thus manage the radio pair IDU5/IDU6.

4.4.5. Management of Co-located and Non Co-located Radios

The scenario shown in Figure 4-15 represents a slightly more complex network of radios and SNMPs and
represents a combination of the configurations discussed in the previous sections.
SNMP 1 SNMP 2 SNMP 3 SNMP 4 SNMP 5 SNMP 6
XPSurf
or
XPVision
SNMP 7 SNMP 8 SNMP 9 SNMP 10 SNMP 11 SNMP 12
Figure 4-15 : Management of co-located and non co-located SNMPs

It should be noted that using combinations of custom IP Routers and Gateways there is no real limit to the
complexity of IP network topologies that can be constructed.

4.4.6. Management of Co-located and Non Co-Located Radios Via Ethernet
The scenario shown in Figure 4-16 represents the most complex network topology that can be managed
by SNMPs without the use of custom IP Routers. This topology can be achieved by interconnecting
SNMPs via Ethernet.
The scenario in the diagram illustrates how radio units connected to SNMPs 1 through to 11 can be
managed from SNMP Manager 1. Equally the radio units connected to SNMPs 1 through to 11 can also
be managed from SNMP Manager 2.
10Base-T or 10Base-2 Ethernet
IDU 1 IDU 2 IDU 3
IDU 4 IDU 5 IDU 6
SNMP 4
10Base-T or 10Base-2 Ethernet
NMI 5 NMI 6 SNMP 7
IDU 7 IDU 8 IDU 9
IDU 10 IDU 11 IDU 12
NMI 8
NMI 9 NMI 10 NMI 11
Figure 4-16 : Management of Co-located and located SNMPs via Ethernet

However when SNMPs are connected together via Ethernet and are configured in such a way as to
require messages to be routed through one SNMP to another then further configuration parameters

require to be set. These parameters are the Gateway IP Address and Broadcast Enable/Disable flag. The
rationale behind the requirement for these parameters can be explained as follows by referring to
4-16.
communicate with. Therefore if SNMP Manager 1 wishes to send an IP message to SNMP8 the route
will be via SNMP2. Similarly if the SNMP Manager 1 wishes to send an IP message to an SNMP
2) The SNMP does not have a complex routing table. This means the SNMP cannot match a foreign
network addresses (i.e. A network address which does not match that of the SNMPs Ethernet Port)
the SNMP has a default route out to which ALL
3) The lack of a routing table causes a problem in the case where SNMP Manager 1 wishes to send a
message to SNMP8. The message will be received on SNMP4’s XP4 port and will be routed via its
SNMP7). However the Ethernet protocol requires that the IP packet be placed in an Ethernet frame and
sent to a particular Ethernet address. As there is no routing table and simply one default route, means
intended. The choice is one between SNMP5, SNMP6 or SNMP7 or broadcast the IP message to all
nodes on the Ethernet network, by setting the Broadcast flag to enable.
user to specify whether Ethernet packets (containing IP messages) should be routed via one gateway
address or broadcast to all nodes on the Ethernet network.
NO requirement to set the Gateway IP Address and Broadcast
Management System i.e. An SNMP will not be routing an IP message to another SNMP.
SNMP 4 XP4
Port
SNMP 4 Ethernet Port

IP Address - 222.0.2.1
SNMP 4 Subnet Mask - 255.255.255.0
Ethernet Address- 0:9:4:6:7:1
Broadcast on
SNMP 5 Ethernet Port SNMP 6 Ethernet Port

IP Address - 222.0.2.1 IP Address - 222.0.2.3
SNMP 5 Subnet Mask - 255.255.255.0 SNMP 6 Subnet Mask - 255.255.255.0
Ethernet Address- 0:9:4:6:7:2 Ethernet Address- 0:9:4:6:7:3
Gateway IP Address 222.0.2.1 Gateway IP Address 222.0.2.1
SNMP 5 XP4 Port SNMP 6 XP4 Port
Figure 4-17 : Setting of Gateway IP Address

A more detailed example of how the Gateway IP address should be set up can be explained by referring
to Error! Reference source not found.. In Error! Reference source not found. SNMP4, SNMP5 and
SNMP6 are the same as those portrayed in Figure 4-16 This scenario represents the most common set-up
that will be encountered.
Page 28
1) If SNMP Manager1 sends an IP message to SNMP8 then the message will be routed to SNMP4. The
Broadcast flag of SNMP4 is set to enabled This means that the IP message will be broadcast to SNMP5,
SNMP6, SNMP7 and SNMP Manager 2.
2) The message will arrive at SNMP8 which will send a reply. This reply will be routed back to SNMP6.
The Gateway IP Address of SNMP6 is that of SNMP4 (222.0.2.1) thus the message will be sent to
SNMP4 and hence routed back to SNMP Manager1.
3) The advantages of the above scenario is that it is possible from the SNMP Manager to reach SNMPs
beyond SNMP5, SNMP6 and SNMP7 via SNMP4.
An alternative set-up would be to change the Gateway IP Address of SNMP4 to be that of SNMP6
(222.0.2.3) with Broadcast set to disabled.
1) If SNMP Manager1 sends an IP message to SNMP8 then the message will be routed to SNMP4. The
Gateway IP Address of SNMP4 is the IP Address of SNMP 6 (222.0.2.3). This means that the IP message
will be sent directly to SNMP6.
2) The message will be routed by SNMP6 and arrive at SNMP8 which will send a reply. This reply will be
routed back to SNMP6. The Gateway IP Address of SNMP6 is that of SNMP4 (222.0.2.1) thus the
message will be sent to SNMP4 and hence routed back to SNMP Manager1.
3) Using this configuration SNMP Manager1 can reach SNMP5, SNMP6 and SNMP7 but can only reach
SNMPs beyond SNMP6. This in some cases may be desirable.
It should be noted that if the scenario shown in Figure 4-13 is configured as shown in Figure 4-14 then the
following restrictions apply with reference to the management access which SNMP Manager 3 has to
SNMPs 1 to 11.
1) SNMP8, SNMP9, SNMP10 and SNMP11 can be reached due to the fact they live on the same Subnet
as SNMP Manager3.
2) SNMP4, SNMP5, SNMP6 and SNMP7 can be reached because the routing tables on SNMP Manager 3
would be set up such that any messages destined for the Subnet which these SNMPs live on would be
routed via SNMP8.
3) SNMPs beyond SNMP4 only could be reached. This is because the Gateway IP Address of SNMP6 is
set to be that of SNMP4.
4) If the Broadcast Flag of SNMP 6 is set to enabled then SNMPs beyond SNMP4, SNMP5 and SNMP7
can be reached.
The above consideration should be taken into account if a radio network using Ethernet based
management is being deployed and there is a requirement to be able to plug an SNMP Management
Station into the network at any point and to be able to see the whole network from that point.
4.4.7. Some Network Management Topology Design Considerations

It should be remembered that managing radios from an SNMP Manager in a daisychained configuration
as shown in Figure 4-10 and in Figure 4-12 will have an overhead in terms of message transit times i.e.
The time it takes for a message to go from the SNMP Manager to SNMP5 and back again. Also if a radio
link goes down e.g. The IDU1 to IDU2 link then SNMPs 2, 3, 4 and 5 will not be able to be accessed from
the SNMP Manager. Careful consideration should be given to these two points when designing the SNMP
network topology. Ideally the Ethernet configuration shown in Figure 4-9 should be used wherever
possible and the number of daisychained connections kept to a minimum if reliable and preferment
SNMP based network management is to be achieved.

4.4.8. IP Routing in a 1+1 Protected Link
Key
IP - IP Address of Port
DR - Default Route IP Address of Port
GI - Gateway IP Address of Port
Co-located Interconnected
Co-located Interconnected IP Address = 222.0.2.1
IP Address = 222.0.1.2
Co-located Radio Port
Co-located Radio Port IP Address = 222.0.4.2
IP - 222.0.2.2
IP - 222.0.1.3
IP-222.0.3.1 DR - 222.0.3.1
DR -222.0.3.2
DR-222.0.1.1 GI - 222.0.2.3
SNMP SNMP
A C
IP-222.0.3.2
DR-222.0.2.3 IP -222.0.2.3
A
A GI - 222.0.2.2
Ethernet Local Remote
Protection Protection SNMP
Switch Switch E
B B
IP-222.0.4.1
DR-222.0.1.1 Ethernet
SNMP SNMP
B D
IP - 222.0.1.2 IP222.0.4.2
- 222.0.4.2 IP - 222.0.2.1
DR-222.0.4.2 DR- 222.0.2.3 DR - 222.0.4.1
GI - 222.0.2.3
IP - 222.0.1.1
GI -222.0.1.3 Co-located Interconnected Co-located Interconnected
IP Address = 222.0.1.3 IP Address = 222.0.2.2
SNMP
Network
Co-located Radio Port Co-located Radio Port
Management IP Address = 222.0.3.1 IP Address = 222.0.3.2
System
Figure 4-18 : Co-located SNMPs inter connected via Ethernet in a 1+1 Protected Link
The diagram shown in Figure 4-18 above illustrates the use of the Co-located Interconnected IP Address
and Co-located Radio Port IP Address parameters in a 1+1 Protected System.
The purpose of the Co-located Interconnected IP Address and Co-located Radio Port IP Address
parameters are to facilitate IP Routing in a 1+1 Protection switched system, prevent message duplication
across the protected link, prevent inappropriate message generation to adjacent networks and messages
getting looped round the link continuously.
As shown in Figure 4-18 each SNMP will have a Co-located Interconnected Port IP Address and a Co-
located Radio Port IP Address parameter.
In terms of defining what co-located means, the Co-located SNMP of SNMP A is SNMP B, the Co-located
SNMP of SNMP C is SNMP D etc.
The Co-located Interconnected Port IP Address parameter is the IP Address of the port of the Co-located
SNMP (Ethernet port or serial port) by which the two SNMPs are connected.
The Co-located Radio Port IP Address parameter is the IP Address of the Radio Port of the Co-located
SNMP.

4.4.8.1.Interconnecting Co-located SNMPs via Ethernet
There are two basic requirements of IP Routing in a 1+1 Protected Link in the case where the Co-located
SNMPs in a 1+1 Protected Link live on the same Ethernet LAN as shown in Figure 4-18. These
requirements are :
1) IP traffic will only be routed across the Online Link.
2) The SNMP Network Management System (NMS) should not have to dynamically change the entries
in its routing tables representing the IP Gateway to be used to reach SNMP E (or any other SNMP or
IP addressable device on or beyond the 222.0.2 Subnet) based on whether SNMP A (222.0.1.3) or
SNMP B (222.0.1.2) is Online. i.e. the SNMP NMS should not have to dynamically change its IP
Gateway to SNMP E between 222.0.1.3 and 222.0.1.2.
In order to satisfy the above requirements, using the scenario as shown in Figure 4-18 as an example,
the following mechanism has been put in place :
1) SNMP NMS Routing Table - When populating the routing table of the SNMP NMS to reach the
222.0.3, 222.0.4, 222.0.2 networks and beyond a Gateway of either 222.0.1.2 or 222.0.1.3 can be
used. It does not matter which is chosen i.e. it does not matter whether the online or offline SNMP is
chosen.
It should be noted that the SNMP NMS could simply be another SNMP which is routing traffic
received over the air link on its Radio Port out onto the 222.0.1 Ethernet LAN. In this case the
Gateway IP Address of the SNMP could be set to that of SNMP A or SNMP B or IP Broadcast could
be enabled.
2) Co-located ARP - All IP Routing will be disabled until the SNMP has detected the presence of the
both the Local\Remote IDUs\ODUs and determined whether or not it is in a 1+1 Protected Link
(except for Hot Standby in which case the Offline SNMP will only be able to detect the Local
IDU\ODU). If the SNMP is in a Protected Link then the SNMP will send an ARP message to the
SNMP whose IP Address is the Co-located Interconnected IP Address.
Using this ARP mechanism SNMP A will discover the Ethernet address of SNMP B and SNMP B will
discover the Ethernet address of SNMP A. SNMP A will then accept Ethernet packets for itself and
SNMP B. SNMP B will then accept Ethernet packets for itself and SNMP A.
The same mechanism takes place between SNMP C and SNMP D.
4.4.8.2.Frequency Diversity Mode and Dual Link Mode
In order to give a high level view of how IP Routing is achieved in Frequency Diversity Mode and Dual
Link Mode if we for the sake of example assume the following :
1) SNMP NMS has a Default Gateway of SNMP A i.e. all IP Messages for Networks other than the
222.0.1 network will be sent to the Ethernet address of SNMP A.
2) The Protected Link is in Dual Link or Frequency Diversity Mode.
3) SNMP A is Online, SNMP B is Offline. SNMP C is Online, SNMP D is Offline.
The IP Routing will be achieved as follows :

I. SNMP A is Online thus will route all IP traffic and hence will perform the following processing on
messages received on its Ethernet Port :
A. Messages whose destination is SNMP A’s IP Address will be processed.
A. Messages whose destination Network address matches that of its Radio port i.e.
messages to 222.0.3.2 will be routed out of the Radio Port to SNMP C.
A. Messages whose destination Network address is not 222.0.1 or 222.0.3 will be routed out
of the Radio Port to SNMP C.
A. Messages whose destination Network address match that of the Co-located Radio Port
i.e. 222.0.4 will be discarded.
I. SNMP B is Offline thus will NOT route all IP traffic and hence will perform the following
processing on messages received on its Ethernet Port :
A. Messages whose destination is SNMP B’s IP Address will be processed.
messages to 222.0.4.2 will be routed out of the Radio Port.
B. Messages whose destination Network address is not 222.0.1 or 222.0.4 will be discarded.
If SNMP A switched to Offline and SNMP B is switched to be Online then the IP Routing will be achieved
as follows :
I. SNMP B is Online thus will route all IP traffic and hence will perform the following processing on
messages to 222.0.4.2 will be routed out of the Radio Port to SNMP D.
of the Radio Port to SNMP D.
i.e. 222.0.3 will be discarded.
I. SNMP A is Offline thus will NOT route all IP traffic and hence will perform the following
processing on messages received on its Ethernet Port :
messages to 222.0.3.2 will be routed out of the Radio Port.
B. Messages whose destination Network address is not 222.0.1 or 222.0.3 will be discarded.
4.4.8.3.General Rules
The IP Routing described in section 0 above can be generalised by the following rules :

1) The Local Online SNMP will route any message it receives on its Ethernet Port out over its Radio
Port.
The Local Offline SNMP will discard any messages it receives on its Ethernet Port which do not have a
destination IP address matching that of its Ethernet Port or an IP Network Address matching that of its
Radio Port.
4.4.9. Hot Standby Mode
In order to give a high level view of how IP Routing is achieved in Hot Standby Mode if we for the sake of
example assume the following :
1) SNMP NMS has a Default Gateway of SNMP A i.e. all IP Messages for Networks other than the
222.0.1 network will be sent to the Ethernet address of SNMP A.
2) The Protected Link is in Hot Standby Mode.
3) SNMP A is Online, SNMP B is Offline. SNMP C is Online, SNMP D is Offline.
The IP Routing will be achieved as follows :
I. SNMP A is Online thus will route all IP traffic and hence will perform the following processing on
messages to 222.0.3.2 will be routed out of the Radio Port to SNMP C.
However because the switch is in Hot Standby Mode then SNMP D will also receive the
message. SNMP D will thus discard all messages received on its Radio Port which are
not specifically addressed to it i.e. any message not destined for 222.0.4.2 will be
discarded.
of the Radio Port to SNMP C.
As described above SNMP D will thus discard all messages received on its Radio Port
which are not specifically addressed to it.
i.e. 222.0.4 will be routed out of the Radio Port. This is because SNMP B is offline and as
such
the Radio Port of SNMP D can’t be reached via SNMP B.
When SNMP D receives a message addressed to its Radio Port it will process the
message but because it is offline its transmitter will be muted and as such will be unable
to send the response back out of its Radio Port. In order to get round this SNMP D will
route the response via its Co-located Interconnected SNMP i.e. it will send the message
to the Ethernet address of SNMP C. SNMP C will route the message across the Radio
link back to SNMP A which will then route the message out its Ethernet Port.
II. When SNMP C receives a message addressed to the Radio Port of SNMP B is Offline thus will
NOT route all IP traffic and hence will perform the following processing on messages received on
its Ethernet Port :

A. Messages whose destination is SNMP B’s IP Address will be processed.
messages to 222.0.4.2 will NOT be routed out of the Radio Port because the unit is offline
and hence the transmitter will be muted.
A. Messages whose destination network address is not 222.0.1 will be discarded.
4.4.9.1.General Rules
The IP Routing described in section 4.4.9 above can be generalised by the following rules :
1) The Local Online SNMP will route any message it receives on its Ethernet Port out over its Radio
Port. These messages will be received by both the Remote Online and Offline SNMPs.
2) The Local Offline SNMP will discard any messages it receives on its Ethernet Port which do not have
a destination IP address matching that of its Ethernet Port.
3) The Remote Online SNMP will discard any messages it receives on its Radio Port which have a
destination IP Network address which matches that of its Co-located Radio Port address i.e. the Radio
Port of the Offline Remote SNMP. The Remote Online SNMP will route all other messages it receives
on its Radio Port which are not destined for its Radio Port IP Address out its Ethernet Port.
The Remote Offline SNMP will discard any IP messages which it receives on its Radio Port which do
not have a destination IP address matching that of its Radio Port.
4) When the Remote Offline SNMP receives a message on its Radio Port which has a destination IP
address matching that of its Radio Port then it will process the message. However because the SNMP
is offline the response will routed to the Co-located Interconnected SNMP i.e. the Remote On-line
SNMP which will in turn route the message across the Radio Link to the Local On-line SNMP.

4.5. Managing via Serial Port

Key
IP - IP Address of Port
DR - Default Route IP Address of Port
GI - Gateway IP Address of Port
Co-located Interconnected
Co-located Interconnected IP Address = 222.0.2.1
Co-located Radio Port
Co-located Radio Port IP Address = 222.0.4.2
IP - 222.0.2.2
IP - 222.0.3.1 DR-222.0.3.1
DR-222.0.5.1 222.0.2.2
GI -222.0.2.3
IP - 222.0.5.2 SNMP SNMP
DR - 222.0.3.2 A C Ethernet
IP - 222.0.3.2
DR-222.0.2.3 IP - 222.0.2.3
SLIP/PPP A
GI- 222.0.2.2
/Ethernet A Local Remote
Protection Protection SNMP
B Switch Switch E
IP - 222.0.5.1 B
IP - 222.0.4.1
DR- 222.0.4.2
DR- 222.0.1.1
SNMP SNMP
B D
SLIP/PPP IP -222.0.4.2
222.0.4.2 IP - 222.0.2.1
IP - 222.0.1.2 DR- 222.0.2.3 DR-222.0.4.1
DR-222.0.4.2 GI-222.0.2.3
IP - 222.0.1.1 Co-located Interconnected
GI- 222.0.1.2 IP Address = 222.0.5.2 Co-located Interconnected
SNMP Co-located Radio Port
Network IP Address = 222.0.3.1 Co-located Radio Port
Management IP Address = 222.0.3.2
System
Figure 4-19 : Co-located SNMPs inter connected via Serial Ports in a 1+1 Protected Link
The only one requirement of IP Routing in a 1+1 Protected Link in the case where the Co-located SNMPs
in a 1+1 Protected Link live on the same Ethernet LAN but the SNMP NMS is connected via a Serial Port
as shown in Figure 4-19 is that IP traffic will only be routed across the Online Link.
In order to satisfy the above requirement, using the scenario as shown in Figure 4-19 as an example, the
following mechanism has been put in place :
1) If SNMP B is Online then IP messages sent from the SNMP NMS to the Serial Port of SNMP B
(222.0.1.2) which are destined for the 222.0.4 network, the 222.0.2 network and beyond will be routed
out of SNMP B’s Radio Port.
Messages sent from the SNMP NMS to the Serial Port of SNMP B (222.0.1.2) which are destined for
SNMP A (222.0.5.2) or SNMP C (222.0.3.2) will be routed out of the Serial Port (222.0.5.1) of SNMP
B to SNMP A.
2) If SNMP A is Online then IP messages sent from the SNMP NMS to the Serial Port of SNMP B
(222.0.1.2) which are destined for the 222.0.4 network, the 222.0.2 network and beyond will be routed
out of SNMP B’s Serial Port (222.0.5.1) to SNMP A.
Messages sent from the SNMP NMS to the Serial Port of SNMP B (222.0.1.2) which are destined for
SNMP A (222.0.5.2) or SNMP C (222.0.3.2) will also be routed out of the Serial Port (222.0.5.1) of
SNMP B to SNMP A.
Apart from the above described difference the rest of the IP Routing functions as was described in
Section 4.4.8.1.

It should be noted that in the configuration shown in Figure 4-19 SNMP B is a single point of failure i.e. if
SNMP B fails then neither SNMP A, C, D, E or any IP Addressable devices beyond SNMP E will be
reachable.
5. SNMP Overview
5.1. Network Management Basics

Why has network management become the current “hot button”?
Historical Background
Historically, computers have been dedicated, homogeneous, stand-alone systems used for solving
specific needs, such as:
• Detailed engineering problems(numerical analysis, for example).

• Specific business needs (printing invoices, for example).
• Manufacturing requirements (operating a controller, for example).
Recent Developments
Currently, computers have become general purpose, heterogeneous, networked systems with different
overlapping administrative responsibilities. Computers address complex system needs, such as integrated
engineering, production, and business requirements.
Basic connectivity is now a foregone conclusion. “Network is the computer” - meaning, if part of the
network is down, a whole company’s business is affected. Network availability has become very important
to end-users.
Terminology
Network Operation Centre (NOC) - A centralised station from which an operator monitors and controls
the network.
Management Station - Equipment used to monitor a network.
Agents - Modules logically within network elements that interact with management stations.
Products - Method by which management information is sent between management stations and agents.
Instrumentation - Modules within agents that actually count events of interest, or generate events.
Management information Base (MIB) - A distributed “pseudo database”. The collection of all agents and
their associated data as seen by a management station.
End-User Model
As seen by an NOC, the network can be loosely modelled as a widely distributed database, which consists
of each agent’s local data, and the events associated with the agent’s system.
The NOC is the user’s interface to this database, providing a user-friendly mechanism for monitoring and
modifying the database (and thus the state of the network).
The user tells the NOC what he wants to monitor and modify. The management station in the NOC handle
the technical details of carrying out the actions.

SNMP Components
The Simple Network Management Protocol (SNMP) architecture model has three components:
1. Managed Nodes - Hosts, gateways, or media devices.

2. Network Management Stations (NMS) - Host systems running software to access managed nodes.
These systems display and/or modify the “distributed database” found in the managed nodes.
3. Protocol - Mechanism used by an NMS to access a managed node.
5.1.1. History of SNMP

Here’s a brief description of all systems that preceded SNMP:
NETMON - Network Monitoring, an enhancement to RIP routing Protocol, is used only for control and
monitoring of gateways to avoid very coarse problems.
SGMP - The simple Gateway Monitoring Protocol is a direct antecedent to SNMP. SGMP provides a
slightly finer control of gateways than NETMON. SNMP utilises most of the underlying SGMP primitives,
but has added ASN1 encoding for CMIP/CMOT compatibility.
CMIP/CMOT - the Common Management Information Protocol (over TCP) competed with SNMP to
become the standard protocol for the management of IP-based networks. CMOT implementations,
however proved to be less functional than SNMP implementations; therefore, SNMP was chosen for the
near term network management solution.
HEMS - The High Level Entity Management System, a sophisticated management infrastructure, was an
early technical alternative to SNMP. HEMS also provided structure to the Management Information Base
(the virtual database).
SNMP - The following events led to the establishment of SNMP as the current network management
standard, and SNMPv2 as the emerging standard:
February ‘88 The Internet Advisory Board advise SNMP as the

current network management standard, and CMIP for
long term network management. This action forced
SNMP to consider an “OSI-like” approach to ease
eventual transition to CMIP. The Management
Information Base definition of distributed
database)was influenced by CMIP
April ‘89 SNMP becomes the recommended TCP/IP standard.
October ‘89 Over 30 vendors show SNMP products at Interop
trade show.
October ‘90 Over 100 vendors show SNMP products at Interop
trade show.
October ‘91 SNMP is “a must” in networked systems.
February ‘92 SNMP security proposal completed.
October ‘92 SNMP has spread into non-networked devices, and
vendors are adding SNMP stacks for the sole purpose
of managing those devices. Networked devices must
have SNMP.
April ‘93 SNMPv2 proposal made and entered on the IETF
standards track.
August ‘93 First SNMPv2 implementations seen at Interop trade
show.

5.1.2. SNMP Design Constraints

SIMPLE Network Management Protocol
SNMP is intended for use in existing TCP/IP products. Agents must fit into small, resource-poor
embedded systems and must be easy to retrofit into diverse fielded architectures. Network elements
should do networking and should not be heavily impacted by instrumentation.
NOCs have responsibility for sophisticated procedures. Database is easily extensible to cover unexpected
requirements.
OSI Network Management
OSI network management includes:
• Configuration Management
• Performance Management
• Fault Management
• Accounting Management
• Security Management
SNMP Network Management
SNMP is not a rigid OSI. Pragmatic requirements drove a looser construction, with the following
characteristics:
• No explicit commands.
• Only examining and changing variables.
• Emphasis on Configuration, Performance and Fault management. In order to cause an action, a
variable that corresponds to a state must be changed. For example, changing the state of a board to
“down” will cause the board to go off-line.
Lightweight Transport Protocol (UDP)
Network management is used heavily in times of unpredictable and unstable network behaviour to
diagnose and fix the problem. Because the network may be unstable when SNMP is needed, SNMP must
have control of its re-transmission strategies. Furthermore, SNMP should not use a connection orientated
protocol, such as TCP, because connections typically shut down when the network is in trouble. If SNMP
relied on TCP sessions staying open in order to work, it would fail when the network was in trouble -
exactly when it is vital that SNMP work. Therefore, SNMP uses UDP for its transport layer.
Limited Use of Traps
Typically, traps are sent from agent to manager to signify a state change.
Traps are designed to inform an NOC that an event has occurred. It is then the responsibility of the NOC
to determine exactly what happened.
Because traps are not acknowledged, they cannot be used to convey critical information. A NOC cannot
depend on receiving a trap from an agent. Instead, it should use a trap only as a mechanism for triggering
increased querying.

5.1.3. SNMPV1 Reference Documents

Structure of Management Information RFC 1155
• Describes the structure used to elaborate managed objects and the methods by which they are
managed.
• Describes an object identification model.
• Describes allowable ASN1 types for management information.
• Introduces concept of virtual database.
• Defines rules by MIB (both Internet standard enterprise specific MIBs).
Management Information Base- RFC1213
Describes the minimum set of objects that make up the virtual database. The standard MIB is a building
block upon which additional MIBs may be attached.
Known as MIB-II, this is the latest Internet standard MIB. It is a superset of RFC1066 (MIB1). RFC1213
recently advanced to an Internet standard. Most devices support MIB1, but are migrating to MIB-II.
Descriptions of each element Includes :
• Naming - Both human readable and dotted ISO notation.

• Definitions - The technical specification of exactly what this element represents in an agent’s
instrumentation.
• Access - Whether this element is read, write or read/write.
• Status - Whether this element is required or optional.
Database elements are identified by:
• Object Identification - Dotted text strings, composed of object type concatenated with object instance.
• Object Description - Textual representations of Object Identifiers.
MIB is a rooted tree structure with globally unique object identifiers. To describe an object, walk from the
root of the tree through the branches to the object. Concatenate ISO numbers for Object Identifiers or text
strings for object descriptions.
While working through the tree, subordinate limbs may be sparse. This allows for private MIBs to be
attached to the standard MIB in any fashion.

MIB Structure
From unlabeled root, the limbs in the Internet tree we are interested in are shown below:
iso(1) org(3)
dod (6)
internet (1)
mgmt (2)
experimental (3)
private (4)
enterprises (1)
ccitt (2)
joint-iso-ccitt(3)
Any specific instance of a MIB element is defined by its position on the rooted tree, followed by a string
specifying its instance.
Example 1
Part of the MIB is a count of how long a device has been up. The object ID for this element is:
iso.org.dod.internet.mgmt.mib.system.sysUpTime
1.3.6.1.2.1.1.3
In addition to knowing its Object ID, the instance must be specified. There is only on system group per
“mib view”, so a 0 is appended to the Object ID to specify this instance of sysUpTime.
iso.org.dod.internet.mgmt.mib.system.sysUpTime.0
1.3.6.1.2.1.1.3.0
Example 2
Part of the MIB is a count of how many octets a device has received. The Object ID for this element is:
iso.org.dod.internet.mgmt.mib.interfaces.iftable.ifentry.ifInOctets
1.3.6.1.2.1.2.2.1.10
In addition to knowing its Object ID, the instance must be specified. Since devices may have more than
one interface, the interface number is appended to the Object ID.
iso.org.dod.internet.mgmt.mib.interfaces.iftable.ifentry.ifInOctets.interface1
1.3.6.1.2.1.2.2.1.10.1
Simple Network Management Protocol-RFC 1157
Describes the protocol used by systems to exchange network management information.

Basic Operations
Systems exchange information using four basic operations:
GET - Access and reads a specific variable, such as “Give me your ARP entry for this host”.
GETNEXT - Searches the MIB for the “next” variable, such as “Give me the next entry in your ARP table”.
The GETNEXT operator is customarily called the “powerful” GETNEXT operator due to a long-standing
debate over the risk-like approach to management endorsed by SNMP.
SET - Changes a specific variable, such as “Set your IP time-to-live to 55”.
TRAP - Used for event notification. Polling is the primary means for gathering SNMP information. Traps
are designed to stimulate additional polling, not to replace polling, such as “something just happened”.
Use traps sparingly because they are unacknowledged, and thus could add to the problem that you are
trapping about.
How SNMP V1 Works
SNMP sends datagrams from one entity to another. The datagrams are classified as requests, responses
and traps.
Requests
A request contains the following:
• Community String - Defines the MIB view to be accessed. Currently overloaded as a pseudo
password. The password/MIB view overloading is being addressed by an IETF committee.
• Requested Operation - Either GET, GETNEXT, SET or TRAP.
• Requested Number - Identifies the request, so that a response may be correlated to it.
• Error Status - If there is an error in processing a request, this field is set in the response.
• Error Index - If the error status is set, this field references the Object ID that was in error.
• Object ID, value pairs - A list of object Ids and their associated values.
Responses
A response is identical in format to a request. If an error occurs in either parsing a SNMP packet or
carrying out a specified action, an error status is set in the response packet. An error index is also set to
indicate value was in error. Errors include:
• tooBig - The agent’s response to this request does not fit into a response packet. This can happen
when doing a GETNEXT on a collection of short Object Ids when the next element is a long Object ID.
The short “dotted strings” fit in a message, the long ones do not.
• noSuchName - The Object ID is unknown.
• badValue - The value associated with an object is invalid. This can happen when setting a state (up,
down) to an undefined state (47, for example).
• readOnly - Attempt to write a read-only variable. (This is a historical error message).
• genErr - Miscellaneous error occurred.

5.1.4. ASN1 - Abstract Syntax Notation One

ASN1 allows machine-independent representation of data. This means, one machine can unambiguously
convey information to another without regard for bit/byte ordering.
SMI/SNMP/MIB use only a subset of ASN1. ASN1 has a very rich vocabulary, only some of which is
required for SNMP. The full vocabulary would be difficult to fit into modest agents.
ASN1 is used both to describe the data elements in the MIBs and the SNMP datagrams that convey
protocol information.
TYPE defines the data elements:
• INTEGER - Whole valued number.

• OCTET STRING - 0 or more 8 bit bytes.
• OBJECT IDENTIFIER - “OSI-style” named object. String of integers specifying an object’s place in the
tree. Each dot-separated number represents which tree branch to take from the root, For example:
1.3.6.1.2.1.1.1
is
iso.org.dod.internet.mgmt.mib.system.sysDescr
• SEQUENCE - Concatenation of other ASN1 types. Similar to a structure in “C”, ASN1 defines the rules
for padding such structures.
• SUBTYPE defines SNMP/SMI/MIB specific variations on types.
6. SNMP Interfaces
6.1. Interface Description

The SNMP presents the following external interfaces :
1) Name - Serial Management Port 1

Purpose - Management of Local and Remote IDU/ODU and SNMP via SNMP. Download of
Local and Remote IDU/ODU software and SNMP software via TFTP.
Protocol - SNMP and TFTP over UDP over IP over SLIP or PPP via fixed link or Dial Up
Modem.
Physical Layer - RS232 or RS422. 8 data bits, 1 start bit, 1 stop bit, no parity, no flow control.
Baud rates ranging from 9600 to 115200.
Connector Type - RJ45
2) Name - Serial Management Port 2

Protocol - SNMP and TFTP over UDP over IP over SLIP or PPP via fixed link or Dial Up
Modem.
Physical Layer - RS232 or RS422. 8 data bits, 1 start bit, 1 stop bit, no parity, no flow control.
Baud rates ranging from 9600 to 115200.
3) Name - Ethernet 10Base-T

Local and Remote IDU/ODU software and SNMP software via

TFTP.
Protocol - SNMP and TFTP over UDP over IP over Ethernet
Physical Layer - 10Base-T
4) Name - Ethernet 10Base-2

Protocol - SNMP and TFTP over UDP over IP over Ethernet
Physical Layer - 10Base-2
Connector Type - BNC
5) Name - VT100
Purpose - Presents a set of menus for configuration of SNMP specific parameters.
Protocol - Straight ASCII for normal operation.
Physical Layer - RS232. 8 data bits, 1 start bit, 1 stop bit, no parity, no flow control. Baud rate of
9600.
6.2. Connector Pinouts

Note :
1. The RS232 RJ45 pinout assignment was allocated as to the pinouts of a 9 way D-type connector.
2. See
Power 10Base-2/
VT100 Rese UTP Cheapernet
SLIP 2 LED
Interface
SLIP 1
BERG 5 BERG 1
shorting
connector
BERG 6
BERG 4
68360
SCC2 CPU
UTP
SCC3
VT100
RS232
Backplane
Connector

SRAM 1 SRAM 2
68160 Dual Port Flash 1

RAM Flash 2
Ethernet
Figure 4-6 for location and identification of connectors on the SNMP card.
3. The pins corresponding to the signals DCD, DTR, DSR, RTS and CTS are connected in
hardware but are not driven by the software.
6.2.1. VT100 8-WAY BERG Connector

The SNMP card provides the VT100 interface via a 8 way BERG connector. The pinout of the connector
is shown below:
BERG Pin Signal Name Signal Direction

Number
1 DCD OUTPUT
2 RXD OUTPUT
3 TXD INPUT
4 DTR INPUT
5 GND -
6 DSR OUTPUT
7 RTS INPUT
8 CTS OUTPUT

6.2.2. RS232 SLIP/PPP 8-WAY BERG Connector

The SNMP card provides the RS232 SLIP/PPP interface via a 8 way BERG connector. The pinout of the
connector is shown below:

Number
1 - -
2 RXD INPUT
3 TXD OUTPUT
4 DTR OUTPUT
5 GND -
6 DSR INPUT
7 RTS OUTPUT
8 CTS INPUT
6.2.3. RS422 SLIP/PPP 8-WAY BERG Connector

The SNMP card provides a RS422 SLIP/PPP interface via an 8 way BERG connector. The pinout of the

Number
1 TXB+ OUTPUT
2 TXA- OUTPUT
3 RXA- INPUT
4 RXB+ INPUT
5 GND -
6 - -
7 - -
8 - -
6.2.4. RS422 SLIP/PPP Connector

The SNMP card provides a SLIP/PPP interface via an 8 pin RJ45 connector. The pinout of the connector,
when set to RS422, is shown below:
RJ45 Pin Signal Name Signal Direction

Number
1 TXB (+) OUTPUT

2 TXA (-) OUTPUT
3 RXA (-) INPUT
4 RXB (+) INPUT
5 GND -
6 - -
7 - -
8 - -
6.2.5. VT100 Connector

The SNMP card provides the VT100 RS232 interface via a RJ45 connector. The pinout of the connector
is shown below:


Number
1 DCD OUTPUT
2 RXD OUTPUT
3 TXD INPUT
4 DTR INPUT
5 GND -
6 DSR OUTPUT
7 RTS INPUT
8 CTS OUTPUT
6.2.6. RS232 SLIP/PPP Connector

The SNMP card provides the RS232 SLIP/PPP interface via a RJ45 connector. The pinout of the

Number
1 - -
2 RXD INPUT
3 TXD OUTPUT
4 DTR OUTPUT
5 GND -
6 DSR INPUT
7 RTS OUTPUT
8 CTS INPUT
6.2.7. RJ45 Ethernet Unshielded Twisted Pair Connector

The SNMP card provides an Unshielded Twisted Pair interface via an 8 way RJ45 connector. The pinout
of the connector is shown below:

Number
1 TPTX+ OUTPUT
2 TPTX- OUTPUT
3 TPRX+ INPUT
4 - -
5 - -
6 TPRX- INPUT
7 - -
8 - -

6.3. Cables
6.3.1. RS422 SLIP/PPP Interface Cable

External Interface NMI Port
Pin 1
13
25
8
14
Pin 1
This type of cable can be used for connecting from the SNMP management system to the SNMP Serial
Management Port.
25 Way D- Pin Direction RJ45 Pin Direction

Type
RXB (+) 5 input TXB (+) 1 output
RXA (-) 3 input TXA (-) 2 output
TXA (-) 6 output RXA (-) 3 input
TXB (+) 22 output RXB (+) 4 input
GND 7 GND 5
6.3.2. VT100 Interface Cable
6.3.2.1. VT100 Interface Cable (Female 25 Way D Type)
Pin 1
Pin 1
1
14
8
25
13
This type of cable can be used for connecting from a VT100 Terminal or a PC serial port (25 Way D-Type
connector) to the SNMP Serial Management Port.

Type
RxD 3 input RxD 2 output
TxD 2 output TxD 3 input
RTS 4 output RTS 7 input
CTS 5 input CTS 8 output
DSR 6 input DSR 6 output
GND 7 - GND 5 -
DCD 8 input DCD 1 output
DTR 20 output DTR 4 input

6.3.2.2. VT100 Interface Cable (Female 9 Way D Type)

Pin 1
1
5
96
8
1
Pin 1
This type of cable can be used for connecting from a VT100 Terminal or a PC serial port (9 Way D-Type
connector) to the SNMP Serial Management Port.
9 Way D-Type Pin Direction RJ45 Pin Direction

RxD 2 input RxD 2 output
TxD 3 output TxD 3 input
RTS 7 output RTS 7 input
CTS 8 input CTS 8 output
DSR 6 input DSR 6 output
GND 5 - GND 5 -
DCD 1 input DCD 1 output
DTR 4 output DTR 4 input
6.3.3. RS232 SLIP/PPP Interface Cable
6.3.3.1.RS232 SLIP/PPP Interface Cable(Female 25 Way D Type)
Pin 1
Pin 1
1
14
8
25
13
This type of cable can be used for connecting from the SNMP management system or PC serial port (25
way D-Type connector)to the SNMP Serial Management Port.

Type
TXD 2 output RxD 2 input
RXD 3 input TxD 3 output
CTS 5 input RTS 7 output
RTS 4 output CTS 8 input
DTR 20 output DSR 6 input
GND 7 - GND 5 -
DCD 8 - DCD 1 -
DSR 6 input DTR 4 output

6.3.3.2.RS232 SLIP/PPP Interface Cable (Female 9 Way D Type)

Pin 1
1
5
96
8
1
Pin 1
This type of cable can be used for connecting from the SNMP management system or PC serial port (9
way D-Type connector)to the SNMP Serial Management Port.
9Way D-Type Pin Direction RJ45 Pin Direction

TXD 3 output RxD 2 input
RXD 2 input TxD 3 output
CTS 8 input RTS 7 output
RTS 7 output CTS 8 input
DTR 4 output DSR 6 input
GND 5 - GND 5 -
DCD 1 - DCD 1 -
DSR 6 input DTR 4 output
6.3.4. RJ45 Ethernet Unshielded Twisted Pair Interface Cable

Pin 1 Pin 1
1 1
8 8
This type of cable can be used for connecting from the SNMP Twisted Pair (UTP) Ethernet Port to an
Ethernet hub.
RJ45 Pin Direction RJ45 Pin Directio

n
TPTX+ 1 output TPTX+ 1 input
TPTX- 2 output TPTX- 2 input
TPRX+ 3 input TPRX+ 3 output
TPRX- 6 input TPRX- 6 output
6.3.5. Serial to serial

Pin 1 Pin 1
1 1
8 8
This type of cable can be used for connecting a SNMP serial port to another SNMP serial port.
RJ45 Pin Direction RJ45 Pin Direction

RXD 2 input TXD 3 output
TXD 3 output RXD 2 input
GND 5 GND 5

7. VT100 User Interface Operation
7.1. RS232 VT100 Interface Operation

The SNMP Card may be accessed by connecting the VT100 port on the card to any VT100 terminal. The
VT100 uses an RS232 Asynchronous interface running at 9600 baud, this can be connected directly to a
VT100 terminal or a PC running VT100 emulation software.
7.1.1. PC Terminal Link Installation.
7.1.2. To connect a PC to the SNMP card.
1. Connect an appropriate RS232 cable between the VT100 Port on the SNMP Card and a free COM
Port on the PC or VT100 terminal.
2. Install the generic modem software that supports VT100 emulation on the PC.
3. Configure the software to use the chosen COM Port and the following COM Port communications
parameters.
Baud Rate: 9600 bits/sec
Data Bits: 8
Stop Bits: 1
Parity: None
Flow Control: None
Initial Modem Commands: None
4. Hit the Return key and the Log on Menu will be displayed.
Note: If the PC uses MS Windows V3.1 or above, the Terminal Application in the Accessories group may
be used to establish the necessary VT100 emulation functionality.
7.1.3. 1.1.3. To Run the VT100 emulation under Windows
1. From the Accessories group select the Terminal Application.

2. Select Communications from the Settings menu.
3. In the Communications dialogue box set the following options:
Baud Rate - 9600
Data Bits - 8, Stop Bits - 1
Parity - None
Flow Control - None
Connector - COM1 or COM2 as appropriate
4. Select the Terminal Emulation option in the Settings menu and choose the VT100 (ANSI) option.

7.2. Initial Log In Procedure
7.2.1. To log on for the first time:

1. The first time the system is started there will be no user accounts configured and a screen similar to
the one shown below will be displayed:
System: <unnamed>
INNOVA Network Management Interface
Press <ENTER> to login::
Figure 7-1: Login Menu (no user accounts configured)
2. Press Enter.
3. The Main Menu will be displayed. See Figure 7-3.
Note : If there are no user accounts on the system the user will be logged on as Administration with modify
access.

7.2.2. To login with user accounts configured:

1. If the system has been used before and user accounts have been configured, A screen similar to the
one below will be seen when you attempt to log in:
System: <unnamed>
INNOVA Network Management Interface
Enter Username:-
Enter Password:-
Figure 7-2: Login Menu (user accounts configured)
2. Type a valid username at the login prompt and press ‘ENTER’

3. The prompt Enter Password will be displayed.
4. Type the password of the user and press ‘ENTER’.
5. The Main Menu will be displayed. See Figure 7-3.
Note : A message will be displayed just above the command line.
“--->User <username> logged in with <access_level> access<---”, where <username> is the name
of the user account used to log in and <access_level> is the access permission of the user account.

7.3. Main Menu

After logging on the Main Menu will be displayed:
INNOVA Network Management Interface Main Menu
System: <unnamed>
16:40:18 Fri May 15 1998
Loggers:
1)Event Logger
2)Error Logger
Options:
3)User Options
4)Code Download
5)Network Port Configuration
6)System Configuration
--->User bob logged in with modify access<---
Enter Selection or <Q> to quit (logoff)::
Figure 7-3: Main Menu
The Main Menu displays the options available the user.
7.3.1. To select an option
1. Press the number corresponding to a menu item.

2. The screen will scroll and the selected sub-menu will be displayed.
7.3.2. To Exit the Interface without saving changes

1. Press the Q key.
2. The following prompt will be displayed :
One or more parameters have been changed but not saved to ROM.
Enter <Q> to quit, <S> to save then quit, any other key to abort.
3. Press the Q key again to exit without saving any changes made.
4.

7.3.3. To Exit the Interface Saving changes

1. Press the Q key.
2. The following prompt will be displayed :
One or more parameters have been changed but not saved to ROM.
Enter <Q> to quit, <S> to save then quit, any other key to abort.
3. Press the S key to save any changes made and then exit the interface.
7.4. Event Logger

The Event Logger Menu is accessed by pressing 1 in the Main Menu. A screen similar to the one shown
below will be displayed:
Innova Network Management Interface Event Log Options Menu

10:26:36 Fri May 15 1998
Source Time Date Event Code Event Description
------------------------------------------------------------------------------
Options:
B) Back C)Clear Event Log S)Save Modifications
G) Goto latest event F)Event Filter is PM Events Disabled
Enter Selection or <Q> to quit::
Figure 7-4: Event Logger Menu
Note :
1. The Event logger will not be empty on power-up.
2. The Event logger will wrap after a predetermined wrap limit is exceeded.
3. Items listed in the Event Log are expected occurrences which occur as part of normal .

7.4.1. Navigating Through the list of Events
7.4.1.1.Browsing the list of events

To browse through the list of logged events:
1. From the Event Logger Menu, press the ‘ENTER’ key.
2. The Event Logger Menu will scroll and show the next events in the list.
3. Repeat step 1 to view the remaining events.
4. When the last event is displayed, pressing ENTER will scroll the Menu screen to display the most
recent event.
7.4.1.2.Examining the latest event

To examine the most recent logged event:
1. From the Event Logger Menu, press the ‘G’ key.
2. The Event Logger Menu will scroll and show a list of events starting with the most recently logged.
7.4.1.3.Clearing the Event Log

To clear the Event Log:
1. From the Event Logger Menu, press the ‘C’ key.
2. A prompt will be displayed to confirm that the log is to be cleared.
3. Press the ‘Y’ key to confirm and the Event Logger Menu will spin showing all events to have cleared.
Note: Clearing the Event Log can be aborted by pressing any key other than ‘Y’.
7.4.1.4.Configuring Event Filter Level

The Event Logger can be configured to log only certain events. The options are:
• Enable All Events
• Disable PM Events
• Disable All Events
To configure the filter level for the Event Logger:

1. From the Event Logger Menu, press the ‘F’ key.
2. A prompt will be displayed showing the available options, Enable All Events, Disable PM Events and
Disable All Events (options 1,2 & 3 respectively).
3. Select the required option by pressing the relevant number and then press ENTER.
4. The menu will scroll and display the choice made.

7.5. Error Logger

The Error Logger Menu is accessed by pressing 2 in the Main Menu. A screen similar to the one shown
Innova Network Management Interface Error Log Options Menu

10:32:29 Fri May 15 1998
Task Id Severity Summary Text Time Date Error Code
--------------------------------------------------------------------------------
Options:
B) Back C)Clear Error Log S)Save Modifications
G) Goto latest error F)Error Severity Filter level = MINOR
Figure 7-5: Error Logger Menu

Note:
1. The Error logger will wrap after a predetermined wrap limit is exceeded
2. Items listed in the error logger are occurrences which should not occur as part of normal system
operation.
7.5.1. Navigating Through the list of Errors
7.5.1.1.Browsing the list of errors

To browse through the list of logged errors:
1. From the Error Logger Menu, press the ‘ENTER’ key.
2. The Error Logger Menu will scroll and show the next 4 errors in the list.
3. Repeat step 1 to view the remaining errors.
4. When the last error is displayed, pressing ENTER will spin the Menu screen to display the most recent
error.

7.5.1.2.Examining the latest error

To examine the most recent logged error:
1. From the Error Logger Menu, press the ‘G’ key.
2. The Error Logger Menu will scroll and show a list of errors starting with the most recently logged.
7.5.1.3.Clearing the Error Log

To clear the Error Log:
1. From the Error Logger Menu, press the ‘C’ key.
2. A prompt will be displayed to confirm that the log is to be cleared.
3. Press the ‘Y’ key to confirm and the Error Logger Menu will spin showing all errors to have cleared.
Note: Clearing the Error Log can be aborted by pressing any key other than ‘Y’.
7.5.1.4.Configuring Error Filter Level

The Error Logger can be configured to log only certain errors depending on their severity. The options
are:
• MINOR (errors with MINOR severity and above are logged)
• MAJOR (errors with MAJOR severity and above are logged)
• CRITICAL (only events with CRITICAL severity are logged)
To configure the filter level for the Error Logger:

1. From the Error Logger Menu, press the ‘F’ key.
2. A prompt will be displayed showing the available options MINOR, MAJOR and CRITICAL (options 1,2
& 3 respectively).
3. Select the required option by pressing the relevant number and then press ENTER.
4. The menu will scroll and display the choice made.

7.6. User Options Menu

The User Options Menu is accessed by pressing 3 in the Main Menu. A screen similar to the one shown
INNOVA Network Management Interface User Options Menu

System: <unnamed>
10:59:19 Fri May 15 1998
Users:
------------------------------------------------------------------------------
super [ Administration ] bob [ Administration ]

john [ Maintenance ] jim [ View ]
Options:
A)Add User D)Delete User
C)Change Password S)Save Modifications
Figure 7-6: User Options Menu
The menu displays a list of all user accounts configured on the system along with their access permission
(View, Maintenance or Administration).
Note: Only users with Administration access may add and delete user accounts, but any user may
change their password.
7.6.1. Adding User Accounts
To add user accounts:
1. From the User Options Menu, press the ‘A’ key.

2. The prompt “Enter Username:- “ will be displayed.
3. Enter a username and press ‘ENTER’.
4. The prompt “Enter User Password:- “will be displayed.

5. Enter a password and press ‘ENTER’.

6. The prompt “Check: Re-enter User Password:- “ will be displayed.
7. Re-type the password and press ‘ENTER’.
8. A prompt showing a list of available access permissions will be displayed. Choose the users access
permission from the list of options shown and press ‘ENTER’
9. The terminal screen will scroll and the User Options Menu is displayed showing the newly added user
account.
10.Repeat steps 1 to 8 to add as many user accounts as necessary.
Note :
1.The first user to be added will be given Administration access automatically.
2. Only users with Administration access may add user accounts.
3. All user names and passwords will have trailing spaces removed.
7.6.2. Deleting User Accounts

To delete a user account:
1. From the User Options Menu, press the ‘ D’ key.

2. When prompted to enter a username, type the name of the user account to delete and press ‘ENTER’.
3. The terminal screen will scroll and the User Options Menu will be displayed with the deleted user
account removed from the user list.
Note: The system will not allow the user to delete the last account with Administration access.
7.6.3. Changing User Passwords

To change the password of a user account :
Note: The password of a user account can only be changed when that user account is used to log in.
1. From the User Options Menu, press the ‘C’ key.

2. When prompted to enter the old password type the old password and press ‘ENTER’.
3. Type the new password at the prompt and press ‘ENTER’.
4. Re-type the new password when prompted and press ‘ENTER’.
5. The terminal screen will scroll and the User Options Menu will be displayed with the message
“--->Password Changed<---”.

7.7. Code Download Menu

The Code Download Menu is accessed by pressing 4 in the Main Menu. The following screen will be
displayed:
INNOVA Network Management Interface Code Download Menu
System: <unnamed>
17:40:27 Fri May 15 1998
1)TFTP Server IP Address 0: 0: 0: 0

2)TFTP Target Port [Ethernet] Serial1 Serial2 XP4
3)SNMP Low Image FileName SNMPlo.bin
4)SNMP High Image Filename SNMPhi.bin
5)IDU Loader Filename iudnld.dwn
6)ODU Loader Filename odudnld.dwn
7)IDU Low Image Filename low.idu
8)IDU High Image Filename high.idu
9)ODU Low Image Filename low.odu
A)ODU High Image Filename high.odu
B)TFTP Inter Packet Time-out 5 seconds
C)Download File from TFTP Server & Reprogram Unit
S)Save Modifications
Enter Selection or <Q> to quit ::
Figure 7-7: Code Download Menu
7.7.1. Configuring TFTP Server IP Address

To modify the TFTP Server IP Address:.
1. Press ‘1’ to select the TFTP Server IP Address option.
2. A prompt to enter the first part of the address will be displayed.
3. Enter the first part of the IP Address and press ‘ENTER’.
4. Repeat this process for the remaining parts of the IP Address.
Note: This procedure can be aborted at any point by entering an invalid value (any non-numeric character
or number outside the range 0-255).
7.7.2. Configuring TFTP Target Port

The TFTP Target Port should be configured to be the port that TFTP will be run over (Ethernet, Serial1,
Serial2 or XP4).
To configure the TFTP Target Port:.
1. Press ‘2’ to select the TFTP Target Port option.

2. The Code Download menu will scroll and show the next selection to in the list.
7.7.3. Configuring Image Filenames

To change the filenames of the SNMP Code Images, IDU/ODU Loaders and IDU/ODU Code Images:
1. Select the filename to be changed by pressing the corresponding key (3-9 or A).
2. A prompt to enter the new filename will be displayed.
3. Enter the new filename and press the ‘ENTER’ key.
4. The Code Download Menu will spin and show the newly entered filename.
7.7.4. Configuring TFTP Inter Packet Time-out

The TFTP Inter Packet Time-out determines the time-out period between TFTP Packets sent from the
SNMP. To configure the time-out period:
1. Press the ‘B’ key to select the TFTP Inter Packet Time-out option.
2. A prompt to enter the new Packet Time-out will be displayed.
3. Enter the new time-out in seconds in the range 1 - 100 and press ‘ENTER’.
4. The Code Download Menu will scroll and show the newly enter Packet Time-out.
7.7.5. Reprogramming the SNMP

To reprogram the SNMP with a new version of code:.
1. Ensure that the TFTP Server is running and that it points to the directory containing the SNMP Code
Image files.
2. Set the TFTP Server IP Address to be the IP Address of the PC running the server.
3. Ensure that one of the Management Ports has a route to the TFTP Server.
4. Set the TFTP Target Port to the Management Port used.
5. Set the SNMP High and Low Image filenames displayed in the Code Download Menu to equal the
names of the SNMP files on the server.
6. Press ‘C’ to select the Download option.
7. A prompt to select the target board will be displayed.
8. Press ‘3’ to select the SNMP.
Note: This process can be aborted by pressing any key that does not correspond to an option (any key
except 1, 2 or 3.
9. The Code Download Menu will scroll and show the message ‘TFTP Download in Progress’.
10.After a time the message ‘TFTP Get Finished’ will be displayed in the event logger and the board will
reprogram itself.
11.The SNMP will then reset, wait 25 seconds and then press ‘ENTER’.
12.The login menu will be displayed.
Note : If the code Download process fails at any point the following messages will be displayed and the
SNMP will then continue running as normal.
The message “ TFTP Get Failed” will be displayed in the event logger if the SNMP image file

transfer does not complete.

The message “TFTP GET or Flash Process Failed” will be displayed in the event logger if the TFTP
transfer fails or an error occurs when the SNMP image is written to Flash ROM.
7.7.6. Reprogramming a Local/Remote IDU/ODU

To reprogram a Local/Remote IDU/ODU with a new version of code:
1. Ensure that the TFTP Server is running and that it points to the directory containing the Loader and
Code Image files.
2. Set the TFTP Server IP Address to be the IP Address of the PC running the server.
3. Ensure that one of the Management Ports has a route to the TFTP Server.
4. Set the TFTP Target Port to the Management Port used.
5. Set the Loader and Code Image filenames displayed in the Code Download Menu to equal the names
of the SNMP files on the server.
6. Press ‘C’ to select the Download option.
7. A prompt to select the target board will be displayed. The ODU or IDU can be selected by pressing 1
or 2 respectively. (Pressing any other key will abort the process).
8. A prompt to select the Local or Remote unit will be displayed. Select the desired destination by
pressing 1 or 2. (Pressing any other key will abort the process).
9. A prompt to choose RUN NEW (run the newly downloaded image) or RUN OLD (continue running the
old code until the unit is reset) will be displayed.
10.Select the desired option by pressing 1 or 2. (Pressing any other key will abort the process)
11.The Code Download Menu will scroll and display the message ‘TFTP Download In Progress’.
12.After a time the message ‘TFTP Get Finished’ will be displayed twice in the event logger.
13.The message ‘TFTP and Flash Process Finished’ will be displayed in the event logger to indicate that
the process was successful.
Note :
1. If the loader or Code image TFTP transfer fails, the message “TFTP Get Failed” will be displayed
in the event logger and the Code Download process will abort. The SNMP will continue operating as
normal. The event and error logs will indicate the errors that occurred.
2. If the transfer of files to the radio fails then the message “Failed after ‘’packets” will be displayed
in the event logger, where ‘’ is the number of packets transferred before an error occurred. The
Code Download process will abort and the SNMP will continue operating as normal.

7.8. Network Port Configuration Menu

The Network Port Configuration Menu is accessed by pressing ‘5’ in the Main Menu. A screen similar to
INNOVA Network Management Interface Network Port Configuration Menu
System: <unnamed>
11:04:40 Fri May 15 1998
Network Parameters:
1)Ethernet Management Port
2)Serial Management Port 1
3)Serial Management Port 2
4)XP4 Management Port
5)Inter-Connected Co-Located IP Address 0: 0: 0: 0
6)Co-Located XP4 Port IP Address 0: 0: 0: 0
Figure 7-8: Network Port Configuration Menu

To select an option press the number or letter corresponding to a menu option. After typing the character
the terminal screen will scroll and the selected sub menu will be displayed.

7.8.1. Ethernet Management Port Menu

The Ethernet Management Port Menu is accessed by pressing 1 in the Network Port Configuration Menu.
A screen similar to the one shown below will be displayed:
INNOVA Network Management Interface Ethernet Management Port Menu
System: <unnamed>
11:06:38 Fri May 15 1998
1)Ethernet Address 0:224:226: 0: 25: 89

2)Gateway IP Address 0: 0: 0: 0
3)IP Broadcast [Disabled] Enabled
4)Default Router IP Address 0: 0: 0: 0
5)Default Router Subnet Mask 0: 0: 0: 0
6)IP Address 194:131:185:246

7)Subnet Mask 255:255:255: 0
8)Trap Destination Menu

9)PM Trap Configuration Menu
A)Ethernet Connector Type [TWISTEDPAIR] BNC

B)Booted Indicator [Booted] Not_Booted
Figure 7-9: Ethernet Management Port Menu
Note:
1. A user with View Level access may not change any of the displayed parameters, only a user with
Maintenance Level access or greater may make modifications.
2. For more information on the Ethernet Management Port see section 8.1.1
3. The Ethernet address is a factory set value. The user can not alter this value.
7.8.1.1.Configuring Ethernet Management Port - Gateway IP Address

To modify the Gateway IP Address:
1. From the Ethernet Management Port Menu, press ‘2’.

3. Enter the first part of the Gateway IP Address and press ‘ENTER’.
4. Repeat this step for the remaining parts of the Gateway IP Address.

7.8.1.2.Configuring Ethernet Management Port - IP Broadcast

To enable or disable the IP Broadcast:

2. The screen will scroll and the Ethernet Management Port Menu will be displayed showing the IP
Broadcast to have toggled between Disabled and Enabled.
7.8.1.3.Configuring Ethernet Management Port - Default Router IP Address

To modify the Default Router IP Address:
1. From the Ethernet Management Port Menu , press ‘4’.

3. Enter the first part of the Default Router IP Address and press ‘ENTER’.
4. Repeat this step for the remaining parts of the Default Router IP Address.
7.8.1.4.Configuring Ethernet Management Port - Default Router Subnet Mask

To modify the Default Router Subnet Mask:.
1. From the Ethernet Management Port Menu , press ‘5’.

3. Enter the first part of the Default Router Subnet Mask and press ‘ENTER’.
4. Repeat this step for the remaining parts of the Default Router Subnet Mask.
7.8.1.5.Configuring Ethernet Management Port - IP Address

To modify the IP Address:
1. From the Ethernet Management Port Menu, press ‘6.

4. Repeat this step for the remaining parts of the IP Address.

7.8.1.6.Configuring Ethernet Management Port - Subnet Mask

To modify the Subnet Mask:

3. Enter the first part of the Subnet Mask and press ‘ENTER’.
4. Repeat this step for the remaining parts of the Subnet Mask.

7.8.1.7.Configuring Ethernet Management Port - Trap Destination IP Addresses

The Trap Destination IP Addresses are the addresses to which the SNMP will send SNMP Traps.
To modify the Trap Destination IP Address:

2. The Ethernet Trap Destination Menu will be displayed
3. Select 1, 2 or 3.
5. Enter the first part of the Trap Destination IP Address and press ‘ENTER’.
6. Repeat this step for the remaining parts of the Trap Destination IP Address.
7. Repeat steps 3 to 6 until all the required Trap destinations have been entered, up to a maximum of
three.
INNOVA network Management Interface Ethernet Trap Destination Menu
System: <unnamed>
11:15:34 Fri May 15 1998
1)Trap Destination 0: 0: 0: 0
4)Trap Generation [Disabled] Enabled
Figure 7-10: Ethernet Trap Destination

Note : With traps enabled, traps will only be sent to the trap destinations which are not set
to 0: 0: 0: 0.

7.8.1.8.Configuring Ethernet Management Port - Trap Generation

Allows the user to enable or disable the trap generation on the selected port.

2. The Ethernet Trap Destination Menu will be displayed.
3. From the Ethernet Trap Destination Menu, press ‘4’.
4. The screen will scroll and the Ethernet Trap Destination Menu will be displayed showing the Trap
Generation to have toggled between Disabled and Enabled.
7.8.1.9.Configuring Ethernet Management Port - PM Trap Configuration

To set the Performance Trap configuration:
1. From the Ethernet Management Port Menu, press ‘9’’.

2. The screen will scroll and the Ethernet PM Trap Configuration Menu will be displayed.
3. Select 1, the screen will scroll and display the Ethernet PM Trap Configuration Menu showing the
Performance Trap Generation to have changed to the next type of trap generation
INNOVA Network Management Interface Ethernet PM Trap Configuration Menu
System: <unnamed>
11:18:30 Fri May 15 1998
1)Performance Trap Generation Disabled Daily [All]
Figure 7-11: Ethernet Trap Configuration

Note : Below is a description of the options available.
Disabled - No Performance Traps are generated

Daily - Only Daily PM Bins generate Performance Traps

All - All Performance Bins generate Performance Traps
7.8.1.10.Configuring Ethernet Management Port - Ethernet Connector Type

To modify the Ethernet Connector Type:
1. From the Ethernet Management Port Menu, press ‘A’.
2. The screen will scroll and the Ethernet Management Port Menu displayed showing the Connector Type
to have toggled between Twisted Pair and BNC.
shorting jumper should not be connected when using 10Base T this will deactivate the 10Base T
7.8.1.11.Configuring Ethernet Management Port - Booted Indicator

The Booted Indicator determines whether the Ethernet Management Port will be initialised after reset.
To modify the Booted Indicator:
1. From the Ethernet Management Port Menu, press ‘B’ to select the Booted Indicator option.
2. The screen will scroll and the Ethernet Management Port Menu displayed showing the Booted Indicator
to have toggled between Booted and Not Booted.

7.8.2. Serial Management Ports 1 & 2

The Serial Management Port Menu are accessed by pressing 2 or 3 in the Network Port Configuration
Menu. A screen similar to the following will be displayed:
INNOVA Network Management Interface Serial Management Port 1 Menu
System: <unnamed>
11:20:55 Fri May 15 1998

3)IP Address 222: 0: 2: 1

4)Subnet Mask 255:255:255: 0
7)Other Serial Management Parameters
Figure 7-12: Serial Management Port Menu

Note:
Maintenance Level access or greater may make modifications.
2. For more information on Serial Management Port 1 and 2 see sections 8.1.2 and 8.1.3.
7.8.2.1.Configuring Serial Management Port - Default Router IP Address

To modify the Default Router IP Address:
1. From the Serial Management port Menu, press ‘1’.

3. Enter the first part of the Default Router IP Address and press ‘ENTER’.

7.8.2.2.Configuring Serial Management Port - Default Router Subnet Mask

To modify the Default Router Subnet Mask :
1. From the Serial Management Port Menu, press ‘2’.

7.8.2.3.Configuring Serial Management Port - IP Address

To Modify the IP Address :
7.8.2.4.Configuring Serial Management Port - Subnet Mask

To modify the Subnet Mask:


7.8.2.5.Configuring Serial Management Port - Trap Destination IP Address


2. The serial Port Trap Destination Menu will be displayed
three.
INNOVA Network Management Interface Port 1 Trap Destination Menu
System: <unnamed>
11:23:32 Fri May 15 1998
Figure 7-13: Serial Port Trap Destination
7.8.2.6. Configuring Serial Management Port - Trap Generation

Allows the user to enable or disable the trap generation on the selected port.


2. The Port Trap Destination Menu will be displayed.
3. From the Port Trap Destination Menu, press ‘4’.
4. The screen will scroll and the Port Trap Destination Menu will be displayed showing the Trap
7.8.2.7.Configuring Serial Management Port - PM Trap Configuration

To set the Performance Trap Generation:
1. From the Serial Management Port Menu, press ‘6’’.

2. The screen will scroll and the Port PM Trap Configuration Menu will be displayed.
3. Select 1, the screen will scroll and display the Port PM Trap Configuration Menu showing the
INNOVA Network Management Interface Port 1 PM Trap Configuration Menu
System: <unnamed>
11:26:02 Fri May 15 1998
Figure 7-14:Serial Trap Configuration

7.8.2.8.Configuring Serial Management Port - Baud Rate

The Baud Rate option is located in the Serial Management Port Sub Menu. To access this menu press ‘7’
in the Serial Management Port Menu. A screen similar to the one shown below will be displayed:
INNOVA Network Management Interface Serial Management Port 1 Sub Menu
System: <unnamed>
18:43:52 Fri May 15 1998
1)Baud Rate 9600 19200 38400 [57600] 115200
2)Interface Type [RS232] RS422
3)Booted Indicator [Booted] Not_Booted
4)Protocol [SLIP] PPP
5)Dial-Out Parameters
Figure 7-15: Serial Management Port 2 Sub Menu

To modify the Baud Rate :
1. From the serial Management Port Sub Menu, press ‘1’.
2. The terminal screen will scroll and display the Serial Management Port Sub Menu showing the Baud
Rate to have changed to the next highest Baud Rate.
3. Repeat Step 1 until the desired Baud Rate is selected.
7.8.2.9.Configuring Serial Management Port - Interface Type.

The interface type is located in the Serial Management Port Sub Menu , which can be accessed by
pressing 7 in the Serial Management Port Menu.
To modify the Interface Type:
1. From the Serial Management Port Sub Menu, press ‘2’.
2. The screen will scroll and the Serial Management Port Sub Menu displayed showing the Interface Type
to have toggled between RS232 and RS422.
7.8.2.10.Configuring Serial Management Port - Booted Indicator

The Booted Indicator determines whether or not the interface port will be initialised after reset.
The Booted Indicator is located in the Serial Management Port Sub Menu, which can be access by
pressing 7 in the Serial Management Port Menu.
To modify the Booted Indicator :


2. The screen will scroll and the Serial Management Port Sub Menu displayed showing the Booted
Indicator to have toggled between Not Booted and Booted.
7.8.2.11.Configuring Serial Management Port - Protocol.

The Protocol is located in the Serial Management Port Sub Menu, which can be access by pressing 7 in
the Serial Management Port Menu.
To modify the Protocol:

2. The screen will scroll and the Serial Management Port Sub Menu displayed showing the Protocol to
have toggled between SLIP and PPP.
7.8.3. Dial-Out Parameters Menu.

The Dial-Out parameters option is located in the Serial Management Port Sub Menu, which can be access
by pressing 7 in the Serial Management Port Menu.
To access the Dial Out Parameters menu:

2. The screen will scroll and the Dial-Out Parameters Menu will be displayed
INNOVA Network Management Interface Dial-Out Menu
System: <unnamed>
11:27:30 Fri May 15 1998
1)Modem Type [None] Robotics Motorola

2)Alarm Trap Generation Disabled Major-Critical [All]
Robotics Default String : ATF1X4Y0&H0&I0&N0&U0&B1&D0
3)Robotics User String : ATF1X4Y0&H0&I0&N0&U0&B1&D0
Motorola Default String :
ATX1N0&D0&K0&S0&R1S202=32\N0+MS=11,0,9600,3
3600
4)Motorola User String :
ATX1N0&D0&K0&S0&R1S202=32\N0+MS=11,0,9600,3
3600
5)Dialling Prefix A :
6)Dialling Prefix B :
7)Number of Modem Command Retries 3
8)Modem Command Timeout 30 seconds
9)Modem Connection Timeout 5 seconds
A)Other Dial-Out Parameters
Options: R)Reset Robotics Default M)Reset Motorola Default


7.8.3.1.Configure Modem Type

This indicates what type of Modem, if any, is connected to the Port.
To configure the modem type
1. From the Dial-Out Parameters Menu, press ‘1’
2. The screen will scroll and display the Dial-Out Parameters Menu showing the Modem type to have
changed to the next modem type.
3. Repeat step 1 until the desired Modem Type is highlighted.
Note : Below is a description of the options available
None - Direct Connection (No Modem)
Robotics - US Robotics V.34 Modem - Sportster Model
Motorola - Motorola Modem SURFR 56K Modem
7.8.3.2.Configure Alarm Trap Generation

This allows the Generation of Alarm Traps to be configured by the user.
To configure the Alarm Trap Generation

2. The screen will scroll and display the Dial-Out Parameters Menu showing the Alarm Trap Generation
to have changed to the next setting.
3. Repeat step 1 until the desired type of alarm trap generation is highlighted.
Disabled - No Alarm Traps are generated
Major-Critical Alarms - Only Major or Critical Alarms generate Alarm Traps
All Alarms - All Alarms generate Alarm Traps
7.8.3.3.Configuring Robotics User String

This string will be the one used to initialise the Modem. On Software Delivery it will match the US
Robotics Default String, but it can be edited by the user. The User String can be set back to the US
Robotics Initialisation String at any time.
To configure the Robotics User String:
1. From the Dial-Out Parameters Menu, press ‘3’.
2. A prompt to enter the new string will be displayed.
3. Enter the new string (of no more than 256 characters) and press ‘ENTER’.
4. The Dial-Out Parameters Menu will scroll showing the newly entered string.
7.8.3.4.Configuring Motorola User String

This string will be the one used to initialise the Modem. On Software Delivery it will match the Motorola
Default String, but it can be edited by the user. The User String can be set back to the Motorola
Initialisation String at any time.
To configure the Motorola User String:
1. From the Dial-Out Parameters menu, press ‘4’.
2. A prompt to enter the new string will be displayed.
3. Enter the new string (of no more than 256 characters) and press ‘ENTER’.
4. The Dial-Out Parameters Menu will spin showing the newly entered string.

7.8.3.5.Resetting Robotics String

To reset the Robotics String to the Default String:
1. From the Dial-Out Parameters menu, press ‘R’.
2. The Dial-Out Parameters Menu will spin and show the Robotics User String to have reset to the
Default Robotics String.
7.8.3.6.Resetting Motorola String

To reset the Motorola String to the Default String:
1. From the Dial-Out Parameters menu, press ‘M’.
2. The Modem Strings Menu will spin and show the Motorola User String to have reset to the default
Motorola String.
7.8.3.7.Configuring Dialling Prefix A

The Dialling Prefix shall be of the form Modem Dial Command + telephone number
e.g. ATDT01236780736
The Modem Dial Command in the example above is ATDT which indicates a Tone Dial network. Various
options are supported by the Modem when dialling out i.e. ATDP may be used if it is a pulse dial network.
Also, other characters may be included in the Text String to perform various functions e.g. A comma will
introduce a delay in the dial-out. The Modem User Manual provides a comprehensive list of these options.
Dialling Prefix A is used initially by the SNMP to establish a connection.
To configure the Dialling Prefix A:

2. A prompt to enter the New Dialling Prefix A will be displayed.
3. Enter the new Dialling Prefix A and press ‘ENTER’.
4. The Dial-Out Parameters Menu will spin showing the newly entered Dialling Prefix A.
Note : If Dialling Prefix A is a NULL string then it will not be used to establish a connection. Instead,
Dialling Prefix B will be used immediately.
7.8.3.8.Configuring Dialling Prefix B

This dialling prefix has the exact same format as Dialling Prefix A. This is used by the SNMP if it fails to
establish a connection using Dialling Prefix A. If Dial-Out fails using Prefix B, then the TRAP is thrown
away, and a Error placed in the Error Log.
To configure the Dialling Prefix B:

2. A prompt to enter the New Dialling Prefix B will be displayed.
3. Enter the new Dialling Prefix A and press ‘ENTER’.
4. The Dial-Out Parameters Menu will spin showing the newly entered Dialling Prefix B.
Note : If Dialling Prefix B is a NULL string then it will not be used to establish a connection. Instead, the
TRAP will be thrown away and an ERROR placed in the Error Log.
7.8.3.9.Configuring Number of Modem Command Retries

This allows the user to configure the number of times that the SNMP will attempt to establish a Modem
connection.

To configure the Number of Modem Command Retries:

2. A prompt to Enter Number Retries will be displayed.
3. Enter the new Number of Modem Command Retries (valid range 0 to 99) and press ‘ENTER’.
4. The Dial-Out Parameters Menu will spin showing the newly entered number of Modem Command
Retries.
Note : The number of retries applies to both Dialling Prefix A and Dialling Prefix B. i.e. If the number of
Retries is 10 the SNMP will attempt to establish a connection using Prefix A 10 times. If this fails
then the SNMP will attempt to establish a connection using Prefix B a further 10 times.
7.8.3.10.Configuring Modem Command Time-out

This allows the user to configure the time-out, in seconds, for each Modem Command.
To configure the Modem Command Time-out :

2. A prompt to enter the Dead Man Time-out will be displayed.
3. Enter the new Modem Command Time-out (valid range 0 to 255) and press ‘ENTER’.
4. The Dial-Out Parameters Menu will spin showing the newly entered Modem Command Time-out.
7.8.3.11.Configuring Modem Connection Time-out

This allows the user to configure the number of seconds the Modem connection will be held.
To configure the Modem Connection Time-out:

2. A prompt to enter the Dial-Out time-out will be displayed.
3. Enter the new Modem Connection Time-out (valid range 0 to 255) and press ‘ENTER’.
4. The Dial-Out Parameters Menu will spin showing the newly entered Modem Connection Time-out.

7.8.4. Dial-Out Parameters Sub Menu.

The Other Dial-Out Parameters option is located in the Dial-Out Parameters Menu, which can be access
by pressing 5 in the Serial Management Port Sub Menu.
To access the Dial Out Parameters sub menu:
1. From the Dial-Out Parameters Menu , press ‘a’.

2. The screen will scroll and the Dial-Out Parameters Sub Menu will be displayed
INNOVA Network Management Interface Dial-Out Parameters Sub-Menu
System: <unnamed>
11:30:07 Fri May 15 1998
1)Daily Update [No] Yes

2)Daily Update Time 00:00
3)Password Authentication [No] Yes
4)Authentication String :
5)User Name :
6)User Password :
7)No. of Authentication Retries 1
8)Authentication Timeout 10 seconds
9)No. of Protocol Retries 1
A)Protocol Timeout 30 seconds
B)IP Routing [No] Yes
Options: S)Save Modifications
7.8.4.1.Configuring Daily Update

To configure the Daily Update:
2. The screen will scroll and display the Dial-Out Parameters Sub Menu showing the Daily Update to
have changed to the next setting.
3. Repeat step 1 until the desired setting is highlighted.
7.8.4.2.Configuring Daily Update Time

To configure the Daily Update Time:
2. A prompt to enter the hour will be displayed.
3. Enter the new Daily Update Time (valid range 0 to 23) and press ‘ENTER’.
4. The Dial-Out Parameters Menu will spin showing the newly entered Daily Update Time.

7.8.4.3.Configuring Password Authentication

This allows Password Authentication with the NMS to be enabled/disabled
To configure the Password Authentication:

2. The screen will scroll and display the Dial-Out Parameters Sub Menu showing the Password
Authentication to have changed to the next setting.
3. Repeat step 1 until the desired setting is highlighted.
7.8.4.4.Configuring Authentication String

This is the string that the SNMP expects back from the NMS to indicate that it has been authenticated,
after the User Name and User Password have been sent out.
To configure the Authentication String:

2. A prompt to enter the new Authentication String will be displayed.
3. Enter the new Authentication String and press ‘ENTER’.
4. The Dial-Out Parameters Menu will spin showing the newly entered Authentication String.
Note : If this string is NULL the SNMP will send the User Name, the User Password and then the TRAP
without waiting for Authentication. Otherwise, the SNMP will wait for this string to be sent back to
the SNMP from the NMS before sending the TRAP. This, of course, is only relevant if the Password
Authentication is enabled.
7.8.4.5.Configuring User Name

This is the User Name to be used, along with the User Password, in the authentication process with the
NMS. It is a NULL terminated text string with a maximum of 10 characters.
To configure the User Name:

2. A prompt to enter the new User Name will be displayed.
3. Enter the new User Name and press ‘ENTER’.
4. The Dial-Out Parameters Menu will spin showing the newly entered User Name.
7.8.4.6.Configuring User Password

This is the User Password to be used, along with the User Name, in the authentication process with the
NMS. It is a NULL terminated text string with a maximum of 10 characters.
To configure the User Password:

2. A prompt to enter the new User Password will be displayed.
3. Enter the new User Password and press ‘ENTER’.
4. The Dial-Out Parameters Menu will spin and redisplay the Dial-Out Parameters Sub menu.

7.8.4.7.Configuring No. of Authentication Retries

This allows the user to configure the number of retries for Authentication.
To configure the No. of Authentication Retries:

2. A prompt to enter the No. of Auth. Retries will be displayed.
3. Enter the new number of Authentication Retries and press ‘ENTER’.
4. The Dial-Out Parameters Menu will scroll showing the new number of Authentication Retries.
7.8.4.8.Configuring Authentication Time-out

This allows the user to configure the time-out, in seconds, for each attempt at Authentication.
To configure the Authentication Time-out:

2. A prompt to enter the Authentication Time-out will be displayed.
3. Enter the new Authentication Time-out and press ‘ENTER’.
4. The Dial-Out Parameters Menu will scroll showing the new Authentication Time-out.
7.8.4.9.Configuring No. of Protocol Retries

This allows the user to configure the number of times that the SNMP will attempt Protocol establishment
with the modem.
To configure the number of Protocol Retries:

2. A prompt to enter the number of Protocol Retries will be displayed.
3. Enter the new number of Protocol Retries and press ‘ENTER’.
4. The Dial-Out Parameters Menu will scroll showing the new number of Protocol Retries.
7.8.4.10.Configuring Protocol Timeout

This allows the user to configure the time-out, in seconds, for each attempt at Protocol establishment.
To configure the Protocol Time-out:

1. From the Dial-Out Parameters menu, press ‘a’.
2. A prompt to enter the Protocol Time-out will be displayed.
3. Enter the new Protocol Time-out and press ‘ENTER’.
4. The Dial-Out Parameters Menu will scroll showing the new Protocol Time-out.
7.8.4.11.Configuring IP Routing
This allows the user to enable or disable IP routing
1. From the Dial-Out Parameters Menu, press ‘b’
2. The screen will scroll and display the Dial-Out Parameters Sub Menu showing the IP Routing to have
toggled between No or Yes.

7.8.4.12. IP Routing Of Traps - Causing Dial-Out

Section 7.8.5 provides a scenario for IP Routing based on a possible configuration.
The configuration shown below shall be used for explanation of IP Routing of Traps - Causing Dial-Out.
Local ODU Remote ODU
XP View
Remote IDU
Local IDU
RS232
9600 Baud Telecom/DataCom SNMP 2
SNMP 1 Analyser
SLIP over RS232

to Serial 1 10 Base-T
Ethernet
Motorola/Robotics
Modem
10 Base-T
Ethernet HUB
PSTN
PC3 Running
SNMP MIB
PPP over RS422 Browser and
to Serial 2 TFTP Server
Motorola/Robotics
Modem
SLIP over
RS232
PC2 Running PC1 Running

VT100 SNMP MIB SNMP MIB
Terminal Browser and Browser and
TFTP Server TFTP Server
IP Routing Of Traps

Example Configuration:
SNMP 1:
I. Ethernet Management Port
Ethernet Address - 0:9:6:7:4:1
IP Address - 194.131.185.236
Subnet Mask - 255.255.255.0
Default Router IP Address - 0.0.0.0
Default Router Subnet Mask - 0.0.0.0
Connector Type - Twisted Pair
Booted Indicator - Booted
Trap Generation - Enabled
Trap Destination 1: 194.131.185.153
II. Serial 1 Management Port

Subnet Mask - 255.255.255.0
Baud Rate - 19200
Protocol - SLIP
Interface Type - RS232
Modem Type - Robotics
IP Routing: On
III. Serial 2 Management Port

Subnet Mask - 255.255.255.0
Trap Generation - Disabled
Baud Rate - 57600
Protocol - PPP
Modem Type - None

IV. XP4 Management Port

Subnet Mask - 255.255.255.0
SNMP 2:
I. Ethernet Management Port
Booted Indicator - Not Booted
II. Serial 1 Management Port

III. Serial 2 Management Port


Subnet Mask - 255.255.255.0
I. PC1
IP Address - 194.131.185.153
Routing Table Entries -
Network 222.0.2.128 : Gateway 194.131.185.236
Network 222.0.3.128 : Gateway 194.131.185.236
Network 222.0.4.2 : Gateway 194.131.185.236
II. PC2
IP Address - 222.0.2.128
III. PC3
IP Address - 222.0.3.128

7.8.5. Routed IP Messages Causing Dial-Out

The SNMP supports the initiation of Dial-Out by routed IP messages. This functionality permits remote
SNMP’s to forward their traps to an SNMP with a modem attached and thus, by way of Dial-Out
connection forward the trap information onto a designated management application. An example scenario
can be explained by referring to the configuration specified for SNMP 1 and SNMP 2 in the figure above.
Example:
On the IDU associated with SNMP 2 raising a Local Radio SIU Tributary 1 Fault Alarm via the front panel
will lead to the following events. The Local Radio will notify SNMP 2 about the Local Trib alarm. Given
SNMP 2’s configuration a trap will be generated with an IP destination address of 222.0.2.128. This trap
will be sent to SNMP 1 by way of the XP4 port. On receiving this trap SNMP 1 (note: that SNMP 1 has IP
Routing enabled) will initiate a Dial-Out sequence to provide a SLIP connection with PC2 (as PC2’s IP
address is 222.0.2.128) so that it can successfully route the IP message. Once this connection is
established the trap information will be transmitted over the modem to the management application.
The SNMP can buffer up to 100 messages (IP messages or SNMP generated traps) to be sent out once
the modem connection (and protocol if necessary) has been established.
IP Routing can be configured (enabled/disabled) from both the VT100 and SNMP. The IP routing setting
will not affect the Dial-Out functionality with respect to locally generated traps.

7.8.6. XP4 Management Menu

The XP4 Management Port Menu is accessed by pressing 4 in the Network Port Configuration Menu. A
screen similar to the one shown below will be displayed:
INNOVA Network Management Interface XP4 Management Port Menu
System: <unnamed>
11:32:40 Fri May 15 1998

3)IP Address 0: 0: 0: 0
4)Subnet Mask 0: 0: 0: 0

7)Booted Indicator Booted [Not_Booted]
Figure 7-16: XP4 Management Port Menu

Note:
Maintenance Level access or greater may make modifications).
2. For more information on XP4 management port see section 8.1.4.
7.8.6.1.Configuring XP4 Management Port - Default Router IP Address

To modify the Default Router IP Address:.
1. From the XP4 Management Port menu, press ‘1’

3. Enter the first part of the Default Router IP Address and press ‘ENTER’’.

7.8.6.2.Configuring XP4 Management Port - Default Router Subnet Mask

To modify the Default Router Subnet Mask:
1. From the XP4 Management Port menu, press ‘2’.
7.8.6.3.Configuring XP4 Management Port - IP Address

To modify the IP Address:

7.8.6.4.Configuring XP4 Management Port - Subnet Mask

To modify Subnet Mask:

7.8.6.5.Configuring XP4 Management Port - Trap Destination IP Address

1. From the XP4 Management Port Menu, press ‘5’.

2. The XP4 Trap Destination Menu will be displayed


three.
INNOVA Network Management Interface XP4 Trap Destination Menu
System: <unnamed>
11:34:07 Fri May 15 1998
Figure 7-17: XP4 Trap Destination

7.8.6.6. XP4 Management Port - Trap Generation

Allows the user to enable or disable the trap generation on the selected port..
1. From the XP4 Management Port Menu, press ‘5’.

2. The XP4 Trap Destination Menu will be displayed.
3. From the Port Trap Destination Menu, press ‘4’.
4. The screen will scroll and the XP4 Trap Destination Menu will be displayed showing the Trap
7.8.6.7.XP4 Management Port - PM Trap Configuration

To set the Performance Trap Generation:
1. From the XP4 Management Port Menu, press ‘6’’.

2. The screen will scroll and the XP4 PM Trap Configuration Menu will be displayed.
3. Select 1, the screen will scroll and display the XP4 PM Trap Configuration Menu showing the
INNOVA Network Management Interface XP4 PM Trap Configuration Menu
System: <unnamed>
11:35:19 Fri May 15 1998
Figure 7-18: XP4 Trap Configuration

7.8.6.8.Configuring XP4 Management Port - Booted Indicator

The Booted Indicator determines whether or not the interface port will be initialised after reset.
To modify the Booted Indicator:

2. The screen will scroll and the XP4 Management Port Sub Menu displayed showing the Booted
Indicator to have toggled between Not Booted and Booted.
7.8.7. Inter-Connected Co-Located IP Address

The Inter-Connected Co-Located IP Address parameter is the IP Address of the Port of the Co-located
SNMP (Ethernet port or serial port only) by which the two SNMPs at the same end of a 1+1 Protected Link
are connected.
1. From the Network Port Configuration menu, press ‘5’.
3. Enter the first part of the Inter-Connected Co-Located IP Address and press ‘ENTER’.
4. Repeat this step for the remaining parts of the Inter-Connected Co-Located IP Address.
7.8.8. Co-Located XP4 Port IP Address

The Co-located Radio Port Address parameter is the IP Address of the Radio Port of the Co-located
SNMP.
1. From the Network Port Configuration menu, press ‘6’.
3. Enter the first part of the Co-Located XP4 Port IP Address and press ‘ENTER’.
4. Repeat this step for the remaining parts of the Co-Located XP4 Port IP Address.

7.9. System Configuration

The System Configuration Menu can be accessed by pressing 6 in the Main Menu. A screen similar to
INNOVA Network Management Interface System Configuration
System: <unnamed>
11:37:48 Fri May 15 1998
1)General
2)Performance Alarm Thresholds
3)SNMP Diagnostics
4)Radio Parameters
5)Software Version
6)Reset Status
Figure 7-19: System Configuration Menu

7.9.1. System Configuration General

The General Menu is accessed by pressing ‘1’ in the System Configuration Menu. A screen similar to the
one shown below will be displayed:
INNOVA Network Management Interface System Configuration - General
System: <unnamed>
11:38:50 Fri May 15 1998
1)System Name <unnamed>
2)Automatic Logout Time 120 Minutes Idle
3)Time 11:38:50
4)Date Fri May 15 1998
5)Set Management Port Defaults
6)Node Active Configuration Menu
7)Reset SNMP
Figure 7-20: System Configuration - General Menu
7.9.1.1.Configuring System Name

To modify the System Name:
1. From the General menu, press ‘1’.

2. A prompt to enter the System name will be displayed.
3. Enter the System Name, ensuring that the name is not more than 40 characters long.
7.9.1.2.Configuring Automatic Logout Time

Once a user has logged in to the VT100 session, if no keys are pressed for a certain amount of time, the
user will automatically be logged out. The time period is determined by the Auto Logout Time.
To modify the Auto Logout Time:
2. A prompt to enter the new Auto Logout Time will be displayed.
3. Enter the new logout time in minutes in the range 0 - 255 (0 disables the Auto Logout Timer)and press
‘ENTER’.

4. The menu screen will spin and show the newly entered logout time.
Note: The process can be aborted at by entering an invalid value (any non-numerical character or number
outside the range 0 - 255).
7.9.1.3.Configuring System Time

To set the System Time:

3. Enter the hour in the range 0 - 23 and press ‘ENTER’.
4. A prompt to enter the minutes will be displayed.
5. Enter the minutes in the range 0 -59 and press ‘ENTER’.
6. A prompt to enter the seconds will be displayed.
7. Enter the seconds in the range 0 - 59 and press ‘ENTER’ at the exact time.
8. The menu screen will spin and display the newly entered System Time.
7.9.1.4.Configuring System Date

To set the System Date:

2. A prompt to enter the day will be displayed.
3. Enter the day in the range 1 - 7 and press ‘ENTER’.
4. A prompt to enter the month will be displayed.
5. Enter the month in the range 1 - 12 and press ‘ENTER’.
6. A prompt to enter the year will be displayed.
7. Enter the year in the range 0 - 99 and press ‘ENTER’.
8. A prompt to enter the century will be displayed.
9. Press the ‘A’ key to select 19 or press the ‘B’ key to select 20.
10.The menu screen will spin and display the newly entered date.
7.9.1.5.Setting Management Port Defaults

This option will set each of the configurable parameters for the SNMP Management Ports and Radio
Stack to sensible default values. See Appendix F.
To set the defaults:
2. The menu screen will spin and display the message ‘Defaults Set’.
Note : This will overwrite the current port setting.( see Appendix F for default values)

7.9.1.6.Node Active Configuration

The node active configuration menu is accessed by selecting 6 from the System Configuration - General
menu. A screen similar to the one shown below will be displayed.
INNOVA Network Management Interface Node Active Configuration Menu
System: <unnamed>
11:40:27 Fri May 15 1998
1)Node Active Trap [No] Yes

2)Daily Time 00:00
Figure 7-21: Node Active Configuration Menu
7.9.1.6.1.Node Active Trap Configuration

The SNMP supports a configurable, via the VT100 and SNMP, Node Active Trap. At a specified time of
day(configured as below) the SNMP will send out a Node Active Trap to all the trap destinations of each
booted port which has traps enabled. the generation of the Node Active Trap can be enabled or disabled
(as shown below). The trap contains one field which will be a string detailing the system description as
specified in the MIBII system table, which for V2.0 NIM software is specified as “Innova XP Series”.
This allows the user to enable or disable the generation of Node Active Traps that will be sent to all the
relevant trap destinations.
1. Select 1 from the Node Active Configuration Menu.
2. The screen will scroll and the Node Active Configuration Menu will be displayed showing the Node
Active Trap to have toggled between No and Yes.
7.9.1.6.2.Daily Time
This allows the user to specify when the trap will be sent each day.
1. Select 2.
3. Enter the hour in the range 0 - 23 and press ‘ENTER’.
4. A prompt to enter the minutes will be displayed.

5. Enter the minutes in the range 0 -59 and press ‘ENTER’.

6. The menu screen will spin and display the newly entered Daily Time.
7.9.1.7.Resetting the SNMP

To reset the SNMP Card complete the following steps.
Note: Only users with Administration access can reset the SNMP Card.
2. A warning message will be displayed.
3. Press the ‘Y’ key to confirm.
4. After 25 seconds the SNMP Card will have reset.
Note : Resetting the SNMP will not effect the service of the XP4 unit to which it is attached.
7.9.2. System Configuration - Performance Alarm Thresholds

The Performance Alarm Thresholds Menu can be accessed by pressing 2 in the System Configuration
Menu. A screen similar to the one shown below will be displayed:
INNOVA Network Management Interface Performance Alarm Thresholds Menu
System: <unnamed>
10:36:07 Sun Dec 7 1997
1)G821 Errored Seconds / Hour: 20

2)G821 Errored Seconds / Day: 200
3)G821 Severely Errored Seconds / Hour: 10
4)G821 Severely Errored Seconds / Day: 100
5)G826 Errored Seconds / Hour: 25

6)G826 Errored Seconds / Day: 250
7)G826 Severely Errored Seconds / Hour: 15
8)G826 Severely Errored Seconds / Day: 150
Figure 7-22: Performance Alarm Thresholds Menu

Note :
1. The Performance Alarm Thresholds Menu, contains the thresholds for G821 and G826
Performance Alarms.
2. The period “DAY” represents 12 midnight to 12 midnight.
The threshold values that are configurable in this menu are:

1. G821 Errored Seconds/Hour - If there are greater than or equal to<threshold value> G821 Errored
Seconds in the last hour then a Minor Alarm will be raised.
2. G821 Errored Seconds/Day - If there are greater than or equal to <threshold value> G821 Errored
Seconds in the last day then a Minor Alarm will be raised.
3. G821 Severely Errored Seconds/Hour - If there are greater than or equal to <threshold value> G821
Severely Errored Seconds in the last hour then a Minor Alarm will be raised.

4. G821 Severely Errored Seconds/Day - If there are greater than or equal to <threshold value> G821
Severely Errored Seconds in the last day then a Minor Alarm will be raised.
5. G826 Errored Seconds/Hour - If there are greater than or equal to <threshold value> G826 Errored
Seconds in the last hour then a Minor Alarm will be raised.
6. G826 Errored Seconds/Day - If there are greater than or equal to <threshold value> G826 Errored
Seconds in the last day then a Minor Alarm will be raised.
7. G826 Severely Errored Seconds/Hour - If there are greater than or equal to <threshold value> G826
Severely Errored Seconds in the last hour then a Minor Alarm will be raised.
8. G826 Severely Errored Seconds/Day - If there are greater than or equal to <threshold value> G826
Severely Errored Seconds in the last day then a Minor Alarm will be raised.
7.9.2.1.Configuring Errored Seconds and Severely Errored Seconds per Hour

To modify the Errored Seconds and Severely Errored Seconds:
1. Select the threshold to modify by pressing the corresponding key (1 or 3 for G821, 5 or 7 for G826).
2. A prompt to enter the threshold will be displayed.
3. Enter the new threshold in the range (0 - 3600) and press ‘ENTER’.
4. The menu screen will spin and display the newly entered value.
Note: This process can be aborted by entering an invalid value (any non-numeric character or number
7.9.2.2.Configuring Errored Seconds and Severely Errored Seconds per Day

To modify the Errored Seconds and Severely Errored Seconds:
1. Select the threshold to modify by pressing the corresponding key (2 or 4 for G821, 6 or 8 for G826).
2. A prompt to enter the threshold will be displayed.
3. Enter the new threshold in the range (0 - 86400) and press ‘ENTER’.
4. The menu screen will spin and display the newly entered value.
Note: This process can be aborted by entering an invalid value (any non-numeric character or number
7.9.3. System Configuration - Diagnostic Status

The Diagnostics Status Menus display the results of Non-Intrusive and Intrusive Diagnostics.

7.9.3.1.Non Intrusive Diagnostics Menu

The Non Intrusive Diagnostics Menu is accessed by pressing ‘3’ in the System Configuration Menu. A
screen similar to the one below will be seen:
INNOVA Network Management Interface System Config - SNMP

Diagnostics
System: <unnamed>
11:42:40 Fri May 15 1998
Non Intrusive SNMP Diagnostic Results

------------------------------------------------------------------------
RAM Test PASSED
Real Time Clock Test PASSED
1)SNMP Intrusive Diagnostics
Figure 7-23: Non Intrusive Diagnostics Menu

The results of the non intrusive diagnostics will be displayed.
Non Intrusive Diagnostics performs the following tests:
RAM Test : Segments of RAM are tested by writing data patterns in double word mode and reading them
back in byte mode.
Real Time Clock Test : This test writes to and reads from the Real Time Clock RAM and verifies that the
Real Time Clock is running.

7.9.3.2.Intrusive Diagnostics Menu

The Intrusive Diagnostics Menu is accessed by pressing 1 in the Non Intrusive Diagnostics Menu. A
System: <unnamed>
11:43:26 Fri May 15 1998
Intrusive SNMP Diagnostic Results
------------------------------------------------------------------------
Serial Eeprom Test NOT RUN
Flash ROM Test NOT RUN
RAM Test NOT RUN
Real Time Clock Test NOT RUN
SCC1 Loopback Test NOT RUN
Radio Stack Test NOT RUN
Press 1 to start Intrusive Diagnostics, <Q> to quit::
Figure 7-24: Intrusive Diagnostics Menu
7.9.3.2.1.Starting Intrusive Diagnostics

To start Intrusive Diagnostics:.
1. From the Non Intrusive Diagnostic Menu, press ‘1’.
2. The message ‘Intrusive Diagnostics in Progress’ will be displayed with a ‘walking dot’.
3. After a time the Intrusive Diagnostics Menu will spin and show the results of each test.
Intrusive Diagnostics performs the following tests :
Serial EPROM Test : Two locations within serial EPROM are reserved for test purposes. Several byte
patterns are written to an read from these test locations.
Flash ROM Test : Segments of Flash are tested by writing data patterns in double word mode and
reading them back in byte mode.
RAM Test : Segments of RAM are tested by writing data patterns in double word mode and reading them
back in byte mode.
Real Time Clock Test : This test writes to an reads from the Real Time Clock RAM and verifies that the
Real Time Clock is running.
Note : The SCC1 Loopback Test is not an appropriate test.
SCC2, SCC3 Tests : The SCC is placed in loopback mode and a test message containing a 5 byte
pattern is transmitted. The test is passed if the message is received.
Radio Stack Test : The Radio Stack is placed in loopback mode and a test message containing a 5 byte
pattern is transmitted. The test is passed if the message is received.

7.9.4. System Configuration - Radio Stack Parameters

The Radio Stack Parameters Menu can be accessed by pressing 4 in the System Configuration Menu. A
Radio Parameters Menu
System: <unnamed>
11:44:27 Fri May 15 1998
1)Maximum Number of Transmit Retries 3
2)Transmit Monitor Timer 2000 milliseconds
Figure 7-25: Radio Stack Parameters Menu
7.9.4.1.Configuring Maximum Number of Transmit Retries

The Maximum Number of Transmit Retries determines the number of times the Radio Stack will attempt
to re-send a message when it has timed out.
To configure the Transmit Monitor Timer:
1. From the Radio Stack Parameters Menu, press ’1’.
2. A prompt to enter a new value will be displayed.
3. Enter a new value in the range (1 - 3) and press ‘ENTER’.
4. The Radio Stack Parameters Menu will spin and show the newly entered value.
Note: This procedure can be aborted by entering an invalid value (any non-numeric character or number
outside the range 1 -3).

7.9.4.2.Configuring Transmit Monitor Timer

The Transmit Monitor Timer specifies how long the SNMP will wait for a response to a transmitted
message before re-transmitting or timing out.
To configure the Transmit Monitor Timer:
1. From the Radio Stack Parameters Menu, press ‘2’.
2. A prompt to enter a new value will be displayed.
3. Enter a new time in milliseconds in the range (300 - 4000) and press ‘ENTER’.
4. The Radio Stack Parameters Menu will spin and show the newly entered value.
Note: This procedure can be aborted by entering an invalid value (any non-numeric character or number
outside the range 300 -4000).
7.9.5. System Configuration - Software Version

The Software Version Menu is accessed by pressing 5 in the System Configuration Menu. A screen
similar to the one shown below will be displayed:
INNOVA Network Management Interface System Config - Software

Version
System: <unnamed>
11:45:36 Fri May 15 1998
Boot Code Version V1.3
Primary Software Version V2.0L
Secondary Software Version V2.0H
Press <Q> to quit::
Figure 7-26: Software Version Menu

Note :
1. The Software Version Menu, displays the current versions of software running on the SNMP.
Versions are for the Boot Code Software and also the Primary and Secondary SNMP Code Images
are displayed.
2. The SNMP can store two code images at one time. If there is a valid code image in Primary then
the SNMP will always run that image, if there is no Primary image then the SNMP will run from
Secondary. In the absence of a valid code image the message ‘No Software Version’ will be
displayed.

7.9.6. Reset Status Menu

The Reset Status Menu is accessed by pressing 6 in the System Configuration Menu. A screen similar to
INNOVA Network Management Interface System Config - Reset Status Menu
System: <unnamed>
10:27:56 Sun Dec 7 1997
External Total System Reset 1

Power-Up Reset 0
Software Watchdog Reset 1
Double Bus Fault 0
Loss of Clock 0
Soft Reset 0
Soft Reset Pin 0
Critical Error 0
While Error 0
While Error Program Counter....0x0
Options:
W)Reset while error count C)Reset Critical Error count
Figure 7-27-: Reset Status Menu

The reset status section of the MIB and the VT100 details information on the type of reset (Software-
Hardware) that occurred on an SNMP.
External Total System Indicates that the last reset was caused by an external signal driving
Reset: RESETH (active low, open drain, bi-directional signal used to initiate an
external reset) low. This will reset all the QUICC’s (Quad Integrated
Communications Controller) peripherals to a state they had at power up
reset. This reset is also refereed to as system reset or hardware reset,
and has the same effect on the system as a power up reset.
Power - Up Reset: Indicates that the last reset was caused by the power up reset circuit.
Software WatchDog Reset Indicates that the last reset was caused by the software watchdog circuit
Double Bus Fault Indicates that the last reset was caused by the double bus fault monitor.
A double bus fault occurs when a bus error or an address error occurs
during exception processing sequence for any of the following:
1. A previous bus error

2. A previous address error
3. A reset.
For example: The processor attempts to stack several words containing
information about the state of the machine while processing a bus error
exception. If a bus error exception occurs during the stacking operation
the second error is considered a double bus fault.
Loss Of Clock: Indicates that the last reset was caused by a loss of frequency reference
to the clock sub-module
Soft Reset Indicates that the processor was reset by a RESET instruction.

Soft Reset Pin Indicates that the last reset was caused by an external signal driving
RESETS low. This can happen if the power dips below an unacceptable
working level. A comparator circuit will then reset the processor.
A critical Error Indicates that the SNMP has encountered a memory (RAM) problem.
This can be caused by for example heap exhaustion.
While Error The while error address is updated when the AMX operating system
detects an error condition. The address detailed indicates the source of
the problem.
7.9.6.1.Resetting While Error Count and Program Count

The While Error Count indicates if any software watchdog resets were due to the operating system
detecting an error.
To reset the counter:
1. From the Reset Status Menu, press ‘W’.
2. The menu will spin and show the counter to have reset to zero.
Note:
1. It is recommended that after the While Error Count is reset that it is saved immediately to non
volatile memory, otherwise a misleading value will be obtained on reset of the SNMP.
2. The Program Counter indicates the address that caused the error.
7.9.6.2.Resetting Critical Error Count

The Critical Error Count indicates if any software watchdog resets were due to a memory allocation or
initialisation error detected by the application software.
To reset the counter:
1. From the Reset Status Menu, press ‘C’
2. The menu will spin and show the counter to have reset to zero.
Note: It is recommended that after the Critical Error Count is reset that it is saved immediately to non
volatile memory, otherwise a misleading value will be obtained on reset of the SNMP.
7.10. Saving Modifications to Non-Volatile Memory

Any modifications made to system parameters must be saved to non-volatile memory otherwise they will
be lost when the SNMP is reset.
To save changes to non-volatile memory:
1. Navigate to a menu screen that has a Save Modifications option.

2. Press the ’S’ key.
3. The screen will scroll and the menu will be displayed showing the message “--->Save successful<---”.
Note : The save process saves all changes made in any menu not just the current menu.
Only users with Maintenance Level access or greater may save changes to non-volatile memory.
If the user has made changes via the VT100 screens and has saved the changes A screen similar to the
one shown below will be displayed when the user exits the VT100 screens:

>>>> logging out <<<<
Note:
The SNMP must be reset before all the

values changed in the last craft
session can take effect.
>>>>>Press Enter for Login Menu<<<<<
8. SNMP Network Port Configuration
8.1. Network Port Parameters

The purpose of this section is to give a brief description of each of the SNMP Network Port Parameters.
It should be noted that any changes made to Network Port parameters will not actually be used until the
SNMP is reset.
8.1.1. Ethernet Port

This section describes the parameters associated with the Ethernet Management Port.
I. Ethernet Address - The Ethernet address of the Ethernet port.
II. Gateway IP Address - The IP Address of the device that will act as the Gateway from an Ethernet
Network onto another Sub-net
III. IP Broadcast - Determines whether the broadcasting of IP packets on the Ethernet network is
enabled or disabled.
IV. Default Router IP Address - IP Address of the network node which is the default router for the
Ethernet port. The network address must correspond to that of the SNMPs other Network Ports
for the route to be valid.
V. Default Router Subnet Mask - The Subnet mask for the default router.
VI. IP Address - The IP address for the Ethernet port.
VII. Subnet Mask - The Subnet mask for the Ethernet port.
VIII. Trap Destination - The IP address to which traps being sent out of the Ethernet port shall be sent.
Up to three destinations can be set-up. Allows the generation of traps via the Ethernet port to be
Enabled or Disabled.
IX. PM Trap Configuration -.The options shall be:
Disabled - Performance traps will not be generated for this port.
Daily Bins - Only daily bin performance traps will be generated.
All - All performance traps will be generated.

X. Ethernet Connector Type - Determines whether the Ethernet port shall operate BNC or Twisted
Pair.
XI. Booted Indicator - Determines whether the Ethernet port is to be initialised or not.
8.1.2. Serial Management Port 1

This section describes the parameters associated with Serial Management Port 1.
Default Router IP Address - IP Address of the network node which is the default router for the Ethernet
port. The network address must correspond to that of the SNMPs other Network Ports for the route to be
valid.
I. Default Router IP Address - IP Address of the network node which is the default router for the
serial port. The network address must correspond to that of the SNMPs other Network Ports for
the route to be valid.
II. Default Router Subnet Mask - The Subnet mask for the default router.
III. IP Address - The IP address for the serial management port.
IV. Subnet Mask - The Subnet mask for the serial management port.
V. Trap Destination - The IP address to which traps being sent out of the serial management port 1
shall be sent. Up to three destinations can be set-up. Allows the generation of traps via the serial
management port to be Enabled or Disabled.
VI. PM Trap Configuration -.The options shall be:
VII. Baud Rate - The baud rate at which the serial management port will operate.
VIII. Interface Type - Determines whether the serial management port is configured for RS232 or
RS422.
IX. Booted Indicator - Determines whether the serial management port is to be initialised or not.
X. Protocol - Determines whether the protocol used over the serial management port is SLIP or PPP.
XI. Modem Type - If set to None then the SNMP assumes that no Modem is attached and will not try
to initialise it. This will not prevent a Modem being attached to the Serial Port for Dial-In purposes.
If set to Robotics then the SNMP will assume a Robotics Modem is attached to the Serial Port and
use Robotics Modem User String to initialise the Modem on port initialisation and as part of the
Dial-Out procedure. If set to Motorola then the SNMP will assume a Motorola Modem is attached
to the Serial Port and use Motorola Modem User String to initialise the Modem on port
initialisation and as part of the Dial-Out procedure.
XII. Alarm Trap Generation - If set to disabled then no Alarm Traps will be generated. If set to Major-
Critical then only Major and Critical Alarm Traps will be generated. If set to All then all Alarm
Traps will be generated.
XIII. Robotics Default String - This string contains the default Initialisation string for the Robotics
Modem to ensure correct operation. It cannot be changed by the user.
XIV. Robotics User String - This string is the Initialisation string that is used to configure the Robotics
Modem. This string can be changed by the user.
XV. Motorola Default String - This string contains the default Initialisation string for the Motorola

XVI. Motorola User String - This string is the Initialisation string that is used to configure the Motorola
XVII. Dialling Prefix A - This is the first dialling prefix (Modem Dial Command + Telephone Number)
used by the SNMP when attempting to Dial-Out.(i.e. ATDT01236780736)
XVIII. Dialling Prefix B - This is the second dialling prefix (Modem Dial Command + Telephone Number)
XIX. Number of Modem Command Retries - This is the number of times the SNMP will send a
command to the Modem if the command is not responded to. The range of values is 0 to 99.
XX. Modem Command Time-out - This is the time (in seconds) that the SNMP will wait for a response
from the Modem after a command has been sent to it. The range of values is 0 to 255.
XXI. Modem Connection Time-out - This is the time (in seconds) that the SNMP will keep the Modem
connection open after dialling out. The range of values is 0 to 255.
XXII. Daily Update - If set to No then the SNMP will NOT attempt to Dial-Out at the specified time of
day. If set to Yes then the SNMP will Dial-Out at the time specified in the Daily Update Time.
XXIII. Daily Update Time - This is the time at which the SNMP will Dial-Out (if configured to do so). The
time is in 24hr format.
XXIV. Password Authentication - If set to No then Traps will be sent over the Modem without an
Authentication. If set to Yes then Password Authentication will be required before the Trap is sent
XXV. Authentication String - This is the Text String that the SNMP expects back from the Remote NMS
to indicate that Password Authentication was successful, thus the Trap can now be sent. If this is
a NULL string then the SNMP will send the Trap regardless.
XXVI. User Name - The is the User Name used in Password Authentication and in PPP Password
Authentication Protocol negotiation.
XXVII. User Password - The is the User Password used in Password Authentication and in PPP
Password Authentication Protocol negotiation.
XXVIII. No. Of Authentication Retries - This is the number of times the SNMP will attempt to establish
authentication before giving up. The range of values is 0 to 99.
XXIX. Authentication Time-out - This is the time (in seconds) that the SNMP will wait for an
authentication reply from the remote NMS. The range of values is 0 to 255.
XXX. No. Of Protocol Retries - This is the number of times the SNMP will attempt to establish the
protocol before giving up (PPP only).The range of values is 0 to 99.
XXXI. Protocol Time-out - This is the time (in seconds) that the SNMP will wait for the protocol to be
established. The range of values is 0 to 255.
XXXII. IP Routing - This option allows the user to enable or disable IP routing
XXXIII. Restore Robotics Default Option - This option will copy the Robotics Default String into the
Robotics User String.
XXXIV. Restore Motorola Default Option - This option will copy the Motorola Default String into the
Motorola User String.

8.1.3. Serial Management Port 2

This section describes the parameters associated with Serial Management Port 2.
Default Router IP Address - IP Address of the network node which is the default router for the Ethernet
port. The network address must correspond to that of the SNMPs other Network Ports for the route to be
valid.
I. Default Router IP Address - IP Address of the network node which is the default router for the
serial port. The network address must correspond to that of the SNMPs other Network Ports for
the route to be valid.
III. IP Address - The IP address for the serial management port.
IV. Subnet Mask - The Subnet mask for the serial management port.
V. Trap Destination - The IP address to which traps being sent out of the serial management port 2
shall be sent. Up to three destinations can be set-up. Allows the generation of traps via the serial
management port to be Enabled or Disabled.
VII. Baud Rate - The baud rate at which the serial management port will operate.
VIII. Interface Type - Determines whether the serial management port is configured for RS232 or
RS422.
IX. Booted Indicator - Determines whether the serial management port is to be initialised or not.
X. Protocol - Determines whether the protocol used over the serial management port is SLIP or PPP.
XI. Modem Type - If set to None then the SNMP assumes that no Modem is attached and will not try
to initialise it. This will not prevent a Modem being attached to the Serial Port for Dial-In purposes.
If set to Robotics then the SNMP will assume a Robotics Modem is attached to the Serial Port and
use Robotics Modem User String to initialise the Modem on port initialisation and as part of the
Dial-Out procedure. If set to Motorola then the SNMP will assume a Motorola Modem is attached
to the Serial Port and use Motorola Modem User String to initialise the Modem on port
initialisation and as part of the Dial-Out procedure.
XII. Alarm Trap Generation - If set to disabled then no Alarm Traps will be generated. If set to Major-
Critical then only Major and Critical Alarm Traps will be generated. If set to All then all Alarm
Traps will be generated.
XIII. Robotics Default String - This string contains the default Initialisation string for the Robotics
XIV. Robotics User String - This string is the Initialisation string that is used to configure the Robotics
XV. Motorola Default String - This string contains the default Initialisation string for the Motorola
XVI. Motorola User String - This string is the Initialisation string that is used to configure the Motorola

XVII. Dialling Prefix A - This is the first dialling prefix (Modem Dial Command + Telephone Number)
XVIII. Dialling Prefix B - This is the second dialling prefix (Modem Dial Command + Telephone Number)
XIX. Number of Modem Command Retries - This is the number of times the SNMP will send a
command to the Modem if the command is not responded to. The range of values is 0 to 99.
XX. Modem Command Time-out - This is the time (in seconds) that the SNMP will wait for a response
from the Modem after a command has been sent to it. The range of values is 0 to 255.
XXI. Modem Connection Time-out - This is the time (in seconds) that the SNMP will keep the Modem
connection open after dialling out. The range of values is 0 to 255.
XXII. Daily Update - If set to No then the SNMP will NOT attempt to Dial-Out at the specified time of
day. If set to Yes then the SNMP will Dial-Out at the time specified in the Daily Update Time.
XXIII. Daily Update Time - This is the time at which the SNMP will Dial-Out (if configured to do so). The
time is in 24hr format.
XXIV. Password Authentication - If set to No then Traps will be sent over the Modem without an
Authentication. If set to Yes then Password Authentication will be required before the Trap is sent
XXV. Authentication String - This is the Text String that the SNMP expects back from the Remote NMS
to indicate that Password Authentication was successful, thus the Trap can now be sent. If this is
a NULL string then the SNMP will send the Trap regardless.
XXVI. User Name - The is the User Name used in Password Authentication and in PPP Password
Authentication Protocol negotiation.
XXVII. User Password - The is the User Password used in Password Authentication and in PPP
Password Authentication Protocol negotiation.
XXVIII. No. Of Authentication Retries - This is the number of times the SNMP will attempt to establish
authentication before giving up. The range of values is 0 to 99.
XXIX. Authentication Time-out - This is the time (in seconds) that the SNMP will wait for an
authentication reply from the remote NMS. The range of values is 0 to 255.
XXX. No. Of Protocol Retries - This is the number of times the SNMP will attempt to establish the
protocol before giving up (PPP only).The range of values is 0 to 99.
XXXI. Protocol Time-out - This is the time (in seconds) that the SNMP will wait for the protocol to be
established. The range of values is 0 to 255.
XXXII. IP Routing - This option allows the user to enable or disable IP routing
XXXIII. Restore Robotics Default Option - This option will copy the Robotics Default String into the
Robotics User String.
XXXIV. Restore Motorola Default Option - This option will copy the Motorola Default String into the
Motorola User String.

8.1.4. XP4 Port

This section describes the parameters associated with the XP4 Management Port.
I. Default Router IP Address - IP Address of the network node which is the default router for the XP4
port. The network address must correspond to that of the SNMPs other Network Ports for the
route to be valid.
III. IP Address - The IP address for the XP4 port.
IV. Subnet Mask - The Subnet mask for the XP4 port.
V. Trap Destination - The IP address to which traps being sent out of theXP4 port shall be sent. Up
to three destinations can be set-up. Allows the generation of traps via the XP4 port to be Enabled
or Disabled.
VII. Booted Indicator - Determines whether the XP4 port is to be initialised or not
VIII. The Inter-Connected Co-Located IP Address parameter is the IP Address of the Port of the Co-
located SNMP (Ethernet port or serial port only) by which the two SNMPs at the same end of a
1+1 Protected Link are connected.
IX. The Co-located Radio Port Address parameter is the IP Address of the Radio Port of the Co-
located SNMP.
8.2. Network Port Configuration Examples

The following sections provide example SNMP configurations and details the SNMP Management Port
settings that are required.
The notation on the diagrams can be explained as follows :
1. A box containing the label SNMPx represents an SNMP.
2. A box containing the label PCx represents a PC.
3. A double arrowed line connected between two boxes is an IP connection.
4. The label on an IP connection indicates the protocol over which IP is running. A value of XP4
indicates that IP messages are being transferred via the XP4 Radio Link (the IDU’s and ODU’s are not
shown on the diagrams).

8.2.1. 2 SNMPs Routing via SLIP
SNMP 1 SNMP 2
Figure 8-1 : 2 SNMPs Routing via SLIP
In order to achieve this test configuration the network interfaces should be configured via the VT100
terminal as follows :
I. SNMP 1
A. Ethernet Management Port
B. Serial 1 Management Port
Subnet Mask - 255.255.255.0
Baud Rate - 57600
Protocol - SLIP
Modem Type - None
C. Serial 2 Management Port
Subnet Mask - 255.255.255.0
Baud Rate - 57600
Protocol - SLIP
Modem Type - None
D. XP4 Management Port

II. SNMP 2
Subnet Mask - 255.255.255.0
Baud Rate - 57600
Protocol - SLIP
Modem Type - None

Subnet Mask - 255.255.255.0
Baud Rate - 57600
Protocol - SLIP
Modem Type - None

III. PC1
IP Address - 222.0.2.128
Routing Table - 222.0.3.0, 222.0.4.0
IV. PC2
IP Address - 222.0.4.128
Routing Table - 222.0.3.0, 222.0.2.0

8.2.2. 2 SNMPs Routing via SLIP and Ethernet
Error! Not a valid link.

Figure 8-2 : 2 SNMPs Routing via SLIP and Ethernet
I. SNMP 1
IP Address - 222.0.1.51
Subnet Mask - 255.255.255.0

Subnet Mask - 255.255.255.0
Baud Rate - 57600
Protocol - SLIP
Modem Type - None


II. SNMP 2
Subnet Mask - 255.255.255.0
Baud Rate - 57600
Protocol - SLIP
Modem Type - None
Subnet Mask - 255.255.255.0
Baud Rate - 57600
Protocol - SLIP
Modem Type - None
III. PC1
IP Address - 222.0.1.12
Routing Table - 222.0.3.0, 222.0.4.0
IV. PC2
IP Address - 222.0.4.128
Routing Table - 222.0.3.0, 222.0.1.0

8.2.3. 2 SNMPs Routing via XP4 and SLIP
SNMP 1 SNMP 2
Figure 8-3 : 2 SNMPs Routing via XP4 and SLIP
In order to achieve this test configuration the network interfaces should be configured via the
VT100 terminal as follows :
I. SNMP 1
Subnet Mask - 255.255.255.0
Baud Rate - 57600
Protocol - SLIP
Modem Type - None
Subnet Mask - 255.255.255.0

II. SNMP 2
Subnet Mask - 255.255.255.0
Baud Rate - 57600
Protocol - SLIP
Modem Type - None
Subnet Mask - 255.255.255.0
III. PC1
IP Address - 222.0.2.128
Routing Table - 222.0.5.0, 222.0.4.0
IV. PC2
IP Address - 222.0.4.128
Routing Table - 222.0.5.0, 222.0.2.0

8.2.4. 2 SNMPs Routing via XP4, SLIP and Ethernet
SNMP 1 SNMP 2
Figure 8-4 : 2 SNMPs Routing via XP4, SLIP and Ethernet
I. SNMP 1
IP Address - 222.0.1.51
Subnet Mask - 255.255.255.0
Subnet Mask - 255.255.255.0

II. SNMP 2
Subnet Mask - 255.255.255.0
Baud Rate - 57600
Protocol - SLIP
Modem Type - None
Subnet Mask - 255.255.255.0
III. PC1
IP Address - 222.0.1.12
Routing Table - 222.0.5.0, 222.0.4.0
IV. PC2
IP Address - 222.0.4.128
Routing Table - 222.0.5.0, 222.0.1.0

8.2.5. 3 SNMPs Routing via SLIP
Figure 8-5 : 3 SNMPs Routing via SLIP
I. SNMP 1
Subnet Mask - 255.255.255.0
Baud Rate - 57600
Protocol - SLIP
Modem Type - None
Subnet Mask - 255.255.255.0
Baud Rate - 57600
Protocol - SLIP
Modem Type - None

II. SNMP 2
Subnet Mask - 255.255.255.0
Baud Rate - 57600
Protocol - SLIP
Modem Type - None
Subnet Mask - 255.255.255.0
Baud Rate - 57600
Protocol - SLIP
Modem Type - None
III. SNMP 3

Subnet Mask - 255.255.255.0
Baud Rate - 57600
Protocol - SLIP
Modem Type - None
Subnet Mask - 255.255.255.0
Baud Rate - 57600
Protocol - SLIP


Modem Type - None

V. PC1
IP Address - 222.0.2.128
Routing Table - 222.0.3.0, 222.0.4.0, 222.0.5.0
VI. PC2
IP Address - 222.0.5.128
Routing Table - 222.0.4.0, 222.0.3.0, 222.0.2.0

8.2.6. 3 SNMPs Routing via SLIP and XP4
Figure 8-6 : 3 SNMPs Routing via SLIP and XP4
I. SNMP 1
Subnet Mask - 255.255.255.0
Baud Rate - 57600
Protocol - SLIP
Modem Type - None
Subnet Mask - 255.255.255.0

II. SNMP 2
Subnet Mask - 255.255.255.0
Baud Rate - 57600
Protocol - SLIP
Modem Type - None
Subnet Mask - 255.255.255.0
III. SNMP 3
Subnet Mask - 255.255.255.0
Baud Rate - 57600
Protocol - SLIP
Modem Type - None
Subnet Mask - 255.255.255.0
Baud Rate - 57600
Protocol - SLIP
Modem Type - None


IV. PC1
IP Address - 222.0.2.128
Routing Table - 222.0.5.0, 222.0.4.0, 222.0.3.0
V. PC2
IP Address - 222.0.3.128
Routing Table - 222.0.4.0, 222.0.5.0, 222.0.2.0
8.2.7. 4 SNMPs Routing over SLIP and XP4
Figure 8-7 : 4 SNMPs Routing over SLIP and XP4
I. SNMP 1
Subnet Mask - 255.255.255.0
Baud Rate - 57600
Protocol - SLIP
Modem Type - None
Subnet Mask - 255.255.255.0
II. SNMP 2


Subnet Mask - 255.255.255.0
Baud Rate - 57600
Protocol - SLIP
Modem Type - None
Subnet Mask - 255.255.255.0
III. SNMP 3
Subnet Mask - 255.255.255.0
Baud Rate - 57600
Protocol - SLIP
Modem Type - None
Subnet Mask - 255.255.255.0

IV. SNMP 4
Subnet Mask - 255.255.255.0
Baud Rate - 57600
Protocol - SLIP
Modem Type - None
V. XP4 Management Port
Subnet Mask - 255.255.255.0
VI. PC1
IP Address - 222.0.2.128
Routing Table - 222.0.3.0, 222.0.4.0, 222.0.5.0, 222.0.6.0
VII. PC2
IP Address- 222.0.3.128
Routing Table - 222.0.5.0, 222.0.4.0, 222.0.3.0, 222.0.2.0

8.2.8. SNMP’s Routing via SLIP, Ethernet and XP4
SNMP 1 SNMP 2
SNMP 4
SNMP 3
Figure 8-8 : 4 SNMP’s Routing via SLIP, Ethernet and XP4

I. SNMP 1
Subnet Mask - 255.255.255.0
Baud Rate - 57600
Protocol - SLIP
Modem Type - None
Subnet Mask - 255.255.255.0
II. SNMP 2


Subnet Mask - 255.255.255.0
Gateway IP Address - 0.0.0.0
IP Broadcast - On
Subnet Mask - 255.255.255.0
III. SNMP 3
Subnet Mask - 255.255.255.0
IP Broadcast - Off
Subnet Mask - 255.255.255.0
Baud Rate - 57600
Protocol - SLIP
Modem Type - None

IV SNMP 4
Subnet Mask - 255.255.255.0
IP Broadcast - Off
V. PC1
IP Address - 222.0.2.128
Routing Table Entries - Network 222.0.3 : Gateway 222.0.2.1
Network 222.0.4 : Gateway 222.0.2.1
VI. PC2
IP Address - 222.0.5.128

8.2.9. 4 SNMPs Routing via SLIP and Ethernet
SNMP 1 SNMP 2
SNMP 4
SNMP 3
Figure 8-9 : 4 SNMPs Routing via SLIP and Ethernet

I. SNMP 1
IP Address - 222.0.1.51
Subnet Mask - 255.255.255.0
Default Router IP Address -222.0.2.2
Subnet Mask - 255.255.255.0
Baud Rate - 57600
Protocol - SLIP
Modem Type - None

II. SNMP 2
Subnet Mask - 255.255.255.0
IP Broadcast - On
Subnet Mask - 255.255.255.0
Baud Rate - 57600
Protocol - SLIP
Modem Type - None
III. SNMP 3
Subnet Mask - 255.255.255.0
IP Broadcast - Off
Subnet Mask - 255.255.255.0
Baud Rate - 57600
Protocol - SLIP
Modem Type - None


IV. SNMP 4
Subnet Mask - 255.255.255.0
IP Broadcast - Off
V. PC1
IP Address - 222.0.1.12
Network 222.0.3 : Gateway 222.0.1.51
Network 222.0.4 : Gateway 222.0.1.51
VI. PC2
IP Address - 222.0.4.128
8.2.10.SNMPs Routing over SLIP, Ethernet, and XP4

Figure 8-10 : SNMPs Routing over SLIP, Ethernet, and XP4
I. SNMP 1
IP Address - 222.0.1.51
Subnet Mask - 255.255.255.0
Default Router IP Address -222.0.4.2
Subnet Mask - 255.255.255.0
II. SNMP 2
Subnet Mask - 255.255.255.0
Baud Rate - 57600
Protocol - SLIP
Modem Type - None

Subnet Mask - 255.255.255.0
III. SNMP 3


Subnet Mask - 255.255.255.0
Baud Rate - 57600
Protocol - SLIP
Modem Type - None
Subnet Mask - 255.255.255.0
IV. SNMP 4
Subnet Mask - 255.255.255.0
Default Router IP Address - 0.0.0.0.
Trap Destination - 222.0.1.12
E. PC1
IP Address - 222.0.1.12
Routing Table - 222.0.4.0, 222.0.5.0, 222.0.6.0
8.2.11.Ethernet/LAN
The configuration shown below shall be used for performing SNMP based management of the XP4
Radios using Ethernet protocol via the Ethernet connector on the SNMP card. The VT100 terminal shall
be connected to the VT100 connector of the SNMP card and shall be required for configuring SNMP IP
Addresses etc. prior to performing the tests.

SNMP
Figure 8-11: Ethernet/LAN
The network interfaces used should initially be configured via the VT100 terminal as follows :
1) Ethernet Management Port
Ethernet Management Port
IP Address - 194.131.185.236
Subnet Mask - 255.255.255.0
Default Router IP Address - 0.0.0.0.
2) Serial 1 Management Port

3) Serial 2 Management Port

4) XP4 Management Port
8.2.12.1+1 Protection Switch Routing Test Configurations

The notation used on the diagrams can be explained as follows :
1) A box containing the label SNMPx represents an SNMP (the IDU and ODU to which the SNMP is
attached is not shown on the diagram to avoid unnecessary clutter).
2) A box containing the label PCx or Snooperx represents a PC or Unix workstation which has an ICMP
Ping utility and a snooper utility allowing the real time analysis and display of all ICMP and IP packets
being transported on the LAN to which it is connected (on a Unix workstation running the Solaris 2.5
Operating System the utility used will be snoop).
3) A double arrowed line connected between two boxes represents an IP connection.
4) The label on an IP connection indicates the protocol over which IP is running. A value of XP4 indicates
the IP messages are being transferred via the XP4 Radio Link. An line representing a 10 Base-T
Ethernet connection is not labelled because the presence of a box representing a 10 Base-T Ethernet
Hub is indicative of the fact that the LAN is Ethernet based.
5) The label next to the double arrow connecting a Protection Switch to an SNMP indicates to which side
of the Protection Switch the SNMP is connected i.e. A or B.

8.2.12.1.Single 1+1 Protected Link
SNMP 1 SNMP 2
SNMP 3 SNMP 4
Figure 8-12 : Single 1+1 Protected Link
I. SNMP 1
IP Address - 194.131.185.246
Subnet Mask - 255.255.255.0
IP Broadcast - Off
Subnet Mask - 255.255.255.0


E. Co-located IP Addresses
Co-located Interconnected IP Address - 194.131.185.248
Co-located Radio Port IP Address - 222.0.2.1
II. SNMP 3
IP Address - 194.131.185.248
Subnet Mask - 255.255.255.0
IP Broadcast - Off
Subnet Mask - 255.255.255.0
III. SNMP 2
Subnet Mask - 255.255.255.0
IP Broadcast - Off


Subnet Mask - 255.255.255.0
IV. SNMP 4
Subnet Mask - 255.255.255.0
IP Broadcast - Off
Subnet Mask - 255.255.255.0
V. PC1
IP Address - 194.131.185.247
Network 222.0.2 : Gateway 194.131.185.246
Network 222.0.3 : Gateway 194.131.185.246
VI. PC2
Network 194.131.185 : Gateway 222.0.3.1

8.2.12.2.Single 1+1 Protected Link and Two 1+0 Links
SNMP 1 SNMP 2
SNMP 10 SNMP 11
SNMP 3 SNMP 4
SNMP 9 SNMP 12
Figure 8-13 : Single 1+1 Protected Links and Two 1+0 Links
I. SNMP 9
IP Address - 194.131.185.246
Subnet Mask - 255.255.255.0

IP Broadcast - Off
Subnet Mask - 255.255.255.0
II. SNMP 10
Ethernet Address - 0:9:6:7:4:a
Subnet Mask - 255.255.255.0
IP Broadcast - Off
Subnet Mask - 255.255.255.0
III. SNMP 1
Subnet Mask - 255.255.255.0


IP Broadcast - Off
Subnet Mask - 255.255.255.0
IV. SNMP 3
Subnet Mask - 255.255.255.0
IP Broadcast - Off
Subnet Mask - 255.255.255.0
V. SNMP 2


Subnet Mask - 255.255.255.0
IP Broadcast - Off
Subnet Mask - 255.255.255.0
VI. SNMP 4
Subnet Mask - 255.255.255.0
IP Broadcast - Off
Subnet Mask - 255.255.255.0

VII. SNMP 11
Ethernet Address - 0:9:6:7:4:b
Subnet Mask - 255.255.255.0
IP Broadcast - Off
Subnet Mask - 255.255.255.0
VIII. SNMP 12
Ethernet Address - 0:9:6:7:4:c
Subnet Mask - 255.255.255.0
IP Broadcast - Off
Subnet Mask - 255.255.255.0


IX. PC1
IP Address - 194.131.185.247
Network 222.0.7 : Gateway 194.131.185.246
Network 222.0.1 : Gateway 194.131.185.246
Network 222.0.2 : Gateway 194.131.185.246
Network 222.0.3 : Gateway 194.131.185.246
Network 222.0.4 : Gateway 194.131.185.246
Network 222.0.5 : Gateway 194.131.185.246
X. PC2
Network 194.131.185 : Gateway 222.0.3.1
XI. Snooper 1
XII. Snooper 2
8.2.12.3. Two 1+1 Protected Links Connected in Series
Figure 8-14 : Two 1+1 Protected Links Connected in Series

I. SNMP 1
IP Address - 194.131.185.246
Subnet Mask - 255.255.255.0
IP Broadcast - Off


Subnet Mask - 255.255.255.0
II. SNMP 3
IP Address - 194.131.185.248
Subnet Mask - 255.255.255.0
IP Broadcast - Off
Subnet Mask - 255.255.255.0
III. SNMP 2
Subnet Mask - 255.255.255.0

IP Broadcast - Off
Subnet Mask - 255.255.255.0
IV. SNMP 4
Subnet Mask - 255.255.255.0
IP Broadcast - Off
Subnet Mask - 255.255.255.0
V. SNMP 5
Subnet Mask - 255.255.255.0


IP Broadcast - Off
Subnet Mask - 255.255.255.0
VI. SNMP 7
Subnet Mask - 255.255.255.0
IP Broadcast - Off
Subnet Mask - 255.255.255.0

VII. SNMP 6
IP Address - 222.0.10.1
Subnet Mask - 255.255.255.0
IP Broadcast - Off
Subnet Mask - 255.255.255.0
VIII. SNMP 8
IP Address - 222.0.10.2
Subnet Mask - 255.255.255.0
IP Broadcast - Off
Subnet Mask - 255.255.255.0

IX. PC1
IP Address - 194.131.185.247
Network 222.0.2 : Gateway 194.131.185.246
Network 222.0.3 : Gateway 194.131.185.246
Network 222.0.8 : Gateway 194.131.185.246
Network 222.0.9 : Gateway 194.131.185.246
Network 222.0.10 : Gateway 194.131.185.246
X. PC2
Network 222.0.9 : Gateway 222.0.10.1
Network 222.0.3 : Gateway 222.0.10.1
Network 222.0.1 : Gateway 222.0.10.1
Network 222.0.2 : Gateway 222.0.10.1
Network 194.131.185 : Gateway 222.0.10.1
XI. Snooper 1

8.2.12.4. Two 1+1 Protected Links Connected in Parallel
Network
222.0.1
Network
222.0.3
SNMP1
NMI SNMP
NMI 2
1 2
XP4
A A
Snooper 1 Protection Protection 10 Base-T

Switch 1 Switch 1 Ethernet HUB
Network Local Remote
222.0.7 Network
222.0.2
B B
SNMP SNMP
NMI3
3 NMI4 4
XP4
SNMP 10 Base-T
NMI
1010 Ethernet HUB
PC2
XP4
SNMP5
NMI NMI
SNMP6 Network
Network 5 6 222.0.10
222.0.6 XP4
A A
Network
Protection 222.0.8 Protection
NMI
SNMP9 10 Base-T
Switch 2 Switch 2
9 Ethernet HUB
Local Remote
B B
XP4
Network 10 Base-T
Ethernet HUB SNMP7
NMI SNMP
194.131.185
7
NMI8
8
Network
222.0.9 PC3
PC1
Figure 8-15 : Two 1+1 Protected Links Connected in Parallel
I. SNMP 9
IP Address - 194.131.185.246
Subnet Mask - 255.255.255.0


IP Broadcast - Off
Subnet Mask - 255.255.255.0
II. SNMP 10
Subnet Mask - 255.255.255.0
IP Broadcast - On
Subnet Mask - 255.255.255.0
III. SNMP 1


Subnet Mask - 255.255.255.0
Broadcast - On
Subnet Mask - 255.255.255.0
IV. SNMP 3
Subnet Mask - 255.255.255.0
IP Broadcast - On
Subnet Mask - 255.255.255.0

V. SNMP 2
Subnet Mask - 255.255.255.0
IP Broadcast - Off
Subnet Mask - 255.255.255.0
VI. SNMP 4
Subnet Mask - 255.255.255.0
IP Broadcast - Off
Subnet Mask - 255.255.255.0


VII. SNMP 5
Subnet Mask - 255.255.255.0
IP Broadcast - On
Subnet Mask - 255.255.255.0
VIII. SNMP 7
Subnet Mask - 255.255.255.0
IP Broadcast - On


Subnet Mask - 255.255.255.0
IX. SNMP 6
IP Address - 222.0.10.1
Subnet Mask - 255.255.255.0
IP Broadcast - Off
Subnet Mask - 255.255.255.0
X. SNMP 8
IP Address - 222.0.10.2
Subnet Mask - 255.255.255.0
IP Broadcast - Off


Subnet Mask - 255.255.255.0
XI. PC1
IP Address - 194.131.185.247
Network 222.0.7 : Gateway 194.131.185.246
Network 222.0.1 : Gateway 194.131.185.246
Network 222.0.2 : Gateway 194.131.185.246
Network 222.0.3 : Gateway 194.131.185.246
Network 222.0.8 : Gateway 194.131.185.246
Network 222.0.9 : Gateway 194.131.185.246
Network 222.0.10 : Gateway 194.131.185.246
XII. PC2
Network 222.0.10 : Gateway 222.0.3.1
Network 194.131.185 : Gateway 222.0.3.1
XIII. PC3
IP Address - 222.0.10.3
Network 222.0.9 : Gateway 222.0.10.1
Network 222.0.7 : Gateway 222.0.10.1
Network 222.0.1 : Gateway 222.0.10.1
Network 222.0.2 : Gateway 222.0.10.1
Network 222.0.3 : Gateway 222.0.10.1
Network 222.0.6 : Gateway 222.0.10.1
Network 194.131.185 : Gateway 222.0.10.1
XIV. Snooper 1

8.2.12.5. Two 1+1 Protected Links Connected in Parallel - Three Hubs
Network
222.0.1
Network
222.0.10
SNMP
NMI 1 SNMP
NMI 2
1 2
XP4
A A
Snooper 1 Protection Protection

Switch 1 Switch 1
Network Local Remote
222.0.7 Network
222.0.2
B B
SNMP
NMI 3 SNMP
NMI 4
3 4
XP4
SNMP
NMI 10 10 Base-T
Ethernet HUB 10 Base-T
10 Ethernet HUB
XP4
NMI 5
SNMP NMI 6
SNMP
Network 5 6
222.0.6
XP4
A A
Network
Protection 222.0.8 Protection
NMI 9
SNMP Switch 2 Switch 2
9 Local Remote
B B
XP4
Network 10 Base-T
194.131.185 Ethernet HUB NMI 7
SNMP SNMP
NMI 8
7 8
Network PC2
222.0.9
PC1
Figure 8-16 : Two 1+1 Protected Links Connected in Parallel - Three Hubs
The network interfaces used in Test Configuration 26 should initially be configured via the VT100
I. SNMP 9
IP Address - 194.131.185.246
Subnet Mask - 255.255.255.0


IP Broadcast - Off
Subnet Mask - 255.255.255.0
II. SNMP 10
Subnet Mask - 255.255.255.0
IP Broadcast - On

Subnet Mask - 255.255.255.0

III. SNMP 1
Subnet Mask - 255.255.255.0
Broadcast - Off
Subnet Mask - 255.255.255.0
IV. SNMP 3
Subnet Mask - 255.255.255.0
IP Broadcast - Off
Subnet Mask - 255.255.255.0


V. SNMP 2
IP Address - 222.0.10.4
Subnet Mask - 255.255.255.0
IP Broadcast - Off
Subnet Mask - 255.255.255.0
VI. SNMP 4
IP Address - 222.0.10.5
Subnet Mask - 255.255.255.0
IP Broadcast - Off


Subnet Mask - 255.255.255.0
VII. SNMP 5
Subnet Mask - 255.255.255.0
IP Broadcast - Off
Subnet Mask - 255.255.255.0
VIII. SNMP 7
Subnet Mask - 255.255.255.0
IP Broadcast - Off


Subnet Mask - 255.255.255.0
IX. SNMP 6
IP Address - 222.0.10.1
Subnet Mask - 255.255.255.0
IP Broadcast - Off

Subnet Mask - 255.255.255.0
X. SNMP 8
IP Address - 222.0.10.2
Subnet Mask - 255.255.255.0


IP Broadcast - Off
Subnet Mask - 255.255.255.0
XI. PC1
IP Address - 194.131.185.247
Network 222.0.7 : Gateway 194.131.185.246
Network 222.0.1 : Gateway 194.131.185.246
Network 222.0.2 : Gateway 194.131.185.246
Network 222.0.3 : Gateway 194.131.185.246
Network 222.0.8 : Gateway 194.131.185.246
Network 222.0.9 : Gateway 194.131.185.246
Network 222.0.10 : Gateway 194.131.185.246
XII. PC2
IP Address - 222.0.10.3
Network 222.0.9 : Gateway 222.0.10.1
Network 222.0.7 : Gateway 222.0.10.1
Network 222.0.1 : Gateway 222.0.10.4
Network 222.0.2 : Gateway 222.0.10.4
Network 222.0.3 : Gateway 222.0.10.1
Network 222.0.6 : Gateway 222.0.10.1
Network 194.131.185 : Gateway 222.0.10.1
XIII. Snooper 1
8.2.12.6.Single 1+1 Protected Link Managed via Serial Port

SNMP 2
SNMP 1
SNMP 3 SNMP 4
Figure 8-17 : Single 1+1 Protected Link Managed via Serial Port
I. SNMP 1
Subnet Mask - 255.255.255.0
Baud Rate - 57600
Protocol - SLIP
Modem Type - None
Subnet Mask - 255.255.255.0
Baud Rate - 57600
Protocol - SLIP


Modem Type - None
Subnet Mask - 255.255.255.0
Co-located Interconnected IP Address - 222.0.4. 2
II. SNMP 3
Subnet Mask - 255.255.255.0
Baud Rate - 57600
Protocol - SLIP
Modem Type - None
Subnet Mask - 255.255.255.0
III. SNMP 2
Subnet Mask - 255.255.255.0

IP Broadcast - Off
Subnet Mask - 255.255.255.0
IV. SNMP 4
Subnet Mask - 255.255.255.0
IP Broadcast - Off
Subnet Mask - 255.255.255.0
V. PC1

VI. PC2

8.2.12.7.Two 1+1 Protected Links and Three 1+0 Links
SNMP 10
SNMP 9
SNMP 1 SNMP 2
SNMP 3 SNMP 4
SNMP 6 SNMP 5
SNMP 8 SNMP 7
SNMP 11 SNMP 12
SNMP 13 SNMP 14
Figure 8-18 : Two 1+1 Protected Links and Three 1+0 Links

I. SNMP 9
IP Address - 194.131.185.246
Subnet Mask - 255.255.255.0
IP Broadcast - Off
Subnet Mask - 255.255.255.0
II. SNMP 10
Subnet Mask - 255.255.255.0
IP Broadcast - Off
Subnet Mask - 255.255.255.0


III. SNMP 1
Subnet Mask - 255.255.255.0
IP Broadcast - Off
Subnet Mask - 255.255.255.0
IV. SNMP 3
Subnet Mask - 255.255.255.0
IP Broadcast - Off


Subnet Mask - 255.255.255.0
V. SNMP 2
Subnet Mask - 255.255.255.0
IP Broadcast - Off
Subnet Mask - 255.255.255.0
VI. SNMP 4
Subnet Mask - 255.255.255.0
IP Broadcast - Off


Subnet Mask - 255.255.255.0
VII. SNMP 5
Subnet Mask - 255.255.255.0
IP Broadcast - Off
Subnet Mask - 255.255.255.0
VIII. SNMP 7
Subnet Mask - 255.255.255.0


IP Broadcast - Off
Subnet Mask - 255.255.255.0
IX. SNMP 6
IP Address - 222.0.10.1
Subnet Mask - 255.255.255.0
IP Broadcast - On
Subnet Mask - 255.255.255.0
X. SNMP 8
IP Address - 222.0.10.2
Subnet Mask - 255.255.255.0


IP Broadcast - On
Subnet Mask - 255.255.255.0
XI. SNMP 11
IP Address - 222.0.10.3
Subnet Mask - 255.255.255.0
IP Broadcast - Off
Subnet Mask - 255.255.255.0
XII. SNMP 12


Ethernet Address - 0:9:6:7:4:c
Subnet Mask - 255.255.255.0
IP Broadcast - Off
Subnet Mask - 255.255.255.0
XIII. SNMP 13
IP Address - 222.0.10.4
Subnet Mask - 255.255.255.0
IP Broadcast - Off
IP Address - 222.0.11.1
Subnet Mask - 255.255.255.0

XIV. SNMP 14
IP Address - 222.0.11.2
Subnet Mask - 255.255.255.0
XV. PC1
IP Address - 194.131.185.247
Network 222.0.10 : Gateway 222.0.5.1
Network 222.0.11 : Gateway 222.0.5.1
XVI. PC2
IP Address - 222.0.11.2
Network 222.0.11 : Gateway 222.0.3.1
Network 222.0.10 : Gateway 222.0.3.1
Network 194.131.185 : Gateway 222.0.3.1
XVII. Snooper 1

XVIII. Snooper 2
XIX. Snooper 3
IP Address - 222.0.10.5
9. SNMP MIB Roadmap

The purpose of this section is to provide an overview of the SNMP SNMP MIB in order to make clear how
the MIB is structured at a top level and how certain actions should be sequenced in order to have the
desired effect.
The MIB is fully defined in ASN.1 format, which is suitable for loading into a MIB browser, in AD096 -
SNMP SNMP MIB.
9.1. MIB II Support
Figure 9- 1 -Top level nodes of MIB II

The diagram shown in Figure 9- 1 represents the top level nodes of MIB II
Implementation of the System group is mandatory for all systems. If an agent is not configured to have a
value for any of these variables, a string of length 0 is returned.
• sysDescr - A textual description of the entity. This value should include the full name and version
identification of the system's hardware type, software operating-system, and networking software. It is
mandatory that this only contain printable ASCII characters

• sysObjectID - The vendor's authoritative identification of the network management subsystem

contained in the entity. This value is allocated within the SMI enterprises subtree (1.3.6.1.4.1) and
provides an easy and unambiguous means for determining `what kind of box' is being managed. For
example, if vendor `Flintstones, Inc.' was assigned the subtree 1.3.6.1.4.1.4242, it could assign the
identifier 1.3.6.1.4.1.4242.1.1 to its `Fred Router'.
• sysUpTime - The time (in hundredths of a second) since the network management portion of the
system was last re-initialized."
• sysContact - The textual identification of the contact person for this managed node, together with
information on how to contact this person
• sysName - An administratively-assigned name for this managed node. By convention, this is the
node's fully-qualified domain name."
• sysLocation - The physical location of this node (e.g., `telephone closet, 3rd floor').
• sysServices - A value which indicates the set of services that this entity primarily offers.
The value is a sum. This sum initially takes the value zero, Then, for each layer, L, in the range
1 through 7, that this node performs transactions for, 2 raised to (L - 1) is added to the sum. For
example, a node which performs primarily routing functions would have a value of 4 (2^(3-1)). In
contrast, a node which is a host offering application services would have a value of 72 (2^(4-1) + 2^(7-
1)). Note that in the context of the Internet suite of protocols, values should be calculated accordingly:
layer functionality
1 physical (e.g., repeaters)
2 datalink/subnetwork (e.g., bridges)
3 internet (e.g., IP gateways)
4 end-to-end (e.g., IP hosts)
7 applications (e.g., mail relays)
For systems including OSI protocols, layers 5 and
6 may also be counted."
The IP address table contains this entity's IP addressing information.

• ipAddrTable The table of addressing information relevant to this entity's IP addresses."
• ipAddrEntry The addressing information for one of this entity's IP addresses."
• ipAdEntAddr - The IP address to which this entry's addressing information pertains.
• ipAdEntIfIndex - The index value which uniquely identifies the interface to which this entry is
applicable. The interface identified by a particular value of this index is the same interface as identified
by the same value of ifIndex.
• ipAdEntNetMask - The subnet mask associated with the IP address this entry. The value of the mask
is an IP address with all the network bits set to 1 and all the hosts bits set to 0."
• ipAdEntBcastAddr - The value of the least-significant bit in the IP broadcast address used for sending
datagrams on the (logical) interface associated with the IP address of this entry. For example, when
the Internet standard all-ones broadcast address is used, the value will be 1. This value applies both
the subnet and network broadcasts addresses used by the entity on this (logical) interface.
• ipAdEntReasmMaxSize - The size of the largest IP datagram which this entity can re-assemble from
incoming IP fragmented datagrams received on this interface.

9.2. MIB Top Level View

The diagram shown in Figure 9- 2 represents the top level nodes of the SNMP SNMP MIB.
innova xp4 radio xp4RadioStatus
xp4RadioConfig
xp4RadioPerformance
xp4RadioDiagnostics
xp4RadioProtectionSwitch
smm xp4SmmStatus
xp4SmmConfig
xp4SmmDiagnostics
xp4SmmCodeDownload
xp4SmmErrorLog
xp4SmmEventLog
systemVars xp4SystemAlarms
xp4SystemTraps
Figure 9- 2: Top level nodes of SNMP SNMP MIB
The top level nodes of the MIB can be described as follows :
• innova - This is the node under which all MIBs shall live. This node is the enterprise node with value
1965.
• xp4 - This is the node under which the MIB allowing management of the XP4 radio shall live.
• radio - This is the section of the MIB which allows management of the Local IDU, the Local ODU, the
Remote IDU and the Remote ODU.
• smm - This is the section of the MIB which allows management of the SNMP.
• systemVars - This is the section of the MIB under which lives data common to both the radio and smm
sections of MIB

Figure 9- 3: xp4RadioStatus Fields
The diagram shown in Figure 9- 3 represents the main nodes that sit below the xp4RadioStatus node of
the MIB which can be described as follows :
• xp4RadioStatusAlarmEvent - This section allows the alarm events that have been passed to the
SNMP for processing by the Local and Remote radios to be viewed.
• xp4RadioStatusRelayImages - This section allows the current status of the Local and Remote radio
relays to be viewed.
• xp4RadioIsPresent - This section provides an indication as to which of the Local IDU, Local ODU,
Remote IDU and Remote ODU have lost communications with the SNMP.
• xp4RadioStatusLogin - This section allows the local and remote radios login to be reviewed.
• xp4RadioStatusPassword - This section allows the local and remote radios password to be reviewed.
• xp4RadioStatusSummaryLEDs - This section provides an indication to the state of a particular

summary LED on a Radio.
xp4RadioStatusOtherSWPartNo -This section indicates the other Software Part Number( the
version not running) for either IDU/ODU on Local/Remote".

Figure 9- 4: xp4RadioConfig Fields

The diagram shown Figure 9- 4 represents the main nodes that sit below the xp4RadioConfig node of the
MIB which can be described as follows :
• xp4RadioConfigDeviceId - This section allows the Local and Remote Radio Device Identification
information to be viewed.
• xp4RadioConfigIdu - This section allows the Local and Remote IDU configuration parameters to be
viewed and configured.
• xp4RadioConfigOdu - This section allows the Local and Remote ODU configuration parameters to be
• xp4RadioConfigInstall - This section allows the Local and Remote Radio installation parameters to be
• xp4RadioConfigRfp - This section allows the Local and Remote Radio Frequency Plan parameters to
be viewed and configured.
• xp4RadioConfigAlarm - This section allows the Local and Remote Radio alarm relays to be mapped
and enabled, BER Warning and Alarm thresholds to be viewed and set, Rx Level thresholds to be
viewed and set and relay names viewed and set.
• xp4RadioConfigIduNames - This section allows the Local and Remote Radio IDU Names to be
• xp4RadioConfigAction - This section allows the user to login and logout of the Local IDU, save
configuration changes to the Local and Remote Radios, upload configuration from the Local and
Remote Radios.
• xp4RadioConfigTxMute - This section allows the Local and Remote Radio Transmitter to be Muted
and Un-muted.
• xp4RadioConfigSoftReboot - This section allows the activation of the Soft reboot option for the radio.
• xp4RadioConfigRadioVersion - This section indicates the code version to run for either IDU/ODU on
the Local/Remote radio when it reboots.
• xp4RadioConfigTxChannelNumber - This section indicates the current Tx Channel Number on a

Radio.
xp4RadioPerformance xp4RadioPerformanceStatisticsTable
xp4PerformanceStreamedDataTable
xp4PerformanceClearBinTable
xp4PerformancePerformanceTable
Figure 9- 5: xp4RadioPerformance Fields

The diagram shown in Figure 9- 5 represents the main nodes that sit below the xp4RadioPerformance
node of the MIB which can be described as follows:
• xp4RadioPerformanceStatisticsTable - This section allows the Performance Bin Statistics for both the
Local and Remote Radios to be viewed.
• xp4PerformanceStreamedDataTable - This section allows the Streamed Performance Data for both
Local and Remote radios to be viewed.

• xp4PerformanceClearBinTable - This section allows the Performance Bins for both the Local and
Remote radios to be cleared.
• xp4PerformancePerformanceTable - This section allows the RSL, BER and BER Mantissa for both
local and remote to be viewed.
xp4RadioDiagnostics xp4RadioConfigDiagnosticsOdu
xp4RadioConfigDiagnosticsIdu
Figure 9- 6: xp4RadioDiagnostics Fields
The diagram shown in Figure 9- 6 represents the main nodes that sit below the xp4RadioDiagnostics node
of the MIB which can be described as follows :
• xp4RadioConfigDiagnosticsOdu - This section allows diagnostic facilities on the Local ODU to be
executed.
• xp4RadioConfigDiagnosticsIdu - This section allows diagnostic facilities on the Local IDU to be

executed.
Figure 9- 7: xp4RadioProtectionSwitch
The diagram shown in Figure 9- 7 represents the main nodes that sit below the xp4RadioProtectionSwitch
of the MIB which can be described as follows :
• xp4RadioProtectionSwitchStatusTable - This section indicates the 1+1 protection switch status for the
local and remote radios.
• xp4RadioProtectionSwitchCommandTable - This section indicates the 1+1 protection switch

commands for the local radio.
Figure 9- 8: xp4SmmStatus Fields

The diagram shown in Figure 9- 8 represents the main nodes that sit below the xp4SmmStatus node of
• xp4SmmStatusResetStatus - This section allows the reason for the last reset of the SNMP to be
viewed.
• xp4SmmStatusLogin - This section indicates the VT100 logged in status for the SNMP
• xp4SmmStatusHardware - This section indicates the Hardware Type of the SNMP

Figure 9- 9: xp4SmmConfig Fields

The diagram shown in Figure 9- 9 represents the main nodes that sit below the xp4SmmConfig node of
• xp4SmmConfigPortParameters - This section allows the SNMP Serial Management Port 1, Serial
Management Port 2, Ethernet Management Port, XP4 Management Port networking parameters to be
• xp4SmmConfigSystemConfig - This section allows other general SNMP parameters to be viewed and
configured.
• xp4SmmConfigRadioStack - This section allows parameters for the radio stack to be viewed and
configured.
• xp4SmmConfigUserAccounts - This section allows user accounts to be added and deleted and user
passwords changed.
• xp4SmmConfigSoftwareVersion - This section allows the versions of software stored on the SNMP to
be viewed.
• xp4SmmConfigAction - This section allows the user to login and logout of the SNMP and to save
changes made to non-volatile memory.
• xp4SmmConfigDialOutParams - This section indicates the Dial-Out Parameters for one Serial Port
• xp4SmmConfigProtectionSwitchIPAddresses - This section allows the user to configure the IP
Address of the Inter-Connected Co-Located port and the IP Address of the Co-Located radio port
xp4SmmDiagnostics xp4SmmIntrusiveDiagnosticTestResults
xp4SmmNonIntrusiveDiagnosticTestResults
xp4SmmIntrusiveDiagnosticStart
Figure 9-10: xp4SmmDiagnostic Fields

The diagram shown in Figure 9-10 represents the main nodes that sit below the xp4SmmDiagnostics node
of the MIB which can be described as follows:

• xp4SmmIntrusiveDiagnosticsTestResults - This section allows the results of Intrusive Diagnostic Tests

to be viewed.
• xp4SmmNonIntrusiveDiagnosticsTestResults - This section allows the results of Non-Intrusive
Diagnostic Tests to be viewed.
• xp4SmmIntrusiveDiagnosticsStart - This section allows Intrusive Diagnostics to be launched.
xp4SmmCodeDownload xp4CodeDownloadDownload
xp4CodeDownloadAction
Figure 9- 11: xp4SmmCodeDownload Fields

The diagram shown in Figure 9- 11 represents the main nodes that sit below the xp4SmmCodeDownload
node of the MIB which can be described as follows:
• xp4CodeDownloadDownload - This section allows the Code Download parameters such as IP Address
and filenames to be viewed and configured.
• xp4CodeDownloadAction - This section allows the Code Download destination parameters to be

viewed and configured. Code Download is launched from here.
xp4SmmErrorLog xp4SmmErrorLogErrorLog
xp4Smm ErrorLogClear
xp4Smm ErrorLogEntryFields
xp4Smm ErrorLogEncodedSinceTimeStamp
xp4Smm ErrorLogEncoded
xp4Smm ErrorLogHowMany
xp4Smm ErrorLogFilter
Figure 9- 12: xp4SmmErrorLog Fields

The diagram shown in
Figure 9- 12 represents the main nodes that sit below the xp4SmmErrorLog node of the MIB which can be
described as follows:
• xp4SmmErrorLogErrorLog - This section allows error in the error log to be viewed with all information
for each error contained in one field.
• xp4SmmErrorLogClear - This section allows the error log to be cleared.
• xp4SmmErrorLogEntryFields - This section allows information about the errors in the error log, such as
a textual description, time stamp, error source and error code, to be viewed as individual fields.
• xp4SmmErrorLogEncodedSinceTimeStamp - This section allows the Time and Date after which
logged errors are of interest to be viewed and configured.
• xp4SmmErrorLogEncoded - This section retrieves all errors from the error log in encoded form.
• xp4SmmErrorLogHowMany - This section allows the number of errors held by the error logger to be
viewed.

• xp4SmmErrorLogFilter - This section allows the error log filter level to be viewed and configured.
xp4SmmEventLog xp4SmmE vent LogErrorLog
xp4Smm Event LogClear
xp4Smm Event LogEntryFields
xp4Smm Event LogEncodedSinceTimeStamp
xp4Smm Event LogEncoded
xp4Smm Event LogHowMany
xp4Smm Event LogFilter
Figure 9- 13: xp4SmmEventLog Fields

The diagram shown in
xp4SmmEventLog xp4SmmE vent LogErrorLog
xp4Smm Event LogClear
xp4Smm Event LogEntryFields
xp4Smm Event LogEncodedSinceTimeStamp
xp4Smm Event LogEncoded
xp4Smm Event LogHowMany
xp4Smm Event LogFilter
Figure 9- 13 represents the main nodes that sit below the xp4SmmEventLog node of the MIB which can
be described as follows:
• xp4SmmEventLogEventLog - This section allows the events in the event log to be viewed with all
information for each event contained in one field.
• xp4SmmEventLogClear - This section allows the event log to be cleared.

• xp4SmmEventLogEntryFields - This section allows information about the events in the event log, such
as a textual description, time stamp, event source and event code, to be viewed as individual fields.
• xp4SmmEventLogEncodedSinceTimeStamp - This section allows the Time and Date, after which
logged events are of interest, to be viewed and configured.
• xp4SmmEventLogEncoded - This section retrieves all events from the event log in encoded form.
• xp4SmmEventLogHowMany - This section allows the number of events held by the event logger to be
viewed.
• xp4SmmEventLogFilter - This section allows the event log filter level to be viewed and configured.

xp4SystemAlarms xp4SystemAlarmsEncodedTable
xp4 SystemAlarmsHighestSeverityTable
xp4 SystemAlarmsDataTable
xp4 SystemAlarmsFilterAlarmsTable
xp4 SystemAlarmsFilterAllAlarmsTable
Figure 9- 14: xp4SystemAlarms Fields

The diagram shown in Figure 9- 14 represents the main nodes that sit below the xp4SystemAlarms node
of the MIB which can be described as follows:
• xp4SystemAlarmsEncodedTable - This section allows all Active alarms outstanding against each
source to be viewed in an encoded format where each alarm is encoded as 10 bytes (Alarm Source,
Alarm Code, Alarm Severity, Century, Year, Month, Day, Hours, Minutes, Seconds).
• xp4SystemAlarmsHighestSeverityTable - This section allows the alarm with the Highest Severity
against each source to be viewed.
• xp4SystemAlarmsDataTable - This section allows the alarm information for each source to be viewed
as individual fields.
• xp4SystemAlarmsFilterAlarmsTable - This section allows the filtering of individual alarms against each
source to be viewed and configured.
• xp4SystemAlarmsFilterAllAlarmsTable - This section allows the filter level for all alarms to be
configured.
Figure 9- 15: xp4SystemTraps Fields

The diagram shown in Figure 9- 15 represents the main nodes that sit below the xp4SystemTraps node of
the MIB which can be described as follows:
• xp4SystemTrapsAlarmTrap - This section defines the fields that will be contained in Alarm Traps
raised against IDU, ODU and SNMP components. It does not allow traps to be viewed. It is used by
the SNMP Manager to allow it to decode incoming traps from the SNMP.
• xp4SystemTrapsPerformanceTrap - This section defines the fields that will be contained in
Performance Traps raised against IDU, ODU and SNMP components. It does not allow traps to be
viewed. It is used by the SNMP Manager to allow it to decode incoming traps from the SNMP.
• xp4SystemTrapsNodeActiveTrap - This section defines the field that will be contained in the Node
Active description. It does not allow traps to be viewed. It is used by the SNMP Manager to allow it to
decode incoming traps from the SNMP.

9.3. Accessing Radio and SNMP Data

This section outlines the sequence of events required to view and change Radio and SNMP configuration
parameters via SNMP.
9.3.1. Security Levels

The levels of security access available are the same as those used in the Radio and hence are as follows
:
• View Level
• Maintenance Level
• Administration Level
Each MIB field has a Read Security Access Level and a Write Security Access Level that corresponds to
one of the Security Levels listed above.
If an attempt is made to view an attribute whose Read Security Level is greater than the security level
with which the user is logged into the SNMP\XP4 with then an SNMP Error will be returned.
If an attempt is made to set an attribute whose Write Security Level is greater than the security level with
which the user is logged into the SNMP\XP4 with then an SNMP Error will be returned.
9.3.2. SNMP Community Names

Before any SNMP SETS are executed it must be ensured that the SNMP Community Name is set to
Private. For SNMP GETS the SNMP Community Name can be set to Public or Private.
9.4. Unified Login to the SNMP and XP4

Before logging into the SNMP\XP4 a user will have View Level access to data.
A unified login procedure can be used to gain access to Radio and SNMP Data as indicated in Figure 9-1
below.
SNMP Set:
xp4.smm.xp4SmmConfig. User
xp4SmmConfigAction.
xp4SmmConfigActionLoginSmm.0
to login for NMI and Radio Data
Access
NMI Data Radio Data
Figure 9-1 : Unified Login to access Radio and SNMP Data

Note: A Dual User system exists for access to the SNMP Data. This Dual User system allows a VT100
User and a SNMP User to be simultaneously logged into the SNMP. These two users are treated as
separate and could either be different users or the same user. If both users are different then they
could have different read/write privileges, depending on their Security Access Level.

9.4.1. SNMP User Login

Under the Unified login scheme it is not possible to login to an SNMP via SNMP without also logging into
the Radio that the SNMP is managing. Thus, a user via SNMP can just log in to the SNMP and will be
automatically logged into the Radio.
9.4.1.1.Unified Permission Levels
If the user successfully logs in to the SNMP from SNMP using the User Name and User Password system
currently implemented for the SNMP Login the user will be automatically logged in to the Radio at the
same Permission level i.e.,
SNMP View Level - View Level on the Radio
SNMP Maintenance Level - Maintenance Level on the Radio
SNMP Administrative Level - Administrative Level on the Radio
Note 1: If the User Name and Password are incorrect then the user login is rejected and a user will have
View Level access to data on the Radio and SNMP.
Note 2: If the SNMP cannot log into the radio then the User Login will be rejected i.e. both SNMP and
Radio login will be denied such that the user will have only View Level access to both SNMP and
Radio parameters.
9.4.1.2.Unified Login with No User Accounts

If there are no user accounts on the SNMP then the user will be automatically granted Administration
access (from VT100 this means Administration access to SNMP parameters and from SNMP this means
Administration access to both SNMP and Radio parameters).
Note : The existing Radio Login method, via SNMP, remains unchanged allowing Radio Login as detailed
in radio data login (Section9.5).
9.4.1.3.Example Unified Login Session

Logging into the SNMP can be achieved by performing the following steps in the
xp4.smm.xp4SmmConfig.xp4SmmConfigAction section of the MIB:
1. Perform an SNMP Get on the following MIB attribute xp4SmmConfigActionLoginRequired.0. If No is
returned then there are no user accounts on the SNMP and the user is now logged into the SNMP and
Radio with Administration access permissions. If Yes is returned then there are user accounts on the
system so the user will have to provide a user name and password, complete the following steps.
2. Perform an SNMP Set on the following MIB attribute
xp4SmmConfigActionLoginDetails.xp4SmmConfigActionLoginDetailsUserName.0 setting the value to
be a valid username.
xp4SmmConfigActionLoginDetails.xp4SmmConfigActionLoginDetailsUserPassword.0 setting the value
to be a valid user password.
4. Perform an SNMP Set on the following MIB attribute xp4SmmConfigActionLoginSmm.0. If the Login is
not successful then an SNMP Error Response will be returned, otherwise the user is now logged into
the SNMP and Radio with the access permission that corresponds to the user account entered.
To logout of the SNMP an SNMP Set should be performed on the following MIB attribute
xp4.smm.xp4SmmConfig.xp4SmmConfigAction.xp4SmmConfigActionLogout.0.
This will log the user out of both the SNMP and Radio.

9.4.2. VT100 User Login

Logging in from the VT100 will log the user into the SNMP and give the user access to SNMP parameters
only. It will NOT log the user into the Radio thus no write access to Radio parameters is granted.
9.5. Radio Data Login

In order to make any changes to a Radios configuration the user must first login to the SNMP and Local
IDU. This can be achieved by performing an SNMP Set on the following MIB attribute
xp4.xp4RadioConfig.xp4RadioConfigAction.xp4RadioConfigActionLogin.0. The value that should be
entered should correspond to the password for the level of access to the radio that is required. The
passwords that should be used are the same as the passwords that are used for XPView.
If the Login is not successful then an SNMP Error Response will be returned. If the Login is successful
then the XPView In Use LED on the Local IDU should illuminate and the user will then be granted access
to view\set data whose read\write access levels are less than or equal to the security level with which the
user has logged in with.
To logout of the radio an SNMP Set should be performed on the following MIB attribute
xp4.xp4RadioConfig.xp4RadioConfigAction.xp4RadioConfigActionLogout.0. The value that should be
entered is 0. If the logout is not successful then an SNMP Error Response will be returned. If the logout is
successful then the XPView in use LED on the Local IDU should turn off and the user will have View Level
access.
9.6. Saving Data Changes to the XP4

In order to make changes to the Local Radio configuration data the following sequence of events must be
followed (the user must already be logged in with the access level required to change the data that is to
be saved) :
Perform an SNMP Set on each of the Local Radio configuration parameters of interest.
• Perform an SNMP Set on the

xp4.xp4RadioConfig.xp4RadioConfigAction.xp4RadioConfigActionSaveTable.
xp4RadioConfigActionSaveEntry.xp4RadioConfigActionSaveConfig.0 MIB attribute with a value of 1.
This will cause each Local Radio attribute which has been changed to be saved to the Local Radio.
In order to make changes to the Remote Radio configuration data the following sequence of events must
be followed (the user must already be logged in with the access level required to change the data that is
to be saved) :
Perform an SNMP Set on each of the Remote Radio configuration parameters of interest.
• Perform an SNMP Set on the
xp4.xp4RadioConfig.xp4RadioConfigAction.xp4RadioConfigActionSaveTable.
xp4RadioConfigActionSaveEntry.xp4RadioConfigActionSaveConfig.1 MIB attribute with a value of 1.
This will cause each Remote Radio attribute which has been changed to be saved to the Remote
Radio.
9.6.1. Save Data Changes to the SNMP

In order to save any SNMP parameter changes to non-volatile memory the following sequence of events
must be followed (the user must already have logged in with the access level required to change the data
that is to be saved) :
• Perform an SNMP Set on each of the SNMP Parameters of interest.

• Perform an SNMP Set on the following MIB attribute

xp4.smm.xp4SmmConfig.xp4SmmConfigAction.xp4SmmConfigActionSaveSmmConfig.0. This will
cause any parameters changed to be saved to non-volatile memory. If the save is unsuccessful an
SNMP Error Response will be returned, otherwise the save has been successful.
9.6.2. Uploading Data from the XP4

The Local Radio data and the Remote Radio data will be uploaded automatically when the SNMP first
detects the Local IDU\ODU and Remote IDU\IDU and any time contact is lost then regained with any of
these units.
However a feature is provided via the MIB whereby Radio data can be forcibly uploaded to the SNMP.
This is achieved by performing am SNMP Set with a value of 1 on the MIB attribute
xp4.xp4RadioConfig.xp4RadioConfigAction.xp4RadioConfigActionUploadTable.
xp4RadioConfigActionUploadEntry.xp4RadioConfigActionUploadConfig.x. If x has a value 0 data will be
uploaded from the Local Radio and if it has a value 1 data will be uploaded from the Remote Radio.

9.6.3. Adding User Accounts on the SNMP

User Accounts on the SNMP can be added by performing the following steps in the
xp4.smm.xp4SmmConfig.xp4SmmConfigUserAccounts section of the MIB:
xp4SmmConfigUserAccountsDetails.xp4SmmConfigUserAccountsDetailsAddUserName.0, setting the
value to be the username of the new User Account.
xp4SmmConfigUserAccountsDetails.xp4SmmConfigUserAccountsDetailsAddUserPassword.0, setting
the value to be the password of the new User Account.
xp4SmmConfigUserAccountsDetails.xp4SmmConfigUserAccountsDetailsAddUserSecurityLevel.0,
setting the value to be the access permission of the new User Account.
4. Perform an SNMP Set on the following MIB attribute xp4SmmConfigUserAccountAddUserAccount.0,
setting the value to be 1. If the add is not successful then an SNMP Error Response will be returned,
otherwise the User Account has been added.
User Accounts on the SNMP can be deleted by performing the following step in the
xp4.smm.xp4SmmConfig.xp4SmmConfigUserAccounts section of the MIB:
xp4SmmConfigUserAccountDeleteUserAccount.0, setting the value to the username of the User
Account to be deleted. If the delete is not successful then an SNMP Error Response will be returned,
otherwise the User Account has been deleted.
9.6.4. Changing Passwords for the MIB

In order to make any changes to an SNMPs configuration the user must first login to the SNMP.
xp4SmmConfigUserPasswordDetailsOldPassword.0, setting the value to the old password.
xp4SmmConfigUserPasswordDetailsNewPassword.0, setting the value to the new password.
3. Perform an SNMP Set on the following MIB attribute xp4SmmConfigChangeUserPassword.0, If the
password change was not successful then an SNMP Error Response will be returned, otherwise the
password will have been changed.

9.6.5. Downloading new code to the SNMP and Radio

Before downloading a new version of code to the SNMP or Radio the following steps must be completed
in the xp4.smm.xp4SmmCodeDownload section of the MIB :
xp4SmmCodeDownloadDownload.xp4SmmCodeDownloadDownloadIpAddress.0, setting the value to
be the IP Address of the TFTP Server containing the new code image files.
xp4SmmCodeDownloadDownload.xp4SmmCodeDownloadDownloadSiuLoaderFileName.0, setting the
value to be the filename of the IDU Loader Code Image file on the TFTP Server.
xp4SmmCodeDownloadDownload.xp4SmmCodeDownloadDownloadAruLoaderFileName.0, setting the
value to be the filename of the ODU Loader Code Image file on the TFTP Server.
xp4SmmCodeDownloadDownload.xp4SmmCodeDownloadDownloadAruHiFileName.0, setting the
value to be the filename of the ODU High Code Image file on the TFTP Server.
xp4SmmCodeDownloadDownload.xp4SmmCodeDownloadDownloadAruLoFileName.0, setting the
value to be the filename of the ODU Low Code Image file on the TFTP Server.
xp4SmmCodeDownloadDownload.xp4SmmCodeDownloadDownloadSiuHiFileName.0, setting the
value to be the filename of the IDU High Code Image file on the TFTP Server.
xp4SmmCodeDownloadDownload.xp4SmmCodeDownloadDownloadSiuLoFileName.0, setting the
value to be the filename of the IDU Low Code Image file on the TFTP Server.
xp4SmmCodeDownloadDownload.xp4SmmCodeDownloadDownloadSNMPHiFileName.0, setting the
value to be the filename of the SNMP High Code Image file on the TFTP Server.
xp4SmmCodeDownloadDownload.xp4SmmCodeDownloadDownloadSNMPLoFileName.0, setting the
value to be the filename of the SNMP Low Code Image file on the TFTP Server.
10.Perform an SNMP Set on the following MIB attribute
xp4SmmCodeDownloadDownload.xp4SmmCodeDownloadTFTPTargetType.0, setting the value to be
the SNMP Management Port to be used for TFTP transfer i.e. Ethernet, Serial 1, Serial 2 or XP4.
To download a new version of code to the SNMP complete the following steps in the
xp4.smm.xp4SmmCodeDownload section of the MIB:
xp4SmmCodeDownloadAction.xp4SmmCodeDownloadTarget.0, setting the value to be 3
(SNMP_IMAGE).
xp4SmmCodeDownloadAction.xp4SmmCodeDownloadTFTPStart.0, setting the value to be 1.
To download a new version of code to the radio complete the following steps in the
xp4.smm.xp4SmmCodeDownload section of the MIB:


xp4SmmCodeDownloadAction.xp4SmmCodeDownloadTarget.0, setting the value to be 1 (to download
to an ODU) or 2 (to download to an IDU).
xp4SmmCodeDownloadAction.xp4SmmCodeDownloadDestination.0, setting the value to be 1 (to
download to a Local radio) or 2 (to download to a Remote radio).
xp4SmmCodeDownloadAction.xp4SmmCodeDownloadTFTPStart.0, setting the value to be 1 (to start
the newly downloaded code as soon as download is complete) or 2 (to delay the start of the newly
downloaded code until after the radio unit resets).
Performing an SNMP Get on the following MIB attribute
xp4.smm.xp4SmmCodeDownload.xp4SmmCodeDownloadDownload.xp4SmmCodeDownloadDownloadSt
atus.0 will allow the progress of the download to be monitored.

10. Reference Documents

Atlantech

Reference Documents
MA039 Product Definition Document IDU Management Module
AD073 Product Requirement Specification IDU Management

Module
AD096 SNMP SNMP MIB
Miscellaneous References
Motorola MC68360 Quad Integrated Communications Controller Users

Manual, MC68360UM/AD
Motorola MC68160 Enhanced Ethernet Transceiver Users Document,

MC68160/D
Dallas DS1305 Serial Alarm Real Time Clock (RTC), 020996
IDT IDT7130SA CMOS Dual-Port RAM 8k(1kx8) with interrupts

Users Document, DSC-2691

11. Glossary
ANS1 Abstract Syntax Notification One
CMIP Common Management Information Protocol
CMOS Complementary Metal Oxide Semiconductor
CMOT CMIP Over TCP/IP
COM Communications
CPU Central Processing Unit
CS Chip Select
CTS Clear To Send
DCD Data Carrier Detect
DCE Data Connecting Equipment
DPR Dual Port RAM
DSACK Data and Size Acknowledge
DSR Data Set Ready
DTACK Data Termination Acknowledge
DTR Data Terminal Ready
EEPROM Electrically Erasable Programmable Read Only Memory
GND Ground
HEMS High level Entity Management Systems
IDC Insulating Displacement Connector
IDT Integrated Device Technology
IDU Indoor Unit
IP Internet Protocol
IRQ Interrupt Request
MBAR Module Base Address Register
MIB Management Information Base
NETMON Network Monitoring
SNMP Network Management Interface
NMS Network Management Station
NOC Network Operating Centre
ODU Outdoor Unit
PC Personal Computer
QUICC Quad Integrated Communication Controller
RSL Receive Signal Level
RTC Real Time Clock
RTS Request To send
RXA Receive A
RXB Receive B
RXD Received Data
SCC Serial Communications Controller
SGMP Simple Gateway Monitoring Protocol
SLIP Serial Line Internet Protocol
SMC Serial Management Controller
SNMP Simple Network Monitoring Protocol
SOIC Small Outline Integrated Circuit
SPI Serial Peripheral Interface
SPISEL Serial Peripheral Interface Select
STQFP Small Thin Quad Flat Pack
TCP Transmission Control Protocol
TFTP Trivial File Transfer Protocol
TPRX Twisted Pair Receive
TPTX Twisted Pair Transmit
TSOP Thin Small Outline Package
TXA Transmit A
TXB Transmit B
TXD Transmit Data
UDP User Datagram Protocol
UTP Unshielded Twisted Pair

Appendix A - Events Logged by the Event Logger
Event Event Description

Number
0 Event Logger has wrapped
1 User Session Aborted
2 Alarm Cleared; Src alarmSource
Sev alarmSev Type alarmType
3 Alarm Declared; Src alarmSource
Sev alarmSev Type alarmType
4 Local ODU config upload successful
5 Local IDU config upload successful
6 Remote ODU config upload successful
7 Remote IDU config upload successful
8 Local ODU config upload failed
9 Local IDU config upload failed
10 Remote ODU config upload failed
11 Remote IDU config upload failed
12 Local Radio config download successful
14 Remote Radio config download successful
16 Local Radio config download failed
18 Remote Radio config download failed
20 Local ODU detected, config uploaded
21 Local IDU detected, config uploaded
22 Remote ODU detected, config uploaded
23 Remote IDU detected, config uploaded
24 Local ODU detected, config upload failed
25 Local IDU detected, config upload failed
26 Remote ODU detected, config upload failed
27 Remote IDU detected, config upload failed
28 Local ODU not responding
29 Local IDU not responding
30 Remote ODU not responding
31 Remote IDU not responding
32 System Time Changed
33 User username logged in
34 User username logged out
37 ODU Code Images transferred to SNMP
38 ODU Code Image transfer to SNMP failed
39 IDU Code Images transferred to SNMP
40 IDU Code Image transfer to SNMP failed
41 Local ODU successfully reprogrammed
42 Local ODU failed to be reprogrammed
43 Local IDU successfully reprogrammed
44 Local IDU failed to be reprogrammed
45 Remote ODU successfully reprogrammed
46 Remote ODU failed to be reprogrammed

47 Remote IDU successfully reprogrammed

48 Remote IDU failed to be reprogrammed
50 Ethernet Net Device initialised
51 Failed to Init Ethernet Net Device
52 Serial 1 Net Device initialised
53 Failed to Init Serial 1 Net Device
54 Serial 2 Net Device initialised
55 Failed to Init Serial 2 Net Device
56 XP4 Net Device initialised
57 Failed to Init XP4 Net Device
58 Ethernet Net Device Route initialised
59 Failed to init Ethernet Net Device route
60 Serial 1 Net Device Route initialised
61 Failed to init Serial 1 Net Device route
62 Serial 2 Net Device Route initialised
63 Failed to init Serial 2 Net Device route
64 XP4 Net Device Route initialised
65 Failed to init XP4 Net Device route
66 binType Performance Bin binNumber
67 Alarm alarmType, Src alarmSource deactivated by
filter
68 Alarm alarmType, Src alarmSource activated by
filter
69 username logged into radio
70 username failed to log into radio
71 Logged out of radio
72 Failed to logout of radio
73 SNMP Passed Intrusive Diagnostics
74 SNMP Failed Intrusive Diagnostics
75 User Account Added
76 User Account Deleted

Appendix B - Errors Logged by the Error Logger
Severity Error Summary Text Error Code Extended Error Text (Max
(Max Length 32) Length 79)
Minor Message Manager 0 Transit Timer Expired - re-
sending solicited message.
Major Tx Message Progress 1 Solicited Message re-transmit
Monitor count exceeds retry limit.
Minor Message Manager 2 No originating partner found for
solicited message.
Minor Tx Message Progress 3 Garbage collection carried out
Monitor on Tx Progress Monitor.
Minor Stack Packet Assembler 4 Packet header error.
Minor Message Manager 5 Received Message has failed
Message CRC check.
Minor Message Manager 6 Received Message has failed
Header CRC check.
Major Message Manager 7 Radio sending message which
exceeds MAX message size.
Minor Code Download 8 TFTP Get Failed
Manager
Minor Code Download 9 Failed to transfer Image Data to
Manager Radio
Major Code Download 10 Failed to program SNMP Image
Manager Data to Flash Memory
Reserved For 11
future use
Reserved For 12
future use
Reserved For 13
future use
Reserved For 14
future use
Minor RTC Driver 15 Invalid RTC values
Major RTC Driver 16 Write Failure
Critical Main 17 System failed to initialise.
Critical Radio Comms Stack 18 Radio Stack not sending Radio
Transmit Messages.
Major Radio Comms Stack 19 Radio Stack not processing
Receive Dual port RAM packets.
Major Local Radio 20 x Performance Messages
Performance Monitor received from Radio in a 15
minute period (where x is
greater than 15)
Major Remote Radio 21 x Performance Messages
Performance Monitor received from Radio in a 15
minute period (where x is
greater than 15)
Critical Local Radio 22 15 Min Performance Bin no
Performance Monitor allocated from heap.
Critical Remote Radio 23 15 Min Performance Bin no
Performance Monitor allocated from heap.
Critical Local Radio 24 24 hr Performance Bin not
Performance Manager allocated from heap.

Critical Remote Radio 25 24 hr Performance Bin not

Performance Manager allocated form heap.
Reserved For 26
future use
Reserved For 27
future use
Major Local Radio Bin 28 Bin Id selected exceeds
Collection maximum bin number
Major Remote Radio Bin 29 Bin Id selected exceeds
Collection maximum bin number
Major Local Radio 30 At least one message received
Performance Monitor but no reference frame count.
Major Remote Radio 31 At least one message received
Performance Monitor but no reference frame count.
Major Alarm Collection 32 Failed to ADD an Alarm
Major Alarm Collection 33 Failed to REMOVE and Alarm
Major Alarm Collection 34 Failed to GET an Alarm
Major Alarm Manager 35 Failed to process an Alarm
Major Alarm Manager 36 Failed to filter an Alarm
Major Alarm Manager 37 Failed to filter ALL Alarms
Minor Logger Has Wrapped 38 Amount of errors entered is
greater than logger size.
Major Serial Manager 39 Trap not sent: Failed to
establish link
Major Trap Manager 40 Performance Trap not sent :
Serial Port 1 trap queue has
reached the maximum
Serial Port 2 trap queue has
reached the maximum
Major Serial Manager 42 Failed to dial out at daily update
time : Failed to establish link
Major Trap Manager 43 Alarm Trap not sent : Serial Port
1 trap queue has reached the
maximum
Major Trap Manager 44 Alarm Trap not sent : Serial
Port 2 trap queue has reached
the maximum
Major Trap Manager 45 Alarm Trap not sent : Normal
trap queue has reached the
maximum
Normal trap queue has reached
the maximum

Appendix C – Alarms
Alarm Alarm type Description Alarm Alarm Source

Type Type
Code severity
1 Failed Self Test Major Local Radio IDU, Remote Radio IDU
2 Link ID Wrong Major Local Radio IDU, Remote Radio IDU
3 Tributary 1 Fault Major Local Radio IDU, Remote Radio IDU
11 Bit Error Rate Exceeded Major Local Radio IDU, Remote Radio IDU
warning Threshold
12 Bit Error Rate Exceeded Major Local Radio IDU, Remote Radio IDU
alarm Threshold
13 Local Auxiliary Input Alarm Major Local Radio IDU, Remote Radio IDU
14 Remote Auxiliary Input Alarm Major Local Radio IDU, Remote Radio IDU
15 Hardware Failure Major Local Radio IDU, Remote Radio IDU
16 Frame Loss Major Local Radio IDU, Remote Radio IDU
17 Tx Frequency Lock Major Local Radio ODU, Remote Radio ODU
18 Tx Power Fail Major Local Radio ODU, Remote Radio ODU
19 Rx Frequency Lock Major Local Radio ODU, Remote Radio ODU
20 Receive Signal Level alarm Major Local Radio ODU, Remote Radio ODU
21 G821 Errored Seconds \ Minor Local Radio, Remote Radio
Hour Threshold Exceeded
22 G821 Errored Seconds \ Day Minor Local Radio, Remote Radio
Threshold Exceeded
23 G821 Severely Errored Minor Local Radio, Remote Radio
Seconds \ Hour Threshold
Exceeded
Seconds \ Day Threshold
Exceeded
25 G826 Errored Seconds \ Minor Local Radio, Remote Radio
Hour Threshold Exceeded
26 G826 Errored Seconds \ Day Minor Local Radio, Remote Radio
Threshold Exceeded
Seconds \ Hour Threshold
Exceeded
Seconds \ Day Threshold
Exceeded
29 More than 5 Major Alarms critical SNMP

Appendix D - Modem Configuration
A Modem connected to a serial port on the SNMP will be automatically initialised correctly if the
serial port is configured for Dial-Out. If the port is not configured for Dial-Out it is recommended
that both the Modem attached to the SNMP and the Remote Modem are configured with the
following parameters. This parameters detailed below should allow correct operation for the
Robotics and Motorola Modems. If any other type of Modem is used then the relevant
Manufacturer's user guide should be used.
It is assumed that the User has read the Manufacturer's Installation and Trouble Shooting guide
and is familiar with the Modem command set used, before attempting to configure the Modem.
Robotics Modem Configuration
The type of Modem supported is the US Robotics Sportster Voice 33600 Fax Modem.
The following parameters should be set :
E0 - Local Echo OFF
Q0 - Displays Result Codes
V1 - Result Codes are Verbal
&A0 - ARQ Result Codes are Disabled
0=2 - Auto Answer will answer after 2 rings
S7=60 - Sets the number of seconds (60) the Modem waits for a carrier before returning No
Carrier indication
F1 - Local Data Echo OFF
X4 - All Result Codes will be used
Y0 - Set power-on default configuration to profile 0 in NVRAM
&H0 - Flow Control Disabled
&I0 - Software Flow Control Disabled
&N0 - Combined with &U0 to allow Modem and Remote Modem
&U0 - to connect at best possible speed
&B1 - Fixed Serial Port rate
&D0 - DTR Override
Once the above parameters are set they can be saved to NVRAM profile 0 using the AT&W0
command. To check the Modem configuration, use the command ATI4 and the following should
be displayed:
B0 E0 F1 M1 Q0 V1 X4 Y0
SPEED=19200 PARITY=N WORDLEN=8
DIAL=TONE OFF LINE
&A0 &B1 &C1 &D0 &H0 &I0 &K1
&M4 &N0 &R1 &S0 &T5 &U0 &Y1
S00=002 S01=000 S02=043 S03=013 S04=010 S05=008 S06=004
S07=060 S08=002 S09=006 S10=014 S11=070 S12=050 S13=000
S15=000 S16=000 S18=000 S19=000 S21=010 S22=017 S23=019
S25=005 S27=001 S28=008 S29=020 S30=000 S31=128 S32=002
S33=000 S34=000 S36=014 S38=000 S39=011 S40=000 S41=000
S42=000
LAST DIALLED £:
Using the ATZ0 command will force the Modem to use the above configuration (stored in profile
0 on NVRAM) when it is powered-up/reset.

Motorola Modem Configuration

The type of Modem supported is the Motorola Modem SURFR 56K Modem.
The following parameters should be set :
E0 - Command Echo OFF
Q0 - Allow response messages to the computer
V1 - Report Response messages as words
W2 - Report modem to modem speed in error correction mode
S0=2 - Auto Answer will answer after 2 rings
S7=60 - Sets the number of seconds (60) the Modem waits for a carrier before returning No
Carrier indication
X1 - Report basic call progress result codes and connection speeds
N0 - Turn Off automode detection
&D0 - The Modem ignores DTR
&K0 - Disable computer/modem flow control
&S0 - DSR always active
&R1 - CTS always active
s202=32 - Used to make the 56K V1.009 Software work better
\N0 - Select normal buffered mode (no error correction)
+MS=11,0,9600,33600 - Turn off 56K feature and limit modem connection speed to between
9600 and 33600 baud
Once the above parameters are set they can be saved to NVRAM profile 0 using the AT&W0
command.
To check the Modem configuration, use the command AT&V and the following should be
displayed:
ACTIVE PROFILE:
B0 E0 L0 M1 N0 Q0 T V1 W2 X1 Y0 &C1 &D0 &G0 &J0 &K0 &Q6 &R1 &S0 &T4 &X0 &Y0
S00:002 S01:000 S02:043 S03:013 S04:010 S05:008 S06:005 S07:060 S08:002 S09:006
S10:014 S11:095 S12:050 S18:000 S25:005 S26:001 S36:007 S37:000 S38:020 S44:020
S46:138 S48:007 S95:000
STORED PROFILE 0:
B0 E0 L0 M1 N0 Q0 T V1 W2 X1 Y0 &C1 &D0 &G0 &J0 &K0 &Q6 &R1 &S0 &T4 &X0
S00:002 S02:043 S06:005 S07:060 S08:002 S09:006 S10:014 S11:095 S12:050 S18:000
S36:007 S37:000 S40:104 S41:195 S46:138 S95:000
STORED PROFILE 1:
B0 E1 L1 M1 N1 Q0 T V1 W0 X4 Y0 &C1 &D2 &G0 &J0 &K3 &Q5 &R1 &S0 &T5 &X0
S00:002 S02:043 S06:005 S07:050 S08:002 S09:006 S10:014 S11:095 S12:050 S18:000
S36:007 S37:000 S40:168 S41:195 S46:138 S95:000
TELEPHONE NUMBERS:
0= 1=
2=
Using the AT&Y0 command will force the Modem to use the above configuration (stored in
profile 0 on NVRAM) when it is powered-up/reset. The command ATZ0 will force the Modem to
use profile 0 on a warm reset.
Note: Even though the above profile will be used the +ms=11,0,9600,33600 is not stored so
therefore must be re-entered if the Modem is re-powered/reset

Appendix E - G.821 & G.826 Performance Monitoring Parameters
G.821 ES The G.821 Errored Seconds count is based on the Error Rate.
A second is errored if the Error Rate is above zero.
G.821 SES The G.821 Severely Errored Seconds count is based on the
Error Rate. A second is severely errored if the Error Rate is
above 1x10E-3.
G.821 Degraded Minutes A minute is degraded if the number of Errored Seconds in a

group of 60 Available Seconds (which are not Severely
Errored) is greater than four
G.821 Available Seconds This is the number of seconds where the consecutive
G.821Severely Errored Seconds count has not been 10 or
more. (i.e. Transition to Unavailable Time requires 10
consecutive G.821 SES)
G821 Unavailable Seconds This is the number of seconds where the consecutive G. Non-
Severely Errored Seconds count has not been 10 or more.
(i.e. transition to Available Time requires 10 consecutive
G.821Non-SES). In Unavailable Time, neither ES, SES or
Degraded Minutes are counted.
G.826 Block Errors A G.826 Block Error is defined as a block in which one or
more bits are in errored. The G.826 standard is based on
Block Errors.
G.826 ES The G.826 Errored Seconds count is based on the Block
Errors. A second is errored if it has one or more errored
blocks.
G.826 ESR The G.826 Errored Seconds Ratio is a ratio of the ES count
to total seconds in available time over a fixed measurement
interval.
G.826 SES The G.826 Severely Errored Seconds count is based on the
Block Errors. A second is severely errored if it has greater
than or equal to 30% errored blocks or it has a Loss of Signal
or Loss of Frame indicated against it.
G.826 SESR The G.826 Severely Errored Seconds Ratio is a ratio of the
SES count to total seconds in available time over a fixed
measurement interval.
G.826 BBE The G.826 Background Block Error count is the number of
block errors that have occurred but not as part of a Severely
Errored Second.
G.826 BBER The G.826 Background Block Error Ratio is the ratio of
errored blocks to total blocks during a fixed measurement
interval, excluding all blocks during SES and unavailable
time.
G.826 Available Seconds This is the number of seconds where the consecutive G.
Severely Errored Seconds count has not been 10 or more.
(i.e. Transition to Unavailable Time requires 10 consecutive
G.826 SES)
G.826 Unavailable Seconds This is the number of seconds where the consecutive G.826
Non-Severely Errored Seconds count has not been 10 or
more.(i.e. transition to Available Time requires 10
consecutive G.826 Non-SES).In Unavailable Time, neither
ES, SES or BBE are counted.

Appendix F - SNMP Attributes Change Implementation
The table below shows when each SNMP attributes’ value takes effect once modified, i.e. as
soon as the attribute is modified or only after the SNMP has been reset. The attribute names
listed below are as shown in the VT100 screens.
SNMP Attribute Name Takes Effect Default Values

:-
Event Logger
Event Filter Immediately PM Events Disabled
Event Logger
Error Severity Filter Level Immediately Minor (i.e. all events enabled)
Code Download
TFTP Server IP Address Immediately 0.0.0.0
TFTP Target Port Immediately Ethernet
SNMP High Image Immediately SNMPhi.bin
Filename
SNMP Low Image Filename Immediately SNMPlo.bin
IDU Loader Filename Immediately idudnld.dwn
ODU Loader Filename Immediately odudnld.dwn
IDU High Image Filename Immediately high.idu
IDU Low Image Filename Immediately low.idu
ODU High Image Filename Immediately high.odu
ODU Low Image Filename Immediately low.odu
TFTP Inter Packet Time- Immediately 5 seconds
Out
Ethernet Management
Port
Ethernet Address Read-Only Factory Programmable
Gateway IP Address After Reset 0.0.0.0
Default Router IP Address After Reset 0.0.0.0
Default Router Subnet Mask After Reset 0.0.0.0
IP Address After Reset 0.0.0.0
Subnet Mask After Reset 0.0.0.0
Trap Destination 1 IP After Reset 0.0.0.0
Address
Address
Address
Trap Generation After Reset Disabled
Ethernet Connector Type After Reset Twisted Pair
Booted Indicator After Reset Not Booted
Broadcast Status After Reset Disabled
PM Trap Generation Immediately All PM Bins
Serial Management
Port 1 & 2

Address
Address
Address
Baud Rate After Reset 57600
Interface Type After Reset RS232
Protocol After Reset SLIP
Modem Type After Reset None
Robotics User String Immediately ATF1X4Y0&H0&I0&N0&U0&B
1&D0
Motorola User String Immediately ATX1N0&D0&K0&S0&R1S202
=32\N0+MS=11,0,9600,33600
Dialling Prefix A Immediately NULL String
Dialling Prefix B Immediately NULL String
Modem Command Retries Immediately 3
Modem Command Timeout Immediately 30 seconds
Alarm Trap Generation Immediately All alarms
Daily Update Immediately No
Daily Update Time Immediately 00:00
Password Authentication Immediately No
Authentication String Immediately NULL String
Authentication Retries Immediately 1
Authentication Timeout Immediately 10 seconds
User Name Immediately NULL String
User Password Immediately NULL String
Modem Connection Timeout Immediately 5 seconds
Protocol Retries Immediately 1
Protocol Timeout Immediately 30 seconds
IP Routing Immediately No
XP4 Management
Port
Address
Address
Address
General
System Name Immediately <unnamed>
Auto Logout Time Immediately 120 minutes
Time Immediately N/A
Date Immediately N/A

Hardware Type Read-Only Factory Programmable

Hardware Version Read-Only Factory Programmable
Performance Alarm
Thresholds
G821 Errored Seconds/Hour Immediately 20
G821 Errored Seconds/Day Immediately 200
G821 Severely Errored Immediately 10
Seconds/Hour
Seconds/Day
G826 Errored Seconds/Hour Immediately 25
G826 Errored Seconds/Day Immediately 250
Seconds/Hour
Seconds/Day
Radio Stack
Transmit Monitor Timer After Reset 2000 milliseconds
Maximum Transmit Retries After Reset 3
Co-Located IP
Addresses
Inter Connected IP Address After Reset 0.0.0.0
Co-Located Radio Port IP After Reset 0.0.0.0
Address
Node Active Trap
Node Active Trap Immediately No
Generation
Node Active Trap Time Immediately 00:00
MIB 2 System Table
System Description Read-Only XP Series
System Object Id Read-Only 1.3.6.1.4.1.1965.1
System Up Time Read-Only N/A
System Contact Immediately Customer Service
System Name Immediately Innova
System Location Immediately Seattle
System Services Read-Only 76

Appendix G - Attributes and their security levels
Attributes Read Write

Access Access
Level Level
xp4SmmStatusResetStatusExt VIEW N/A
External total system reset.
xp4SmmStatusResetStatusPow VIEW N/A
Power up reset.
xp4SmmStatusResetStatusSw VIEW N/A
Software watchdog reset.
xp4SmmStatusResetStatusDbf VIEW N/A
Double bus fault.
xp4SmmStatusResetStatusLoc VIEW N/A
Loss of clock reset.
xp4SmmStatusResetStatusSrst VIEW N/A
Soft reset.
xp4SmmStatusResetStatusSrstp VIEW N/A
Soft reset pin.
xp4SmmStatusLoginSmmVt100LoggedIn VIEW N/A
VT100 logged in status for SNMP.
xp4SmmStatusLoginSmmVt100UserName VIEW N/A
VT100 logged in users login name.
xp4SmmStatusLoginSmmVt100UserLevel VIEW N/A
VT100 logged in users login level.
xp4SmmStatusLoginSmmSNMPLoggedIn VIEW N/A
SNMP logged in status for SNMP.
xp4SmmStatusLoginSmmSNMPUserName VIEW N/A
SNMP logged in users login name.
xp4SmmStatusLoginSmmSNMPUserLevel VIEW N/A
SNMP logged in users login level.
xp4SmmStatusHardwareType VIEW N/A
The Hardware Type of the SNMP.
xp4SmmStatusHardwareVersion VIEW N/A
The Hardware version of the SNMP.
xp4SmmConfigPortParametersEthernetAddress VIEW N/A
The Ethernet Address of the Port (if applicable).
xp4SmmConfigPortParametersDefaultEthernetAddress VIEW Maintenance
The Default Ethernet Address of the Port (if applicable).
xp4SmmConfigPortParametersDefaultRouterIpAddress VIEW Maintenance
The Default Router IP Address of the Port.
xp4SmmConfigPortParametersDefaultRouterSubnetMask VIEW Maintenance
The Default Router Subnet Mask of the Port.
xp4SmmConfigPortParametersIpAddress VIEW Maintenance
The IP Address of the Port.
xp4SmmConfigPortParametersSubnetMask VIEW Maintenance
The Subnet Mask of the Port.
xp4SmmConfigPortParametersTrapDestinationIpAddress VIEW Maintenance
The Trap Destination IP Address of the Port.
xp4SmmConfigPortParametersTrapGeneration VIEW Maintenance
The Interface Type of the Port.
xp4SmmConfigPortParametersBaudRate VIEW Maintenance
The Baud Rate of the Port.
xp4SmmConfigPortParametersInterfaceType VIEW Maintenance

The Interface Type of the Port.

xp4SmmConfigPortParametersBootedIndicator VIEW Maintenance
Indicates whether the Port is to be booted or not.
xp4SmmConfigPortParametersProtocol VIEW Maintenance
The Protocol to be used over the Port.
xp4SmmConfigPortParametersModemType VIEW Maintenance
The type of Modem connected.
xp4SmmConfigPortParametersEthernetConnectionType VIEW Maintenance
The type of connection for Ethernet.
xp4SmmConfigPortParametersPMTrapGeneration VIEW Maintenance
Indicates what PM Bins will generate traps on this port.
xp4SmmConfigPortParametersGatewayIpAddress VIEW Maintenance
The Gateway IP Address of the Gateway (if applicable).
xp4SmmConfigPortParametersIpBroadcast VIEW Maintenance
Indicates whether the SNMP is utilising IP broadcast.
xp4SmmConfigPortParametersTrapDstinationIpAddress2 VIEW Maintenance
xp4SmmConfigPortParametersTrapDstnationIpAddress3 VIEW Maintenance
xp4SmmConfigSystemConfigSystemName VIEW Maintenance
The name of the System.
xp4SmmConfigSystemConfigESHourG821 VIEW Maintenance
The Errored Seconds per Hour threshold.
xp4SmmConfigSystemConfigESDayG821 VIEW Maintenance
The Errored Seconds per Day threshold.
xp4SmmConfigSystemConfigSESHourG821 VIEW Maintenance
The Severely Errored Seconds per Hour threshold.
xp4SmmConfigSystemConfigSESDayG821 VIEW Maintenance
The Severely Errored Seconds per Day threshold.
xp4SmmConfigSystemConfigESHourG826 VIEW Maintenance
The Errored Seconds per Hour threshold.
xp4SmmConfigSystemConfigESDayG826 VIEW Maintenance
The Errored Seconds per Day threshold.
xp4SmmConfigSystemConfigSESHourG826 VIEW Maintenance
The Severely Errored Seconds per Hour threshold.
xp4SmmConfigSystemConfigSESDayG826 VIEW Maintenance
The Severely Errored Seconds per Day threshold.
xp4SmmConfigSystemConfigAutoLogout VIEW Maintenance
Indicates whether Auto Logout is disabled i.e. value = 0, or the
actual logout time i.e. > 0.
xp4SmmConfigSystemConfigSystemDate VIEW Maintenance
Format: day/month/year e.g., 25/12/1996.
xp4SmmConfigSystemConfigSystemTime VIEW Maintenance
Format: hr.min.sec e.g., 13.23.00.
xp4SmmConfigSystemConfigNodeActiveTrap VIEW Maintenance
Do we send a <Node Active Trap> due at Node Active Trap
Time.
xp4SmmConfigSystemConfigNodeActiveTrapTime VIEW Maintenance
The Daily Time for sending a <Node Active Trap>.
xp4SmmConfigRadioStackConfigMaxRetries VIEW Maintenance
Number of retries for a Xp4 message.
xp4SmmConfigRadioStackConfigMonitorTimer VIEW Maintenance
Timer value for message retry.
xp4SmmConfigUserAccountsUserNames VIEW N/A

Account holders name.

xp4SmmConfigUserAccountsUserPasswords Administratio N/A
Account holders password. n
xp4SmmConfigUserAccountsUserSecurityLevel VIEW N/A
Security Level.
xp4SmmConfigUserAccountsDetailsAddUserName VIEW Administratio
User's name. n
xp4SmmConfigUserAccountsDetailsddUserPassword VIEW Administratio
User's password. n
xp4SmmConfigUserAccountsDetailsAddUserSecurityLevel VIEW Administratio
User's security level. n
xp4SmmConfigAccountAddUserAccount VIEW Administratio
Add user using previously set user name, user password and n
user security level.
xp4SmmConfigAccountDeleteUserAccount VIEW Administratio
User's name for deletion from user accounts. n
xp4SmmConfigUserPasswordDetailsOldPassword VIEW VIEW
User's old Password.
xp4SmmConfigUserPasswordDetailsNewPassword VIEW VIEW
User's new password.
xp4SmmConfigChangeUserPassword VIEW VIEW
Change user's password after previously setting old password
and new password attributes.
xp4SmmConfigSoftwareVersionPrimary VIEW N/A
Primary Software version.
xp4SmmConfigSoftwareVersionSecondary VIEW N/A
Secondary Software version.
xp4SmmConfigSoftwareVersionBootCode VIEW N/A
Boot Code Version.
xp4SmmConfigActionLoginRequired VIEW N/A
Indicates whether SNMP login is required.
xp4SmmConfigActionLoginDetailsUserName VIEW VIEW
User's name for log in.
xp4SmmConfigActionLoginDetailsUserPassword VIEW VIEW
User's password for log in.
xp4SmmConfigActionLoginSmm VIEW VIEW
Login into SNMP.
xp4SmmConfigActionLogout VIEW VIEW
Log out of SNMP.
xp4SmmConfigActionSaveSmmConfig VIEW VIEW
Save any values changed to flash or serial eeprom.
xp4SmmConfigActionSmmReset VIEW Administratio
Resets SNMP card. This takes around 60 seconds to complete. n
xp4SmmConfigDialOutParamsDiallingPrefixA VIEW Maintenance
Dialling Prefix A for Modem Dial-Out.
xp4SmmConfigDialOutParamsDiallingPrefixB VIEW Maintenance
Dialling Prefix B for Modem Dial-Out.
xp4SmmConfigDialOutParamsNumberOfModemCommandRetri VIEW Maintenance
es
The Number of Times a Modem Command will be retried.
xp4SmmConfigDialOutParamsAlarmTrapGeneration VIEW Maintenance
Indicates what Alarms will generate traps.
xp4SmmConfigDialOutParamsDailyUpdate VIEW Maintenance
Do we Dial-Out due at the daily update time.

xp4SmmConfigDialOutParamsDailyUpdateTime VIEW Maintenance

The Daily Update Time.
xp4SmmConfigDialOutParamsPasswordAuthentication VIEW Maintenance
Do we need to be authenticated before sending the Trap.
xp4SmmConfigDialOutParamsAuthenticationString VIEW Maintenance
The String expected back for Authentication.
xp4SmmConfigDialOutParamsUserName VIEW Maintenance
The User Name used as part of Authentication.
xp4SmmConfigDialOutParamsUserPassword VIEW Maintenance
The User Password used as part of Authentication.
xp4SmmConfigDialOutParamsModemConnectionTimeout VIEW Maintenance
The number of seconds the Modem connection will be held.
xp4SmmConfigDialOutParamsNumberOfProtocolRetries VIEW Maintenance
The number of retries for Protocol establishment.
xp4SmmConfigDialOutParamsProtocolTimeout VIEW Maintenance
The timeout, in seconds, for each attempt at Protocol
establishment.
xp4SmmConfigDialOutParamsNumberOfAuthenticationRetries VIEW Maintenance
The number of retries for Authentication.
xp4SmmConfigDialOutParamsAuthenticationTimeout VIEW Maintenance
The timeout, in seconds, for each attempt at Authentication.
xp4SmmConfigDialOutParamsModemCommandTimeout VIEW Maintenance
The timeout, in seconds, for each Modem Command.
xp4SmmConfigDialOutParamsMotorolaDefaultCommandString VIEW N/A
Default AT command string for Motorola modem.
xp4SmmConfigDialOutParamsMotorolaUserCommandStringUse VIEW Maintenance
r
AT command string for Motorola modem.
xp4SmmConfigDialOutParamsRoboticsDefaultCommandString VIEW N/A
Default AT command string for Robotics modem.
xp4SmmConfigDialOutParamsRoboticsUserCommandString VIEW Maintenance
User AT command string for Robotics modem.
xp4SmmConfigDialOutParamsRestoreMotorolaDefaultCmdStrin N/A Maintenance
g
Restore the Default AT command string for Motorola modem i.e.
copy it to the User String.
xp4SmmConfigDialOutParamsRestoreRoboticsDefaultCmdStrin N/A Maintenance
g
Restore the Default AT command string for Robotics modem i.e.
Copy it to the User String.
xp4SmmConfigDialOutParamsIpRouting VIEW Maintenance
Select whether routed IP messages result in dial out
procedure being instigated.
xp4SmmConfigProtectionSwitchIPAddressesInterconnectedPort VIEW Maintenance
The IP Address of the Inter-Connected Co-Located Port
xp4SmmConfigProtectionSwitchIPAddressesCoLocatedRadioPo VIEW Maintenance
rt
The IP Address of the Co-Located Radio Port
xp4SmmIntrusiveDiagnosticsTestRes VIEW N/A
Intrusive Diagnostic Result alternatives.
xp4SmmIntrusiveDiagnosticsTestFailureReasen VIEW N/A
Intrusive Diagnostic result descriptions.
xp4SmmNonIntrusiveDiagnosticsTestRes VIEW N/A
Non Intrusive Diagnostic Result alternatives.

xp4SmmNonIntrusiveDiagnosticsTestFail VIEW N/A

Non Intrusive Diagnostic result descriptions.
xp4SmmIntrusiveDiagnosticsStart VIEW Administratio
Starts the intrusive diagnostic task. n
xp4SmmCodeDownLoadDownLoadIpAddress VIEW Administratio
TFTP Server IP Address. n
xp4SmmCodeDownLoadDownLoadSiuLoaderFileName VIEW Administratio
SIU Loader File Name. n
xp4SmmCodeDownLoadDownLoadAruLoaderFileName VIEW Administratio
ARU Loader File Name. n
xp4SmmCodeDownLoadDownLoadAruHiFileName VIEW Administratio
ARU High File Name. n
xp4SmmCodeDownLoadDownLoadAruLoFileName VIEW Administratio
ARU Low File Name. n
xp4SmmCodeDownLoadDownLoadSiuHiFileName VIEW Administratio
SIU High File Name. n
xp4SmmCodeDownLoadDownLoadSiuLoFileName VIEW Administratio
SIU Low File Name. n
xp4SmmCodeDownLoadDownLoadSNMPHiFileName VIEW Administratio
SNMP High File Name. n
xp4SmmCodeDownLoadDownLoadSNMPLoFileName VIEW Administratio
SNMP Low File Name. n
xp4SmmCodeDownLoadDownLoadStatus VIEW N/A
Down load status.
xp4SmmCodeDownloadTFTPInterPacketDelay VIEW Administratio
The Delay between Packet requests. n
xp4SmmCodeDownloadTFTPTargetType VIEW Administratio
Target port for TFTP. n
xp4SmmCodeDownloadTarget N/A Administratio
Identifies target for code download. n
xp4SmmCodeDownloadDestination N/A Administratio
Indicates local or remote radio. n
xp4SmmCodeDownloadTFTPStart N/A Administratio
Initiates TFTP Code Download using parameters for n
target(SNMP,SIU,ARU) and destination(LOCAL and REMOTE).
xp4SmmErrorLogError VIEW N/A
String representation of error.
xp4SmmErrorLogClearErrorLog VIEW Administratio
Clears the Error Log. n
xp4SmmErrorLogEntrySummaryTextField VIEW N/A
Displays the summary text field of an error log entry.
xp4SmmErrorLogEntrySourceTextField VIEW N/A
Displays the source text field of an error log entry.
xp4SmmErrorLogEntryTimeStamp VIEW N/A
Displays the time stamp field of an error log entry.
xp4SmmErrorLogEntryTaskID VIEW N/A
Displays the task Id field of an error log entry.
xp4SmmErrorLogEntrySeverity VIEW N/A
Displays the severity field of an error log entry.
xp4SmmErrorLogEntryErrorCode VIEW N/A
Displays the error code field of an error log entry.
xp4SmmErrorLogEncodedSinceTimeStampDate VIEW VIEW
date after which encoded errors are of interest. Format:
day/month/year e.g., 25/12/1996.

xp4SmmErrorLogEncodedSinceTimeStampTime VIEW VIEW

Time after which encoded errors are of interest. Format:
hr.min.sec e.g., 13.23.00
xp4SmmErrorLogEncodedSinceTimeStampAllEncodedErrors VIEW N/A
Retrieves all errors, in encoded form, since a specified time and
date.
xp4SmmErrorLogEncodedAllEncodedErrors VIEW N/A
Retrieves all errors in encoded form from error logger.
xp4SmmErrorLogHowManyErrors VIEW N/A
Counts how many errors are held by error logger.
xp4SmmErrorLogFilterError VIEW Maintenance
Sets error log filter level.
xp4SmmEventLogEvent VIEW N/A
String representation of event.
xp4SmmEventLogClearEventLog VIEW Administratio
Clears the Event Log. n
xp4SmmEventLogEntryTextualDescription VIEW N/A
Displays the textual description field of an event log entry.
xp4SmmEventLogEntryTimeStamp VIEW N/A
Displays the timestamp field of an event log entry.
xp4SmmEventLogEntrySource VIEW N/A
Displays the source field of an event log entry.
xp4SmmEventLogEntryEventCode VIEW N/A
Displays the event code field of an event log entry.
xp4SmmEventLogEncodedSinceTimeStampDate VIEW VIEW
date after which encoded events are of interest. Format:
day/month/year e.g., 25/12/1996
xp4SmmEventLogEncodedSinceTimeStampTime VIEW VIEW
Time after which encoded events are of interest. Format:
hr.min.sec e.g., 13.23.00
xp4SmmEventLogEncodedSinceTimeStampAllEncodedEvents VIEW N/A
Retrieves all events, in encoded form, since a specified time and
date.
xp4SmmEventLogEncodedAllEncodedEvents VIEW N/A
Retrieves all events in encoded form from event logger.
xp4SmmEventLogHowManyEvents VIEW N/A
Counts how many events are held by event logger.
xp4SmmEventLogFilterEvent VIEW Maintenance
Sets error log filter level.
xp4SystemAlarmsEncodedAlarmData VIEW N/A
The Encoded Alarms for an Alarm Source.
xp4SystemAlarmsHighestSeverityAlarmData VIEW N/A
The Highest Severity Alarm for an Alarm Source.
xp4SystemAlarmsDataAlarmSeverity VIEW N/A
The Alarm Severity of the Alarm selected.
xp4SystemAlarmsDataAlarmDescription VIEW N/A
The Alarm Description of the Alarm selected.
xp4SystemAlarmsDataAlarmTimeStamp VIEW N/A
The Alarm TimeStamp of the Alarm selected.
xp4SystemAlarmsDataAlarmState VIEW N/A
The Alarm State of the Alarm selected.
xp4SystemAlarmsFilterAlarmData VIEW Maintenance
The filter state of the alarm.
xp4SystemAlarmsFilterAllAlarms N/A Maintenance

Filter/Unfilter ALL alarms on the system.

Appendix H - Functional Enhancements For SNMP V2.0 Software Release
See AD310 - SNMP Network Management Interface V2.0 Requirements Specification for more
details on functional enhancements for the SNMP V2.0 software release

XP4 SNMPInterface Users Manual

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

XP4 SNMPInterface Users Manual

Uploaded by

Copyright:

Available Formats

Digital Microwave Corporation SNMP Interface User Manual

3. OBJECTIVES AND SCOPE.............................................................................................. 6

510-000011-003, Rev. B Page 1 November, 1998

4.4.8. IP Routing in a 1+1 Protected Link ......................................................................... 30

510-000011-003, Rev. B Page 2 November, 1998

7.1. RS232 VT100 INTERFACE OPERATION ............................................................................ 50

510-000011-003, Rev. B Page 3 November, 1998

7.8.2.11. Configuring Serial Management Port - Protocol. ......................................................... 75

510-000011-003, Rev. B Page 4 November, 1998

7.9.6. Reset Status Menu............................................................................................... 101

11. GLOSSARY ................................................................................................................ 196

510-000011-003, Rev. B Page 5 November, 1998

APPENDIX B - ERRORS LOGGED BY THE ERROR LOGGER ......................................................... 199

3. Objectives and Scope

3.1. Objectives and Scope

3.2. Intended Audience

3.3. Document Structure

510-000011-003, Rev. B Page 6 November, 1998

4.1. Functional Overview

• Radio Status Monitoring

• G.826 and G.821 Radio Performance Monitoring

• Radio Code Download

• SNMP Code Download

• 1+1 Protection System Status/Configuration

510-000011-003, Rev. B Page 7 November, 1998

4.2. Hardware Overview

4.2.1. Physical Description

Figure 4-1- SNMP connected to IDU

The dimensions of the SNMP are as follows :

Depth - 3 inches (76.2 mm)

510-000011-003, Rev. B Page 8 November, 1998

Figure 4-2 : Radio front panel with SNMP access

Figure 4-3 : SNMP accessed via SNMP back panel

IN TRIB1 OUT IN TRIB2 OUT IN TRIB3 OUT IN TRIB4 OUT

ALARM RELAYS COMPUTER

ODU ODU ODU ODU ODU ODU ODU ODU

Figure 4-4 : Radio front panel with no SNMP access

510-000011-003, Rev. B Page 9 November, 1998

4.2.2. Hardware Block Diagram

Figure 4-5 : Hardware Block Diagram

510-000011-003, Rev. B Page 10 November, 1998

68160 Dual Port Flash 1 Flash 2

510-000011-003, Rev. B Page 11 November, 1998

68160 Dual Port Flash 1 Flash 2

510-000011-003, Rev. B Page 12 November, 1998

4.2.2.2. Memory Configuration

4.2.2.3. Flash - Non Volatile Storage

4.2.2.5. SPI Serial EEPROM

510-000011-003, Rev. B Page 13 November, 1998

4.2.2.6. SPI RTC (Real Time Clock)

4.2.2.7.Dual Port RAM

Figure 4-8 : Dual Port RAM

510-000011-003, Rev. B Page 14 November, 1998

4.2.2.8. Memory Map

The chipselects have been allocated in hardware as follows;

Chipselect Device Size Block Size Port Width Access

4.2.2.9. CPU Interrupts

INTERFACE INTERRUPT ACTIVITY

4.2.2.10. RS232 VT100 Interface

510-000011-003, Rev. B Page 15 November, 1998

4.2.2.11. Ethernet Interface

4.2.2.12. RS232/RS422 SLIP/PPP Interface

4.2.2.13. IDU High Bandwidth Interface