|
|
This chapter describes how to perform basic configuration for the Cisco 6400 node switch processor (NSP). The Cisco 6400 can contain two NSPs configured for redundancy. This chapter contains the following sections:
The following methods are available for configuring the NSP:
 |
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. |
For general information on basic Cisco IOS configuration, see the Cisco IOS Configuration Fundamentals Configuration Guide associated with your software release level.
To check the software release version, connect a console terminal or a terminal server to the NSP console port on the NSP faceplate. After you boot the NSP, the following information is displayed to verify that the NSP has booted successfully.
Take note of the software release version included in the display. For information on upgrading to a higher release version, see "Upgrading Software on the Cisco 6400."
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. To configure the DHCP server, add an entry in the DHCP database using the instructions that came with the server.
|
Note The Cisco 6400 performs a DHCP request only if the NME interface is configured with the ip address negotiated interface configuration command. |
Use the show dhcp lease command to confirm the IP address, subnet mask, default gateway, and static route information obtained from a DHCP server:
Although they are not required, several system parameters should be set as part of the initial system configuration. To set the system clock and hostname, complete the following steps beginning in privileged EXEC mode:
| Command | Purpose | |
|---|---|---|
| Step 1 | ||
| Step 2 | ||
| Step 3 |
In the following example, the system clock and hostname are configured:
To confirm the system clock setting, use the show clock command:
To confirm the hostname, check the CLI prompt. The new hostname will appear in the prompt.
The Cisco 6400 NSP ships with the ATM address autoconfigured, which enables the switch to automatically configure attached end systems using the Integrated Local Management Interface (ILMI) protocol. Autoconfiguration also enables the NSP to establish itself as a node in a single-level Private Network-Network Interface (PNNI) routing domain.
To manually configure the ATM address, see the "Configuring the ATM Address Manually" section.
|
Note If you chose to manually change any ATM address, it is important to maintain the uniqueness of the address across large networks. Refer to the "Configuring ATM Routing and PNNI" chapter in the ATM Switch Router Software Configuration Guide for PNNI address considerations and for information on obtaining registered ATM addresses. |
During the initial startup, the NSP generates an ATM address using the defaults shown in Figure 2-1.
The autoconfigured ATM address includes the following components:
|
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 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. |
Manually configuring the ATM address is required:
To configure a new ATM address, refer to the chapter "Configuring ATM and PNNI" in the ATM Switch Router Software Configuration Guide.
 |
