NCN802

Configuration Note

Configuring the 8230 MainStreet

MainStreet LAN Products for Network Management Access

Table of Contents

1.0 Introduction
1.1 Remote Access
1.2 Access over the Network

2.0 Remote Access Configuration

2.1 Overview
2.2 8230 MainStreet Little Bridge Configuration
2.3 Craft Interface Configuration
2.3.1 Node Descriptions
2.3.2 Serial Port Configuration
2.3.3 Initiating a Node Management Session

3.0 Network Access Configuration

3.1 Overview
3.2 8230 MainStreet IP Parametre Configuration
3.3 CPSS Management Access
3.4 SNMP Management Access
3.4.1 Open Network Access
3.4.2 Controlled Network Access

Appendix - SNMP Primer

1.0 Introduction

Newbridge LAN products support a wide range of network management features. These
features are very useful for:
1. diagnosing and locating network faults,
2. monitoring and controlling the network’s nodes, and
3. analyzing performance and making appropriate adjustments.

To take full advantage of these features, all installed Newbridge LAN products must be
configured properly for Network Management access. This may seem to be quite obvious but,
in the headlong rush to get the equipment working, this part of the configuration is sometimes
forgotten.

1
NCN802
Configuration Note

Configuring the 8230 MainStreet

for Network Management Access MainStreet LAN Products

1.1 Remote Access

Remote access to the network must be provided for Newbridge support staff. This access
can be provided by a phone line and modem attached to the Newbridge NMS or one of the
Newbridge LAN nodes. Ideally, there should be remote access provided to every major LAN
node. At the least, a second remote access link should be installed. Additional remote access
lines are recommended wherever sections of a network might become isolated due to network
failures.

1.2 Network Access

All LAN nodes in the network must be configured to be accessible to the Network
Management System (NMS). If no permanent NMS is installed, then they should be
configured to be accessible to one of the LAN nodes which is centrally located and least likely
to be affected by network failures. Newbridge LAN products can be configured for Network
Management access via a LAN or a WAN interface. It is advisable to configure access via
more than one interface. This provides an alternate access path in case of network failures.

2.0 Remote Access Configuration

2.1 Overview

To obtain remote access to an 8230 MainStreet Ethernet Little Bridge, you must first
configure the bridge for modem access. This includes setting the port for the proper protocol,
and the remote network management’s modem phone number.

Once this is done, you must configure the Craft Interface (CI ) on your remote network
management station. This is done by defining the destination node parameters in the CIs
database. The serial port of the network management station is then configured for modem
connection in the Craft Interface records (refer to the Craft Interface manual for a description
of the modems supported by the Craft Interface release 3.0 and any manual configuration
settings or changes to the MODEM.CFG file that should be made before connecting the
modem to the Craft Interface ). Connection to the remote node via the Craft Interface is then
possible.

2
 NCN802
Configuration Note

Configuring the 8230 MainStreet

MainStreet LAN Products for Network Management Access

2.2 8230 MainStreet Little Bridge Configuration

To configure the 8230 MainStreet for modem access:

Procedure

Step 1 Set the port to the required protocol, by choosing the following softkeys when
connected to the 8230 MainStreet:

HOUSE SERIAL_PORT PORT_TYPE CPSS_MODEM

PROCEED

Step 2 To configure the network manager’s modem number choose the following
softkeys :
HOUSE MORE NOC_NUMBER <modem_no>
PROCEED

where <modem_no > = up to 12

digits (including Hayes AT modem commands)

2.3 Craft Interface Configuration

2.3.1 Configuring a Node Description Card

To describe a Newbridge node :

Procedure

Step 1 Select “Configure Craft Interface”.

Step 2 Select “Edit Node Descriptions”.

The Craft Interface displays the node description screen (see Figure 2-1).

3
NCN802
Configuration Note

Configuring the 8230 MainStreet

for Network Management Access MainStreet LAN Products

Craft Interface Main Menu

Configure Craft Interface

Edit Node Descriptions

Full name: -
Short name: -
Telephone: -
CPSS node ID: -
Login method: Manual

F2=Change this card F9=Delete this card

F3=Add new card =Next card, =Prev

