Configuring the Node Switch Processor

This chapter tells how you initially configure the Cisco 6400 node switch processor (NSP) using the command-line interface (CLI). The system defaults to a working configuration suitable for most networks. However, you might need to customize the configuration for your network.

You can configure and customize all aspects of the operation of the Cisco 6400, using network management applications, the Web Console, and the text-based CLI.

You must assign an IP address to allow up to 32 simultaneous Telnet sessions to connect to the system or to use the Simple Network Management Protocol (SNMP). The IP address is assigned to the Ethernet interface, either manually, by a Bootstrap Protocol (BOOTP) server, or through Dynamic Host Configuration Protocol (DHCP). See the "Configuring Network Management IP Parameters" subsection.

Note For a description of the commands mentioned in this chapter, refer to the ATM Switch Router Command Reference and the Cisco IOS Release 12.0 Command Reference documents.

The following sections describe the NSP initial configuration:

4.1 Methods Available for Configuring the NSP

Three methods are available for configuring the NSP using the CLI:

From a local console or workstation---Connect to the console port or connect to the Ethernet port of an NSP. This connection allows you to enter CLI commands directly to the Cisco 6400 chassis.
From the Web Console application---see "Using the Web Console."
From a remote console or workstation---Initiate a Telnet connection to a target NSP. The Cisco 6400 NSP has two types of terminal lines: a console line and an auxiliary line. For a complete description of configuration tasks and commands used to set up your lines, modems, and terminal settings, refer to the Cisco IOS Configuration Fundamentals Configuration Guide and Cisco IOS Dial Solutions Configuration Guide.

Note If your Telnet station or 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 a description of static routing table configuration tasks, refer to "Configuring ATM Routing and PNNI" in the ATM Switch Router Configuration Guide.

4.1.1 Configuration Prerequisites

You might need the following information before you configure the NSP:

If you want to configure a BOOTP or DHCP server to inform the NSP of its IP address and mask, you need the Media Access Control (MAC) address of the Ethernet port.

: Optionally, you may also need a default gateway address and/or static routes.

If you want to configure a new Asynchronous Transfer Mode (ATM) address for the NSP (an autoconfigured ATM address is assigned by Cisco), you need an ATM address assigned by your system administrator.
If you are not using BOOTP or DHCP, you need an IP address, a netmask, and a default for DHCP.

4.1.2 Verifying Installed Software and Hardware

When you first power up your console and Cisco 6400 system, a screen similar to the following appears:

Restricted Rights Legend
 
Use, duplication, or disclosure by the Government is
subject to restrictions as set forth in subparagraph
(c) of the Commercial Computer Software - Restricted
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) C6400 Software (C6400S-WP-M), Version 12.0(5)DB
Copyright (c) 1986-1999 by cisco Systems, Inc.
Compiled Tue 18-May-99 15:00 by jdoe
Image text-base: 0x60010908, data-base: 0x6069A000
 
 
FPGA VERSION: 97/11/25 22:11:51 1383107375 /rhino/fpga/fc_abr_fc3/xil/abr_fpga_r.bit
98/02/24 17:11:36 1332837880 /rhino/fpga/fc_stat_fpga/xilinx/stat_fpga_r.bit
97/11/13 10:03:51 1059421866 /rhino/fpga/fc_traffic_fc3/xil/upc_fpga.bit
97/08/06 13:09:19  288278431 /rhino/fpga/fc_netclk/xilinx/pll_cntl_r.bit
 
Initializing FC-PFQ hardware ... done.
cisco C6400S (R4600) processor with 131072K bytes of memory.
R4700 CPU at 100Mhz, Implementation 33, Rev 1.0
Last reset from s/w peripheral
2 Ethernet/IEEE 802.3 interface(s)
11 ATM network interface(s)
507K bytes of non-volatile configuration memory.
 
107520K bytes of ATA PCMCIA card at slot 0 (Sector size 512 bytes).
8192K bytes of Flash internal SIMM (Sector size 256K).
 
 
Press RETURN to get started!
 
Switch>

The first section of the script displays the banner information, including the software version (indicated with the arrow). The next portion of the script lists the installed hardware configuration.

Note If the Cisco 6400 displays a ROMMON prompt (rommon>), your system requires a manual boot to recover. See the Cisco IOS 12.0 Configuration documentation for more information about manual booting.

4.2 Configuring the DHCP or BOOTP Server

Note The Cisco 6400 performs a BOOTP or DHCP request only if the current IP address is set to 0.0.0.0.

DHCP

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 DHCP, add an entry in the DHCP database using the instructions that came with your DHCP server.

BOOTP

The BOOTP protocol automatically assigns an Ethernet IP address by adding the MAC and IP addresses of the Ethernet port to the BOOTP server configuration file. To allow your Cisco 6400 to retrieve its IP address from a BOOTP server, you must first determine the MAC address of the NSP and add that MAC address, IP address, and default mask to the BOOTP configuration file on the BOOTP server.

The following tasks are an example showing how to create a BOOTP server configuration file:

Install the BOOTP server code on the workstation, if it is not already installed.
Determine MAC address from label on chassis.
Add an entry in the BOOTP configuration file (usually /usr/etc/bootptab) for the NSP.
Use the restart command to restart the Cisco 6400 and automatically request the IP address from the BOOTP server.

4.3 Configuring the ATM Address

The Cisco 6400 NSP ships with the ATM address autoconfigured, which allows the switch to automatically configure attached end systems using the Integrated Local Management Interface (ILMI) protocol. Autoconfiguration also allows the NSP to establish itself as a node in a single-level Private Network-Network Interface (PNNI) routing domain.

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 chapter "Configuring ATM Routing and PNNI" in the ATM Switch Router Configuration Guide for PNNI address considerations and for information on obtaining registered ATM addresses.

4.3.1 Auto-configured ATM Addressing Scheme

During the initial startup, the Cisco 6400 generates an ATM address using the defaults shown in Figure 4-1.

Figure 4-1: ATM Address Format

Authority and format identifier (AFI)---1 byte
Cisco-specific International Code Designator (ICD)---2 bytes
Cisco-specific information---4 bytes
Cisco switch ID---6 bytes (used to distinguish multiple switches)

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.

MAC address of the NSP---6 bytes (used to distinguish multiple end system identifier [ESI] addresses)

Note Both MAC address fields in the ATM address are the same, but they might not be the same as the address printed on the chassis label.

Selector equals 0---1 byte

4.3.2 Manually Configuring the ATM Address

The following situations require manually configuring the ATM address:

To connect to another system using IISP. Using IISP means that PNNI must be disabled, so there is no ILMI support. In this case the ATM address must be manually configured.
To configure a new ATM address that replaces the previous ATM address and generates a new PNNI node ID and peer group ID for migrating from flat to hierarchical PNNI.
To connect to multiple levels of a PNNI hierarchy.
To connect to a service provider network that requires you to use the addressing scheme for that network.
To use a particular style of addressing. For instance, in some circumstances a mnemonic scheme might be useful for identifying nodes in an ATM network.

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. The correct address must always be present. If you are configuring a new ATM address, the old one must be completely removed from the configuration.

4.3.3 Configuring ATM Interfaces

When the Cisco 6400 is powered on initially without any previous configuration data, the ATM interfaces are automatically configured on the physical ports. ILMI and the physical card type are used to automatically derive the following:

ATM interface type
UNI version
Maximum virtual path identifier (VPI) and virtual channel identifier (VCI) bits
ATM interface side
ATM UNI type

You can accept the default ATM interface configuration, or overwrite the default interface configuration using the CLI. See "Configuring ATM Interfaces," for the interface default configuration and modification procedures.

4.4 Configuring Network Management IP Parameters

The Cisco 6400 uses the Ethernet port on the NSP as a network management Ethernet (NME) interface. Depending on the Cisco IOS software version on your NSP, perform one of the following tasks to enable the NME interface:

New NSP with Cisco IOS 12.0(5)DB or Newer

On an NSP that is pre-loaded with a 12.0(5)DB or newer software image, the combined NME interface is included in the default configuration.

If your NRP does not use a DHCP server to obtain an IP address, you must configure a static IP address. Perform the following task starting in global configuration mode:

Step Command Task

1 .

interface BVI1

Select the combined NME interface.

2 .

ip address address subnet

Configure the IP and subnetwork address.

Upgrading an NSP to Cisco IOS 12.0(5)DB or Newer

If you are upgrading the NSP from an older software version, you must first disable the standard Ethernet interface. This will allow the Cisco 6400 to use the combined NME interface to manage the system.

To disable IP on the standard Ethernet interface as a combined management interface, perform the following tasks starting in global configuration mode:

Step Command Task

1 .

interface ethernet 0/0/0

Select the ethernet interface.

2 .

no ip address

Disable IP on the ethernet interface.

Additionally, you must configure a static IP address if your NRP does not use a DHCP server. Perform the following task starting in global configuration mode:

Step Command Task

1 .

interface BVI1

Select the combined NME interface.

2 .

ip address address subnet

Configure the IP and subnetwork address.

Cisco IOS 12.0(4)DB or Older

If your NSP uses an older software, you must configure the Ethernet port as a separate management interface. Perform the following tasks starting in global configuration mode:

Step Command Task

1 .

interface ethernet 0/0/0

Select the NME interface to be configured.

2 . or

ip address address subnet

Configure a static IP address and subnetwork address.

3 .

ip address negotiated

Allow the interface to obtain an IP address, subnet mask, router address, and static routes from a DHCP server.

Example

The following example shows how to configure the Ethernet interface with IP address 172.20.40.93 and subnet mask 255.255.255.0:

Switch(config)# interface ethernet 0/0/0
Switch(config-if)# ip address 172.20.40.93 255.255.255.0

4.5 Configuring Internal Cross-Connections

The following sections describe minimal procedures for creating virtual circuits (VCs) and virtual paths (VPs). For more information, see the following sections of the ATM Switch Router Configuration Guide:

"Configuring Virtual Connections" (VCs)
"Configuring ATM Network Interfaces" (VPs, including shared and hierarchical VP tunnels)

