ATM Switch Router Software Configuration Guide, 12.1(7a)EY - Initially Configuring the ATM Switch Router [Cisco Catalyst 8500 Series Multiservice Switch Routers]

Table Of Contents

Initially Configuring the ATM Switch Router

Methods for Configuring the ATM Switch Router

Terminal Line Configuration (Catalyst 8540 MSR)

Terminal Line Configuration (Catalyst 8510 MSR and LightStream 1010)

Configuration Prerequisites

Verifying Software and Hardware Installed on the ATM Switch Router

Configuring the BOOTP Server

Configuring the ATM Address

Manually Setting the ATM Address

Modifying the Physical Layer Configuration of an ATM Interface

Configuring the IP Interface

Configuring IP Address and Subnet Mask Bits

Testing the Ethernet Connection

Configuring Network Clocking

Network Clocking Features

Configuring Network Clock Sources and Priorities (Catalyst 8540 MSR)

Configuring Network Clock Sources and Priorities (Catalyst 8510 MSR and LightStream 1010)

Configuring the Transmit Clocking Source

Configuring Network Clocking with NCDP

Network Clock Services for CES Operations and CBR Traffic

Configuring Network Routing

Configuring ATM Static Routes for IISP or PNNI

Configuring System Information

Configuring Online Diagnostics (Catalyst 8540 MSR)

Access Test (Catalyst 8540 MSR)

OIR Test (Catalyst 8540 MSR)

Snake Test (Catalyst 8540 MSR)

Configuring Online Diagnostics (Catalyst 8540 MSR)

Configuring Redundancy and Enhanced High System Availability (Catalyst 8540 MSR)

Route Processor Redundant Operation (Catalyst 8540 MSR)

Synchronizing the Configurations (Catalyst 8540 MSR)

Synchronizing the Dynamic Information (Catalyst 8540 MSR)

Displaying the Route Processor Redundancy Configuration (Catalyst 8540 MSR)

Preparing a Route Processor for Removal (Catalyst 8540 MSR)

Configuring Switch Fabric Enhanced High System Availability Operation (Catalyst 8540 MSR)

Displaying the Switch Processor EHSA Configuration (Catalyst 8540 MSR)

Configuring SNMP and RMON

Storing the Configuration

Testing the Configuration

Confirming the Hardware Configuration (Catalyst 8540 MSR)

Confirming the Hardware Configuration (Catalyst 8510 MSR and LightStream 1010)

Confirming the Software Version

Confirming Power-on Diagnostics

Confirming the Ethernet Configuration

Confirming the ATM Address

Testing the Ethernet Connection

Confirming the ATM Connections

Confirming the ATM Interface Configuration

Confirming the Interface Status

Confirming Virtual Channel Connections

Confirming the Running Configuration

Confirming the Saved Configuration

Initially Configuring the ATM Switch Router

This chapter discusses specific steps used to initially configure the ATM switch router.

Note This chapter provides advanced configuration instructions for the Catalyst 8540 MSR, Catalyst 8510 MSR, and LightStream 1010 ATM switch routers. For conceptual and background information, refer to the Guide to ATM Technology. For complete descriptions of the commands mentioned in this chapter, refer to the ATM Switch Router Command Reference publication.

This chapter includes the following sections:

• Methods for Configuring the ATM Switch Router

• Configuration Prerequisites

• Configuring the BOOTP Server

• Configuring the ATM Address

• Modifying the Physical Layer Configuration of an ATM Interface

• Configuring the IP Interface

• Configuring Network Clocking

• Configuring Network Routing

• Configuring System Information

• Configuring Online Diagnostics (Catalyst 8540 MSR)

• Configuring Redundancy and Enhanced High System Availability (Catalyst 8540 MSR)

• Storing the Configuration

• Testing the Configuration

Methods for Configuring the ATM Switch Router

The ATM switch router defaults to a working configuration suitable for most networks. However, you might need to customize the configuration for your network.

Note If your Telnet station or SNMP network management workstation is on a different network from the switch, you must add a static routing table entry to the routing table. See "Configuring ATM Routing and PNNI"

Terminal Line Configuration (Catalyst 8540 MSR)

The Catalyst 8540 MSR has a console terminal line that might require configuration. For line configuration, you must first set up the line for the terminal or the asynchronous device attached to it. For a complete description of configuration tasks and commands used to set up your terminal line and settings, refer to the Configuration Fundamentals Configuration Guide and Dial Solutions Configuration Guide.

