Section 11.1, Simple Network Management Protocol. Section 11.2, Port Data Capture

Chapter 11

SNMP and

Port Data Capture

his module discusses the Simple Network Management Protocol (SNMP) and the BANDIT device’s Port Data Capture feature, and how they can be used to augment or enhance system management in Encore Networks’ BANDIT products. See the following sections:

• Section 11.1, Simple Network Management Protocol • Section 11.2, Port Data Capture

Note:

For information on the BANDIT products’ standard system management, see Chapter 10, System Management.

11.1

Simple Network Management Protocol

to easily add network management functions. SNMP also separates the management architecture from the architecture of the hardware devices, which broadens the base of multivendor support.

SNMP contains two primary elements: a manager and agents. The manager is the software on the console through which a (human) network

administrator performs network management functions. An agent is the software entity that interfaces to a device being managed. Bridges, routers, and network servers are examples of managed devices.

Managed devices contain managed objects. Managed objects are items such as hardware, configuration parameters, performance statistics, and so on, that directly relate to the operation of the device. These objects are arranged in a management information base (MIB). SNMP managers and agents communicate in order to view and use these MIBs.

Different types of MIBs are available, including the internet standard MIB, defined in Request for Comments (RFC) documents 1212 and 1213; the remote monitoring MIB, defined in RFC 1271; and private-enterprise MIBs that vendors define for their products. Encore Networks, Inc., supports MIB II with Encore Networks’ proprietary extensions.

The SNMP manager reads the values of the objects within a MIB and modifies the values as appropriate—in other words, it manages the objects. Because SNMP is an application-layer protocol, it must rely on protocols in the lower OSI layers for other communication functions. For example, the User Datagram Protocol (UDP) transports the SNMP message through the network. IP provides network-layer functions, such as addressing for the datagram.

11.1.1

SNMP Access to the BANDIT

Note:

See Appendix D, Default Passwords, for the default values of the BANDIT device’s SNMP Get Community string and Set Community string.

To gain SNMP access to the BANDIT, you must configure the SNMP parameters on the BANDIT and you must configure an SNMP manager on the control terminal. See the following sections:

• Section 11.1.2, The BANDIT SNMP Agent • Section 11.1.3, The SNMP Manager

11.1.2

The BANDIT SNMP Agent

The SNMP agent is part of the BANDIT software and thus always resides in the BANDIT. You need to configure the BANDIT’s SNMP settings so that the SNMP manager can manage the BANDIT. Configure the BANDIT’s SNMP Get and Set communities, its SNMP Trap Table, and a default SNMP trap address. (The default SNMP trap address is the SNMP manager’s IP address.)

11.1.2.1

Predefined SNMP Traps

The BANDIT supports several predefined SNMP traps:

• Port Down. This allows the unit to send a message to the SNMP manager indicating that a physical entity, such as a cable or a CSU/DSU, is not functional.

• Network Down. This allows the unit to send a message to the SNMP manager indicating that the switch is not responding.

• DLCI Down. This allows the unit to send a message to the SNMP manager indicating that a DLCI is down.

• Checkstatus. This is reserved for use in testing.

• Memorylow. This is generated when units have insufficient memory. • Physicallineup. This is sent when DTR ON has been detected by any

physical port.

BANDIT plays the network role in the Frame Relay connection, this means that the port starts responding to polls. If the BANDIT plays the user role in the Frame Relay connection, this means that the port begins receiving responses to polls. (The user role is always sending polls across the Frame Relay network.)

• FRportmgmtdown. This is sent when Frame Relay management is down. If the BANDIT plays the network role in the Frame Relay connection, this means that the port stops responding to polls. If the BANDIT plays the user role in the Frame Relay connection, this means that the port stops receiving responses to polls.

• FRdlciup. This is sent when a DLCI is active, when the previous status was “new” or “DLCIDown.”

• FRdlcidown. This is sent when a DLCI is inactive, when the previous status was “new” or “DLCIUp.”

11.1.2.2

SNMP Configuration in the BANDIT

Note:

This procedure must be performed via the direct connection between the BANDIT device and the local management console.