4.5.1 Configuring PVCs

A 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 permanent virtual circuits (PVCs) to pass traffic between the node line card (NLC) ATM interfaces, and node route processors (NRPs). Typically, each subscriber is bound to a specific NRP and should be configured as a separate PVC.

To create a PVC between an ATM interface and an NRP, follow these steps starting in global configuration mode:

Step Command Task

1 .

interface atm slot/subslot/port

Select the NLC interface to be configured.

2 .

atm pvc vpi vci interface atm slot/subslot/port vpi vci

Configure the PVC, using the slot/subslot/port of the NRP you want to connect.

Examples

The following example shows how to configure an internal PVC between an ATM interface at 1/0/0 (VPI = 0, VCI = 50) and an NRP at 5/0/0 (VPI = 2, VCI = 100):

Switch(config)# interface atm 1/0/0
Switch(config-if)# atm pvc 0 50 interface atm 5/0/0 2 100
Switch(config-if-atm-vc)# ^Z

The PVC must now be configured on the NRP side as well. The following example shows how to configure a PVC on the NRP, completing the PVC configured in the previous example:

Router(config)# interface atm 0/0/0
Router(config-if)# pvc 2/100
Router(config-if-atm-vc)# ^Z

For more information about configuring PVCs on the NRP, refer to "Configuring the Node Route Processor."

4.5.2 Configuring PVPs

A permanent virtual path (PVP), or VP tunnel , 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.

To create a PVP between an ATM interface and an NRP, follow these steps starting in global configuration mode:

Step Command Task

1 .

interface atm slot/subslot/port

Select the NLC interface to be configured.

2 .

atm pvp vpi interface atm slot/subslot/port vpi

Configure the PVP, using the slot/subslot/port of the NRP you want to connect.

Examples

The following example shows how to configure a VP tunnel between an ATM interface at 1/0/0
(VPI = 0) and an NRP at 5/0/0 (VPI = 2):

Switch(config)# interface atm 1/0/0
Switch(config-if)# atm pvp 0 interface atm 5/0/0 2
Switch(config-if-atm-vc)# ^Z

You must also configure PVCs on the NRP that will use the VP tunnel.For more information about configuring PVCs on the NRP, refer to "Configuring the Node Route Processor."

4.6 Configuring Network Clocking

This section describes network clocking and network clocking configuration of the Cisco 6400. Each port has a transmit clock and derives its receive clock from the receive data. Transmit clocking can be configured for each port in one of the following ways:

Free-running---Transmit clocking is derived from the local oscillator on a line card or from the NSP.
Network derived---Transmit clocking is derived from the highest priority configured source, either from the system clock (the local oscillator on the NSP) or the public network.
Loop-timed---Transmit clock is derived from the receive clock source.

The network clocking configuration uses priorities 1 to 4, each of which initially defaults 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, priority 5 is used as the derived clock.

Network clocking configuration is described in the following sections:

For more information on network clocking, see the chapter "Initially Configuring the ATM Switch" in the ATM Switch Router Configuration Guide.

4.6.1 Configure Network Clock Priorities and Sources

To configure the network clocking priorities and sources, use the following commands in global configuration mode:

Command Task

network-clock-select priority {system¹ | atm slot/subslot/port } [revertive]

Configure the network clock.

¹Selects the NSP reference clock.

Command	Task
network-clock-select priority {system¹ \| atm slot/subslot/port } [revertive]	Configure the network clock.

Examples

In the following example, interface 2/0/0 is configured as the highest priority clock source to receive the network clocking:

Switch(config)# network-clock-select 1 atm 2/0/0
Switch(config)# network-clock-select 2 atm 2/0/1
Switch(config)# network-clock-select 3 atm 1/0/0

The following example shows how to configure the network clock to revert back to the highest priority clock source after a failure:

Switch(config)# network-clock-select revertive

4.6.2 Configure Transmit Clocking Source

To configure an interface to receive its transmit clocking, use the following commands starting in global configuration mode:

Step Command Task

1 .

interface atm slot/subslot/port

Select the interface to be configured.

2 .

clock source {free-running | loop-timed | network-derived}

Configure the interface network clock source.

Example

The following example shows how to configure ATM interface 4/0/0 to receive its transmit clocking from a network-derived source:

Switch(config)# interface atm 4/0/0
Switch(config-if)# clock source network-derived

4.6.3 Display Network Clocking Configuration

To show the switch network clocking configuration, use the following command:

Command Task

show network-clocks

Show the network clocking configuration.

Command	Task
show network-clocks	Show the network clocking configuration.

Examples

The following example shows how to display the switch clock source configuration:

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#

4.6.4 Network Timing Modules in a Cisco 6400 Chassis

Any node line card 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. By entering the network-clock-select command with appropriate parameters, you can cause a particular port in a Cisco 6400 chassis to serve as the source of a PRS for the entire chassis or for other devices in the networking environment. This command is described in the "Configure Network Clock Priorities and Sources" section.

In effect, through the network-clock-select command, 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 CBR data.