You can connect a modem to the console port. The following settings on the modem are required:

•Enable auto answer mode

•Suppress result codes

You can configure your modem by setting the DIP switches on the modem or by connecting the modem to terminal equipment. Refer to the user manual provided with your modem for the correct configuration information.

Note Because there are no hardware flow control signals available on the console port, the console port terminal characteristics should match the modem settings.

Terminal Line Configuration (Catalyst 8510 MSR and LightStream 1010)

The ATM switch has two types of terminal lines: a console line and an auxiliary line. For line configuration, you must first set up the lines for the terminals or other asynchronous devices attached to them. For a complete description of configuration tasks and commands used to set up your lines, modems, and terminal settings, refer to the Configuration Fundamentals Configuration Guide and Dial Solutions Configuration Guide.

Configuration Prerequisites

Consider the following information you might need before you configure your ATM switch router:

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

•If you want to configure a new ATM address for the switch (an autoconfigured ATM address is assigned by Cisco), you need an ATM address assigned by your system administrator.

•If you are not using BOOTP, you need an IP address and a netmask address.

Verifying Software and Hardware Installed on the ATM Switch Router

When you first power up your console and ATM switch router, a screen similar to the following from a Catalyst 8540 MSR 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) PNNI Software (cat8540m-WP-M), Version 12.0(4a)W5(10.44),  INTERIM TEST
 SOFTWARE
Copyright (c) 1986-1999 by cisco Systems, Inc.
Compiled Tue 17-Aug-99 03:18 by
Image text-base: 0x60010930, data-base: 0x60936000
CUBI Driver subsystem initializing ...
primary interrupt reg read FFC00
secondary interrupt reg read EA800
*** this cpu is the primary
Enabling the MS timer
Switch Fabric Driver subsystem initializing ...
found
 smid=0
 smid=2
 smid=4
 smid=6
 smid=1
 smid=3
 smid=5
 smid=7
in cfc_init
... DONE
IDPROM in slot 0 not properly programmed
cisco C8540MSR (R5000) processor with 262144K bytes of memory.
R5000 processor, Implementation 35, Revision 2.1 (512KB Level 2 Cache)
Last reset from power-on
3 Ethernet/IEEE 802.3 interface(s)
11 ATM network interface(s)
507K bytes of non-volatile configuration memory.
20480K bytes of Flash PCMCIA card at slot 0 (Sector size 128K).
8192K bytes of Flash PCMCIA card at slot 1 (Sector size 128K).
8192K bytes of Flash internal SIMM (Sector size 256K).
%ENABLING INTERFACES.PLEASE WAIT...
%Secondary CPU has not booted IOS
Press RETURN to get started!
Note If an rommon> prompt appears, your switch requires a manual boot to recover. Refer to the Configuration Fundamentals Configuration Guide for instructions on manually booting from Flash memory.

Configuring the BOOTP Server

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. When the switch boots, it automatically retrieves the IP address from the BOOTP server.

The switch performs a BOOTP request only if the current IP address is set to 0.0.0.0. (This is the default for a new switch or a switch that has had its startup-config file cleared using the erase command.)

To allow your ATM switch router to retrieve its IP address from a BOOTP server, you must first determine the MAC address of the switch and add that MAC address to the BOOTP configuration file on the BOOTP server. The following steps provide an example of creating a BOOTP server configuration file:

Command

Purpose

Step 1

—

Installs the BOOTP server code on the workstation, if it is not already installed.

Step 2

—

Determines the MAC address from the label on the chassis.

Step 3

—

Adds an entry in the BOOTP configuration file (usually /usr/etc/bootptab) for each switch. Press Return after each entry to create a blank line between each entry. See the example BOOTP configuration file that follows.

Step 4

Switch# reload

Restarts the ATM switch router to automatically request the IP address from the BOOTP server.

Example