1

On the BANDIT’s Main Menu, select System Administration. On the System Administration menu, select SNMP Configuration. ™ The following menu is displayed. This menu sets passwords (i.e., a Get Community string and a Set Community string) for SNMP management. This menu also configures trap addresses (in the SNMP Trap Table) and sets a default trap address.

1) SNMP Get Community String : ****** 2) SNMP Set Community String : ****** 3) SNMP Trap Default Addr : 0.0.0.0 4) SNMP Trap Table

Note:

See Appendix D, Default Passwords, for the BANDIT device’s SNMP Get and Set Community Strings.

2

Select Get Community String.

Note:

The Get string lets you view (read) the remote device’s configuration.

™ The following prompt is displayed:

a Enter the Get community string.

3

Select Set Community String.

Note:

The Set string lets you modify (write) the remote device’s configuration.

™ The following prompt is displayed:

a Enter the Set community string.

4

Select SNMP Trap Default Addr to set the default trap address. ™ The following prompt is displayed:

Define SNMP Get Community String:

a Enter the IP address of the terminal that runs the SNMP manager, and press Enter.

5

Select SNMP Trap Table to record up to five trap addresses. ™ The following prompt is displayed:

a Enter a trap address and press Enter.

™ A prompt for the next table entry appears.

6

You can continue entering addresses, or you can press Escape to return to the SNMP menu.

7

When you have finishing configuring the BANDIT, Write (save) the configuration and Reset the BANDIT. See the following sections: • Section 3.3.7, Write Configuration

• Section 3.3.8, Reset Unit

8

If you have not yet done so, configure the SNMP manager on your control terminal.

11.1.3

The SNMP Manager

To use an SNMP manager, you must configure the manager to use the Get and Set string that match those configured in the BANDIT. In addition, you must compile the SNMP manager’s MIBs.

11.1.3.1

MIB Compilation

Before you can use an SNMP manager to communicate with a device’s SNMP agent, you must compile the manager’s MIBs. MIBs must be

Enter SNMP Trap Default Address (N.N.N.N):

compiled in a specific order. Follow the instructions in the SNMP manager’s user guide to organize and compile the MIBs.

Note:

To receive the Encore Networks proprietary MIBs, contact your Encore Networks representative.

The order for compiling the Encore Networks MIBs is easy; just compile the Encore Networks MIB files in alphabetic order. (Private MIBs from other organizations do not necessarily follow alphabetic order when compiling.)

Figure 11-1 through Figure 11-3 provide one example of looking at the private MIBs available on the SNMP Manager. (This example uses Castle Rock Computing’s SNMPc™, a Windows-based SNMP manager.)

Figure 11-2. SNMP MIBs Directory

11.1.3.2

Encore Networks’ MIB Extensions

In addition to the standard MIBs in MIB II, the BANDIT uses proprietary MIB extensions from Encore Networks, Inc. The BANDIT uses the following proprietary MIB file:

• Fc.mib

This file is divided into three subfiles: • Fc_fastc.mib

• Fc_port.mib • Fc_stats.mib

The Fc_fastc.mib file is further divided into three groups:

• Registration Group. The Registration group contains only the Object Identifiers for all products.

• Temporary Group. The Temporary group contains experimental MIB variables not yet released.

• Product Group. The Product group comprises two subgroups: - The snmpAgent subgroup contains several subgroups, described

below. The snmpAgent subgroup contains all SNMP-specific

parameters. SNMP variables match the menu parameters and ranges used for unit configuration. The snmpAgent subgroup consists of the following files: › snmpMibVersion › snmpAgentIpAddr › snmpAgentName › snmpAgentSetCommunity › snmpAgentGetCommunity › snmpAgentDefaultTrapIpAddr › snmpAgentTrapSendTable

- The FrameRelay subgroup contains another subgroup called fsFrad. The fsFrad subgroup contains all SNMP-specific parameters.

Note:

The “fs” at the beginning of these MIBs represents the BANDIT. The BANDIT parameters have up to 30 virtual logical ports, from 0 to 29.