4.7 Configuring Network Routing

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. Section 4.7.1, "Configure ATM Static Routes for IISP or PNNI" describes modifications that can be made to the default PNNI or Interim-Interswitch Signaling Protocol (IISP) routing configurations.

For routing protocol configuration information, see the chapters "Configuring ILMI" and "Configuring ATM Routing and PNNI" in the ATM Switch Router Software Configuration Guide for detailed configuration information.

4.7.1 Configure ATM Static Routes for IISP or PNNI

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 Task

atm route addr-prefx atm slot/subslot/port

Specify a static route to a reachable address prefix.

Command	Task
atm route addr-prefx atm slot/subslot/port	Specify a static route to a reachable address prefix.

Note An interface must be UNI or IISP to be configured with static route. Static routes configured as PNNI interfaces default as down.

The following example shows how to use the atm route command to configure the 13-byte peer group prefix 47.0091.8100.567.0000.0ca7.ce01 at interface 3/0/0:

Switch(config)# atm route 47.0091.8100.567.0000.0ca7.ce01 atm 3/0/0
Switch(config)#

4.8 Configuring System Information

Although they are not required, several system parameters should be set as part of the initial system configuration. To set the system parameters, perform the following tasks in EXEC mode:

Step Command Task

1
clock set hh:mm:ss day_of_month month year

Set the system clock.

2
configure [terminal]

At the privileged EXEC prompt, enter configuration mode from the terminal.

3
hostname name_string

Set the system name.

Step	Command	Task
1	clock set hh:mm:ss day_of_month month year	Set the system clock.
2	configure [terminal]	At the privileged EXEC prompt, enter configuration mode from the terminal.
3	hostname name_string	Set the system name.

Examples

The following example shows how to configure the time, date, and month using the clock set command:

Switch# clock set 15:01:00 17 October 1997
Switch#

The following example shows how to configure the host name using the hostname command:

Switch# config term
Enter configuration commands, one per line.  End with CNTL/Z.
Switch(config)# hostname Publications
Publications#

The following example shows how to confirm the clock setting using the show clock command:

Publications# show clock
.15:03:12.015 UTC Fri Oct 17 1997
Publications#

4.9 Storing the Configuration

When autoconfiguration and any manual configurations are complete, you should copy the configuration into nonvolatile random-access memory (NVRAM). If you should power off your Cisco 6400 before you save the configuration in NVRAM, all manual configuration changes are lost. An example of the copy system:running-config command follows:

Switch# copy system:running-config nvram:startup-config
Building configuration...
[OK]
Switch#

4.9.1 Using the NSP File Systems and Memory Devices

File systems on the NSP include read-only memory (NVRAM, or system), Flash memory (such as Flash disks 0 and 1, and bootflash), 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. For example:

Switch# show file systems
File Systems:
 
     Size(b)     Free(b)      Type  Flags  Prefixes
           -           -     flash     rw   sec-slot0:
           -           -     flash     rw   sec-slot1:
           -           -     flash     rw   sec-disk0:
           -           -     flash     rw   sec-disk1:
           -           -     flash     rw   sec-bootflash:
           -           -     nvram     rw   sec-nvram:
   109760512   108228608     flash     rw   disk0:
           -           -     flash     rw   disk1:
*          -           -     flash     rw   slot0: flash:
           -           -     flash     rw   slot1:
     7602176     3873740     flash     rw   bootflash:
           -           -    opaque     rw   null:
           -           -    opaque     rw   system:
           -           -   network     rw   tftp:
      520184      518050     nvram     rw   nvram:
           -           -   network     rw   rcp:
           -           -   network     rw   ftp:
     5242880           0    opaque     ro   atm-acct-ready:
     5242880     5242880    opaque     ro   atm-acct-active:
 
Switch#

Use the dir command to show the contents of a file system. Remember to include the trailing colon in the name of the file system:

Switch# dir bootflash:
Directory of bootflash:/
 
  1  -rw-     3728308   Jan 01 2000 00:02:44  c6400s-wp-mz.120-5.DB
 
7602176 bytes total (3873740 bytes free)
Switch#

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 Flash disks on the NSP. Use disk0: and disk1: instead.

Switch# dir disk0:
Directory of disk0:/
 
  3  -rw-      628224   Jan 01 2000 00:08:55  c6400s-html.tar.120-4.DB
157  drw-           0   Jan 01 2000 00:11:01  nsp-html
376  -rw-        2134   Jan 05 2000 22:05:27  startup.config
 
109760512 bytes total (108228608 bytes free)
Switch# dir slot0:
%Error opening slot0:/ (Device not ready)
Switch#

4.10 Verifying the Configuration

When you have finished configuring the Cisco 6400 NSP, you can use the following tasks to confirm the hardware, software, and interface configuration:

4.10.1 Confirm the Hardware Configuration

Use the show hardware command to confirm the correct hardware configuration :

Switch# show hardware
 
6400 named orange, Date: 05:29:10 UTC Tue Apr 13 1999
Feature Card's FPGA Download Version: 0
 