The following example BOOTP configuration file shows the added entry:
# /etc/bootptab: database for bootp server (/etc/bootpd)
#
# Blank lines and lines beginning with '#' are ignored.
#
# Legend:
#
#       first field -- hostname
#                       (may be full domain name and probably should be)
#
#       hd -- home directory
#       bf -- bootfile
#       cs -- cookie servers
#       ds -- domain name servers
#       gw -- gateways
#       ha -- hardware address
#       ht -- hardware type
#       im -- impress servers
#       ip -- host IP address
#       lg -- log servers
#       lp -- LPR servers
#       ns -- IEN-116 name servers
#       rl -- resource location protocol servers
#       sm -- subnet mask
#       tc -- template host (points to similar host entry)
#       to -- time offset (seconds)
#       ts -- time servers
#
<information deleted>
#
#########################################################################
# Start of individual host entries
#########################################################################
Switch:         tc=netcisco0:   ha=0000.0ca7.ce00:      ip=172.31.7.97:
dross:          tc=netcisco0:   ha=00000c000139:        ip=172.31.7.26:
<information deleted>
Configuring the ATM Address

The ATM switch router ships with a preconfigured ATM address. The Integrated Local Management Interface (ILMI) protocol uses the first 13 bytes of this address as the switch prefix that it registers with end systems. Autoconfiguration also allows the ATM switch router 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 Guide to ATM Technology for PNNI address considerations and for information on obtaining registered ATM addresses.

For a description of the autoconfigured ATM address and considerations when assigning a new address, refer to the Guide to ATM Technology.

Manually Setting the ATM Address

To configure a new ATM address that replaces the previous ATM address when running IISP software only, see "Configuring ATM Routing and PNNI".

To configure a new ATM address that replaces the previous ATM address and generates a new PNNI node ID and peer group ID, see "Configuring ATM Routing and PNNI"

Modifying the Physical Layer Configuration of an ATM Interface

Each of the ATM switch router's physical interfaces has a default configuration, listed in "Configuring Interfaces" You can accept the defaults, or you can override them by reconfiguring the physical interface.

The following example describes modifying an OC-3c interface from the default settings to the following:

•Disable scrambling cell-payload.

•Disable scrambling STS-streaming.

•Change Synchronous Optical Network (SONET) mode of operation from Synchronous Time Stamp level 3c (STS-3c) mode to Synchronous Transfer Module level 1 (STM-1).

To change the configuration of the example interface, perform the following steps, beginning in global configuration mode:

Command

Purpose

Step 1

Switch(config)# interface atm card/subcard/port

Switch(config-if)#

Selects the physical interface to be configured.

Step 2

Switch(config-if)# no scrambling cell-payload

Disables cell-payload scrambling.

Step 3

Switch(config-if)# no scrambling sts-stream

Disables STS-stream scrambling.

Step 4

Switch(config-if)# sonet stm-1

Configures SONET mode as SDH/STM-1.

Example

The following example shows how to disable cell-payload scrambling and STS-stream scrambling and changes the SONET mode of operation to Synchronous Digital Hierarchy/Synchronous Transfer Module 1 (SDH/STM-1) of OC-3c physical interface ATM 0/0/0:
Switch(config)# interface atm 0/0/0
Switch(config-if)# no scrambling cell-payload
Switch(config-if)# no scrambling sts-stream
Switch(config-if)# sonet stm-1
To change any of the other physical interface default configurations, refer to the commands in the ATM Switch Router Command Reference publication.

To display the physical interface configuration, use the following privileged EXEC commands:

Command

Purpose

show controllers atm card/subcard/port

Shows the physical layer configuration.

more system:running-config

Shows the physical layer scrambling configuration.

Examples

The following example demonstrates using the show controllers command to display the OC-3c physical interface configuration after modification of the defaults:
Switch# show controllers atm 0/0/0
IF Name: ATM0/0/0    Chip Base Address: A8808000
Port type: 155UTP    Port rate: 155 Mbps    Port medium: UTP
Port status:SECTION LOS    Loopback:None    Flags:8300
TX Led: Traffic Pattern    RX Led: Traffic Pattern  TX clock source:  network-derived
Framing mode:  stm-1
Cell payload scrambling off
Sts-stream scrambling off
 
<information deleted>
The following example displays the OC-3c physical layer scrambling configuration after modification of the defaults using the more system:running-config command:
Switch# more system:running-config
!
version XX.X
<information deleted>
!
interface ATM0/0/0
 no keepalive
 atm manual-well-known-vc
 atm access-group tod1 in
 atm pvc 0 35 rx-cttr 3 tx-cttr 3  interface  ATM0 0 any-vci  encap qsaal
 sonet stm-1
 no scrambling sts-stream
 no scrambling cell-payload
!
<information deleted>
Configuring the IP Interface