Esc=Quit F1=Help F2=Change F3=Add F9=Delete 3:20p

Figure 2-1: Craft Interface Node Description Screen

Step 3a. To create a new node description, press <F3>.

Step 3b. To edit an existing node description, use the left and right arrows to select the
desired node description card and then press <F2>.

Step 4. Configure parameters. Each field on a node description card must match what
the node knows about itself.

Enter the name of the node, which can be any combination of up to 20

alphanumeric characters. This name is user-configurable.

Enter the short name, which should be an abbreviated form of the full name
and can have a maximum of six characters. All letters are automatically
converted to upper case.

4
 NCN802
Configuration Note

Configuring the 8230 MainStreet

MainStreet LAN Products for Network Management Access

Enter the telephone number of the modem at the node.

Include the area code and any other prefix digits required to reach that
number. Also include modem dial modifiers where necessary. The following
is a short list of some typical modem dial modifiers for a Hayes AT 2400 baud
modem:

‘,’ = pause

‘W’ = wait for dial tone

‘@’ = wait for silence

Enter the CPSS node ID, which is a number between 1 and 999 inclusive.
Each node must have a unique CPSS node ID for the Craft Interface to
communicate with it.

Enter the login method. If this node does not support automatic login and
access levels, select “Manual”. If this node does support automatic login and
access levels, select “Automatic”. Enter the desired level and password for
this level.

Step 5 Press <F2> to save changes.

Step 6 Press <F3> to get another blank card and fill in the required information.
Repeat this process until there is a completed card for each node you wish to
manage. Figure 2-2 shows an example of a completed node description card.

5
NCN802
Configuration Note

Configuring the 8230 MainStreet

for Network Management Access MainStreet LAN Products

Craft Interface Main Menu

Configure Craft Interface

Edit Node Descriptions

Full name: Ft. Lauderdale

Short name: LAUDER
Telephone: 9W1-613-591-3600
CPSS node ID: 304
Login method: Automatic
Level: 5
Password: MAINSTREET

F2=Change this card F9=Delete this card

F3=Add new card =Next card, =Prev

Esc=Quit F1=Help F2=Change F3=Add F9=Delete 3:20p

Figure 2-2: Example of a Completed Node Description Card

2.3.2 Serial Port Configuration

To configure the Craft Interface serial port for modem connection:

Procedure

Step 1 Select “Configure Craft Interface”.

Step 2 Select “Serial Port Configuration”.

The Craft Interface displays the serial port configuration screen (see Figure
2-3).

6
 NCN802
Configuration Note

Configuring the 8230 MainStreet

MainStreet LAN Products for Network Management Access

Craft Interface Main Menu

Configure Craft Interface

Serial Port Configuration

Port: COM2
Baud Rate: 9600
Databits: 8
Stopbits: 1
Parity: None
Medium: Modem
Modem Type: Hayes 2400

Use to cycle through options

Esc=Quit (making no changes) F2=Save changes

Esc=Quit F1=Help F2=Save Changes 3:20p

Figure 2-3: Craft Interface Serial Port Configuration Screen

Step 3 Use the left and right arrows to select the serial port connected to the node.
Step 4 Press <F2> to make changes.
Step 5 Configure Baud Rate, Databits, Stop Bits, and Parity to match the node serial
port configuration.

Step 6 Highlight “Medium” and select “Modem”.

Step 7 Highlight “Modem Type” and select the appropriate modem.

Step 8 Press <F2> to save changes.

7
NCN802
Configuration Note

Configuring the 8230 MainStreet

for Network Management Access MainStreet LAN Products

2.3.3 Initiating a Node Management Session

To initiate a node management session:

Procedure

Step 1 Select “Connect to a node”.

The Craft Interface displays the long name from all node description cards
currently configured (see Figure 2-4).

Craft Interface Main Menu

Start a Node Configuration Session

Tower North Unamed CPSS #203

Operations Unamed CPSS#311

Tower South

Enter=Start node session

F2=Make modem connection Path via modem
F9=Restart node ? No path to node

Esc=Quit F1=Help 3:20p

Figure 2-4: Craft Interface Connect to a Node Screen

