-
Cisco IOS Configuration Fundamentals and Network Management Command Reference, Release 12.3
-
Introduction
-
CFR Commands: absolute -- clock timezone
-
CFR Commands: clock update-calendar -- escape-character
-
CFR Commands: exception core-file -- ip ftp passive
-
CFR Commands: ip ftp password -- lsr-path
-
CFR Commands: memory sanity -- periodic
-
CFR Commands: ping -- service sequence numbers
-
CFR Commands: service slave-log -- show
tee -
CFR Commands: show context -- show ip http server
-
CFR Commands: show kron schedule -- show rtr enhanced-history
-
12.3 CF CR Commands: show rtr distributions-statistics -- snmp-server enable informs
-
CFR Commands: snmp-server enable traps -- statistics-distribution-interval
-
CFR Commands: stopbits -- ttl ip
-
CFR Commands: type dhcp - xsm vdm
-
CFR Appendix: ASCII Character Set and Hex Values
-
Table Of Contents
type slm frame-relay interface
type slm frame-relay pvc interface
upgrade rom-monitor preference
xsm privilege configuration level
type dhcp
To configure a Dynamic Host Configuration Protocol Service Assurance Agent (SAA) operation, use the type dhcp command in SAA RTR configuration mode. To disable a DHCP SAA operation, use the no form of this command.
type dhcp [source-ipaddr source-ip-address] [dest-ipaddr dest-ip-address] [option decimal-option [circuit-id circuit-id] [remote-id remote-id] [subnet-mask subnet-mask]]
no type dhcp
Syntax Description
Defaults
No SAA operation type is associated with the operation number being configured.
Command Modes
SAA RTR configuration
Command History
12.0(5)T
This command was introduced.
12.1(1)T
The following keywords were added:
•
source-ipaddr
•
•
Usage Guidelines
You must configure the type of operation before you can configure any of the other characteristics of the operation.
If the source IP address is configured, then packets will be sent with that source address.
You may configure the ip dhcp-server command to identify the DHCP server that the DHCP operation will measure.
If the target IP address is configured, then only that device will be measured.
If the ip dhcp-server command is not configured and the target IP address is not configured, then DHCP discover packets will be sent on every available IP interface.
Option 82 is called the Relay Agent Information option and is inserted by the DHCP relay agent when forwarding client-originated DHCP packets to a DHCP server. Servers recognizing the Relay Agent Information option may use the information to implement IP address or other parameter assignment policies. The DHCP Server echoes the option back verbatim to the relay agent in server-to-client replies, and the relay agent strips the option before forwarding the reply to the client.
The Relay Agent Information option is organized as a single DHCP option that contains one or more suboptions that convey information known by the relay agent. The initial sub-options are defined for a relay agent that is co-located in a public circuit access unit. These suboptions are as follows: a circuit-id for the incoming circuit, a remote-id which provides a trusted identifier for the remote high-speed modem, and a subnet-mask designation for the logical IP subnet from which the relay agent received the client DHCP packet.
If an odd number of characters are specified for the circuit-id, a zero will be added to the end of the string.
Examples
In the following example, SAA operation number 4 is configured as a DHCP operation enabled for DHCP server 172.16.20.3:
Router(config)# rtr 4Router(config-rtr)# type dhcp option 82 circuit-id 10005A6F1234Router(config-rtr)# exitRouter(config)# ip dhcp-server 172.16.20.3Related Commands
type dlsw
To configure a data-link switching (DLSw) Service Assurance Agent (SAA) operation, use the type dlsw command in SAA RTR configuration mode. To remove the type configuration for the operation, use the no form of this command.
type dlsw peer-ipaddr ip-address
no type dlsw peer-ipaddr ip-address
Syntax Description
Defaults
No SAA operation type is associated with the operation number being configured.
Command Modes
SAA RTR configuration
Command History
Usage Guidelines
In order to configure a DLSw operation, the DLSw feature must be configured on the local and target routers.
You must configure the type of operation before you can configure any of the other characteristics of the operation.
The default for the optional characteristic request-data-size for a DLSw SAA operation is 0 bytes.
The default for the optional characteristic timeout for a DLSw SAA operation is 30 seconds.
Examples
In the following example, SAA operation number 4 is configured as a DLSw operation enabled for remote peer IP address 172.21.27.11. The data size is 15 bytes.
Router(config)# rtr 4Router(config-rtr)# type dlsw peer-ipaddr 172.21.27.11Router(config-rtr)# request-data-size 15Related Commands
type dns
To configure a Domain Name System (DNS) Service Assurance Agent (SAA) operation, use the type dns command in SAA RTR configuration mode. To remove the type configuration for the operation, use the no form of this command.
type dns target-addr {ip-address | hostname} name-server ip-address
no type dns target-addr {ip-address | hostname} name-server ip-address
Syntax Description
target-addr {ip-address | hostname}
Target (destination) IP address or hostname.
name-server ip-address
IP address of the Domain Name Server.
Defaults
No SAA operation type is associated with the operation number being configured.
Command Modes
SAA RTR configuration
Command History
Usage Guidelines
You must configure the type of operation before you can configure any of the other characteristics of the operation.
Examples
In the following example, SAA operation 7 is created and configured as a DNS operation using the target IP address 172.20.2.132:
Router(config)# rtr 7Router(config-rtr)# type dns target-addr lethe name-server 172.20.2.132Related Commands
type echo
To configure an Service Assurance Agent (SAA) end-to-end echo response time probe operation, use the type echo command in SAA RTR configuration mode. To remove the operation from the configuration, use the no form of this command.
type echo protocol protocol-type target [source-ipaddr ip-address]
no type echo protocol protocol-type target [source-ipaddr ip-address]
Syntax Description
Defaults
The default SNA host sna-application name for an SNA LU type echo is NSPEcho.
The default data size for a IP/ICMP echo operation is 28 bytes.Command Modes
SAA RTR configuration
Command History
11.2
This command was introduced.
12.0(5)T
The source-ipaddr ip-address keyword/argument combination was added to support the specification of an IP source for the operation.
Usage Guidelines
Support of echo to a protocol and pathEcho to a protocol is dependent on the protocol type and implementation. In general most protocols support echo and few protocols support pathEcho.
Note
Prior to sending a operation packet to the responder, the SAA sends a control message to the Responder to enable the destination port.
The default for the optional characteristic request-data-size for a ipIcmpEcho operation is 28 bytes. This is the payload portion of the Icmp packet, which makes a 64 byte IP packet.
Examples
In the following example, operation 10 is created and configured as an echo probe using the IP/ICMP Echo protocol and the destination IP address 172.16.1.175:
Router(config)# rtr 10Router(config-rtr)# type echo protocol ipIcmpEcho 172.16.1.175Related Commands
rtr
Specifies an SAA operation and enters SAA RTR configuration mode.
show rtr configuration
Displays configuration values for RTR operations.
type frame-relay
To measure response time, frame loss, or data corruption across a Frame Relay permanent virtual circuit (PVC) using the Service Assurance Agent (SAA), use the type frame-relay command in global configuration mode. To delete a preconfigured frame-relay operation, use the no form of this command.
type frame-relay interface interface-id dlci dlci-number
no type frame-relay interface interface-id dlci dlci-number
Syntax Description
Defaults
No SAA operation type is associated with the operation number being configured.
Command Modes
RTR Entry configuration mode
Command History
Usage Guidelines
The SAA Responder must be enabled on the target router before this command is used. Use the rtr responder type frame-relay all global configuration command or the rtr responder global configuration command on the target router to enable the responder.
If the first measurement does not have the correct values for frames sent and frames lost, the Frame Relay monitoring operation cannot work properly. There need to be at least two successful measurements for the frames sent and frames lost to be correct.
If the encapsulation on the target interface is not Frame Relay (for example, if the encapsulation is changed), the Frame Relay operation will be removed automatically from the configuration.
Examples
In the following example, a Frame Relay monitoring operation is configured to be sent from serial interface 0/1 using DLCI subinterface 22:
Router(config)# rtr 1Router(config-rtr)# type frame-Relay interface Serial0 dlci 22Related Commands
type ftp
To configure an FTP operation, use the type ftp command in SAA RTR configuration mode. To remove the type configuration for the operation, use the no form of this command.
type ftp operation get url url [source-ipaddr source-ip-address] [mode {passive | active}]
no type ftp operation get url url [source-ipaddr source-ip-address] [mode {passive | active}]
Syntax Description
Defaults
No SAA operation type is associated with the operation number being configured.
Command Modes
SAA RTR configuration
Command History
Usage Guidelines
GET is the only valid operation value. The URL must be in one of the following formats:
•
•
If the user and password keywords are not specified, the defaults are anonymous and test, respectively.
Examples
In the following example, an FTP operation is configured. Joe is the user and Young is the password. zxq is the host and test is the file name.
Router(config)# rtr 3Router(config-rtr)# type ftp operation get ftp://joe:young@zxq/testRelated Commands
type http
To configure a Hypertext Transfer Protocol (HTTP) Service Assurance Agent (SAA) operation, use the type http command in SAA RTR configuration mode. To remove the type configuration for the operation, use the no form of this command.
type http operation {get | raw} url url [name-server ip-address] [version version-number] [source-ipaddr {name | ip-address}] [source-port port-number] [cache {enable | disable}] [proxy proxy-url]
no type http operation {get | raw} url url [name-server ip-address] [version version-number] [source-ipaddr {name | ip-address}] [source-port port-number] [cache {enable | disable}] [proxy proxy-url]
Syntax Description
Defaults
No SAA operation type is associated with the operation number being configured.
Command Modes
SAA RTR configuration
Command History
Usage Guidelines
You must configure the type of operation before you can configure any of the other characteristics of the operation.
Examples
HTTP GET operation
In this example operation 5 is created and configured as an HTTP GET operation. The destination URL is http://www.cisco.com.
Router(config)# rtr 5Router(config-rtr)# type http operation get url http://www.cisco.comRouter(config-rtr)# exitRouter(config)# rtr schedule 5 start-time nowHTTP RAW operation using RAW submode
In this example operation 6 is created and configured as an HTTP RAW operation. To use the raw request commands, HTTP-RAW submode is entered using the http-raw-request command. The RTR HTTP-RAWsubmode is indicated by the (config-rtr-http) router prompt.
Router(config)# rtr 6Router(config-rtr)# type http operation raw url http://www.cisco.comRouter(config-rtr)# http-raw-requestRouter(config-rtr-http)# GET /index.html HTTP/1.0\r\nRouter(config-rtr-http)# \r\nRouter(config-rtr-http)# exitRouter(config)# rtr schedule 6 start-time nowHTTP RAW operation through a Proxy Server
In this example http://www.proxy.cisco.com is the proxy server and http://www.yahoo.com is the HTTP Server:
Router(config)# rtr 6Router(config-rtr)# type http operation raw url http://www.proxy.cisco.comRouter(config-rtr)# http-raw-requestRouter(config-rtr-http)# GET http://www.example.com HTTP/1.0\r\nRouter(config-rtr-http)# \r\nRouter(config-rtr-http)# exitRouter(config)# rtr schedule 6 start-time nowRelated Commands
type jitter
To configure a jitter Service Assurance Agent (SAA) operation, use the type jitter command in SAA RTR configuration mode. To disable a jitter operation, use the no form of this command.
type jitter dest-ipaddr {name | ip-address} dest-port port-number [source-ipaddr {name | ip-address}] [source-port port-number] [control {enable | disable}] [num-packets number-of-packets] [interval inter-packet-interval]
no type jitter dest-ipaddr {name | ip-address} dest-port port-number [source-ipaddr {name | ip-address}] [source-port port-number] [control {enable | disable}] [num-packets number-of-packets] [interval inter-packet-interval]
Syntax Description
Defaults
No SAA operation type is associated with the operation number being configured.
The default for the optional characteristic request-data-size for a SAA Jitter operation is 32 bytes of UDP data.
Command Modes
SAA RTR configuration
Command History
Usage Guidelines
The type jitter command configures a UDP Plus SAA operation. The UDP Plus operation is a superset of the UDP echo operation. In addition to measuring UDP round trip time, the UDP Plus operation measures per-direction packet-loss and jitter (inter-packet delay variance). Packet loss is a critical element in SLAs, and Jitter statistics are useful for analyzing traffic in a VoIP network.
You must enable the SAA RTR Responder on the target router (using the rtr responder command) before you can configure a Jitter operation. Prior to sending a operation packet to the responder, the SAA sends a control message to the SAA RTR Responder to enable the destination port.
You must configure the type of operation before you can configure any of the other characteristics of the operation.
Examples
In the following example, operation 6 is created and configured as a Jitter operation using the destination IP address 172.30.125.15, the destination port number 2000, 20 packets, and an interval of 20:
Router(config)# rtr 6Router(config-rtr)# type jitter dest-ip 172.30.125.15 dest-port 2000 num-packets 20 interval 20Related Commands
request-data-size
Sets the payload size for SAA operation requests.
rtr
Specifies an SAA operation and enters SAA RTR configuration mode.
type pathEcho
To configure an Internet Protocol/Internet Control Message Protocol (IP/ICMP) Path Echo Service Assurance Agent (SAA) operation, use the type pathEcho command in SAA RTR configuration mode. To remove the operation from the configuration, use the no form of this command.
type pathEcho protocol ipIcmpEcho {ip-address | ip-hostname}
no type pathEcho protocol ipIcmpEcho {ip-address | ip-hostname}
Syntax Description
Defaults
No SAA operation type is associated with the operation number being configured.
Command Modes
SAA RTR configuration
Command History
Usage Guidelines
Keywords are not case sensitive and are shown in mixed case for readability only.
Examples
In the following example, SAA operation 10 is created and configured as pathEcho probe using the IP/ICMP Echo protocol and the destination IP address 172.16.1.175:
Router(config)# rtr 10Router(config-rtr)# type pathEcho protocol ipIcmpEcho 172.16.1.175Related Commands
rtr
Specifies an SAA operation and enters SAA RTR configuration mode.
show rtr configuration
Displays configuration values for RTR operations (probes).
type pathJitter
To configure an Service Assurance Agent (SAA) Path Jitter monitoring operation, use the type pathJitter command in RTR Entry configuration mode. To remove an inactive Path Jitter entry from the RTR configuration, use the no form of this command.
type pathJitter dest-ipaddress ip-address [source-ipaddress source-ip] [num-packets packet-number] [interval time-ms] [targetOnly]
no type pathJitter dest-ipaddress ip-address [source-ipaddress source-ip] [num-packets packet-number] [interval time-ms] [targetOnly]
Syntax Description
Defaults
No SAA operation type is associated with the operation number being configured.
Command Modes
SAA RTR configuration
Command History
Usage Guidelines
The Path Jitter SAA operation traces a specified IP path from the source to the destination and then sends a specified number of packets to each hop along the traced path. Optionally, the time interval between each test packet can be specified.
If the number of packets and the time interval are not specified, the path jitter operation will use the default values.
If the targetOnly keyword is not used, the path jitter operation will trace the "hop-by-hop" IP path from the source to the destination and send the specified number of test packets to each hop along the trace path, using the specified time interval between each test packet.
If the targetOnly keyword is used, the command will cause the pathJitter operation to send echos to the destination only (the path from the source to the destination is not traced).
Examples
The following example enables the Path Jitter operation to trace the IP path to the destination 172.69.1.129 and send ten test packets to each hop with an interval of 20 ms between each test packet:
Router# config terminalRouter(config)# rtr 1Router(config-rtr)# type pathJitter dest-ipaddr 172.69.1.129The following example enables the Path Jitter operation to send 50 test packets to 172.69.5.6 with an interval of 30 ms between each test packet:
Router# config terminalRouter(config)# rtr 2Router(config-rtr)# type pathJitter 172.69.5.6 num-packets 50 interval 30 targetOnlytype slm controller
To configure a Service Assurance Agent (SAA) operation as an SLM interface operation, and to specify the interface that the operation should be run on, use the type slm controller command in SAA RTR configuration mode. To remove or replace a previously configured SAA operation, use the no rtr operation-number global configuration command.
type slm controller controller-id
Syntax Description
controller-id
The controller type and slot/port number. Valid controller types include E1, E3, T1, and T3.
Defaults
No SAA operation type is associated with the operation number being configured.
Command Modes
SAA RTR configuration
Command History
Usage Guidelines
This SAA RTR configuration command specifies that the operation is an SLM physical controller operation, which provides information about the data link layer connection, and specifies the controller that the operation should be run on.
Controllers that can be monitored using this operation include T1, E1, T3, and E3.
The specified controller should be configured for Frame Relay or ATM.
Examples
In the following example, SAA operation 1 is configured as an SLM controller operation:
Router> enablePassword:Router# configure terminalEnter configuration commands, one per line.Router(config)# rtr slm frame-relay statisticsRouter(config)# rtr 1Router(config-rtr)# type slm controller T1 0Router(config-rtr-slm-if)# enhanced-history interval 900 buckets 100Router(config-rtr-slm-if)# exitRouter(config)# rtr schedule 1 start-time now life foreverRouter(config)# endRouter#Router# show rtr configuration 1 | include TypeType of operation to perform: slm controllerReaction Type: NoneRouter#Related Commands
type slm frame-relay interface
To configure a Service Assurance Agent (SAA) operation as an Service Level Management (SLM) Frame Relay (FR) interface operation, and to specify the interface that the operation should be run on, use the type slm frame-relay interface command in SAA RTR configuration mode. To remove or replace a previously configured SAA operation, use the no rtr operation-number global configuration command.
type slm frame-relay interface interface-type interface-number
Syntax Description
interface-type interface-number
The interface type (Serial) and number. An intervening space is not required.
Defaults
No SAA operation type is associated with the operation number being configured.
Command Modes
SAA RTR configuration
Command History
Usage Guidelines
The SAA SLM FR interface operation provides Frame Relay link (Layer 2) layer data. The type slm frame-relay interface command specifies the operation type and the interface that the operation should be run on. The specified interface should be configured for Frame Relay.
Frame Relay interface link statistics are used to monitor the basic health of a Frame Relay interface. This information includes some traffic counters, assorted error counts, and some performance-related counters.
To view the gathered statistics, use the show rtr enhanced-history distribution-statistics command or the show rtr enhanced-history collection-statistics command. Statistics gathered with this operation can also be retrieved from external network monitoring applications via the CNS event gateway.
Examples
In the following example, SAA operation 2 is configured as an SLM Frame Relay Interface operation:
Router> enablePassword:Router# configure terminalEnter configuration commands, one per line.Router(config)# rtr slm frame-relay statisticsRouter(config)# rtr 2Router(config-rtr)# type slm frame-relay interface Serial0:0Router(config-rtr-slm-fr-if)# enhanced-history interval 900 buckets 100Router(config-rtr-slm-fr-if)# exitRouter(config)# rtr schedule 2 start-time now life foreverRouter(config)# endRouter#Router# show rtr configuration 2 | include TypeType of operation to perform: Slm Frame-relay InterfaceReaction Type: NoneRelated Commands
type slm frame-relay pvc interface
To configure an Service Assurance Agent (SAA) operation as an Service Level Management (SLM)Frame Relay (FR) Circuit operation, and specify the interface that the operation should be run on, use the type slm frame-relay pvc interface command in SAA RTR configuration mode. To remove or replace a previously configured SAA operation, use the no rtr operation-number global configuration command.
type slm frame-relay pvc interface interface-type interface-number dlci-number
Syntax Description
Defaults
No SAA operation type is associated with the operation number being configured.
Command Modes
SAA RTR configuration mode
Command History
Usage Guidelines
This command specifies that the operation is an SAA SLM FR circuit operation, which provides data for the specified circuit. The specified interface should be configured with a permanent virtual circuit (PVC) connection.
The Frame Relay circuit statistics are used to monitor the basic health of a Frame Relay circuit. This information includes some traffic counters, assorted error counts, and some performance-related counters.
This command puts the CLI into SAA SLM FR Circuit configuration mode (config-rtr-slm-fr-dlci).
Examples
In the following example, SAA operation 3 is configured as an SLM Frame Relay Circuit (or PVC) operation:
Router> enablePassword:Router# configure terminalEnter configuration commands, one per line.Router(config)# rtr slm frame-relay statisticsRouter(config)# rtr 3Router(config-rtr)# type slm frame-relay pvc interface Serial0:0 111Router(config-rtr-slm-fr-dlci)# enhanced-history interval 900 buckets 100Router(config-rtr-slm-fr-dlci)# exitRouter(config)# rtr schedule 3 start-time now life foreverRouter(config)# endRouter#Router# show rtr configuration 3 | include TypeType of operation to perform: Slm Frame-relay PvcReaction Type: NoneRelated Commands
type slm interface
To configure a Service Assurance Agent (SAA) operation as an Service Level Management (SLM) interface operation, and to specify the interface that the operation should be run on, use the type slm interface command in SAA RTR configuration mode. To remove or replace a previously configured SAA operation, use the no rtr operation-number global configuration command.
type slm interface type number
Syntax Description
type number
The interface type and number. Interface types include Serial and FR-ATM. Alternatively, an Inverse Multiplexing over ATM (IMA) group number can be specified.
Defaults
No default behavior or values.
Command Modes
SAA RTR configuration
Command History
Usage Guidelines
The type slm interface SAA RTR configuration command specifies that the operation is an SLM physical interface operation, which provides information about the data link layer connection. The specified interface should be configured for Frame Relay or ATM.
Interfaces that can be monitored using this operation include Serial or HSSI (high speed serial interface) for Frame Relay interfaces, and IMA for ATM interfaces. To specify an HSSI interface, use the Serial keyword as the type.
In order for this operation to work, either the atm slm statistics global configuration command or the rtr slm frame-relay statistics global configuration command must be enabled on the device.
This command puts the CLI into SAA SLM controller/interface configuration mode, in which you can configure optional characteristics for the operation. To view the available options, enter the ? command at the (config-rtr-slm-if) prompt.
Examples
In the following example, SAA operation 1 is configured as an SLM interface operation for a Frame Relay interface:
Router> enablePassword:Router# configure terminalEnter configuration commands, one per line.Router(config)# rtr slm frame-relay statisticsRouter(config)# rtr 1Router(config-rtr)# type slm interface Serial 0.1Router(config-rtr-slm-if)# enhanced-history interval 900 buckets 100Router(config-rtr-slm-if)# exitRouter(config)# rtr schedule 1 start-time now life foreverRouter(config)# endRouter#Router# show rtr configuration 1 | include TypeType of operation to perform: slm interfaceReaction Type: NoneRouter#Related Commands
type tcpConnect
To define a tcpConnect probe, use the type tcpConnect command in Service Assurance Agent (SAA) RTR configuration mode. To remove the type configuration for the probe, use the no form of this command.
type tcpConnect dest-ipaddr {name | ip-address} dest-port port-number [source-ipaddr {name | ip-address} source-port port-number] [control {enable | disable}]
no type tcpConnect dest-ipaddr {name | ip-address} dest-port port-number
Syntax Description