IP addresses can be configured on the multiservice route processor interfaces. Each IP address is configured for one of the following types of connections:

•Ethernet port—Can be configured either from the BOOTP server or by using the ip address command in interface configuration mode.

•Classical IP over ATM—See "Configuring IP over ATM"

•LANE client—See "Configuring LAN Emulation"

•Serial Line Internet Protocol/Point-to-Point Protocol (SLIP/PPP)—Refer to the Dial Solutions Configuration Guide.

Note These IP connections are used only for network management.

To configure the switch to communicate via the Ethernet interface, provide the IP address and subnet mask bits for the interface.

This section includes the following:

• Configuring IP Address and Subnet Mask Bits

• Testing the Ethernet Connection

Configuring IP Address and Subnet Mask Bits

Define subnet mask bits as a decimal number between 0 and 22 for Class A addresses, between 0 and 14 for Class B addresses, or between 0 and 6 for Class C addresses. Do not specify 1 as the number of bits for the subnet field. That specification is reserved by Internet conventions.

To configure the IP address, perform the following steps, beginning in global configuration mode:

Command

Purpose

Step 1

Switch(config)# interface ethernet 0

Switch(config-if)#

Selects the interface to be configured.

Step 2

Switch(config-if)# ip address ip-address mask

Configures the IP and subnetwork address.

Note Since release 12.0(1a)W5(5b) of the ATM switch software, addressing the interface on the processor (CPU) has changed. The ATM interface is now called atm 0, and the Ethernet interface is now called ethernet 0. The old formats (atm 2/0/0 and ethernet 2/0/0) are still supported.

Example

The following example shows how to configure interface ethernet 0 with IP address 172.20.40.93 and subnetwork mask 255.255.255.0:
Switch(config)# interface ethernet 0
Switch(config-if)# ip address 172.20.40.93 255.255.255.0
Displaying the IP Address

To display the IP address configuration, use the following privileged EXEC commands:

Command

Purpose

show interfaces ethernet 0

Displays the Ethernet interface IP address.

more system:running-config

Shows the physical layer scrambling configuration.

Examples

The following example shows how to use the show interfaces command to display the IP address of interface ethernet 0:
Switch# show interfaces ethernet 0
Ethernet0 is up, line protocol is up
  Hardware is SonicT, address is 0040.0b0a.1080 (bia 0040.0b0a.1080)
  Internet address is 172.20.40.93/24
  <information deleted>
The following example uses the more system:running-config command to display the IP address of interface ethernet 0:
Switch# more system:running-config
!
version XX.X
<information deleted>
!
interface Ethernet0
 ip address 172.20.40.93 255.255.255.0
!
<information deleted>
Testing the Ethernet Connection

After you have configured the IP address(es) for the Ethernet interface, test for connectivity between the switch and a host. The host can reside anywhere in your network. To test for Ethernet connectivity, use the following EXEC command:

Command

Purpose

ping ip ip-address

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

The following example show how to test the Ethernet connectivity from the switch to a workstation with an IP address of 172.20.40.201:
Switch# ping ip 172.20.40.201
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
Configuring Network Clocking

This section describes network clocking configuration of the ATM switch router. Properly synchronized network clocking is important in the transmission of constant bit rate (CBR) and variable bit rate real time (VBR-RT) data. For an overview of network clocking and network clock configuration issues, refer to the chapter "Network Clock Synchronization" in the Guide to ATM Technology.

Network Clocking Features

Different types of network clock sources are available on the ATM switch router, both internal and external. Table 3-1 provides a summary of network clocking features.

Table 3-1 Network Clocking Feature Summary

Platform

Up/Down Detection

Loss of Synchronization Detection

Phase Adjustment Cutover

Stratum 3
Clock

BITS¹ Port

Clock Source Preference

Catalyst 8540 MSR with network clock module

Yes

Yes

Yes

Yes

Yes

Best

Catalyst 8510 MSR

Yes

Yes

Yes

No

No

Medium

LightStream 1010 with FC-PFQ

Yes

Yes

Yes

No

No

Medium

Catalyst 8540 MSR without network clock module

Yes

No

No

No

No

Poor

LightStream 1010 without FC-PFQ

Yes

No

No

No

No

Poor

¹BITS = Building Integrated Timing Supply

Configuring Network Clock Sources and Priorities (Catalyst 8540 MSR)

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

Command

Purpose