Step 2 Highlight the desired node.

Step 3a If the Craft Interface is directly connected to the node, press <Return>.
Step 3b Since the CI is connected via modem to the node, press <F2>.

The Craft Interface prompts for the node’s level and password (if sup-
ported by the node).

8
 NCN802
Configuration Note

Configuring the 8230 MainStreet

MainStreet LAN Products for Network Management Access

Step 4 Type the level and password for the node and press <Return>. The default
password is ‘MAINSTREET’.

The Craft Interface initiates a node management session with the node and
displays the node management session main menu.

3.0 Network Access Configuration

3.1 Overview

To allow the 8230 MainStreet to be managed by the 4602 MainStreet Network Manager
and by SNMP Managers, the bridge must be configured for network access. Network access
is comprised of two types of virtual management connections:

Control Packet Switching Service (CPSS) and Simple Network Management

Protocol (SNMP)

The 8230 MainStreet can communicate with other nodes using the Control Packet
Switching System (CPSS) protocol. CPSS is Newbridge’s error-correcting, X.25-based
network management protocol. CPSS connections will be used to establish 4602 MainStreet/
8001 MainStreet management sessions with the 8230 MainStreet Ethernet Little Bridge. In
order for the 8230 MainStreet to communicate with a remote network manager over network
links (via CPSS), the 8230 MainStreet must be configured with the remote network
manager’s node number. CPSS connections must then be configured in order to allow remote
network management.

Simple Network Management Protocol connections will enable a SNMP manager to

read/write to the 8230 MainStreet, provided that the access rights have been properly
configured to do so. There are two possible scenarios; secure or non-secure network access.
In the first, the configuration consists of defining the message community name as
“PUBLIC” and setting read/write access privileges. In a secure network, the message
community name and IP address should be specific to your SNMP manager. The access
privilege configuration could either be set to read or read/write, depending on the actual
needs.

The 8230 MainStreet implements the Internet Protocol (IP) and User Datagram Protocol
(UDP) transport layer protocol to provide an error free packet delivery service to convey

9
NCN802
Configuration Note

Configuring the 8230 MainStreet

for Network Management Access MainStreet LAN Products

network management messages (both CPSS and SNMP) over LAN and expansion module
circuits. Hence, for either management access method, bridge IP parameters have to be
configured.

3.2 8230 MainStreet IP Parameter Configuration

To configure the 8230 MainStreet for use with IP, you must configure five parameters.
For details on these parameters, see the 8230 MainStreet Ethernet Little Bridge Technical
Reference manual. The procedure is as follows (Figure 3-1 shows the IP Parameter display):

Procedure:

From the main menu, choose

Step 1 CONFIG BRIDGE IP ADDRESS <address>

PROCEED
where <address> = IP address in dotted decimal form

In a network which does not already use TCP/IP, Newbridge recommends to

use an IP address which lies between 200.1.1.X and 200.1.254.X where X is
a host ID between 1 - 254.

In a network with TCP/IP already configured, the IP address should be unique

and correspond to the network or subnetwork that the bridge resides in.

CAUTION: If the bridge IP address is changed, all existing LAN module

circuit and serial data module circuit CPSS cross-connections must be
disconnected and reconfigured.

Step 2 CONFIG BRIDGE IP BROADCAST <address>

PROCEED
where <address> = IP address in dotted decimal form

Step 3 CONFIG BRIDGE IP SUBNET_MASK <mask>

PROCEED
where <mask> = subnet mask in dotted decimal form

10
 NCN802
Configuration Note

Configuring the 8230 MainStreet

MainStreet LAN Products for Network Management Access

Step 4 CONFIG BRIDGE IP DEF_ROUTER <address>

PROCEED
<address> = IP address in dotted decimal form

Step 5 CONFIG BRIDGE IP TIME_TO_LIVE <time>

PROCEED
where <time> = 0 to 255 s

NOTE: If Time to Live is set to zero, an IP packet originating from the bridge will be
dropped at the first intermediate node on the way to the destination.

8230 MainStreet M111-03-05 122-1 Hops Alarms: 21 9-Mar-91 9:40A

