|
|
To enable random early detection on an interface, use the random-detect interface configuration command. To disable random early detection on the interface, use the no form of this command.
random-detect [weighting]
weighting | (Optional) Exponential weighting constant in the range 1 to 16 used to determine the rate that packets are dropped when congestion occurs. The default is 10 (that is, drop 1 packet every 10). |
Disabled
Interface configuration
On high speed networks, random detection is used to avoid congestion by dropping packets at a controlled rate.
Use the default value for the exponential weighting constant; however, you might need to change this value depending on your operational environment. For example, a value of 10 (the default), which might achieve a loss rate of 10-4, is recommended for high-speed links such as DS3 and OC3, whereas a value of 7, which might achieve a loss rate of 10-3; is recommended for T1 links.
Random early detection cannot be configured on an interface already configured with custom, priority, or fair queueing default values.
When RSVP is configured on the interface, packets from other traffic flows are dropped before RSVP flows (when possible). Also, the IP precedence of the packet determines whether the packet is dropped.
Lower-precedence traffic is dropped before higher-precedence traffic.
The following example shows how to enable random early detection on an ASP interface.
Switch(config)# interface 2/0/0
Switch(config-if)# random-detect
custom-queue-list
priority-group
show interface
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 LightStream 1010 ATM Switch 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 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:
1. Accepts the connection.
2. Prints the custom message.
3. Clears the connection.
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 0
Switch(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 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 less frequently the interface resource information. 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 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 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 | (Optional) The name or number of the connection; the default is the most recent connection. |
keyword | (Optional) One of the options listed in Table 16-1. |
Table 16-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. |
1 /noline
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 Issue 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.
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 set an alarm on any MIB object, use the rmon alarm configuration command. Use the no form of this command to disable the alarm.
rmon alarm number variable interval {delta | absolute} rising-threshold value
number | Alarm number, which is identical to the alarmIndex in the alarm Table in the Remote Monitoring (RMON) MIB. |
variable | MIB object to monitor, which translates into the alarmVariable used in the alarmTable of the RMON MIB. |
interval | Time in seconds the alarm monitors the MIB variable, which is identical to the alarmValue used in the alarmTable of the RMON MIB. |
delta | Tests the change between MIB variables, which affects the alarmSampleType in the alarmTable of the RMON MIB. |
absolute | Tests each MIB variable directly, which affects the alarmSampleType in the alarmTable of the RMON MIB. |
rising-threshold value | Value at which the alarm is triggered. |
event-number | (Optional) Event number to trigger when the rising or falling threshold exceeds its limit. This value is identical to the alarmRisingEventIndex or the alarmFallingEventIndex in the alarmTable of the RMON MIB. |
falling-threshold value | Value at which the alarm is reset. |
owner string | (Optional) Specifies an owner for the alarm, which is identical to the alarm owner in the alarmTable of the RMON MIB. |
No alarms configured
Global configuration
To disable the RMON alarms, you must use the no form of the command on each configured alarm. For example, enter no rmon alarm 1, where the 1 identifies which alarm is to be removed.
See RFC 1757 for more information about the RMON alarm group.
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 add or remove an event in the RMON event table that is associated with an RMON event number, use the rmon event global configuration command. Use the no form of this command to disable RMON on the interface.
rmon event number [log] [trap community] [description string] [owner string]
number | Assigned event number, which is identical to the eventIndex in the eventTable in the RMON MIB. |
log | (Optional) Generates an RMON log entry when the event is triggered and sets the eventType in the RMON MIB to log or log-and-trap. |
trap | (Optional) SNMP community string used for this trap. Configures the setting of the eventType in the RMON MIB for this row as either snmp-trap or log-and-trap. This value is identical to the eventCommunityValue in the eventTable in the RMON MIB. |
description | (Optional) Specifies a description of the event, which is identical to the event description in the eventTable of the RMON MIB. |
owner | (Optional) Owner of this event, which is identical to the eventDescription in the eventTable of the RMON MIB. |
No events configured
Global configuration
See RFC 1757 for more information about the RMON MIB.
The following example enables the rmon event command.
Switch# rmon event 1 log trap eventtrap description "High ifOutErrors" owner jhunt
This example configuration creates RMON event number 1, which is defined as High ifOutErrors, and generates a log entry when the event is triggered by an alarm. The user jhunt owns the row that is created in the event table by this command. This configuration also generates a Simple Network Management Protocol (SNMP) trap when the event is triggered.
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 0
Switch(config-line)# rxspeed 2400
|
|