network-clock-select {priority {{atm | cbr} card/subcard/port} | bits {0 | 1} | system} |
bits {e1 | t1} | revertive

Configures the network clock priority.

Note Specifying the keyword system with the network-clock-select command selects the route processor reference clock (a stratum 4 clock source) or the network clock module (a stratum 3 clock source), if present.

Systems equipped with the network clock module can derive clocking from a Building Integrated Timing Supply (BITS) source. To specify the line type attached to the BITS ports on the network clock module and to assign a priority to a port, use the following commands in global configuration mode:

Command

Purpose

network-clock-select bits {t1 | e1}

Selects the line type. This command applies to both BITS ports.

network-clock-select priority bits {0 | 1}

Selects the priority for a BITS port.

Examples

The following example shows how to configure the network clock priorities:
Switch(config)# network-clock-select 1 atm 0/0/0
Switch(config)# network-clock-select 2 atm 0/0/3
Note This configuration assumes that a full-width module, such as the 4-port OC-12c module, is being used to derive clocking. If port adapters inserted into carrier modules are used, the priority 1 and 2 source ports must be on different port adapters.

The following example shows how to configure the network clock to revert to the highest priority clock source after a failure and takeover by the source with the next lowest priority.
Switch(config)# network-clock-select revertive
Configuring Network Clock Sources and Priorities (Catalyst 8510 MSR and LightStream 1010)

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

Command

Purpose

network-clock-select {priority {{atm | cbr} card/subcard/port} | system} | revertive

Configures the network clock priority.

Note Specifying the keyword system with the network-clock-select command selects the processor card reference clock (a stratum 4 clock source).

Examples

The following example shows how to configure the network clock priorities:
Switch(config)# network-clock-select 1 atm 0/0/0
Switch(config)# network-clock-select 2 atm 0/0/3
The following example shows how to configure the network clock to revert to the highest priority clock source after a failure and takeover by the source with the next lowest priority.
Switch(config)# network-clock-select revertive
Configuring the Transmit Clocking Source

To configure where each interface receives its transmit clocking, perform the following steps, beginning in global configuration mode:

Command

Purpose

Step 1

Switch(config)# interface atm card/subcard/port

Switch(config-if)#

Selects the interface to be configured.

Step 2

Switch(config-if)# clock source {free-running | loop-timed | network-derived}

Configures the interface clock source.

Caution If the Network Clock Distribution Protocol (NCDP) is running on an interface, you should not override that port's clock source by configuring it to free-running or loop-timed. Doing so could cause synchronization problems, particularly in the case of loop-timed, which could cause a clocking loop to be formed on a link. See the Configuring Network Clocking with NCDP.

Example

The following example configures ATM interface 3/0/0 to receive its transmit clocking from a network-derived source:
Switch(config)# interface atm 3/0/0
Switch(config-if)# clock source network-derived
Displaying the Network Clocking Configuration

To show the switch's network clocking configuration, use the following privileged EXEC commands:

Command

Purpose

show network-clocks

Shows the network clocking configuration.

more system:running-config

Shows the interface clock source configuration.

show controllers [atm card/subcard/port]

Shows the interface controller status.

Examples

The following example shows the configured network clock sources on a Catalyst 8510 MSR or LightStream 1010:
Switch# show network-clocks
clock configuration is NON-Revertive
Priority 1 clock source: ATM1/0/0
Priority 2 clock source: ATM1/1/0
Priority 3 clock source: No clock
Priority 4 clock source: No clock
Priority 5 clock source: System clock
Current clock source:System clock, priority:5
Note A source listed as "No clock" indicates that no clock source configured at that priority.

The following example shows the switch clock source configuration with the network clock module installed:
Switch# show network-clocks
Network clocking information:
---------------------------------------
Source switchover mode:    revertive
Netclkd state:             Active
Source selection method:   provisioned
NCLKM hardware status:     installed & usable
NCLKM status:              software enabled
Primary   clock source:    ATM0/0/0
Secondary clock source:    not configured
Present   clock source:    NCLKM Stratum 3 osc (0) 
The following example shows the clock source configuration stored in the running configuration:
Switch# more system:running-config
!
<information deleted>
!
network-clock-select revertive
network-clock-select 1 ATM0/0/0
<information deleted>
Configuring Network Clocking with NCDP