Table 11-1. fsFRAD subgroups

(1 of 3)

fsFRAD

Subgroup

Component Subgroups

fsGeneralParms fsReloadFactoryValues, fsResetUnit, fsSaveToNonVolatile, FsFirmwareVersion, fsParamModStatus, fsClearAllStats,

fsClockSource, fsActiveCodeRegion, fsSoftwareVersion, fsMACAddr, fsDatabase, fsActiveDataBase, fsDatabaseToBeUsed, fsClearDatabase, fsSystemOne, fsNetworkLoader, fsHostIPAddr, fsCodeFileName, fsLoadTimeOut, fsRegion1Priority, fsRegion2Priority,

fsActiveDatabase, fsEraseInactiveRegion, fsInitDownload, fsNetLoaderSectorTable, fsCsuDsuSpeed, fsDistributedSystem, fsFradRole, fsFradBoardTable, fsRemoteLogging,

fsIpFilteringRemoteLogStatus, fsIpFilteringRemoteLogAddr, fsIpFilteringRemoteLogFac, fsCopyConfig, fsLocALocType, fsLocALoadMethod, fsLocATFTPSerAddr, fsLocATFTPFileName, fsLocBLocType, fsLocBLoadMethod, fsLocBTFTPSerAddr,

fsRouting fsIpRouting, fsIpRoutingMode, fsIpStatisRouting, fsIpDefaultRouter, fsIpToDlciTable, fsIpRipIPFramePri, fsIpRipIPV2Passwed,

fsIpRipIPDynLinkSupport, fsIpRipAccList1Action,

fsIpRipAccList2Action, fsIpRipAccList3Action, fsIpRipAccList4Action, fsIpRipAccList5Action, fsIpRipAccList1Table, fsIpRipAccList2Action, fsIpRipAccList3Action, fsIpRipAccList4Action, fsIpRipAccList5Action, fsIpRipInterfaceTable, fsIpRipStaticTable, fsIpRipPacketPri,

fsIpBOOTPAddress, fsIpNameTable, fsIpFiltering, fsIpFilteringEnable, fsIpFilteringRemoteLog, fsIpFilteringTable, fsIpPriority, fsIpPriEnable, fsIpPriDefPriority, fsIpPriTable, fsIpDHCP, fsIpDHCPPrimaryAddr, fsIpDHCPSecondaryAddr, fsIpNAT, fsIpNatCfg1NATStatus,

fsIpNatCfg1IPMasMode, fsIpNatCfg1NATIPMasAddr, fsIpNatCfg1PMasAddr, fsIpNatCfg1RemoteLog, fsIpNatCfg1StaticTable, fsIpNatCfg2NATStatus,

fsIpNatCfg2IPMasMode, fsIpNatCfg2NATIPMasAddr, fsIpNatCfgRemoteLog, fsIpNatCfg2StaticTable, fsIpxRouting, fsIpxRoutingMethod, fsIpxEncapsulationMethos,

fsIpxPassThruGPTName, fsIpmFrameRelayPri, fsIpmRipPacketPri, fsIpxSapPacketPri, fsIpxWANFlag, fsIpxPrimaryNetwork,

fsIpxRouterName, fsIpxNetworkSize, fsIpxRouteTable,

fsIpxTableEntry, FsIpxTableEntry, fsIpxIndex, fsIpxNetNum, fsIpxPri, fsIpxGptName, fsIpxSapMode, fsIpxStatus, fsFrameRelayRouting, FsFrameRelayRoutingTable, fsSna, fsX25NewGlob,

FsX25NewGlobSwEntry

fsStats FC_STATS.MIB: fsFrameRelayStats, fsAsyncEncapsulationStats, fsBitSyncEncapsulationStats, fsSlipStats, fsRipRoutingStats, fsAsyncBurosEmulationStats, fsSyncBurosEmulationStats, fsSdlcRoutingStats, fsByteSyncEncapsulationStats,

fsTelnetTerminalStats, fsIpxStats, fsALCStats, fsTokenStats, fsEtherStats, fsIPStats, fsICMPStats, fsUDPStats, fsTCPStats,

