Cisco 6400 Software Setup Guide June 2003 Corporate Headquarters Cisco Systems, Inc. 170 West Tasman Drive San Jose, CA 95134-1706 USA http://www.cisco.
THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL STATEMENTS, INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS.
CONTENTS Preface xi Document Objectives xi Related Documentation Audience xi xii Organization xii Conventions xiii Command Syntax Examples xiii xiii Keyboard xiv Notes, Timesavers, Tips, Cautions, and Warnings xiv Obtaining Documentation xiv World Wide Web xiv Documentation CD-ROM Ordering Documentation Documentation Feedback xv xv xv Obtaining Technical Assistance xv Cisco.
Contents Configuring the System Clock and Hostname 2-3 Verifying the System Clock and Hostname Configuration 2-4 ATM Address 2-4 Understanding the Autoconfigured ATM Addressing Scheme Configuring the ATM Address Manually Verifying the ATM Address 2-6 2-4 2-5 Network Management Ethernet Interface 2-6 Enabling NME Consolidation on the NSP 2-7 Enabling NME Consolidation on a New NSP Preloaded with Cisco IOS Release 12.
Contents Using the NSP File Systems and Memory Devices C H AP TER 3 Basic NRP Configuration 2-24 3-1 NRP-1 Configuration 3-1 Methods Available for Configuring the NRP-1 Initial NRP-1 Configuration 3-2 3-1 Using DHCP 3-2 Checking the Software Release Version and Choosing the Configuration Method Configuring the NRP-1 3-3 Verifying the Initial NRP-1 Configuration 3-4 Segmentation and Reassembly Buffer Management Setting the Segmentation Buffer Size 3-5 Setting the I/O Memory Size 3-6 Using the NRP-1
Contents Configuring PVCs on ATM Subinterfaces 3-22 Verifying PVCs on ATM Subinterfaces 3-24 Configuring VC Classes 3-24 Verifying VC Classes 3-26 Configuring PVC Discovery 3-26 Verifying PVC Discovery 3-28 Configuring PVC Traffic Shaping 3-28 Verifying PVC Traffic Shaping 3-29 C H AP TER 4 Node Line Card Interface Configuration NLC Interface Identification 4-1 4-1 Autoconfiguration 4-2 Disabling Autoconfiguration 4-2 Default NLC Interface Configuration Verifying Autoconfiguration 4-3 ATM Interface
Contents Configuring Redundant NSPs 5-3 Verifying NSP Redundancy 5-3 Synchronizing Redundant NSPs 5-4 Verifying Synchronized NSPs 5-5 Erasing Startup Configurations on Redundant NSPs Verifying Erased Startup Configurations 5-5 5-5 PCMCIA Disk Mirroring 5-5 Restrictions and Recommendations 5-6 Disabling PCMCIA Disk Mirroring 5-7 Enabling PCMCIA Disk Mirroring 5-7 Specifying the File Size Threshold 5-8 Specifying to Copy All Files Blindly 5-9 Initiating PCMCIA Disk Synchronization 5-10 Performing Mirrored
Contents Reversing NLC Redundancy Roles 5-23 Resetting Cards, Slots, and Subslots 5-23 C H AP TER 6 SNMP, RMON, and Alarm Configuration Simple Network Management Protocol Identifying and Downloading MIBs 6-1 6-1 6-1 Using the NSP as the SNMPv3 Proxy Forwarder for the NRP-2 6-1 Task 1: Configuring the NSP as the Proxy Forwarder 6-2 Task 2: Configuring the NRP-2 to Use the NSP as the Proxy Forwarder Verifying the SNMPv3 Proxy Forwarder Remote Monitoring 6-4 6-4 Alarms 6-4 Configuring Temperature Thre
Contents Adding and Removing Domain Name Servers A-16 SNMP Management A-16 Entering System Options A-17 Entering Community Strings A-18 Adding Trap Managers NRP Status A-18 A-19 Subscriber Management A-19 Adding and Removing Subscribers System Status A-22 Loading New Web Console Pages A PPE NDI X B A-20 A-24 Upgrading Software on the Cisco 6400 Recommendations B-1 B-1 Upgrading Software on Nonredundant NRP-1s B-2 Example—Upgrading the Nonredundant NRP-1 B-3 Upgrading Software on Nonredundant
Contents Reload the Secondary NSP B-15 Upgrade the Primary NSP Images B-16 Switch the Primary and Secondary NSPs B-17 Example—Upgrading Redundant NSPs B-17 Upgrading the Secondary NSP Images B-17 Reloading the Secondary NSP B-18 Upgrading the Primary NSP Images B-18 Switching the Primary and Secondary NSPs AP PE N DIX C B-19 Optimizing the Number of Virtual Connections on the Cisco 6400 C-1 An Overview of the ITT and Virtual Connection Limitations C-1 How VCI Values Limit the Number of Virtual Conn
Preface This chapter describes the objectives, organization, and audience of this guide, as well as conventions and related documentation. Document Objectives The purpose of this guide is to help you set up your Cisco 6400 carrier-class broadband aggregator with a basic configuration and connectivity among the Cisco 6400 components. For external connectivity and information on deploying the many features supported by the Cisco 6400, see the Cisco 6400 Feature Guide for your software release.
Preface Audience Audience This guide is designed for the system administrator who will be responsible for setting up the CiscoIOS software on the Cisco6400. The system administrator should be familiar with the installation of high-end networking equipment.
Preface Conventions Conventions This section describes the following conventions used by this guide: • Command Syntax • Examples • Keyboard • Notes, Timesavers, Tips, Cautions, and Warnings Command Syntax Descriptions of command syntax use the following conventions: Convention Description boldface Indicates commands and keywords that are entered literally as shown.
Preface Obtaining Documentation Keyboard This guide uses the following conventions for typing keys: Convention Description Z Keys are indicated in capital letters but are not case sensitive. ^ orCtrl Represents the Control key. For example, when you read ^D or Ctrl-D , you should hold down the Control key while you press the D key. Notes, Timesavers, Tips, Cautions, and Warnings The following conventions are used to attract the reader's attention: Note Timesaver Tip Means reader take note.
Preface Obtaining Technical Assistance • http://www-china.cisco.com • http://www-europe.cisco.com Documentation CD-ROM Cisco documentation and additional literature are available in a CD-ROM package, which ships withyour product. The Documentation CD-ROM is updated monthly and may be more current than printed documentation. The CD-ROM package is available as a single unit or as an annualsubscription.
Preface Obtaining Technical Assistance Cisco.com Cisco.com is the foundation of a suite of interactive, networked services that provides immediate, open access to Cisco information and resources at anytime, from anywhere in the world. This highly integrated Internet application is a powerful, easy-to-use tool for doing business with Cisco. Cisco.com provides a broad range of features and services to help customers and partners streamline business processes and improve productivity. Through Cisco.
Preface Obtaining Technical Assistance P1 and P2 level problems are defined as follows: • P1—Your production network is down, causing a critical impact to business operations if service is not restored quickly. No workaround is available. • P2—Your production network is severely degraded, affecting significant aspects of your business operations. No workaround is available.
Preface Obtaining Technical Assistance Cisco 6400 Software Setup Guide xviii OL-1183-04
C H A P T E R 1 Product Overview The Cisco 6400 carrier-class broadband aggregator is a high-performance, scalable service gateway that enables the selection and delivery of broadband network services, virtual private networks (VPNs), and voice- and entertainment-driven traffic over the full suite of access media.
Chapter1 Product Overview Cisco 6400 System Figure1-1 Cisco 6400 Carrier-Class Broadband Aggregator Cisco 6400 System The Cisco6400 uses a ten-slot, modular chassis featuring the option of half-height and full-height card and slot redundancy, along with dual, fault-tolerant, load-sharing AC or DC power supplies. The two central slots (slot 0A and 0B) in the Cisco6400 are dedicated to redundant, field-replaceable NSP modules that support the 5-Gbps shared memory, fully nonblocking switch fabric.
Chapter1 Product Overview Cisco 6400 System Figure1-2 Simple Schematic of Cisco 6400 Internal and External Connectivity Node Switch Processor The Cisco 6400 NSP provides ATM switching functionality. The NSP uses permanent virtual circuits (PVCs) or permanent virtual paths (PVP) to direct ATM cells between the NRP and ATM interface. The NSP also controls and monitors the Cisco 6400 system, including component NLCs and NRPs.
Chapter1 Product Overview Cisco 6400 System The Cisco6400 can contain multiple NRP modules, configured to operate independently or as 1+1 redundant pairs.
Chapter1 Product Overview Network Management—Cisco 6400 SCM Node Line Card NLCs provide ATM interfaces for the Cisco 6400 system and are controlled by the NSP. The three types of NLC available for the Cisco 6400 each offer a different interface type, as shown in Table1-2.
Chapter1 Product Overview Network Management—Cisco 6400 SCM For more information, see theCisco 6400 SCM documentation on Cisco.com at http://www.cisco.
C H A P T E R 2 Basic NSP Configuration This chapter describes how to perform basic configuration for the Cisco 6400 node switch processor (NSP). The Cisco6400 can contain two NSPs configured for redundancy.
Chapter2 Basic NSP Configuration Checking the Software Release Version Note If your Telnet station or Simple Network Management Protocol (SNMP) network management workstation and the Cisco 6400 are on different networks, you must add a static routing table entry to the routing table. For information on configuring static routes, see the “Configuring ATM Routing and PNNI” chapter of the ATM Switch Router Software Configuration Guide.
Chapter2 Basic NSP Configuration DHCP DHCP Dynamic Host Configuration Protocol (DHCP) is the default IP assignment protocol for a new NSP, or for an NSP that has had its configuration file cleared by means of the erase nvram:startup-config command. For DHCP, an Ethernet IP address, subnet mask, and the default route are retrieved from the DHCP server for any interface set with the ip address negotiated command.
Chapter2 Basic NSP Configuration ATM Address Verifying the System Clock and Hostname Configuration To confirm the system clock setting, use the show clock command: Publications# show clock .15:03:12.015 UTC Fri Oct 17 2002 Publications# To confirm the hostname, check the CLI prompt. The new hostname will appear in the prompt.
Chapter2 Basic NSP Configuration ATM Address Note The first 13 bytes of the address make up a switch prefix used by ILMI in assigning addresses to end stations connected to User-Network Interface (UNI) ports. • Note MAC address of the NSP—6 bytes (used to distinguish multiple end system identifier [ESI] addresses) Both MAC address fields in the ATM address are the same, but they will not be the same as the address printed on the chassis label.
Chapter2 Basic NSP Configuration Network Management Ethernet Interface 47.0091.8100.0000.0041.0b0a.1081.4000.0c80.0030.00 47.0091.8100.0000.0041.0b0a.1081.4000.0c80.1000.00 47.0091.8100.0000.0041.0b0a.1081.4000.0c80.1010.00 47.0091.8100.0000.0041.0b0a.1081.4000.0c80.1020.00 47.0091.8100.0000.0041.0b0a.1081.4000.0c80.1030.00 47.0091.8100.0000.0041.0b0a.1081.4000.0c80.8000.00 47.0091.8100.0000.0041.0b0a.1081.4000.0c80.8010.00 47.0091.8100.0000.0041.0b0a.1081.4000.0c80.8020.00 47.0091.8100.0000.0041.0b0a.
Chapter2 Basic NSP Configuration Network Management Ethernet Interface Enabling NME Consolidation on the NSP The method used to enable the combined NME interface on the NSP depends on whether or not the NSP was upgraded to or preloaded with Cisco IOS Release 12.0(5)DB or later. Enabling NME Consolidation on a New NSP Preloaded with Cisco IOS Release 12.0(5)DB or Later On an NSP that is preloaded with a Cisco IOS Release 12.
Chapter2 Basic NSP Configuration Network Management Ethernet Interface Task 2: Setting up the Bridge Group To set up the bridge group, complete the following steps beginning in global configuration mode: Command Purpose Step1 Switch(config)# bridge irb Enables integrated routing and bridging. Step2 Switch(config)# bridge 1 protocol ieee Selects the IEEE Ethernet Spanning-Tree Protocol for bridge group 1. Step3 Switch(config)# bridge 1 route ip Enables IP routing in bridge group 1.
Chapter2 Basic NSP Configuration Network Management Ethernet Interface Enabling NME Consolidation on the NRP In addition to configuring the NSP for NME consolidation, you must configure the NRP Ethernet interfaces to also support NME consolidation. Complete the following steps, beginning in global configuration mode: Command Purpose Step1 Router(config)# interface ethernet 0/0/0 Selects the Ethernet 0/0/0 interface. Step2 Router(config-if)# no ip address Removes the IP address from the interface.
Chapter2 Basic NSP Configuration Internal Cross-Connections ! Verifying the NME Interface Configuration Use the show interface EXEC command to verify successful configuration of the NME interface on the NSP. If the NSP is configured for NME consolidation, use show interface BVI 1 . On an NSP configured to use a separate NME interface, use show interface ethernet 0/0/0.
Chapter2 Basic NSP Configuration Internal Cross-Connections Configuring PVCs (VC Switching) A permanent virtual circuit (PVC) is a permanent logical connection that you must configure manually, from source to destination, through the ATM network. Once configured, the ATM network maintains the connection at all times, regardless of traffic flow. That is, the connection is always up whether or not there is traffic to send.
Chapter2 Basic NSP Configuration Internal Cross-Connections To create a PVP between an ATM interface and an NRP, complete the following steps beginning in global configuration mode: Command Purpose Step1 Switch(config)# interface atm slot/subslot/port Selects the NLC interface to be configured. Step2 Switch(config-if)# atm pvp vpi interface atm slot/subslot/port vpi Configures the PVP, using the slot/subslot/port of the NRP to which you want to connect the NLC.
Chapter2 Basic NSP Configuration Internal Cross-Connections ATM0/0/0 ATM0/0/0 ATM0/0/0 ATM0/0/0 ATM1/0/0 ATM1/0/0 ATM1/0/1 Interface ATM1/0/1 ATM5/0/0 ATM5/0/0 ATM6/0/0 ATM6/0/0 ATM7/0/0 ATM7/0/0 ATM7/0/0 ATM7/0/1 ATM7/0/1 ATM7/1/0 ATM7/1/0 ATM7/1/0 ATM7/1/1 Interface ATM7/1/1 ATM8/1/0 ATM8/1/0 ATM8/1/0 ATM8/1/1 ATM8/1/1 0 0 0 0 0 0 0 VPI 0 0 0 0 0 0 0 0 0 0 0 0 0 0 VPI 0 0 0 0 0 0 54 55 56 57 5 16 5 VCI 16 5 16 5 16 5 16 18 5 16 5 16 18 5 VCI 16 5 16 18 5 16 PVC PVC PVC PVC PVC PVC PVC Type PVC PVC PV
Chapter2 Basic NSP Configuration Network Clocking Cross-connect OAM-state: Not-applicable Encapsulation: AAL5ILMI Threshold Group: 6, Cells queued: 0 Rx cells: 35, Tx cells: 35 Tx Clp0:35, Tx Clp1: 0 Rx Clp0:35, Rx Clp1: 0 Rx Upc Violations:0, Rx cell drops:0 Rx pkts:16, Rx pkt drops:0 Rx connection-traffic-table-index: 3 Rx service-category: VBR-RT (Realtime Variable Bit Rate) Rx pcr-clp01: 424 Rx scr-clp01: 424 Rx mcr-clp01: none Rx cdvt: 1024 (from default for interface) Rx mbs: 50 Tx connection-traff
Chapter2 Basic NSP Configuration Network Clocking Configuring the Transmit Clock Source By default, the interface uses a network-derived clock source. To modify how an interface derives its transmit clock, complete the following steps beginning in global configuration mode: Command Purpose Step1 Switch(config)# interface atm slot/subslot/port Selects the interface to be configured.
Chapter2 Basic NSP Configuration Network Clocking Configuring Network Clock Revertive Behavior Revertive behavior enables the network clock to automatically switch to the highest priority clock source available. When a clock failure is detected, the next highest priority clock source is selected. If revertive behavior is not configured, the clock source will not switch back even when the failed (but higher priority) clock source is restored.
Chapter2 Basic NSP Configuration Network Clocking NSP# show hardware 6400 named NSP, Date:16:59:29 UTC Wed Feb 28 2001 Feature Card's FPGA Download Version:0 Slot ----1/0 2/0 3/0 4/0 5/0 6/0 7/0 8/0 5/1 0A/PC 0A/FC 0A/SC 0A/NC 0B/PC 0B/FC 0B/SC 0B/NC Ctrlr-Type -----------NRP2 622SM NLC NRP2 NRP2 155SM NLC NRP2 622SM NLC NRP2 155SM NLC NSP-PC FC-PFQ NSP-SC NSP-NC NSP-PC FC-PFQ NSP-SC NSP-NC Part No.
Chapter2 Basic NSP Configuration Network Routing Verifying the Network Clock Configuration To verify the switch network clocking configuration, use the show network-clocks EXEC command: Switch# show network-clocks clock configuration is NON-Revertive Priority 1 clock source: ATM2/0/0 up Priority 2 clock source: ATM7/0/0 down Priority 3 clock source: ATM6/0/0 up Priority 4 clock source: unconfigured Priority 5 clock source: system Current clock source: ATM2/0/0, priority: 1 Switch# To verify BITS network
Chapter2 Basic NSP Configuration NRP-2 and NRP-2SV Support Verifying ATM Static Routes for IISP or PNNI To verify successful configuration of an ATM static route, use the show atm route and showatmpnnitopology EXEC commands.
Chapter2 Basic NSP Configuration NRP-2 and NRP-2SV Support You can create additional directories on the PCMCIA disk with the mkdir command. See the “Cisco IOS File Management” chapter in the Cisco IOS Configuration Fundamentals Configuration Guide. Configuring NRP-2 Image Management on the NSP 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.
Chapter2 Basic NSP Configuration NRP-2 and NRP-2SV Support Changing the NRP-2 Configuration Register Setting 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: Command Purpose 1 Switch(config)# hw-module slot slot config-register value 1.
Chapter2 Basic NSP Configuration NRP-2 and NRP-2SV Support SNMPv3 Proxy Forwarder The NSP and NRP-2 support SNMPv1, SNMPv2c, and SNMPv3. The NSP can use the SNMPv3 Proxy Forwarder feature to: • Route the SNMPv3 messages destined for NRP-2 • Forward NRP-2 traps to the Network Element Manager For general information on using SNMP, see the “Configuring Simple Network Management Protocol (SNMP)” section i n the “System Management” part of the Cisco IOS Configuration Fundamentals Configuration Guide.
Chapter2 Basic NSP Configuration Storing the NSP Configuration Interface User Mode Idle Peer Address NSP# In 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 6 Tty Typ Tx/Rx * 6 TTY 0/0 - A Modem - Roty AccO AccI - Uses 7 Noise 0 Overruns 0/0 Int - Line 6, Location:"", Type:"XTERM" Length:24 lines, Width:80 columns Status:Ready, Connected, Active Capabilities:EXEC Suppressed, Software Flowcontrol In, Softwar
Chapter2 Basic NSP Configuration Using the NSP File Systems and Memory Devices Using the NSP File Systems and Memory Devices File systems on the NSP include read-only memory (NVRAM, or system), Flash memory (such as PCMCIA disks 0 and 1, and boot flash), and remote file systems (such as TFTP or rcp servers).
Chapter2 Basic NSP Configuration Using the NSP File Systems and Memory Devices Example—Disk0: versus Slot0: Switch# dir disk0: Directory of disk0:/ 3 157 376 -rwdrw-rw- 628224 0 2134 Jan 01 2000 00:08:55 Jan 01 2000 00:11:01 Jan 05 2000 22:05:27 c6400s-html.tar.120-4.DB nsp-html startup.config 109760512 bytes total (108228608 bytes free) Switch# dir slot0: %Error opening slot0:/ (Device not ready) Switch# In Cisco IOS Release 12.
Chapter2 Basic NSP Configuration Using the NSP File Systems and Memory Devices Cisco 6400 Software Setup Guide 2-26 OL-1183-04
C H A P T E R 3 Basic NRP Configuration This chapter describes how to perform a basic configuration for the node route processors (NRP-1, NRP-2, and NRP-2SV). The Cisco6400 can contain multiple NRP modules, configured to operate independently or as 1+1 redundant pairs (NRP-1 only at this time).
Chapter3 Basic NRP Configuration NRP-1 Configuration Note If your Telnet station or Simple Network Management Protocol (SNMP) network management workstation and the Cisco 6400 are on different networks, you must either use Dynamic Host Configuration Protocol (DHCP) to provide a default route, or add a static routing table entry to the routing table. To assign a static IP route, use the ip route global configuration command. Initial NRP-1 Configuration An NRP-1 running Cisco IOS Release 12.
Chapter3 Basic NRP Configuration NRP-1 Configuration Rights clause at FAR sec. 52.227-19 and subparagraph (c) (1) (ii) of the Rights in Technical Data and Computer Software clause at DFARS sec. 252.227-7013. Cisco Systems, Inc. 170 West Tasman Drive San Jose, California 95134-1706 Cisco Internetwork Operating System Software IOS (tm) C6400R Software (C6400R-G4P5-M), Version 12.3 Copyright (c) 1986-2002 by cisco Systems, Inc.
Chapter3 Basic NRP Configuration NRP-1 Configuration An enable secret can contain from 1 to 25 uppercase and lowercase alphanumeric characters; an enable password or virtual terminal password can contain any number of uppercase and lowercase alphanumeric characters. In all cases, a number cannot be the first character. Spaces are also valid password characters. Leading spaces are ignored; trailing spaces are recognized. Step 3 Enter a host name for the NRP-1. The default host name is prompt. Router.
Chapter3 Basic NRP Configuration NRP-1 Configuration Segmentation and Reassembly Buffer Management In Cisco IOS Release 12.1(1)DC, the following segmentation and reassembly (SAR) buffer management enhancements were introduced: • Reduced Segmentation Buffer Size—Prior to this release, the default size of the PVC segmentation buffer was 256 packets. This meant that each PVC could queue up to 256 packets to be segmented and sent.
Chapter3 Basic NRP Configuration NRP-1 Configuration Verifying the PVC Segmentation Buffer Size To verify successful configuration of the segmentation buffer size, use the show running-config EXEC command. Setting the I/O Memory Size To manually set the size of I/O memory, enter the following command in ROMMON mode: Command Purpose Rommon> IOMEM=size Sets the size, in MB, of I/O memory. Allowed values depend on the amount of DRAM on your NRP, and they are listed in Table3-1 .
Chapter3 Basic NRP Configuration NRP-2 and NRP-2SV Configuration 3407872 7602176 129016 - * 249884 3905620 128049 - flash nvram flash flash opaque opaque network nvram opaque network network rw rw rw rw rw rw rw rw wo rw rw sec-bootflash: sec-nvram: bootflash: flash: null: system: tftp: nvram: lex: rcp: ftp: Router# Use the dir command to show the contents of a file system.
Chapter3 Basic NRP Configuration NRP-2 and NRP-2SV Configuration Restrictions For a complete list of restrictions, limitations, and supported features, see the release notes for the software version running on your NRP-2. This section describes the following limitations: • Soft PVCs Between the NRP-2 and NSP • Maximum Transmission Unit • VPI and VCI Limitation Soft PVCs Between the NRP-2 and NSP Soft PVCs between the NRP-2 and NSP are not supported.
Chapter3 Basic NRP Configuration NRP-2 and NRP-2SV Configuration Methods Available for Configuring the NRP-2 There are two methods available for accessing the NRP-2: • Accessing the NRP-2 Console Through the NSP • Using Telnet to Connect to the NRP-2 from the NSP You can also configure the NRP-2 with the Cisco 6400 Service Connection Manager, Release 2.2(1) and later. For more information, see theCisco 6400 SCM documentation.
Chapter3 Basic NRP Configuration NRP-2 and NRP-2SV Configuration 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 available Press RETURN to get started.
Chapter3 Basic NRP Configuration NRP-2 and NRP-2SV Configuration Password: NSP> NSP> nrps6 Trying 10.6.0.2 ... Open 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 The NRP-2 ATM interface to the backplane supports a maximum packet size, or maximum transmission unit (MTU), of 1900 bytes.
Chapter3 Basic NRP Configuration NRP-2 and NRP-2SV Configuration Example—Cisco 7200 7200# show interface atm 1/0 ATM1/0 is up, line protocol is up Hardware is ENHANCED ATM PA MTU 4470 bytes, sub MTU 4470, BW 149760 Kbit, DLY 80 usec, ... Example—Cisco 6400 NRP-1 NRP-1# show interface atm 0/0/0 ATM0/0/0 is up, line protocol is up Hardware is ATM-SAR MTU 4470 bytes, sub MTU 4470, BW 156250 Kbit, DLY 80 usec, ...
Chapter3 Basic NRP Configuration NRP-2 and NRP-2SV Configuration In the following example, the network neighbor MTU size is reduced to 1900 to match the MTU size of the NRP-2. ! interface ATM0/0/0 mtu 1900 no ip address atm vc-per-vp 2048 no atm ilmi-keepalive ! Verifying 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 Use the show interface atm 0/0/0[.
Chapter3 Basic NRP Configuration NRP-2 and NRP-2SV Configuration Table3-3 Allowed Entries for the number Argument NRP-2SV 2 1 NRP-2 VCI Range VCI Bits VPI Range VPI Bits VPI Range VPI Bits 2048 0–2047 11 0–31 5 0–7 3 4096 0–4095 12 0–15 4 0–3 2 8192 0–8191 13 0–7 3 0–1 1 number 1. Notice that the smallest allowed number entry is 64.
Chapter3 Basic NRP Configuration NRP-2 and NRP-2SV Configuration Saving the NRP-2 Startup Configuration To save the NRP-2 running configuration to NVRAM as the startup configuration, use the copy EXEC command: NRP-2# copy system:running-config nvram:startup-config Destination filename [nrp-startup-config]? 847927 bytes copied in 280.
Chapter3 Basic NRP Configuration NRP-2 and NRP-2SV Configuration Troubleshooting and Monitoring the NRP-2 Use the following debug commands to troubleshoot the NRP-2: Debug Command (Entered on the NRP-2) Purpose Router# debug se64 {detail | errors } Displays debug messages for the NRP-2 ATM SAR. Router# debug xconn Tracks the requests and responses for the cross-connect information protocol. Router# debug pmbox Displays debug messages for traffic flowing on the NRP-2 PAM mailbox serial interface.
Chapter3 Basic NRP Configuration NRP-2 and NRP-2SV Configuration NSP# who Line * 0 con 0 18 vty 0 Interface User User Host(s) idle 10.6.0.2 Idle Location 00:00:00 00:03:07 20.1.5.
Chapter3 Basic NRP Configuration NRP-2 and NRP-2SV Configuration Example—Using the show line Command on the NRP-2 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 0 Tty Typ Tx/Rx * 0 CTY - A Modem - Roty AccO AccI - Uses 0 Noise 0 Line 0, Location:"", Type:"" Length:24 lines, Width:80 columns Status:PSI Enabled, Ready, Active, Automore On Capabilities:Software Flowcontrol In, Software Flowcontrol Out Modem s
Chapter3 Basic NRP Configuration NRP-2 and NRP-2SV Configuration Example—Using the show controller async Command on the NSP 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 async Async NRP2 Pam bus controller TTY line 1 not available TTY line 2 not available TTY line 3 not available TTY line 4 not available TTY line 5 not available TTY line 6 PAM bus data for mailbox at 0xA8A8FFC0
Chapter3 Basic NRP Configuration Transferring an NRP-1 Configuration to an NRP-2 or NRP-2SV Transferring an NRP-1 Configuration to an NRP-2 or NRP-2SV This section describes how to properly transfer an existing NRP-1 configuration to an NRP-2 or NRP-2SV. Unless a clear distinction is made, all references to the NRP-2 also apply to the NRP-2SV. Complete the following steps: Step 1 Copy the existing NRP-1 configuration to a location where you can edit the file: Router# copy flash:my.cfg tftp://10.1.1.
Chapter3 Basic NRP Configuration Permanent Virtual Circuits The following sections describe common methods of configuring PVCs: • Configuring PVCs on the ATM Interface, page 3-21 • Configuring PVCs on ATM Subinterfaces , page 3-22 • Configuring VC Classes , page 3-24 • Configuring PVC Discovery, page 3-26 • Configuring PVC Traffic Shaping, page 3-28 For more general information on configuring PVCs, refer to the “Configuring ATM” chapter in the CiscoIOS Wide-Area Networking Configuration Guide as
Chapter3 Basic NRP Configuration Permanent Virtual Circuits Example—PVC with PPPoA on an ATM Interface The following example shows a typical PVC configuration for PPP over ATM (PPPoA). For information on configuring PPPoA, see the“PPPoA Baseline Architecture”white paper on Cisco.com.
Chapter3 Basic NRP Configuration Permanent Virtual Circuits To configure a PVC on an ATM subinterface, complete the following steps beginning in global configuration mode: Command Description Step1 Router(config)# interface atm 0/0/0 .subinterface {multipoint | point-to-point} Specifies the NRP ATM subinterface. Also selects multipoint or point-to-point subinterface type. Step2 Router(config-subif)# pvc [name] vpi/vci Configures a new ATM PVC by assigning a name (optional) and VPI/VCI values.
Chapter3 Basic NRP Configuration Permanent Virtual Circuits Example—PVCs on Subinterfaces with Encapsulation Type Inherited from the Main ATM Interface In the following example, PVCs 0/70 and 0/71 on ATM subinterface 0/0/0.40 inherit the AAL5 multiplex (MUX) encapsulation type from the main ATM interface. PVC 0/72 is specifically configured for AAL5 SNAP, overriding the inherited encapsulation type.
Chapter3 Basic NRP Configuration Permanent Virtual Circuits To configure and apply a VC class directly to a PVC, complete the following steps beginning in global configuration mode: Command Purpose Step1 Router(config)# vc-class atm name Creates or selects a map class. Step2 Router(config-vc-class)# encapsulation aal-encap [ppp virtual-template number] Configures the ATM adaptation layer (AAL) and encapsulation type.
Chapter3 Basic NRP Configuration Permanent Virtual Circuits interface atm 0/0/0 class-int snap pvc 0/40 ! pvc 0/41 ! pvc 0/42 ip address 172.25.14.198 255.255.255.0 ! ! interface atm 0/0/0.2 multipoint pvc 0/43 ! pvc 0/44 class-vc ppp-atm ! ! Verifying VC Classes To verify successful configuration of VC classes, use the show atm vc EXEC command. Check that the VC class properties (encapsulation) are inherited by the appropriate PVCs.
Chapter3 Basic NRP Configuration Permanent Virtual Circuits Command Purpose Step8 Router(config-if)# interface atm 0/0/0. subinterface-number {multipoint | point-to-point} (Optional) Specifies the ATM subinterface. Also selects multipoint or point-to-point subinterface type. Step9 Router(config-if)# class-int vc-class-name or Router(config-subif)# class-int vc-class-name Associates a VC class with the interface or subinterface.
Chapter3 Basic NRP Configuration Permanent Virtual Circuits Verifying PVC Discovery To verify successful configuration of PVC discovery, use the show atm vc interface atm 0/0/0 EXEC command. Discovered interfaces appear with the “PVC-D” type. Router# show atm vc interface atm VCD / Interface Name VPI VCI 0/0/0 1 0 16 0/0/0.1 2 1 32 0/0/0.1 3 1 33 0/0/0.2 4 2 32 0/0/0.
Chapter3 Basic NRP Configuration Permanent Virtual Circuits Example—Traffic Shaping a PVC with UBR QoS In the following example, PVC 0/40 is configured with the UBR QoS class, at a peak cell rate of 512kbps: ! interface atm 0/0/0 pvc 0/40 encapsulation aal5snap ubr 512 ! Example—Traffic Shaping a PVC with VBR-NRT In the following example, PVC 103/100 is configured with the VBR-NRT QoS class, with a peak cell rate of 512 kbps, a sustained cell rate of 16 kbps, and a burst rate of 10 kbps: ! interface AT
Chapter3 Basic NRP Configuration Permanent Virtual Circuits Cisco 6400 Software Setup Guide 3-30 OL-1183-04
C H A P T E R 4 Node Line Card Interface Configuration The plug-and-play mechanisms of the Cisco 6400 allow it to come up automatically. All configuration information for node line cards (NLCs) can be saved between hot swaps and switch reboots, while interface types are automatically discovered by the switch, eliminating mandatory manual configuration.
Chapter4 Node Line Card Interface Configuration Autoconfiguration Autoconfiguration Enabled by default, autoconfiguration determines the interface type each time an interface initially comes up. To manually configure an NLC interface, you must disable autoconfiguration. Disabling Autoconfiguration Autoconfiguration is enabled by default, but can be disabled to manually configure an NLC interface.
Chapter4 Node Line Card Interface Configuration ATM Interface Types Verifying Autoconfiguration To check if autoconfiguration is enabled or disabled on an NLC interface, use the show atm interface EXEC command.
Chapter4 Node Line Card Interface Configuration ATM Interface Types Figure4-1 Note UNI Example The UNI interface is the default for NLCs designed for the Cisco 6400. See Table4-1 for the other parameters of the default NLC interface configuration.
Chapter4 Node Line Card Interface Configuration ATM Interface Types Verifying UNI Configuration To verify UNI configuration for an ATM interface, use the show atm interface EXEC command: Switch# show atm interface atm 3/0/0 Interface: IF Status: Auto-config: IF-Side: ATM0/1/0 UP disabled Network Port-type: Admin Status: AutoCfgState: IF-type: oc3suni up not applicable UNI Uni-type: ... private Uni-version: V3.
Chapter4 Node Line Card Interface Configuration ATM Interface Types Example In the following example, ATM 3/0/0 is configured as an NNI: ! interface atm 3/0/0 no atm auto-configuration atm nni ! Verifying NNI Configuration To verify NNI configuration for an ATM interface, use the show atm interface EXEC command: Switch# show atm interface atm 3/0/0 Interface: IF Status: Auto-config: ATM3/0/0 UP disabled Port-type: oc3suni Admin Status: up AutoCfgState: not applicable IF-Side: Uni-type: Network not
Chapter4 Node Line Card Interface Configuration ATM Interface Types Configuring IISP Interfaces To manually configure an IISP interface, complete the following steps beginning in global configuration mode: Command Purpose Step1 Switch(config)# interface atm slot/subslot/port Specifies an ATM interface and enters interface configuration mode. Step2 Switch(config-if)# no atm auto-configuration Disables autoconfiguration on the interface.
Chapter4 Node Line Card Interface Configuration NLC Interface Clocking Input cells: 264089 Output cells: 273253 5 minute input rate: 0 bits/sec, 0 cells/sec 5 minute output rate: 0 bits/sec, 0 cells/sec Input AAL5 pkts: 172421, Output AAL5 pkts: 176993, AAL5 crc errors: 0 NLC Interface Clocking Each NLC port can be configured to support the following clocking options: • Free-running—Transmit clock is derived from the local oscillator on the NLC port, with stratum level 4 accuracy.
Chapter4 Node Line Card Interface Configuration OC-3 NLC and OC-12 NLC Interface Options • STS-12c—Synchronous Transport Signal level 12, concatenated (12 x 51.84 Mbps). SONET format that specifies the frame structure for the 5184-Mbps lines used to carry ATM cells. (Default for OC-12 NLC.
Chapter4 Node Line Card Interface Configuration DS3 NLC Interface Options DS3 NLC Interface Options The DS3 NLC supports the following framing modes: • cbitadm—C-bit with ATM direct mapping (default framing mode) • cbitplcp—C-bit with physical layer convergence procedure (PLCP) framing • m23adm—M23 ATM direct mapping • m23plcp—M23 with PLCP framing The DS3 NLC supports the cell payload scrambling mode, which scrambles only the payload of the cell (not the header).
Chapter4 Node Line Card Interface Configuration Troubleshooting the NLC Interface Configuration Verifying the DS3 Interface Configurations To verify successful configuration of DS3 interfaces, use the show controllers atm EXEC command. Check that the output displays the interface options you configured.
Chapter4 Node Line Card Interface Configuration Troubleshooting the NLC Interface Configuration Cisco 6400 Software Setup Guide 4-12 OL-1183-04
C H A P T E R 5 Redundancy and SONET APS Configuration The Cisco 6400 contains two slots for node switch processors (NSPs) and eight slots for node line cards (NLCs) or node route processors (NRPs), as shown in Figure5-1. Each slot can contain one full-height or two half-height cards. NRPs and NSPs support enhanced high system availability (EHSA) redundancy, and NLCs support SONET automatic protection switching (APS) redundancy at the port-level.
Chapter5 Redundancy and SONET APS Configuration Memory Requirements Figure5-1 Cisco 6400 Carrier-Class Broadband Aggregator Memory Requirements When configuring redundancy between two NRPs or two NSPs, the two cards must have identical hardware configurations.
Chapter5 Redundancy and SONET APS Configuration NSP Redundancy NSP Redundancy Both NSP slots are numbered slot 0 for consistent interface identification between primary and secondary devices. Nevertheless, the left NSP slot is labeled slot A and the right slot is labeled slot B to distinguish between the two slots, when required. You can use EHSA redundancy for simple hardware backup or for software error protection.
Chapter5 Redundancy and SONET APS Configuration NSP Redundancy Primary (NSP A) ehsa state:SANTA_EHSA_PRIMARY Secondary (NSP B) ehsa state:SANTA_EHSA_SECONDARY EHSA pins: peer present = 1 peer state = SANTA_EHSA_SECONDARY crash status:this-nsp=NO_CRASH(0x1) peer-nsp=NO_CRASH(0x1) EHSA related MAC addresses: this bpe mac-addr = 0000.0c00.0003 peer bpe mac-addr = 0000.0c00.
Chapter5 Redundancy and SONET APS Configuration NSP Redundancy Verifying Synchronized NSPs To verify that NVRAM and sec-NVRAM contain identical startup configurations, compare the output of the following command entries: Switch# cd nvram: Switch# dir Switch# more startup-config Switch# cd sec-nvram: Switch# dir Switch# more startup-config The displayed output should be identical.
Chapter5 Redundancy and SONET APS Configuration NSP Redundancy Disk mirroring provides full NSP redundancy for the NRP-2, which depends on the NSP for image and file storage. Without disk mirroring, there is no guarantee of NRP-2 support after an NSP failover (user intervention might be required to restore the NRP2 state to that prior to the failover). With disk mirroring enabled, NRP-2 has continued support from the NSP, except during the relatively short NSP failover period.
Chapter5 Redundancy and SONET APS Configuration NSP Redundancy Disabling PCMCIA Disk Mirroring Disk mirroring is enabled by default. To disable disk mirroring, complete the following steps beginning in global configuration mode: Command Purpose Step1 Switch(config)# redundancy Enters redundancy configuration mode. Step2 Switch(config-r)# main-cpu Enters main-cpu configuration mode. Step3 Switch(config-r-mc)# no mirror Disables data synchronization between the NSP PCMCIA disks.
Chapter5 Redundancy and SONET APS Configuration NSP Redundancy Verifying that Disk Mirroring is Enabled To verify that disk mirroring is enabled, complete one or both of the following steps: Step 1 Use the show redundancy sync-status EXEC command to check that disk mirroring is enabled: Switch# show redundancy sync-status Disk Mirror is enabled in configuration:proper sync (Mirror threshold is 0 MB:smaller files will be copied blindly) Peer Secondary NSP is present disk1 or sec-disk1 is wrong or missing
Chapter5 Redundancy and SONET APS Configuration NSP Redundancy Verifying the File Size Threshold To verify the file size threshold, use the show redundancy sync-status EXEC command, and check the Mirror Threshold field: Switch# show redundancy sync-status Disk Mirror is enabled in configuration:proper sync (Mirror threshold is 2 MB:smaller files will be copied blindly) Peer Secondary NSP is present disk1 or sec-disk1 is wrong or missing mir-disk0 (disk0 -> sec-disk0):out of sync.
Chapter5 Redundancy and SONET APS Configuration NSP Redundancy mir-disk1 (disk1 -> sec-disk1):out of sync. Disk Mirror full sync is in progress (disk0 to sec-disk0, 23%) Switch# Initiating PCMCIA Disk Synchronization Disk synchronization copies the data from one PCMCIA disk to another.
Chapter5 Redundancy and SONET APS Configuration NSP Redundancy Verifying Disk Synchronization To verify disk synchronization, complete one or both of the following steps: Step 1 Use the show redundancy sync-status EXEC command to check that the disk content is synchronized: Switch# show redundancy sync-status Disk Mirror is enabled in configuration:proper sync (Mirror threshold is 0 MB:smaller files will be copied blindly) Peer Secondary NSP is present disk1 or sec-disk1 is wrong or missing mir-disk0(dis
Chapter5 Redundancy and SONET APS Configuration NSP Redundancy Troubleshooting and Monitoring PCMCIA Disk Mirroring Use the show redundancy sync-status EXEC command to display all status information on disk mirroring and synchronization. Use the debug disk-mirror EXEC command to display debug messages for IFS call events, disk write events, and disk synchronization events. Using NSP Redundancy for Hardware Backup For simple hardware backup, the redundant NSPs must have the same system image.
Chapter5 Redundancy and SONET APS Configuration NSP Redundancy Verifying NSP Redundancy for Hardware Backup To verify that the NSP redundancy is configured for hardware backup, use the show bootvar and dir EXEC commands from Step 1 and Step 2. Check that both NSPs use the same system image and store the image in identical locations. Using NSP Redundancy for Software Error Protection For software error protection, the primary and secondary NSPs should have different system images.
Chapter5 Redundancy and SONET APS Configuration NSP Redundancy Step 6 Save the configuration file to the startup configuration in NVRAM. Because automatic synchronization is enabled, this step saves the boot system commands to both NSP startup configurations. Switch# copy system:running-config nvram:startup-config Step 7 If the primary NSP is not running the correct image, reset both NSPs.
Chapter5 Redundancy and SONET APS Configuration NRP Redundancy Note Make sure the DHCP server is properly set up with appropriate dynamic and static pools of IP addresses. Example In the following example, the NSP network management interface is configured for DHCP IP address acquisition. This allows you to boot redundant NSPs from a network server.
Chapter5 Redundancy and SONET APS Configuration NRP Redundancy Verifying NRP Redundancy To verify NRP redundancy, use the show redundancy EXEC command on the NRP: Router# show redundancy Primary NRP in slot 2, system configured non redundant User EHSA configuration (by CLI config): slave-console = off keepalive = on config-sync modes: standard = on start-up = on boot-var = on config-reg = on NSP EHSA configuration (via pam-mbox): redundancy = off preferred (slot 2) = yes Debug EHSA Information: NRP speci
Chapter5 Redundancy and SONET APS Configuration NLC Redundancy Verifying Erased Startup Configurations To verify that you erased the startup configuration on redundant NRPs, use the dir nvram: and dirsec-nvram: EXEC commands and check that the startup-config size is zero: NRP# dir nvram: Directory of nvram:/ 1 -rw- 0 startup-config 129016 bytes total (129016 bytes free) You can also use the show startup EXEC command and make sure that a valid configuration file does not appear: NRP# show s
Chapter5 Redundancy and SONET APS Configuration NLC Redundancy Example In the following example, the OC-12s in slots 5 and 6 are configured for redundancy: ! redundancy associate slot 5 6 ! Configuring Redundant Half-Height NLCs For two half-height NLCs to act as a redundant pair, they must be installed in one of the following slot/subslot pairs: Note • 1/0 and 2/0, or 1/1 and 2/1 • 3/0 and 4/0, or 3/1 and 4/1 • 5/0 and 6/0, or 5/1 and 6/1 • 7/0 and 8/0, or 7/1 and 8/1 By default, the NLC in
Chapter5 Redundancy and SONET APS Configuration SONET APS for NLC Port Redundancy SONET APS for NLC Port Redundancy SONET automatic protection switching (APS) provides a mechanism to support redundant transmission interfaces (circuits) between SONET devices. Automatic switchover from the working (primary) circuit to the protection (secondary) circuit happens when the working circuit fails or degrades.
Chapter5 Redundancy and SONET APS Configuration SONET APS for NLC Port Redundancy Example—Disabling Redundancy and SONET APS The following table shows example configurations before and after redundancy is turned off: Redundancy On After Redundancy Is Turned Off redundancy associate slot 1 2 ! interface ATM1/0/0 no ip address no ip redirects no ip proxy-arp no atm auto-configuration no atm ilmi-keepalive atm uni version 4.
Chapter5 Redundancy and SONET APS Configuration SONET APS for NLC Port Redundancy To set the APS priority requests, use the following commands in EXEC mode: Command Purpose Switch# aps lockout atm slot/subslot/port APS priority level 1 request. Prevents a working interface from switching to a protection interface. Switch# aps force atm slot/subslot/port from [protection | working] APS priority level 2 request.
Chapter5 Redundancy and SONET APS Configuration Primary and Secondary Role Switching The aps signal-degrade BER threshold command controls the BER value at which a signal degrade is announced, indicating an unstable or error-prone connection. This BER threshold can be in the range of 10 - 5 to 10 - 9, and there is no default threshold. The aps signal-fail BER threshold command controls the BER value at which a signal failure is announced, indicating a broken connection.
Chapter5 Redundancy and SONET APS Configuration Primary and Secondary Role Switching Reversing NSP and NRP Redundancy Roles To reverse the primary and secondary roles in a redundant pair of NSPs or NRPs, use the following command in EXEC mode: Command Purpose Switch# redundancy force-failover {slot | slot/subslot | main-cpu} Forces the system to switch the current primary and secondary devices of the redundant pair.
Chapter5 Redundancy and SONET APS Configuration Primary and Secondary Role Switching Cisco 6400 Software Setup Guide 5-24 OL-1183-04
C H A P T E R 6 SNMP, RMON, and Alarm Configuration This chapter contains information on the following system management topics: • Simple Network Management Protocol, page 6-1 • Remote Monitoring, page 6-4 • Alarms, page 6-4 Simple Network Management Protocol Simple Network Management Protocol (SNMP) is an application-layer protocol that allows an SNMP manager, such as a network management system (NMS), and an SNMP agent on the managed device to communicate.
Chapter6 SNMP, RMON, and Alarm Configuration Simple Network Management Protocol Note The SNMPv3 Proxy Forwarder feature was introduced in Cisco IOS Releases 12.1(4)DB and 12.1(4)DC for the node route processor 2 (NRP-2). The feature is not supported in earlier releases or by the node route processor 1 (NRP-1).
Chapter6 SNMP, RMON, and Alarm Configuration Simple Network Management Protocol Task 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 in global configuration mode: Command (Entered on the NRP-2) Purpose Step1 Router(config)# snmp-server group groupname v3 noauth Configures a new SNMPv3 group. Make sure that the groupname argument entry matches that entered on the NSP in Task1.
Chapter6 SNMP, RMON, and Alarm Configuration Remote Monitoring Verifying the SNMPv3 Proxy Forwarder To verify successful configuration of the SNMPv3 Proxy Forwarder feature, use the moresystem: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.
Chapter6 SNMP, RMON, and Alarm Configuration Alarms To set thresholds for the minor and major temperature alarms at the two monitored locations, use the following command in global configuration mode: Command Purpose Switch(config)# facility-alarm [intake-temperature | core-temperature] [minor °C | major °C] Specifies thresholds for the intake and core major and minor alarms in degrees Celsius.
Chapter6 SNMP, RMON, and Alarm Configuration Alarms Clearing Alarms You can use the clear facility-alarm EXEC command to reset the external alarm relays and stop an auditory alarm indication. However, the alarm cause and LED indication may still be in effect, and the alarm can be viewed with the show facility-alarm status EXEC command until the alarm is cleared at the source.
A P P E N D I X A Web Console This chapter tells you how to use the online Web Console, a graphical user interface (GUI), to set or change the system configuration and monitor system activity. The Web Console application communicates with the system by translating HTML pages into Cisco IOS commands. You can enter similar configuration parameters for your system using the command-line interface (CLI).
AppendixA Web Console Web Console Installation Web Console Installation Before you can use the Web Console to configure your Cisco 6400, you must install the Web Console HTML pages. You can install the Web Console from the PCMCIA disk in the node switch processor (NSP) disk slot 0 (disk0:) or from a TFTP server. After the HTML pages are installed, they can be updated at any time using the procedure described in the “Loading New Web Console Pages” section on pageA-24.
AppendixA Web Console Web Console Installation Installing the Web Console from the PCMCIA Disk To install the Web Console pages from the PCMCIA disk, complete the following steps in EXEC mode: Step 1 Insert the PCMCIA disk with the Web Console image into disk slot 0 of the NSP. Step 2 Create a directory, nsp-html , for the Web Console files on disk0:.
AppendixA Web Console Using the Web Console Running the Web Console After you have installed Web Console on the NSP, open a browser (Netscape Navigator 4.x or above or Microsoft Internet Explorer 4.x or above) on any other workstation, using the following settings: • Enable the JavaScript option. • Set the browser memory and disk cache sizes to a minimum or 4096 kilobytes. • Set the browser cache to local disk.
AppendixA Web Console Using the Web Console TableA-1 Features, Default Settings, and Web Console Pages Feature Default Setting Web Console Page Management Switch IP address, subnet mask, domain, and default gateway 0.0.0.
AppendixA Web Console Using the Web Console FigureA-1 Update Page The Update page allows you to confirm the changes you just made to the system configuration, before actually applying them to the running configuration of your switch. This page also indicates whether or not any errors occurred when the information was transferred to the operating system. If you are sure that you want to apply the changes to the running configuration, click Update Page. If you want to discard your changes, click Close.
AppendixA Web Console Using the Web Console FigureA-2 Save As Window Step 2 Click the button that corresponds to where you want the configuration you just entered to be stored. Step 3 Enter a filename if you are saving to a file. Step 4 Click the Save button. Accessing the Web Console The switch must have an IP address before you can access the Web Console. Follow the prompts when you install the switch to assign an IP address and other IP information.
AppendixA Web Console Basic System Configuration Page FigureA-3 Cisco Systems Access Page From the Access page, you can also open a Telnet connection to the NSP, show interfaces, show diagnostics, monitor the NSP, and display technical support information. You can also access Cisco.com, the Cisco Systems customer website, from the Web Console home page. From Cisco.com, you can download the latest software and display the latest Cisco 6400 carrier-class broadband aggregator documentation.
AppendixA Web Console Basic System Configuration Page FigureA-4 Basic System Configuration Navigating in Web Console After you have started the Web Console and displayed the Cisco 6400 home page (FigureA-4), you can use the action bar at the top of each page to move between pages. TableA-2 lists the functions that are available for each action bar selection.
AppendixA Web Console Basic System Configuration Page Entering Basic Configuration Parameters This information is usually entered once and not changed. Click Apply after entering information in the fields, Revert to return values to the previous settings, or Save As to save the configuration. Each of the fields is described in TableA-3. TableA-3 System Configuration Field Descriptions Field Description System Name Enter a name for the Cisco 6400 system.
AppendixA Web Console Basic System Configuration Page FigureA-5 Note Advanced System Configuration To return to the System Configuration page, click System in the Action bar. Enter the System Reload Options and Core Dump parameters described in TableA-4 and then click Apply.
AppendixA Web Console Basic System Configuration Page TableA-4 Advanced System Configuration Field Descriptions Field Description System Reload Options System Image File Enter the path and name of the Cisco IOS image file to be loaded when the system reboots. Configuration File Enter the path and the name of the configuration file that the image file reads to configure the system.
AppendixA Web Console Configuring Redundancy Configuring Redundancy Use the Redundancy page to set up redundant CPUs, slots, and subslots. This page also allows you to set the primary/secondary relationship between redundant pairs. To display this page, click Redundancy on the action bar. FigureA-6 shows the slots and subslots listed on the redundancy page. FigureA-6 Redundancy Page For more information about configuring redundancy, see Chapter 5, “Redundancy and SONET APS Configuration.
AppendixA Web Console IP Address Management For the CPU, you can also set the configuration synchronization option as described in the “Synchronizing Redundant NSPs” section on page5-4. IP Address Management To manage the IP address used for the NME port, static IP routes, and DNS servers, use the Mgmt IP page. (See FigureA-7.) To display this page, click Mgmt IP on the action bar. Caution Changing the switch IP address on this page will end your Web Console session.
AppendixA Web Console IP Address Management Note If the Cisco 6400 is configured for NME consolidation, do not use the Web Console to configure management information. See the “Network Management Ethernet Interface” section on page2-6 for more information. Follow these steps to enter the IP parameters for the management Ethernet: Step 1 Enter the subnet mask (Mgmt Ethernet Mask) for the switch. Step 2 Enter the broadcast address for the switch. Step 3 Enter the domain name of the NME.
AppendixA Web Console SNMP Management Adding and Removing Domain Name Servers A Domain Name Server (DNS) converts domain names into their corresponding IP addresses. To define DNS servers that are used on the NME, follow these steps: Step 1 Enter the Ethernet address of a new DNS in the New Server field. Step 2 Click Add. To remove a DNS, follow these steps: Step 1 Select the DNS you want to remove from the list of current servers. Step 2 Click Remove.
AppendixA Web Console SNMP Management FigureA-8 SNMP Page Entering System Options System Option information is used by network management applications to identify the switch on a topology map. To begin entering the information, proceed as follows: Step 1 Enter a name to be used for the system. Step 2 Enter the location of the system. Step 3 Enter the name of a person or organization associated with the system. Step 4 Click Apply to save the current information to your running configuration.
AppendixA Web Console SNMP Management Entering Community Strings Community strings serve as passwords for SNMP messages. You can enter them with either of the following characteristics: • Read Only—Enables requests accompanied by the string to display MIB-object information • Read and Write—Enables requests accompanied by the string to display MIB-object information and to set MIB objects To supply a community string, proceed as follows: Step 1 Enter a character string in the String field.
AppendixA Web Console NRP Status NRP Status The NRP page allows you to display information about any of the node route processors (NRPs) installed in the Cisco 6400 chassis. To display the NRP page (FigureA-9 ), click NRP in the action bar. FigureA-9 NRP Page Subscriber Management Use the Subscriber Setup page (see FigureA-10) to set and display the cross-connections for each of your current system subscribers.
AppendixA Web Console Subscriber Management FigureA-10 Subscriber Setup Page Adding and Removing Subscribers To add new subscribers and set up the virtual circuits, follow these steps: Step 1 Select the ATM interface into which the subscriber packets arrive at the switch. Step 2 Enter the incoming VPI. Step 3 Enter the incoming VCI. Step 4 Enter the outgoing (egress) ATM interface. This is the other side of the cross-connection. Step 5 Enter the outgoing VPI and VCI. Step 6 Click Add.
AppendixA Web Console Subscriber Management FigureA-11 VC Subscriber Setup Page—Cisco IOS Release 12.0(7)DB1 To remove subscribers, follow these steps: Step 1 Select a subscriber from the list of subscribers. Step 2 Click Remove. Step 3 Click Apply to save the current subscribers to your running configuration. Step 4 Click Save As to save the current subscribers to your configuration file, Flash memory, disk, or TFTP server.
AppendixA Web Console System Status FigureA-12 VP Subscriber Setup Page—Cisco IOS Release 12.0(7)DB1 System Status This page has a live image (see FigureA-13) of the system that displays much of the same information as the LEDs on the front of the system. You can use this image in the following ways: • Display the status of ports. Colors indicate the status. • Display the status and redundancy configuration of the NSPs.
AppendixA Web Console System Status FigureA-13 System Status Cisco 6400 Software Setup Guide OL-1183-04 A-23
AppendixA Web Console Loading New Web Console Pages Loading New Web Console Pages Cisco 6400 systems are shipped with the Web Console pages described in this chapter. However, from time to time, you might want to load updated Web Console pages into local memory (either Flash memory or Flash disk) on your system. To load new Web Console pages onto your system, perform the following tasks from the privileged EXEC mode: Command Purpose Step1 copy tftp://tftpservername/../c6400s-html.
A P P E N D I X B Upgrading Software on the Cisco 6400 This appendix describes how to upgrade the software images on the Cisco 6400 carrier-class broadband aggregator, and contains the following sections: • Recommendations , page B-1 • Upgrading Software on Nonredundant NRP-1s, page B-2 • Upgrading Software on Nonredundant NRP-2s and NRP-2SVs, page B-4 • Upgrading Software on Nonredundant NSPs , page B-5 • Upgrading Software on Redundant NRP-1s, page B-8 • Upgrading Software on Redundant NSPs,
AppendixB Upgrading Software on the Cisco 6400 Upgrading Software on Nonredundant NRP-1s • If you are using the Web Console, use the same version level for the NSP system image and the Web Console image. Upgrading Software on Nonredundant NRP-1s This section describes how to upgrade software on an NRP-1 that is not configured for redundancy. To upgrade software on redundant NRP-1s, see the “Upgrading Software on Redundant NRP-1s” section on pageB-8 .
AppendixB Upgrading Software on the Cisco 6400 Upgrading Software on Nonredundant NRP-1s Step 11 If you set the config register to 0x0 in Step 8, you will see the rommon prompt after completion of the NRP-1 reload. Complete the following steps to manually boot the NRP-1 and set it up for automatic reboot. a. Use the dir command to locate and identify the new image. rommon 1 > dir flash: b. Use the boot command to manually boot the NRP-1. rommon 2 > boot flash:c6400r-g4p5-mz.122-13.
AppendixB Upgrading Software on the Cisco 6400 Upgrading Software on Nonredundant NRP-2s and NRP-2SVs Router(config)# end Router# copy system:running-config nvram:startup-config 00:03:03:%SYS-5-CONFIG_I:Configured from console by console mem Warning:Attempting to overwrite an NVRAM configuration previously written by a different version of the system image. Overwrite the previous NVRAM configuration?[confirm] Building configuration...
AppendixB Upgrading Software on the Cisco 6400 Upgrading Software on Nonredundant NSPs Step 3 Use the more system:running-config EXEC command to view the current NRP-2 image configuration. Switch# more system:running-config ... hw-module slot 2 image c6400r2sp-g4p5-mz.121-4.DC1 priority 2 hw-module slot 2 image tftp://10.1.1.1/c6400r2sp-g4p5-mz.121-4.DC1 priority 3 hw-module slot 2 image disk0:MyDir/c6400r2sp-g4p5-mz.121-4.DC1 priority 4 hw-module slot 3 image c6400r2sp-g4p5-mz.121-4.DC1 priority 2 ...
AppendixB Upgrading Software on the Cisco 6400 Upgrading Software on Nonredundant NSPs Step 4 Use the copy EXEC command to load the new images. Switch# copy tftp://10.1.1.1/c6400s-wp-mz.DB1 disk0:c6400s-wp-mz.DB1 Switch# copy tftp://10.1.1.1/c6400s-html.tar.DB1 disk0:c6400s-html.tar.DB1 Switch# copy tftp://10.1.1.1/c6400s-wp-mz.DB1 bootflash:c6400s-wp-mz.DB1 Step 5 Use the no boot system global configuration command to remove the old startup image configuration.
AppendixB Upgrading Software on the Cisco 6400 Upgrading Software on Nonredundant NSPs 2277 2223 -rw-rw- 91833 4504276 Jul 27 2000 10:25:19 Aug 03 2000 09:44:01 pvc-config c6400s-wp-mz.120-7.DB 20819968 bytes total (16121856 bytes free) Switch# show version Cisco Internetwork Operating System Software IOS (tm) C6400 Software (C6400S-WP-M), Version 12.0(7)DB, EARLY DEPLOYMENT RELEASE SOFTWARE (fc1) TAC:Home:SW:IOS:Specials for info Copyright (c) 1986-2000 by cisco Systems, Inc.
AppendixB Upgrading Software on the Cisco 6400 Upgrading Software on Redundant NRP-1s Upgrading Software on Redundant NRP-1s This section describes how to upgrade software on redundant NRP-1s. To upgrade software on a nonredundant NRP-1, see the “Upgrading Software on Nonredundant NRP-1s” section on pageB-2. To upgrade the software images on redundant NRP-1s, perform the following tasks in the specified order. Each task in the list identifies the device used to perform the task: 1.
AppendixB Upgrading Software on the Cisco 6400 Upgrading Software on Redundant NRP-1s Identify the New System Image as the Startup Image for the Secondary NRP-1 To ensure that the new image is used upon system reload, choose one of the following methods: • Ensuring That the New System Image Is the First File in the Flash Memory , page B-9 or • Updating the Boot System Variable, page B-10 Ensuring That the New System Image Is the First File in the Flash Memory Complete the following steps to make sure
AppendixB Upgrading Software on the Cisco 6400 Upgrading Software on Redundant NRP-1s Updating the Boot System Variable If you completed the steps described in the “Ensuring That the New System Image Is the First File in the Flash Memory” section on pageB-9, skip this section and continue with the “Reload the Secondary NRP-1” section on pageB-10. Complete the following steps from the primary NRP-1 to update both the primary and secondary NRP-1 configurations to reflect the new startup image.
AppendixB Upgrading Software on the Cisco 6400 Upgrading Software on Redundant NRP-1s Step 3 Use the delete EXEC command to mark the old images for deletion. NRPslot5# delete flash:c6400r-g4p5-mz.120-7.DC NRPslot5# delete bootflash:c6400r-boot-mz.120-7.DC Step 4 Use the squeeze EXEC command to permanently delete the images marked for deletion. NRPslot5# squeeze flash: NRPslot5# squeeze bootflash: Step 5 Use the copy EXEC command to load the new images from the secondary NRP-1.
AppendixB Upgrading Software on the Cisco 6400 Upgrading Software on Redundant NRP-1s Step 5 Use the squeeze EXEC command to permanently delete the primary NRP-1 images that are marked for deletion. NRPslot5# squeeze flash: NRPslot5# squeeze bootflash: Step 6 If you performed Step 3, use the copy EXEC command to transfer the files back from the TFTP server to the primary NRP-1’s Flash memory. NRPslot5# copy tftp://10.1.1.1/filename1 flash:filename1 NRPslot5# copy tftp://10.1.1.
AppendixB Upgrading Software on the Cisco 6400 Upgrading Software on Redundant NRP-1s Upgrading the Images on the Secondary NRP-1 In the following example, the secondary NRP-1 system image is upgraded from CiscoIOSRelease12.0(7)DC to CiscoIOS Release 12.2(13)T. NRP slot5 is the primary device in slot 5 of the Cisco 6400 chassis, and NRP slot6 is the secondary device in slot 6. NRPslot5# dir sec-flash: Directory of sec-flash:/ 1 -rw- 5018040 Aug 09 2000 12:47:44 c6400r-g4p5-mz.120-7.
AppendixB Upgrading Software on the Cisco 6400 Upgrading Software on Redundant NSPs Upgrading the Images on the Primary NRP-1 In the following example, the primary NRP-1 system image is upgraded from CiscoIOSRelease12.0(7)DC to CiscoIOS Release 12.2(13)T. NRP slot5 is the primary device, and NRP slot6 is the secondary device. NRPslot5# dir sec-flash: Directory of sec-flash:/ 1 -rw5215184 Aug 09 2000 13:09:38 c6400r-g4p5-mz.122-13.
AppendixB Upgrading Software on the Cisco 6400 Upgrading Software on Redundant NSPs Prerequisites Make sure that automatic configuration synchronization is enabled before you follow these procedures. Switch# configure terminal Switch(config)# redundancy Switch(config-r)# main-cpu Switch(config-r-mc)# auto-sync standard Upgrade the Secondary NSP Images Complete the following steps to upgrade the secondary NSP images. The NSP in slot 0A is the primary device, and the NSP in slot 0B is the secondary device.
AppendixB Upgrading Software on the Cisco 6400 Upgrading Software on Redundant NSPs Upgrade the Primary NSP Images Complete the following steps to upgrade the software images on the primary NSP. The NSP in slot 0A is still the primary device, and the NSP in slot 0B is still the secondary device. Step 1 Use the dir EXEC command to locate and identify the images you want to replace on the primary NSP.
AppendixB Upgrading Software on the Cisco 6400 Upgrading Software on Redundant NSPs Switch the Primary and Secondary NSPs Complete the following steps to switch the primary and secondary NSPs. Before this task is completed, the NSP in slot 0A is the primary device, and the NSP in slot 0B is the secondary device. Step 1 Use the redundancy force-failover EXEC command to switch the primary and secondary devices.
AppendixB Upgrading Software on the Cisco 6400 Upgrading Software on Redundant NSPs !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!! [OK - 4575296/9150464 bytes] 4575296 bytes copied in 256.468 secs (17872 bytes/sec) Reloading the Secondary NSP In the following example, the secondary NSP is reset from the primary NSP. The NSP in slot 0A is the primary device, and the NSP in slot 0B is the secondary device.
AppendixB Upgrading Software on the Cisco 6400 Upgrading Software on Redundant NSPs cisco C6400S (R4600) processor with 131072K bytes of memory. R4700 CPU at 100Mhz, Implementation 33, Rev 1.0 Last reset from s/w peripheral Bridging software. 2 Ethernet/IEEE 802.3 interface(s) 8 ATM network interface(s) 507K bytes of non-volatile configuration memory. --More-20480K bytes of ATA PCMCIA card at slot 0 (Sector size 512 bytes). 8192K bytes of Flash internal SIMM (Sector size 256K).
AppendixB Upgrading Software on the Cisco 6400 Upgrading Software on Redundant NSPs Cisco 6400 Software Setup Guide B-20 OL-1183-04
A P P E N D I X C Optimizing the Number of Virtual Connections on the Cisco 6400 This appendix describes how to optimize the number of supported virtual connections on the Cisco 6400 carrier-class broadband aggregator by: • Properly assigning virtual path identifier (VPI) and virtual channel identifier (VCI) values • Reducing Input Translation Table (ITT) memory fragmentation For general information on configuring virtual connections, see the “Configuring Virtual Connections” chapter of the ATM Switch
AppendixC Optimizing the Number of Virtual Connections on the Cisco 6400 An Overview of the ITT and Virtual Connection Limitations How VCI Values Limit the Number of Virtual Connections Each ATM interface supports VPIs as large as 8 bits (0 to 255) and VCIs as large as 14 bits (0 to16,383).
AppendixC Optimizing the Number of Virtual Connections on the Cisco 6400 Guidelines for Maximizing the Number of Virtual Connections Guidelines for Maximizing the Number of Virtual Connections Use the following methods to maximize the number of virtual connections on the Cisco 6400: • Assigning VCI Values to Maximize the Number of Entries per Block • Specifying the Minimum ITT Block Size • Using Automatic Determination of the Minimum ITT Block Size • Shrinking ITT Blocks • Displaying ITT Allocati
AppendixC Optimizing the Number of Virtual Connections on the Cisco 6400 Guidelines for Maximizing the Number of Virtual Connections Specifying the Minimum ITT Block Size If you know the maximum VCI that will be used for a particular ATM port and VPI combination, you can use the highest VCI to determine the minimum ITT block size for that ATM port and VPI combination. Specifying the minimum block size reduces fragmentation by avoiding block expansion as virtual connections are created.
AppendixC Optimizing the Number of Virtual Connections on the Cisco 6400 Guidelines for Maximizing the Number of Virtual Connections Using Automatic Determination of the Minimum ITT Block Size The NSP can automatically track the size of the required ITT block as virtual connections are created and deleted. The required block size is stored in the running configuration and is used to optimally allocate ITT resources after an interface flap.
AppendixC Optimizing the Number of Virtual Connections on the Cisco 6400 Guidelines for Maximizing the Number of Virtual Connections Shrinking ITT Blocks Once an ITT block expands, it does not automatically shrink if the block becomes larger than necessary for the ATM port and VPI combination. The unused portion of the block, especially when adjacent to an unused fragment of ITT memory, can instead be used to create another ITT block. Note This functionality is available in Cisco IOS Release 12.
AppendixC Optimizing the Number of Virtual Connections on the Cisco 6400 Guidelines for Maximizing the Number of Virtual Connections Note This functionality is available in Cisco IOS Release 12.1(4)DB and later releases.
AppendixC Optimizing the Number of Virtual Connections on the Cisco 6400 Guidelines for Maximizing the Number of Virtual Connections 53248 40960 57344 4096 8192 8192 1 1 1 Input Translation Table Total Free = 64350 Input Translation Table In Use (display combines contiguous blocks): Inuse-start Inuse-end Size 0 0 1 16384 17407 1024 17472 17535 64 32768 32768 1 49216 49247 32 49280 49343 64 Cisco 6400 Software Setup Guide C-8 OL-1183-04
GLOSSARY A AAA authentication, authorization, and accounting (pronounced "triple a"). AAL ATM adaptation layer. Service-dependent sublayer of the data link layer. The AAL accepts data from different applications and presents it to the ATM layer in the form of 48-byte ATM payload segments. AALs consist of two sublayers, CS and SAR.
Glossary APS automatic protection switching. SONET switching mechanism that routes traffic from working lines to protect them in case of a line card failure or fiber cut. ATM Asynchronous Transfer Mode. International standard for cell relay in which multiple service types (such as voice, video, or data) are conveyed in fixed-length (53-byte) cells. Fixed-length cells allow cell processing to occur in hardware, thereby reducing transit delays.
Glossary C CBOS Cisco Broadband Operating System. The common operating system for DSL CPE, including the Cisco 675, the Cisco 675e, the Cisco 676, and the Cisco 677. 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. CEF Cisco Express Forwarding.
Glossary D DCC Data Country Code. One of two ATM address formats developed by the ATM Forum for use by private networks. Adapted from the subnetwork model of addressing in which the ATM layer is responsible for mapping network layer addresses to ATM addresses. Compare with ICD. DHCP Dynamic Host Configuration Protocol. Provides a mechanism for allocating IP addresses dynamically so that addresses can be reused when hosts no longer need them. DMA direct memory access.
Glossary Ethernet ETSI EXEC Baseband LAN specification originated by Xerox Corporation and developed jointly by Xerox, Intel, and Digital Equipment Corporation. Ethernet networks use CSMA/CD and run over a variety of cable types at 10 Mbps. Ethernet is similar to the IEEE 802.3 series of standards. See also 10BaseT and Fast Ethernet. European Telecommunications Standards Institute. Interactive command processor of Cisco IOS. F Fast Ethernet Any of a number of 100-Mbps Ethernet specifications.
Glossary I ICD International Code Designator. One of two ATM address formats developed by the ATM Forum for use by private networks. Adapted from the subnetwork model of addressing in which the ATM layer is responsible for mapping network layer addresses to ATM addresses. Compare with DCC. ICMP Internet Control Message Protocol. Network layer Internet protocol that reports errors and provides other information relevant to IP packet processing. Documented in RFC 792. IDI initial domain identifier.
Glossary K kbps kilobits per second. L L2F Layer 2 Forwarding. Protocol that supports the creation of secure virtual private dial-up networks over the Internet. L2TP Layer 2 Tunneling Protocol. An Internet Engineering Task Force (IETF) standards track protocol defined in RFC 2661 that provides tunneling of PPP. Based upon the best features of L2F and PPTP, L2TP provides an industry-wide interoperable method of implementing VPDN. LAC L2TP access concentrator.
Glossary M M23 A method of multiplexing four DS1 signals into a DS2 signal, then multiplexing seven DS2 signals into a DS3 signal. MAC Media Access Control. Lower of the two sublayers of the data link layer defined by the IEEE. The MAC sublayer handles access to shared media. Mbps megabits per second. MBS maximum burst size. In an ATM signaling message, burst tolerance is conveyed through the MBS, which is coded as a number of cells.
Glossary NMS network management system. System responsible for managing at least part of a network. An NMS is generally a reasonably powerful and well-equipped computer such as an engineering workstation. NMSs communicate with agents to help keep track of network statistics and resources. NNI Network-to-Network Interface. ATM Forum standard that defines the interface between two ATM switches that are both located in a private network or are both located in a public network.
Glossary 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. PEM power entry module. The PEM converts the -48 VDC power voltage into the voltages used internally by the Cisco 6400. The Cisco 6400 is designed to operate on one or two PEM units. ping packet internet groper. ICMP echo message and its reply.
Glossary PTA PPP Termination Aggregation. PVC permanent virtual circuit or connection. Virtual circuit that is permanently established. PVCs save bandwidth associated with circuit establishment and tear down in situations where certain virtual circuits must exist all the time. In ATM terminology, called a permanent virtual connection. Compare with SVC. See also virtual circuit (VC). PVP permanent virtual path. Virtual path that consists of PVCs. See also PVC and virtual path.
Glossary S SAR segmentation and reassembly. SCM Service Connection Manager. SCR sustainable cell rate. 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. SDH Synchronous Digital Hierarchy. European standard that defines a set of rate and format standards that are transmitted using optical signals over fiber. SDH is similar to SONET, with a basic SDH rate of 155.
Glossary STS-3c Synchronous Transport Signal level 3, concatenated. SONET format that specifies the frame structure for the 155.52-Mbps lines used to carry ATM cells. See also SONET. subnet mask 32-bit address mask used in IP to indicate the bits of an IP address that are being used for the subnet address. SVC switched virtual circuit. Virtual circuit that is dynamically established on demand and is torn down when transmission is complete.
Glossary U UAC universal access concentrator. 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. UDP User Datagram Protocol. Connectionless transport layer protocol in the TCP/IP protocol stack.
Glossary virtual circuit Logical circuit created to ensure reliable communication between two network devices. A virtual circuit is defined by a VPI/VCI pair, and can be either permanent (PVC) or switched (SVC). Virtual circuits are used in Frame Relay and X.25. In ATM, a virtual circuit is called a virtual channel. Sometimes abbreviated VC. virtual path Logical grouping of virtual circuits that connect two sites. See also virtual circuit.
Glossary Cisco 6400 Software Setup Guide GL-16 OL-1183-04
INDEX static route A 2-18 2-5 atm address command alarms clearing 4-7 atm iisp command 6-6 atm ilmi-pvc-discovery command 6-5 displaying status atm input-xlate-table autominblock command 6-5 displaying thresholds atm input-xlate-table autoshrink command 6-4 overview atm input-xlate-table minblock command 6-4 temperature APS atm maxvci-bits command 4-4, 4-5, 4-7 atm maxvpi-bits command 4-4, 4-5, 4-7 disabling 5-19 atm nni command 4-5 enabling 5-19 atm pvc command 2-11 atm pvp com
Index See DNS C caution, entering atm vc tx command 3-5 5-5 cd nvram: command 1-5 Cisco 6400 SCM enable password command class-int command 3-25, 3-27 class-vc command 3-25 enable secret command encapsulation command 6-6 clear facility-alarm command erase nvram: command 6-6 clearing alarms clear line command E 3-3 3-3 3-21, 3-23, 3-25, 3-26 5-5, 5-16 erase nvram:startup-config command 2-22, 3-16 erase sec-nvram: command 3-2 5-5, 5-16 clocking See network clocking clock set command F
Index interface BV11 command 2-7 mtu command 3-12 interface BVI1 command 2-8 MTU limitation on NRP-2 (ATM) 3-11to 3-13 Interim Interswitch Signalling Protocol See IISP N 3-6 IOMEM command ip address command network clocking 2-9 NRP, NME consolidation BITS 3-4 NRP-1 static IP address 2-7 NSP static IP address 2-9 separate NME interface NRP-1, NME consolidation 2-8 2-3, 3-2, 5-14 revertive 2-16 2-15 2-15 network-clock-select command 3-4 BITS 2-17 2-15, 2-17 priority upgraded NS
Index 4-8 framing 4-8 scrambling requirements redundancy 5-2 reversing primary and secondary 5-17 and APS 5-17 NRP-1, nonredundant half-height, configuring 5-18 NRP-1, redundant 5-23 reversing primary and secondary supported types (table) B-8 B-4 1-5 recommendations B-1 Web Console status, displaying 2-7to 2-9, 2-10 A-19 See also NRP-1 and NRP-2 2-9to 2-10 NRP-1 A-14 Web Console, using NNI B-2 NRP-2, nonredundant NME consolidation configuration methods 3-1 4-5to 4-6 DHCP no at
Index NRP-1, transferring configuration from 3-20 hardware backup 1-4 NRP-2SV, differences (footnote) overview 6-1 proxy forwarder, using NSP startup configuration B-4 reversing primary and secondary 3-15 software error protection 3-15 software release, checking 3-16to 3-19 troubleshooting 5-23 5-13 5-4 synchronizing 3-10 Telnet access 5-5to 5-12 5-2 requirements software upgrade, nonredundant system logging 5-3 PCMCIA disk mirroring 3-8 restrictions 5-14 netbooting 3-15 NV
Index R S redundancy scrambling NLC DS3 5-17 and APS OC-12 full-height, configuring 5-17 half-height, configuring 5-18 OC-3 4-10 4-8 4-8 scrambling command See also APS 4-9, 4-10 show aps command NRP 5-21 verifying APS priority requests 5-15 configuring 5-18 verifying NLC redundancy 5-16 erasing startup configurations NSP verifying SONET APS 5-20 2-5 show atm addresses command erasing startup configuration 5-5 5-12 hardware backup show atm input-xlate-table inuse command 5-1
Index show facility-alarm status command 6-5, 6-6 T show file systems command 3-6 NRP-1 NSP tar -xvf c6400s-html.
Index A-3 PCMCIA disk, from A-3 TFTP server, from A-24 loading new pages A-9 navigating A-14 NME A-19 NRP status, displaying A-24 pages, loading new redundancy running A-13 A-4 saving startup configuration A-6 SNMP community strings system options trap managers static routes A-17 A-18 A-15 status, displaying A-22 A-22 subscribers VCs A-18 A-22 who command 2-22, 3-16 Cisco 6400 Software Setup Guide IN-8 OL-1183-04
