|
|
The commands shown in this chapter apply to the Catalyst 8540 MSR, Catalyst 8510 MSR, and LightStream 1010 ATM switch routers. Where an entire command or certain attributes of a command have values specific to a particular switch or switch router, an exception is indicated by the following callouts:
Refer to Appendix D of this command reference for a detailed list of commands that have been removed, changed or replaced.
To instruct the PNNI to redistribute static routes throughout the PNNI routing domain, use the redistribute PNNI node configuration command. To disable redistribution of static routes, use the
no form of this command.
Syntax Description
Defaults
Command Modes
Command History
Usage Guidelines
All redistributed routes are advertised in exterior reachable address PTSE with default scope and without metric. All redistributed routes are summarized by the summary-address command.
In autoconfiguration mode, PNNI is set to redistribute the configured static routes.
For more information, refer to the ATM Switch Router Software Configuration Guide.
Examples
The following script shows how to access the redistribute PNNI node configuration command.
Related Commands
|
To switch to the redundancy mode, use the redundancy global configuration command.
Syntax Description
This command has no arguments or keywords.
Command Modes
Command History
Usage Guidelines
To enter the main-cpu mode of redundancy mode, use the main-cpu command.
Examples
The following example shows how to enter the redundancy mode.
The following example shows how to switch to the main-cpu submode of redundancy mode.
Related Commands
To force the primary route processor to allow the secondary route processor to take over and become the primary, use the redundancy force-failover main-cpu EXEC command.
Syntax Description
This command has no arguments or keywords.
Command Modes
Command History
Usage Guidelines
If the secondary route processor is in ROMMON mode, it becomes the primary route processor but continues in the ROMMON mode, meaning that the IOS software does not automatically open.
The force-failover main-cpu command causes the main processor functions of the switch to change
to the secondary route processor, if one is installed. If the command is executed when only one route processor is installed, the force-failover main-cpu command is ignored and an error message indicating this condition appears.
 |
Caution Any unsaved configuration and all the SVC connections in the former primary route processor are lost after the failover is complete. Only PVC connections are preserved during failover. |
If the new primary route processor does not have the same configuration as the previous primary route processor, functionality provided by the additional resources in the former primary route processor is lost after the failover. For example, if the new primary route processor does not have a network clock module installed and the old primary did, network clock functionality will not be available after the switchover.
Examples
The following example shows how to make the secondary route processor the primary.
Related Commands
 |