fsSNMPStats, fsNetLoaderStats, fsPriorityStats, fsSdlc2Stats, fsLlcStats, fsSnaSwStats, fsT1DsuStats, fsE1DsuStats, fsX25NewStats,

fsXPadStats, fsISDNStats, fsIpFilteringStats, fsNewPPPStats, fsMLPStats

fsT1DsuConfig fsT1DsuFrameFormat, fsT1DsuLineCode, fsT1DsuBitStuffing, fsT1DsuLineBuildOut, fsT1DsuClock, fsT1DsuLineLoopBack, fsT1DsuTimeSlotDataRate, fsT1DsuTimeSlots,

fsT1DsuTimeSlotDataType, fsT1DsuYellowAlarm,

fsT1DsuLoopbackLocalAnalog, fsT1DsuLoopbackLocalDigit, fsT1DsuLoopbackRemoteAnalog, fsT1DsuLoopbackRemoteDigit

Table 11-1. fsFRAD subgroups

(2 of 3)

fsFRAD

11.1.3.3

Preparing an SNMP Connection

To configure and manage the unit, connect the terminal to the Supervisor port. Press Enter to access the system. Use the BANDIT menus to configure the system. When you have finished the session, save (write) the

configuration. Then select Exit from the Main Menu to terminate the session. To set up an SNMP connection, configure the following items:

• IP Address. This option allows the user to configure a valid IP Local Address via an async terminal. (See Section 4.2, Identifying the BANDIT in the Network.)

• Config port. This option allows the user to configure a port as Frame Relay, SLIP, or PPP via an async terminal, depending on the desired access method. An IP Routing table must also be configured.

• Ping. This option pings the configured IP Address to test connectivity. • Config agent trap. This option allows the user to configure the

snmpAgentTrapIpAddr parameter (within the snmpAgent subgroup) with the IP address of the Network Manager. The unit sends SNMP traps to that address.

fsE1DsuConfig fsE1DsuFrameFormat, fsE1DsuCRC, fsE1DsuClock,

fsE1DsuLineLoopBack, fsE1DsuTimeSlots, fsE1DsuDataType, fsE1DsuDisFrame, fsE1DsuAISTrans

fsGPT fsGPTTable, FsGPTEntry, fsGPTEntry, fsGPTIndex, fsGPTPathName, fsGPTPathType, fsGPTPort, fsGPTDLCINum,

fsGPTBackupPathName, fsGPTCallingAddress, fsGPTCalledAddress, fsGPTPVCNumber, fsGPTAdminStatus

fsIsdnConfig fsIsdnEnable, fsIsdnLocalPhel, fsIsdnSPID1, fsIsdnLocalPhe2, fsIsdnSPID2, fsIsdnSwitchSel

fsExtDialupDev fsExtDialupDevTable, FsExtDialupDevEntry, fsExtDialupDevEntry, fsExtDevIndex, fsExtDevPort, fsExtDevModemType, fsExtDevStatus fsPortProtocol FC-PORT-MI: fsPortDefinition. fsFrameRelay, fsAsyncEncapsulation,

fsBitSyncEncapsulation, fsSLIP, fsAsyncBurosEmulation, fsSyncBurosEmulation , fsSdlcRoute, fsByteSyncEncapsulation, fsTelnetTerminal, fsALC, fsSDLC2, fsX25NEW, fsXPAD, fsPPPNew, fsPPPMLink, fsEtherNet, fsTokenRing

Table 11-1. fsFRAD subgroups

fsFRAD

• Modify Get/Modify Set. These options allow the user to modify the Get and/or Set Community names (parameters snmpAgentGetCommunity and snmpAgentSetCommunity within the snmpAgent subgroup). • Select protocol. This option allows the user to select the appropriate

protocol under the fsPortProtocol MIB. Set the SNMP parameters for the protocol.

• Save. This option allows the user to save all the parameters into the unit’s non-volatile database by setting the fsSaveToNonVolatile parameter (within fsGeneralParms) to Initiate.