Slot Ctrlr-Type    Part No.  Rev  Ser No  Mfg Date   RMA No. Hw Vrs  Tst EEP
---- ------------  ---------- -- -------- --------- -------- ------- --- ---
1/0  155SM NLC     73-2892-03 03 09702972 Aug 26 98 00-00-00   3.1     0  FF
5/0  NRP           73-3082-03 ?? 09701443 Jan 00 00 00-00-00   2.20   FF   0
6/0  622SM NLC     73-3868-02 02 10785155 Mar 23 99 00-00-00   2.0     0   2
7/0  155SM NLC     73-2892-01 05 07287379 May 20 98 00-00-00   3.1     0   2
8/0  155SM NLC     73-2892-01 05 07287394 May 26 98 00-00-00   3.1     0   2
7/1  155SM NLC     73-2892-03 03 09702916 Aug 15 98 00-00-00   3.1     0  FF
8/1  DS3 NLC       12-3456-78 00 10783359 Apr 01 98 00-00-00   1.0     0   2
0/0  NSP-PC        73-2996-01 00 07285884 Apr 28 98 00-00-00   1.0     0   2
0/1  FC-PFQ        73-2281-04 A0 07841515 Feb 13 98 00-00-00   4.1     0   2
 
DS1201 Backplane EEPROM:
 Model  Ver.  Serial  MAC-Address  MAC-Size  RMA  RMA-Number   MFG-Date
------- ---- -------- ------------ --------  ---  ----------  -----------
C6400    2   313177   00107B79A600   128     0    0           May 01 1998
 
Switch#

4.10.2 Confirm the Software Version

Use the show version command to confirm the correct version and type of software and the configuration register are installed:

Switch# show version
 
IOS (tm) C6400 Software (C6400S-WP-M), Version 12.0(5)DB
Copyright (c) 1986-1999 by cisco Systems, Inc.
Compiled Tue 18-May-99 15:00 by jdoe
Image text-base: 0x60010908, data-base: 0x6069A000
 
ROM: System Bootstrap, Version 11.3(19980609:232048) [gmgreen-ci2 133], DEVELOPE
ROM: C6400S WA4-5 Software (C6400S-WP-M), Experimental Version 12.0(19980722:21]
 
orange uptime is 2 days, 20 hours, 39 minutes
System restarted by reload
System image file is "tftp://172.28.254.254/c6400s-wp-mz.120-4.DB"
 
cisco C6400S (R4600) processor with 131072K bytes of memory.
R4700 CPU at 100Mhz, Implementation 33, Rev 1.0
Last reset from s/w peripheral
2 Ethernet/IEEE 802.3 interface(s)
11 ATM network interface(s)
507K bytes of non-volatile configuration memory.
 
107520K bytes of ATA PCMCIA card at slot 0 (Sector size 512 bytes).
8192K bytes of Flash internal SIMM (Sector size 256K).
Configuration register is 0x2
 
Switch#

4.10.3 Confirm the Network Management Ethernet Configuration

Use the show interface command to confirm the NME interface on the NSP is configured. If the NSP is configured to use the combined NME, use the command show interface BVI 1; on an NSP with older software, use the command show interface ethernet 0/0/0. For more information, see the "Configuring Network Management IP Parameters" section.

Switch# show interface BVI 1
BVI1 is up, line protocol is up
  Hardware is BVI, address is 0050.736f.5756 (bia 0000.0000.0000)
  Internet address is 172.194.71.11/24
  MTU 4470 bytes, BW 10000 Kbit, DLY 5000 usec,
     reliability 255/255, txload 1/255, rxload 1/255
  Encapsulation ARPA, loopback not set
  ARP type: ARPA, ARP Timeout 04:00:00
  Last input never, output never, output hang never
  Last clearing of "show interface" counters never
  Queueing strategy: fifo
  Output queue 0/0, 0 drops; input queue 0/75, 0 drops
  5 minute input rate 0 bits/sec, 0 packets/sec
  5 minute output rate 0 bits/sec, 0 packets/sec
     53 packets input, 3180 bytes, 0 no buffer
     Received 0 broadcasts, 0 runts, 0 giants, 0 throttles
     0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
     57 packets output, 0 bytes, 0 underruns
     0 output errors, 0 collisions, 0 interface resets
     0 output buffer failures, 0 output buffers swapped out
 
Switch#

4.10.4 Confirm the ATM Address

Use the show atm addresses command to confirm correct configuration of the ATM address for the Cisco 6400 :

Switch# show atm addresses
 
Switch Address(es):
  47.0091810000000003455B7000.0003455B7000.00 active
 
Soft VC Address(es):
  47.0091.8100.0000.0003.455b.7000.4000.0c80.8000.00 ATM1/0/0
  47.0091.8100.0000.0003.455b.7000.4000.0c80.8010.00 ATM1/0/1
  47.0091.8100.0000.0003.455b.7000.4000.0c82.8000.00 ATM5/0/0
  47.0091.8100.0000.0003.455b.7000.4000.0c83.0000.00 ATM6/0/0
  47.0091.8100.0000.0003.455b.7000.4000.0c83.8000.00 ATM7/0/0
  47.0091.8100.0000.0003.455b.7000.4000.0c83.8010.00 ATM7/0/1
  47.0091.8100.0000.0003.455b.7000.4000.0c83.9000.00 ATM7/1/0
  47.0091.8100.0000.0003.455b.7000.4000.0c83.9010.00 ATM7/1/1
  47.0091.8100.0000.0003.455b.7000.4000.0c84.1000.00 ATM8/1/0
  47.0091.8100.0000.0003.455b.7000.4000.0c84.1010.00 ATM8/1/1
 