The Network Clock Distribution Protocol (NCDP) provides a means by which a network can synchronize automatically to a primary reference source (PRS). To do so, NCDP constructs and maintains a spanning network clock distribution tree. This tree structure is superimposed on the network nodes by the software, resulting in an efficient, synchronized network suitable for transport of traffic with inherent synchronization requirements, such as voice and video.

The following sections provide instructions for configuring NCDP. For a description of how NCDP works, refer to the Guide to ATM Technology.

Note The NCDP is intended for use on ATM switch routers equipped with FC-PFQ or with the network clock module.

NCDP Network Example

Figure 3-1 shows a network of six ATM switch routers with clocking derived from a stratum 3 PRS. Node A is configured to receive priority 1 clocking on two of its ports, while node B is configured to receive priority 2 clocking on one of its ports.

Figure 3-1 Network Configuration for NCDP

Enabling NCDP

To enable NCDP, use the following global configuration command for each node that you want to configure for NCDP:

Command

Purpose

ncdp

Enables NCDP.

Configuring Network Clock Sources and Priorities

You must specify the clocking sources, their priorities, and associated stratums used by NCDP in constructing the clock distribution tree. To do so, use the following command in global configuration mode:

Command

Purpose

ncdp source priority {{atm | cbr} card/subcard/port stratum | bits¹ {0 | 1} stratum | system}

Specifies a priority and source (stratum level or system) for this interface.

¹Allows you to specify a Building Integrated Timing Supply (BITS) source. This option is available only on the Catalyst 8540 MSR equipped with the network clock module.

If you do not configure a clock source, NCDP advertises its default source of network clock, which is its local oscillator; if no nodes in the network have a clock source configured, the tree is built so that it is rooted at the switch having the highest stratum oscillator (lowest numerical value) and lowest ATM address.

Example

The following example demonstrates configuring the network clock source, priority, and stratum on node A in Figure 3-1.
Switch(config)# ncdp source 1 atm 1/0/0 3
Switch(config)# ncdp source 1 atm 3/0/0 3
Configuring Optional NCDP Global Parameters

Optional NCDP parameters you can configure at the global level include the maximum number of hops between any two nodes, revertive behavior, and the values of the NCDP timers. To change any of these parameters from their defaults, use the following commands in global configuration mode:

Command

Purpose

ncdp max-diameter hops

Specifies the maximum network diameter for the protocol. The default maximum network diameter is 20.

ncdp revertive

Specifies the NCDP as revertive.

ncdp timers {hello | hold} time-in-msec jitter-percent

Specifies the values to be used by the NCDP timers.

When you specify a maximum diameter, you constrain the diameter of the spanning tree by specifying the maximum number of hops between any two nodes that participate in the protocol. Each node must be configured with the same maximum network diameter value for NCDP to operate correctly.

When you configure the NCDP as revertive, a clock source that is selected and then fails is selected again once it has become operational for a period of time. On the Catalyst 8510 MSR and LightStream 1010 platforms, if NCDP is configured to be revertive, a failed clocking source node after a switchover is restored to use after it has been functioning correctly for at least 1 minute. On the Catalyst 8540 MSR the failed source is restored after about 25 seconds. The network clock is, by default, configured as nonrevertive. Nonrevertive prevents a failed source from being selected again.

Example

The following example shows setting the maximum number of hops to 11 and enabling revertive behavior:
Switch(config)# ncdp max-diameter 11
Switch(config)# ncdp revertive
Configuring Optional NCDP Per-Interface Parameters

On a per-interface basis, you can enable or disable NCDP, specify the cost metric associated with the port, and change the control virtual circuit used to transport protocol messages between adjacent protocol entities. To change any of these parameters from their defaults, use the following commands in interface configuration mode:

Command

Purpose

ncdp admin-weight weight

Specifies the cost metric associated with the given port.

ncdp control-vc vpi vci

Specifies the VPI/VCI values to use for control VCs on the physical interface. The default is 0, 34.

Note To change the control VC to a VPI other than 0, the VPI must exist on the physical interface.

no ncdp

Disables NCDP on the interface.

Example

The following example demonstrates setting the administrative weight on an interface:
Switch(config)# interface atm 0/0/0
Switch(config-if)# ncdp admin-weight 75
Displaying the NCDP Configuration

To display the NCDP configuration, use the following EXEC commands:

Command

Purpose

show ncdp path root

Displays the NCDP clock path from the switch to the root source.

show ncdp ports

Displays NCDP port information.

show ncdp sources

