|
|
To instruct the PNNI to redistribute static routes throughout the PNNI routing domain, use the redistribute node-level subcommand. To reset disable redistribution of static routes, use the no form of this command.
redistribute protocol| protocol | This keyword is used for static routes. |
Enabled.
ATM router PNNI node-level 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 LightStream 1010 ATM Switch Software Configuration Guide.
The following script shows how to access the redistribute node-level subcommand.
Switch#configure terminalSwitch(config)#atm router pnniSwitch(config-atm-router)#node 1Switch(config-pnni-node)#redistribute atm-static
To define a line-in-use message, use the refuse-message line configuration command. Use the no form of this command to disable the message.
refuse-message d message d| d | Delimiting character of your choice--a pound sign (#), for example. You cannot use the delimiting character in the message. |
| message | Message text. |
No line-in-use message is defined.
Line configuration.
Follow the command with one or more blank spaces and a delimiting character of your choice. Then enter one or more lines of text, terminating the message with the second occurrence of the delimiting character. You cannot use the delimiting character within the text of the message.
When you define a message using this command, the switch performs the following tasks:
In the following example, line 0 is configured with a lines-in-use message, and the user is instructed to try again later.
Switch(config)#line aux 0Switch(config-line)#refuse-message/The dial-out modem is currently in use. Please try again later./
To reload the operating system, use the reload privileged EXEC command.
reloadThis command has no arguments or keywords.
Privileged EXEC.
The reload command halts the system. If the system is set to restart on error, it reboots itself. Use the reload command after configuration information is entered into a file and saved to the startup configuration.
You cannot reload from a virtual terminal if the system is not set up for automatic booting. This prevents the system from dropping to the ROM monitor and thereby taking the system out of the remote user's control.
If you modify your configuration file, the system prompts you to save the configuration. During a save operation, the system asks you if you want to proceed with the save if the config_file environment variable points to a startup configuration file that no longer exists. If you enter "yes" in this situation, the system saves the running configuration to startup configuration.
The following example illustrates how to enter the reload command at the privileged EXEC prompt.
Switch# reload
copy running-config
copy startup-config
To configure the period of time that PNNI polls resource management to update the values of the interface metrics and attributes, use the rm-poll-interval ATM router PNNI configuration command. To return to the default value, use the no form of this command.
rm-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 rm-poll-interval can generate a smaller number of PTSE updates causing slower creation time to changes in the RM interface status. A large rm-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 LightStream 1010 ATM Switch Software Configuration Guide.
The following example shows how to change the period of time the interface metrics and attributes are updated using the rm-poll-interval ATM router PNNI configuration command.
Switch#configure terminalSwitch(config)#atm router pnniSwitch(config-atm-router)#rm-poll-interval 30
To define a group of lines consisting of one of more virtual terminal lines or one auxiliary port line, use the rotary line configuration command. Use the no form of this command to remove a line or group of lines from a rotary group.
rotary group| group | Integer between 1 and 100 you choose to identify the rotary group. |
No rotary groups are defined.
Line configuration.
Typically, rotary groups are used on devices with multiple modem connections to allow connections to the next free line in a hunt group. Rotary groups are still useful for defining groups of virtual terminal lines or for defining a rotary group consisting of the single auxiliary port on switches that have only one modem line (the auxiliary port). Putting the auxiliary port in a rotary group is useful because the auxiliary port is not necessarily the same line on all hardware; by putting it in a rotary group, you do not have to track the line number.
Connections to a rotary group can take advantage of the following features:
The remote host must specify a particular TCP port on the switch to connect to a rotary group that has connections to an individual line. The available services are the same, but the TCP port numbers are different. Table 15-1 lists the services and port numbers for both rotary groups and individual lines.
For example, if Telnet protocols are required, the remote host connects to the TCP port numbered 3000 (decimal) plus the rotary group number. If the rotary group identifier is 13, the corresponding TCP port is 3013.
| Services Provided | Base TCP Port for Rotaries | Base TCP Port for Individual Lines |
|---|---|---|
| Telnet Protocol | 3000 | 2000 |
| Raw TCP protocol (no Telnet protocol) | 5000 | 4000 |
| Telnet protocol, binary mode | 7000 | 6000 |
The following example establishes a rotary group consisting of virtual terminal lines 2 through 4 and defines a password on those lines. By using Telnet to connect to TCP port 3001, the user gets the next free line in the rotary group. The user does not have to remember the range of line numbers associated with the password.
Switch(config)#line vty 2 4Switch(config-line)#rotary 1Switch(config-line)#password letmeinSwitch(config-line)#login
modem callout
modem cts-required
session-timeout
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. |
| /user username | (Optional) 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
To set the terminal baud rate receive (from terminal) speed, use the rxspeed line configuration command.
rxspeed bps| bps | Baud rate in bits per second (bps); see the Usage Guidelines below for settings. |
9600 bps.
Line configuration.
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
The following example sets the auxiliary line receive rate to 2400 bps.
Switch(config)#line aux 0Switch(config-line)#rxspeed 2400
|
|