|
|
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.
redistribute protocol
protocol | The protocol keyword used for static routes is atm-static. |
Enabled for atm-static.
PNNI node configuration
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.
Switch# configure terminal Switch(config)# atm router pnni Switch(config-atm-router)# node 1 Switch(config-pnni-node)# redistribute atm-static
To upgrade nonvolatile microcode or programmable logic on a selected card from a Flash file, use the reprogram EXEC command.
reprogram flash-file-name [slot | rommon] subcard
flash-file-name | Name of the image to download, which can be in the PCMCIA flash or bootflash. |
slot | Physical slot number of the controller you want to reprogram. |
rommon | If you select rommon, the rommon of the route processor ATM switch router on which the command is invoked is reprogrammed with the image in the given file. |
subcard | Can indicate a subcard in a slot for half-width cards or daughter cards in full width cards. If you do not specify a subcard number, the motherboard in the given slot is reprogrammed. |
The motherboard in the given slot is reprogrammed.
EXEC
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.
Switch# reprogram cpu_3_10.exo 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.
resource-poll-interval seconds
seconds | Specifies the interval, in seconds, at which the values of the interface metrics and attributes are updated. |
5 seconds
ATM router PNNI configuration
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.
Switch# configure terminal Switch(config)# atm router pnni Switch(config-atm-router)# resource-poll-interval 30
To switch to another open Telnet, LAT, or PAD session, use the resume EXEC command.
resume [connection] [keyword]
connection | The name or number of the connection; the default is the most recent connection. |
keyword | One of the options listed in Table 17-1. |
/noline1
EXEC
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 1 Escape out of the current session by pressing the escape sequence (Ctrl^ then x [Ctrl^x] by default) and return to the EXEC prompt.
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.
| Option | Description |
|---|---|
/debug | Displays parameter changes and messages. In the Cisco IOS software, this option displays informational messages whenever the remote host changes an X.3 parameter, or sends an X.29 control packet. |
/echo | Performs local echo. |
/line | Enables line-mode editing. |
/nodebug | Cancels printing of parameter changes and messages. |
/noecho | Disables local echo. |
/noline1 | Disables line mode and enables character-at-a-time mode, which is the default. |
/nostream | Disables stream processing. |
/set parameter:value | Sets X.3 connection options. |
/stream | Enables stream processing. |
The following example shows how to escape out of a connection and to resume connection 2.
Swift% ^^X Switch> resume 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.
Switch> 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.
rif mac-addr [rif-string]
mac-addr | MAC address of the RIF entry. |
rif-string | 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.
Global configuration
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.
Switch(config)# rif 1000.5A12.3456 0630.0081.0090
multiring
show rif
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.
rif always-forwardThis command has no keyword or arguments.
RIFs are not stored in the forward direction.
Global configuration
rif
show rif
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.
rif timeout minutes
minutes | Number of minutes an inactive RIF entry is kept in the cache. The valid range is 1 to 120. |
15 minutes
Global configuration
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.
Switch(config)# rif timeout 5
clear rif-cache
rif
show rif
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.
rif validate-ageThis command has no keywords or options.
Aged entries are removed.
Global configuration
rif
rif timeout
show rif
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.
rif validate-enableThis command has no keywords or arguments.
RIF validation is enabled.
Global configuration
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:
rif timeout
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.
rif xid-explorerThis command has no keywords or arguments.
TEST commands are sent.
Global configuration
rif
show rif
The following example configures an RMON alarm using the rmon alarm command.
Switch# rmon alarm 10 ifOutErrors.1 20 delta rising-threshold 15 1 falling-threshold 0 owner jhunt
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.
rsh {ip-address | host} [/user username] line
ip-address | IP address of the remote host on which to execute the rsh command. Either the IP address or the host name is required. |
host | Name of the remote host on which to execute the command. Either the host name or the IP address is required. |
username | Remote username. |
line | Required parameter to be executed remotely. |
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.
Privileged EXEC
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.
Switch1# rsh mysys.cisco.com /user rusty ls -a . .. .alias .cshrc .emacs .exrc .history .login .mailrc .newsrc .oldnewsrc .rhosts .twmrc .xsession jazz
Posted: Thu Sep 2 10:32:05 PDT 1999
Copyright 1989-1999©Cisco Systems Inc.