Displays NCDP clock sources configured on the switch.

show ncdp status

Displays NCDP status.

show ncdp timers

Displays NCDP timer information.

Example

The following example shows the NCDP status:
Switch# show ncdp status
 = ncdp switch information ==== enabled ==============
 non-revertive
 root clock source priority:      1
 root clock source stratum level: 4
 root clock source prs id:        255
 stratum level of root switch:    4
 clocking root address:           4700918100000000E0F75D040100E0F75D040100
 hop count:                       0
 root path cost:                  0
 root port:                       0
 max age:                         5
 hello time:                      500
 priority      of best source:    1
 stratum level of best source:    4
 prs id        of best source:    255
 switch stratum level:            4
 address:                         4700918100000000E0F75D040100E0F75D040100
 switch max age:                  5
 switch hello time:               500
 switch hold time:                500
 max diameter:                    5
 converged root count:            359375
 converged:                       1
 total timer events:              687271
 total queue events:              0
 rx config messages:              0
 tx config messages:              363716
 rx tcn messages:                 0
 tx tcn messages:                 0
 rx non-participant messages:     0
 rx unknown messages:             0
Switch#
Network Clock Services for CES Operations and CBR Traffic

Circuit emulation services-interworking functions (CES-IWF) and constant bit rate (CBR) traffic relate to a quality of service (QoS) classification defined by the ATM Forum for Class A (ATM adaptation layer 1 [AAL1]) traffic in ATM networks. In general, Class A traffic pertains to voice and video transmissions, which have particular clocking requirements. For details, refer to "Configuring Circuit Emulation Services"

Configuring Network Routing

