|
|
To guarantee CPU time for processes, use the scheduler allocate global configuration command. The no form of this command restores the default.
scheduler allocate interrupt-time process-time| interrupt-time | Integer (in microseconds) that limits the maximum number of microseconds to spend on fast switching within any one network interrupt context. The range is 400 to 60000 microseconds. The default is 4000 microseconds. |
| process-time | Integer (in microseconds) that guarantees the minimum number of microseconds to spend at the process level when network interrupts are disabled. The range is 100 to 4000. The default is 200 microseconds. |
Approximately 5 percent of the CPU is available for process tasks.
Global configuration
The normal operation of the network server allows the switching operations to use as much of the central processor as is required. If the network is running unusually heavy loads that do not allow the processor the time to handle the routing protocols, give priority to the system process scheduler. Use the scheduler allocate command to guarantee processor time.
The following example makes 20 percent of the CPU available for process tasks.
Switch(config)# scheduler allocate 2000 500
To specify the mapping from a range of organizational scope values (used at UNI interfaces) to a PNNI scope value (such as, in terms of PNNI routing level indicators), use the scope map PNNI node-level subcommand. To set to default a range of organizational scope values, use the no form of this command.
scope map low-org-scope [high-org-scope] level level_indicator| low-org-scope | Specifies the low end of the range of organizational scope values. The valid range of organizational scope values is from local (1) to global (15). |
| high-org-scope | Specifies the high end of the range of organizational scope values. The valid range of organizational scope values is from local (1) to global (15). If no value is specified, then the range includes only one entry (for example, high-org-scope equals low-org-scope). |
| level_indicator | Specifies the PNNI scope value to which the range of organizational scope values is mapped. The range is from 0 to 104. |
The default values are specified in the ATM Forum PNNI 1.0 Specification and are as follows:
org-scope range equals ATM Forum default level
1-3 96
4-5 80
6-7 72
8-10 64
11-12 48
13-14 32
15 global 0
PNNI node configuration
The scope map command is used to change the values of specific entries. This command is only accepted when the scope mode is set to manual.
When the organizational scope of a registered address maps to a PNNI level that is lower in the PNNI hierarchy (larger PNNI routing level) than the level of this node, the registered address is not advertised. Similarly, when the connection scope of a setup attempt maps to a PNNI level that is lower in the PNNI hierarchy than the level of this node, then only destinations directly attached to this switch are considered acceptable.
The LightSteam 1010 ATM switch provides an option to automatically adjust the level changes. In automatic mode, the default scope map table is tied to the level of the node when it is generated.
Note that the default organizational scope of an individual address is global (15), and the default organizational scope of a group address is local (1).
The following example shows setting the scope mode to manual and setting the scope map entries for organizational scope values 1 through 5 to PNNI level 96, using the scope map PNNI node-level subcommand.
Switch#configure terminalSwitch(config)#atm router pnniSwitch(config-atm-router)#node 1Switch(config-pnni-node)#scope mode manualSwitch(config-pnni-node)#scope map 1 5 level 96
To specify the configuration mode of the mapping from organizational scope values (used at UNI interfaces) to PNNI scope (such as, in terms of PNNI routing level indicators), use the scope mode node-level subcommand.
scope mode {automatic | manual}| automatic | Generates a default scope-map table automatically which is tied to the PNNI level of the node. In this mode, no modifications of the scope-map table entries are allowed. |
| manual | Allows for manual configuration of the scope mapping table using the scope map command. |
automatic as follows:
org scope range ATM Forum default level automatic mode level
1-3 96 min(l,96)
4-5 80 min(l,80)
6-7 72 min(l,72)
8-10 64 min(l,64)
11-12 48 min(l,48)
13-14 32 min(l,32)
15(global) 0 0
PNNI node configuration
Use this command to modify the way in which the default scope map table is computed.
Using the automatic mode ensures that all organizational scope values cover an area at least as wide as this node's peer group, even when the node is at a level higher than 96. As a result, all addresses including those of local scope are advertised across this node's peer group.
For each organizational scope value, the corresponding PNNI level is the minimum of the ATM Forum PNNI 1.0 default value and the level l of this node.
Note that the scope mapping table is overwritten whenever the scope-mode is changed from manual to automatic (for example, all scope map commands for this node are removed).
The following example shows setting the scope mode to manual using the scope mode PNNI node-level subcommand.
Switch#configure terminalSwitch(config)#atm router pnniSwitch(config-atm-router)#node 1Switch(config-pnni-node)#scope mode manual
To allow scrambling to be enabled or disabled from the current port, use the scrambling interface configuration command.
scrambling scramblingmode
no scrambling scramblingmode
| scramblingmode | Specify either sts-stream or cell-payload |
In SONET interfaces, both modes are enabled.
In DS3 interfaces, the mode is disabled.
Interface configuration
The sts-stream scrambling is applicable to only SONET interfaces.
The following example shows how to disable sts-stream and cell-payload scrambling on the physical device associated with card 3, subcard 0, and port 0.
Switch#interface atm 3/0/0Switch#no scrambling cell-payloadSwitch#no scrambling sts-stream
To specify that a chat script start on a line any time the line is activated, use the script activation line configuration command. Use the no form of this command to disable this feature.
script activation regexp| regexp | Regular expression specifying the set of modem scripts that might be executed. The first script name that matches the argument regexp is used. |
Disabled
Line configuration
This command provides an asynchronous handshake to a user or device that activates the line. It can be used only on the auxiliary port of the switch. The line can be activated by events such as the following: a user issuing a carriage return on a vacant line, a modem on the line sensing an incoming carrier, or an asynchronous device (such as a communication server) sending data. Each time an EXEC session is started on a line, the system checks to see if a script activation command is configured on the line. If so, and the argument regexp (a regular expression) matches an existing chat script name, the matched script is run on the line.
The script activation command can mimic a login handshake of another system. For example, a system that dials into the auxiliary port on a switch and expects an IBM mainframe login handshake can be satisfied with an appropriate activation script.
This command can also send strings to asynchronous devices that are connecting or dialing into a communication server.
The script activation command functions only on physical terminal lines (tty). It does not function on virtual terminal (vty) lines.
The following example specifies that the chat script with a name that includes telebit is activated whenever line 0 is activated.
Switch(config-line)#line aux 0Switch(config-line)#script activation telebit
chat-script
dir
script connection
script reset
script startup
start-chat
To specify that a chat script start on a line any time a remote network connection is made to a line, use the script connection line configuration command. Use the no form of this command to disable this feature.
script connection regexp| regexp | Specifies the set of modem scripts that might be executed. The first script name that matches the argument regexp is used. |
Disabled
Line configuration
This command provides modem dialing commands and commands for logging on to remote systems. The script connection command functions only on physical terminal (tty) lines. It does not function on virtual terminal (vty) lines.
This command can be used to initialize an asynchronous device sitting on a line to which a reverse network connection is made. This command can only be used on the auxiliary port of the switch.
The following example specifies that the chat script with a name that includes inband is activated whenever a remote connection to line 0 is established. The switch can send a login string and password to the UNIX server when a network tunneling connection comes into line 0, the auxiliary port.
Switch(config-line)#line aux 0Switch(config-line)#script connection inband
chat-script
dir
script activation
script reset
script startup
start-chat
To specify that a chat script start on a line any time the specified line is reset, use the script reset line configuration command. Use the no form of this command to disable this feature.
script reset regexp| regexp | Regular expression specifying the set of modem scripts that might be executed. The first script name that matches the argument regexp is used. |
Disabled
Line configuration
Chat scripts provide modem dialing commands and commands for logging on to remote systems. Use this command to reset a modem attached to a line every time a call is dropped.
The script reset command functions only on physical terminal lines (tty). It does not function on virtual terminal (vty) lines. This command can only be used on the auxiliary port of the switch.
This example specifies that any chat script name with the word linebackup in it is activated any time line 0 is reset.
Switch(config-line)#line aux 0Switch(config-line)#script reset linebackup
chat-script
dir
script activation
script connection
script startup
start-chat
To specify that a chat script start on a line any time the switch is turned on, use the script startup line configuration command. Use the no form of this command to disable this feature.
script startup regexp| regexp | Regular expression specifying the set of modem scripts that might be executed. The first script name that matches the argument regexp is used. |
Disabled
Line configuration
Use this command to initialize asynchronous devices connected to a line when the switch is turned on or reloaded. You can also use it to start up a banner other than the default banner on lines. The script startup command functions only on physical terminal (tty) lines. It does not function on virtual terminal (vty) lines. This command can only be used on the auxiliary port of the switch.
The following example specifies the startup chat script as linestart.
Switch(config-line)#line 0Switch(config-line)#script startup linestart
chat-script
dir
script activation
script connection
script reset
start-chat
To send a message to other TTY lines, use the send privileged EXEC command.
send {aux | console | vty | *}| aux | Auxiliary line number. |
| console | Primary terminal line. |
| vty | Virtual terminal. |
| * | Message is sent to all lines. |
Privileged EXEC
You use this command to inform users of an impending shut-down on the switch. The system prompts you for a message, which can be up to 500 characters long. Enter ^Z to end the message or stop the command.
To compress configuration files, use the service compress-config global configuration command. To disable compression, use the no form of this command.
service compress-configThis command has no arguments or keywords.
Global configuration
To enable autoloading of configuration files from a network server, use the service config global configuration command. Use the no form of this command to restore the default.
service configThis command has no arguments or keywords.
Disabled
Global configuration
Usually, the service config command is used in conjunction with the boot host or boot network command. You must enter the service config command to enable the switch to automatically configure the system from the file specified by the boot host command.
The service config command can also be used without the boot host command. If you do not specify host or network configuration filenames, the switch uses the default configuration files. The default network configuration file is network-config. The default host configuration file is host-config, where host is the host name of the switch. If the switch cannot resolve its host name, the default host configuration file is switch-config.
In the following example, the switch is configured to autoload the default host configuration file.
Switch(config)#boot hostSwitch(config)#service config
To delay the startup of the EXEC on noisy lines, use the service exec-wait global configuration command. Use the no form of this command to disable this feature.
service exec-waitThis command has no arguments or keywords.
Disabled
Global configuration
This command delays startup of the EXEC until the line has been idle (no traffic seen) for 3 seconds. The default is to enable the line immediately on modem activation.
This command is useful on noisy modem lines or when a modem attached to the line is configured to ignore MNP or V.42 negotiations and MNP or V.42 modems may be dialing in. In these cases, noise or MNP/V.42 packets may be interpreted as usernames and passwords, causing authentication failure before the user gets a chance to enter a username and password. The command is not useful on nonmodem lines or lines without a login configured.
The following example delays the startup of the EXEC.
Switch(config)# service exec-wait
To allow Finger protocol requests (defined in RFC 742) to be made of the network server, use the service finger global configuration command. This service is equivalent to issuing a remote show users command. The no form of this command removes this service.
service fingerThis command has no arguments or keywords.
Enabled
Global configuration
The following is an example of how to disable the Finger protocol.
Switch(config)# no service finger
To configure the switch to display line number information after the EXEC or incoming banner, use the service linenumber global configuration command. To disable this function, use the no form of this command.
service linenumberThis command has no arguments or keywords.
Disabled
Global configuration
With the service linenumber command, the switch can display the host name, line number, and location each time an EXEC is started or an incoming connection is made. The line number banner appears immediately after the EXEC banner or incoming banner. It is useful for tracking problems with modems because the host and line for the modem connection are listed. Modem type information can also be included.
The following example illustrates the type of line number information that can appear after the EXEC banner.
Switch(config)# user1 location1%telnet switch2 2001
Trying 131.109.44.37
Connected to user1-gw.cisco.com
Escape character is '^]'.
switch1 line 1 virtual terminal 0
To enable the Nagle congestion control algorithm, use the service nagle global configuration command. Use the no form of this command to disable this feature.
service nagleThis command has no arguments or keywords.
Disabled
Global configuration
When using a standard TCP implementation to send keystrokes between machines, TCP tends to send one packet for each keystroke typed. On larger networks, many small packets use up bandwidth and contribute to congestion.
John Nagle's algorithm (RFC 896) helps alleviate the small-packet problem in TCP. In general, it works this way:
The effect is to accumulate characters into larger chunks, and pace them out to the network at a rate matching the round-trip time of the given connection. This method is usually good for all TCP-based traffic. However, do not use the service nagle command if you have XRemote users on X Window sessions.
The following example enables the nagle algorithm on the switch.
Switch(config)# service nagle
To encrypt passwords, use the service password-encryption global configuration command. Use the no form of this command to disable this service.
service password-encryptionThis command has no arguments or keywords.
No encryption
Global configuration
The actual encryption process occurs when the current configuration is written or when a password is configured. Password encryption can be applied to both the privileged command password and to console and virtual terminal line access passwords.
When password encryption is enabled, the encrypted form of the passwords is displayed when a show startup-config command is entered.
The following example causes password encryption to take place.
Switch(config)# service password-encryption
To generate keepalive packets on idle network connections, use the service tcp-keepalives global configuration command. The no form of this command with the appropriate keyword disables the keepalives.
service tcp-keepalives-{in | out}| in | Generates keepalives on incoming connections (initiated by remote host). |
| out | Generates keepalives on outgoing connections (initiated by a user). |
Disabled
Global configuration
The following example generates keepalives on incoming TCP connections.
Switch(config)#service tcp-keepalives-in
To set the TCP window to zero (0) when the Telnet connection is idle, use the service telnet-zeroidle global configuration command. Use the no form of this command to disable this feature.
service telnet-zeroidleThis command has no arguments or keywords.
Disabled
Global configuration
Normally, data sent to noncurrent Telnet connections is accepted and discarded. When service telnet-zero-idle is enabled, if a session is suspended (that is, some other connection is made active or the EXEC is sitting in command mode), the TCP window is set to zero. This action prevents the remote host from sending any more data until the connection is resumed. Use this command when it is important that all messages sent by the host be seen by the users and the users are likely to use multiple sessions.
Do not use this command if your host eventually times out and logs out a TCP user whose window is zero.
The following example sets the TCP window to zero when the Telnet connection is idle.
Switch# service telnet-zeroidle
To configure the system to timestamp debugging or logging messages, use one of the service timestamps global configuration commands. Use the no form of this command to disable this service.
service timestamps [type uptime]type | Type of message to timestamp: debug or log. |
|---|---|
| uptime | (Optional) Timestamp with time since the system was rebooted. |
| datetime | Timestamp with the date and time. |
| msec | (Optional) Include milliseconds in the date and timestamp. |
| localtime | (Optional) Timestamp relative to the local time zone. |
| show-timezone | (Optional) Include the time zone name in the timestamp. |
No timestamping.
If service timestamps is specified with no arguments or keywords, default is service timestamps debug uptime.
The default for service timestamps type datetime is to format the time in UTC, with no milliseconds and no time zone name.
The command no service timestamps by itself disables timestamps for both debug and log messages.
Global configuration
Timestamps can be added to either debugging or logging messages independently. The uptime form of the command adds timestamps in the format hh:mm:ss, indicating the time since the system was rebooted. The datetime form of the command adds timestamps in the format mm dd hh:mm:ss, indicating the date and time according to the system clock. If the system clock has not been set, the date and time are preceded by an asterisk (*) to indicate the date and time are not correct.
The following example enables timestamps on debugging messages, showing the time since reboot.
Switch(config)# service timestamps debug uptime
The following example enables timestamps on logging messages, showing the current time and date relative to the local time zone, with the time zone name included.
Switch(config)# service timestamps log datetime localtime show-timezone
clock set
debug ports
ntp clock-period
To set the interval for closing the connection when there is no input or output traffic, use the session-timeout line configuration command. The no form of this command removes the timeout definition.
session-timeout minutes [output]| minutes | Specifies the time interval in minutes. |
| output | (Optional) Specifies the connection is retained when traffic is sent to an asynchronous line from the switch (within the specified interval). |
The default interval is zero, indicating the switch maintains the connection indefinitely.
Line configuration
This command sets the interval that the switch waits for traffic before closing the connection to a remote computer and returning the terminal to an idle state. If the keyword output is not specified, the session timeout interval is based solely on detected input from the user. You can specify a session timeout on each port.
The following example sets an interval of 20 minutes and specifies that the timeout is subject to traffic detected from the user (input only).
Switch(config-line)#line aux 0Switch(config-line)#session-timeout 20
To disable an interface, use the shutdown interface configuration command. To restart a disabled interface, use the no form of this command.
shutdownThis command has no arguments or keywords.
Enabled
Interface configuration
The shutdown command disables all functions on the specified interface.When the ATM interfaces shut down a loss of signal is transmitted to the far-end.
This command also marks the interface as unavailable. To check whether an interface is disabled, use the EXEC command show interfaces. An interface that has been shut down is shown as administratively down in the display from this command.
The following example turns off the Ethernet interface 2/0/0.
Switch#interface ethernet 2/0/0Switch(config-if)#shutdown
The following example turns the interface on.
Switch# interface ethernet 2/0/0
Switch(config-if)# no shutdown
Use the slip EXEC command to attach or detach a Serial-line IP (SLIP) interface.
slipThis command has no keywords or arguments.
EXEC
To create or update an access policy, use the snmp-server access-policy global configuration command. To remove the specified access policy, use the no form of this command.
snmp-server access-policy destination-party source-party context privileges| destination-party | Name of a previously defined party identified as the destination party or target for this access policy. This name serves as a label used to reference a record defined for this party through the snmp-server party command. |
| source-party | Name of a previously defined party identified as the source party or subject for this access policy. This name serves as a label used to reference a record defined for this party through the snmp-server party command. |
| context | Name of a previously defined context that defines the resources for the access policy. This name serves as a label used to reference a record defined for this context through the snmp-server context command. |
| privileges | Bit mask representing the access privileges that govern the management operations that the source party can ask the destination party to perform. |
Global configuration
An access policy defines the management operations the destination party can perform in relation to resources defined by the specified context when requested by the source party. A destination party performs management operations that are requested by a source party. A source party sends communications to a destination party requesting the destination party to perform management operations. A context identifies object resources accessible to a party.
Access policies are defined on the switch for communications from the manager to the agent; in this case, the agent is the destination party and the manager is the source party. Access policies can also be defined on the switch for Response message and trap message communication from the agent to the manager; in this case, the manager is the destination party and the agent is the source party.
The privileges argument specifies the types of SNMP operations that are allowed between the two parties. There are seven types of SNMP operations.You specify the privileges as a bit mask representing the access privileges that govern the management operations that the source party can ask the destination party to perform. In other words, the bit mask identifies the commands that the source party can send to the destination party.
You use decimal or hexadecimal format to specify privileges as a sum of values in which each value specifies an SNMP PDU type that the source party can use to request an operation. The decimal values are defined as follows:
To remove an access-policy entry, all three arguments specified as command arguments must match exactly the values of the entry to be deleted. A difference of one value constitutes a different access policy.
The first snmp-server command you enter enables both versions of SNMP.
The following example configures an access policy providing the manager with read-only access to the agent.
Switch# snmp-server access-policy agt1 mgr1 ctx1 0x23
The following example configures an access policy providing the manager with read-write access to the agent.
Switch# snmp-server access-policy agt2 mgr2 ctx2 43
The following example configures an access policy that allows responses and SNMP v.2 traps to be sent from the agent to a management station.
Switch# snmp-server access-policy mgr1 agt1 ctx1 132
The following example removes the access policy configured for the destination party named agt1, the source party named mgr1, and with a context named ctx1.
Switch(config)# no snmp-server access-policy agt1 mgr1 ctx1
snmp-server context
snmp-server party
To set up the community access string to permit access to the SNMPv1 protocol, use the snmp-server community global configuration command. The no form of this command removes the specified community string.
snmp-server community string [ro | rw] [number]| string | Community string that acts like a password and permits access to the SNMP protocol. |
| ro | (Optional) Specifies read-only access. Authorized management stations are only able to retrieve MIB objects. |
| rw | (Optional) Specifies read-write access. Authorized management stations are able to both retrieve and modify MIB objects. |
| number | (Optional) Integer from 1 to 99 that specifies an access list of IP addresses that are allowed to use the community string to gain access to the SNMP v1 agent. |
By default, an SNMP community string permits read-only access.
Global configuration
For the previous version of this command, the string argument was optional. The string argument is now required. However, to prevent errors and provide backward-compatibility, if the string option is omitted, a default value of public is assumed.
The no snmp-server command disables both versions of SNMP (SNMPv1 and SNMPv2).
The first snmp-server command that you enter enables both versions of SNMP.
The following example assigns the string comaccess to SNMPv1, allowing read-only access and specifying that IP access list 4 can use the community string.
Switch(config)# snmp-server community comaccess ro 4
The following example disables both versions of SNMP.
Switch(config)# no snmp-server
To set the system contact (syscontact) string, use the snmp-server contact global configuration command. Use the no form of this command to remove the system contact information.
snmp-server contact text| text | String that describes the system contact information. |
No syscontact string is set.
Global configuration
The following is an example of a syscontact string.
Switch(config)# snmp-server contact Dial System Operator at beeper # 27345
To create or update a context record, use the snmp-server context global configuration command. To remove a specific context entry, use the no form of this command.
snmp-server context context-name context-oid view-name| context-name | Name of the context to be created or updated. This name serves as a label used to reference a record for this context. |
| context-oid | Object identifier to assign to the context. Specify this value in dotted decimal notation, with an optional text identifier; for example, 1.3.6.1.6.3.3.1.4.131.108.45.11.1 (== initialContextId.131.108.45.11.1). |
| view-name | Name of a previously defined view. The view defines the objects available to the context. |
Global configuration
A context record identifies object resources accessible to a party. A context record is one of the components that make up an access policy. Therefore, you must configure a context record before you can create an access policy that includes the context. Context records and party records further codify MIB views.
To remove a context entry, specify only the name of the context. The name identifies the context to be deleted.
The first snmp-server command that you enter enables both versions of SNMP.
The following example shows how to create a context that includes all objects in the MIB-II subtree using a previously defined view named mib2.
Switch(config)# snmp-server context mycontext initialContextid.131.108.24.56.3 mib2
copy running-config
show running-config
snmp-server view
To enable the router to send SNMP traps, use the snmp-server enable global configuration command. To disable SNMP and stop sending traps, use the no form of this command.
snmp-server enable traps [trap-type] [trap-option]| traps | Enables all traps. |
| trap-type | (Optional) Type of trap to enable. If no type is specified, all traps are sent (including envmon and repeater). It can be one of the following values:
· atm-accounting--Enable SNMP ATM Accounting traps · chassis-change--Enable SNMP Chassis Change Trap · chassis-fail--Enable SNMP Chassis Fail Trap · config--Enable SNMP config traps · snmp--Enable SNMP traps |
| trap-option | (Optional) When envmon is used, you can enable a specific environmental trap type, or accept all trap types from the environmental monitor system. If no option is specified, all environmental types are enabled. It can be one or more of the following values: voltage, shutdown, supply, fan, and temperature.
When repeater is used, you can specify the repeater option. If no option is specified, all repeater types are enabled. It can be one or more of the following values: · health---enable IETF Repeater Hub MIB (RFC 1516) health trap. · reset---enable IETF Repeater Hub MIB (RFC 1516) reset trap. |
No traps are enabled.
If you enter this command with no keywords, the default is to enable all trap types.
Global configuration
Use the snmp-server enable command to specify which SNMP traps the switch sends, and use the snmp-server host command to specify which host or hosts receive SNMP traps.
You must issue a separate snmp-server enable command for each trap type, including envmon and repeater.
The following example enables the switch to send ATM accounting traps.
Switch(config)# snmp-server enable trap atm accounting
snmp-server host
snmp-server trap-source
To specify the recipient of an SNMP trap operation or Inform information, use the snmp-server host global configuration command. The no form of this command removes the specified host.
snmp-server host host community-string [chassis-change] [chassis-failure] [config] [snmp]| host | Name or Internet address of the host. |
| community-string | Password-like community string to send with the trap operation. |
| trap-type | Optional) Type of trap to be sent to the trap receiver host. If no type is specified, all traps are sent. It can be one or more of the following values:
· config--Send configuration traps. · dspu--Send downstream physical unit (DSPU) traps. · envmon--Send Cisco enterprise-specific environmental monitor traps when an environmental threshold is exceeded. · frame-relay--Send Frame Relay traps. · isdn--Send ISDN traps. · llc2--Send Logical Link Control, type 2 (LLC2) traps. · rptr--Send standard repeater (hub) traps · rsrb--Send remote source route bridging (RSRB) traps. · sdlc--Send Synchronous Data Link Control (SDLC) traps. · sdllc--Send SDLLC traps. · snmp--Send SNMP traps defined in RFC 1157. · stun--Send serial tunnel (STUN) traps. · tty--Send Cisco enterprise-specific traps when a TCP connection closes. |
| chassis-change | (Optional) Enables the chassis changes. |
| chassis-failure | (Optional) Enables the chassis failures. |
| config | (Optional) Enables the config traps. |
| snmp | (Optional) Enables the SNMP traps defined in RFC 1157. |
| tty | (Optional) Enables Cisco enterprise-specific traps when a TCP connection closes. |
No traps are sent.
If you enter the command with no keywords, the default is to enable all trap types.
Global configuration
The snmp-server host command specifies which host or hosts should receive SNMP traps. You need to issue the snmp-server host command once for each host acting as a trap recipient. When multiple snmp-server host commands are given, the community string in the last command is used, and in general, the trap types set in the last command are used for all SNMP trap operations.
Whether a trap-type option is available depends on the LightStream software features supported
The following example sends the SNMP traps defined in RFC 1157 to the host specified by the name cisco.com. The community string is defined as the string comaccess.
Switch(config)# snmp-server host cisco.com comaccess snmp
The following example sends the SNMP and Cisco enterprise-specific traps to address 131.108.2.160.
Switch(config)# snmp-server host 131.108.2.160
snmp-server trap-source
snmp-server trap-timeout
To set the system location string, use the snmp-server location global configuration command. Use the no form of this command to remove the location string.
snmp-server location text| text | String that describes the system location information. |
No system location string is set.
Global configuration
The following example illustrates a system location string.
Switch(config)# snmp-server location Building 3/Room 214
To establish control over the largest SNMP packet size permitted when the SNMP server is receiving a request or generating a reply, use the snmp-server packetsize global configuration command. Use the no form of this command to restore the default value.
snmp-server packetsize byte-count| byte-count | Integer byte count from 484 to 8192. |
484 bytes
Global configuration
The following example establishes a packet filtering of a maximum size of 1024 bytes.
Switch(config)# snmp-server packetsize 1024
To create or update a party record, use the snmp-server party global configuration command. To remove a specific party entry, use the no form of this command.
snmp-server party party-name party-oid [authentication {md5 key [snmpv1 string]}] [local || party-name | Name of the party characterized by the contents of the record. This name serves as a label used to reference the party record that you are creating or modifying. |
| party-oid | Object identifier to assign to the party. Specify this value in dotted decimal notation, with an optional text identifier; for example, 1.3.6.1.6.3.3.1.3.131.108.34.54.1 (= initialPartyId.131.108.34.54.1) |
| authentication | (Optional) Indicates that the party uses an authentication protocol. If specified, either md5 or snmpv1 is required. |
| md5 key | (Optional) Indicates that the party uses the Message Digest algorithm md5 for message authentication. If md5 is specified, you must also specify a 16-byte hexadecimal ASCII string representing the MD5 authentication key for the party. All messages sent to this party are authenticated using the snmpv1 md5 authentication method with the key specified by key. |
| snmpv1 string | (Optional) Community string. The keyword snmpv1 indicates that the party uses community-based authentication. All messages sent to this party are authenticated using the snmpv1 community string specified by string instead of md5. |
| local | remote | (Optional) Indicates that the party is local or remote. If neither local nor remote is specified, a default value of local is assumed. |
| packetsize size | (Optional) Maximum size in bytes of a message that this party is able to receive. By default, the packet size set through the snmp-server packetsize command is used (484-65507). |
| udp protocol-address | (Optional) Address of the protocol that the party record pertains to. Currently the only supported protocol is UDP, so this value specifies a UDP address in the format a.b.c.d port.
This value is used to specify the destination of trap messages. |
If neither local nor remote is specified to indicate the location of the party, the party is assumed to be local.
If you do not specify a packet size, the packet size set through the snmp-server packetsize command is used.
Global configuration
You define parties to identify managers and agents. An SNMPv2 party identity is unique; it includes the logical network location of the party, characterized by the transport protocol domain and transport addressing information, and, optionally, an authentication method and its arguments. The authentication protocol reliably identifies the origin of all messages sent by the party. The authentication protocol also ensures the integrity of the messages; in other words, it ensures that the message received is the message that was sent.
Specifying md5 as the authentication method implies that this party record pertains to an SNMPv2 party.
Specifying snmpv1 as the authentication method implies that this party record pertains to an SNMPv1 party. This allows a management station that supports only SNMPv1 to use SNMPv2 MIB views. Instead of using the snmp-server community command, you can use the snmp-server party command with the snmpv1 keyword to define an SNMPv1 party to be used to communicate with an SNMPv1 management station. The snmp-server community command does not allow you to create MIB views for an SNMPv1 management station.
If authentication is not specified, the party record pertains to an SNMPv2 party, and no authentication is performed for messages sent to this party.
To remove a party record, specify only the name of the party. The name identifies the party to be deleted.
The first snmp-server command that you enter enables both versions of SNMP.
The following example configures a remote unauthenticated party.
Switch(config)# snmp-server party mgr1 initialPartyId.131.108.45.32.3 udp 131.108.45.76 162
The following example configures a local MD5-authenticated party with a large maximum packet size. You enter this command as a single line.
Switch(config)# snmp-server party agt1 initialPartyId.131.108.45.32.4 packetsize 1500 local authentication md5 23de457623900ac3ef568fcb236589 lifetime 400
The following example configures an SNMPv1 proxy party for the community public.
Switch(config)# snmp-server party proxyv1 initialPartyId.131.108.45.32.100 authentication snmpv1 public
The following example removes the party named mgr1.
Switch(config)# no snmp-server party mgr1
copy running-config
show running-config
snmp-server community
snmp-server packetsize
To establish the message queue length for each trap host, use the snmp-server queue-length global configuration command.
snmp-server queue-length length| length | Integer that specifies the number of trap events that can be held before the queue must be emptied. |
10 events
Global configuration
This command defines the length of the message queue for each trap host. Once a trap message is successfully transmitted, software continues to empty the queue, but never faster than at a rate of four trap messages per second.
The following example establishes a message queue that traps four events before it must be emptied.
Switch(config)# snmp-server queue-length 4
To use the SNMP message reload feature, the device configuration must include the snmp-server system-shutdown global configuration command. The no form of this command prevents an SNMP system-shutdown request (from an SNMP manager) from resetting the Cisco agent.
snmp-server system-shutdownThis command has no arguments or keywords.
This command is not included in the configuration file.
Global configuration
The following example illustrates how to include the SNMP message reload feature in the device configuration.
Switch(config)# snmp-server system-shutdown
To limit the number of TFTP servers used via SNMP, use the snmp-server tftp-server-list global configuration command. To disable this feature, use the no form of this command.
snmp-server tftp-server-list number| number | Sets the number of IP standard access lists from 1 to 99. |
Disabled
Global configuration
Before using this command, use the snmp-server enable global configuration command.
The following example shows limiting the number of TFTP servers to 44.
Switch(config)# snmp-server tftp-server-list 44
To establish trap message authentication, use the snmp-server trap-authentication global configuration command. To remove message authentication, use the no form of this command.
snmp-server trap-authentication [snmpv1 | snmpv2]| snmpv1 | (Optional) Indicates that SNMP authentication traps are sent to SNMPv1 management stations only. |
| snmpv2 | (Optional) Indicates that SNMP authentication traps are sent to SNMPv2 management stations only. |
Specifying the snmp-server trap-authentication command without a keyword turns on trap message authentication. In this case, messages are sent to the host that is specified through the snmp-server host command and to any SNMP stations configured through access policies to receive trap messages.
Global configuration
Specify the snmpv1 or snmpv2 keyword to indicate the type of management stations to send the trap messages to.
This command enables the switch as an agent to send a trap message when it receives an SNMPv1 packet with an incorrect community string or an SNMPv2 packet with an incorrect MD5 authentication key.
The SNMP specification requires that a trap message be generated for each packet with an incorrect community string or authentication key; however, because this action can result in a security breach, the switch (as an agent) by default does not send a trap message when it receives an incorrect community string or authentication key.
The community string or key is checked before any access list that may be set, so it is possible to get spurious trap messages. In other words, if you issued an snmp-server community command with a specified access list, you might receive messages that come from someone not on the access list; in this case, an authentication trap is issued. The only workarounds are to disable trap authentication or to configure an access list on a switch between the SNMP agent and the SNMP manager to prevent packets from getting to the SNMP agent.
To turn off all message authentication traps, use the no snmp-server trap-authentication without a keyword. To turn off message authentication traps only for SNMPv1 stations or only for SNMPv2 stations, give the negative form of the command with the appropriate keyword.
The first snmp-server command that you enter enables both versions of SNMP.
The following example illustrates how to enter the command that establishes trap message authentication.
Switch(config)# snmp-server trap-authentication
To specify the interface (and hence the corresponding IP address) that an SNMP trap should originate from, use the snmp-server trap-source global configuration command. Use the no form of the command to remove the source designation.
snmp-server trap-source interface| interface | Interface from which the SNMP trap originates. The argument includes the interface type and number in platform-specific syntax. |
No interface is specified.
Global configuration
When an SNMP trap is sent from a Cisco SNMP server, it displays the trap address of the interface it left at the time of the request. Use this command if you want to use the trap address to trace specified needs.
The following example specifies that the IP address for interface Ethernet 2/0/0 is the source for all traps on the switch.
Switch(config)# snmp-server trap-source ethernet 2/0/0
To define how often to try resending trap messages on the retransmission queue, use the snmp-server trap-timeout global configuration command.
snmp-server trap-timeout seconds| seconds | Integer that sets the interval, in seconds, for resending the messages. |
30 seconds
Global configuration
Before the switch tries to send a trap, it looks for a route to the destination address. If there is no known route, the trap is saved in a retransmission queue. The server trap-timeout command determines the number of seconds between retransmission attempts.
The following example sets an interval of 20 seconds to try resending trap messages on the retransmission queue.
Switch(config)# snmp-server trap-timeout 20
To create or update a view entry, use the snmp-server view global configuration command. To remove the specified SNMP server view entry, use the no form of this command.
snmp-server view view-name mib-tree {included | excluded}| view-name | Label for the view record that you are updating or creating. The name is used to reference the record. |
| mib-tree | Object identifier of the ASN.1 subtree to be included or excluded from the view. To identify the subtree, specify a text string consisting of numbers, such as 1.3.6.2.4, or a word, such as system. Replace a single subidentifier with the asterisk (*) wildcard to specify a subtree family; for example, 1.3.*.4. |
| included | excluded | Type of view. You must specify either included or excluded. |
Global configuration
Other SNMPv2 commands require a view as an argument. You use this command to create a view to be used as arguments for other commands that create records including a view.
Two standard predefined views can be used when a view is required, instead of defining a view. One is everything, which indicates that the user can see all objects. The other is restricted, which indicates that the user can see three groups: system, snmpStats, and snmpParties. The predefined views are described in RFC 1447.
The first snmp-server command that you enter enables both versions of SNMP.
The following example creates a view that includes all objects in the MIB-II subtree.
Switch(config)# snmp-server view mib2 mib-2 included
The following example creates a view that includes all objects in the MIB-II system group and all objects in the Cisco enterprise MIB.
Switch(config)#snmp-server phred system includedSwitch(config)#snmp-server view phred cisco included
The following example creates a view that includes all objects in the MIB-II system group except for sysServices (System 7) and all objects for interface 1 in the MIB-II interfaces group.
Switch(config)#snmp-server view agon system includedSwitch(config)#snmp-server view agon system.7 excludedSwitch(config)#snmp-server view agon ifEntry.*.1 included
copy running-config startup-config
show running-config
snmp-server context
snmp-server view
To set the mode of operation and thus control type of ATM cell used for cell-rate decoupling on the SONET, use the sonet interface configuration command. The no form of this command restores the default sts3c operation (applies to only OC3 and OC12 interfaces).
sonet [stm-1 | sts-3c]| stm-1 | SDH/STM-1 operation (ITU-T specification).1 |
| stm-4 | SDH/STM-4 operation (ITU-T specification). |
The default for OC3 is sts3c.
The default for OC12 is sts12c.
Interface configuration
This command applies to all ports except the CPU. Use stm-1 in applications where the ATM switch requires "idle cells" for rate adaptation. An idle cell contains 31 zeros followed by a 1.
Use the default (sts3c) in applications where the ATM switch requires "unassigned cells" for rate adaptation. An unassigned cell contains 32 zeros.
The following example specifies ATM SONET STM-1.
Switch(config-if)# atm sonet stm-1
show controllers
show running-config
write terminal
To configure the number of data bits per character for special characters such as software flow control characters and escape characters, use the special-character-bits line configuration command.
special-character-bits {7 | 8}| 7 | Selects the 7-bit ASCII character set. |
| 8 | Selects the full 8-bit character set for special characters. |
7
Line configuration
Setting the special character bits to 8 allows you to use twice as many special characters as with the 7-bit ASCII character set. The special characters affected by this setting are the escape, hold, stop, start, disconnect, and activation characters.
The following example allows the full 8-bit international character set for special characters on the auxiliary port.
Switch(config)#line aux 0Switch(config-line)#special-character-bits 8
default-value exec-character-bits
default-value special-character-bits
exec-character-bits
terminal exec-character-bits
terminal special-character-bits
To set the terminal baud rate, use the speed line configuration command. The command sets both the transmit (to terminal) and receive (from terminal) speeds.
speed bps| bps | Baud rate in bits per second (bps); see 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 whatever device you connected 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 speeds, in bits per second, are available.
75, 110, 134, 150, 300, 600, 1200, 1800, 2000, 2400, 4800, 9600, 19200, 38400
The following example sets the auxiliary line to 2400 bps.
Switch(config)#line aux 0Switch(config-line)#speed 2400
To permanently delete Flash files, use the squeeze privileged EXEC command.
squeeze device:| device: | Flash device from which to permanently delete files. The colon (:) is required. Valid devices are as follows:
· bootflash: This device is the internal Flash memory. · slot0: This device is the first PCMCIA slot on the ASP card. · slot1: This device is the second PCMCIA slot on the ASP card. |
Privileged EXEC
When Flash memory is full, you might need to rearrange the files so that the space used by the "deleted" files can be reclaimed. When you issue the squeeze command, the switch copies all valid files to the beginning of Flash memory and erases all files marked "deleted." At this point, you cannot recover "deleted" files, and you can write to the reclaimed Flash memory space.
The following example instructs the switch to permanently erase the files marked deleted from the Flash memory card inserted in the second slot of the ASP card.
Switch# squeeze slot1:
To change the connection control timer, use the sscop cc-timer interface configuration command. To restore the default value, use the no form of this command.
sscop cc-timer seconds| seconds | Number of seconds between Begin messages. |
10 seconds
Interface configuration
The connection control timer determines the time between transmission of BGN (establishment), END (release), or RS (resynchronization) protocol data units (PDUs) as long as an acknowledgment is not received.
In the following example, the connection control timer is set to 15 seconds.
Switch(config-if)# sscop cc-timer 15
To set the time SSCOP is idle, use the sscop idle-timer interface configuration command. To restore the timer to the default, use the no form of this command.
sscop idle-timer msecs| msecs | Specifies the number of seconds between Poll PDU messages. |
10 seconds
Interface configuration
The sscop idle-timer command determines the time between two consecutive polls at idle phase.
This is a UNI 3.1 protocol defined timer and does not affect UNI 3.0 protocol.
The following example shows setting the idle timer to 15.
Switch(config-if)# sscop idle-timer 15
To change the keepalive timer, use the sscop keepalive-timer interface configuration command. The no form of this command restores the default value.
sscop keepalive-timer seconds| seconds | Number of seconds the router waits between transmission of POLL PDUs when no sequential data (SD) or SDP PDUs are queued for transmission or are outstanding pending acknowledgments. |
30 seconds
Interface configuration
In the following example, the keepalive timer is set to 15 seconds.
Switch(config-if)# sscop keepalive-timer 15
To change the retry count of connection control, use the sscop max-cc interface configuration command. The no form of this command restores the default value.
sscop max-cc retries| retries | Number of times that SSCOP retries to transmit BGN (establishment), END (release), or RS (resynchronization) PDUs as long as an acknowledgment is not received. Valid range is 1 to 6000. |
10 retries
Interface configuration
In the following example, the retry count of the connection control is set to 20.
Switch(config-if)# sscop max-cc 20
To set the amount of time the SSCOP does not respond, use the sscop noresponse-timer interface configuration command. To restore the timer to the default, use the no form of this command.
sscop noresponse-timer secs| secs | Specifies the number of seconds which no response is required. |
30 seconds
Interface configuration
The no response -timer command determines the maximum time a poll can be outstanding without at least one STAT PDU response.
The following example shows setting the timer to 15.
Switch(config-if)# sscop noresponse-timer 15
sscop keepalive-timer
sscop poll-timer
To change the poll timer, use the sscop poll-timer interface configuration command. The no form of this command restores the default value.
sscop poll-timer seconds| seconds | Number of seconds the switch waits between transmission of POLL PDUs. |
10 seconds
Interface configuration
The poll timer controls the maximum time between transmission of POLL PDUs when SD or SDP PDUs are queued for transmission or are outstanding pending acknowledgments.
In the following example, the poll timer is set to 15 seconds.
Switch(config-if)# sscop poll-timer 15
To change the receiver window, use the sscop receive-window interface configuration command. The no form of this command restores the default value.
sscop receive-window packets| packets | Number of packets the interface can receive before it must send an acknowledgment to the ATM switch. Valid range is 1 to 6000. |
7 packets
Interface configuration
In the following example, the receiver's window is set to 10 packets.
Switch(config-if)# sscop receive-window 10
To change the transmitter window, use the sscop send-window interface configuration command. The no form of this command restores the default value.
sscop send-window packets| packets | Number of packets the interface can send before it must receive an acknowledgment from the ATM switch. Valid range is 1 to 6000. |
7 packets
Interface configuration
In the following example, the transmitter's window is set to 10 packets.
Switch(config-if)# sscop send-window 10
To set the flow control start character, use the start-character line configuration command. The command defines the character that signals the start of data transmission when software flow control is in effect. The no form of this command removes the character.
start-character ascii-number| ascii-number | ASCII decimal representation of the start character. |
ASCII decimal 17
Line configuration
The following example changes the start character to Ctrl-B, which is ASCII decimal 2.
Switch(config)#line aux 0Switch(config-line)#start-character 2
To manually start a chat script, use the start-chat privileged EXEC command. Use the no form of this command to stop the chat script.
start-chat regexp [aux 0 [dialer-string]]| regexp | Regular expression specifying the name of a regular expression or modem script to be executed. If there is more than one script with a name that matches the argument regexp, the first script found is used. |
| aux 0 | (Optional) Indicates the line number on which to execute the chat script. If you do not specify a line number, the current line number is chosen. If the specified line is busy, the script is not executed and an error message appears. If the dialer-string argument is specified, aux 0 must be entered; this command is not optional if you specify a dialer-string. This command functions only on physical terminal (tty) lines. It does not function on virtual terminal (vty) lines. |
| dialer-string | (Optional) String of characters (often a telephone number) to be sent to a DCE. If you enter a dialer-string, you must also specify aux 0, or the chat script regexp does not start. |
Disabled
Privileged EXEC
This command provides modem dialing commands for a chat script that you want to apply immediately to a line. If you do not specify a line, the script runs on the current line. If the specified line is already in use, the script is not activated and an error message appears. This command can only be used on the auxiliary port of the switch.
The argument regexp is used to specify the name of the modem script that is to be executed. The first script that matches the argument in this command and the dialer map command is used.
The following example manually starts the chat script with the word telebit in its name on line 0.
Switch# start-chat telebit aux 0
chat-script
dir
script activation
script connection
script reset
script startup
To turn on the PNNI statistics feature, use the statistics ATM router PNNI configuration command. To disable this feature, use the no form of this command.
statistics [call]| call | Specifies statistics related to route computation for call and party setups. |
Disabled
ATM router PNNI configuration
For more information, refer to the LightStream 1010 ATM Switch Software Configuration Guide.
The following script shows how to access the statistics ATM router PNNI configuration command.
Switch#configure terminalSwitch(config)#atm router pnniSwitch(config-atm-router)#statistics call
To set the number of the stop bits transmitted per byte, use the stopbits line configuration command.
stopbits {1 | 1.5 | 2}| 1 | One stop bit. |
| 1.5 | One and one-half stop bits. |
| 2 | Two stop bits. |
2 stop bits
Line configuration
The following example changes the default from 2 stop bits to 1 as a performance enhancement.
Switch(config)#line aux 0Switch(config-line)#stopbits 1
To set the flow control stop character, use the stop-character line configuration command. The no form of this command removes the character.
stop-character ascii-number| ascii-number | ASCII decimal representation of the stop character. |
ASCII decimal 19
Line configuration
This command defines the character that signals the end of data transmission when software flow control is in effect.
The following example changes the stop character to ^E, which is ASCII decimal 5.
Switch(config)#line aux 0Switch(config-line)#stop-character 5
To configure summary address prefixes on a PNNI node, use the summary-address node-level subcommand. To remove configured summary address prefixes, use the no form of this command.
summary-address address-prefix [internal | exterior] [suppress]| address-prefix | Specifies the summary address prefix. The maximum length of the address prefix is 19 bytes. Each character in the prefix is 4-bits long. The length of the prefix must fall on a nibble boundary. In other words, the length of the prefix must be a multiple of 4-bits. |
| internal | Local knowledge of reachability, including end-system addresses registered via ILMI address registration. |
| exterior | Knowledge of reachability through remote networks or derived from other protocol exchanges outside the PNNI routing domain. |
| suppress | Indicates that neither the summary address nor any addresses for which the summary address is the longest matching prefix are advertised. |
Default summary addresses are controlled by the auto-summary command.
The default summary address type is internal.
PNNI node configuration
Summary addresses can be used to decrease the amount of information advertised by this PNNI node. Summary addresses should only be configured when all endsystem addresses matching the summary address are reachable from this switch (for example, not reachable through PNNI interfaces to other switches).
Summary addresses of type internal only summarize internal addresses reachable from this switch (such as ILMI-registered addresses and internal static routes). Summary addresses of type exterior only summarize exterior addresses reachable from this switch (for example, exterior static routes on IISP or Public UNI interfaces).
Suppressed summary addresses can be used to prevent other PNNI nodes from learning of this switch's connectivity to certain addresses (for example, for backdoors).
For more information, refer to the LightStream 1010 ATM Switch Software Configuration Guide.
The following script shows how to access the summary-address node-level subcommand.
Switch#configure terminalSwitch(config)#atm router pnniSwitch(config-atm-router)#node 1Switch(config-pnni-node)#summary-address 48.91...
atm route
auto-summary
show atm route
This command has been replaced by the show users command. Refer to that command for information.
|
|