ILMI Switch Prefix(es):
  47.0091.8100.0000.0003.455b.7000
 
ILMI Configured Interface Prefix(es):
 
LECS Address(es):

4.10.5 Test the Network Management Ethernet Connection

After you have configured the IP address(es) for the NME interface, test for connectivity between the NSP and a host. The host can reside anywhere in your network. To test for Ethernet connectivity, perform the following task:

Command Task

ping ip ip_address

Test the configuration using the ping command. The ping command sends an echo request to the host specified in the command line.

Command	Task
ping ip ip_address	Test the configuration using the ping command. The ping command sends an echo request to the host specified in the command line.

For example, to test Ethernet connectivity from the NSP to a workstation with an IP address of 172.20.40.201, enter the command ping ip 172.20.40.201. If the NSP receives a response, the following message displays:

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 172.20.40.201, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 1/202/1000 ms
Switch#

4.10.6 Confirm the ATM Connections

Use the ping atm command to confirm that the ATM interfaces are configured correctly. Here is an example of the use of this command :

Switch# ping atm interface atm 3/0/0 0 5 seg-loopback
 
Type escape sequence to abort.
Sending Seg-Loopback 5, 53-byte OAM Echoes to a neighbour,timeout is 5 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 1/1/4 ms
Switch#

4.10.7 Confirm the ATM Interface Configuration

Use the show atm interface command to confirm the atm interfaces are configured correctly. Here is an example of the use of this command:

Switch# show atm interface atm 7/0/0
 
Interface:      ATM7/0/0        Port-type:      oc3suni
IF Status:      UP              Admin Status:   up
Auto-config:    enabled         AutoCfgState:   completed
IF-Side:        Network         IF-type:        NNI
Uni-type:       not applicable  Uni-version:    not applicable
Max-VPI-bits:   8               Max-VCI-bits:   14
Max-VP:         255             Max-VC:         16383
ConfMaxSvpcVpi: 255             CurrMaxSvpcVpi: 255
ConfMaxSvccVpi: 255             CurrMaxSvccVpi: 255
ConfMinSvccVci: 35              CurrMinSvccVci: 35
Svc Upc Intent: pass            Signalling:     Enabled
ATM Address for Soft VC: 47.0091.8100.0000.0003.455b.7000.4000.0c83.8000.00
Configured virtual links:
  PVCLs SoftVCLs   SVCLs   TVCLs   PVPLs SoftVPLs   SVPLs Total-Cfgd Inst-Conns
      3        0       0       0       0        0       0          3          3
Logical ports(VP-tunnels):     0
Input cells:    108674          Output cells:   108608
5 minute input rate:             0 bits/sec,       0 cells/sec
5 minute output rate:            0 bits/sec,       0 cells/sec
Input AAL5 pkts: 70949, Output AAL5 pkts: 70927, AAL5 crc errors: 0

4.10.8 Confirm the ATM Interface Status

Use the show atm status command to confirm the status of ATM interfaces:

Switch# show atm status
NUMBER OF INSTALLED CONNECTIONS: (P2P=Point to Point, P2MP=Point to MultiPoint,)
 
Type     PVCs SoftPVCs     SVCs     TVCs     PVPs SoftPVPs     SVPs      Total
P2P         9        0        0        0        0        0        0          9
P2MP        0        0        0        0        0        0        0          0
MP2P        0        0        0        0        0        0        0          0
                                      TOTAL INSTALLED CONNECTIONS =          9
 
PER-INTERFACE STATUS SUMMARY AT 05:37:45 UTC Tue Apr 13 1999:
   Interface      IF         Admin  Auto-Cfg    ILMI Addr     SSCOP    Hello
     Name       Status      Status    Status    Reg State     State    State
------------- -------- ------------ -------- ------------ --------- --------
ATM0/0/0            UP           up      n/a  UpAndNormal      Idle      n/a
ATM1/0/0          DOWN         down  waiting          n/a      Idle      n/a
ATM1/0/1          DOWN         down  waiting          n/a      Idle      n/a
ATM5/0/0          DOWN         down  waiting          n/a      Idle      n/a
ATM6/0/0          DOWN         down  waiting          n/a      Idle      n/a
ATM7/0/0            UP           up     done  UpAndNormal    Active  LoopErr
ATM7/0/1          DOWN     shutdown  waiting          n/a      Idle      n/a
ATM7/1/0            UP           up     done  UpAndNormal    Active  LoopErr
ATM7/1/1          DOWN         down  waiting          n/a      Idle      n/a
ATM8/1/0            UP           up     done  UpAndNormal    Active  LoopErr
ATM8/1/1          DOWN         down  waiting          n/a      Idle      n/a
 