Bridge IP address : 138.20.15.3 Subnet Mask : 255.255.255.0

Broadcast IP address: 138.20.255.255 Default Router: 138.20.15.1
Time to live : 40 secs.

ARP cache has 6 entries (maximum 8 entries)

# Host IP address Ethernet address

- --------------- ----------------------
1 138.20.15.1 WFT:00-00-A2-C5-A6-70 (default router)
2 138.20.10.2 NNC:00-80-21-11-75-A5
3 138.20.15.4 NNC:00-80-21-AA-DF-67
4 --- --- (empty)
5 138.20.15.6 WD :00-00-0C-2E-Ad-71
6 138.20.10.2 SUN:08-00-20-97-3D-1A
7 138.20.15.7 WD :00-00-0C-8A-AA-89
8 --- --- (empty)

CONFIG BRIDGE IP

F1-ADDRESS F2-BROADCAST F3-SUBNET_MASK F4-TIME_TO_LIVE F5-DEF_ROUTER

F6- F7- F8-CANCEL F9-QUIT F10-
AltQ=Quit

Figure 3-1: IP Parameter Display

11
NCN802
Configuration Note

Configuring the 8230 MainStreet

for Network Management Access MainStreet LAN Products

3.3 CPSS Management Access

To configure the remote network manager’s CPSS node number:

Procedure

Step 1 HOUSE MORE NOC_NODE <node_no> PROCEED

where <node_no> = 1023 which is the CPSS node ID for an active4602

MainStreet Network Management Station
or
where <node_no> =1000-1020 which is the CPSS node ID for an 8001
MainStreet LAN Manager

To make CPSS Cross-Connections for Serial Data and LAN Module CPSS Connections:

Step 2 From the bridge at one end of the link (bridge _A):

CONFIG CONNECT <CPSS-n>

To_HOST <address_B> PROCEED

Step 3 From the bridge at the other end of the link (bridge_B):

CONFIG CONNECT <CPSS-n>

TO_HOST <address_A> PROCEED

NOTE: Up to eight CPSS circuits can be cross-connected to a LAN module circuit.

<CPSS-n> is the CPSS circuit identifier listed in Table 3-1.

For Primary Rate Expansion Module CPSS Connections to any timeslot:

Step 1 CONFIG CONNECT <CPSS-n>

TO_CIRCUIT <Pn-cc> PROCEED
or
To use the Facilities Data Link for T-1 Modules:

Step 2 CONFIG CONNECT <CPSS-n>

TO_CIRCUIT <Pn-FDL> PROCEED

12
 NCN802
Configuration Note

Configuring the 8230 MainStreet

MainStreet LAN Products for Network Management Access

or
To use Time Slot Zero for E-1 modules:

Step 2 CONFIG CONNECT <CPSS-n>

TO_CIRCUIT <Pn-TS0> PROCEED

NOTE: Only one CPSS circuit can be cross-connected to a primary rate expansion
module circuit. <CPSS-n> is the CPSS circuit identifier listed in Table 3-1.

Valid Circuits for

CPSS Circuits Protocol
Cross -Connection

T1 Primary Rate:
P3-cc, P3-FDL 1
CPSS over
CPSS-1
LAPB
E1 Primary Rate:
P3-cc, P3-TS0 2
T1 Primary Rate:
P4-cc, P4-FDL 1
CPSS over
CPSS-2
LAPB
E1 Primary Rate:
P4-cc, P4-TS0 2

LAN:
P1-1, P2-1
CPSS over
CPSS-3 to CPSS-10 UDP/IP Serial Data:3
P3-1, P4-1

1 Facilities Data Link (FDL) is available on a T-1 link when Extended Superframe (ESF)
framing is selected.
2 Time Slot Zero (TS0) is always available on an E-1 link.
3 Only one CPSS circuit may be cross-connected to a given Serial Data expansion module
circuit.

Table 3-1: CPSS Circuit Identifiers

13
NCN802
Configuration Note

Configuring the 8230 MainStreet

for Network Management Access MainStreet LAN Products

3.4 SNMP Management Access

3.4.1 Open Network Access

