|
|
This chapter describes the function and displays the syntax of commands used to manage the router system and its performance on the network. For more information about defaults and usage guidelines, see the corresponding chapter of the Configuration Fundamentals Command Reference.
To enable the router to create a temporary access list entry in a dynamic access list, use the access-enable EXEC command.
access-enable [host] [timeout minutes]| host | (Optional) Tells the software to enable access only for the host from which the Telnet session originated. If not specified, the software allows all hosts on the defined network to gain access. The dynamic access list contains the network mask to use for enabling the new network. |
| timeout minutes | (Optional) Specifies an idle timeout for the temporary access list entry. If the access list entry is not accessed within this period, it is automatically deleted and requires the user to authenticate again. The default is for the entries to remain permanently. It is recommended that this value equal the idle timeout set for the WAN connection. |
To manually place a temporary access list entry on a router to which you are connected, use the access-template EXEC command.
access-template [access-list-number] [dynamic-name] [source] [destination] [timeout minutes]| access-list-number | (Optional) Number of the dynamic access list. |
| dynamic-name | (Optional) Name of a dynamic access list. |
| source | (Optional) Source address in a dynamic access list. The keywords host and any are allowed. All other attributes are inherited from the original access-list entry. |
| destination | (Optional) Destination address in a dynamic access list. The keywords host and any are allowed. All other attributes are inherited from the original access-list entry. |
| timeout minutes | (Optional) Specifies a maximum time limit for each entry within this dynamic list. This is an absolute time, from creation, that an entry can reside in the list. The default is an infinite time limit and allows an entry to remain permanently. |
To create a command alias, use the alias global configuration command. Use the no alias command to delete all aliases in a command mode or to delete a specific alias, and to revert to the original command syntax.
alias mode alias-name alias-command-line| mode | Command mode of the original and alias commands. Values are:
· controller--Controller configuration · exec--EXEC · hub--Hub configuration · interface--Interface configuration · ipx-router--IPX router configuration · line--Line configuration · map-class--Map-class configuration · map-list--Map list configuration · route-map--Route map configuration · router--Router configuration |
| alias-name | Command alias. |
| alias-command-line | Original command syntax. |
To set the number of history buckets that are kept during the response time reporter probe's lifetime, use the buckets-of-history-kept response time reporter configuration command. Use the no form of this command to return to the default value.
buckets-of-history-kept size| size | Number of history buckets kept during the response time reporter probe's lifetime. The default is 50 buckets. |
Use the buffers global configuration command to make adjustments to initial buffer pool settings and to the limits at which temporary buffers are created and destroyed. Use the no form of this command to return the buffers to their default size.
buffers {small | middle | big | verybig | large | huge | type number} {permanent | max-free| small | Buffer size of this public buffer pool is 104 bytes. |
| middle | Buffer size of this public buffer pool is 600 bytes. |
| big | Buffer size of this public buffer pool is 1524 bytes. |
| verybig | Buffer size of this public buffer pool is 4520 bytes. |
| large | Buffer size of this public buffer pool is 5024 bytes. |
| huge | Default buffer size of this public buffer pool is 18024 bytes. This value can be configured with the buffers huge size command. |
| type number | Interface type and interface number of the interface buffer pool. The type value cannot be fddi. |
| permanent | Number of permanent buffers that the system tries to create and keep. Permanent buffers are normally not trimmed by the system. |
| max-free | Maximum number of free or unallocated buffers in a buffer pool. |
| min-free | Minimum number of free or unallocated buffers in a buffer pool. |
| initial | Number of additional temporary buffers that are to be allocated when the system is reloaded. This keyword can be used to ensure that the system has necessary buffers immediately after reloading in a high-traffic environment. |
| number | Number of buffers to be allocated. |
Use the buffers huge size global configuration command to dynamically resize all huge buffers to the value you specify. Use the no form of this command to restore the default buffer values.
buffers huge size number| number | Number of buffers to be allocated. |
To set the system calendar for a Cisco 7000 series, Cisco 7200 series, or Cisco 4500 system, use the calendar set EXEC command.
calendar set hh:mm:ss day month year| hh:mm:ss | Current time in hours (military format), minutes, and seconds. |
| day | Current day (by date) in the month. |
| month | Current month (by name). |
| year | Current year (no abbreviation). |
To enable Cisco Discovery Protocol (CDP) on an interface, use the cdp enable interface configuration command. Use the no form of this command to disable CDP on an interface.
cdp enableTo specify the amount of time the receiving device should hold a CDP packet from your router before discarding it, use the cdp holdtime global configuration command. Use the no form of this command to revert to the default setting.
cdp holdtime seconds| seconds | Specifies the hold time to be sent in the CDP update packets. |
To enable CDP, use the cdp run global configuration command. Use the no form of this command to disable CDP.
cdp runTo specify how often the Cisco IOS software sends CDP updates, use the cdp timer global configuration command. Use the no form of this command to revert to the default setting.
cdp timer seconds| seconds | Specifies how often the Cisco IOS software sends CDP updates. |
To reset CDP traffic counters to zero (0), use the clear cdp counters privileged EXEC command.
clear cdp countersTo clear the table that contains CDP information about neighbors, use the clear cdp table privileged EXEC command.
clear cdp tableTo configure the Cisco 7000 series or the Cisco 4500 as a time source for a network based on its calendar, use the clock calendar-valid global configuration command. Use the no form of this command to set the Cisco IOS software so that the calendar is not an authoritative time source.
clock calendar-validTo manually read the calendar into either the Cisco 7000, Cisco 7200 series, or Cisco 4500 series clock, use the clock read-calendar EXEC command.
clock read-calendarTo manually set the system clock, use the clock set EXEC command.
clock set hh:mm:ss day month year| hh:mm:ss | Current time in hours (military format), minutes, and seconds. |
| day | Current day (by date) in the month. |
| month | Current month (by name). |
| year | Current year (no abbreviation). |
To configure the system to automatically switch to summer time (daylight savings time), use one of the formats of the clock summer-time configuration command. Use the no form of this command to configure the Cisco IOS software not to automatically switch to summer time.
clock summer-time zone recurring [week day month hh:mm week day month hh:mm [offset]]| zone | Name of the time zone (PDT,...) to be displayed when summer time is in effect. |
| week | Week of the month (1 to 5 or last). |
| day | Day of the week (Sunday, Monday,...). |
| date | Date of the month (1 to 31). |
| month | Month (January, February,...). |
| year | Year (1993 to 2035). |
| hh:mm | Time (military format) in hours and minutes. |
| offset | (Optional) Number of minutes to add during summer time (default is 60). |
To set the time zone for display purposes, use the clock timezone global configuration command. To set the time to Coordinated Universal Time (UTC), use the no form of this command.
clock timezone zone hours [minutes]| zone | Name of the time zone to be displayed when standard time is in effect. |
| hours | Hours offset from UTC. |
| minutes | (Optional) Minutes offset from UTC. |
To set the Cisco 7000, Cisco 7200, or Cisco 4500 calendar from the system clock, use the clock update-calendar EXEC command.
clock update-calendarTo assign a custom queue list to an interface, use the custom-queue-list interface configuration command. To remove a specific list or all list assignments, use the no form of the command.
custom-queue-list list| list | Number of the custom queue list you want to assign to the interface. An integer from 1 to 16. |
To set the number of statistic distributions kept per hop during the response time reporter probe's lifetime, use the distributions-of-statistics-kept response time reporter configuration command. Use the no form of this command to return to the default value.
distributions-of-statistics-kept size| size | Number of statistic distributions kept per hop. The default is 1 distribution. |
To generate a configuration that is compatible with an earlier Cisco IOS release, use the downward-compatible-config global configuration command. To remove this feature, use the no form of this command.
downward-compatible-config version| version | Cisco IOS Release number, not earlier than 10.2. |
| congestive-discard-threshold | (Optional) Number of messages allowed in each queue in the range 1 to 512. The default is 64 messages. When the number of messages in the queue for a high-bandwidth conversation reaches the specified threshold, new high-bandwidth messages are discarded. |
| dynamic-queues | (Optional) Number of dynamic queues used for best-effort conversations (that is, a normal conversation not requiring any special network services). Values are 16, 32, 64, 128, 256, 512, 1024, 2048, and 4096. The default is 256. |
| reservable-queues | (Optional) Number of reservable queues used for reserved conversations in the range 0 to 1000. The default is 0. Reservable queues are used for interfaces configured for the Resource Reservation Protocol (RSVP) feature. |
To define the type of information kept in the history table for the response time reporter probe, use the filter-for-history response time reporter configuration command. Use the no form of this command to return to the default value.
filter-for-history {none | all | overThreshold | failures}| none | No history kept. This is the default. |
| all | All probe operations attempted are kept in the history table. |
| overThreshold | Only packets that are over the threshold are kept in the history table. |
| failures | Only packets that fail for any reason are kept in the history table. |
To set the rate at which the response time reporter probe starts a response time operation, use the frequency response time reporter configuration command. Use the no form of this command to return to the default value.
frequency second| second | Number of seconds between the probe's response time reporter operations. The default value is 60 seconds. |
To set the number of hops for which statistics are maintained per path for the response time reporter probe, use the hops-of-statistics-kept response time reporter configuration command. Use the no form of this command to return to the default value.
hops-of-statistics-kept size| size | Number of hops for which statistics are maintained per path. The default is 16 hops for type pathecho and 1 hop for type echo. |
To specify or modify the host name for the network server, use the hostname global configuration command. The host name is used in prompts and default configuration filenames. The setup command facility also prompts for a host name at startup.
hostname name| name | New host name for the network server. |
To set the number of hours for which statistics are maintained for the response time reporter probe, use the hours-of-statistics-kept response time reporter configuration command. Use the no form of this command to return to the default value.
hours-of-statistics-kept hours| hours | Number of hours that the router maintains statistics. The default is 2 hours. |
Use the ip telnet source-interface global configuration command to allow a user to select an address of an interface as the source address for Telnet connections.
ip telnet source-interface interface| interface | The interface whose address is to be used as the source for Telnet connections. |
Use the ip tftp source-interface global configuration command to allow a user to select the interface whose address will be used as the source address for TFTP connections.
ip tftp source-interface interface| interface | The interface whose address is to be used as the source for TFTP connections. |
To set the number of lives maintained in the history table for the response time reporter probe, use the lives-of-history-kept response time reporter configuration command. Use the no form of this command to return to the default value.
lives-of-history-kept lives| lives | Number of lives maintained in the history table for the probe. The default is 0 lives. |
To change the length of time for which data is used to compute load statistics, use the load-interval interface configuration command. Use the no form of this command to revert to the default setting.
load-interval seconds| seconds | Length of time for which data is used to compute load statistics. A value that is a multiple of 30, from 30 to 600 (30, 60, 90, 120, and so forth). |
To log messages to a syslog server host, use the logging global configuration command. The no form of this command deletes the syslog server with the specified address from the list of syslogs.
logging host| host | Name or IP address of the host to be used as a syslog server. |
To log messages to an internal buffer, use the logging buffered global configuration command. The no form of this command cancels the use of the buffer and writes messages to the console terminal, which is the default.
logging buffered [size]| size | (Optional) Size of the buffer from 4096 to 4294967295 bytes. The default is 4096 bytes (4K). |
To limit messages logged to the console based on severity, use the logging console global configuration command. The no form of this command disables logging to the console terminal.
logging console level| level | Limits the logging of messages displayed on the console terminal to a specified level. Values are:
· emergencies (level 0)--System unusable (LOG_EMERG) · alerts (level 1)--Immediate action needed (LOG_ALERT) · critical (level 2)--Critical conditions (LOG_CRIT) · errors (level 3)--Error conditions (LOG_ERR) · warnings (level 4)--Warning conditions (LOG_WARNING) · notifications (level 5)--Normal but significant condition (LOG_NOTICE) |
| · informational (level 6)--Informational messages only (LOG_INFO)
· debugging (level 7)--Debugging messages (LOG_DEBUG) |
To configure the syslog facility in which error messages are sent, use the logging facility global configuration command. To revert to the default of local7, use the no form of this command.
logging facility facility-type| facility-type | Syslog facility. Values are: auth, cron, daemon, kern, local0-7, lpr, mail, news, sys9, sys10, sys11, sys12, sys13, sys14, syslog, user, and uucp. |
To limit syslog messages sent to the router's history table and the SNMP network management station based on severity, use the logging history global configuration command. The no form of this command returns the logging of syslog messages to the default level.
logging history level| level | Limits the messages saved in the history table and sent to the SNMP network management station to the specified set of levels. Values are:
· emergencies (level 0)--System unusable (LOG_EMERG) · alerts (level 1)--Immediate action needed(LOG_ALERT) · critical (level 2)--Critical conditions (LOG_CRIT) · errors (level 3)--Error conditions (LOG_ERR) |
| · warnings (level 4)--Warning conditions (LOG_WARNING)
· notifications (level 5)--Normal but significant condition (LOG_NOTICE) · informational (level 6)--Informational messages only (LOG_INFO) · debugging (level 7)--Debugging messages (LOG_DEBUG) |
To change the number of syslog messages stored in the router's history table, use the logging history size global configuration command. The no form of this command returns the number of messages to the default value.
logging history size number| number | Number from 1 to 500 that indicates the maximum number of messages stored in the history table. |
To limit messages logged to the terminal lines (monitors) based on severity, use the logging monitor global configuration command. This command limits the logging messages displayed on terminal lines other than the console line to messages with a level at or above level. The no form of this command disables logging to terminal lines other than the console line.
logging monitor level| level | One of the level keywords. Values are:
· emergencies (level 0)--System unusable (LOG_EMERG) · alerts (level 1)--Immediate action needed(LOG_ALERT) · critical (level 2)--Critical conditions (LOG_CRIT) · errors (level 3)--Error conditions (LOG_ERR) · warnings (level 4)--Warning conditions (LOG_WARNING) · notifications (level 5)--Normal but significant condition (LOG_NOTICE) · informational (level 6)--Informational messages only (LOG_INFO) · debugging (level 7)--Debugging messages (LOG_DEBUG) |
To control logging of error messages, use the logging on global configuration command. This command enables or disables message logging to all destinations except the console terminal. The no form of this command enables logging to the console terminal only.
logging on| level severity-level | (Optional) Specifies the message severity level. Messages with a severity level equal to or higher than this value are printed asynchronously. When specifying a severity level number, consider that for the logging system, low numbers indicate greater severity and high numbers indicate lesser severity. The default value is 2. |
| all | (Optional) Specifies that all messages are printed asynchronously, regardless of the severity level. |
| limit number-of-buffers | (Optional) Specifies the number of buffers to be queued for the terminal after which new messages are dropped. The default value is 20. |
To limit messages logged to the syslog servers based on severity, use the logging trap global configuration command. The command limits the logging of error messages sent to syslog servers to only those messages at the specified level. Use the no form of this command to disable logging to syslog servers.
logging trap level| level | One of the level keywords. Values are:
· emergencies (level 0)--System unusable (LOG_EMERG) · alerts (level 1)--Immediate action needed(LOG_ALERT) · critical (level 2)--Critical conditions (LOG_CRIT) · errors (level 3)--Error conditions (LOG_ERR) · warnings (level 4)--Warning conditions (LOG_WARNING) · notifications (level 5)--Normal but significant condition (LOG_NOTICE) |
| · informational (level 6)--Informational messages only (LOG_INFO)
· debugging (level 7)--Debugging messages (LOG_DEBUG) |
To control access to the system's Network Time Protocol (NTP) services, use the ntp access-group global configuration command. To remove access control to the system's NTP services, use the no form of this command.
ntp access-group {query-only | serve-only | serve | peer} access-list-number| query-only | Allows only NTP control queries. See RFC 1305 (NTP version 3). |
| serve-only | Allows only time requests. |
| serve | Allows time requests and NTP control queries, but does not allow the system to synchronize to the remote system. |
| peer | Allows time requests and NTP control queries and allows the system to synchronize to the remote system. |
| access-list-number | Number (1 to 99) of a standard IP access list. |
To enable Network Time Protocol (NTP) authentication, use the ntp authenticate global configuration command. Use the no form of this command to disable the feature.
ntp authenticateTo define an authentication key for Network Time Protocol (NTP), use the ntp authentication-key global configuration command. Use the no form of this command to remove the authentication key for NTP.
ntp authentication-key number md5 value| number | Key number (1 to 4294967295). |
| md5 | Authentication key. Message authentication support is provided using the Message Digest (MD5) algorithm. The key type md5 is currently the only key type supported. |
| value | Key value (an arbitrary string of up to eight characters). |
To specify that a specific interface should send Network Time Protocol (NTP) broadcast packets, use the ntp broadcast interface configuration command. Use the no form of this command to disable this capability.
ntp broadcast [version number]| version number | (Optional) Number from 1 to 3 indicating the NTP version. |
To allow the system to receive NTP broadcast packets on an interface, use the ntp broadcast client command. Use the no form of this command to disable this capability.
ntp broadcast clientTo set the estimated round-trip delay between the Cisco IOS software and a Network Time Protocol (NTP) broadcast server, use the ntp broadcastdelay global configuration command. Use the no form of this command to revert to the default value.
ntp broadcastdelay microseconds| microseconds | Estimated round-trip time (in microseconds) for NTP broadcasts. The range is from 1 to 999999. |
Caution Do not enter this command; it is documented for informational purposes only. The system automatically generates this command as Network Time Protocol (NTP) determines the clock error and compensates.
As NTP compensates for the error in the system clock, it keeps track of the correction factor for this error. The system automatically saves this value into the system configuration using the ntp clock-period global configuration command. The system uses the no form of this command to revert to the default.
ntp clock-period value| value | Amount to add to the system clock for each clock hardware tick (in units of 2-32 seconds). |
To prevent an interface from receiving Network Time Protocol (NTP) packets, use the ntp disable interface configuration command. To enable receipt of NTP packets on an interface, use the no form of this command.
ntp disable Caution Use this command with extreme caution. It is very easy to override valid time sources using this command, especially if a low stratum number is configured. Configuring multiple machines in the same network with the ntp master command can cause instability in keeping time if the machines do not agree on the time.
To configure the Cisco IOS software as a Network Time Protocol (NTP) master clock to which peers synchronize themselves when an external NTP source is not available, use the ntp master global configuration command. To disable the master clock function, use the no form of this command.
ntp master [stratum]| stratum | (Optional) Number from 1 to 15. Indicates the NTP stratum number that the system will claim. |
To configure the system clock to synchronize a peer or to be synchronized by a peer, use the ntp peer global configuration command. To disable this capability, use the no form of this command.
ntp peer ip-address [version number] [key keyid] [source interface] [prefer]| ip-address | IP address of the peer providing, or being provided, the clock synchronization. |
| version | (Optional) Defines the Network Time Protocol (NTP) version number. |
| number | (Optional) NTP version number (1 to 3). |
| key | (Optional) Defines the authentication key. |
| keyid | (Optional) Authentication key to use when sending packets to this peer. |
| source | (Optional) Names the interface. |
| interface | (Optional) Name of the interface from which to pick the IP source address. |
| prefer | (Optional) Makes this peer the preferred peer that provides synchronization. |
To allow the system clock to be synchronized by a time server, use the ntp server global configuration command. To disable this capability, use the no form of this command.
ntp server ip-address [version number] [key keyid] [source interface] [prefer]| ip-address | IP address of the time server providing the clock synchronization. |
| version | (Optional) Defines the Network Time Protocol (NTP) version number. |
| number | (Optional) NTP version number (1 to 3). |
| key | (Optional) Defines the authentication key. |
| keyid | (Optional) Authentication key to use when sending packets to this peer. |
| source | (Optional) Identifies the interface from which to pick the IP source address. |
| interface | (Optional) Name of the interface from which to pick the IP source address. |
| prefer | (Optional) Makes this server the preferred server that provides synchronization. |
To use a particular source address in Network Time Protocol (NTP) packets, use the ntp source global configuration command. Use the no form of this command to remove the specified source address.
ntp source type number| type | Type of interface. |
| number | Number of the interface. |
To authenticate the identity of a system to which Network Time Protocol (NTP) will synchronize, use the ntp trusted-key global configuration command. Use the no form of this command to disable authentication of the identity of the system.
ntp trusted-key key-number| key-number | Key number of authentication key to be trusted. |
To periodically update the Cisco 7000 series or Cisco 7200 series calendar from Network Time Protocol (NTP), use the ntp update-calendar global configuration command. Use the no form of this command to disable this feature.
ntp update-calendarTo configure the SNMP owner of the response time reporter probe, use the owner response time reporter configuration command. Use the no form of this command to return to the default value.
owner text| text | Name of the SNMP owner from 0 to 255 ASCII characters. The default is none. |
To set the number of paths for which statistics are maintained per hour for the response time reporter probe, use the paths-of-statistics-kept response time reporter configuration command. Use the no form of this command to return to the default value.
paths-of-statistics-kept size| size | Number of paths for which statistics are maintained per hour. The default is 5 paths for type pathEcho and 1 path for type echo. |
Use the ping (packet internet groper) privileged EXEC command to diagnose basic network connectivity on Apollo, AppleTalk, Connectionless Network Service (CLNS), DECnet, IP, Novell IPX, VINES, or XNS networks.
ping [protocol] {host | address}| protocol | (Optional) Protocol keyword, one of apollo, appletalk, clns, decnet, ip, ipx, vines, or xns. |
| host | Host name of system to ping. |
| address | Address of system to ping. |
Use the ping (packet internet groper) user EXEC command to diagnose basic network connectivity on AppleTalk, CLNS, IP, Novell, Apollo, VINES, DECnet, or XNS networks.
ping [protocol] {host | address}| protocol | (Optional) Protocol keyword, one of apollo, appletalk, clns, decnet, ip, ipx, vines, or xns. |
| host | Host name of system to ping. |
| address | Address of system to ping. |
To assign the specified priority list to an interface, use the priority-group interface configuration command. Use the no form of this command to remove the specified priority group assignment.
priority-group list| list | Priority list number assigned to the interface. |
To assign a priority queue for those packets that do not match any other rule in the priority list, use the priority-list default global configuration command. Use the no form of this command to return to the default or assign normal as the default.
priority-list list-number default {high | medium | normal | low}| list-number | Arbitrary integer between 1 and 10 that identifies the priority list selected by the user. |
| high | medium | normal | low | Priority queue level. |
To establish queuing priorities on packets entering from a given interface, use the priority-list interface global configuration command. Use the no form of this command with the appropriate arguments to remove an entry from the list.
priority-list list-number interface interface-type interface-number {high | medium || list-number | Arbitrary integer between 1 and 10 that identifies the priority list selected by the user. |
| interface-type | Specifies the name of the interface. |
| interface-number | Number of the specified interface. |
| high | medium | normal | low | Priority queue level. |
To establish queuing priorities based upon the protocol type, use the priority-list protocol global configuration command. Use the no form of this command with the appropriate list number to remove an entry from the list.
priority-list list number protocol protocol-name {high | medium | normal | low}| list-number | Arbitrary integer between 1 and 10 that identifies the priority list selected by the user. |
| protocol-name | Specifies the protocol type: aarp, arp, apollo, appletalk, bridge (transparent), clns, clns_es, clns_is, compressedtcp, cmns, decnet, decnet_node, decnet_router-l1, decnet_router-l2, ip, ipx, pad, rsrb, stun, vines, xns, and x25. |
| high | medium | normal | low | Priority queue level. |
| queue-keyword keyword-value | Possible keywords are fragments, gt, lt, list, tcp, and udp. |
To specify the maximum number of packets that can be waiting in each of the priority queues, use the priority-list queue-limit global configuration command.The no form of this command selects the normal queue.
priority-list list-number queue-limit high-limit medium-limit normal-limit low-limit| list-number | Arbitrary integer between 1 and 16 that identifies the priority list selected by the user. |
| high-limit medium-limit normal-limit low-limit | Priority queue maximum length. A value of 0 for any of the four arguments means that the queue can be of unlimited size for that particular queue. |
To customize the prompt, use the prompt global configuration command. To revert to the default prompt, use the no form of this command.
prompt string| string | Prompt. It can consist of all printing characters and the following escape sequences:
· %h--Host name. This is either Router or the name defined with the hostname global configuration command. · %n--Physical terminal line (TTY) number of the EXEC user. · %p--Prompt character itself. It is either an angle bracket (>) for EXEC mode or a pound sign (#) for privileged EXEC mode. · %s--Space. · %t--Tab. · %%--Percent sign (%). |
To assign a priority queue for those packets that do not match any other rule in the queue list, use the queue-list default global configuration command. To restore the default value, use the no form of this command.
queue-list list-number default queue-number| list-number | Number of the queue list. An integer from 1 to 16. |
| queue-number | Number of the queue. An integer from 1 to 16. |
To establish queuing priorities on packets entering on an interface, use the queue-list interface global configuration command. To remove an entry from the list, use the no form of the command.
queue-list list-number interface interface-type interface-number queue-number| list-number | Number of the queue list. An integer from 1 to 16. |
| interface-type | Required argument that specifies the name of the interface. |
| interface-number | Number of the specified interface. |
| queue-number | Number of the queue. An integer from 1 to 16. |
To establish queuing priority based upon the protocol type, use the queue-list protocol global configuration command. Use the no form of this command with the appropriate list number to remove an entry from the list.
queue-list list-number protocol protocol-name queue-number queue-keyword keyword-value| list-number | Number of the queue list. An integer from 1 to 16. |
| protocol-name | Required argument that specifies the protocol type: aarp, arp, apollo, appletalk, bridge (transparent), clns, clns_es, clns_is, compressedtcp, cmns, decnet, decnet_node, decnet_routerl1, decnet_routerl2, ip, ipx, pad, rsrb, stun, vines, xns, and x25. |
| queue-number | Number of the queue. An integer from 1 to 16. |
| queue-keyword keyword-value | Possible keywords are gt, lt, list, tcp, and udp. |
To designate the byte size allowed per queue, use the queue-list queue byte-count global configuration command. To return the byte size to the default value, use the no form of the command.
queue-list list-number queue queue-number byte-count byte-count-number| list-number | Number of the queue list. An integer from 1 to 16. |
| queue-number | Number of the queue. An integer from 1 to 16. |
| byte-count-number | Specifies the lower boundary on how many bytes the system allows to be delivered from a given queue during a particular cycle. |
To designate the queue length limit for a queue, use the queue-list queue limit global configuration command. To return the queue length to the default value, use the no form of the command.
queue-list list-number queue queue-number limit limit-number| list-number | Number of the queue list. An integer from 1 to 16. |
| queue-number | Number of the queue. An integer from 1 to 16. |
| limit-number | Maximum number of packets which can be enqueued at any time. Range is 0 to 32767 queue entries. |
To enable random early detection on an interface, use the random-detect interface configuration command. Use the no form of this command to disable random early detection on the interface.
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 210). |
To set the protocol data size in the payload of the response time reporter probe's request packet, use the request-data-size response time reporter configuration command. Use the no form of this command to return to the default value.
request-data-size byte| byte | Size of the protocol data in the payload of the probe's request packet. Range is 0 to the protocol's maximum. The default is 1 byte. |
To set the protocol data size in the payload of the response time reporter probe's response packet, use the response-data-size response time reporter configuration command. Use the no form of this command to return to the default value.
response-data-size byte| byte | Size of the protocol data in the payload in the probe's response packet. For "appl" protocols, the default is 0 byte. For all others, the default is the same value as the request-data-size. |
To enable Remote Network Monitoring (RMON) on an Ethernet interface, use the rmon interface configuration command. Use the no form of this command to disable RMON on the interface.
rmon {native | promiscuous}| native | Enables RMON on the Ethernet interface. In native mode, the router processes only packets destined for this interface. |
| promiscuous | Enables RMON on the Ethernet interface. In promiscuous mode, the router examines every packet. |
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 [event-number]| number | Alarm number, which is identical to the alarmIndex in the alarmTable in the Remote Network 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. |
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 community | (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 string | (Optional) Specifies a description of the event, which is identical to the event description in the eventTable of the RMON MIB. |
| owner string | (Optional) Owner of this event, which is identical to the eventDescription in the eventTable of the RMON MIB. |
To change the size of the queue that holds packets for analysis by the Remote Network Monitoring (RMON) process, use the rmon queuesize global configuration command. Use the no form of this command to restore the default value.
rmon queuesize size| size | Number of packets allowed in the queue awaiting RMON analysis. Default queue size is 64 packets. |
To configure a response time reporter probe, use the rtr global configuration command. Use the no form of this command to remove all configuration information for a probe including the probe's schedule, reaction configuration, and reaction triggers.
rtr probe| probe | Number of the response time reporter probe (instance) to configure. |
To configure certain actions to occur based on events under the control of the response time reporter, use the rtr reaction-configuration global configuration command. Use the no form of this command to return to the probe's default values.
rtr reaction-configuration probe [connection-loss-enable] [timeout-enable]| probe | Number of the response time reporter probe to configure. |
| connection-loss-enable | (Optional) Enable checking for connection loss in connection-oriented protocols. The default is disabled. |
| timeout-enable | (Optional) Enable checking for response time reporting operation timeouts based on the timeout value configured for the probe with the timeout response time reporter configuration command. The default is disabled. |
| threshold-falling milliseconds | (Optional) Set the falling threshold (standard RMON-type hysteresis mechanism) in milliseconds. When the falling threshold is met, generate a resolution reaction event. The probe's rising over threshold is set with the threshold response time reporter configuration command. The default value is 3000 ms. |
| threshold-type option | (Optional) Specify the algorithm used by the response time reporter to calculate over and falling threshold violations. Option can be one of the following keywords:
· never--Do not calculate threshold violations (the default). · immediate--When the response time exceeds the rising over threshold or drops below the falling threshold, immediately perform the action defined by action-type. · consecutive [occurrences]--When the response time exceeds the rising threshold consecutively 5 times or drops below the falling threshold consecutively 5 times, perform the action defined by action-type. Optionally specify the number of consecutive occurrences. The default is 5. · xofy [x-value y-value]--When the response time exceeds the rising threshold 5 out of the last 5 times or drops below the falling threshold 5 out of the last 5 times, perform the action defined by action-type. Optionally specify the number of violations that must occur and the number that must occur within a specified number. The default is 5 for both x-value and y-value. · average [attempts]--When the average of the last 5 response times exceeds the rising threshold or when the average of the last 5 response times drops below the falling threshold, perform the action defined by action-type. Optionally specify the number of operations to average. The default is the average of the last 5 response time operations. For example: if the probe's threshold is 5000 ms and the probe's last 3 attempts results are 6000, 6000, and 5000 ms, the average would be 6000+6000+5000=17000/3>5000, thus violating the 5000-ms threshold. |
| action-type option | (Optional) Specify what action or combination of actions the probe performs when you configure connection-loss-enable or timeout-enable, or threshold events occur. For the action-type to occur for threshold events, the threshold-type must be defined to anything other than never. Option can be one of the following keywords:
· none--No action is taken. · trapOnly--Send an SNMP trap on both over and falling threshold violations. · nmvtOnly--Send an SNA NMVT Alert on over threshold violation and an SNA NMVT Resolution on falling threshold violations. |
| · triggerOnly--Transition one or more target probe's operational state from "pending" to "active" on over (and falling) threshold violations. The target probes are defined with the rtr reaction-trigger command. A target probe will continue until its life expires as specified by the target probe's life value configured with the rtr schedule global configuration command. After a target probe is triggered, it must finish its life before it can be triggered again.
· trapAndMmvt--Send a combination of trapOnly and nmvtOnly. · trapAndTrigger--Send a combination of trapOnly and triggerOnly. · nmvtAndTrigger--Send a combination of nmvtOnly and triggerOnly. · trapNmvtAndTrigger--Send a combination of trapOnly, nmvtOnly, and triggerOnly. |
To define a second response time reporter probe to make the transition from a "pending" state to an "active" state when one of the trigger action-type options are defined with the rtr reaction-configuration global configuration command, use the rtr reaction-trigger global configuration command. Use the no form of this command to remove the trigger combination.
rtr reaction-trigger probe target-probe| probe | Number of the probe in the "active" state that has the action-type set with the rtr reaction-configuration global configuration command. |
| target-probe | Number of the probe in the "pending" state that is waiting to be triggered with the rtr global configuration command. |
To perform a shutdown and restart of the response time reporter, use the rtr reset global configuration command.
rtr resetTo configure the time parameters for a response time reporter probe, use the rtr schedule global configuration command. Use the no form of this command to stop the probe and restart it with the default parameters (that is, pending).
rtr schedule probe [life seconds] [start-time {pending | now | hh:mm [month day || probe | Number of the response time reporter probe to schedule. |
| life seconds | (Optional) Number of seconds the probe actively collects information. The default is 3600 seconds (one hour). |
| start-time | (Optional) Time when the probe starts collecting information. If the start-time is not specified, no information is collected until the start-time is configured or a trigger occurs that performs a start-time now. |
| pending | No information is collected. This is the default value. |
| now | Information is immediately collected. |
| hh:mm | Information is collected at the specified time (use a 24-hour clock). The time is the current day if you do not specify the month and day. |
| month | (Optional) Name of the month, any characters in a unique string. If month is not specified, the current month is used. This requires a day. |
| day | (Optional) Number of the day in the range 1 to 31. If day is not specified, the current day is used. This requires a month. |
| ageout seconds | (Optional) Number of seconds to keep the probe when it is not actively collecting information. The default is 0 seconds (never ages out). |
To set the number of entries kept in the history table per bucket for the response time reporter probe, use the samples-of-history-kept response time reporter configuration command. Use the no form of this command to return to the default value.
samples-of-history-kept samples| samples | Number of entries kept in the history table per bucket. The default is 16 entries for type pathecho and 1 entry for type echo. |
To guarantee CPU time for processes, use the scheduler allocate global configuration command on the Cisco 7200 series and Cisco 7500 series. 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. |
To control the maximum amount of time that can elapse without running the system processes, use the schedule interval global configuration command. The no form of this command restores the default.
scheduler-interval milliseconds| milliseconds | Integer that specifies the interval, in milliseconds. The minimum interval that you can specify is 500 milliseconds; there is no maximum value. |
To specify that line numbers be displayed and interpreted as decimal numbers rather than octal numbers, use the service decimal-tty global configuration command. Use the no form of this command to restore the default.
service decimal-ttyTo 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-waitTo 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. Use the no form of this command to remove this service.
service fingerTo hide addresses while trying to establish a Telnet session, use the service hide-telnet-address global configuration command. Use the no form of this command to remove this service.
service hide-telnet-addressTo 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 nagleTo display the configuration prompt (config), use the service prompt config global configuration command. Use the no form of this command to remove the configuration prompt.
service prompt configTo generate keepalive packets on idle incoming network connections (initiated by the remote host), use the service tcp-keepalives-in global configuration command. The no form of this command with the appropriate keyword disables the keepalives.
service tcp-keepalives-inTo generate keepalive packets on idle outgoing network connections (initiated by a user), use the service tcp-keepalives-out global configuration command. The no form of this command with the appropriate keyword disables the keepalives.
service tcp-keepalives-outTo access minor TCP/IP services available from hosts on the network, use the service tcp-small-servers command. Use the no form of the command to disable these services.
service tcp-small-serversTo set the TCP window to zero (0) when the Telnet connection is idle, use the service telnet-zero-idle global configuration command. Use the no form of this command to disable this feature.
service telnet-zero-idleTo 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. |
To access minor User Datagram Protocol (UDP) services available from hosts on the network, use the service udp-small-servers command. Use the no form of the command to disable these services.
service udp-small-serversTo display all alias commands, or the alias commands in a specified mode, use the show aliases EXEC command.
show aliases [mode]| mode | (Optional) Command mode. Values are:
· controller--Controller configuration · exec--EXEC · hub--Hub configuration · interface--Interface configuration · ipx-router--IPX router configuration · line--Line configuration · map-class--Map class configuration · map-list--Map list configuration · route-map--Route map configuration · router--Router configuration |
Use the show buffers EXEC command to display statistics for the buffer pools on the network server.
show buffers [type number | alloc [dump]]| type number | (Optional) Displays interface pool information. If the specified interface type and number has its own buffer pool, displays information for that pool. Value of type can be ethernet, serial, tokenring, fddi, bri, atm, e1, t1. |
| alloc | (Optional) Displays a brief listing of all allocated buffers. |
| dump | (Optional) Dumps all allocated buffers. This keyword must be used with the alloc keyword, not by itself. |
Use the show c7200 EXEC command to display information about the CPU and midplane for Cisco 7200 series routers.
show c7200To display the calendar hardware setting for the Cisco 7000 series, Cisco 7200 series, or Cisco 4500 series, use the show calendar EXEC command.
show calendarTo display global CDP information, including timer and hold-time information, use the show cdp privileged EXEC command.
show cdpTo display information about a neighbor device listed in the CDP table, use the show cdp entry privileged EXEC command.
show cdp entry entry-name [protocol | version]| entry-name | Name of neighbor about which you want information. |
| protocol | (Optional) Limits the display to information about the protocols enabled on a router. |
| version | (Optional) Limits the display to information about the version of software running on the router. |
To display information about the interfaces on which CDP is enabled, use the show cdp interface command.
show cdp interface [type number]| type | (Optional) Type of interface about which you want information. |
| number | (Optional) Number of the interface about which you want information. |
To display information about neighbors, use the show cdp neighbors privileged EXEC command.
show cdp neighbors [type number] [detail]| type | (Optional) Type of the interface connected to the neighbors about which you want information. |
| number | (Optional) Number of the interface connected to the neighbors about which you want information. |
| detail | (Optional) Displays detailed information about a neighbor (or neighbors) including network address, enabled protocols, hold time, and software version. |
To display traffic information from the CDP table, use the show cdp traffic privileged EXEC command.
show cdp trafficTo display the system clock, use the show clock EXEC command.
show clock [detail]| detail | (Optional) Indicates the clock source (NTP, VINES, 7000 calendar, and so forth) and the current summer-time setting (if any). |
To display information about the types of CDP debugging that are enabled for your router, use the show debugging privileged EXEC command.
show debugging| all | (Optional) Displays a detailed listing of the power supplies, temperature readings, and voltage readings. |
| last | (Optional) Displays the reason for the last system shutdown that was related to voltage or temperature and the environmental status at that time. |
| table | (Optional) Displays the temperature and voltage thresholds and a table that lists the ranges of environmental measurements that are within specification. |
Use the show gt64010 EXEC command to display all GT64010 internal registers and interrupt status on the Cisco 7200 series routers.
show gt64010Use the show logging EXEC command to display the state of logging (syslog).
show logging [history]| history | (Optional) Display information in the syslog history table only. |
Use the show memory EXEC command to show statistics about memory, including memory free pool statistics.
show memory [memory-type] [free] [summary]| memory-type | (Optional) Memory type to display (processor, multibus, io, sram). If type is not specified, statistics for all memory types present are displayed. |
| free | (Optional) Displays free memory statistics. |
| summary | (Optional) Displays a summary of memory usage including the size and number of blocks allocated for each address of the system call that allocated the block. |
To show the status of Network Time Protocol (NTP) associations, use the show ntp associations EXEC command.
show ntp associations [detail]| detail | (Optional) Shows detailed information about each NTP association. |
To show the status of Network Time Protocol (NTP), use the show ntp status EXEC command.
show ntp statusUse the show pci EXEC command to display information about the peripheral component interconnect (PCI) hardware registers or bridge registers for the Cisco 7200 series routers.
show pci {hardware | bridge [register]}| hardware | Display PCI hardware registers. |
| bridge | Display PCI bridge registers. |
| register | (Optional) Number of a specific bridge register in the range 0 to 7. If not specified, this command displays information about all registers. |
Use the show processes EXEC command to display information about the active processes.
show processes [cpu]| cpu | (Optional) Displays detailed CPU utilization statistics. |
Use the show processes memory EXEC command to show memory used.
show processes memoryUse the show protocols EXEC command to display the configured protocols.
This command shows the global and interface-specific status of any configured Level 3 protocol; for example, IP, DECnet, IPX, AppleTalk, and so forth.
show protocolsTo list the current state of the queue lists, use the show queueing privileged EXEC command.
show queueing [custom | fair | priority]| custom | (Optional) Shows status of custom queuing list configuration. |
| fair | (Optional) Shows status of the fair queuing configuration. This is the default. |
| priority | (Optional) Shows status of priority queuing list configuration. |
Use the show rmon EXEC command to display the current RMON agent status on the router.
show rmon [alarms | capture | events | filter | history | hosts | matrix | statistics | task | topn]| alarms | (Optional) Displays the RMON alarm table. |
| capture | (Optional) Displays the RMON buffer capture table. Available on Cisco 2500 series and Cisco AS5200 only. |
| events | (Optional) Displays the RMON event table. |
| filter | (Optional) Displays the RMON filter table. Available on Cisco 2500 series and Cisco AS5200 only. |
| history | (Optional) Displays the RMON history table. Available on Cisco 2500 series and Cisco AS5200 only. |
| hosts | (Optional) Displays the RMON hosts table. Available on Cisco 2500 series and Cisco AS5200 only. |
| matrix | (Optional) Displays the RMON matrix table. Available on Cisco 2500 series and Cisco AS5200 only. |
| statistics | (Optional) Displays the RMON statistics table. Available on Cisco 2500 series and Cisco AS5200 only. |
| task | (Optional) Displays general RMON statistics. |
| topn | (Optional) Displays the RMON top-n hosts table. Available on Cisco 2500 series and Cisco AS5200 only. |
Use the show rmon alarms EXEC command to display the contents of the router's RMON alarm table.
show rmon alarmsUse the show rmon capture EXEC command to display the contents of the router's RMON capture table.
show rmon captureUse the show rmon events EXEC command to display the contents of the router's RMON event table.
show rmon eventsUse the show rmon filter EXEC command to display the contents of the router's RMON filter table.
show rmon filterUse the show rmon history EXEC command to display the contents of the router's RMON history table.
show rmon historyUse the show rmon hosts EXEC command to display the contents of the router's RMON hosts table.
show rmon hostsUse the show rmon matrix EXEC command to display the contents of the router's RMON matrix table.
Use the show rmon statistics EXEC command to display the contents of the router's RMON statistics table.
show rmon statisticsUse the show rmon topn EXEC command to display the contents of the router's RMON Top-N host table.
show rmon topn| tabular | (Optional) Display information in a column format reducing the number of screens required to display the information. |
| full | (Optional) Display all information using identifiers next to each displayed value. This is the default. |
| probe | (Optional) Number of the response time reporter probe to display. |
| tabular | (Optional) Display information in a column format reducing the number of screens required to display the information. |
| full | (Optional) Display all information using identifiers next to each displayed value. This is the default. |
| probe | (Optional) Number of the response time reporter probe to display. |
| tabular | (Optional) Display information in a column format reducing the number of screens required to display the information. |
| full | (Optional) Display all information using identifiers next to each displayed value. This is the default. |
| probe | (Optional) Number of the response time reporter probe to display. |
| tabular | (Optional) Display information in a column format reducing the number of screens required to display the information. This is the default |
| full | (Optional) Display all information using identifiers next to each displayed value. |
| probe | (Optional) Number of the response time reporter probe to display. |
| tabular | (Optional) Display information in a column format reducing the number of screens required to display the information. This is the default. |
| full | (Optional) Display all information using identifiers next to each displayed value. |
| probe | (Optional) Number of the response time reporter probe to display. |
| tabular | (Optional) Display information in a column format reducing the number of screens required to display the information. |
| full | (Optional) Display all information using identifiers next to each displayed value. This is the default. |
| probe | (Optional) Number of the response time reporter probe to display. |
| tabular | (Optional) Display information in a column format reducing the number of screens required to display the information. |
| full | (Optional) Display all information using identifiers next to each displayed value. This is the default. |
| probe | (Optional) Number of the response time reporter probe to display. |
| tabular | (Optional) Display information in a column format reducing the number of screens required to display the information. |
| full | (Optional) Display all information using identifiers next to each displayed value. This is the default. |
To check the status of communications between the SNMP agent and SNMP manager, use the show snmp EXEC command.
show snmpUse the show stacks EXEC command to monitor the stack utilization of processes and interrupt routines.
show stacksUse the show tcp EXEC command to display the status of TCP connections.
show tcp [line-number]| line-number | (Optional) Absolute line number of the line for which you want to display Telnet connection status |
To display a concise description of TCP connection endpoints, use the show tcp brief EXEC command.
show tcp brief [all]| all | (Optional) Displays status for all endpoints. Without this keyword, endpoints in the LISTEN state are not shown. |
To display general information about the router when reporting a problem, use the show tech-support privileged EXEC command.
show tech-support [page] [password]| page | (Optional) Causes the output to display a page of information at a time. Use the return key to display the next line of output or use the space bar to display the next page of information. If not used, the output scrolls (that is, does not stop for page breaks). |
| password | (Optional) Leaves passwords and other security information in the output. If not used, passwords and other security-sensitive information in the output are replaced with the word "<removed>" (this is the default). |
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. |
To provide a message line identifying the SNMP server serial number, use the snmp-server chassis-id global configuration command. Use the no form of this command to restore the default value, if any.
snmp-server chassis-id text| text | Message you want to enter to identify the chassis serial number. |
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 [view view-name] [ro | rw] [number]| string | Community string that acts like a password and permits access to the SNMP protocol. |
| view view-name | (Optional) Name of a previously defined view. The view defines the objects available to the community. |
| 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 v.1 agent. |
To set the system contact (syscontact) string, use the snmp-server contact global configuration command. Use the no form to remove the system contact information.
snmp-server contact text| text | String that describes the system contact information. |
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.192.180.45.11.1(== initialContextId.192.180.45.11.1). |
| view-name | Name of a previously defined view. The view defines the objects available to the context. |
To enable the router to send SNMP traps, use the snmp-server enable global configuration command. The no form of this command disables sending SNMP traps.
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:
· bgp--Send Border Gateway Protocol (BGP) state change traps. · config--Send configuration traps. · frame-relay--Send Frame Relay traps. · isdn--Send ISDN traps. · envmon--Send Cisco enterprise-specific environmental monitor traps when an environmental threshold is exceeded. When envmon is selected, you can specify a trap-option. · repeater--Send Ethernet hub repeaters. When repeater is selected, you can specify a trap-option. · syslog--Send error message traps (Cisco Syslog MIB). Specify the level of messages to be sent with the logging history level command. |
| 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. |
To specify the recipient of an SNMP trap operation, use the snmp-server host global configuration command. The no form of this command removes the specified host.
snmp-server host host community-string [trap-type]| 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:
· bgp--Send Border Gateway Protocol (BGP) state change traps. · 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. · syslog--Send error message traps (Cisco Syslog MIB). Specify the level of messages to be sent with the logging history level command. · tty--Send Cisco enterprise-specific traps when a TCP connection closes. · x25--Send X.25 event traps. |
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. |
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. |
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 [protocol-address] [packetsize size]| 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.192.180.34.54.1 (= initialPartyId.192.180.34.54.1). |
| 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.
In future releases, additional protocols will be supported. This value is used to specify the destination of trap messages. |
| 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. |
| 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. |
| 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 will be authenticated using the SNMP v2 MD5 authentication method with the key specified by key. |
| clock clock | (Optional) Initial value of the authentication clock. |
| lifetime lifetime | (Optional) Lifetime, in seconds, that represents the upper bound on acceptable delivery delay for messages generated by the party. |
| snmpv1 string | (Optional) Community string. The keyword snmpv1 indicates that the party uses community-based authentication. All messages sent to this party will be authenticated using the SNMP v1community string specified by string instead of MD5. |
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. |
To use the SNMP message reload feature, the router 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-shutdownTo 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 will be sent to SNMPv1 management stations only. |
| snmpv2 | (Optional) Indicates that SNMP authentication traps will be sent to SNMPv2 management stations only. |
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. |
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. |
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 oid-tree {included | excluded}| view-name | Label for the view record that you are updating or creating. The name is used to reference the record. |
| oid-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. |
To set the time interval for each statistics distribution kept for the response time reporter, use the statistics-distribution-interval response time reporter configuration command. Use the no form of this command to return to the default value.
statistics-distribution-interval milliseconds| milliseconds | Number of milliseconds used for each statistics distribution kept. The default is 20 ms. |
To create a user-specified identifier for a response time reporter probe, use the tag response time reporter configuration command. It is normally used to logically link probes together in a group. Use the no form of this command to remove a tag from a probe.
tag text| text | Name of a group that this probe belongs to. From 0 to 16 ASCII characters. |
To test Flash memory on MCI and envm Flash EPROM interfaces, use the test flash EXEC command.
test flashTo test the system interfaces on the modular router, use the test interfaces EXEC command.
test interfacesTo perform a test of Multibus memory (including nonvolatile memory) on the modular router, use the test memory EXEC command.
test memoryTo set the rising threshold (hysteresis) that generates a reaction event and stores history information for the response time reporter probe, use the threshold response time reporter configuration command. Use the no form of this command to return to the default value.
threshold millisecond| millisecond | Number of milliseconds required for a rising threshold to be declared. The default value is 5000 ms. |
To set the amount of time the response time reporter probe waits for a response from its request packet, use the timeout response time reporter configuration command. Use the no form of this command to return to the default value.
timeout millisecond| millisecond | Number of milliseconds the probe waits to receive a response from its request packet. The default is 5000 ms. |
Use the trace EXEC command to discover the routes that packets will actually take when traveling to their destination.
trace [protocol] [destination]| protocol | (Optional) Protocols that can be used are appletalk, clns, ip and vines. |
| destination | (Optional) Destination address or host name on the command line. The default parameters for the appropriate protocol are assumed and the tracing action begins. |
Use the trace EXEC command to discover the IP routes that packets will actually take when traveling to their destination.
trace [protocol] [destination]| protocol | (Optional) Protocols that can be used are appletalk, clns, ip and vines. |
| destination | (Optional) Destination address or host name on the command line. The default parameters for the appropriate protocol are assumed and the tracing action begins. |
To configure a Frame Relay subinterface to estimate the available bandwidth when backward explicit congestion notifications (BECNs) are received, use the traffic-shape adaptive interface configuration command. Use the no form of this command to stop adapting to congestion signals.
traffic-shape adaptive [bit-rate]| bit-rate | (Optional) Lowest bit rate that traffic is shaped to in kbps. The default is half the value specified for the traffic-shape rate or traffic-shape group bit-rate option. |
To enable traffic shaping based on a specific access list for outbound traffic on an interface, use the traffic-shape group interface configuration command. Use the no form of this command to disable traffic shaping on the interface for the access list.
traffic-shape group access-list bit-rate [burst-size [excess-burst-size]]| access-list | Number of the access list that controls the packets that traffic shaping is applied to on the interface. |
| bit-rate | Bit rate that traffic is shaped to in bps. This is the access bit rate that you contract with your service provider or the service level you intend to maintain. |
| burst-size | (Optional) Sustained number of bits that can be transmitted per interval. On Frame Relay interfaces, this is the committed burst size contracted with your service provider. The default is the bit-rate divided by 8. |
| excess-burst-size | (Optional) Maximum number of bits that can exceed the burst size in the first interval in a congestion event. On Frame Relay interfaces, this is the excess burst size contracted with your service provider. The default is equal to the burst-size. |
To enable traffic shaping for outbound traffic on an interface, use the traffic-shape rate interface configuration command. Use the no form of this command to disable traffic shaping on the interface.
traffic-shape rate bit-rate [burst-size [excess-burst-size]]| bit-rate | Bit rate that traffic is shaped to in kbps. This is the access bit rate that you contract with your service provider or the service level you intend to maintain. |
| burst-size | (Optional) Sustained number of bits that can be transmitted per interval. On Frame Relay interfaces, this is the committed burst size contracted with your service provider. The default is the bit-rate divided by 8. |
| excess-burst-size | (Optional) Maximum number of bits that can exceed the burst size in the first interval in a congestion event. On Frame Relay interfaces, this is the excess burst size contracted with your service provider. The default is equal to the burst-size. |
To configure the type of response time reporter probe, use the type response time reporter configuration command. You must configure the probe's type before you can configure any of the other characteristics of the probe. Use the no form of this command to remove all response time reporter configuration information for a probe and return all other response time reporter configuration commands to their default values.
type {echo | pathEcho} protocol type type-target| echo | Perform end-to-end response time reporter operations only. |
| pathEcho | Perform response time reporter operations by using a route discovery algorithm to find a path to the destination and echo each device on the path. |
| protocol type type-target | Protocol used by the probe. Type can be one of the following keywords (whether the keyword is available depends on the Cisco IOS software features installed on your router) followed by the required type parameter:
· ipIcmpEcho {ip-address | ip-host-name}--IP/ICMP Echo that requires a destination IP address or IP host name. · snaRUEcho sna-host-name--SNA's SSCP Native Echo that requires the host name defined for the SNA's Physical Unit connection to VTAM. · snaLU0EchoAppl sna-host-name [sna-application] [sna-mode]--An SNA LU Type 0 connection to Cisco's NSPECHO host application that requires the host name defined for the SNA's Physical Unit connection to VTAM. Optionally specify the host application name (the default is NSPECHO) and SNA mode to access the application. · snaLU2EchoAppl sna-host-name [sna-application] [sna-mode]--An SNA LU Type 2 connection to Cisco's NSPECHO host application that requires the host name defined for the SNA's Physical Unit connection to VTAM. Optionally specify the host application name (the default is NSPECHO), and SNA mode to access the application. |
To cause the response time reporter probe to check each response for corruption, use the verify-data response time reporter configuration command. Use the no form of this command to return to the default value.
verify-data
|
|