Downloads |
Table Of Contents
Differences Between the NRP-1 and NRP-2
Supported Standards, MIBs, and RFCs
Configuring the NSP to Support the NRP-2 (Required)
Configuring NRP-2 Image Management on the NSP (Required)
Changing the NRP-2 Configuration Register Setting (Optional)
Reloading the NRP-2 (Optional)
Transferring an NRP-1 Configuration to an NRP-2 (Optional)
Configuring the NRP-2 (Required)
Methods Available for Accessing the NRP-2
Matching the MTU Size of the NRP-2 and Its Network Neighbors (Optional)
Displaying the MTU for the Main ATM Interface
Displaying the MTU for a Subinterface
Displaying the MTU for a Network Neighbor
Changing the MTU on a Network Neighbor
Verifying the MTU Size of the NRP-2 and Its Network Neighbors
Using the NSP as the SNMPv3 Proxy Forwarder (Optional)
Task 1: Configuring the NSP as the Proxy Forwarder
Task 2: Configuring the NRP-2 to Use the NSP as the Proxy Forwarder
Verifying the SNMPv3 Proxy Forwarder
Manual Disk Mirroring for Limited NSP Redundancy (Optional)
Modifying VPI and VCI Ranges (Optional)
Verifying the VPI and VCI Ranges
Using Console and System Logging (Optional)
Monitoring and Maintaining the NRP-2
NRP-2
This feature module describes the first release of Cisco 6400 NRP-2 and includes the following sections:
•
Supported Standards, MIBs, and RFCs
•
NRP-2 Overview
The node route processor 2 (NRP-2) for the Cisco 6400 platform allows aggregation and termination of large numbers of broadband subscribers while supporting Layer 3 and integrated high-touch services such as authentication, policy routing, and Network Address Translation (NAT). The Cisco 6400 receives subscribers over OC-3, OC-12, or DS-3 interfaces on node line cards (NLCs). The node switch processor (NSP) switches incoming virtual circuits (VCs) or virtual paths (VPs) to the appropriate NRP-2. The NRP-2 aggregates and terminates the incoming virtual circuits (VCs), offering extended services based on user and service profiles through the Service Selection Gateway (SSG).
Benefits
Increased Session Scalability
The NRP-2 increases the session capacity of the Cisco 6400, providing a dramatic reduction in cost per subscriber. See the release notes for the number of sessions supported by your software release.
Increased Bandwidth
The NRP-2 supports a 622-Mbps ATM interface to the backplane and a Gigabit Ethernet (GE) packet interface on the faceplate.
Note
Dual Processors
The NRP-2 hardware includes two processor subsystems. In Cisco IOS Release 12.1(4)DC, only one of the processors is used. In later software releases, the second processor will be used to provide increased session scalability.
Integrated System Management
Configuration storage, console traffic, and network management traffic are now controlled by the existing NSP, providing a more manageable and integrated platform. You can use a single console port on the NSP to access the console lines of all NRP-2s in the Cisco 6400 chassis, and use a single management Ethernet interface on the NSP to monitor all NRP-2s in the system.
Modular Design
The modular nature of the NRP-2 allows you to upgrade as your subscriber base grows. As the demand for services rises, you can add NRP-2 modules to the Cisco 6400 to provide increased session and bandwidth support.
Backward Compatibility
The NRP-2 can be deployed in a Cisco 6400 chassis with existing modules, including the node route processor 1 (NRP-1). This enables you to increase your network capacity without replacing the chassis.
Note
Note
Differences Between the NRP-1 and NRP-2
Table 1 shows the major differences between the NRP-1 and NRP-2.
Table 1 Differences Between NRP-1 and NRP-2
Session scalability
Hardware supports as many as 2000 sessions per NRP-1.
Hardware supports as many as 16,000 sessions per NRP-2.
Physical interfaces
Faceplate interfaces:
•
•
•
•
Backplane interfaces:
•
•
Faceplate interfaces:
•
Backplane interfaces:
•
•
Location of software images, configurations, and crash information
NRP-1 memory
(built-in or internal Flash)PCMCIA2 disk on NSP.
Message logging
Messages are logged on the NRP-1 as a local message.
NRP-2 messages are logged on both the NSP and NRP-2. NRP-2 messages on the NSP include the NRP-2 slot number.
Console line access
Direct external connection to NRP-1 console port or auxiliary port
Indirect external connection via the NSP. NSP contains a virtual communication server to access the NRP-2 console.
ROMMON3
ROMMON not upgradable;
NRP-1 ROM state information stored locally on NRP-1ROMMON is upgradable;
NRP-2 ROM state information is stored on the NSP PCMCIA disk.SNMP4
Standard SNMP services
Standard SNMP services, or can use the NSP as the proxy forwarder.
LED display5
None
On faceplate.
1 The PAM mailbox serial interface is used for internal system communication. Do not attempt to configure serial interfaces on the Cisco 6400.
2 PCMCIA = Personal Computer Memory Card International Association
3 ROMMON = ROM Monitor
4 SNMP = Simple Network Management Protocol
5 The LED display on the NRP-2 does not provide any information in Cisco IOS Release 12.1(4)DC.
NRP-2 Physical Interfaces
622-Mbps ATM interface to backplane
interface ATM 0/0/0
interface ATM slot/0/0
PAM mailbox serial interface1 to backplane
interface Serial 0/0/0
interface Serial slot/0/0
Gigabit Ethernet interface on faceplate
interface GigabitEthernet 0/0/0
—
1 The PAM mailbox serial interface is used for internal system communication. Do not attempt to configure any serial interfaces on the Cisco 6400.
Note
Management Through the NSP
The NRP-2 is designed for tighter integration with the node switch processor (NSP) of the Cisco 6400. The NSP provides the following functions for the NRP-2:
Image and File Storage
The NRP-2 has no local image or file storage. The NSP stores the following NRP-2 files on the PCMCIA disk:
•
•
•
•
Note
Whenever the NSP reloads, the NSP checks for the following directories on the PCMCIA disk. The NSP automatically creates any missing directories upon reload or PCMCIA disk insertion:
•
•
–
–
–
–
Note
You can create additional directories on the PCMCIA disk with the mkdir command. See "Cisco IOS File Management" in the Cisco IOS Configuration Fundamentals Configuration Guide for details.
System Logging
By default, each system log message created by the NRP-2 appears on the NSP as a local message, and the message is labeled with the slot number of the NRP-2 that created the message. Each system log message also appears on the NRP-2 console.
For more information on using system logging, see the "Using Console and System Logging (Optional)" section.
Console and Telnet Access
The NSP has been equipped with an internal communication server to access the NRP-2 console line. The NSP also has alias commands for telnetting to the NRP-2. For more information, see the "Methods Available for Accessing the NRP-2" section.
SNMPv3 Proxy Forwarder
The NSP and NRP-2 support SNMPv1, SNMPv2c and SNMPv3. The NSP uses the SNMPv3 Proxy Forwarder feature to:
•
•
For general information on using SNMP, see "Configuring Simple Network Management Protocol (SNMP)" in the Cisco IOS Configuration Fundamentals Configuration Guide. For information on the Proxy Forwarder feature, see the "Using the NSP as the SNMPv3 Proxy Forwarder (Optional)" section.
Restrictions and Limitations
For a complete list of restrictions and limitations, see the release notes for the software version running on your NRP-2. The release notes also include a list of hardware and software feature differences between the NRP-1 and NRP-2.
This section describes the following limitations:
Maximum Transmission Unit
The maximum transmission unit (MTU) of the NRP-2 ATM interface to the backplane is 1900 bytes. Any incoming packet larger than 1900 bytes is dropped by the NRP-2. To make sure that no incoming packets are larger than the NRP-2 MTU, see the "Matching the MTU Size of the NRP-2 and Its Network Neighbors (Optional)" section.
VPI and VCI Limitations
VPI and VCI values on the NRP-2 must share 14 bits. By default, VPI values are limited to 4 bits (0-15), and VCI values are limited to 10 bits (0-1023). You can change the VPI and VCI ranges, but together the VPI and VCI values cannot exceed 14 bits. To change the allowed VPI and VCI values, see the "Modifying VPI and VCI Ranges (Optional)" section.
Related Documents
•
Supported Platforms
NRP-2 is supported on the Cisco 6400.
Supported Standards, MIBs, and RFCs
Standards
None
MIBs
•
•
For lists of MIBs supported by the Cisco 6400, see MIBs Supported by the Cisco 6400. To download MIB modules, go to the Cisco MIB web site on Cisco Connection Online (CCO) at http://www.cisco.com/public/sw-center/netmgmt/cmtk/mibs.shtml.
RFCs
None
Prerequisites
•
•
•
Configuration Tasks
See the following sections for NRP-2 configuration tasks. Each task in the list indicates if it is optional or required:
•
•
•
•
•
•
•
•
•
Configuring the NSP to Support the NRP-2 (Required)
See the following sections for NSP configuration tasks for supporting NRP-2. Each task in the list indicates if the task is optional or required:
•
•
Configuring NRP-2 Image Management on the NSP (Required)
The NSP controls and manages the NRP-2 image download process. Cisco recommends that you store all NRP-2 images on the NSP PCMCIA disk, but you can also store NRP-2 images on a TFTP, FTP, or rcp server.
For each NRP-2 in your Cisco 6400 system, enter the following command on the NSP in global configuration mode:
Without the hw-module (image) command in the NSP configuration, the NRP-2 attempts to load the default image (c6400r2sp-g4p5-mz) from the disk0:/images/ directory.
Timesaver
Example
In the following example, the NRP-2 in slot 2 of the Cisco 6400 chassis has three images assigned with different priorities, while the NRP-2 in slot 3 has only one image assigned:
hw-module slot 2 image c6400r2sp-g4p5-mz.DC priority 2hw-module slot 2 image tftp://10.1.1.1/c6400r2sp-g4p5-mz.DC priority 3hw-module slot 2 image disk0:MyDir/c6400r2sp-g4p5-mz.DC priority 4hw-module slot 3 image c6400r2sp-g4p5-mz.DC priority 2
Changing the NRP-2 Configuration Register Setting (Optional)
The configuration register defaults to the correct setting for normal operation. You should not change this setting unless you want to enable the break sequence or switch ROMMON devices.
To change the NRP-2 configuration register setting, enter the following command in global configuration mode:
Switch(config)# hw-module slot slot config-register value1
Changes the configuration register setting of the NRP-2 in the specified slot.
1 For specific configuration register values, see the command reference for hw-module.
Example
In the following example, an NRP-2 in slot 3 is set to boot to ROMMON, where ROMMON runs from the image found in BootFROM1. If you enter the boot ROMMON command, the NRP-2 loads the specified image from the disk0:/images/ directory.
hw-module slot 3 config-register 0x2100hw-module slot 3 image c6400r2sp-g4p5-mz.DC priority 2Reloading the NRP-2 (Optional)
Use one of the following commands to reload the NRP-2:
Switch# hw-module slot slot reset
NSP
Simulates removal and insertion of the NRP-2 in the selected slot. The NRP-2 reloads.
Router# reload
NRP-2
Reloads the NRP-2.
Note
Transferring an NRP-1 Configuration to an NRP-2 (Optional)
This section describes how to properly transfer an existing NRP-1 configuration to an NRP-2. Complete the following steps:
Step 1
Router# copy flash:my.cfg tftp://10.1.1.1/my.cfgStep 2
Step 3
Step 4
Switch# clear facility-alarm cardtype 4Step 5
Switch# copy tftp://10.1.1.1/my.cfg disk0:/slot4/nrp2-startup-configStep 6
Switch# hw-module slot 4 reset
Configuring the NRP-2 (Required)
Once you access the NRP-2 command line interface, you can configure the NRP-2 exactly as you would configure an NRP-1. See the following section, "Methods Available for Accessing the NRP-2," to access the NRP-2 command line interface.
Note
Methods Available for Accessing the NRP-2
There are two methods available for accessing the NRP-2:
•
•
Accessing the NRP-2 Console Through the NSP
The NSP is equipped with an internal communication server for accessing the NRP-2 console line. To access the NRP-2 console line, telnet to the NSP as a communication server, using the port numbers shown in Table 2 to select the NRP-2.
To exit the NRP-2 console line without closing the console connection, use the escape sequence Ctrl-Shift-6. To close the NRP-2 console line connection, use the exit command.
Example
Suppose the NSP in your Cisco 6400 system has the management IP address 10.1.5.4. To access the console line of the NRP-2 in Slot 6 of the same Cisco 6400 chassis, use the telnet command:
device# telnet 10.1.5.4 2006Trying 10.1.5.4, 2006 ... OpenNRP-2#To return to the device prompt without closing the NRP-2 console line connection, enter the escape sequence Ctrl-Shift-6 at the NRP-2 prompt. Notice that the escape sequence does not appear as you enter it in the command-line interface (CLI):
NRP-2# Ctrl^device#To return to the connected NRP-2 console line, enter a blank line at the device prompt:
device#[Resuming connection 1 to 10.1.5.4 ... ]NRP-2#To close the NRP-2 console line connection, use the escape sequence to return to the device prompt, and then use the exit command.
NRP-2# Ctrl^device# exit(You have open connections) [confirm]Closing:10.1.5.4 !device con0 is now availablePress RETURN to get started.device>Telnetting to the NRP-2 from the NSP
The NSP is equipped with command aliases for telnetting to the NRP-2s in the same Cisco 6400 chassis. To telnet to the NRP-2, use the following NSP command alias in EXEC mode:
Note
To exit the NRP-2 VTY line without closing the Telnet session, use the escape sequence Ctrl-Shift-6. To close the NRP-2 Telnet session, use the exit command.
Example
Suppose you want to telnet to the NRP-2 from a device outside your Cisco 6400 system, and the NSP in the Cisco 6400 has the management IP address 10.1.5.4.
To telnet to the NRP-2, telnet first to the NSP, and then use the nrps command alias to telnet to the NRP-2:
device# telnet 10.1.5.4Trying 10.1.5.4 ... OpenUser Access VerificationPassword:NSP>NSP> nrps6Trying 10.6.0.2 ... OpenNRP-2>To exit the NRP-2 prompt without closing the NRP-2 Telnet session, use escape sequence Ctrl-Shift-6 at the NRP-2 prompt. Notice that the escape sequence does not appear as you enter it in the command-line interface (CLI):
NRP-2> Ctrl^device#The escape sequence returns the prompt to the original Telnet device, instead of the NSP. To return to the NRP-2 Telnet session, enter a blank line at the device prompt:
device#[Resuming connection 1 to 10.1.5.4 ... ]NRP-2>To close the Telnet session to the NRP-2 and return to the NSP prompt, use the exit command.
NRP-2> exit[Connection to 10.6.0.2 closed by foreign host]NSP>Matching the MTU Size of the NRP-2 and Its Network Neighbors (Optional)
The NRP-2 ATM interface to the backplane supports a maximum packet size, or maximum transmission unit (MTU), of 1900 bytes. The ATM interface drops any incoming packet larger than 1900 bytes. To prevent packets from being dropped, make sure that the MTU sizes match for both ends of VCs.
Displaying the MTU for the Main ATM Interface
To check the current MTU size on the NRP-2 ATM main interface, use the show interface atm 0/0/0 EXEC command, which displays the following fields:
•
•
Example—Main ATM Interface
NRP-2# show interface atm 0/0/0...MTU 1870 bytes, sub MTU 1850, BW 599040 Kbit, DLY 60 usec,
...Displaying the MTU for a Subinterface
To display the current MTU size on the NRP-2 ATM subinterface, use the show interface atm 0/0/0.subinterface EXEC command. This command displays only one "MTU" field that represents the MTU setting for the subinterface.
Example—ATM Subinterface
NRP-2# show interface atm 0/0/0.100...Displaying the MTU for a Network Neighbor
To check the current MTU size on the network neighbor, use the show interface atm EXEC command for the interface used to terminate the VC from the NRP-2.
Example—Cisco 7200
7200# show interface atm 1/0ATM1/0 is up, line protocol is upHardware is ENHANCED ATM PAExample—Cisco 6400 NRP-1
NRP-1# show interface atm 0/0/0ATM0/0/0 is up, line protocol is upHardware is ATM-SARChanging the MTU on the NRP-2
To adjust the MTU size on the NRP-2, complete the following steps beginning in global configuration mode:
Changing the MTU on a Network Neighbor
To adjust the MTU size on the network neighbor, complete the following steps beginning in global configuration mode:
Example
Suppose that the show interface atm 0/0/0 EXEC command displayed the MTU size of 1900 bytes on the NRP-2, and the MTU size of 4470 bytes on a neighboring NRP-1.
NRP-2# show interface atm 0/0/0ATM0/0/0 is up, line protocol is upHardware is NRP2 ATM SAR
NRP-1-neighbor# show interface atm 0/0/0ATM0/0/0 is up, line protocol is upHardware is ATM-SARIn the following example, the network neighbor MTU size is reduced to 1900 to match the MTU size of the NRP-2.
!interface ATM0/0/0Verifying the MTU Size of the NRP-2 and Its Network Neighbors
To verify that the MTU size matches for the NRP-2 and its network neighbors, complete the following steps for each network neighbor:
Step 1
Step 2
Step 3
Using the NSP as the SNMPv3 Proxy Forwarder (Optional)
The SNMPv3 Proxy Forwarder feature enables all NSP and NRP-2 components of the Cisco 6400 system to be managed as one functional entity. With the Proxy Forwarder feature enabled, the NSP:
•
•
To configure the Proxy Forwarder feature, complete the following tasks:
•
•
Task 1: Configuring the NSP as the Proxy Forwarder
To enable the NSP to act as the proxy forwarder for the NRP-2s in the Cisco 6400 chassis, enter the following NSP commands, beginning in global configuration mode:
When you complete the previous steps, the NSP automatically generates snmp-server user and snmp-server group commands in the configuration.
Each time the NSP reloads or you insert an NRP-2 into the chassis, the NSP automatically generates snmp-server engineID commands in the configuration.
Note
Example
In the following example, the NSP is configured to act as the proxy forwarder:
snmp-server group usmgrp v3 noauthsnmp-server user usmusr usmgrp v3snmp-server forwardersnmp-server host 10.100.100.100 vrf 6400-private version 3 noauth trapusrThe previous commands cause the NSP to automatically generate the following commands:
snmp-server engineID remote 10.3.0.2 vrf 6400-private 80000009030000107BA9C7A0snmp-server user trapusr trapusr v3snmp-server user trapusr trapusr remote 10.3.0.2 vrf 6400-private v3snmp-server user usmusr usmgrp remote 10.3.0.2 vrf 6400-private v3snmp-server group trapusr v3 noauth notify *tv.FFFFFFFF.FFFFFFFFTask 2: Configuring the NRP-2 to Use the NSP as the Proxy Forwarder
To configure the NRP-2 to communicate with the NSP as the proxy forwarder, complete the following steps beginning in global configuration mode:
When you complete the previous steps, the NRP-2 automatically generates snmp-server user and snmp-server group commands in the configuration.
If you do not select any specific types of traps, the NRP-2 also automatically generates snmp-server enable traps commands to specify all available types of traps.
Note
Example
In the following example, the NRP-2 is configured to allow the NSP to act as the proxy forwarder:
snmp-server group usmgrp v3 noauthsnmp-server user usmusr usmgrp v3snmp-server enable trapssnmp-server host 10.3.0.1 vrf 6400-private version 3 noauth trapusrThe previous commands cause the NRP-2 to automatically generate the following commands:
snmp-server user trapusr trapusr v3snmp-server group trapusr v3 noauth notify *tv.FFFFFFFF.FFFFFFFFsnmp-server enable traps snmp authentication linkdown linkup coldstartsnmp-server enable traps configsnmp-server enable traps syslogsnmp-server enable traps bgpsnmp-server enable traps ipmulticastsnmp-server enable traps rsvpsnmp-server enable traps frame-relaysnmp-server enable traps rtrVerifying the SNMPv3 Proxy Forwarder
To verify successful configuration of the SNMPv3 proxy forwarder feature, use the more system:running-config EXEC command. On both the NSP and NRP-2, check that you properly configured the commands described in the previous tasks.
Also check that the automatically generated commands correctly appear on both the NSP and NRP-2 running configurations. On the NSP, the three automatically generated commands that include an IP address are generated for every active NRP-2 in the chassis. The other automatically generated commands are created only once, regardless of the number of active NRP-2s installed in the chassis.
Manual Disk Mirroring for Limited NSP Redundancy (Optional)
NSP Redundancy is limited in Cisco IOS Release 12.1(4)DB, because automatic disk mirroring of the PCMCIA disk in the NSP is not available in that release, and the NRP-2 relies on the NSP PCMCIA disk for file storage.
To perform manual disk mirroring, complete the following steps from the primary NSP:
Step 1
Switch# dirDirectory of disk0:/3296 drw- 0 Aug 08 2000 21:20:40 images3297 drw- 0 Aug 08 2000 21:20:42 slot13298 drw- 0 Aug 08 2000 21:20:42 slot23299 drw- 0 Aug 08 2000 21:20:42 slot33300 drw- 0 Aug 08 2000 21:20:42 slot43301 drw- 0 Aug 08 2000 21:20:42 slot53302 drw- 0 Aug 08 2000 21:20:42 slot63303 drw- 0 Aug 08 2000 21:20:42 slot73304 drw- 0 Aug 08 2000 21:20:42 slot820819968 bytes total (20434944 bytes free)Switch#Step 2
Switch# dir sec-disk0:Directory of sec-disk0:/3296 drw- 0 Aug 08 2000 21:20:40 images3297 drw- 0 Aug 08 2000 21:20:42 slot13298 drw- 0 Aug 08 2000 21:20:42 slot23299 drw- 0 Aug 08 2000 21:20:42 slot33300 drw- 0 Aug 08 2000 21:20:42 slot43301 drw- 0 Aug 08 2000 21:20:42 slot53302 drw- 0 Aug 08 2000 21:20:42 slot63303 drw- 0 Aug 08 2000 21:20:42 slot73304 drw- 0 Aug 08 2000 21:20:42 slot820819968 bytes total (20434944 bytes free)Switch#Step 3
a.
Switch# format sec-disk0:b.
Switch# mkdir sec-disk0/images/Switch# mkdir sec-disk0/slot1/Switch# mkdir sec-disk0/slot2/...Switch# mkdir sec-disk0/slot8/Step 4
Switch# copy disk0:/images/c6400r2sp-g4p5-mz.DC sec-disk0:/images/c6400r2sp-g4p5-mz.DCSwitch# copy disk0:/slot7/nrp2-startup-config sec-disk0:/slot7/nrp2-startup-configSwitch# copy disk0:/slot7/nrp2_rommon_nv.0 sec-disk0:/slot7/nrp2_rommon_nv.0
Note
Modifying VPI and VCI Ranges (Optional)
By default, VPI values are limited to 4 bits (0-15), and VCI values are limited to 10 bits (0-1023). You can change the VPI and VCI ranges, but the VPIs and VCIs must share 14 bits.
To change the VPI and VCI ranges, use the following commands beginning in global configuration mode:
Step 1
Router(config)# interface atm 0/0/0
Selects the ATM interface on the NRP-2.
Step 2
Router(config-if)# atm vc-per-vp number
Sets the maximum number of allowed VCIs. The number of allowed VPIs is adjusted accordingly, such that the combination of VPIs and VCIs does not exceed 14 bits. See Table 3 for the allowed entries. The default number is 1023.
Note
Table 3 Allowed Entries for number Argument
64
0 - 63
6
0 - 255
8
128
0 - 127
7
0 - 127
7
256
0 - 255
8
0 - 63
6
512
0 - 511
9
0 - 31
5
1024
0 - 1023
10
0 - 15
4
2048
0 - 2047
11
0 - 7
3
4096
0 - 4095
12
0 - 3
2
8192
0 - 8191
13
0 - 1
1
1 Notice that the smallest allowed number entry is 64. The next possible value would be 32 (VCI range 0 - 31), but VCI values 0 through 31 are reserved by the ATM forum for particular functions (such as ILMI).
Example
In the following example, the VCI range is set to 2048 values (0 - 2047), and the VPI range is set to 8 values (0 - 7):
!interface ATM0/0/0no ip addressVerifying the VPI and VCI Ranges
To verify successful configuration of the VPI and VCI ranges, complete one or both of the following steps:
Step 1
Router# more system:running-config...interface ATM0/0/0no ip addressStep 2
Router# show controller atm 0/0/0...*** SE64 General Data ***SE64_MAX_TX_PTYPE_HOLDER = 49152SE64_PARTICLE_POOL = 32255
Using Console and System Logging (Optional)
By default, each system log message created by the NRP-2 appears on the NSP as a local message, and the message is labeled with the slot number of the NRP-2 that created the message. Each system log message also appears on the NRP-2 console.
To control console and system logging, use the following commands:
For more information on system and console logging, see the "Redirecting Debug and Error Message Output" section of the "Using Debug Commands" chapter of the Cisco IOS Debug Command Reference, Release 12.1.
Troubleshooting Tips
Use the following debug commands to troubleshoot the NRP-2:
Monitoring and Maintaining the NRP-2
Examples
In the following example, the who EXEC command is used to identify the connection from the NSP to the NRP-2 console, and the clear privileged EXEC command is used to close the NRP-2 console session:
NSP# whoLine User Host(s) Idle Location* 0 con 0 idle 00:00:00In the following example, the show line EXEC command is entered on the NSP to look at the console connection to the NRP-2:
NSP# show line 6Tty Typ Tx/Rx A Modem Roty AccO AccI Uses Noise Overruns Int* 6 TTY 0/0 - - - - - 7 0 0/0 -Line 6, Location:"", Type:"XTERM"Length:24 lines, Width:80 columnsStatus:Ready, Connected, ActiveCapabilities:EXEC Suppressed, Software Flowcontrol In,Software Flowcontrol OutModem state:ReadyModem hardware state:CTS DSR DTR RTSSpecial Chars:Escape Hold Stop Start Disconnect Activation^^x none ^S ^Q noneTimeouts: Idle EXEC Idle Session Modem Answer Session Dispatch00:10:00 never none not setIdle Session Disconnect WarningneverLogin-sequence User Response00:00:30Autoselect Initial Waitnot setModem type is unknown.Session limit is not set.Time since activation:00:03:26Editing is enabled.History is enabled, history size is 10.DNS resolution in show commands is enabledFull user help is disabledAllowed transports are telnet. Preferred is telnet.No output characters are paddedNo special data dispatching charactersNSP#In the following example, the show line EXEC command is used to view the NRP-2 console line parameters from the NRP-2:
NRP-2> show line con 0Tty Typ Tx/Rx A Modem Roty AccO AccI Uses Noise Overruns Int* 0 CTY - - - - - 0 0 0/0 -Line 0, Location:"", Type:""Length:24 lines, Width:80 columnsStatus:PSI Enabled, Ready, Active, Automore OnCapabilities:Software Flowcontrol In, Software Flowcontrol OutModem state:ReadySpecial Chars:Escape Hold Stop Start Disconnect Activation^^x none ^S ^Q noneTimeouts: Idle EXEC Idle Session Modem Answer Session Dispatchnever never none not setIdle Session Disconnect WarningneverLogin-sequence User Response00:00:30Autoselect Initial Waitnot setModem type is unknown.Session limit is not set.Time since activation:00:09:09Editing is enabled.History is enabled, history size is 10.DNS resolution in show commands is enabledFull user help is disabledAllowed transports are pad telnet rlogin. Preferred is telnet.No output characters are paddedNo special data dispatching charactersNRP-2>In the following example, the show controller async EXEC command is used to look at the NRP-2 PAM mailbox serial interface:
NRP-2> show controller asyncPam bus async console controllerPAM bus data for mailbox at 0x1C00FFC0magic1 = 0xDEADBABE, magic2 = 0x21524541in_data = 0x0000000D, out_data = 0x0000000Ain_status.received_break = 0out_status.received_break = 0tx_owned = TRUE, rx_owned = FALSEBuffer informationRx ttycnt 0Tx ttycnt 16BRx Buffs:inpk 0/0 inheadpk 0 dataq 0 0 0pakq 0 0 0Tx Buffs:outpk 0 txpkq 0 0 0Rx totalin 325 Tx totalout 7933NRP-2>In the following example, the show controller async EXEC command is entered on the NSP to view the PAM mailbox serial interface for the NRP-2 in slot 6:
NSP# show controller asyncAsync NRP2 Pam bus controllerTTY line 1 not availableTTY line 2 not availableTTY line 3 not availableTTY line 4 not availableTTY line 5 not availableTTY line 6PAM bus data for mailbox at 0xA8A8FFC0magic1 = 0xDEADBABE, magic2 = 0x21524541in_data = 0x0000000D, out_data = 0x0000003Ein_status.received_break = 0out_status.received_break = 0tx_owned = TRUE, rx_owned = FALSEBuffer informationRx ttycnt 0Tx ttycnt 0Rx Buffs:inpk 0/0 inheadpk 0 dataq 0 0 0pakq 0 0 0Tx Buffs:outpk 0 txpkq 0 0 0Rx totalin 1302 Tx totalout 69TTY line 7 not availableTTY line 8 not availableTTY line 9 not availableTTY line 10 not availableTTY line 11 not availableTTY line 12 not availableTTY line 13 not availableTTY line 14PAM bus data for mailbox at 0xA8E8FFC0magic1 = 0xDEADBABE, magic2 = 0x21524541in_data = 0x00000000, out_data = 0x00000000in_status.received_break = 0out_status.received_break = 0tx_owned = TRUE, rx_owned = FALSEBuffer informationRx ttycnt 0Tx ttycnt 0Rx Buffs:inpk 0/0 inheadpk 0 dataq 0 0 0pakq 0 0 0Tx Buffs:outpk 0 txpkq 0 0 0Rx totalin 0 Tx totalout 0TTY line 15 not availableTTY line 16 not availableNSP#NRP-2 Command Reference
This section documents new or modified commands. All other commands used with this feature are documented in the Cisco IOS Release 12.1 command reference publications.
show controllers atm 0/0/0
To display information on the physical ATM interface of the Cisco 6400 NRP-2 or NRP-1, use the show controllers atm 0/0/0 privileged EXEC command.
Cisco 6400 NRP-2
show controllers atm 0/0/0
Cisco 6400 NRP-1
show controllers atm 0/0/0 [detailed | scheduler | vc vpi/vci]
Syntax Description
Defaults
On the NRP-2, the default output shows all available information on the ATM interface.
On the NRP-1, the default output shows only segmentation and reassembly (SAR) controller information.
Command Modes
Privileged EXEC
Command History
Examples
In the following NRP-2 example, the output displays all available SAR controller information:
NRP-2# show controllers atm 0/0/0*** SE64 General Data ***Resources:Thold Thold per-VCPool Total Used Free Norm Sys Limit VCs------ ----- ----- ----- ----- ----- ------ -----TX-VBR 3273 1 3272 3241 3273 3273 1TX-UBR 409 8 401 377 409 2RX 32255 0 32255 21504 21568 3583 3MP-hld 49152 8 49144Performance:Throttled Throttled Throttled SpinPath Total Queued Total Sys Hi Pri avg/max---- ----- ------ ---------- ---------- ---------- -------TX 3682 8 0 0 0 0/128RX 32255 0 0 1/128Other:TX hw Links = 2 RX Free (tbl) = 32255VPI/VCI bits = 3/11 SAR Rev = D*** SE64 Global Statistics ***RX Path:rx_giant_discard = 0 rx_misc_discard = 0rx_pkt = 4 rx_drop_vc_bad = 0rx_drop_crc = 0 rx_drop_runt = 0rx_drop_vc_del = 0 rx_drop_giant = 0rx_drop_throttle = 0RX OAM Path:rx_oam_spin_int = 0 rx_oam_spin_poll = 0rx_oam = 0 rx_oam_drop_buf = 0rx_oam_drop_crc_10 = 0RX General:rx_count = 0 rx_pkt_spin_start = 4rx_pkt_spin_total = 4 rx_spin_int = 4rx_spin_poll = 0 rx_pkt_clp = 0rx_pkt_ci = 0TX Path:tx_pkt_safe_start = 8 tx_pkt_fast = 0tx_drop_idb_down = 0 tx_drop_vc_down = 0tx_drop_vc_del = 0 tx_drop_1par_clone = 0tx_drop_2par_room = 0 tx_drop_2par_coal = 0tx_drop_gt2par = 0 tx_drop_credit = 0tx_drop_credit_sys = 0 tx_drop_credit_pri = 0tx_drop_oam_f4 = 0 tx_drop_pkt_len_0 = 0tx_drop_pkt_align = 0 tx_drop_pkt_mp = 0TX General:tx_count_vbr = 0 tx_count_ubr = 8tx_tbl_count_vbr = 1 tx_tbl_count_ubr = 17tx_vc_limit_vbr = 3273 tx_pkt_spin_start = 0tx_pkt_spin_total = 0 tx_spin_int = 0tx_spin_poll = 0 tx_combine = 0tx_2par_coal = 0SE64 stats interrupts:tx_desc_wm = 0 tx_tmp_cb_full = 0tx_cb_full = 0 abr_sched_drift = 0SE64 error interrupts:rx_stat_rpt_ring_ful = 0 tx_stat_rpt_ring_ful = 0rm_cell_ring_full = 0 rx_buf_pool1_mt = 0rx_buf_pool2_mt = 0 rx_buf_pool3_mt = 0tx_buf_pkt_desc_mt = 0 rx_cb_full = 0rx_tmp_cb_full = 0 fail_sched_abr_vc = 0crm = 0 biu_addr = 0rx_cam_mult_hit = 0 tx_cam_mult_hit = 0rx_hec = 0 data_parity = 0In the following NRP-1 example, the output consists only of the SAR controller information:
NRP-1# show controllers atm 0/0/0Interface ATM0/0/0Hardware is ATM-SARPCI registers:bus_no=0, device_no=4CFID=0xA102104C, CFCS=0x02000006, CFRV=0x02030002, CFLT=0x0000FF00CFBA=0x4A000000, CFIT=0x02010100*** TI1575 SAR at address 0x3A000000 ***Receive/Transmit Statisticsrx_isrs: 0 rx_isr_pkts: 1 rx_isr_bufs: 0rx_cells_ovf: 0 tx_cells_ovf: 0 hec_errors_ovf: 0rx_unkn_prot: 314 rx_aal5_disc: 0 rx_pkt_ovf: 0unkn_prot_ovf:0 aal5_disc_ovf: 0 tx_count: 0rx_crc_error: 0 rx_no_buf: 0 rx_timeout: 0rx_abort: 0 rx_cong_cells: 0 rx_freeze: 0rx_no_valbuf: 0 rx_bad_vc: 0 fallback act: 0tx_abort: 0 tx_no_desc: 0 tx_align: 0tx_freeze: 0 disabled: 0 enabled: 0tx_clones: 0 tx_xmt_paks: 3 teardown_vc: 0tx_pend_count_negative: 0tx_forced: 0 (0)tx_max_queued: 6144 seg_ring_size: 32tx output drops: 0pkt_too_big: 0 tx_pak_failed: 0idb_down: 0 invalid_pkt_type: 0invalid_vcd: 0 vc_ring_full: 0over_max_queued: 0 slot_owned_by_chip: 0vc_not_in_use: 0invalid_addr_count: 0PCI Statisticsdetect_parity 0 system_error 0 master_abort 0rx_target_abort 0 sig_target_abort 0 data_parity 0Internal registersconfig: 0x6037 status: 0x2000040 imask: 0xC381ratcount: 0x800 globrat: 0x79 rxunkn: 0x10000010txcompsize: 0x7FF rxcompsize: 0x1FF txsegsize: 0x1Faal5discard:0x0 hecerrors: 0x0 unknprot: 0x14Crxcells: 0x1 txcells: 0x1B schedsize: 0x1txqueue: 0x80002009(spinerr:0) txpause: 0x0 chancount: 0x5txcompring: 0x311A00C rxcompring: 0x3114020
Structures common to all VCsreceive free buffer ringaddress: 0x3110820 buf size: 10 ring size: 63 sar_indx: 1 drv_indx: 1receive completion ringaddr: 0x3114000 indx: 1transmit completion ringaddr: 0x311A000 indx: 3In the following NRP-1 example, the output consists of all available information:
NRP-1# show controllers atm 0/0/0 detailedInterface ATM0/0/0Hardware is ATM-SARPCI registers:bus_no=0, device_no=4CFID=0xA102104C, CFCS=0x02000006, CFRV=0x02030002, CFLT=0x0000FF00CFBA=0x4A000000, CFIT=0x02010100*** TI1575 SAR at address 0x3A000000 ***Receive/Transmit Statisticsrx_isrs: 0 rx_isr_pkts: 1 rx_isr_bufs: 0rx_cells_ovf: 0 tx_cells_ovf: 0 hec_errors_ovf: 0rx_unkn_prot: 514 rx_aal5_disc: 0 rx_pkt_ovf: 0unkn_prot_ovf:0 aal5_disc_ovf: 0 tx_count: 0rx_crc_error: 0 rx_no_buf: 0 rx_timeout: 0rx_abort: 0 rx_cong_cells: 0 rx_freeze: 0rx_no_valbuf: 0 rx_bad_vc: 0 fallback act: 0tx_abort: 0 tx_no_desc: 0 tx_align: 0tx_freeze: 0 disabled: 0 enabled: 0tx_clones: 0 tx_xmt_paks: 3 teardown_vc: 0tx_pend_count_negative: 0tx_forced: 0 (0)tx_max_queued: 6144 seg_ring_size: 32tx output drops: 0pkt_too_big: 0 tx_pak_failed: 0idb_down: 0 invalid_pkt_type: 0invalid_vcd: 0 vc_ring_full: 0over_max_queued: 0 slot_owned_by_chip: 0vc_not_in_use: 0invalid_addr_count: 0PCI Statisticsdetect_parity 0 system_error 0 master_abort 0rx_target_abort 0 sig_target_abort 0 data_parity 0Internal registersconfig: 0x6037 status: 0x2000040 imask: 0xC381ratcount: 0x800 globrat: 0x79 rxunkn: 0x10000010txcompsize: 0x7FF rxcompsize: 0x1FF txsegsize: 0x1Faal5discard:0x0 hecerrors: 0x0 unknprot: 0x214rxcells: 0x1 txcells: 0x1B schedsize: 0x1txqueue: 0x80002009(spinerr:0) txpause: 0x0 chancount: 0x5txcompring: 0x311A00C rxcompring: 0x3114020Structures common to all VCsreceive free buffer ringaddress: 0x3110820 buf size: 10 ring size: 63 sar_indx: 1 drv_indx: 1receive completion ringaddr: 0x3114000 indx: 1transmit completion ringaddr: 0x311A000 indx: 3
*** VC information and associated 1575 structures ***seg ring: 5 ringaddr: 0x311C400 ringindx:0 pendindx:0tx dma: 5 ctrlring: 0xC47100 pktcnt: 0rword10: 0x0 rword11: 0x0rword20: 0x0 rword21: 0x0 rword22: 0x0 rword23: 0x0pxmt 0 queued: 0VCs mapped to this ringvcd: 1 cellhdr: 0x1E00640 encap: 0 crcerror: 0rx dma: 5 config: 0x24000000 ctrlrxring: 0x80000200 timecnt: 0xC8000lookup: 2 channel: 5 vpivci: 0x1E0064seg ring: 6 ringaddr: 0x311C480 ringindx:0 pendindx:0tx dma: 6 ctrlring: 0xC47120 pktcnt: 0rword10: 0x0 rword11: 0x0rword20: 0x0 rword21: 0x0 rword22: 0x0 rword23: 0x0pxmt 0 queued: 0VCs mapped to this ringvcd: 2 cellhdr: 0x2800C80 encap: 0 crcerror: 0rx dma: 6 config: 0x24000000 ctrlrxring: 0x80000400 timecnt: 0xC8000lookup: 3 channel: 6 vpivci: 0x2800C8seg ring: 7 ringaddr: 0x311C500 ringindx:0 pendindx:0tx dma: 7 ctrlring: 0xC47140 pktcnt: 0rword10: 0x0 rword11: 0x0rword20: 0x0 rword21: 0x0 rword22: 0x0 rword23: 0x0pxmt 0 queued: 0VCs mapped to this ringvcd: 3 cellhdr: 0xA0 encap: 0 crcerror: 0rx dma: 7 config: 0x24000000 ctrlrxring: 0x80000600 timecnt: 0xC8000lookup: 0 channel: 7 vpivci: 0xAseg ring: 8 ringaddr: 0x311C580 ringindx:0 pendindx:0tx dma: 8 ctrlring: 0xC47160 pktcnt: 0rword10: 0x0 rword11: 0x0rword20: 0x0 rword21: 0x0 rword22: 0x0 rword23: 0x0pxmt 0 queued: 0VCs mapped to this ringvcd: 4 cellhdr: 0x500 encap: 0 crcerror: 0rx dma: 8 config: 0x24000000 ctrlrxring: 0x80000800 timecnt: 0xC8000lookup: 1 channel: 8 vpivci: 0x50seg ring: 9 ringaddr: 0x311C600 ringindx:3 pendindx:3tx dma: 9 ctrlring: 0xC47183 pktcnt: 0rword10: 0x663C0000 rword11: 0x33CE274rword20: 0x0 rword21: 0x33CDFC4 rword22: 0x0 rword23: 0x0pxmt 0 queued: 0VCs mapped to this ringvcd: 5 cellhdr: 0x3200640 encap: 0 crcerror: 0rx dma: 9 config: 0x24000000 ctrlrxring: 0x80000A00 timecnt: 0xC8000lookup: 4 channel: 9 vpivci: 0x320064*** TI1585/1585 Scheduler at address 0x3A040000 ***Configuration/Statisticsline bw: 149760 min vc bw: 64 total slots: 2free slots: 21585 internal registersconfig: 0x227 status: 0x1E imask: 0x0clkfreq: 0x18FCA1 revnum: 0x0 acrlow: 0x80000000acrok: 0x800000001585 connection config/statusscheduler id 5type: VBR pcr: 353207 scr: 353207 mbs: 91rtv: 0x100scheduler id 6type: VBR pcr: 353207 scr: 353207 mbs: 91rtv: 0x100scheduler id 7type: VBR pcr: 353207 scr: 353207 mbs: 91rtv: 0x100scheduler id 8type: VBR pcr: 353207 scr: 353207 mbs: 91rtv: 0x100scheduler id 9type: VBR pcr: 353207 scr: 353207 mbs: 91rtv: 0x100In the following NRP-1 example, the output consists of only the SAR scheduler information:
NRP-1# show controllers atm 0/0/0 schedulerInterface ATM0/0/0Hardware is ATM-SARPCI registers:bus_no=0, device_no=4CFID=0xA102104C, CFCS=0x02000006, CFRV=0x02030002, CFLT=0x0000FF00CFBA=0x4A000000, CFIT=0x02010100*** TI1585/1585 Scheduler at address 0x3A040000 ***Configuration/Statisticsline bw: 149760 min vc bw: 64 total slots: 2free slots: 21585 internal registersconfig: 0x227 status: 0x1E imask: 0x0clkfreq: 0x18FCA1 revnum: 0x0 acrlow: 0x80000000acrok: 0x800000001585 connection config/statusscheduler id 5type: VBR pcr: 353207 scr: 353207 mbs: 91rtv: 0x100scheduler id 6type: VBR pcr: 353207 scr: 353207 mbs: 91rtv: 0x100scheduler id 7type: VBR pcr: 353207 scr: 353207 mbs: 91rtv: 0x100scheduler id 8type: VBR pcr: 353207 scr: 353207 mbs: 91rtv: 0x100scheduler id 9type: VBR pcr: 353207 scr: 353207 mbs: 91rtv: 0x100In the following NRP-1 example, the VC output consists only of information specific to VC 1/100:
NRP-1# show controllers atm 0/0/0 vc 50/100Interface ATM0/0/0Hardware is ATM-SARPCI registers:bus_no=0, device_no=4CFID=0xA102104C, CFCS=0x02000006, CFRV=0x02030002, CFLT=0x0000FF00CFBA=0x4A000000, CFIT=0x02010100*** VC information and associated 1575 structures ***seg ring: 9 ringaddr: 0x311C600 ringindx:3 pendindx:3tx dma: 9 ctrlring: 0xC47183 pktcnt: 0rword10: 0x663C0000 rword11: 0x33CE274rword20: 0x0 rword21: 0x33CDFC4 rword22: 0x0 rword23: 0x0pxmt 0 queued: 0VCs mapped to this ringvcd: 5 cellhdr: 0x3200640 encap: 0 crcerror: 0rx dma: 9 config: 0x24000000 ctrlrxring: 0x80000A00 timecnt: 0xC8000lookup: 4 channel: 9 vpivci: 0x320064In the following NRP-1 example, the output displays cyclic redundancy check (CRC) error counters for each configured VC:
NRP-1# show controllers atm 0/0/0 detailed | include crcrx_crc_error: 0 rx_no_buf: 0 rx_timeout: 0vcd: 1 cellhdr: 0x1E00640 encap: 0 crcerror: 0vcd: 2 cellhdr: 0x2800C80 encap: 0 crcerror: 0vcd: 3 cellhdr: 0xA0 encap: 0 crcerror: 0vcd: 4 cellhdr: 0x500 encap: 0 crcerror: 0vcd: 5 cellhdr: 0x3200640 encap: 0 crcerror: 0Related Commands
show se64
To display detailed NRP-2 ATM SAR information, use the show se64 EXEC command.
show se64 {regs | mp_holder | vc-stats vpi vci | shaper shaper-number | vcd vcd}
Syntax Description
Defaults
No default behavior or values.
Command Modes
EXEC
Command History
Usage Guidelines
The show se64 command is used for debugging and troubleshooting the NRP-2 ATM SAR.
The output of the show se64 vc-stats command is divided into five categories:
•
•
•
•
•
Note
Each shaper number can be mapped to one or more VCDs. The VCDs mapped to the selected shaper appears at the end of the show se64 shaper command output:
NRP-2# show se64 shaper 0Shaper Number 0pcr_kb 1000, pcr_cr 2271, pcr_count 24218scr_kb 50, scr_cr 113, scr_count 4843600mbs 10, mbs count 10skip count 190, scr_inc 1023To determine the VCD number to use in the show se64 vcd command, use the show atm pvc privileged EXEC command:
NRP-2# show atm pvcVCD / Peak Avg/Min BurstInterface Name VPI VCI Type Encaps SC Kbps Kbps Cells Sts0/0/0.100 1 0 300 PVC SNAP UBR 10000 UP0/0/0.200 2 0 400 PVC SNAP VBR 1000 50 10 UP0/0/0.300 foobe 0 500 PVC SNAP UBR 599040 UP...If the VCD is displayed as a name instead of a number for the PVC of interest, use the show atm pvc name privileged EXEC command to determine the VCD number:
NRP-2# show atm pvc foobeATM0/0/0.300:VCD:3, VPI:0, VCI:500, Connection Name:foobeUBR, PeakRate:599040AAL5-LLC/SNAP, etype:0x0, Flags:0xC20, VCmode:0x0...Examples
Router# show se64 regs*** SE64 Internal Regs ***SAR revision DVPI bits 3, VCI bits 11Number of free mp holders:49152Number of particle in the sar 32255rx buffer base:virtual 0C000000, physical AC000000rx buffer size (byte):66058240, number of rx buffers:32255OAM cell ring base:virtual 0B050000, physical AB050000OAM shadow write pointer:0, OAM read pointer:10OAM cell ring size (byte):65536, number of entries:1024RM cell ring base:virtual 0AFC4000, physical AAFC4000RM cell ring size (byte):16384, number of entries:256Rx status ring base:virtual 0B020000, physical AB020000Rx shadow write pointer:0, Rx read pointer:1284Rx status ring size (byte):131072, number of entries:16384Tx status ring base:virtual 0AFE0000, physical AAFE0000Tx shadow write pointer:0, Tx read pointer:707Tx status ring size (byte):131072, number of entries:16384
SE64 internal memory and registers base:virtual 24000000, physical 84000000SE64 registers base:virtual 2401F000, physical 8401F000SE64 local memory base:virtual 20000000, physical 80000000Rx VC descriptor table base:virtual 20000000, physical 80000000Rx VC descriptor table size(byte):1048576Tx VC descriptor table base:virtual 20100000, physical 80100000Tx VC descriptor table size(byte):1048576Tx link pool base:virtual 20200000, physical 80200000Tx link pool size(byte):794624SE64 register value:Addr 2401F000, high 84000037, low 84000037, Rc Lg Buffer Pool Config Register 1Addr 2401F010, high FC000009, low FC000009, Rc Lg Buffer Pool Config Register 2Addr 2401F020, high 7FF0000C, low 7FF0000C, Rc Sm Buffer Pool Config RegisterAddr 2401F040, high 00000000, low 00000000, Rc Lg Buffer Pool Depth RegisterAddr 2401F060, high 00000000, low 00000000, Rc Sm Buffer Pool Depth RegisterAddr 2401F100, high 00000000, low 00000000, Rc Buffer Pool Return RegisterAddr 2401F180, high 00000000, low 00000000, Rc Lg Buffer Pool Region Flag RegrAddr 2401F190, high FFFFFFFF, low FFFFFFFF, Rc Sm Buffer Pool Row Map Regr 1Addr 2401F1A0, high FFFFFFFF, low FFFFFFFF, Rc Sm Buffer Pool Row Map Regr 2Addr 2401F400, high 00000090, low 00000090, Receive Processor Control RegisterAddr 2401F410, high 00000000, low 00000000, Rc Ext. Descriptor Table Base RegrAddr 2401F420, high 82FC4000, low 82FC4000, Rc RM Cell Ring RegisterAddr 2401F430, high 83050285, low 83050285, Rc OAM Cell Ring RegisterAddr 2401F440, high 80000000, low 80000000, Rc RM Cell Ring Stop RegisterAddr 2401F450, high 8006800B, low 8006800B, Rc OAM Cell Ring Stop RegisterAddr 2401F800, high 001C4FA7, low 00508002, Transmit Packet-Add Register 1Addr 2401F808, high 00000000, low 82FC9038, Transmit Packet-Add Register 2Addr 2401F810, high 11C28F06, low 11C28F06, Transmit Buffer-Add RegisterAddr 2401F900, high 0000FEFE, low 0000FEFE, Tx Buf Link Pool Region FlagRegrAddr 2401F908, high C0000001, low C0000001, Tx Buffer Link Pool Depth RegisterAddr 2401FA00, high 00000000, low 00000000, Protocol Header Register 0HAddr 2401FA08, high 00000000, low 00000000, Protocol Header Register 0LAddr 2401FA10, high 00000000, low 00000000, Protocol Header Register 1HAddr 2401FA18, high 00000000, low 00000000, Protocol Header Register 1LAddr 2401FA20, high 00000000, low 00000000, Protocol Header Register 2HAddr 2401FA28, high 00000000, low 00000000, Protocol Header Register 2LAddr 2401FA30, high 00000000, low 00000000, Protocol Header Register 3HAddr 2401FA38, high 00000000, low 00000000, Protocol Header Register 3LAddr 2401FA40, high 00000000, low 00000000, Protocol Header Register 4HAddr 2401FA48, high 00000000, low 00000000, Protocol Header Register 4LAddr 2401FA50, high 00000000, low 00000000, Protocol Header Register 5HAddr 2401FA58, high 00000000, low 00000000, Protocol Header Register 5LAddr 2401FA60, high 00000000, low 00000000, Protocol Header Register 6HAddr 2401FA68, high 00000000, low 00000000, Protocol Header Register 6LAddr 2401FA70, high 00000000, low 00000000, Protocol Header Register 7HAddr 2401FA78, high 00000000, low 00000000, Protocol Header Register 7LAddr 2401FA80, high 00000000, low 00000000, Protocol Header Register 8HAddr 2401FA88, high 00000000, low 00000000, Protocol Header Register 8LAddr 2401FA90, high 00000000, low 00000000, Protocol Header Register 9HAddr 2401FA98, high 00000000, low 00000000, Protocol Header Register 9LAddr 2401FAA0, high 00000000, low 00000000, Protocol Header Register AHAddr 2401FAA8, high 00000000, low 00000000, Protocol Header Register ALAddr 2401FAB0, high 00000000, low 00000000, Protocol Header Register BHAddr 2401FAB8, high 00000000, low 00000000, Protocol Header Register BLAddr 2401FB00, high 00000000, low 00000000, VC Base Address RegisterAddr 2401FB08, high 00FFFFFF, low 00FFFFFF, FRM Cell Time Interval RegisterAddr 2401FB10, high 00000000, low 00000000, CRM Interrupt Register...(additional register settings deleted)...
NRP-2# show se64 mp_holderNumber of free mp holders:49146vcd 1, number of holders 6Number of mp holders in the closed VC queue:0
NRP-2# show se64 vc-stats 4 33*** SE64 Statistics for VPI/VCI = 4/33 ***General:rx_count = 0 rx_limit = 7064tx_count = 0 tx_limit = 40RX Path:rx_pkt = 209 rx_drop_giant = 0rx_drop_crc = 7 rx_drop_runt = 0rx_drop_vc_del = 0 rx_drop_throttle = 0RX general:rx_pkt_clp = 0 rx_pkt_ci = 0rx_cell_count = 319TX Path:tx_pkt_safe_start = 224 tx_pkt_fast = 27tx_drop_idb_down = 0 tx_drop_vc_down = 0tx_drop_vc_del = 0 tx_drop_1par_clone = 0tx_drop_2par_room = 0 tx_drop_2par_coal = 0tx_drop_gt2par = 0 tx_drop_credit = 0tx_drop_oam_f4 = 0 tx_drop_pkt_len_0 = 0tx_drop_pkt_align = 0 tx_drop_pkt_mp = 0TX General:tx_combine = 0 tx_2par_coal = 0
NRP-2# show se64 shaper 0Shaper Number 0pcr_kb 1000, pcr_cr 2271, pcr_count 24218scr_kb 50, scr_cr 113, scr_count 4843600mbs 10, mbs count 10skip count 190, scr_inc 1023VC on the shaper:00002
If the shaper has no PVCs assigned to it, the show se64 shaper command displays an invalid status:
NRP-2# show se64 shaper 3Shaper Number 3Status:Invalid
NRP-2# show se64 vcd 1TXAddr 20100000, high 9BD294BF low 00000001Addr 20100008, high 0000001C low 98000000Addr 20100010, high 00000000 low 0006000DAddr 20100018, high 40000000 low 00000000Addr 20100020, high 80000000 low 000012C0Addr 20100028, high 00000000 low 00000000Addr 20100030, high 00000000 low 00000000Addr 20100038, high 00000000 low 00000000RXAddr 20004B00, high C704DD7B low 21000000Addr 20004B08, high 00000002 low BC0010B0Addr 20004B10, high 00000000 low 00000000Addr 20004B18, high 00000000 low 00000000Addr 20004B20, high 80001010 low 00000000Addr 20004B28, high 00000000 low 00000000Addr 20004B30, high 00000000 low 00000000Addr 20004B38, high 00000000 low 00000000Related Commands
Displays global (as opposed to VC-specific) information on the physical ATM interface.
show chassis xconn
To display the current state of the cross connect information requests from the NRP-1 or NRP-2 to the NSP, use the show chassis xconn EXEC mode command.
show chassis xconn
Syntax Description
This command has no keywords or arguments.
Defaults
No default behavior or values.
Command Modes
EXEC
Command History
Examples
In the following example, there are no outstanding cross-connect requests from the NRP-2 to the NSP:
NRP-2> show chassis xconnXconn List len = 2048Req outstanding = 0, Req Pending = 0VC status---------Outstanding_cnt = 0, Pending_cnt = 0In the following example, there is one request that is outstanding. The request is for PVC 40/50 on the NRP-2 ATM 0/0/0 interface. The request has nine more retries with a current timeout of 8000 milliseconds.
NRP-2# show chassis xconnXconn List len = 2048Req outstanding = 1, Req Pending = 0VC status---------Outstanding VC (1002) 40/50, retry cnt = 9, timeout_period = 8000Outstanding_cnt = 1, Pending_cnt = 0Related Commands
NSP Command Reference
This section documents new or modified commands. All other commands used with this feature are documented in the Cisco IOS Release 12.1 command reference publications.
•
hw-module
hw-module (image)
To identify the image to download to a specific NRP-2 processor, use the hw-module (image) global configuration command. To remove an NRP-2 image specification, use the no form of this command.
hw-module slot slot image image priority priority
no hw-module slot slot image image priority priority
hw-module (config-register)
To change the configuration register settings for the NRP-2, use the hw-module (config-register) global configuration command.
hw-module slot slot config-register value
hw-module (reset)
To simulate removal and insertion of a device installed in the Cisco 6400 chassis, use the hw-module (reset) EXEC command.
hw-module {slot slot | subslot slot/subslot | main-cpu | sec-cpu | nsp {A | B}} reset
hw-module (shutdown)
To simulate removal or shutdown of a device installed in the Cisco 6400 chassis, use the hw-module (shutdown) global configuration command. The device remains in removed state even through system reloads. To return the device to inserted state in the chassis, use the no form of this command.
hw-module {slot slot | subslot slot/subslot | main-cpu | sec-cpu | nsp {A | B}} shutdown
no hw-module {slot slot | subslot slot/subslot | main-cpu | sec-cpu | nsp {A | B}} shutdown
Syntax Description
Defaults
hw-module (image)
No image identified
hw-module (config-register)
Configuration register value is 0x2101
hw-module (reset)
No default behavior or values
hw-module (shutdown)
Shutdown disabled
Command Modes
Global configuration
The reset version of this command can be used in EXEC mode.
Command History
Usage Guidelines
hw-module (image)
Enter at least one instance of this command for each NRP-2 in the Cisco 6400 system. Without the command in the NSP configuration, the NRP-2 attempts to load the default image (c6400r2sp-g4p5-mz) from the NSP disk0:/images/ directory. If the image cannot be located, the NRP-2 is not able to boot.
Cisco recommends that you store all NRP-2 images on the NSP PCMCIA "disk0:/images" directory, but you can also store NRP-2 images on any integrated file system (IFS) device, including disk1 and TFTP, FTP, or rcp servers.
For images in the disk0:/images directory, you can use a shortened no version of the command to remove an NRP-2 image specification: no hw-module filename.
The hw-module (image) command performs the same function for the NRP-2 as the boot system global configuration command does for the NRP-1. Because NRP-2 boot information is stored on the NSP, the hw-module (image) command is entered on the NSP.
Note
hw-module (config-register)
This command enables you to change the NRP-2 configuration register settings.
The hw-module (config-register) command performs the same function for the NRP-2 as the config register global configuration and confreg ROMMON mode commands do for the NRP-1. Because the NRP-2 ROM state information is stored on the NSP, the hw-module (config-register) command is entered on the NSP.
Note
hw-module (reset)
This is the only version of the hw-module command that can be entered in EXEC mode. It can be used to reload the specified device from the NSP.
hw-module (shutdown)
This command keeps the selected card offline, even through system reloads.
Examples
hw-module (image)
In the following example, the NRP-2 in slot 2 of the Cisco 6400 chassis has three images assigned with different priorities, while the NRP-2 in slot 3 has only one image assigned:
Switch(config)# hw-module slot 2 image c6400r2sp-g4p5-mz.DC priority 2Switch(config)# hw-module slot 2 image tftp://10.1.1.1/c6400r2sp-g4p5-mz.DC priority 3Switch(config)# hw-module slot 2 image disk0:MyDir/c6400r2sp-g4p5-mz.DC priority 4Switch(config)# hw-module slot 3 image c6400r2sp-g4p5-mz.DC priority 2
Timesaver
hw-module (config-register)
In the following example, the configuration register setting causes the NRP-2 in slot 4 to boot only to ROMMON mode:
Switch(config)# hw-module slot 4 config-register 0x0In the following example, the configuration register setting causes the NRP-2 in slot 2 to boot the image specified with the hw-module (image) command:
Switch(config)# hw-module slot 2 config-register 0x1hw-module (reset)
In the following example, the device in slot 5 is reset:
Switch# hw-module slot 5 reset*Sep 28 22:30:56.590:%NSP_OIR-6-FULL_CREM:Card NRP2 removed from slot:5*Sep 28 22:30:58.510:%NSP_OIR-6-FULL_CINS:Card NRP2 inserted into slot:5*Sep 28 22:30:58.510:%NSP_OIR-6-FULL_ONLINE:Card NRP2, slot:5, being brought onlineIn the following example, the NSP in slot 0A is reset:
Switch# hw-module nsp A resethw-module (shutdown)
In the following example, the device in slot 4 is shutdown:
Switch(config)# hw-module slot 4 shutdownnrps
To telnet from the NSP to the NRP-2, use the nrps EXEC command alias.
nrpsslot
Syntax Description
Defaults
No default behavior or values.
Command Modes
EXEC (alias)
Command History
Not applicable for command aliases
Usage Guidelines
This is a command alias that telnets to the NRP-2.
You need to set the VTY line password before you can telnet to the NRP-2.
Examples
In the following example, the user telnets from the NSP to the NRP-2 in slot 4 of the Cisco 6400 chassis, enters privileged EXEC mode, and then exits the Telnet session.
NSP# nrps4Trying 10.4.0.2 ... OpenRouter> enableRouter# exit[Connection to 10.4.0.2 closed by foreign host]NSP#show controllers async
To display information on the NRP-2 PAM mailbox serial interface from the NSP, use the show controllers async EXEC command.
show controllers async
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values.
Command Modes
EXEC
Command History
Usage Guidelines
On the Cisco 6400, the show controllers async command can be used on the NSP or NRP-2 to view information for the NRP-2 PAM mailbox serial interface.
Examples
In the following example, the show controllers async command is used to view the NRP-2 PAM mailbox serial interface from the NSP:
NSP# show controllers asyncAsync NRP2 Pam bus controllerTTY line 1 not availableTTY line 2 not availableTTY line 3 not availableTTY line 4 not availableTTY line 5 not availableTTY line 6PAM bus data for mailbox at 0xA8A8FFC0magic1 = 0xDEADBABE, magic2 = 0x21524541in_data = 0x0000000D, out_data = 0x0000003Ein_status.received_break = 0out_status.received_break = 0tx_owned = TRUE, rx_owned = FALSEBuffer informationRx ttycnt 0Tx ttycnt 0Rx Buffs:inpk 0/0 inheadpk 0 dataq 0 0 0pakq 0 0 0Tx Buffs:outpk 0 txpkq 0 0 0Rx totalin 1302 Tx totalout 69
TTY line 7 not availableTTY line 8 not availableTTY line 9 not availableTTY line 10 not availableTTY line 11 not availableTTY line 12 not availableTTY line 13 not availableTTY line 14PAM bus data for mailbox at 0xA8E8FFC0magic1 = 0xDEADBABE, magic2 = 0x21524541in_data = 0x00000000, out_data = 0x00000000in_status.received_break = 0out_status.received_break = 0tx_owned = TRUE, rx_owned = FALSEBuffer informationRx ttycnt 0Tx ttycnt 0Rx Buffs:inpk 0/0 inheadpk 0 dataq 0 0 0pakq 0 0 0Tx Buffs:outpk 0 txpkq 0 0 0Rx totalin 0 Tx totalout 0TTY line 15 not availableTTY line 16 not availableNSP#snmp-server forwarder
To enable the SNMPv3 proxy forwarder, use the snmp-server forwarder global configuration command. To disable the proxy forwarder, use the no form of this command.
snmp-server forwarder
no snmp-server forwarder
Syntax Description
This command has no arguments or keywords.
Defaults
Disabled
Command Modes
Global configuration
Command History
12.1(4)DB
This command was introduced on the Cisco 6400 NSP to support the NRP-2.
Usage Guidelines
The SNMPv3 Proxy Forwarder feature enables all NSP and NRP-2 components of the Cisco 6400 system to be managed as one functional entity. With the Proxy Forwarder feature enabled, the NSP:
•
•
When the NSP and NRP-2 are properly configured for SNMPv3 and the Proxy Forwarder feature, both the NSP and NRP-2 automatically generate a series of SNMP commands. Do not modify or delete the automatically generated commands, because doing so may prevent SNMP from working properly.
Examples
In the following example, the NSP is configured to act as the proxy forwarder:
snmp-server group usmgrp v3 noauthsnmp-server user usmusr usmgrp v3The previous commands cause the NSP to automatically generate the following commands:
snmp-server engineID remote 10.3.0.2 vrf 6400-private 80000009030000107BA9C7A0snmp-server user trapusr trapusr v3snmp-server user trapusr trapusr remote 10.3.0.2 vrf 6400-private v3snmp-server user usmusr usmgrp remote 10.3.0.2 vrf 6400-private v3snmp-server group trapusr v3 noauth notify *tv.FFFFFFFF.FFFFFFFFIn the following example, the NRP-2 is configured to allow the NSP to act as the proxy forwarder:
snmp-server group usmgrp v3 noauthsnmp-server user usmusr usmgrp v3snmp-server enable trapssnmp-server host 10.3.0.1 vrf 6400-private version 3 noauth trapusrThe previous commands cause the NRP-2 to automatically generate the following commands:
snmp-server user trapusr trapusr v3snmp-server group trapusr v3 noauth notify *tv.FFFFFFFF.FFFFFFFFsnmp-server enable traps snmp authentication linkdown linkup coldstartsnmp-server enable traps configsnmp-server enable traps syslogsnmp-server enable traps bgpsnmp-server enable traps ipmulticastsnmp-server enable traps rsvpsnmp-server enable traps frame-relaysnmp-server enable traps rtrRelated Commands
The SNMPv3 Proxy Forwarder feature requires the NSP and NRP-2 to be configured using specific options in the snmp-server global configuration commands:
NRP-2 Debug Commands
This section documents new or modified debug commands. All other commands used with this feature are documented in the Cisco IOS Release 12.1 command reference publications.
debug pmbox
To display debug messages for traffic flowing on the NRP-2 PAM mailbox serial interface, use the debug pmbox EXEC command. The no form of this command disables debugging output.
debug pmbox {events | {rx-path | tx-path} {all | config-download | config-update | diag | driver | ehsa | force-fail | image-download | info-request | nrp | ping | status-update | syslog | test1 | test2 | xc-request | xc-response}}
no debug pmbox {events | {rx-path | tx-path} {all | config-download | config-update | diag | driver | ehsa | force-fail | image-download | info-request | nrp | ping | status-update | syslog | test1 | test2 | xc-request | xc-response}}
Syntax Description
Defaults
No default behavior or values.
Command History
Examples
In the following example, image download messages are received and transmitted by the PAM mailbox serial interface of the NRP-2 in slot 5. Notice that the request messages are 24 bytes long and the response messages are 12288 bytes long.
Switch# debug pmbox rx-path tx-path image-downloadSwitch#RX(5/0) type:IMAGE DNLD, len = 24TX(5/0) type:IMAGE DNLD, len = 12288RX(5/0) type:IMAGE DNLD, len = 24TX(5/0) type:IMAGE DNLD, len = 12288RX(5/0) type:IMAGE DNLD, len = 24TX(5/0) type:IMAGE DNLD, len = 12288debug se64
To display debug messages for the NRP-2 ATM SAR, use the debug se64 EXEC command. The no form of this command disables debugging output.
debug se64 {detail | errors}
no debug se64 {detail | errors}
Syntax Description
detail
Enables the show controllers atm 0/0/0 privileged EXEC command to display internal ATM SAR data and register values.
errors
Displays run time SAR driver error information.
Defaults
No default behavior or values.
Command History
Examples
In the following example, the debug output shows that the SAR was not ready to transmit packets:
NRP-2# debug se64 errorsNRP-2#01:39:05:%SYS-5-CONFIG_I:Configured from console by console01:39:15:%NRP2_SE64-3-LLD_SNDPAK_SARNOTREADY:SAR not ready during packet TX:vcd 2644-Traceback= 60124A88 601CFF28 6012D878 602EFBCC 802C7EAC01:39:45:%NRP2_SE64-3-LLD_SNDPAK_SARNOTREADY:SAR not ready during packet TX:vcd 2249-Traceback= 60124A88 601CFF28 6012D878 602EFBCC 802C7EAC01:40:15:%NRP2_SE64-3-LLD_SNDPAK_SARNOTREADY:SAR not ready during packet TX:vcd 3810Related Commands
debug xconn
To track the requests and responses for the cross-connect information protocol, use the debug xconn EXEC command. The no form of this command disables debugging output.
debug xconn
no debug xconn
Syntax Description
This command has no keywords or arguments.
Defaults
No default behavior or values.
Command History
Examples
The debug output contains the following information:
•
–
–
–
–
•
•
•
In the following example, the debug output tracks the requests and responses for the cross-connect information protocol on VC 42/52. One request message is sent and identified as outstanding, then is resent three times. Finally, a response message is received, reducing the total number of outstanding messages to 0. This example includes no pending messages:
1w3d:O (1-0) 42/521w3d:A (1-0) 42/521w3d:A (1-0) 42/521w3d:A (1-0) 42/521w3d:R (0-0) 42/52Related Commands
Displays the current state of the cross-connect information requests from the NRP-1 or NRP-2 to the NSP.
NSP Debug Commands
This section documents new or modified debug commands. All other commands used with this feature are documented in the Cisco IOS Release 12.1 command reference publications.
debug config-download
The Cisco 6400 uses a download protocol to download the NRP-2 startup configuration from the NSP. The download protocol and data pass through the NRP-2 PAM mailbox serial interface. To view the configuration download protocol message header types as they are received on the PAM mailbox serial interface, use the debug config-download EXEC command. The no form of this command disables debugging output.
debug config-download
no debug config-download
Syntax Description
This command has no keywords or arguments.
Defaults
Disabled
Command History
12.1(4)DC
This command was introduced on the Cisco 6400 NSP to support the NRP-2.
Examples
In the following example, the debug config-download command is used to display configuration download protocol monitoring information:
switch# debug config-downloadCDNLD debugging is onSwitch#00:01:39:CDNLD(6/0):WRR00:01:39:CDNLD(6/0):DR00:01:39: do_chksum num_bytes = 61000:01:39: calc cksum = 0xC40500:01:39:CDNLD(6/0):DRRelated Commands
debug image-download
The Cisco 6400 uses a download protocol to download the NRP-2 image from the NSP or integrated file system (IFS). The download protocol and data pass through the NRP-2 PAM mailbox serial interface. To view the image download protocol message header types as they are received on the PAM mailbox serial interface, use the debug image-download EXEC command. The no form of this command disables debugging output.
debug image-download [tftp]
no debug image-download
Syntax Description
Defaults
Disabled
Command History
12.1(4)DC
This command was introduced on the Cisco 6400 NSP to support the NRP-2.
Related Commands
Glossary
ABR—available bit rate. QoS class defined by the ATM Forum for ATM networks. ABR is used for connections that do not require timing relationships between source and destination. ABR provides no guarantees in terms of cell loss or delay, providing only best-effort service. Traffic sources adjust their transmission rate in response to information they receive describing the status of the network and its capability to successfully deliver data. Compare with CBR, UBR, and VBR.
BPE—Backplane Ethernet.
CBR—constant bit rate. QoS class defined by the ATM Forum for ATM networks. CBR is used for connections that depend on precise clocking to ensure undistorted delivery. Compare with ABR, UBR, and VBR.
CRC—cyclic redundancy check. Error-checking technique in which the frame recipient calculates a remainder by dividing frame contents by a prime binary divisor and compares the calculated remainder to a value stored in the frame by the sending node.
FTP—File Transfer Protocol. Application protocol, part of the TCP/IP protocol stack, used for transferring files between network nodes. FTP is defined in RFC 959.
GBIC—gigabit interface converter.
GCRA—generic cell rate algorithm. In ATM, an algorithm that defines conformance with respect to the traffic contract of the connection. For each cell arrival, the GCRA determines whether the cell conforms to the traffic contract.
GE—gigabit Ethernet.
IFS—integrated file system, such as TFTP, FTP, or rcp servers.
MBS—maximum burst size. In an ATM signaling message, burst tolerance is conveyed through the MBS, which is coded as a number of cells. The burst tolerance together with the SCR and the GCRA determine the MBS that can be transmitted at the peak rate and still be in conformance with the GCRA. See also SCP and GCRA.
MTU—maximum transmission unit. Maximum packet size, in bytes, that a particular interface can handle.
NME—network management Ethernet. The local area network used to control and manage equipment in a Central Office and branch locations. The NME connection on the Cisco 6400 is an RJ-45 connector for a 10BaseT port on the NSP module.
NRP—node route processor. One of the component modules used in the Cisco 6400. This module is the Layer 3 element for the Cisco 6400 responsible for implementing the routing function.
NRP-1—Node route processor that incorporates a 100-Mbps Fast Ethernet interface for connecting into an IP network and has processing capability for OC-3 rate of user traffic. Compare with NRP-2.
NRP-2—Node route processor that provides a Gigabit Ethernet interface and sufficient processing capability for handling OC-12 rate of user traffic. Compare with NRP-1.
NSP—node switch processor. Node switch processor. One of the component modules used in the Cisco 6400. This module is responsible for all ATM switching and control functions within the Cisco 6400.
OC—Optical carrier. A series of physical protocols (OC-3, OC-12, and so on), defined for SONET optical signal transmissions.
PAM mailbox serial interface—Backplane interface that connects the NSP and the NRP-2. Used for internal communication only, the PAM mailbox serial interface is not intended to carry user data.
PCMCIA—Personal Computer Memory Card International Association. Refers to a standard used for credit-card sized computer peripherals. Type I devices are very thin memory cards: Type 2 devices include most modems and interfaces; and Type 3 devices are used for disk drives and thicker components.
PCR—peak cell rate. Parameter defined by the ATM Forum for ATM traffic management. In CBR transmissions, PCR determines how often data samples are sent. In ABR transmissions, PCR determines the maximum value of the ACR.
QoS—quality of service. Measure of performance for a transmission system that reflects its transmission quality and service availability.
rcp—remote copy protocol. Protocol that allows users to copy files to and from a file system residing on a remote host or server on the network. The rcp protocol uses TCP to ensure the reliable delivery of data.
ROMMON—ROM Monitor.
SAR—segmentation and reassembly.
SCR—Parameter defined by the ATM Forum for ATM traffic management. For VBR connections, SCR determines the long-term average cell rate that can be transmitted. See also VBR.
SNMP—Simple Network Management Protocol. Network management protocol used almost exclusively in TCP/IP networks. SNMP provides a means to monitor and control network devices, and to manage configurations, statistics collection, performance, and security.
TFTP—Trivial File Transfer Protocol. Simplified version of FTP that allows files to be transferred from one computer to another over a network.
UBR—unspecified bit rate. QoS class defined by the ATM Forum for ATM networks. UBR allows any amount of data up to a specified maximum to be sent across the network, but there are no guarantees in terms of cell loss rate and delay. Compare with ABR, CBR, and VBR.
VBR—variable bit rate. QoS class defined by the ATM Forum for ATM networks. VBR is subdivided into a real time (RT) class and non-real time (NRT) class. VBR-RT is used for connections in which there is a fixed timing relationship between samples. VBR-NRT is used for connections in which there is no fixed timing relationship between samples, but that still need a guaranteed QoS. Compare with ABR, CBR, and UBR.
VCD—virtual circuit descriptor. When you create a PVC, you create a VCD and attach it to the VPI and VCI. A VCD identifies which VPI/VCI to use for a particular packet. The number chosen for the VCD is independent of the VPI/VCI used.