If your network does not require restricted SNMP access to SNMP managers, then the
following configuration is adequate (Figure 3-2 shows the message community display):

Procedure

Step 1 Message Community Name

CONFIG BRIDGE SNMP MSG_COMMUN NEW <name>
PROCEED
Where the name entered is “PUBLIC”

Step 2 Message Community Access Privileges

CONFIG BRIDGE SNMP MSG_COMMUN <entry no>
ACC_PRIV READ_WRITE

8230 MainStreet M111-03-06 122-1 Hops Alarms: 21 09-Mar-91 9:40A

# Community Name IP Address Access Privilege

- --------------- --------------- ----------------
1 PUBLIC Unassigned READ_WRITE
2 --- --- --- (not configured)
3 --- --- --- (not configured)
4 --- --- --- (not configured)
5 --- --- --- (not configured)
6 --- --- --- (not configured)
7 --- --- --- (not configured)
8 --- --- --- (not configured)

CONFIG BRIDGE SNMP MSG_COMMUN "??"

Enter an entry number

F1- F2-NEW F3-DELETE_ALL F4-DELETE F5-

F6- F7- F8-CANCEL F9-QUIT F10-
AltQ=Quit

Figure 3-2: Message Community Display (Open Network Access)

14
 NCN802
Configuration Note

Configuring the 8230 MainStreet

MainStreet LAN Products for Network Management Access

3.4.2 Controlled Network Access

If your network requires security enhancements such as restricted access to SNMP

managers, then configure the 8230 MainStreet in the following manner (Figure 3-3 shows the
message community display):

Procedure
Step 1 CONFIG BRIDGE SNMP MSG_COMMUN NEW <name>
PROCEED
Where the name is defined as the network manager’s host name, for example
“4602 NMS”.
Step 2 CONFIG BRIDGE SNMP MSG_COMMUN <entry_no>
IP_ADDRESS <address>
PROCEED
Newbridge suggests to use an IP address which is defined to be 200.1.X.X
where X is a value between 1 - 254.
Step 3 CONFIG BRIDGE SNMP MSG_COMMUN <entry no>
ACC_PRIV READ_WRITE or ACC_PRIV READ

8230 MainStreet M111-03-06 122-1 Hops Alarms: 21 09Mar-91 9:40A

# Community Name IP Address Access Privilege

- --------------- --------------- ----------------
1 --- --- --- (not configured)
2 --- --- --- (not configured)
3 --- --- --- (not configured)
4 NET_MANAGER 138.120.10.6 READ_WRITE
5 --- --- --- (not configured)
6 --- --- --- (not configured)
7 --- --- --- (not configured)
8 --- --- --- (not configured)

CONFIG BRIDGE SNMP MSG_COMMUN "??"

Enter an entry number

F1- F2-NEW F3-DELETE_ALL F4-DELETE F5-

F6- F7- F8-CANCEL F9-QUIT F10-
AltQ=Quit

Figure 3-3: Message Community Display (Controlled Network Access)

15
NCN802
Configuration Note

Configuring the 8230 MainStreet

for Network Management Access MainStreet LAN Products

Appendix - A Brief Tour of SNMP

Introduction

What is SNMP?

SNMP stands for the Simple Network Management Protocol which became a standard
in 1989 (RFC 1157). SNMP originated in the Internet community in response for the need
to manage TCP/IP networks. Although it is used primarily in this environment, its
architecture supports its use over any network media or protocol suite, including OSI.

SNMP has gained popularity because of its: simplicity (it has been relatively easy for
vendors to implement), extensibility (vendors can model their own devices), functionality
(although limited in scope, SNMP does provide a degree of multi-vendor network manage-
ment) and availability (SNMP is available now and is a proven solution). As a result of these
four factors, SNMP has become the defacto standard protocol for LAN network manage-
ment.

SNMP Jargon

Generally speaking any protocol defines: how a manager (i.e. the 8001 MainStreet) gets
data from and sends data to a managed entity (i.e. an 8230 MainStreet); how the data is
formatted; when it is transmitted; and how the manager references the data in the managed
device. SNMP has a variety of jargon to describe each of these aspects which are described
below. Several of these terms are shown in Figure 2.0.