Caution ATM addressing can lead to conflicts if not configured correctly. If you are configuring a new ATM address, the old one must be completely removed from the configuration. |
The following example shows how to change the active ATM address, create a new address, verify that it exists, and then delete the current active address. Using the ellipses (...) adds the default Media Access Control (MAC) address as the last six bytes.
Use the show atm addresses EXEC command to confirm correct configuration of the ATM address for the NSP.
As of Cisco IOS Release 12.0(5)DB and later releases, including 12.3, the Cisco 6400 system can use the Ethernet port on the NSP as a combined network management Ethernet (NME) interface for all cards in the Cisco 6400 chassis. This is called "NME consolidation." Before Cisco IOS Release 12.0(5)DB, each NRP and NSP used a separate NME interface.
The Cisco IOS software version on your NSP determines the type of NME interface supported by your Cisco 6400 system:
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.
On an NSP that is preloaded with a Cisco IOS Release 12.0(5)DB or later software image, NME consolidation is already included in the default configuration.
If your NSP does not use a DHCP server to obtain an IP address, you must configure a static IP address. Complete the following steps beginning in global configuration mode:
| Command | Purpose | |
|---|---|---|
| Step 1 | ||
| Step 2 |
To enable NME consolidation on an NSP upgraded from a Cisco IOS Release 12.0(4)DB or earlier software image, complete the following tasks:
To remove the IP addresses from the Ethernet 0/0/0 and Ethernet 0/0/1 interfaces, complete the following steps beginning in global configuration mode:
| Command | Purpose | |
|---|---|---|
| Step 1 | ||
| Step 2 | ||
| Step 3 | ||
| Step 4 | ||
| Step 5 |
To set up the bridge group, complete the following steps beginning in global configuration mode:
| Command | Purpose | |
|---|---|---|
| Step 1 | ||
| Step 2 | Selects the IEEE Ethernet Spanning-Tree Protocol for bridge group 1. |
|
| Step 3 | ||
| Step 4 | ||
| Step 5 |
To configure the NME interface, complete the following steps beginning in global configuration mode:
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 | |
|---|---|---|
| Step 1 | ||
| Step 2 | ||
| Step 3 | ||
| Step 4 | Configures a static IP address and subnetwork address. Use the same subnet from the Ethernet 0/0/1 interface on the NSP. |
Cisco IOS Release 12.0(4)DB and earlier images do not support NME consolidation. You must configure the NSP Ethernet interface as a separate NME interface that is unable to handle network management of the NRPs in the Cisco 6400 system.
Complete the following steps beginning in global configuration mode:
| Command | Purpose | |
|---|---|---|
| Step 1 | ||
| Step 2 | Configures a static IP address and subnetwork address. Enables the interface to obtain an IP address, subnet mask, router address, and static routes from a DHCP server. |
In the following example, the NSP is configured to use the separate NME interface:
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. Check that the output shows:
The following sections describe minimal procedures for creating virtual circuits (VCs) and virtual paths (VPs).
|
Note Soft VCs between the NRP and NSP are not supported. |
For more information, see the following chapters of the ATM Switch Router Software Configuration Guide:
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.
The Cisco 6400 uses PVCs to pass traffic between the node line card (NLC) ATM interfaces and node route processors (NRPs). Typically, when VC switching is used, each subscriber is bound to a specific NRP and should be configured as a separate PVC. If the Cisco 6400 is used as an ATM switch, VCs are simply connected between the ATM interfaces.
To create a PVC between an ATM interface and an NRP, complete the following steps beginning in global configuration mode:
| Command | Purpose | |
|---|---|---|
| Step 1 | ||
| Step 2 | Configures the PVC, using the slot/subslot/port of the NRP to which you want to connect the NLC. |
You must also configure the PVC on the NRP side. For instructions on configuring PVCs on the NRP, see the "Permanent Virtual Circuits" section.
In the following example, an internal PVC is configured between the NLC ATM interface 1/0/0 and an NRP in slot 5. Both the NRP and NSP must be configured to create the PVC.
Configuration fragment on the NSP:
Configuration fragment on the NRP:
A permanent virtual path (PVP) allows you to connect two ATM switch routers at different locations across a public ATM network that does not support ATM signaling. Signaling traffic is mapped into the PVP, and the switches allocate a virtual channel connection (VCC) on that VP, instead of the default VP 0. This mapping allows the signaling traffic to pass transparently through the public network. VP switching also provides NSP redundancy at the ATM layer.
To create a PVP between an ATM interface and an NRP, complete the following steps beginning in global configuration mode:
| Command | Purpose | |
|---|---|---|
| Step 1 | ||
| Step 2 | Configures the PVP, using the slot/subslot/port of the NRP to which you want to connect the NLC. |
You must also configure PVCs on the NRP that will use the VP switch. For instructions on configuring PVCs on the NRP, see the "Permanent Virtual Circuits" section.
In the following example, an internal PVP is configured between the NLC ATM interface at 1/0/0 and an NRP in slot 5. Both the NRP and NSP must be configured to create the PVP.
Configuration fragment on the NSP:
Configuration fragment on the NRP:
Use the show atm vc EXEC command to confirm the status of ATM virtual channels:
Use the show atm vc interface atm EXEC command to confirm the status of ATM virtual channels on a specific interface:
Use the show atm vc interface atm EXEC command to confirm the status of a specific ATM interface and virtual channel:
This section describes the network clocking configuration of the Cisco 6400. Each port has a transmit clock that is derived from the receive data. The transmit clock can be configured for each port in one of the following ways:
Any NLC in a Cisco 6400 chassis capable of receiving and distributing a network timing signal can propagate that signal to any similarly capable module in the chassis. Using the network-clock-select global configuration command, you can cause a particular port in a Cisco 6400 chassis to serve as the primary reference source (PRS) for the entire chassis or for other devices in the networking environment. In other words, you can designate a particular port in a Cisco 6400 chassis to serve as a "master clock" source for distributing a single clocking signal throughout the chassis or to other network devices. This reference signal can be distributed wherever needed in the network and can globally synchronize the flow of constant bit rate (CBR) data.
For more information on network clocking, see the chapter "Initially Configuring the ATM Switch" in the ATM Switch Router Software Configuration Guide.
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 | |
|---|---|---|
| Step 1 | ||
| Step 2 |
In the following example, ATM interface 4/0/0 is configured to derive its transmit clock from the clock source received on the same interface:
You can configure multiple network clock sources and assign priority values to each source. The system uses the highest priority clock source available as the "network-derived" clock source for the transmit clock.
To configure the network clock priorities and sources, use the following command in global configuration mode:
| Command | Purpose |
|---|---|
Configures a network clock priority and source. Priority1 values range from 1 (highest) to 4 (lowest). System selects the local oscillator on the NSP. |
| 1Priorities 1 to 4 initially default to "no clock." Priority 5 is a pseudo-priority that defaults to "system clock" and is not configurable. If priorities 1 to 4 are not configured, the priority 5 system (NSP) clock is used as the derived clock. |
In the following example, interface ATM 2/0/0 is configured as the highest priority network clock source:
As long as interface ATM 2/0/0 is available, all transmit clocking on ATM 1/0/0 will be derived from ATM 2/0/0. If the ATM 2/0/0 clock source fails, the system will attempt to use the next highest priority clock source, which in this case is ATM 2/0/1.
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.
To enable network clock revertive behavior on the NSP, use the following command in global configuration mode:
| Command | Purpose |
|---|---|
In the following example, the network clock reverts to the highest priority clock source after a failure:
BITS network clocking enables the Cisco 6400 to derive network timing from the central office (CO) BITS as well as from a clock recovered from a specified NLC interface. The Cisco 6400 can also distribute the BITS network timing with stratum level 3 accuracy to other network devices.
The BITS Network Clocking feature requires the NSP with stratum 3/BITS (NSP-S3B) module. Figure 2-2 shows the NSP-S3B module faceplate.
In addition to enabling the BITS Network Clocking feature, the NSP-S3B allows the Cisco 6400 to serve as a stratum 3 network clock source for other network devices. When no external clock source is available, the NSP-S3B provides stratum level 3 internal timing on the Cisco 6400. Otherwise, the NSP-S3B is identical to the default NSP.
For information about installing the NSP-S3B, see the Cisco 6400 UAC Hardware Installation and Maintenance Guide . To see if the NSP-S3B is installed in the Cisco 6400 chassis, use the show hardware EXEC command. The output will contain an "NSP-NC" controller type (Ctrlr-Type) for each NSP-S3B in the chassis.
|
Note To derive network clocking from the CO BITS, the BITS input must be less than 9.2 parts per million (ppm) off center. Otherwise, the NSP-S3B declares the clock source invalid. |
To derive network clocking from the BITS signal, use the following commands on the NSP-S3B in global configuration mode:
| Command | Purpose | |
|---|---|---|
| Step 1 | ||
| Step 2 |
In the following example, the CO BITS is selected as the priority 1 network clock source. Lower priority clock sources are also configured for redundancy, and revertive behavior is selected.
To verify the switch network clocking configuration, use the show network-clocks EXEC command:
To verify BITS network clocking, make sure the show network-clocks command output includes the following lines:
The default software image for the Cisco 6400 contains the PNNI routing protocol. The PNNI protocol provides the route dissemination mechanism for complete plug-and-play capability. The following section, "Configuring ATM Static Routes for IISP or PNNI," describes modifications that can be made to the default PNNI or IISP routing configurations.
For more routing protocol configuration information, see the chapters "Configuring ILMI" and "Configuring ATM Routing and PNNI" in the ATM Switch Router Software Configuration Guide.
Static route configuration allows ATM call setup requests to be forwarded on a specific interface if the addresses match a configured address prefix. To configure a static route, use the following command in global configuration mode:
| Command | Purpose |
|---|---|
|
Note An interface must be UNI or IISP to be configured with a static route. Static routes configured as PNNI interfaces default to down state. |
In the following example, the atm route command is used to configure the 13-byte peer group prefix 47.0091.8100.567.0000.0ca7.ce01 at interface 3/0/0:
To verify successful configuration of an ATM static route, use the show atm route and show atm pnni topology EXEC commands.
The NSP provides the following functions for the NRP-2 and NRP-2SV:
|
Note Unless a clear distinction is made, all references to the NRP-2 also apply to the NRP-2SV. |
The NRP-2 has no local image or file storage. The NSP stores the following NRP-2 files on the Personal Computer Memory Card International Association (PCMCIA) disk:
Whenever the NSP reloads, a PCMCIA disk is inserted, or the PCMCIA disk is formatted, the NSP checks for the following directories on the PCMCIA disk and automatically creates those that are missing:
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.
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.
You can also assign priority values to each NRP-2 image and path. This allows you to enter multiple hw-module (image) commands in any order, while still having control over how they are executed.
For each NRP-2 in your Cisco 6400 system, enter the following command on the NSP in global configuration mode:
| Command | Purpose |
|---|---|
Assigns an image filename and path to the specified NRP-2 processor in the selected slot. Priority range is from 1 (highest) to 4 (lowest). |
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 If you do not use all the priority values for NRP-2 images, leave priority 1 free for new or temporary images. Otherwise, you will have to adjust the priority levels of the other images for your NRP-2 to accommodate the new 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:
In the first and last entries of the example, the system tries to find the images (with no specified path) in the disk0:/images/ directory.
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 |
|---|---|
Changes the configuration register setting of the NRP-2 in the specified slot. |
| 1For specific configuration register values, see "hw-module" in the Cisco 6400 Command Reference. |
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.
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. If console logging is enabled, each system log message also appears on the NRP-2 console.
For more information on NRP-2 console and system logging, see the "Using NRP-2 Console and System Logging" section.
To disable the appearance of NRP-2 system log messages on the NSP, use the following EXEC command:
| Command | Purpose |
|---|---|
The NSP has been equipped with an internal communication server to access the NRP-2 console lines. The NSP also has alias commands for using Telnet to connect to the NRP-2. For more information, see the "Methods Available for Configuring the NRP-2" section.
The NSP and NRP-2 support SNMPv1, SNMPv2c, and SNMPv3. The NSP can use the SNMPv3 Proxy Forwarder feature to:
For general information on using SNMP, see the "Configuring Simple Network Management Protocol (SNMP)" section in the "System Management" part of the Cisco IOS Configuration Fundamentals Configuration Guide. For information on the Proxy Forwarder feature, see the "Using the NSP as the SNMPv3 Proxy Forwarder for the NRP-2" section.
Use the following NSP commands to troubleshoot or monitor the NRP-2:
More troubleshooting and monitoring commands can be entered on the NRP-2. See the "Troubleshooting and Monitoring the NRP-2" section.
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:
In the following example, the show line EXEC command is entered on the NSP to look at the console connection to the NRP-2:
When autoconfiguration and any manual configurations are complete, you should copy the configuration into nonvolatile random-access memory (NVRAM). If you reload the NSP before you save the configuration in NVRAM, you will lose all manual configuration changes.
To save your running configuration as the startup configuration in NVRAM, use the copy system:running-config EXEC command:
To view the running configuration, use the more system:running-config EXEC command.
To view the startup configuration in NVRAM, use the more nvram:startup-config EXEC command.
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). Use the show file systems privileged EXEC command to display the valid file systems on your NSP:
Use the dir privileged EXEC command to show the contents of a file system. Remember to include the trailing colon in the name of the file system:
If your Cisco 6400 system contains an additional (secondary) NSP, use the dir command with file systems that begin with sec- to show file systems on the secondary NSP. For example, dir sec-nvram: will show the contents of the NVRAM on the secondary NSP.
|
Caution Do not use slot0: and slot1: to refer to the NSP PCMCIA disks. Use disk0: and disk1: instead. |
In Cisco IOS Release 12.1(5)DB, the PCMCIA Disk Mirroring feature introduced the mir-disk0: and mir-disk1: labels. These labels enable you to perform any integrated file system (IFS) operation (such as copy, rename, and delete) on the same file on both the primary and secondary PCMCIA disks. For more information, see the "Performing Mirrored IFS Operations" section.
Posted: Mon Jun 23 14:11:13 PDT 2003
All contents are Copyright © 1992--2003 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.
