|
|
This chapter discusses how to initially configure the ATM switch, and includes the following sections:
The ILMI and PNNI protocols, when used with an IP address autoconfiguration mechanism such as BOOTP, allow the ATM switch to be entirely self-configured. Through network management applications and the text-based command-line interface (CLI), you can configure and customize all aspects of the operation of the switch.
You must assign an IP address to allow up to eight simultaneous Telnet sessions to connect to the switch or to use the Simple Network Management Protocol (SNMP) system for the switch. The Ethernet IP address is assigned either manually or by a BOOTP server. See the section "Configure IP Interface Parameters" in this chapter.
Two methods are available for configuring the ATM switch:
Consider the following information you might need before you configure your ATM switch:
When you first power up your console and ATM switch, 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) PNNI Software (ls1010-wp-m), Version XX.X(X.X.WAX.X.XX)
Copyright (c) 1986-1998 by cisco Systems, Inc.
Compiled Tue NNXXX-98 02:59 by
Image text-base: 0x600108D0, data-base: 0x603EE000
cisco ASP (R4600) processor with 16384K bytes of memory.
R4600 processor, Implementation 32, Revision 2.0
Last reset from power-on
1 Ethernet/IEEE 802.3 interface(s)
25 ATM network interface(s)
125K bytes of non-volatile configuration memory.
8192K bytes of Flash PCMCIA card at slot 0 (Sector size 128K).
8192K bytes of Flash internal SIMM (Sector size 256K).
Press RETURN to get started!
The ATM switch should be operating correctly and transferring data.
rommon> prompt appears, your switch requires a manual boot to recover. Refer to the Cisco Configuration Fundamentals Configuration Guide for instructions on manually booting from Flash memory.
| Step | Command | Task |
|---|---|---|
| 1 | --- | Install the BOOTP server code on the workstation, if it is not already installed. |
| 2 | --- | Determine the MAC address from the label on the chassis. |
| 3 | --- | Add 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. |
| 4 | reload | Restart the ATM switch to automatically request the IP address from the BOOTP server. |
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>
The ATM switch 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.
During the initial startup, the ATM switch generates an ATM address using the defaults shown in Figure 3-2.
Using the default address format has the following features and implications:
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 ILMI."
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."
Multiple addresses can be configured for a single switch, and this configuration can be used during ATM address migration. ILMI registers end systems with multiple prefixes during this period until an old address is removed. PNNI automatically summarizes all the switch prefixes in its reachable address advertisement.
For operation with ATM addresses other than the autoconfigured ATM address, use the atm address command to manually assign a 20-byte ATM address to the switch. The atm address command address_template variable can be a full 20-byte address or a 13-byte prefix followed by ellipses (...). Entering the ellipses will automatically add one of the switch's 6-byte MAC addresses in the ESI portion and 0 in the selector portion of the address.
When the switch 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:
See the chapter "Configuring Port Adapter Interfaces" for the interface default configuration and modification procedures.
You can accept the default ATM interface configuration or overwrite the default interface configuration as described in the chapter "Configuring ATM Network Interfaces."
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:
| Step | Command | Task |
|---|---|---|
| 1 | interface atm card/subcard/port | Select the physical interface to be configured. |
| 2 | no scrambling cell-payload | Disable cell-payload scrambling. |
| 3 | no scrambling sts-stream | Disable STS-stream scrambling. |
| 4 | Configure SONET mode as SDH/STM-1. |
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 LightStream 1010 ATM Switch and Catalyst 8510 MSR Command Reference.
To display the physical interface configuration, use the following privileged EXEC commands:
| Command | Task |
|---|---|
show controllers atm card/subcard/port | Show the physical layer configuration. |
more system:running-config | Show the physical layer scrambling configuration. |
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-3 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>
IP addresses can be configured on the 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, as described in the following sections.
Internet addresses are 32-bit values assigned to hosts that use the IP protocols. These addresses are in dotted decimal format (four decimal numbers separated by periods) such as 192.17.5.100. Each number is an 8-bit value between 0 and 255. The following is a summary of IP addressing concepts for those who are somewhat familiar with IP addressing.
The addresses are divided into three classes, which differ in the number of bits allocated to the network and host portions of the address:
Default: None.
Enter your Internet address in dotted decimal format for each interface you plan to configure.
Subnetting is an extension of the Internet addressing scheme, which allows multiple physical networks to exist within a single Class A, B, or C network. The usual practice is to use a few of the far left bits in the host portion of the network address for a subnet field. The subnet mask determines whether subnetting is in effect on a network.
Internet addressing conventions allow a total of 24 host bits for Class A addresses, 16 host bits for Class B addresses, and 8 host bits for Class C addresses. When you are further subdividing your network (that is, subnetting your network), the number of host addressing bits is divided between subnetting bits and actual host address bits. You must specify a minimum of two host address bits, or the subnetwork is not populated by hosts.
Default: 0.
Table 3-1 provides a summary of subnetting parameters.
| First Class | First Byte | Network Bits | Host Bits | |
|---|---|---|---|---|
| Max Subnet Bits | Min Address Bits | |||
A | 1-126 | 8 | 22 | 2 |
B | 128-191 | 16 | 14 | 2 |
C | 192-223 | 24 | 6 | 2 |
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:
| Step | Command | Task |
|---|---|---|
| 1 | interface ethernet0 | Select the interface to be configured. |
| 2 | ip address ip-address mask | Configure the IP and subnetwork address. |
Switch(config)# interface ethernet0
Switch(config-if)# ip address 172.20.40.93 255.255.255.0
To display the IP address configuration, use the following privileged EXEC commands:
| Command | Task |
|---|---|
Display the Ethernet interface IP address. | |
more system:running-config | Show the physical layer scrambling configuration. |
The following example shows how to use the show interface command to display the IP address of interface ethernet0:
Switch# show interface ethernet0
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 ethernet0:
Switch# more system:running-config
! version XX.X <information deleted> ! interface Ethernet0 ip address 172.20.40.93 255.255.255.0 ! <information deleted>
| Command | Task |
|---|---|
ping 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 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:
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
This section describes network clocking and network clocking configuration of the ATM switch. Network clocking configuration is described in the following sections:
The following subsections describe how to configure the sources and priority of network clocking.
A derived clock is received, along with data, from a specified interface. For example, in Figure 3-3 the clocking signal configured as priority one is extracted from the data received at interface 0/0/0 and is distributed as the transmit clock to the rest of the switch through the backplane. Interface 3/0/0 is configured to use network-derived transmit clocking, received across the backplane from interface 0/0/0.
If the network clock source interface goes down, the software switches to the next highest-configured priority network clock source. For example, Figure 3-4 shows the following:
To configure the network clocking priorities and sources, use the following command in global configuration mode:
| Command | Task |
|---|---|
network-clock-select priority {interface-type card/subcard/port | system} [revertive] | Configure the network clock priority. |
The following example shows how to configure the network clock priorities shown in Figure 3-4:
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
To configure where each interface receives its transmit clocking, perform the following tasks, beginning in global configuration mode:
| Step | Command | Task |
|---|---|---|
| 1 | interface atm card/subcard/port | Select the interface to be configured. |
| 2 | clock source {free-running | loop-timed | network-derived} | Configure the interface clock source. |
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
To show the switch's network clocking configuration, use the following privileged EXEC commands:
| Command | Task |
|---|---|
Show the network clocking configuration. | |
more system:running-config | Show the interface clock source configuration. |
show controllers [atm card/subcard/port] | Show the interface controller status. |
The following example shows the configured network clock sources:
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
The following example shows the clock source configuration stored in the running configuration:
Switch# more system:running-config
! version XX.X no service pad no service password-encryption ! hostname LS1010 ! network-clock-select 1 ATM1/0/0 network-clock-select 2 ATM1/1/0 ! <information deleted>
The following example displays the clock source in the interface controller configuration of ATM interface 1/0/0:
Switch# show controllers atm 1/0/0
IF Name: ATM1/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 <information deleted>
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.
If the clock frequency is not the same at both the ingress and egress nodes of the circuit, the data queues and buffers in the network either overflow or underflow, resulting in periodic line errors.
The CES modules have been designed specifically to handle CBR traffic in an ATM networking environment. To provide the required timing functions to support CES operations, you can specify any one of three clocking modes:
However, to support synchronous clocking or SRTS clocking in your ATM switch operating environment, your network must incorporate the following facilities:
Planning, designing, and implementing an ATM network requires many considerations. Such considerations might include, but are not limited to, the specific hardware used in the network, the purposes served by the network, the protocols implemented within the network, and the physical topology of the network.
Among these important considerations is how a clocking signal should be distributed within the network. In all cases, distributing a clocking signal within the network ensures that each CBR device has access to a common reference clocking signal for synchronizing CBR data transport.
For this reason, planning for distributing a timing signal must be done on a per-chassis basis. Planning must also include a means for distributing up to three alternative clocking signals, in the event of failure of the primary clock signal. You can think of network clocking in general as a kind of protocol to be implemented in the network.
In summary, network administrators must plan for the following:
When these network clocking facilities are established and operational, they tend to remain static until the primary clock is lost for any reason. In this case, network clocking is dynamic in the sense that an alternate clocking signal must be placed into effect immediately, so the network can remain operational.
In many cases, using a clocking signal from a telephone company is the simplest and best solution for a stable and reliable clocking signal, especially in those instances where you are already using a CES circuit to interconnect telephone equipment.
For example, to meet its own need for internal consistency, a telephone company typically distributes a timing signal to govern its own networking operations. Therefore, the telephone company has already addressed timing requirements similar to those that an ATM switch user must address in relation to their own CES operations. Consequently, a private branch exchange (PBX) can serve as a ready means for providing a timing signal to any user CBR device.
A network administrator can define up to two clocking signal sources per chassis, assigning a priority to each one. Under normal operating conditions, the priority 1 signal serves as the primary clocking signal. The priority 2 signal source serves as a backup in the event of failure of the primary (priority 1) clock.
As is the case for other modules, the clock sources for a CES module can be configured as revertive or nonrevertive. For example, assume that a clock of lower priority is currently in effect due to failure of a higher priority clock source. If network clocking is revertive, the system automatically reverts to the higher priority clock signal when the higher priority clock is again restored to service for at least one minute.
To make use of network timing services in an ATM switch chassis, you must define the port from which a network timing signal is to be taken, and specify the alternative clock source for the port in the same order of priority as specified for the network at large.
You can accomplish these clock configuration tasks by using the network-clock-select command, as described in the section "Configure Network Clock Sources and Priorities."
A PRS from a major telephone carrier is often the timing signal of choice, because such signals are known to be highly stable, reliable, and accurate.
Any module in an ATM switch chassis capable of receiving and distributing a network timing signal can propagate that signal to any similarly capable module in the chassis.The following entities are capable of receiving and distributing a PRS:
By issuing the network-clock-select command with appropriate parameters, you can define a particular port in an ATM switch 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 section "Configure Network Clock Sources and Priorities."
You can also use the network-clock-select command to designate a particular port in an ATM switch chassis to serve as a "master clock" source for distributing a single clocking signal throughout the chassis or to other network devices. Hence, this reference signal can be distributed wherever needed in the network to globally synchronize the flow of CBR data.
For CES operations and CBR traffic, as noted earlier, three locking modes can be used with any CES module. Table 3-2 summarizes, in order of preference, the characteristics of the three clocking modes available for handling CBR traffic in an ATM switch networking environment.
| Clocking Mode | Advantages | Limitations |
|---|---|---|
Supports both unstructured (clear channel) and structured CBR traffic. Exhibits superior wander and jitter characteristics. | Requires a PRS and network clock synchronization services. Ties the CES interface to the network clock synchronization services clocking signal (PRS). | |
Conveys externally generated user clocking signal through ATM network, providing independent clocking signal for each CES circuit. | Requires a PRS and network clock synchronization services. Supports only unstructured (clear channel) CBR traffic. Exhibits moderate wander characteristics. | |
Does not require a PRS or network clock synchronization services. | Supports only unstructured (clear channel) CBR traffic. Exhibits poorest wander characteristics. |
Although the wander and jitter characteristics of these clocking modes differ, all clocking modes preserve the integrity of the your CBR data, ensuring error-free data transport from source to destination. However, there are important differences, summarized as follows:
When equipped with a CES module and appropriate software, any ATM switch can:
Figure 3-5 shows that an ATM switch can use a PRS that originates from one of two possible sources. However, this does not mean that only two such clocking signals can be made available for use in the ATM network. In fact, numerous clocking signals may be present in the ATM switch operating environment.
The important concepts shown in Figure 3-5 include the following:
Note that each PRS in Figure 3-5 is externally generated. The timing signal originates from a source outside the ATM network---either the PBX or an OC-3 or OC-12 trunk line that can propagate a PRS between adjacent ATM networks.
If the priority 1 PRS fails, the network clock synchronization service automatically recovers network timing by using the priority 2 PRS available from another source.
Assume that the T1/E1 trunk at the top of Figure 3-5 is currently supplying a priority 1 PRS to the network. If the PRS fails, the OC-3/OC-12 trunk line (linking the adjacent ATM networks) can provide a secondary (priority 2) PRS for network synchronization purposes. If network clocking is configured as revertive, the network clock synchronization service automatically reverts to the priority 1 PRS when its service is restored.
Figure 3-6 shows how a PRS for synchronous clocking can be provided to an edge node of an ATM network and propagated through the network to synchronize the flow of CBR data between the communicating ATM end nodes.
In this network scenario, a PRS is available to the network by the PBX at the edge of the network. The PRS is present at the port of a CES module in edge node A (the ingress node). From there, the PRS is propagated into the first ATM network through an ATM port and conveyed across an OC-3 trunk to an adjacent ATM network. This same clocking signal is then used to synchronize the handling of CBR data in edge node B (the egress node).
See the preceding sections for clocking configuration examples:
SRTS clocking can be used if the your edge equipment is driven by a different clocking signal than that being used in the ATM network. Figure 3-7 shows such an operating scenario, in which a timing signal is provided to edge nodes independently from the ATM network.
Using Figure 3-7, assume that the user of edge node 1 wants to send CBR data to a user at edge
node 3. In this scenario, SRTS clocking works as follows:
1. Clock A is driving the devices within the ATM network.
2. At edge node 1, the user introduces CBR traffic into the ATM network according to clock B.
3. As edge node 1 segments the CBR bit stream into ATM cells, it measures the difference between user clock B, which drives it and network clock A.
4. As edge node 1 generates the ATM cell stream, it incorporates this delta value into every eighth cell.
5. The cells are then propagated through the network in the usual manner.
6. As destination edge node 3 receives the cells, this node not only reassembles the ATM cells into the original CBR bit stream, but also reconciles, or reconstructs, the user clock B timing signal from the delta value carried within every eighth ATM cell.
Thus, during SRTS clocking, CBR traffic is synchronized between the ingress (segmentation) side of the CES circuit and the egress (reassembly) side of the circuit according to user clock signal B, while the ATM network continues to function according to clock A.
The name adaptive clocking mode reflects the fact that the rate at which CBR data is propagated through an ATM network is driven essentially by the rate at which CBR data is introduced into the network by the user's edge equipment. The actual rate of CBR data flow through the network may vary from time to time during adaptive clocking, depending on how rapidly (or how slowly) CBR data is being introduced into the network. Nevertheless, CBR data transport through the network occurs in a "pseudo synchronous" manner that ensures the integrity of the data.
Adaptive clocking requires neither the network clock synchronization service nor a global PRS for effective handling of CBR traffic. Rather than using a clocking signal to convey CBR traffic through an ATM network, adaptive clocking in a CES module infers appropriate timing for data transport by calculating an "average" data rate upon arrival and conveying that data to the output port of the module at an equivalent rate.
For example, if CBR data is arriving at a CES module at a rate of so many bits per second, then that rate is used, in effect, to govern the flow of CBR data through the network. What happens behind the scenes, however, is that the CES module automatically calculates the average data rate using microcode (firmware) built into the board. This calculation occurs dynamically as user data traverses the network.
When the CES module senses that its segmentation and reassembly (SAR) buffer is filling up, it increases the rate of the transmit (TX) clock for its output port, thereby draining the buffer at a rate that is consistent with the rate of data arrival.
Similarly, the CES module slows down the transmit clock of its output port if it senses that the buffer is being drained faster than CBR data is being received. Adaptive clocking attempts to minimize wide excursions in SAR buffer loading, while at the same time providing an effective means of propagating CBR traffic through the network.
Relative to the other clocking modes, implementing adaptive clocking is simple and straightforward. It does not require network clock synchronization services, a PRS, or the advance planning typically associated with developing a logical network timing map. However, adaptive clocking does not support structured CES services, and it exhibits relatively high wander characteristics.
The following factors enter into proper functioning of CES circuits:
The default software image for the ATM switch 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."
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 card/subcard/port | Specify a static route to a reachable address prefix. |
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)#
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:
| Step | Command | Task |
|---|---|---|
| 1 | clock set hh:mm:ss day month year | Set the system clock. |
| 2 | configure | Enter global configuration mode from the terminal. |
| 3 | hostname name | Set the system name. |
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 1997
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 1997
For detailed instructions on SNMP and general RMON configuration, see the Configuration Fundamentals Configuration Guide. For instructions on configuring ATM RMON, see the chapter "Configuring ATM Accounting and ATM RMON."
To save the running configuration to NVRAM, use the following command in privileged EXEC mode:
| Command | Task |
|---|---|
copy system:running-config nvram:startup-config | Copy the running configuration in system memory to the startup configuration stored in NVRAM. |
The following sections describe tasks you can perform to confirm the hardware, software, and interface configuration:
Use the show hardware and command to confirm the correct hardware installation:
Switch# show hardware
LS1010 named ls1010_c5500, Date: XX:XX:XX UTC Thu Jan 8 1998 Feature Card's FPGA Download Version: 10 Slot Ctrlr-Type Part No. Rev Ser No Mfg Date RMA No. Hw Vrs Tst EEP ---- ------------ ---------- -- -------- --------- -------- ------- --- --- 0/0 T1 PAM 12-3456-78 00 00000022 Aug 01 95 00-00-00 0.4 0 2 0/1 T1 PAM 12-3456-78 00 00000025 Aug 01 95 00-00-00 0.4 0 2 1/0 155MM PAM 73-1496-03 06 02180446 Jan 17 96 00-00-00 3.0 0 2 1/1 QUAD DS3 PAM 73-2197-02 00 03656116 Dec 18 96 00-00-00 1.0 0 2 3/0 155MM PAM 73-1496-03 00 02180455 Jan 17 96 00-00-00 3.0 0 2 2/0 ATM Swi/Proc 73-1402-06 D0 07202996 Dec 20 97 00-00-00 4.1 0 2 2/1 FeatureCard1 73-1405-05 B0 07202788 Dec 20 97 00-00-00 3.2 0 2 DS1201 Backplane EEPROM: Model Ver. Serial MAC-Address MAC-Size RMA RMA-Number MFG-Date ------ ---- -------- ------------ -------- --- ---------- ----------- LS1010 2 69000050 00400B0A2E80 256 0 0 Aug 01 1995
Use the show version command to confirm the correct version and type of software and the configuration register are installed:
Switch# show version
Cisco Internetwork Operating System Software IOS (tm) PNNI Software (LS1010-WP-M), Version XX.X(X), RELEASE SOFTWARE (fc1) Copyright (c) 1986-1998 by cisco Systems, Inc. Compiled XXX XX-XXX-XX XX:XX by Image text-base: 0x60010910, data-base: 0x604E6000 ROM: System Bootstrap, Version XX.X(X.X.WAX.X) [integ X.X.WAX.X], RELEASE SOFTWARE Switch uptime is 2 weeks, 2 days, 39 minutes System restarted by power-on System image file is "bootflash:ls1010-wp-mz.XXX-X.X.X.FWAX.X.XX", booted via bootflash cisco ASP (R4600) processor with 65536K bytes of memory. R4700 processor, Implementation 33, Revision 1.0 Last reset from power-on 1 Ethernet/IEEE 802.3 interface(s) 20 ATM network interface(s) 123K bytes of non-volatile configuration memory. 8192K bytes of Flash internal SIMM (Sector size 256K). Configuration register is 0x2101
Use the show diag power-on command to confirm the power-on diagnostics:
Switch# show diag power-on
LS1010 Power-on Diagnostics Status (.=Pass,F=Fail,U=Unknown,N=Not Applicable) ----------------------------------------------------------------------------- Last Power-on Diags Date: 97/12/29 Time: 16:27:18 By: V 3.40 BOOTFLASH: . PCMCIA-Slot0: . PCMCIA-Slot1: . CPU-IDPROM: . FCard-IDPROM: . NVRAM-Config: . SRAM: . DRAM: . PS1: N PS2: N PS (12V): . FAN: . Temperature: . Bkp-IDPROM: . MMC-Switch Access: . Accordian Access: . LUT: . ITT: . OPT: . OTT: . STK: . LNK: . ATTR: . Queue: . Cell-Memory: . Feature-Card Access: . ICC: . OCC: . OQP: . OQE: . CC: . RT: . TM0: . TM1: . TMC: . IT: . LT: . RR: . ABR: . Access/Interrupt/Loopback/CPU-MCast/Port-MCast/FC-MCast/FC-TMCC Test Status: Ports 0 1 2 3 ---------------------------------------------------------------------------- Ethernet-port Access: . Ethernet-port CAM-Access: . Ethernet-port Loopback: . Ethernet-port Loadgen: . Power-on Diagnostics Passed.
Use the show interface command to confirm that the Ethernet interface on the processor is configured correctly:
Switch# show interface ethernet0
Ethernet0 is up, line protocol is up
Hardware is SonicT, address is 0000.0000.0000 (bia 0000.0000.0000)
Internet address is 172.20.52.20/26
MTU 1500 bytes, BW 10000 Kbit, DLY 1000 usec, rely 255/255, load 1/255
Encapsulation ARPA, loopback not set, keepalive set (10 sec)
ARP type: ARPA, ARP Timeout 04:00:00
Last input 00:00:00, output 00:00:00, output hang never
Last clearing of "show interface" counters never
Queueing strategy: fifo
Output queue 0/40, 0 drops; input queue 0/75, 0 drops
5 minute input rate 1000 bits/sec, 2 packets/sec
5 minute output rate 0 bits/sec, 1 packets/sec
69435 packets input, 4256035 bytes, 0 no buffer
Received 43798 broadcasts, 0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
0 input packets with dribble condition detected
203273 packets output, 24079764 bytes, 0 underruns
0 output errors, 0 collisions, 2 interface resets
0 babbles, 0 late collision, 0 deferred
0 lost carrier, 0 no carrier
0 output buffer failures, 0 output buffers swapped out
Use the show atm addresses command to confirm correct configuration of the ATM address for the ATM switch:
Switch# show atm addresses
Switch Address(es): 47.009181000000000100000001.000100000001.00 active Soft VC Address(es): 47.0091.8100.0000.0001.0000.0001.4000.0c80.9000.00 ATM1/1/0 47.0091.8100.0000.0001.0000.0001.4000.0c80.9010.00 ATM1/1/1 47.0091.8100.0000.0001.0000.0001.4000.0c80.9020.00 ATM1/1/2 47.0091.8100.0000.0001.0000.0001.4000.0c80.9030.00 ATM1/1/3 47.0091.8100.0000.0001.0000.0001.4000.0c81.8000.00 ATM3/0/0 47.0091.8100.0000.0001.0000.0001.4000.0c81.8000.63 ATM3/0/0.99 47.0091.8100.0000.0001.0000.0001.4000.0c81.8010.00 ATM3/0/1 47.0091.8100.0000.0001.0000.0001.4000.0c81.8020.00 ATM3/0/2 47.0091.8100.0000.0001.0000.0001.4000.0c81.8030.00 ATM3/0/3 47.0091.8100.0000.0001.0000.0001.4000.0c81.9000.00 ATM3/1/0 47.0091.8100.0000.0001.0000.0001.4000.0c81.9010.00 ATM3/1/1 47.0091.8100.0000.0001.0000.0001.4000.0c81.9020.00 ATM3/1/2 47.0091.8100.0000.0001.0000.0001.4000.0c81.9030.00 ATM3/1/3 <information deleted> ILMI Switch Prefix(es): 47.0091.8100.0000.0001.0000.0001 ILMI Configured Interface Prefix(es): LECS Address(es):
| Command | Task |
|---|---|
ping 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 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:
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
Use the ping atm command to confirm that the ATM interfaces are configured correctly:
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#
Use the show atm interface command to confirm the atm interfaces are configured correctly:
Switch# show atm interface atm 1/0/0
Interface: ATM1/0/0 Port-type: oc3suni
IF Status: UP Admin Status: up
Auto-config: disabled AutoCfgState: not applicable
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.00e0.4fac.b401.4000.0c80.8000.00
Configured virtual links:
PVCLs SoftVCLs SVCLs TVCLs PVPLs SoftVPLs SVPLs Total-Cfgd Inst-Conns
4 0 0 0 1 0 0 5 3
Logical ports(VP-tunnels): 1
Input cells: 263109 Output cells: 268993
5 minute input rate: 0 bits/sec, 0 cells/sec
5 minute output rate: 1000 bits/sec, 2 cells/sec
Input AAL5 pkts: 171788, Output AAL5 pkts: 174718, AAL5 crc errors: 0
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 PVPs SoftPVPs SVPs Total
P2P 30 0 0 1 1 0 32
P2MP 0 0 0 1 0 0 1
TOTAL INSTALLED CONNECTIONS = 33
PER-INTERFACE STATUS SUMMARY AT 16:07:59 UTC Wed Nov 5 1997:
Interface IF Admin Auto-Cfg ILMI Addr SSCOP Hello
Name Status Status Status Reg State State State
------------- -------- ------------ -------- ------------ --------- --------
ATM1/1/0 DOWN down waiting n/a Idle n/a
ATM1/1/1 DOWN down waiting n/a Idle n/a
ATM1/1/2 DOWN down waiting n/a Idle n/a
ATM1/1/3 DOWN down waiting n/a Idle n/a
ATM0 UP up n/a UpAndNormal Idle n/a
ATM3/0/0 UP up n/a UpAndNormal Active LoopErr
ATM3/0/0.99 UP up waiting WaitDevType Idle n/a
ATM3/0/1 UP up done UpAndNormal Active LoopErr
ATM3/0/2 UP up n/a UpAndNormal Active LoopErr
ATM3/0/3 UP up done UpAndNormal Active LoopErr
ATM3/1/0 UP up done UpAndNormal Active LoopErr
ATM3/1/1 UP up done UpAndNormal Active LoopErr
ATM3/1/2 UP up done UpAndNormal Active LoopErr
ATM3/1/3 UP up done UpAndNormal Active LoopErr
<information deleted>
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 ATM1/1/0 0 5 PVC ATM0 0 52 QSAAL DOWN ATM1/1/0 0 16 PVC ATM0 0 32 ILMI DOWN ATM1/1/1 0 5 PVC ATM0 0 53 QSAAL DOWN ATM1/1/1 0 16 PVC ATM0 0 33 ILMI DOWN ATM1/1/2 0 5 PVC ATM0 0 54 QSAAL DOWN ATM1/1/2 0 16 PVC ATM0 0 34 ILMI DOWN ATM1/1/3 0 5 PVC ATM0 0 55 QSAAL DOWN ATM1/1/3 0 16 PVC ATM0 0 35 ILMI DOWN ATM0 0 32 PVC ATM1/1/0 0 16 ILMI DOWN ATM0 0 33 PVC ATM1/1/1 0 16 ILMI DOWN ATM0 0 34 PVC ATM1/1/2 0 16 ILMI DOWN ATM0 0 35 PVC ATM1/1/3 0 16 ILMI DOWN ATM0 0 36 PVC ATM3/0/0 0 16 ILMI UP ATM0 0 37 PVC ATM3/0/1 0 16 ILMI UP ATM0 0 38 PVC ATM3/0/2 0 16 ILMI UP ATM0 0 39 PVC ATM3/0/3 0 16 ILMI UP ATM0 0 40 PVC ATM3/1/0 0 16 ILMI UP ATM0 0 41 PVC ATM3/1/1 0 16 ILMI UP ATM0 0 42 PVC ATM3/1/2 0 16 ILMI UP ATM0 0 43 PVC ATM3/1/3 0 16 ILMI UP <information deleted>
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 3/0/0
Interface VPI VCI Type X-Interface X-VPI X-VCI Encap Status
ATM3/0/0 0 5 PVC ATM0 0 56 QSAAL UP
ATM3/0/0 0 16 PVC ATM0 0 36 ILMI UP
ATM3/0/0 0 18 PVC ATM0 0 85 PNNI UP
ATM3/0/0 50 100 PVC ATM3/0/1 60 200 DOWN
ATM3/0/2 70 210 UP
ATM3/0/3 80 220 UP
ATM3/0/0 100 200 SoftVC NOT CONNECTED
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.
The following example shows the display output with feature card per-class queuing (FC-PCQ) installed:
Switch# show atm vc interface atm 1/0/0 83 93
Interface: ATM1/0/0, Type: oc3suni VPI = 83 VCI = 93 Status: UP Time-since-last-status-change: 00:00:40 Connection-type: PVC Cast-type: point-to-point Packet-discard-option: disabled Usage-Parameter-Control (UPC): pass Number of OAM-configured connections: 0 OAM-configuration: disabled OAM-states: Not-applicable Cross-connect-interface: ATM3/0/0, Type: oc3suni Cross-connect-VPI = 19 Cross-connect-VCI = 67 Cross-connect-UPC: pass Cross-connect OAM-configuration: disabled Cross-connect OAM-state: Not-applicable Rx cells: 0, Tx cells: 0 Rx connection-traffic-table-index: 1 Rx service-category: UBR (Unspecified Bit Rate) Rx pcr-clp01: 7113539 Rx scr-clp01: none Rx mcr-clp01: none Rx cdvt: 1024 (from default for interface) Rx mbs: none Tx connection-traffic-table-index: 1 Tx service-category: UBR (Unspecified Bit Rate) Tx pcr-clp01: 7113539 Tx scr-clp01: none Tx mcr-clp01: none Tx cdvt: none Tx mbs: none Switch#
The following example shows the display output with the FC-PFQ installed:
Switch# show atm vc interface atm 1/1/0 77 42
Interface: ATM1/1/0, Type: oc3suni VPI = 77 VCI = 42 Status: UP Time-since-last-status-change: 00:27:54 Connection-type: PVC Cast-type: point-to-point Packet-discard-option: disabled Usage-Parameter-Control (UPC): pass Wrr weight: 32 Number of OAM-configured connections: 0 OAM-configuration: disabled OAM-states: Not-applicable Cross-connect-interface: ATM1/0/0, Type: oc3suni Cross-connect-VPI = 100 Cross-connect-VCI = 90 Cross-connect-UPC: pass Cross-connect OAM-configuration: disabled Cross-connect OAM-state: Not-applicable Threshold Group: 5, Cells queued: 0 Rx cells: 0, Tx cells: 0 Tx Clp0:0, Tx Clp1: 0 Rx Clp0:0, Rx Clp1: 0 Rx Upc Violations:0, Rx cell drops:0 Rx Clp0 q full drops:0, Rx Clp1 qthresh drops:0 Rx connection-traffic-table-index: 1 Rx service-category: UBR (Unspecified Bit Rate) Rx pcr-clp01: 7113539 Rx scr-clp01: none Rx mcr-clp01: none Rx cdvt: 1024 (from default for interface) Rx mbs: none Tx connection-traffic-table-index: 1 Tx service-category: UBR (Unspecified Bit Rate) Tx pcr-clp01: 7113539 Tx scr-clp01: none Tx mcr-clp01: none Tx cdvt: none Tx mbs: none Switch#
Use the more system:running-config command to confirm that the configuration being used is configured correctly:
Switch# more system:running-config
! version XX.X no service pad service udp-small-servers service tcp-small-servers ! hostname Switch ! interface CBR0/0/0 no ip address ! <information deleted> ! interface ATM3/0/3 no keepalive ! interface ATM3/1/0 no keepalive ! interface ATM3/1/1 no keepalive ! interface ATM3/1/2 no keepalive ! interface ATM3/1/3 no keepalive ! <information deleted> ! line con 0 line aux 0 monitor line vty 0 4 login ! end Switch#
Use the more nvram:startup-config command to confirm that the configuration saved in NVRAM is configured correctly:
Switch# more nvram:startup-config
Using 2026 out of 129016 bytes ! version XX.X no service pad service udp-small-servers service tcp-small-servers ! hostname Switch ! boot bootldr bootflash:/tftpboot/rbhide/ls1010-wp-mz.XXX-X.X.WA4.X.XX ! ip host-routing ip rcmd rcp-enable ip rcmd rsh-enable ip rcmd remote-username dplatz ip domain-name cisco.com ip name-server 192.168.30.32 atm filter-set tod1 index 4 permit time-of-day 0:0 0:0 atm service-category-limit cbr 64512 atm service-category-limit vbr-rt 64512 atm service-category-limit vbr-nrt 64512 atm service-category-limit abr-ubr 64512 atm qos default cbr max-cell-loss-ratio clp1plus0 12 atm qos default vbr-nrt max-cell-loss-ratio clp1plus0 12 atm address 47.0091.8100.0000.0041.0b0a.1081.0041.0b0a.1081.00 atm address 47.0091.8100.5670.0000.0000.0000.0040.0b0a.1081.00 atm router pnni node 1 level 56 lowest redistribute atm-static ! <information deleted> ! interface ATM0 no ip address no keepalive atm maxvp-number 0 atm pvc 0 any-vci encap aal5snap ! interface Ethernet0 ip address 172.20.40.93 255.255.255.0 ! no ip classless ip route 0.0.0.0 0.0.0.0 172.20.40.201 atm route 47.0091.8100.0000... ATM0/0/0 scope 1 atm route 47.0091.8100.0000.00... ATM0/0/0 e164-address 1234567 ! line con 0 line aux 0 line vty 0 4 login ! end Switch#
|
|