A SNMP agent is software process which runs in a managed device. The agent stores a
variety of management data and responds to the manager’s requests for specific data. The
SNMP agent has to be properly configured in order to communicate with a network manager.

A SNMP manager (also known as a client), is a software process which runs within a
network management station. The manager has the ability to query agents using several
SNMP commands.

The Management Information Base (MIB), can be thought of as a database of managed

objects. An agent will read or write to these objects as a result of a command from the SNMP
client. These read and write commands are known as gets and sets respectively. The MIB
is very similar to the Master Parameter List (MPL) found in 3600 MainStreet nodes.

16
 NCN802
Configuration Note

Configuring the 8230 MainStreet

MainStreet LAN Products for Network Management Access

A trap is a special unsolicited command send from an agent to a manager after it has
sensed a predefined condition.

Network Management SNMP: Simple Network

Management Protocol
Applications
Network
Management MIB: Management
Information Base
Station SNMP
Manager/Client
eg. Intelligent
NetworkStation
• TRAP
• SET
• GET

SNMP Agent
SNMP Agent
MIB
MIB A Standard
A Standard AA AB AC
Manageable
Devices AA AB AC Z Private
X Private
ZA ZB XC
eg. Bridges
Routers XA XB XC ZD ZE
LAN Adapters
Workstations

Figure A.0: The Basic Components of SNMP

More detailed descriptions of these definitions are given in the following sections.

The MIB

Its Overall Structure

The Management Information Base is used to: describe what information is managed,
define objects in the useful protocol layers, and place information in logical groupings.
Information is represented in the MIB in accordance with an Internet standard, the Structure
of Management Information (SMI) for TCP/IP-based Internets (RFC 1155).

17
NCN802
Configuration Note

Configuring the 8230 MainStreet

for Network Management Access MainStreet LAN Products

Managed objects are organized hierarchically in the MIB as a tree. The branches describe
the logical grouping of management data and the leaves are the actual management data
objects (see Figure A.1). Associated with each object is an identifier, a string of numbers
which uniquely defines the object in the MIB. An identifier is created by tracing the path from
the root (i.e. top) of the tree downward to the object. As an example, the path to the
experimental branch is 1.3.6.1.3.

A MIB view is a subset of all the network management variables. Each object may have
a SNMP access mode which is READ-ONLY or READ-WRITE.

The portions of the MIB relevant to the 8001 MainStreet are the management MIB (path
1.3.6.1.2 – commonly known as the Internet-standard or standard MIB), and the private
enterprise MIB (path 1.3.6.1.4.1 ). These are described in detail below.

iso ccitt joint-iso-ccit

(1) (2) (3)

org
(3)

dod
(6)
internet
(1)
private
(4)
directory mgmt experimental
(1) (2) (3)
mib I mib II
(1) (2)
enterprise
(1)
reserved
(0) ... Wellfleet Newbridge
(18) ... ...
(123)

Figure A.1: The Management Information Base

18
 NCN802
Configuration Note

Configuring the 8230 MainStreet

MainStreet LAN Products for Network Management Access

Each MIB object is defined using the following fields:

Object: A textual name, termed the object descriptor, for the object type, along with
it’s corresponding object identifier.
Definition: A textual description of the object.
Syntax: syntax of the variable (examples are counter, gauges, IpAddress)
Access: (read only, read write, write only, or not accessible)
Status: (mandatory, optional, or obsolete)

The Standard MIB

This MIB subtree has approximately 100 standard objects specified in it, which are
common to a number of devices (i.e. LAN bridges, routers, wiring hubs, etc.). It includes
objects such as network addresses, interface types, counters and thresholds. Using the
standard MIB, a network manager can provide some rudimentary management of another
vendor’s device.

The first version of the standard MIB is known as MIB I (RFC 1156). Since its
introduction additional objects have been added and introduced in MIB II (RFC 1158).

Many related objects are organized in groups (i.e. system, interfaces, IP, etc.). Although
not all objects in the standard MIB must be implemented in a devices, several groups are
mandatory.

The Private Enterprise MIB