The default software image for the ATM switch router contains the Private Network-Network Interface (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 Interim-Interswitch Signalling Protocol (IISP) routing configurations.

For routing protocol configuration information, refer to "Configuring ILMI,"and "Configuring ATM Routing and PNNI"

Configuring 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

Purpose

atm route addr-prefx atm card/subcard/port

Specifies a static route to a reachable address prefix.

Note An interface must be User-Network Interface (UNI) or Interim Interswitch Signalling Protocol (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 ATM 3/0/0:
Switch(config)# atm route 47.0091.8100.567.0000.0ca7.ce01 atm 3/0/0
Switch(config)# 
Configuring System Information

Although not required, the system clock and hostname should be set as part of the initial system configuration. To set these system parameters, perform the following steps, beginning in privileged EXEC mode:

Command

Purpose

Step 1

Switch# clock set hh:mm:ss day month year

Sets the system clock.

Step 2

Switch# configure terminal

Switch(config)#

Enters global configuration mode from the terminal.

Step 3

Switch(config)# hostname name

Sets the system name.

Examples

The following example shows how to configure the time, date, and month using the clock set command, enter global configuration mode, and assign a hostname.
Switch# clock set 15:01:00 17 October 1999
Switch# configure terminal
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 1999
Configuring Online Diagnostics (Catalyst 8540 MSR)

Online and insertion diagnostics detect and report hardware failures in the Catalyst 8540 MSR during system bootup and operation.

The online diagnostics on the Catalyst 8540 MSR provide the following types of tests:

•Access tests between the route processor and the switch processors, feature cards, port adapters, and interface modules

•Online insertion and removal (OIR) diagnostic tests

•Snake tests through the switch router to ensure connectivity between the ports

Note Online diagnostics tests only run on the primary route processor.

Access Test (Catalyst 8540 MSR)

The access tests ensure connectivity at a configurable interval between the primary route processor and the following:

•Active switch processors

•Standby switch processor, if it is present

•Feature cards

•Carrier modules

•ATM port adapters

•ATM and Layer 3 interface modules

•ATM router modules

When the access test detects a hardware failure, the system issues an error message to the console.

If the access test detects a hardware problem with an active switch processor, the standby switch processor, if it is present, automatically takes over and becomes an active switch processor. The system generates an SNMP trap when the switchover occurs.

Note The access test does not support the network clock module.

OIR Test (Catalyst 8540 MSR)

Online insertion and removal (OIR) tests check the functioning of the switch fabric and interfaces on a per-port basis. The switch router performs these tests when the system boots up and when you insert a port adapter or interface module into a slot. The OIR test sends a packet to the interface loopback and expects to receive it back within a certain time period. If the packet does not reach the port within the expected time period, or the route processor receives a corrupted packet, the system issues an error message to the console, generates an SNMP trap, and brings the port to an administrative down state.

Note The size of the packet used in the test is configurable.

The OIR tests support all ATM port adapters, all ATM interface modules, all ATM router modules, and all Layer 3 interface modules except the 8-port Gigabit Ethernet.

Snake Test (Catalyst 8540 MSR)

The snake test detects and reports port-to-port connectivity failures. The snake test establishes a connection across all the active ports in the switch router, originating and terminating at the primary route processor. The route processor establishes a connection by sending a packet to each port in turn, which then terminates at the route processor. If the packet does not reach the route processor within the expected time period, or the received packet is corrupted, further testing is performed to isolate and disable the port causing the problem.The size of the packet and frequency of the test are configurable to minimize the impact on system performance.

The snake test supports all ATM interface modules and enhanced Gigabit Ethernet interface modules. It does not support ATM port adapters, ATM router modules, 16-port 10/100 Fast Ethernet interface modules, 2-port Gigabit Ethernet interface modules, or 8-port Gigabit Ethernet interface modules.

Note The snake test does not support ATM port adapters because of a hardware limitation in the carrier module.

Configuring Online Diagnostics (Catalyst 8540 MSR)

To configure online diagnostics, use the following global configuration commands:

Command

Purpose

diag online

Enables all of the online diagnostic tests.

diag online access

Enables only the access diagnostic test.

diag online access freq [seconds]

Configures the frequency of the access diagnostic tests. The default frequency is every 10 seconds.

diag online oir

Enables only the OIR test.

diag online oir pktsize [bytes]

Specifies the packet size for the OIR test. The default size is 1000 bytes.

diag online snake

Enables only the snake test.

diag online snake timer [seconds]

Specifies the time interval for the snake test. The default interval is 60 seconds.

no diag online [access | oir | snake]

Disables the online diagnostic tests.

debug diag online [access | oir | snake]

Enables debugging of online diagnostic tests.

no debug diag online [access | oir | snake]

Disables debugging of online diagnostic tests.

Examples

The following example shows how to enable all online diagnostic tests:
Switch(config)# diag online
 ONLINE-DIAG: Enabling all Online Diagnostics tests 
The following example shows how to change the frequency of the access test to 20 seconds:
Switch(config)# diag online access freq 20
ONLINE-DIAG: Online Access Test Frequency set to 20 sec
Displaying the Online Diagnostics Configuration and Results (Catalyst 8540 MSR)

To display the online diagnostics configuration and results, use the following EXEC command:

Command

Purpose

show diag online [details | status] [access | oir | snake]

Displays information about the online diagnostics test configuration and the test results.

Examples

The following example shows how to display detailed access test configuration and results:
Switch# show diag online details access
======== Online Access Test Details ========
Current Test Status : Test is Enabled
Current Frequency of Access Test : 20 seconds
Slot Card-Type       Iteration    Success    Failure    Last Failure 
---- ----------      ----------   -------    -------    ------------ 
 0/* Super Cam       42998        42998      0          ----
 0/0 8T1 IMA PAM     42998        42998      0          ----
 0/1 8E1 IMA PAM     42998        42998      0          ----
 2/* ARM PAM         42998        42998      0          ----
 3/* ETHERNET PAM    42998        42998      0          ----
 5/* Switch Card     42998        42998      0          ----
 5/0 Feature Card    42998        42998      0          ----
 7/* Switch Card     42998        42998      0          ----
 7/0 Feature Card    42998        42998      0          ----
 9/* OC48c PAM       42998        42998      0          ----
10/* OCM Board       42998        42998      0          ----
10/0 QUAD 622 Generi 42998        42998      0          ----
======== Online Access Test Details End ========
The following example shows how to display the status of the OIR test:
Switch# show diag online status oir
======== Online OIR Test Status ========
Current Test Status : Test is Enabled
-------- Bootup OIR status --------
Port    Card Type   Pkt Size  Result                    Test Time LOOP
_______ ___________ _________ ___________________  ______________ ____
00/0/00 8T1 IMA PAM       300 OIR_SUCCESS                00:00:41  PIF
00/0/01 8T1 IMA PAM       300 OIR_SUCCESS                00:00:41  PIF
00/0/02 8T1 IMA PAM       300 OIR_SUCCESS                00:00:41  PIF
00/0/03 8T1 IMA PAM       300 OIR_SUCCESS                00:00:41  PIF