Table of Contents

Initially Configuring the ATM Switch Router

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

This chapter includes the following sections:

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.

Terminal Line Configuration (Catalyst 8540)

The ATM switch router 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 Cisco IOS Configuration Fundamentals Configuration Guide.

Terminal Line Configuration (LightStream 1010 and Catalyst 8510)

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 Cisco IOS 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:

Verify 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 appears:

The ATM switch router should be operating correctly and transferring data.

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 tasks provide an example of creating a BOOTP server configuration file:

Example

The following example BOOTP configuration file shows the added entry:

Switch: tc=netcisco0: ha=0000.0ca7.ce00: ip=172.31.7.97:

Configuring the ATM Address

The ATM switch router is autoconfigured with an ATM address using a hierarchical addressing model similar to the OSI network service access point (NSAP) addresses. PNNI uses this hierarchy to construct ATM peer groups. ILMI uses the first 13 bytes of this address as the switch prefix that it registers with end systems.

The ATM switch router 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 ATM switch router to establish itself as a node in a single-level Private Network-Network Interface (PNNI) routing domain.

This section includes the following:

Autoconfigured ATM Addressing Scheme

During the initial startup, the ATM switch router generates an ATM address using the defaults described in the Guide to ATM Technology. For complete descriptions of the commands mentioned in this section refer to the ATM Switch Router Command Reference.

Manually Setting the ATM Address

To configure a new ATM address that replaces the previous ATM address when running IISP software only, see the section "Configure the ATM Address" in the chapter "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 the section "Configure an ATM Address and PNNI Node Level" in the chapter "Configuring ATM Routing and PNNI."

Modify the Default for Physical Layer Configuration of an ATM Interface

This section describes modifying an ATM interface from the default configuration listed in the chapter "Configuring Port Adapter Interfaces." You can accept the ATM interface configuration or overwrite the default interface configuration using the CLI commands, which are described in the chapter "Configuring Virtual Connections."

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

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

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-3 physical interface 0/0/0:

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:

Examples

The following example demonstrates using the show controllers command to display the OC-3 physical interface configuration after modification of the defaults:

The following example displays the OC-3 physical layer scrambling configuration after modification of the defaults using the more system:running-config command:

Configure 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:

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:

Configure 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 tasks, beginning in global configuration mode:

Example

The following example shows how to configure interface ethernet0 with IP address 172.20.40.93 and subnetwork mask 255.255.255.0:

Display the IP Address

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

Examples

The following example shows how to use the show interface command to display the IP address of interface ethernet0:

The following example uses the more system:running-config command to display the IP address of interface ethernet0:

Test 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 command in EXEC mode:

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

Configuring Network Clocking

This section describes network clocking and network clocking configuration of the ATM switch router.

This section includes the following:

Configure Network Clock Sources and Priorities (Catalyst 8540)

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

Systems equipped with the network clock module can derive clocking from a 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:

Examples

The following example shows how to configure the network clock priorities:

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.

Configure 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:

Examples

The following example shows how to configure the network clock priorities:

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.

Configure the Transmit Clocking Source

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

Example

The following example configures ATM interface 3/0/0 to receive its transmit clocking from a network-derived source:

Display the Network Clocking Configuration

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

Examples

The following example shows the configured network clock sources:

The following example shows the switch clock source configuration with the network clock module installed:

The following example shows the clock source configuration stored in the running configuration:

Configuring Network Clocking with the 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.

For overview information about the NCDP feature refer to the Guide to ATM Technology.

How It Works

Figure 3-1 shows a hypothetical network that is synchronized to an external PRS. The network has the following configuration for clocking sources:

NCDP selects the root to be used for the clocking distribution tree by evaluating a vector comprised of the priority, stratum level, and PRS ID. These three elements can have the following values:

The clocking sources in Figure 3 have the following vectors:

The vectors are evaluated first using the priority element; the vector with the highest priority wins. If there is a tie, a comparison of the stratum level is done, and the vector with the highest stratum level wins. If there is still a tie, then the source with the external clock source wins. If there is a tie among these three elements, the software checks the stratum of the oscillator on the switch (processor or network clock module). If there is still a tie, the ATM address associated with the vector becomes the tie breaker, with the vector having the lower ATM address declared the victor.