The private enterprise MIB was designed to allow vendors to more accurately model their
devices using objects outside of those described in the standard MIB. These objects are placed
in a separate branch of the private enterprise subtree. Any vendor may apply to receive a
separate branch emanating from this point.

Any object written in a private MIB must conform to the format of the SMI. In order to
promote multi-vendor management (and more importantly to sell more of their boxes), many
vendors are publishing their MIB extensions. This information can be used by a network
manager to provide an increased level of management of a given device.

19
NCN802
Configuration Note

Configuring the 8230 MainStreet

for Network Management Access MainStreet LAN Products

Newbridge’s Private Enterprise MIB

Figure A.2 illustrates the structure of the Newbridge private enterprise MIB branch.

The product line branch is used to provide a unique name for each product type (i.e. the
number 1.3.6.1.4.1.123.1.1.1.1 will uniquely define an 8230 MainStreet). These objects will
not be available for any SNMP get or set requests.

The NCI modifier branch is used to allow all NCI objects to be modelled using SNMP.
This will allow a network manager to perform any action on a device using SNMP that is
currently accomplished using a NCI-2 read/set command.

As our routers are OEM’d products from Wellfleet, their MIB extensions are located
below the Wellfleet branch (1.3.6.1.4.1.18).

Private Enterprise
(1.3.6.1.4.1)

Newbridge
(123)

Product Line
(1.1) NCI Modifiers
(1.2)
Standalone Products Integral Products
(1) (2)

class.item.modifier1.modifier2
8230 MainStreet 3600 MainStreet ITB
(1) (1)

Figure A.2: Newbridge’s Private Enterprise MIB Branch

Commands and Responses

SNMP specifies five types of commands or responses that are used by agents and or
managers. GetRequest, GetNextRequest, SetRequest, GetResponse, and Trap.

20
 NCN802
Configuration Note

Configuring the 8230 MainStreet

MainStreet LAN Products for Network Management Access

Manager Commands

An agent will read the value of MIB variables after receiving either a GetRequest (get)
or GetNextRequest (getnext) command from a manager with an object identifer. The get will
return the object specified exactly by the object identifier (or an error if no object exists) while
a get next will return the object located “next” to it (with the tree being ordered top —>bottom
and left—>right).

Upon receipt of a SetRequest from a manager, the agent will change (i.e. write) to a MIB
variable.

Agent Responses

The agent then sends back the data it gathers to the manager requesting the information
with a GetResponse verb.

An agent will send out a trap to managers that have been registered to receive it when
it has sensed a predefined condition. SNMP has defined seven types of traps:

Relating to product boots • ColdStart

• WarmStart

Relating to link status change • LinkDown

• LinkUp

Miscellaneous • AuthenticationFailure
• EGPneighbourloss
• Enterprise-specific

Much like the enterprise specific MIB, enterprise-specific traps allow vendors to model
events that are unique to their equipment.

In order to receive a trap from an agent, the agent must be configured to send traps to that
manager.

Because one cannot be assured a SNMP trap will reach a manager (since SNMP uses UDP
– the Unreliable Datagram Protocol as a transport mechanism), a manager must continually
poll network devices to ensure they are “healthy”. Traps provide a means to redirect the
manager’s polling to a troubled device. The manager can then read a number of MIB variables

21
NCN802
Configuration Note

Configuring the 8230 MainStreet

for Network Management Access MainStreet LAN Products

to assess the state of the device. Polling may also be used to continually collect one or more
MIB variables to provide real time statistical displays.

Using Management Tools On the MIB

To illustrate how a network management system would use the MIB, a simple example
is given in Figure A.3. In this example a used car advertisement is modelled like the
management information base.

To determine what type of radio the car was equipped with, the user could type GET
1.3.1.1.1. This would return AM/FM. Alternatively the alias “radio”, could have been used
(i.e. GET radio) which would return the same value.

To find out what type of tape deck, the user could type GETNEXT radio, GET 1.3.1.1.2,
or GET tape. The GETNEXT command could be used again to collect the remaining
information in the tree (i.e. NO, 1984, 180,000, SILVER, CAR, $1000). Note: if a subsequent
GETNEXT command is issued, an error will be returned as all objects “in front” of the
original object identifer have been read.