• Reset. This option allows the user to reset the unit by setting the fsResetUnit parameter (within fsGeneralParms) to Initiate.

11.1.3.4

Adding, Deleting, Modifying, and Viewing Table Entries

You can add, delete, modify, or view any table entry in the SNMP manager. The default value for table entries is View.

• To add an entry, put the cursor anywhere in the table, and select the dropdown list in the Status column. Select Add.

™ A row is added to the end of the table.

• To delete an entry, put the cursor in the row you want to delete, and select the dropdown list in the Status column. Select Delete.

™ The row is removed from the table.

• To modify an entry, put the cursor in the row you want to modify. Select the dropdown list in the Status column and select Modify. Make the necessary changes.

Note:

All entries are indexed by port number, protocol name, and other variables.

11.1.3.5

Using SNMP to View the BANDIT Menus

H

ow to Use the SNMP Manager to View the BANDIT Menus

Note:

This example uses Castle Rock Computing’s SNMPc™, a Windows-based SNMP Manager.

1

In the SNMP Manager, make sure you have configured an SNMP device for the BANDIT. (To configure the device settings, follow the instructions in the SNMP manager’s instruction manual.)

The BANDIT’s SNMP device configuration must include the following:

• The BANDIT’s IP address. This allows the SNMP Manager to find the BANDIT on the network.

• The BANDIT’s Get Community string. This allows the SNMP Manager to view the BANDIT’s settings.

Note:

The default value for the BANDIT’s SNMP Get Community string is listed in Appendix D, Default Passwords.

• The BANDIT’s Set Community string. This allows the SNMP Manager to configure and save the BANDIT’s settings.

Note:

The default value for the BANDIT’s SNMP Set Community string is listed in Appendix D, Default Passwords.

2

Select the BANDIT SNMP device.

Figure 11-4. BANDIT SNMP Device, Highlighted

3

On the top menu, or by right-clicking the SNMP device, select a Telnet connection. (On the example shown in Figure 11-5, using Castle Rock Computing’s SNMPc™, the menu choices are Tools,

Connect Telnet.)

Figure 11-5. Selecting a Telnet Connection through the SNMP Manager

Note:

Default passwords are listed in Appendix D.

™ The BANDIT’s main menu appears (Figure 11-6).

5

Use the BANDIT menus to configure and monitor the BANDIT.

Figure 11-6. BANDIT’s Main Menu, Telnetted through SNMP Manager

11.1.4

Using SNMP with Port Data Capture

Port Data Capture (PDC) can be used in conjunction with SNMP to enhance troubleshooting, especially when a problem is intermittent. The Encore Networks device can be programmed to send an SNMP trap under certain conditions—e.g., when an intermittent problem is actually occurring. The SNMP management station can be programmed to issue a script, based on this SNMP trap, that starts a Port Data Capture to run for a predetermined amount of time—e.g., 15 minutes. The network administrator can retrieve the captured data later for analysis.

11.2

Port Data Capture

Port Data Capture (PDC) is a powerful troubleshooting feature embedded in all of Encore Networks’ data products, including the BANDIT. The port trace functionality allows the unit to monitor data packets on any or all of a unit’s data ports. This feature helps resolve network problems by displaying live data for the ports.

PDC encompasses features to troubleshoot legacy traffic on serial interfaces and to troubleshoot IP traffic. No external test or monitoring hardware is required for monitoring data packets on the LAN, WAN, modem, serial, or expansion ports.

11.2.1

Features of Port Data Capture

All ports on all BANDIT models support Port Data Capture: • Ethernet LAN, WAN, and DMZ

• T1/E1 CSU • 56k/64k DSU • Serial

• Modem

The Remote Data Unit, used with the BANDIT Plus and the VSR-1200, also supports PDC on its Ethernet port and on all 12 serial ports.

PDC has the following features:

• The user can select the format—ASCII, EBCDIC, or hexadecimal—for the information the PDC displays.

Example:

Suppose a product at a remote branch is having problems with data traffic. The remote site can notify the central office by sending an SNMP trap/alarm to an SNMP Manager.

