Table Of Contents
type dhcp
type dlsw
type dns
type echo
type frame-relay
type ftp
type http
type jitter
type pathEcho
type pathJitter
type slm controller
type slm frame-relay interface
type slm frame-relay pvc interface
type slm interface
type tcpConnect
type udpEcho
undelete
upgrade rom-monitor file
upgrade rom-monitor preference
vacant-message
verify
verify-data
vrf (SAA)
where
width
write core
write erase
write memory
write mib-data
write network
write terminal
xmodem
xsm
xsm dvdm
xsm edm
xsm history edm
xsm history vdm
xsm privilege configuration level
xsm privilege monitor level
xsm vdm
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
source-ipaddr source-ip-address
|
(Optional) Source name or IP address.
|
dest-ipaddr dest-ip-address
|
(Optional) Destination name or IP address.
|
option decimal-option
|
(Optional) Option number. The only currently valid value is 82. DHCP option 82 allows you to specify the circuit-id, remote-id, and/or the subnet-mask for the destination DHCP server.
|
circuit-id circuit-id
|
(Optional) Circuit ID in hexadecimal.
|
remote-id remote-id
|
(Optional) Remote ID in hexadecimal.
|
subnet-mask subnet-mask
|
(Optional) Subnet mask IP address. The default value is 255.255.255.0.
|
Defaults
No SAA operation type is associated with the operation number being configured.
Command Modes
SAA RTR configuration
Command History
Release
|
Modification
|
12.0(5)T
|
This command was introduced.
|
12.1(1)T
|
The following keywords were added:
• source-ipaddr
• dest-ipaddr
• option 82
|
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)# type dhcp option 82 circuit-id 10005A6F1234
Router(config)# ip dhcp-server 172.16.20.3
Related Commands
Command
|
Description
|
ip dhcp-server
|
Specifies which DHCP servers to use on a network, and specifies the IP address of one or more DHCP servers available on the network.
|
rtr
|
Specifies an SAA operation and enters SAA RTR configuration mode.
|
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
peer-ipaddr
|
Peer destination.
|
ip-address
|
IP address.
|
Defaults
No SAA operation type is associated with the operation number being configured.
Command Modes
SAA RTR configuration
Command History
Release
|
Modification
|
12.0(5)T
|
This command was introduced.
|
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)# type dlsw peer-ipaddr 172.21.27.11
Router(config-rtr)# request-data-size 15
Related Commands
Command
|
Description
|
request-data-size
|
Sets the protocol data size in the payload of the SAA operation's request packet.
|
rtr
|
Specifies an SAA operation and enters SAA RTR configuration mode.
|
show dlsw peers
|
Displays DLSw peer information.
|
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
Release
|
Modification
|
12.0(5)T
|
This command was introduced.
|
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)# type dns target-addr lethe name-server 172.20.2.132
Related Commands
Command
|
Description
|
rtr
|
Specifies an SAA operation and enters SAA RTR configuration mode.
|
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
protocol protocol-type target
|
Protocol used by the operation. The protocol-type target argument combination must take one of the following forms:
• ipIcmpEcho {ip-address | hostname}—IP/ICMP Echo. Requires a destination IP address or IP host name.
• snaRUEcho sna-hostname—SNA's SSCP Native Echo. Requires the host name defined for the SNA's PU connection to VTAM.
• snaLU0EchoAppl sna-hostname [sna-application] [sna-mode]— SNA LU type 0 connection to Cisco's NSPECHO host application that requires the host name defined for the SNA's PU connection to VTAM. Optionally, specify the host application name (the default is NSPECHO) and SNA mode to access the application.
• snaLU2EchoAppl sna-hostname [sna-application] [sna-mode]— SNA LU type 2 connection to Cisco's NSPECHO host application that requires the host name defined for the SNA's PU connection to VTAM. Optionally, specify the host application name (the default is NSPECHO) and SNA mode to access the application.
|
source-ipaddr ipaddr
|
(Optional) Specifies an IP address as the source for the operation.
|
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
Release
|
Modification
|
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
Keywords are not case sensitive and are shown in mixed case for readability only.
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)# type echo protocol ipIcmpEcho 172.16.1.175
Related Commands
Command
|
Description
|
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
interface interface-id
|
Specifies the Frame Relay interface from which the operation will be sent. The interface-id argument should consist of the interface type and identification number (for example, serial 1/0).
|
dlci dlci-number
|
Specifies the Frame Relay PVC subinterface link that is assigned to the interface.
|
Defaults
No SAA operation type is associated with the operation number being configured.
Command Modes
RTR Entry configuration mode
Command History
Release
|
Modification
|
12.2(2)T
|
This command was introduced.
|
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)# type frame-Relay interface Serial0 dlci 22
Related Commands
Command
|
Description
|
rtr
|
Specifies an SAA operation and enters SAA RTR configuration mode.
|
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
operation get
|
Specifies an FTP GET operation. (Support for other FTP operation types may be added in future releases.)
|
url url
|
Location information for the file to retrieve.
|
source-ipaddr source-ip-address
|
(Optional) Source address of the operation.
|
mode
|
(Optional) Specifies the transfer mode, either active or passive.
|
passive
|
FTP passive transfer mode. This is the default.
|
active
|
FTP active transfer mode.
|
Defaults
No SAA operation type is associated with the operation number being configured.
Command Modes
SAA RTR configuration
Command History
Release
|
Modification
|
12.1(1)T
|
This command was introduced.
|
Usage Guidelines
GET is the only valid operation value. The URL must be in one of the following formats:
•
ftp://user:password@host/filename
•
ftp://host/filename
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)# type ftp operation get ftp://joe:young@zxq/test
Related Commands
Command
|
Description
|
show rtr collection-statistics
|
Displays statistical errors for all SAA operations or the specified operation.
|
show rtr operational-state
|
Displays the operational state of all SAA operations or the specified operation.
|
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
operation get
|
Specifies an HTTP GET operation.
|
operation raw
|
Specifies an HTTP RAW operation.
|
url url
|
Specifies the URL of destination HTTP server.
|
name-server
|
(Optional) Specifies name of destination Domain Name Server.
|
ip-address
|
(Optional) IP address of Domain Name Server.
|
version
|
(Optional) Specifies version number.
|
version-number
|
(Optional) Version number.
|
source-ipaddr
|
(Optional) Specifies source name or IP address.
|
name
|
Source name.
|
ip-address
|
Source IP address.
|
source-port
|
(Optional) Specifies source port.
|
port-number
|
(Optional) Source port number.
|
cache
|
(Optional) Enables or disables download of cached HTTP page.
|
enable
|
Enables downloads of cached HTTP page.
|
disable
|
Disables download of cached HTTP page.
|
proxy
|
(Optional) Proxy information.
|
proxy-url
|
(Optional) Proxy information or URL.
|
Defaults
No SAA operation type is associated with the operation number being configured.
Command Modes
SAA RTR configuration
Command History
Release
|
Modification
|
12.0(5)T
|
This command was introduced.
|
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)# type http operation get url http://www.cisco.com
Router(config)# rtr schedule 5 start-time now
HTTP 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)# type http operation raw url http://www.cisco.com
Router(config-rtr)# http-raw-request
Router(config-rtr-http)# GET /index.html HTTP/1.0\r\n
Router(config-rtr-http)# \r\n
Router(config-rtr-http)# exit
Router(config)# rtr schedule 6 start-time now
HTTP 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)# type http operation raw url http://www.proxy.cisco.com
Router(config-rtr)# http-raw-request
Router(config-rtr-http)# GET http://www.example.com HTTP/1.0\r\n
Router(config-rtr-http)# \r\n
Router(config-rtr-http)# exit
Router(config)# rtr schedule 6 start-time now
Related Commands
Command
|
Description
|
rtr
|
Specifies an SAA operation and enters SAA RTR configuration mode.
|
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
dest-ipaddr
|
Destination for the operation.
|
name
|
Destination IP host name.
|
ip-address
|
Destination IP address.
|
dest-port
|
Destination port.
|
port-number
|
Port number of the destination port.
|
source-ipaddr
|
(Optional) Source IP address.
|
name
|
IP host name.
|
ip-address
|
IP address.
|
source-port
|
(Optional) Source port.
|
port-number
|
Port number of the source.
|
control
|
(Optional) Combined with the enable or disable keyword, enables or disables sending a control message to the destination port.
|
enable
|
Enables the SAA to send a control message to the destination port prior to sending a probe packet. This is the default value.
|
disable
|
Disables sending of control messages to the responder prior to sending a probe packet.
|
num-packets number-of-packets
|
(Optional) Number of packets, as specified by the number argument. The default value is 10.
|
interval inter-packet-interval
|
(Optional) Interpacket interval in milliseconds. The default value of the inter-packet-interval argument is 20 ms.
|
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
Release
|
Modification
|
12.0(5)T
|
This command was introduced.
|
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)# type jitter dest-ip 172.30.125.15 dest-port 2000 num-packets 20
interval 20
Related Commands
Command
|
Description
|
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
protocol ipIcmpEcho
|
Specifies an IP/ICMP Echo operation. This is currently the only protocol type supported for the SAA Path Echo operation.
|
ip-address
|
Specifies the IP address of the target device.
|
ip-hostname
|
Specifies the designated IP name of the target device.
|
Defaults
No SAA operation type is associated with the operation number being configured.
Command Modes
SAA RTR configuration
Command History
Release
|
Modification
|
11.2
|
This command was introduced.
|
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)# type pathEcho protocol ipIcmpEcho 172.16.1.175
Related Commands
Command
|
Description
|
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
dest-ipaddress ip-address
|
Specifies the destination (target) IP address or host name.
|
source-ipaddress source-ip
|
(Optional) Specifies the source IP address that will be used for the operational probe packets.
|
num-packets packet-number
|
(Optional) The number of packets to be transmitted in each operation. The default value is 10.
|
interval time-ms
|
(Optional) Time interval between packets (in milliseconds). The default value is 20 ms.
|
targetOnly
|
(Optional) Sends test packets to the destination only (path is not traced).
|
Defaults
No SAA operation type is associated with the operation number being configured.
Command Modes
SAA RTR configuration
Command History
Release
|
Modification
|
12.2(2)T
|
This command was introduced.
|
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-rtr)# type pathJitter dest-ipaddr 172.69.1.129
The 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-rtr)# type pathJitter 172.69.5.6 num-packets 50 interval 30 targetOnly
type 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
Release
|
Modification
|
12.2(15)T
|
This command was introduced for T3 and E3 controllers using ATM. This command replaces the type t1-slm command.
|
12.3(1)
|
Support for controllers configured for Frame Relay was added.
|
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# configure terminal
Enter configuration commands, one per line.
Router(config)# rtr slm frame-relay statistics
Router(config-rtr)# type slm controller T1 0
Router(config-rtr-slm-if)# enhanced-history interval 900 buckets 100
Router(config-rtr-slm-if)# exit
Router(config)# rtr schedule 1 start-time now life forever
Router# show rtr configuration 1 | include Type
Type of operation to perform: slm controller
Related Commands
Command
|
Description
|
rtr
|
Allows configuration of SAA operations by entering SAA RTR configuration mode for the specified operation number.
|
show rtr enhanced-history collection-statistics
|
Displays data for all collected history buckets for the specified SAA operation, with data for each bucket shown individually.
|
show rtr enhanced-history distribution-statistics
|
Displays enhanced history data for all collected buckets in a summary table.
|
type slm interface
|
Specifies that the SAA operation is an SLM interface operation, and specifies the interface that the operation should be run on.
|
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
Release
|
Modification
|
12.3(1)
|
This command was introduced.
|
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# configure terminal
Enter configuration commands, one per line.
Router(config)# rtr slm frame-relay statistics
Router(config-rtr)# type slm frame-relay interface Serial0:0
Router(config-rtr-slm-fr-if)# enhanced-history interval 900 buckets 100
Router(config-rtr-slm-fr-if)# exit
Router(config)# rtr schedule 2 start-time now life forever
Router# show rtr configuration 2 | include Type
Type of operation to perform: Slm Frame-relay Interface
Related Commands
Command
|
Description
|
rtr
|
Allows configuration of SAA operations by entering SAA RTR configuration mode for the specified operation number.
|
show rtr enhanced-history collection-statistics
|
Displays data for all collected history buckets for the specified SAA operation, with data for each bucket shown individually.
|
show rtr enhanced-history distribution-statistics
|
Displays enhanced history data for all collected buckets in a summary table.
|
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
interface-type interface-number
|
The interface type (Serial) and number. An intervening space is not required.
|
dlci-number
|
Data link connection identifier (DLCI) of the permanent virtual circuit (PVC) to be monitored.
|
Defaults
No SAA operation type is associated with the operation number being configured.
Command Modes
SAA RTR configuration mode
Command History
Release
|
Modification
|
12.3(1)
|
This command was introduced.
|
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# configure terminal
Enter configuration commands, one per line.
Router(config)# rtr slm frame-relay statistics
Router(config-rtr)# type slm frame-relay pvc interface Serial0:0 111
Router(config-rtr-slm-fr-dlci)# enhanced-history interval 900 buckets 100
Router(config-rtr-slm-fr-dlci)# exit
Router(config)# rtr schedule 3 start-time now life forever
Router# show rtr configuration 3 | include Type
Type of operation to perform: Slm Frame-relay Pvc
Related Commands
Command
|
Description
|
rtr
|
Allows configuration of SAA operations by entering SAA RTR configuration mode for the specified operation number.
|
show rtr enhanced-history collection-statistics
|
Displays data for all collected history buckets for the specified SAA operation, with data for each bucket shown individually.
|
show rtr enhanced-history distribution-statistics
|
Displays enhanced history data for all collected buckets in a summary table.
|
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
Release
|
Modification
|
12.2(11)T
|
This command was introduced to support ATM SLM operations.
|
12.2(13)T
|
This command was updated to support T1 IMA (ATM) interfaces.
|
12.3(1)
|
This command was updated to support FR SLM operations (Serial interfaces).
|
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# configure terminal
Enter configuration commands, one per line.
Router(config)# rtr slm frame-relay statistics
Router(config-rtr)# type slm interface Serial 0.1
Router(config-rtr-slm-if)# enhanced-history interval 900 buckets 100
Router(config-rtr-slm-if)# exit
Router(config)# rtr schedule 1 start-time now life forever
Router# show rtr configuration 1 | include Type
Type of operation to perform: slm interface
Related Commands
Command
|
Description
|
rtr
|
Allows configuration of SAA operations by entering SAA RTR configuration mode for the specified operation number.
|
show rtr enhanced-history collection-statistics
|
Displays data for all collected history buckets for the specified SAA operation, with data for each bucket shown individually.
|
show rtr enhanced-history distribution-statistics
|
Displays enhanced history data for all collected buckets in a summary table.
|
type slm controller
|
Specifies that the SAA operation is an SLM controller operation, and specifies the controller that the operation should be run on.
|
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
dest-ipaddr name | ip-address
|
|