![]() |
ATM Switch Router Command Reference, 12.0(1a)W5(7b)
|
|||||||||||||||||||||||||
R Commands for the ATM Switch
![]() |
||||||||||||||||||||||||||
|
Table of ContentsR Commandsredistribute reprogram resource-poll-interval resume rif rif always-forward rif timeout rif validate-age rif validate-enable rif xid-explorer route-map router rotary rsh R CommandsNote Commands that are identical to those documented in the Cisco IOS software documentation have been removed from this chapter. Refer to Appendix D, "Removed and Changed Commands," of this command reference for a list of removed commands. redistributeTo 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
|
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 Catalyst 8540 MSR Software Configuration Guide.
The following script shows how to access the redistribute PNNI node configuration command.
To upgrade nonvolatile microcode or programmable logic on a selected card from a Flash file, use the reprogram EXEC command.
The motherboard in the given slot is reprogrammed.
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 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 during a reprogram operation because damage can occur to the controller you are reprogramming. If you power-cycle the switch while reprogramming is in progress, you also might be unable to boot the switch after the reprogram is complete. |
The following example shows how to reprogram the image on the route processor in slot 4.
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.
|
Specifies the interval, in seconds, at which the values of the interface metrics and attributes are updated. |
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 Catalyst 8540 MSR Software Configuration Guide.
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.
To switch to another open Telnet, LAT, or PAD session, use the resume EXEC command.
|
The name or number of the connection; the default is the most recent connection. |
|
|
One of the options listed in Table 17-1. |
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 17-1 lists the Telnet and rlogin resume options.
Table 17-1 Telnet and rlogin Resume Options
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.
session-timeout
show sessions
where
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.
|
Series of 4-digit hexadecimal numbers separated by a period (.). This RIF string is inserted into the packets sent to the specified MAC address. |
No static source-route information is entered.
If a Token Ring host does not support the use of IEEE 802.2 TEST or XID datagrams as explorer packets, you may 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 will 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.
The following example shows inserting a RIF cache entry with MAC address 1000.5A12.3456 and RIF 0630.0081.0090.
To specify that RIFs 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.
This command has no keyword or arguments.
RIFs are not stored in the forward direction.
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.
|
Number of minutes an inactive RIF entry is kept in the cache. The valid range is 1 to 120. |
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.
The following example shows changing the timeout to 5 minutes.
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.
This command has no keywords or options.
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.
This command has no keywords or arguments.
A RIF validation algorithm is used for 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.
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.
This command has no keywords or arguments.
The following example configures an RMON alarm using the rmon alarm command.
This example configures RMON alarm number 10. The alarm monitors the MIB variable ifOutErrors.1 once every 20 seconds until the alarm is disabled, and checks the change in the variable's rise or fall. If the ifOutErrors.1 value shows a MIB counter increase of 15 or more, such as from 100000 to 100015, the alarm is triggered. The alarm in turn triggers event number 1, which is configured with the rmon event command. Possible events include a log entry or a SNMP trap.
If the ifOutErrors.1 value changes by 0 (falling-threshold 0), the alarm is reset and can be triggered again.
To execute a command remotely on a remote rsh host, use the rsh privileged EXEC command.
|
IP address of the remote host on which to execute the rsh command. Either the IP address or the host name is required. |
|
|
Name of the remote host on which to execute the command. Either the host name or the IP address is required. |
|
If you do not specify the /user keyword and argument, the switch 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 through Telnet and the user was authenticated through the username command, the switch software sends that username as the remote username. If the TTY username is invalid, the switch software uses the switch 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.
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 provides Telnet and connect services that you can use rather than rsh.
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.