stored, or can be captured and sent to the central office for analysis. • PDC can be set to monitor data indefinitely or for a specific time period.

The default is 3 hours.

• The user can determine the amount of memory used to capture data. When starting a capture, the menu prompts for buffer size and capture slice. The user can accept the defaults or enter new values. The default capture slice is 64 bytes and the default buffer allocation is 75,000 bytes. The maximum allowed buffer is 3.4 Mbytes.

• PDC does not affect the operation of the Encore Networks product or any of its ports. PDC is passive; it requires no processing resource and runs quietly in the background.

Note:

The settings for Port Data Capture cannot be saved as part of the BANDIT device’s configuration.

H

ow to Use the Port Data Capture Feature

1

From the Main Menu, select System Administration >> Port Data

Capture.

™ The Data Capture—Port Selection and Status menu appears.

2

Do one of the following:

a Press the Escape key to return to the higher menu. b Select the port you wish to monitor.

™ The port’s Capture menu, similar to the following, is displayed. The menu shown here indicates that the port’s capture status is Off.

3

Do one of the following:

a To return to the Data Capture—Port Selection menu, press the

Escape key.

™ The Data Capture Port—Selection menu appears. Go to Step 2. b To capture this port’s data, select Start a Capture.

™ The following prompts appear. Answer them as appropriate for your network, and press Enter. (Or just press Enter, without typing anything, to accept the defaults.)

Capture of : SERIAL currently OFF ---1) Start a capture

2) Stop a capture 3) Clear capture buffer 4) Display captured data

5) Dump captured data to the screen

Enter Choice :

Enter max slice [64] :

Enter max buffer [75000] :

parameters, the following message appears.

™ Then the port’s Capture menu re-appears. Note that the port status indicates that capturing is in progress. Repeat Step 3.

c If you want to stop a capture before it times out, select Stop a

Capture.

™ The following message appears, followed by the port’s Capture menu, showing the port capture status as Stopped. Repeat Step 3.

d To clear the capture buffers, and to turn off a capture session, select

Clear Capture Buffer.

™ The following message appears, followed by the port’s Capture menu, showing capture status as Off. Repeat Step 3.

** Capture started **

Capture of : SERIAL currently CAPTURING Total=0 ---1) Start a capture

2) Stop a capture 3) Clear capture buffer 4) Display captured data

5) Dump captured data to the screen

Enter Choice :

** Capture stopped **

e To see a line-by-line display of the port data, select Display

Captured Data. Go to Step 4.

™ The menu for display mode appears.

f To see a complete display of the captured port data, select Dump

Captured Data to the Screen.

™ The format selection menu appears. Go to Step 6.

4

For a line-by-line display of captured data, do the following: a Select the mode you wish to view:

™ A menu to select the format appears:

b Select the format for the display.

™ The screen displays capture data for this port. (If there are no data, the message indicates that.) After the display, a line asks for the next line of data you wish to view.

5

Do one of the following:

a To stop the data display, press the Escape key.

™ The port’s Capture menu is redisplayed. Go to Step 3. b To change the display format, select Change Format.

™ The menu for display mode appears again. Go to Step 4a. c To view a specific line, select Specific.

™ A prompt asks for the line number.

• Type the line number and press Enter. ™ The display continues. Repeat Step 5. d To view the first line again, select First.

™ The display continues. Repeat Step 5. e To view the next line, select Next.

™ The display continues. Repeat Step 5.

6

For a complete display of captured data, do the following: a Select the format for the display.

*** Capture buffer for this port is empty ***

Enter [(F)irst, (N)ext, (S)pecific or (C)hange format]:

b To display the data, press the Enter key. ™ The information is displayed on the screen.

™ After the data have been displayed, the capture is automatically stopped.

™ Then the port’s Capture menu is redisplayed. Go to Step 3.

Start the file capture, press to display capture

*** Capture buffer for this port is empty ***

Stop the file capture

Capture of : SERIAL currently STOPPED Total=0 ---1) Start a capture

2) Stop a capture 3) Clear capture buffer 4) Display captured data

5) Dump captured data to the screen