|
|
This chapter discusses specific steps used to initially configure the ATM switch router.
This chapter includes the following sections:
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.
Consider the following information you might need before you configure your ATM switch router:
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 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: 0x600108F8, data-base: 0x605C4000
cisco C8540MSR (R5000) processor with 65536K/256K bytes of memory.
R5000 processor, Implementation 35, Revision 2.1 (512KB Level 2 Cache)
Last reset from power-on
1 Ethernet/IEEE 802.3 interface(s)
8 ATM network interface(s)
507K bytes of non-volatile configuration memory.
16384K 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 router 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 | Purpose |
|---|---|---|
| 1 | --- | Installs the BOOTP server code on the workstation, if it is not already installed. |
| 2 | --- | Determines the MAC address from the label on the chassis. |
| 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. |
| 4 | reload | Restarts the ATM switch router 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 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:
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.
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."
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 | Purpose |
|---|---|---|
| 1 | interface atm card/subcard/port | Selects the physical interface to be configured. |
| 2 | no scrambling cell-payload | Disables cell-payload scrambling. |
| 3 | no scrambling sts-stream | Disables STS-stream scrambling. |
| 4 | Configures 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 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. |
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 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:
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 | Purpose |
|---|---|---|
| 1 | interface ethernet0 | Selects the interface to be configured. |
| 2 | ip address ip-address mask | Configures 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 | Purpose |
|---|---|
Displays the Ethernet interface IP address. | |
more system:running-config | Shows 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>
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:
| Command | Purpose |
|---|---|
ping ip address | Tests 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 router.
This section includes the following:
To configure the network clocking priorities and sources, use the following command in global configuration mode:
| Command | Purpose |
|---|---|
network-clock-select priority {interface-type card/subcard/port | system} [revertive] | Configures the network clock priority. |
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:
| 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. |
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
To configure the network clocking priorities and sources, use the following command in global configuration mode:
| Command | Purpose |
|---|---|
network-clock-select priority {interface-type card/subcard/port | system} [revertive] | Configures the network clock priority. |
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
To configure where each interface receives its transmit clocking, perform the following tasks, beginning in global configuration mode:
| Step | Command | Purpose |
|---|---|---|
| 1 | interface atm card/subcard/port | Selects the interface to be configured. |
| 2 | clock source {free-running | loop-timed | network-derived} | Configures 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 | Purpose |
|---|---|
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. |
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 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 ! version XX.X <information deleted> ! network-clock-select revertive network-clock-select 1 ATM0/0/0 ! <information deleted>
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.
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.
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.
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.
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:
| Command | Purpose |
|---|---|
Enters NCDP 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:
| Command | Purpose |
|---|---|
ncdp max-diameter hops | Specifies the maximum network diameter for the protocol. The default maximum network diameter is 20. |
The following example shows enabling the NCDP and setting the maximum number of hops to 11:
Switch(config)# ncdp max-diameter 11
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:
| Command | Purpose |
|---|---|
ncdp source priority {{atm | cbr} card/subcard/port} | {system}} | Specifies a priority and source (stratum level or system) for this interface. |
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:
| Command | Purpose |
|---|---|
Specifies the NCDP as revertive. |
The following example demonstrates configuring the network clock sources, priorities, and revertive NCDP for the ports on node A in Figure 3-2:
Switch(config)# ncdp source 1 atm 1/0/0 3 Switch(config)# ncdp source 1 atm 3/0/0 3 Switch(config)# ncdp revertive
To display the NCDP configuration, use the following EXEC commands:
| Command | Purpose |
|---|---|
Displays the NCDP clock path from the switch to the root source. | |
Displays NCDP port information. | |
Displays NCDP clock sources configured on the switch. | |
Displays NCDP status. | |
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#
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."
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."
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. |
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 | Purpose |
|---|---|---|
| 1 | clock set hh:mm:ss day month year | Sets the system clock. |
| 2 | configure | Enters global configuration mode from the terminal. |
| 3 | hostname name | Sets 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
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:
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.
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.
You can manually force the secondary route processor to take over as primary. To do so, use the following command in privileged EXEC mode:
| Command | Purpose |
|---|---|
Forces a switchover. |
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:
| Step | Command | Purpose |
|---|---|---|
| 1 | config-register 0x2002 | Sets the config register for autoboot. |
| 2 | end | Returns to privileged EXEC mode. |
| 3 | copy running-config startup-config | Saves the configuration to NVRAM. |
The following example shows how to change the configuration register to 0x2002:
Switch(config)# config-register 0x2002 Switch(config)# end Switch(config)# copy running-config startup-config
To display the configuration register value, use the following privileged EXEC command:
| Command | Purpose |
|---|---|
Displays the configuration register value. |
The following example shows the configuration register value:
Switch# show version Cisco Internetwork Operating System Software IOS (tm) PNNI Software (cat8540m-WP-M), Version XX.X(X)WX(X), RELEASE SOFTWARE Copyright (c) 1986-19XX by cisco Systems, Inc. Compiled Mon XX-XXX-XX 10:15 by integ Image text-base: 0x60010930, data-base: 0x606CE000 ROM: System Bootstrap, Version XX.XXX.X(X)WX(X) [BLD-JAGUAR120-4.0.9 ], E Switch uptime is 3 weeks, 5 days, 23 hours, 30 minutes System restarted by bus error at PC 0x6007EF24, address 0xFC System image file is "bootflash:cat8540m-wp-mz.XXX-X.X.WX.X.XX" cisco C8540MSR (R5000) processor with 65536K/256K bytes of memory. R5000 processor, Implementation 35, Revision X.X (512KB Level 2 Cache) Last reset from power-on 1 Ethernet/IEEE 802.3 interface(s) 9 ATM network interface(s) 507K 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). Secondary is up Secondary has 0K bytes of memory.
Configuration register is 0x100 (will be 0x2002 at next reload)
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:
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:
| Command | Purpose |
|---|---|
redundancy manual-sync {startup-config | running-config | both} | Immediately synchronizes the configuration. |
In the following example, both the startup and running configurations are synchronized immediately:
Switch# redundancy manual-sync both
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:
| Step | Command | Purpose |
|---|---|---|
| 1 | Enters redundancy configuration mode. | |
| 2 | Enters main-cpu configuration submode. | |
| 3 | sync config {startup | running | both}1 | Synchronizes either or both configurations during switchover or writing the files to NVRAM. |
| 4 | end | Returns to privileged EXEC mode. |
| 5 | copy running-config startup-config | Forces a manual synchronization of the configuration files in NVRAM. Note This step is unnecessary to synchronize the running configuration file in DRAM. |
| 1Alternatively, you can force an immediate synchronization by entering the redundancy manual-sync command in privileged EXEC mode. |
In the following example, both the startup and running configurations are synchronized:
Switch(config)# redundancy Switch(config-r)# main-cpu Switch(config-r-mc)# sync config both Switch(config-r-mc)# end Switch# copy running-config startup-config
To display the route processor redundancy configuration, use the following privileged EXEC command:
| Command | Purpose |
|---|---|
Displays the redundancy configuration. |
In the following example the route processor redundancy configuration displays:
Switch# show redundancy Primary ------- Slot: a4/0/0 Uptime: 50 minutes Image: Version XX.X(19980716:020138) 107] Last Running Config. Sync: 50 minutes Last Startup Config. Sync: 50 minutes Last Restart Reason: Normal boot Secondary --------- Slot: a8/0/0 Uptime: 50 minutes Image: Version XX.X(19980716:020138)
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:
| Command | Purpose |
|---|---|
redundancy prepare-for-cpu-removal | Changes the secondary route processor to ROM monitor mode prior to removal. |
The following example, changes the secondary route processor to ROM monitor mode prior to removal:
Switch# redundancy prepare-for-cpu-removal
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.
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:
| Command | Purpose |
|---|---|
Immediately synchronizes the configuration. |
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:
Switch# redundancy preferred-switch-card-slots 5 7 The preferred switch cards selected are already active
To display the preferred switch processor redundancy configuration, use the following privileged EXEC command:
| Command | Purpose |
|---|---|
Displays the redundancy configuration. |
In the following example the preferred switch processor redundancy configuration displays:
Switch# show preferred-switch-card-slots The currently preferred switch card slots are slot: 5 and slot: 7 The currently active switch card slots are slot: 5 and slot: 7
The switch processor EHSA feature is self-configuring. The tasks described in the following sections are therefore optional.
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:
| Step | Command | Task |
|---|---|---|
| 1 | Enter redundancy configuration mode. | |
| 2 | switch-card redundant slot-number | Specify the slot of the redundant switch processor. |
| 3 | end | Exit redundancy configuration mode. |
In the following example the card in slot 7 is designated the redundant switch processor:
Switch(config)# redundancy Switch(config-r)# switch-card redundant 7 Switch(config-r)# exit
To display the switch processor EHSA configuration, use the following privileged EXEC command:
| Command | Purpose |
|---|---|
show capability {primary | secondary} | Displays the switch redundancy configuration. |
The following shows the primary switch processor EHSA configuration:
Switch# show capability primary Dram Size is :64 MB Pmem Size is :4 MB Nvram Size is :512 KB BootFlash Size is :8 MB ACPM hw version 5.2 ACPM functional version 4.0 Netclk Module present flag :16 NCLK hw version 3.1 NCLK func version 8.0 Printing the parameters for Switch card: 0 SWC0 HW version 7.2 SWC0 Functional version 1.2 SWC0 Table memory size: 0 MB SWC0 Feat Card Present Flag: 0 SWC0 Feat Card HW version 0.0 SWC0 Feat Card Functional version 0.0 Printing the parameters for Switch card: 1 SWC1 HW version 0.0 SWC1 Functional version 0.0 SWC1 Table memory size: 0 MB SWC1 Feat Card Present Flag: 0 SWC1 Feat Card HW version 0.0 SWC1 Feat Card Functional version 0.0 Printing the parameters for Switch card: 2 SWC2 HW version 7.2 SWC2 Functional version 1.2 SWC2 Table memory size: 0 MB SWC2 Feat Card Present Flag: 0 SWC2 Feat Card HW version 0.0 SWC2 Feat Card Functional version 0.0 Number of Controller supported in IOS: 7 Driver 0 type: 2560 super cam Functional Version 1.3 Driver 1 type: 2562 OC12 SPAM Functional Version 5.1 Driver 2 type: 2564 OC mother board Functional Version 5.1 Driver 3 type: 258 Switch Card Functional Version 1.0 Driver 4 type: 259 Switch Feature Card Functional Version 4.0
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."
To save the running configuration to NVRAM, use the following command in privileged EXEC mode:
| Command | Purpose |
|---|---|
copy system:running-config nvram:startup-config | Copies 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 show capability commands to confirm the correct hardware installation:
Switch# show hardware C8540 named Switch, Date: 08:36:44 UTC Fri May 21 1999 Slot Ctrlr-Type Part No. Rev Ser No Mfg Date RMA No. Hw Vrs Tst EEP ---- ------------ ---------- -- -------- --------- -------- ------- --- --- 0/* Super Cam 73-2739-02 02 07287xxx Mar 31 98 3.0 0/0 155MM PAM 73-1496-03 06 02180424 Jan 16 96 00-00-00 3.0 0 2 0/1 155MM PAM 73-1496-03 00 02180455 Jan 17 96 00-00-00 3.0 0 2 4/* Route Proc 73-2644-05 A0 03140NXK Apr 04 99 0 5.7 4/0 Netclk Modul 73-2868-03 A0 03140NSU Apr 04 99 0 3.1 5/* Switch Card 73-3315-08 B0 03170SMB May 03 99 0 8.3 5/0 Feature Card 73-3408-04 B0 03160S4H May 03 99 0 4.1 7/* Switch Card 73-3315-08 B0 03160SDT May 03 99 0 8.3 7/0 Feature Card 73-3408-04 B0 03160RQV May 03 99 0 4.1 8/* Route Proc 73-2644-05 A0 03140NXH Apr 04 99 0 5.7 8/0 Netclk Modul 73-2868-03 A0 03140NVT Apr 04 99 0 3.1 DS1201 Backplane EEPROM: Model Ver. Serial MAC-Address MAC-Size RMA RMA-Number MFG-Date ------ ---- -------- ------------ -------- --- ---------- ----------- C8540 2 6315484 00902156D800 1024 0 0 Mar 23 1999 cubi version : F Power Supply: Slot Part No. Rev Serial No. RMA No. Hw Vrs Power Consumption ---- ---------------- ---- ----------- ----------- ------- ----------------- 0 34-0829-02 A000 APQ0225000R 00-00-00-00 1.0 2746 cA
See "Display the Switch Processor EHSA Configuration (Catalyst 8540 MSR)" for an example of the show capability command.
Use the show hardware 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 (cat8540m-WP-M), Version XX.X(X), RELEASE SOFTWARE Copyright (c) 1986-1998 by cisco Systems, Inc. Compiled XXX XX-XXX-XX XX:XX by Image text-base: 0x600108B4, data-base: 0x6057A000 ROM: System Bootstrap, Version XX.X(X) RELEASE SOFTWARE Switch uptime is 1 hour, 1 minute System restarted by reload System image file is "tftp://cat8540m-wp-mz_nimmu" cisco C8540MSR (R5000) processor with 65536K/256K bytes of memory. R5000 processor, Implementation 35, Revision 2.1 (512KB Level 2 Cache) Last reset from power-on 1 Ethernet/IEEE 802.3 interface(s) 8 ATM network interface(s) 507K bytes of non-volatile configuration memory. 16384K bytes of Flash PCMCIA card at slot 0 (Sector size 128K). 8192K bytes of Flash internal SIMM (Sector size 256K). Configuration register is 0x0
Use the show diag power-on command to confirm the power-on diagnostics:
Switch# show diag power-on
Cat8540 Power-on Diagnostics Status (.=Pass,F=Fail,U=Unknown,N=Not Applicable)
-----------------------------------------------------------------------------
Last Power-on Diags Date: 97/11/05 Time: 11:03:41 By: V 3.2
BOOTFLASH: . PCMCIA-Slot0: N PCMCIA-Slot1: N
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: .
switch processor feature card
Access: .
RST: . REG: . IVC: . IFILL: . OVC: . OFILL: .
TEST:
CELL: . SNAKE: . RATE: . MCAST: . SCHED: .
TGRP: . UPC : . ABR : . RSTQ : .
Access/Interrupt/Loopback/CPU-MCast/Port-MCast/FC-MCast/FC-TMCC Test Status:
Ports 0 1 2 3
----------------------------------------------------------------------------
PAM 0/0 (155UTP) .....NN .....NN .....NN .....NN
PAM 1/0 (155MM) .....NN .....NN .....NN .....NN
PAM 1/1 (622) .....NN N N N
PAM 3/0 (622MM) .....NN N N N
PAM 3/1 (DS3Q) .....NN .....NN .....NN .....NN
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 route 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 router:
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 | Purpose |
|---|---|
ping ip address | Tests 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.
Switch# show atm vc int atm 0/0/0 0 16 Interface: ATM0/0/0, Type: oc3suni VPI = 0 VCI = 16 Status: DOWN Time-since-last-status-change: 1w5d Connection-type: PVC Cast-type: point-to-point Packet-discard-option: enabled Usage-Parameter-Control (UPC): pass Wrr weight: 15 Number of OAM-configured connections: 0 OAM-configuration: disabled OAM-states: Not-applicable Cross-connect-interface: ATM0, Type: Unknown Cross-connect-VPI = 0 Cross-connect-VCI = 35 Cross-connect-UPC: pass Cross-connect OAM-configuration: disabled Cross-connect OAM-state: Not-applicable Encapsulation: AAL5ILMI Threshold Group: 6, Cells queued: 0 Rx cells: 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 pkts:0, Rx pkt drops:0 Rx connection-traffic-table-index: 3 Rx service-category: VBR-RT (Realtime Variable Bit Rate) Rx pcr-clp01: 424 Rx scr-clp01: 424 Rx mcr-clp01: none Rx cdvt: 1024 (from default for interface) Rx mbs: 50 Tx connection-traffic-table-index: 3 Tx service-category: VBR-RT (Realtime Variable Bit Rate) Tx pcr-clp01: 424 Tx scr-clp01: 424 Tx mcr-clp01: none Tx cdvt: none Tx mbs: 50
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 no service password-encryption ! hostname Switch ! <information deleted> ! interface Ethernet0 ip address 172.20.52.11 255.255.255.224 no ip directed-broadcast ! interface ATM-E0 no ip address no ip directed-broadcast atm pvc 0 29 pd on wrr-weight 15 rx-cttr 3 tx-cttr 3 interface ATM0 0 any-vci wrr-weight 15 encap ! interface Async1 no ip address no ip directed-broadcast hold-queue 10 in ! logging buffered 4096 debugging ! line con 0 exec-timeout 0 0 transport input none line vty 0 4 exec-timeout 0 0 no login ! end
Use the more nvram:startup-config command to confirm that the configuration saved in NVRAM is configured correctly:
Switch# more nvram:startup-config version XX.X no service pad no service password-encryption ! hostname Switch ! <information deleted> ! interface Ethernet0 ip address 172.20.52.11 255.255.255.224 no ip directed-broadcast ! interface ATM-E0 no ip address no ip directed-broadcast ! interface Async1 no ip address no ip directed-broadcast hold-queue 10 in ! logging buffered 4096 debugging ! line con 0 exec-timeout 0 0 transport input none line vty 0 4 exec-timeout 0 0 no login ! end
Posted: Thu Mar 23 11:11:40 PST 2000
Copyright 1989 - 2000©Cisco Systems Inc.