Evaluating the configuration vectors in Figure 3-1 results in the following:

1. The first port on node C is declared the root clocking source node. With node C as the root, the software constructs a spanning network clocking distribution tree using well-known VCs. The arrows in Figure 3-1 show the construction of the tree.

2. If the link on the first port of node C fails, or the reference clock provided on this link degrades to the point where it is unusable, node C uses the local oscillator (if FC-PFQ is present) or runs in holdover mode (if the network clock module is present) until it can switch over to the second port.

Configuring a second port on the primary node with the same priority provides a backup in the event of failure of a link without the need to switch over to the second node and reconstruct the distribution tree.

Note If NCDP is configured as revertive, a failed clocking source node after a switchover is restored to use after it has been functioning correctly for 25 seconds on the Catalyst 8540 MSR and about one minute on the Catalyst 8510 MSR and LightStream 1010.

3. If the second link on node C fails, the distribution tree is reconstructed so that it is rooted at the port located on node F.

4. If the link on node F fails, node F uses its local oscillator (processor or network clock module).

5. Should the system clock source on node F fail, the local oscillator on the node with the highest stratum clock becomes the clocking source. In the event of a tie in stratum, the node with the lowest ATM address becomes the clocking source.

Considerations When Using the NCDP

The location of the primary and secondary clock source nodes is important. Locate the primary and secondary clock source nodes as close to each other as possible so that the number of disruptions seen by end systems attached to the network as the clocking root moves from primary to secondary is minimized. The primary and secondary clock source nodes should also be located as close as possible to the center of the network to minimize the height of the spanning network clock distribution tree. This ensures that the algorithm converges as quickly as possible, is more reliable because disruptions are contained within a limited portion of the tree, and minimizes the possibility of cumulative wander that could be introduced at each clocking stage.

An example of a configuration that takes these considerations into account is shown in Figure 3-2.

The network in Figure 3-2 is constructed so that the primary and secondary clock source nodes are physically adjacent and close to the center of the network. Further, to contain switchovers to a minimum number of nodes in the event of a change in root clock source node, every node that is adjacent to the primary clock source node is also adjacent to the secondary clock source node.

A further consideration in planning an NCDP implementation is the clock stratum. A node should extract clocking only from a source of equal or better stratum. When a network of switches participating in NDCP is comprised of devices of different stratum levels (for example, a network of NCDP-capable Catalyst 8540 MSR ATM switch routers and LightStream 1010 ATM switches), a node at a higher stratum level (a lower numerical stratum value) will never choose to extract its clock from a link attaching it to a lower stratum level device (a higher numerical stratum level). This can result in a partition of the network clock distribution tree into multiple trees. For example, if a Catalyst 8540 MSR has a priority 1 clock source, and a LightStream 1010 has a priority 2 clock source, and the Catalyst 8540 MSR loses its priority 1 source, it would run in holdover or free running mode and the LightStream 1010 ATM switch would switch to use the priority 2 clock source.

Enable NCDP and Configure the Maximum Diameter

You can have NCDP software automatically select the best clock source and synchronize the network to that source.

To enable NCDP, perform the following steps for each node that you want to configure for NCDP, beginning in global configuration mode:

You can optionally 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 (max-diameter) for NCDP to operate correctly. For example, in Figure 3-2, if node A has a maximum network diameter value of 11, nodes B through F must have the same value.

Enter the following command in global configuration mode:

Example

The following example shows enabling the NCDP and setting the maximum number of hops to 11:

Configure Network Clock Sources, Priorities, and Revertive Behavior

You can specify external clocking sources and override the protocol's automatic selection of source clock node, by entering the following command in global configuration mode:

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 at least 60 seconds. Nonrevertive (the default) prevents a failed source from being selected again. To configure revertive NCDP, enter the following command in global configuration mode:

Example

The following example demonstrates configuring the network clock sources, priorities, and revertive NCDP for the ports on node A in Figure 3-2:

Display the NCDP Configuration

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

Example

The following example shows the NCDP status:

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 and have particular clocking requirements. For details, refer to the chapter "Configuring Circuit Emulation Services."

Configuring Network Routing

The default software image for the ATM switch router contains the PNNI routing protocol. The PNNI protocol provides the route dissemination mechanism for complete plug-and-play capability. The following section, "Configure 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, see the chapters "Configuring ILMI" and "Configuring ATM Routing and PNNI."

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:

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:

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 tasks, beginning in privileged EXEC mode:

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.

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

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

The ATM switch router supports redundant CPU operation with dual route processors. In addition, Extended High System Availability (EHSA) is provided in the switching fabric when three switch processors are installed in the chassis. These features and their configuration are described in the following sections:

Route Processor Redundant Operation (Catalyst 8540 MSR)

The ATM switch router supports fault resistance by allowing a secondary route processor to take over if the primary fails. This secondary, or redundant, route processor runs in standby mode. In standby mode, the secondary route processor is partially booted with the Cisco IOS software; however, no configuration is loaded. At the time of a switchover, the secondary route processor takes over as primary and loads the configuration as follows:

The former primary then becomes the secondary route processor.

When the ATM switch router is powered on, the two route processors go through an arbitration to determine which is the primary route processor and which is the secondary. The following rules apply during arbitration:

During normal operation, the primary route processor is booted completely. The secondary CPU is partially up, meaning it stops short of parsing the configuration. From this point, the primary and secondary processors communicate periodically to synchronize any system configuration changes.

The following situations can cause a switchover of the primary route processor:

When a switchover occurs, PVCs are preserved; SVCs and ILMI address states are lost, and then restored after they are dynamically redetermined.

Configuring Route Processor Redundancy (Catalyst 8540 MSR)

For redundant operation, the following requirements must be met:

If these requirements are met, the ATM switch router runs in redundant mode by default. The tasks described in the following sections are optional and used only to change nondefault values.

Force a Switchover (Catalyst 8540 MSR)

You can manually force the secondary route processor to take over as primary. To do so, use the following command in privileged EXEC mode:

As long as you have not changed the default configuration register setting, which is set to autoboot by default, the secondary route processor (formerly the primary) completes the boot process from standby mode.

If you have changed the default configuration register value, you can change it back to autoboot by performing the following tasks beginning in global configuration mode:

Example

The following example shows how to change the configuration register to 0x2002:

Display the Configuration Register Value

To display the configuration register value, use the following privileged EXEC command:

The following example shows the configuration register value:

Configuration register is 0x100 (will be 0x2002 at next reload)

Synchronize the Configurations (Catalyst 8540 MSR)

During normal operation, the startup and running configurations are synchronized by default between the two route processors. In the event of a switchover, the new primary uses the current configuration.

There are two commands used to synchronize the startup and running configuration between the two route processors:

Immediately Synchronize Route Processor Configurations (Catalyst 8540 MSR)

To immediately synchronize the configurations used by the two route processors, perform the following task on the primary route processor, beginning in EXEC configuration mode:

Example

In the following example, both the startup and running configurations are synchronized immediately:

Synchronize the Configurations During Switchover (Catalyst 8540 MSR)

To manually synchronize the configurations used by the two route processors during a switchover, perform the following tasks on the primary route processor, beginning in global configuration mode:

Example

In the following example, both the startup and running configurations are synchronized:

Display the Route Processor Redundancy Configuration (Catalyst 8540 MSR)

To display the route processor redundancy configuration, use the following privileged EXEC command:

In the following example the route processor redundancy configuration displays:

Prepare a Route Processor for Removal (Catalyst 8540 MSR)

Before removing a route processor that is running the IOS in secondary mode, it is necessary to change it to ROM monitor mode. You could use the reload command to force the route processor to ROM monitor mode but the automatic reboot would occur and you would interrupt switch traffic.

Caution If you fail to prepare the secondary route processor for removal, the traffic through the switch could be interrupted.

To change the secondary route processor to ROM monitor mode and eliminate the automatic reboot prior to removal, perform the following task beginning in EXEC configuration mode:

Example

The following example, changes the secondary route processor to ROM monitor mode prior to removal:

Switching Fabric Extended High System Availability Operation (Catalyst 8540 MSR)

Slots 5, 6, and 7 in the ATM switch router chassis can accommodate either two or three switch processor cards, with a switching capacity of 10 Gbps each. The possible configurations are as follows:

When three switch processors are installed, two are active at any time, while the third runs in standby mode. By default, switch processors 5 and 7 are active and switch processor 6 is the standby. To force the standby switch processor to become active, use the redundancy preferred-switch-card-slots command.

When a switchover to the standby switch processor occurs, the system resets and all connections are lost. When the system comes up again, all PVCs and SVCs are reestablished automatically.

Configure Preferred Switching Processors (Catalyst 8540 MSR)

To configure which two of the three switch processors are active and which runs in standby mode, perform the following task on the primary route processor, beginning in EXEC configuration mode:

Example

In the following example, the preferred switch processors are configured to be in slots 5 and 7 with the slot 6 switch processor running in standby mode:

Display the Preferred Processor Redundancy Configuration (Catalyst 8540 MSR)

To display the preferred switch processor redundancy configuration, use the following privileged EXEC command:

In the following example the preferred switch processor redundancy configuration displays:

Configuring Switch Processor Extended High System Availability (Catalyst 8540 MSR)

The switch processor EHSA feature is self-configuring. The tasks described in the following sections are therefore optional.

Establish the Spare Switch Processor (Catalyst 8540 MSR)

When the switch router is powered up, and three switch processors are present, the software determines which is the spare card. You can also specify the spare card by performing the following steps, beginning in global configuration mode:

In the following example the card in slot 7 is designated the redundant switch processor:

Display the Switch Processor EHSA Configuration (Catalyst 8540 MSR)

To display the switch processor EHSA configuration, use the following privileged EXEC command:

The following shows the primary switch processor EHSA configuration:

Configuring SNMP and RMON

SNMP is an application-layer protocol that allows an SNMP manager, such a network management system (NMS), and an SNMP agent on the managed device to communicate. You can configure SNMPv1, SNMPv2, or both, on the ATM switch router. Remote Monitoring (RMON) allows you to see the activity on network nodes. By using RMON in conjunction with the SNMP agent on the ATM switch router, you can monitor traffic through network devices, segment traffic that is not destined for the ATM switch router, and create alarms and events for proactive traffic management.

For detailed instructions on SNMP and general RMON configuration, refer to the Configuration Fundamentals Configuration Guide. For instructions on configuring ATM RMON, see the chapter "Configuring ATM Accounting and ATM RMON."

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 ATM switch router prior to saving the configuration in NVRAM, all manual configuration changes are lost.

To save the running configuration to NVRAM, use the following command in privileged EXEC mode:

Testing the Configuration

The following sections describe tasks you can perform to confirm the hardware, software, and interface configuration:

Confirm the Hardware Configuration (Catalyst 8540 MSR)

Use the show hardware and show capability commands to confirm the correct hardware installation:

See "Display the Switch Processor EHSA Configuration (Catalyst 8540 MSR)" for an example of the show capability command.

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

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

Confirm the Software Version

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

Confirm Power-on Diagnostics

Use the show diag power-on command to confirm the power-on diagnostics:

Confirm the Ethernet Configuration

Use the show interface command to confirm that the Ethernet interface on the route processor is configured correctly:

Confirm the ATM Address

Use the show atm addresses command to confirm correct configuration of the ATM address for the ATM switch router:

Test 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 command:

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

Confirm the ATM Connections

Use the ping atm command to confirm that the ATM interfaces are configured correctly:

Confirm the ATM Interface Configuration

Use the show atm interface command to confirm the atm interfaces are configured correctly:

Confirm the Interface Status

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

Confirm Virtual Channel Connections

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

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

Use the show atm vc interface atm card/subcard/port vpi vci command to confirm the status of a specific ATM interface and virtual channel.

Confirm the Running Configuration

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

Confirm the Saved Configuration

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