Switch#

4.10.9 Confirm Virtual Connections

Use the show atm vc command to confirm the status of ATM virtual channels:

Switch# show atm vc
Interface         VPI   VCI   Type    X-Interface       X-VPI X-VCI  Encap Status
ATM0/0/0           0     35     PVC     ATM1/0/0           0     16    ILMI   DN
ATM0/0/0           0     36     PVC     ATM1/0/0           0     5     QSAAL  DN
ATM0/0/0           0     37     PVC     ATM1/0/1           0     16    ILMI   DN
ATM0/0/0           0     38     PVC     ATM1/0/1           0     5     QSAAL  DN
ATM0/0/0           0     39     PVC     ATM5/0/0           0     16    ILMI   DN
ATM0/0/0           0     40     PVC     ATM5/0/0           0     5     QSAAL  DN
ATM0/0/0           0     41     PVC     ATM6/0/0           0     16    ILMI   DN
ATM0/0/0           0     42     PVC     ATM6/0/0           0     5     QSAAL  DN
ATM0/0/0           0     43     PVC     ATM7/1/0           0     16    ILMI   UP
ATM0/0/0           0     44     PVC     ATM7/1/0           0     5     QSAAL  UP
ATM0/0/0           0     45     PVC     ATM7/1/1           0     16    ILMI   DN
Interface         VPI   VCI   Type    X-Interface       X-VPI X-VCI  Encap Status
ATM0/0/0           0     46     PVC     ATM7/1/1           0     5     QSAAL  DN
ATM0/0/0           0     47     PVC     ATM8/1/0           0     16    ILMI   UP
ATM0/0/0           0     48     PVC     ATM8/1/0           0     5     QSAAL  UP
ATM0/0/0           0     49     PVC     ATM8/1/1           0     16    ILMI   DN
ATM0/0/0           0     50     PVC     ATM8/1/1           0     5     QSAAL  DN
ATM0/0/0           0     51     PVC     ATM7/0/0           0     16    ILMI   UP
ATM0/0/0           0     52     PVC     ATM7/0/0           0     5     QSAAL  UP
ATM0/0/0           0     53     PVC     ATM7/0/1           0     16    ILMI   DN
ATM0/0/0           0     54     PVC     ATM7/0/1           0     5     QSAAL  DN
ATM0/0/0           0     55     PVC     ATM7/1/0           0     18    PNNI   UP
ATM0/0/0           0     56     PVC     ATM8/1/0           0     18    PNNI   UP
ATM0/0/0           0     57     PVC     ATM7/0/0           0     18    PNNI   UP
ATM1/0/0           0     5      PVC     ATM0/0/0           0     36    QSAAL  DN
ATM1/0/0           0     16     PVC     ATM0/0/0           0     35    ILMI   DN
ATM1/0/1           0     5      PVC     ATM0/0/0           0     38    QSAAL  DN
Interface         VPI   VCI   Type    X-Interface       X-VPI X-VCI  Encap Status
ATM1/0/1           0     16     PVC     ATM0/0/0           0     37    ILMI   DN
ATM5/0/0           0     5      PVC     ATM0/0/0           0     40    QSAAL  DN
ATM5/0/0           0     16     PVC     ATM0/0/0           0     39    ILMI   DN
ATM6/0/0           0     5      PVC     ATM0/0/0           0     42    QSAAL  DN
ATM6/0/0           0     16     PVC     ATM0/0/0           0     41    ILMI   DN
ATM7/0/0           0     5      PVC     ATM0/0/0           0     52    QSAAL  UP
ATM7/0/0           0     16     PVC     ATM0/0/0           0     51    ILMI   UP
ATM7/0/0           0     18     PVC     ATM0/0/0           0     57    PNNI   UP
ATM7/0/1           0     5      PVC     ATM0/0/0           0     54    QSAAL  DN
ATM7/0/1           0     16     PVC     ATM0/0/0           0     53    ILMI   DN
ATM7/1/0           0     5      PVC     ATM0/0/0           0     44    QSAAL  UP
ATM7/1/0           0     16     PVC     ATM0/0/0           0     43    ILMI   UP
ATM7/1/0           0     18     PVC     ATM0/0/0           0     55    PNNI   UP
ATM7/1/1           0     5      PVC     ATM0/0/0           0     46    QSAAL  DN
Interface         VPI   VCI   Type    X-Interface       X-VPI X-VCI  Encap Status
ATM7/1/1           0     16     PVC     ATM0/0/0           0     45    ILMI   DN
ATM8/1/0           0     5      PVC     ATM0/0/0           0     48    QSAAL  UP
ATM8/1/0           0     16     PVC     ATM0/0/0           0     47    ILMI   UP
ATM8/1/0           0     18     PVC     ATM0/0/0           0     56    PNNI   UP
ATM8/1/1           0     5      PVC     ATM0/0/0           0     50    QSAAL  DN
ATM8/1/1           0     16     PVC     ATM0/0/0           0     49    ILMI   DN
 
Switch#

Use the show atm vc interface command to confirm the status of ATM virtual channels on a specific interface:

Switch# show atm vc interface atm 7/0/0
Interface         VPI   VCI   Type    X-Interface       X-VPI X-VCI  Encap Status
ATM7/0/0           0     5      PVC     ATM0/0/0           0     52    QSAAL  UP
ATM7/0/0           0     16     PVC     ATM0/0/0           0     51    ILMI   UP
ATM7/0/0           0     18     PVC     ATM0/0/0           0     57    PNNI   UP
Switch#

Use the show atm vc interface atm command to confirm the status of a specific ATM interface and virtual channel:

Switch# show atm vc interface atm 7/0/0 0 16
 
Interface: ATM7/0/0, Type: oc3suni
VPI = 0  VCI = 16
Status: UP
Time-since-last-status-change: 2d20h
Connection-type: PVC
Cast-type: point-to-point
Packet-discard-option: enabled
Usage-Parameter-Control (UPC): pass
Wrr weight: 15
Number of OAM-configured connections: 0
OAM-configuration: disabled
OAM-states:  Not-applicable
Cross-connect-interface: ATM0/0/0, Type: CPU card
Cross-connect-VPI = 0
Cross-connect-VCI = 51
Cross-connect-UPC: pass
Cross-connect OAM-configuration: disabled
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-traffic-table-index: 3
Tx service-category: VBR-RT (Realtime Variable Bit Rate)
Tx pcr-clp01: 424
Tx scr-clp01: 424
Tx mcr-clp01: none
Tx      cdvt: none
Tx       mbs: 50
AAL5 statistics:
Crc Errors:0, Sar Timeouts:0, OverSizedSDUs:0
BufSzOvfl:  Small:0, Medium:0, Big:0, VeryBig:0, Large:0
 
Switch#

Use the show dhcp lease command to confirm the IP address, subnet mask, default router, and static route information obtained from a DHCP server:

Switch# show dhcp lease
Temp IP addr: 10.1.1.3  for peer on Interface: unknown
Temp  sub net mask: 255.255.0.0
   DHCP Lease server: 223.255.254.254, state: 3 Bound
   DHCP transaction id: 18D9
   Lease: 86400 secs,  Renewal: 43200 secs,  Rebind: 75168 secs
Temp default-gateway addr: 10.1.0.1
Temp ip static route0: dest 223.255.254.254 router 10.1.0.1
   Next timer fires after: 00:29:59
   Retry count: 0   Client-ID: cisco-0010.7ba9.c600-Ethernet0/0/0

4.10.10 Confirm the Running Configuration

Use the more system:running-config command to confirm that the configuration being used is configured correctly:

Switch# more system:running-config
Building configuration...
 
Current configuration:
!
version 12.0
no service pad
service timestamps debug uptime
service timestamps log uptime
no service password-encryption
!
hostname switch
!
enable password foo
!
redundancy
 no associate subslot 1/0 2/0
 no associate subslot 3/0 4/0
 no associate subslot 5/0 6/0
 associate subslot 7/0 8/0
 no associate subslot 1/1 2/1
 no associate subslot 3/1 4/1
 no associate subslot 5/1 6/1
 no associate subslot 7/1 8/1
 main-cpu
facility-alarm intake-temperature major 50
facility-alarm intake-temperature minor 40
facility-alarm core-temperature major 65
facility-alarm core-temperature minor 55
ip subnet-zero
ip host boot 223.255.254.254
!
atm address 47.0091.8100.0000.0003.4ba4.9a01.0003.4ba4.9a01.00
atm router pnni
 no aesa embedded-number left-justified
 node 1 level 56 lowest
  redistribute atm-static
!
!
interface ATM0/0/0
 no ip address
 no ip directed-broadcast
 atm maxvp-number 0
!
interface Ethernet0/0/0
ip address 10.1.11.52 255.255.0.0
 no ip directed-broadcast
!
interface Ethernet0/0/1
 no ip address
 no ip directed-broadcast
!
interface ATM2/0/0
 no ip address
 no ip directed-broadcast
!
interface ATM7/0/0
 no ip address
 no ip directed-broadcast
 aps mode linear 1+1 nonreverting unidirectional
!
interface ATM7/0/1
 no ip address
 no ip directed-broadcast
 aps mode linear 1+1 nonreverting unidirectional
!
ip default-gateway 10.1.0.1
ip classless
ip route 0.0.0.0 0.0.0.0 10.1.0.1
ip http server
ip http path tftp://boot/xxx/nsp-html
!
no logging console
snmp-server community public RW
!
line con 0
 exec-timeout 0 0
 transport input none
line aux 0
line vty 0 4
 exec-timeout 0 0
 password lab
 login
!
end

4.10.11 Confirm the Saved Configuration

Use the more nvram:startup-config command to confirm that the configuration saved in NVRAM is configured correctly:

Switch# more nvram:startup-config
Using 1724 out of 520184 bytes
!
version 12.0
no service pad
service timestamps debug uptime
service timestamps log uptime
no service password-encryption
!
hostname switch
 
<information deleted>

Table of Contents

Configuring the Node Switch Processor

Example

Examples

Examples

Examples

Example

Examples

Examples