If the user specifed get 1.3.3 (get age), an error would be returned as there is no object at
this point.

In order to change the selling price in the add the user would type SET 3.

22
 NCN802
Configuration Note

Configuring the 8230 MainStreet

MainStreet LAN Products for Network Management Access

description selling price

vehicle
(1) (3)
(2) CAR $1000

make details
model
(1) (3)
TOYOTA (2)
number type colour
age
(1) SR5 HATCHBACK (2) SILVER (4)
(3)

options year kilometers

(1) (1) 1984 180,000 (2)
sound system air conditioner
(1) NO (2)
radio tape
(1) AM/FM None (2)

Figure A.3: An Example of Walking the MIB

Access Control

SNMP Communities

As SNMP’s architecture allows multiple managers to access a given manageable device,

the concept of a community was introduced. A community is a pairing of a SNMP agent with
one or more network management stations which are used to provide a level of access control
(an access mode may be read only or read-write).

As well, the agent may restrict what portion of the MIB a manager may have access to.
This is known as a MIB View.

23
NCN802
Configuration Note

Configuring the 8230 MainStreet

for Network Management Access MainStreet LAN Products
R01-1191

Newbridge welcomes any comments or suggestions you may have regarding this document or Newbridge
products. Please forward them to the attention of the Corporate Applications Group through one of the offices
listed below.

This Configuration Note pertains to generic M111-03-05.

Other product releases (earlier or later) may operate differently from those described herein.

Newbridge makes no warranty for the use of this document and assumes no responsibility for errors which may
appear herein. No commitment is made to update the information contained herein.

Newbridge, MainStreet and the Newbridge logo are trade marks of Newbridge Networks Corporation.

Copyright 1991, Newbridge Networks Corporation, All Rights Reserved

Newbridge Locations:

CANADA: ASIA PACIFIC Area REGIONAL OFFICES:

and the Soviet Union:
Newbridge Networks Corporation, Atlanta (404) 594-0100
600 March Road, Newbridge Networks Corporation, Boston (508) 875-3600
P.O. Box 13600, P.O. Box 13600, Chicago (708) 932-1200
Kanata, Ontario, Kanata, Ontario, Cincinnati (513) 772-9300
Canada, K2K 2E6 Canada, K2K 2E6 Cleveland (216) 757-8700
Tel. (613) 591-3600 Tel. (613) 591-3600 Dallas (214) 490-4200
FAX (613) 591-3680 FAX (613) 591-3201 Denver (303) 986-3600
Telex 053-3653 Edmonds (206) 774-0466
Newbridge Soviet Telecom, Fairfield (201) 882-9595
Montreal (514) 599-5715 Nastasinski per. 7 Houston (713) 376-3608
Ottawa (613) 591-6300 Moscow, 103006, USSR Indianapolis (317) 575-0800
Toronto (416) 238-5214 Tel. 7-095-438-4156 Lincoln (402) 438-2700
Vancouver (604) 430-3600 FAX 7-095-200-4233 Los Angeles (213) 860-3600
or Dial 1-800-267-MAIN Manhattan (212) 563-3600
Hong Kong 852-807-1380 Marlboro (201) 972-0184
EUROPE, MIDDLE EAST Yokohama 81-45-661-3612 New York City (201) 283-3000
and AFRICA: Auckland 64-9-358-8103 Northern New Jersey (201) 818-8688
Leningrad 7-812-1126770 Philadelphia (609) 486-1100
Newbridge Networks Limited Minsk 7-0172-346986 Phoenix (602) 258-3200
Coldra Woods, Raleigh-Durham (919) 481-0400
Chepstow Road, UNITED STATES: St. Louis (314) 576-6400
Newport, Gwent, San Francisco (415) 933-3600
United Kingdom, NP6 1JB Newbridge Networks Inc. Seattle (206) 232-4300
Tel. 633-413600 593 Herndon Parkway, Washington (703) 834-3600
FAX 633 413680 Herndon, Virginia, or Dial 1-800-332-1080
22070, U.S.A.
London (71) 638 0022 Tel. (703) 834-3600
FAX (703) 471-7080

24