Note The show redundancy command is available on the primary route processor only. |
To manually update the configuration on the secondary processor to be identical with the configuration on the primary processor, use the redundancy manual-sync EXEC command. Use this command to update the startup configuration, the running configuration, or both.
Syntax Description
|
Command Modes
Command History
Usage Guidelines
Normally this command is not required because whenever you exit configuration mode (either using cntrl-Z or end), the running configuration is updated on the secondary processor. Similarly, the startup configuration is updated whenever you issue the write memory command. Use the redundancy manual-sync (Catalyst 8540 MSR) command if you see an error and want to manually force a configuration update.
Examples
The following example shows how to update the secondary processor with the startup configuration on the primary processor.
Related Commands
|
Note The show redundancy command is available on the primary route processor only. |
If the switch has three switch cards, then by default the switch cards in slots 5 and 7 are the active switch cards and the one in slot 6 is the standby switch card. To change the active switch slots, use the redundancy preferred-switch-card-slot EXEC command.
Syntax Description
Defaults
Slots 5 and 7 are the active slots. Slot 6 is the standby slot.
Command Modes
Command History
Usage Guidelines
Two unique preferred slots must be specified. If one of the preferred slots selected is not a currently active switch card, you are asked if the system should change the active switch cards to the preferred switch cards. If such a switchover occurs, all the active connections in the system are reinitialized. If you wish to continue, then the preferred switch cards become active and the other switch card becomes the standby. This configuration remains in effect until one of the active switch cards is removed. The preferred switch card configuration is preserved across route processor switchovers but not when the system is power cycled or when both route processors are reloaded to ROM monitor mode.
Examples
The following example shows how to change the preferred active slots to slots 5 and 6.
Related Commands
|
Note The show redundancy command is available on the primary route processor only. |
Prior to removing a route processor from the chassis, precautions must be taken. To be sure that a switch router running IOS is in the proper state, use the redundancy prepare-for-cpu-removal EXEC command.
Syntax Description
This command has no arguments or keywords.
Defaults
Command Modes
Command History
Usage Guidelines
It is safest to have the route processor module in RMON monitor mode before removing it from the chassis. If the switch is running IOS, you can accomplish this using the reload command unless the switch is configured to automatically boot IOS again. To ensure that the route processor is in RMON monitor mode, use the redundancy prepare-for-cpu-removal (Catalyst 8540 MSR). After issuing this command the route processor will go to ROM monitor mode and stay there even if the system is configured to automatically boot IOS. At this point it is safe to remove the route processor module from the chassis.
|
Note Be sure to issue the redundancy prepare-for-cpu-removal (Catalyst 8540 MSR) command after connecting to the console port of the route processor module to be removed. If the system has a Y cable, then the Y cable must be removed and a local connection to the route processor being removed must be obtained before issuing the command. Always issue the redundancy prepare-for-cpu-removal (Catalyst 8540 MSR) command on a route processor that is in IOS mode, even if it is the secondary route processor. |
Examples
The following example shows how to prepare a route processor for removal by putting it into ROM monitor mode.
Related Commands
|
Note The show redundancy command is available on the primary route processor only. |
To upgrade nonvolatile microcode or programmable logic on a selected card from a flash file, use the reprogram EXEC command.
Syntax Description
|
Defaults
The systemboard in the given slot is reprogrammed.
Command Modes
Command History
Usage Guidelines
This command causes nonvolatile change to the controller you select. It also resets the selected controller, which causes active connections and configurations to be lost.
If you reprogram a currently-running controller or switch card, power-cycle the switch router after the reprogram completes to make the newly downloaded image active. If you do not perform a power-cycle, the controller continues to run the older image. For secondary controllers or port adapters, you need not perform a power-cycle.
|
Caution Do not power-cycle the switch router during a reprogram operation because damage can occur to the controller you are reprogramming. If you power-cycle the switch router while reprogramming is in progress, you also might be unable to boot the switch router after the reprogram is complete. |
Examples
The following example shows how to reprogram the image on the route processor in slot 3.
Related Commands
|
To configure the period of time that PNNI polls resource management to update the values of the interface metrics and attributes, use the resource-poll-interval ATM router PNNI configuration command. To return to the default value, use the no form of this command.
Syntax Description
|
Defaults
Command Modes
Command History
Usage Guidelines
The maximum allowable poll interval is 300 seconds. Using this value impacts the number of self-generated PTSEs created by the switch. A larger resource-poll-interval can generate a smaller number of PTSE updates, as PNNI polls the interface resource information less frequently. A large resource-poll-interval is desirable when reducing the number of self-generated PTSEs caused by interface traffic fluctuation.
Lowering the default allows PNNI to poll the resource manager (for resource information) at a higher frequency. This allows PNNI to track resource information faster, but it costs more in processing time and should be adjusted only when needed.
For more information, refer to the ATM Switch Router Software Configuration Guide.
Examples
The following example shows how to change the period of time the interface metrics and attributes are updated using the resource-poll-interval ATM router PNNI configuration command.
Related Commands
|
To switch to another open Telnet, LAT, or PAD session, use the resume EXEC command.
Syntax Description
|
Defaults
Command Modes
Command History
Usage Guidelines
Several concurrent sessions can be open and you can switch back and forth between them. The number of sessions that can be open is defined by the sessions command.
You can switch between sessions by escaping one session and resuming a previously opened session, as follows:
Step 2 Enter the where command to list the open sessions. All open sessions associated with the current terminal line are displayed.
Step 3 Enter the resume command and the session number to make the connection.
You also can resume the previous session by pressing the Return key.
The Ctrl^x, where, and resume commands are available with all supported connection protocols.
Table 16-1 lists the Telnet and rlogin resume options.
Table 16-1 Telnet and rlogin resume options
|
Examples
The following example shows how to escape out of a connection and to resume connection 2.
You can omit the command name and simply enter the connection number to resume that connection. The following example illustrates how to resume connection 3.
Related Commands
To enter static source-route information into the routing information field (RIF) cache, use the rif global configuration command. To remove an entry from the cache, use the no form of this command.
Syntax Description
|
Defaults
No static source-route information is entered.
Command Modes
Command History
Usage Guidelines
If a Token Ring host does not support the use of IEEE 802.2 TEST or XID datagrams as explorer packets, you might need to add static information to the RIF cache.
Using the command rif mac-address without any other arguments puts an entry into the RIF cache indicating that packets for this MAC address do not have RIF information.
Do not configure a static RIF with any of the all rings type codes. Doing so causes traffic for the configured host to appear on more than one ring and leads to unnecessary congestion.
Examples
The following example shows inserting a RIF cache entry with MAC address 1000.5A12.3456 and RIF 0630.0081.0090.
Related Commands
To specify that RIFs must always be stored in the forward direction, use the rif always-forward global configuration command. To disable forward-direction storing of RIFs, use the no form of this command.
Syntax Description
This command has no keyword or arguments.
Defaults
RIFs are not stored in the forward direction.
Command Modes
Command History
Related Commands
|
To specify the number of minutes an inactive entry is kept in the RIF cache, use the rif timeout
global configuration command. To restore the default time, use the no form of this command.
Syntax Description
Defaults
Command Modes
Command History
Usage Guidelines
A RIF entry is refreshed only if a RIF field of an incoming frame is identical to the RIF information of the RIF entry in the cache.
Until a RIF entry is removed from the cache, no new information is accepted for that RIF entry.
Examples
The following example shows changing the timeout to 5 minutes.
Related Commands
|
To permit invalidated and aged-out entries to be removed from the RIF cache, use the
rif validate-age global configuration command. To disable this feature, use the no form of this command.
Syntax Description
This command has no keywords or options.
Defaults
Command Modes
Command History
Related Commands
|
To enable RIF validation for entries learned on an interface, use the rif validate-enable global configuration command. To disable the specification, use the no form of this command.
Syntax Description
This command has no keywords or arguments.
Defaults
Command Modes
Command History
Usage Guidelines
A RIF validation algorithm is used in the following cases:
A directed IEEE TEST command is sent to the destination MAC address. If a response is received in the time specified by rif validate-time, the entry is refreshed and is considered valid. Otherwise, the entry is removed from the cache. To prevent sending too many TEST commands, any entry that has been refreshed in less than 70 seconds is considered valid.
Validation is triggered when any of the follows occurs:
|
Note If the RIF entry has been in the RIF cache for six hours, and has not been refreshed for the time specified in the rif timeout command, the entry is removed from the cache. |
|
Note This command has no effect on remote entries learned over RSRB. |
Related Commands
To send IEEE XID explorer packets instead of TEST commands to learn RIF information, use the rif xid-explorer global configuration command. To disable this specification, use the no form of this command.
Syntax Description
This command has no keywords or arguments.
Defaults
Command Modes
Command History
Related Commands
|
To execute a command remotely on a remote rsh host, use the rsh privileged EXEC command.
Syntax Description
|
Defaults
If you do not specify the /user keyword and argument, the switch router sends a default remote username. As the default value of the remote username, the switch software sends the username associated with the current TTY process if that name is valid. For example, if the user is connected to the switch router through Telnet and the user was authenticated through the username command, the switch router software sends that username as the remote username. If the TTY username is invalid, the switch router software uses the switch router host name as both the remote and local usernames.
|
Note TTYs are commonly used in Cisco communications servers. The concept of TTY originated with UNIX. For UNIX systems, each physical device is represented in the file system. Terminals are called TTY devices, which stands for teletype, the original UNIX terminal. |
Command Modes
Command History
Usage Guidelines
Use the rsh command to execute commands remotely. The host on which you remotely execute the command must support the rsh protocol, and the .rhosts files on the rsh host must include an entry that permits you to remotely execute commands on that host.
For security reasons, the switch software does not default to a remote login if no command is specified. Instead, the switch router provides Telnet and connect services that you can use rather than rsh.
Examples
The following command specifies that user rusty attempts to remotely execute the UNIX ls command with the -a argument on the remote host mysys.cisco.com. The command output resulting from the remote execution follows the command example.
To set the terminal baud rate receive (from terminal) speed, use the rxspeed line configuration command. To set the baud rate to the default, use the no form of this command.
Syntax Description
Defaults
Command Modes
Command History
Usage Guidelines
This command pertains to the auxiliary port only. Set the speed to match the baud rate of any device you connect to the port. Some baud rates available on devices connected to the port might not be supported on the switch. The switch indicates if the speed you select is not supported.
The following is a list of supported baud rates:
75, 110, 134, 150, 300, 600, 1200, 1800, 2000, 2400, 4800, 9600, 19200, 38400
Examples
The following example sets the auxiliary line receive rate to 2400 bps.
Related Commands
Posted: Tue Aug 12 17:30:34 PDT 2003
All contents are Copyright © 1992--2003 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.