show auto discovery qos
To display the data collected during the Auto-Discovery (data collection) phase of the AutoQoS for the Enterprise feature, use the show auto discovery qos command in privileged EXEC mode.
show auto discovery qos [interface [type number]]
Syntax Description
interface |
(Optional) Indicates that the configurations for a specific interface type will be displayed. |
type number |
(Optional) Specifies the interface type and number. |
Command Default
Displays the configurations created for all interface types.
Command Modes
Privileged EXEC
Command History
|
|
12.3(7)T |
This command was introduced. |
12.3(11)T |
Command output was modified to include suggested policy map information. |
Usage Guidelines
The suggested policy output (shown in the example below) lets you preview class maps and policy maps before you issue the auto qos command on an interface. You can then continue with the Auto-Discovery phase until more data is gathered or you can cut and paste the existing data and edit it as desired.
Examples
The following is sample output from the show auto discovery qos command. This example displays the data collected during the Auto-Discovery (data collection) phase using DSCP classification in trusted mode and includes suggested policy map information.
Router# show auto discovery qos
AutoQoS Discovery enabled for trusted DSCP
Discovery up time: 2 hours, 42 minutes
AutoQoS Class information:
Recommended Minimum Bandwidth: 118 Kbps/1% (PeakRate)
DSCP value AverageRate PeakRate Total
(kbps/%) (kbps/%) (bytes)
----------- ----------- -------- ------------
46/ef 106/1 118/1 129510064
Recommended Minimum Bandwidth: 25 Kbps/<1% (AverageRate)
DSCP value AverageRate PeakRate Total
(kbps/%) (kbps/%) (bytes)
----------- ----------- -------- ------------
34/af41 25/<1 28/<1 31084292
Recommended Minimum Bandwidth: 50 Kbps/<1% (AverageRate)
DSCP value AverageRate PeakRate Total
(kbps/%) (kbps/%) (bytes)
----------- ----------- -------- ------------
24/cs3 50/<1 56/<1 61838040
Recommended Minimum Bandwidth: 79 Kbps/<1% (AverageRate)
DSCP value AverageRate PeakRate Total
(kbps/%) (kbps/%) (bytes)
----------- ----------- -------- ------------
32/cs4 79/<1 88/<1 96451788
Recommended Minimum Bandwidth: 105 Kbps/1% (AverageRate)
DSCP value AverageRate PeakRate Total
(kbps/%) (kbps/%) (bytes)
----------- ----------- -------- ------------
18/af21 105/1 117/1 127798678
Recommended Minimum Bandwidth: 132 Kbps/1% (AverageRate)
DSCP value AverageRate PeakRate Total
(kbps/%) (kbps/%) (bytes)
----------- ----------- -------- ------------
10/af11 132/1 147/1 160953984
Recommended Minimum Bandwidth: 24 Kbps (AverageRate)/0% (fixed)
DSCP value AverageRate PeakRate Total
(kbps/%) (kbps/%) (bytes)
----------- ----------- -------- ------------
8/cs1 24/<1 27/<1 30141238
Recommended Minimum Bandwidth: 34 Kbps/<1% (AverageRate)
DSCP value AverageRate PeakRate Total
(kbps/%) (kbps/%) (bytes)
----------- ----------- -------- ------------
16/cs2 34/<1 38/<1 41419740
Recommended Minimum Bandwidth: 7 Kbps/<1% (AverageRate)
DSCP value AverageRate PeakRate Total
(kbps/%) (kbps/%) (bytes)
----------- ----------- -------- ------------
Current Bandwidth Estimation: 820 Kbps/8% (AverageRate)
DSCP value AverageRate PeakRate Total
(kbps/%) (kbps/%) (bytes)
----------- ----------- -------- ------------
0/default 820/8 915/9 997576380
Suggested AutoQoS Policy based on a discovery uptime of 2 hours, 42 minutes:
class-map match-any AutoQoS-Voice-Trust
class-map match-any AutoQoS-Inter-Video-Trust
class-map match-any AutoQoS-Signaling-Trust
class-map match-any AutoQoS-Stream-Video-Trust
class-map match-any AutoQoS-Transactional-Trust
class-map match-any AutoQoS-Bulk-Trust
class-map match-any AutoQoS-Scavenger-Trust
class-map match-any AutoQoS-Management-Trust
class-map match-any AutoQoS-Routing-Trust
policy-map AutoQoS-Policy-S2/1.1Trust
class AutoQoS-Voice-Trust
class AutoQoS-Inter-Video-Trust
bandwidth remaining percent 1
class AutoQoS-Signaling-Trust
bandwidth remaining percent 1
class AutoQoS-Stream-Video-Trust
bandwidth remaining percent 1
class AutoQoS-Transactional-Trust
bandwidth remaining percent 1
bandwidth remaining percent 1
class AutoQoS-Scavenger-Trust
bandwidth remaining percent 1
class AutoQoS-Management-Trust
bandwidth remaining percent 1
class AutoQoS-Routing-Trust
bandwidth remaining percent 1
Table 39 describes the significant fields shown in the display.
Table 39 show auto discovery qos Field Descriptions
|
|
Serial2/1.1 |
The interface or subinterface on which data is being collected. |
AutoQoS Discovery enabled for trusted DSCP |
Indicates that the data collection phase of AutoQoS has been enabled. |
Discovery up time |
Indicates the period of time in which data was collected. |
AutoQoS Class information |
Displays information for each AutoQoS class. |
Class Voice |
Information for the named class, along with data pertaining to the detected applications. This data includes DSCP value, average rate (in kilobits per second (kbps)), peak rate (kbps), and total packets (bytes). |
Suggested AutoQoS Policy based on a discovery uptime of hours and minutes |
Policy-map and class-map statistics based on a specified discovery time. |
Related Commands
|
|
auto qos |
Installs the QoS class maps and policy maps created by the AutoQoS for the Enterprise feature. |
auto discovery qos |
Begins discovering and collecting data for configuring the AutoQoS for the Enterprise feature. |
show auto qos |
Displays the interface configurations, policy maps, and class maps created by AutoQoS on a specific interface or all interfaces. |
show auto qos
To display the interface configurations, policy maps, and class maps created by AutoQoS on a specific interface or all interfaces, use the show auto qos command in privileged EXEC mode.
show auto qos [interface [type slot/port]]
Syntax Description
interface |
(Optional) Displays the configurations created by the AutoQoS - VoIP feature on all the interfaces or PVCs on which the AutoQoS - VoIP feature is enabled. When the interface keyword is configured but an interface type is not specified, the show auto qos interface command displays the configurations created by the AutoQoS - VoIP feature on all the interfaces or Permanent Virtual Circuits (PVCs) on which the AutoQoS - VoIP feature is enabled. |
type |
(Optional) Specifies an interface type; valid values are atm, ethernet, fastethernet, ge-wan, gigabitethernet, pos, and tengigabitethernet. |
slot/port |
Module and port number. |
Command Default
Configurations created for all interface types are displayed.
Command Modes
Privileged EXEC (#)
Command History
|
|
12.2(15)T |
This command was introduced as part of the AutoQoS—VoIP feature. |
12.3(7)T |
This command was modified for the AutoQoS for the Enterprise feature. The command displays the classes, class maps, and policy maps created on the basis of the data collected during the Auto-Discovery phase of the AutoQoS for the Enterprise feature. |
12.2(33)SXH |
This command was integrated into Cisco IOS Release 12.2(33)SXH. |
Usage Guidelines
The show auto qos interface command can be used with Frame Relay data-link connection identifiers (DLCIs) and ATM permanent virtual circuits (PVCs).
When the AutoQoS—VoIP or the AutoQos for the Enterprise features are enabled, configurations are generated for each interface or PVC. These configurations are then used to create the interface configurations, policy maps, class maps, and access control lists (ACLs) for use on the network. The show auto qos command can be used to verify the contents of the interface configurations, policy maps, class maps, and ACLs.
Catalyst 6500 Series Switches
AutoQoS is supported on the following modules:
•WS-X6548-RJ45
•WS-X6548-RJ21
•WS-X6148-GE_TX
•WS-X6548-GE-TX-CR
•WS-X6148-RJ45V
•WS-X6148-RJ21V
•WS-X6348-RJ45
•WS-X6348-RJ21
•WS-X6248-TEL
Examples
show auto qos interface Command: Configured for the AutoQoS—VoIP Feature
When the interface keyword is configured along with the corresponding type slot/port argument, the show auto qos interface type slot/port command displays the configurations created by the AutoQoS—VoIP feature on the specified interface.
In the following example, the serial subinterface 6/1.1 has been specified:
Router# show auto qos interface serial6/1.1
frame-relay traffic-shaping
interface Serial6/1.1 point-to-point
frame-relay interface-dlci 100
class AutoQoS-VoIP-FR-Serial6/1-100
frame-relay ip rtp header-compression
map-class frame-relay AutoQoS-VoIP-FR-Serial6/1-100
frame-relay mincir 512000
service-policy output AutoQoS-Policy-UnTrust
When the interface keyword is configured but an interface type is not specified, the show auto qos interface command displays the configurations created by the AutoQoS—VoIP feature on all the interfaces or PVCs on which the AutoQoS—VoIP feature is enabled.
Router# show auto qos interface
frame-relay traffic-shaping
interface Serial6/1.1 point-to-point
frame-relay interface-dlci 100
class AutoQoS-VoIP-FR-Serial6/1-100
frame-relay ip rtp header-compression
map-class frame-relay AutoQoS-VoIP-FR-Serial6/1-100
frame-relay mincir 512000
service-policy output AutoQoS-Policy-UnTrust
interface ATM2/0.1 point-to-point
encapsulation aal5mux ppp Virtual-Template200
interface Virtual-Template200
ip address 10.10.107.1 255.255.255.0
service-policy output AutoQoS-Policy-UnTrust
ppp multilink fragment-delay 10
The following example displays all of the configurations created by the AutoQoS—VoIP feature:
frame-relay traffic-shaping
interface Serial6/1.1 point-to-point
frame-relay interface-dlci 100
class AutoQoS-VoIP-FR-Serial6/1-100
frame-relay ip rtp header-compression
map-class frame-relay AutoQoS-VoIP-FR-Serial6/1-100
frame-relay mincir 512000
service-policy output AutoQoS-Policy-UnTrust
Table 40 describes the significant fields shown in the display.
Table 40 show auto qos Field Descriptions (AutoQoS—VoIP Feature Configured)
|
|
class AutoQoS-VoIP-FR-Serial6/1-100 |
Name of the class created by the AutoQoS—VoIP feature. In this instance, the name of the class is AutoQoS-VoIP-FR-Serial6/1-100. |
service-policy output AutoQoS-Policy-UnTrust |
Indicates that the policy map called "AutoQoS-Policy-UnTrust" has been attached to an interface in the outbound direction of the interface. |
show auto qos interface Command: Configured for the AutoQoS for the Enterprise Feature
The following is sample output from the show auto qos command. This example displays the classes, class maps, and policy maps created on the basis of the data collected during the Auto-Discovery phase of the AutoQoS for the Enterprise feature.
policy-map AutoQoS-Policy-Se2/1.1
class AutoQoS-Voice-Se2/1.1
class AutoQoS-Inter-Video-Se2/1.1
bandwidth remaining percent 10
class AutoQoS-Stream-Video-Se2/1.1
bandwidth remaining percent 1
class AutoQoS-Transactional-Se2/1.1
bandwidth remaining percent 1
class AutoQoS-Scavenger-Se2/1.1
bandwidth remaining percent 1
policy-map AutoQoS-Policy-Se2/1.1-Parent
service-policy AutoQoS-Policy-Se2/1.1
class-map match-any AutoQoS-Stream-Video-Se2/1.1
class-map match-any AutoQoS-Transactional-Se2/1.1
class-map match-any AutoQoS-Voice-Se2/1.1
class-map match-any AutoQoS-Inter-Video-Se2/1.1
rmon event 33333 log trap AutoQoS description "AutoQoS SNMP traps for Voice Drops" owner
AutoQoS
interface Serial2/1.1 point-to-point
frame-relay interface-dlci 58
class AutoQoS-FR-Serial2/1-58
map-class frame-relay AutoQoS-FR-Serial2/1-58
frame-relay mincir 1024000
service-policy output AutoQoS-Policy-Se2/1.1-Parent
Table 41 describes the significant fields shown in the display.
Table 41 show auto qos Field Descriptions (AutoQoS for the Enterprise Feature Configured)
|
|
policy-map AutoQoS-Policy-Se2/1.1 |
Name of the policy map created by the AutoQoS feature. In this instance the name of the policy map is AutoQoS-Policy-Se2/1.1. |
class AutoQoS-Voice-Se2/1.1 priority percent 70 set dscp ef |
Name of class created by the AutoQoS feature. In this instance, the name of the class is AutoQoS-Voice-Se2/1.1. Following the class name, the specific QoS features configured for the class are displayed. |
class-map match-any AutoQoS-Stream-Video-Se2/1.1 match protocol cuseeme |
Name of the class map and the packet matching criteria specified. |
Related Commands
|
|
auto discovery qos |
Begins discovering and collecting data for configuring the AutoQoS for the Enterprise feature. |
auto qos |
Installs the QoS class maps and policy maps created by the AutoQoS for the Enterprise feature. |
auto qos voip |
Configures the AutoQoS—VoIP feature on an interface. |
show auto discovery qos |
Displays the data collected during the Auto-Discovery phase of the AutoQoS for the Enterprise feature. |
show class-map
To display class maps and their matching criteria, use the show class-map command in user EXEC or privileged EXEC mode.
Cisco 3660, 3845, 6500, 7400, and 7500 Series Routers
show class-map [type {stack | access-control}] [class-map-name]
Cisco 7600 and ASR 1000 Series Routers
show class-map [class-map-name]
Syntax Description
type stack |
(Optional) Displays class maps configured to determine the correct protocol stack in which to examine via flexible packet matching (FPM). |
type access-control |
(Optional) Displays class maps configured to determine the exact pattern to look for in the protocol stack of interest. |
class-map-name |
(Optional) Name of the class map. The class map name can be a maximum of 40 alphanumeric characters. |
Command Default
All class maps are displayed.
Command Modes
User EXEC (>)
Privileged EXEC (#)
Command History
|
|
12.0(5)T |
This command was introduced. |
12.2(13)T |
This command was modified to display the Frame Relay data-link connection identifier (DLCI) number or Layer 3 packet length as a criterion for matching traffic inside a class map. |
12.2(14)SX |
This command was implemented on the Cisco 7600 series routers. |
12.2(17d)SXB |
This command was implemented on the Supervisor Engine 2 and integrated into Cisco IOS Release 12.2(17d)SXB. |
12.2(28)SB |
This command was integrated into Cisco IOS Release 12.2(28)SB. |
12.2(33)SRA |
This command was integrated into Cisco IOS Release 12.2(33)SRA. |
12.4(4)T |
The type, stack, and access-control keywords were added to support FPM. |
Cisco IOS XE Release 2.2 |
This command was implemented on Cisco ASR Aggregation Services 1000 series routers. |
15.0(1)M |
This command was modified. The output was modified to display encrypted filter information. |
Usage Guidelines
You can use the show class-map command to display all class maps and their matching criteria. If you enter the optional class-map-name argument, the specified class map and its matching criteria will be displayed.
Examples
In the following example, three class maps are defined. Packets that match access list 103 belong to class c3, IP packets belong to class c2, and packets ingressing through Ethernet interface 1/0 belong to class c1. The output from the show class-map command shows the three defined class maps.
Match input-interface Ethernet1/0
In the following example, a class map called c1 has been defined, and the Frame Relay DLCI number of 500 has been specified as a match criterion:
The following example shows how to display class-map information for all class maps:
Class Map match-any class-default (id 0)
Class Map match-any class-simple (id 2)
Class Map match-all ipp5 (id 1)
Class Map match-all agg-2 (id 3)
The following example shows how to display class-map information for a specific class map:
Router# show class-map ipp5
Class Map match-all ipp5 (id 1)
The following is sample output from the show class-map type access-control command for an encrpted FPM filter:
Router# show class-map type access-control accesscontrol1
Class Map type access-control match-all accesscontrol1 (id 4)
Match encrypted FPM filter
filter-hash : FC50BED10521002B8A170F29AF059C53
filter-version: 0.0_DummyVersion_20090101_1830
filter-id : cisco-sa-20090101-dummy_ddts_001
Match start TCP payload-start offset 0 size 10 regex "abc.*def"
Match field TCP source-port eq 1234
Table 42 describes the significant fields shown in the display.
Table 42 show class-map Field Descriptions1
|
|
Class Map |
Class of traffic being displayed. Output is displayed for each configured class map in the policy. The choice for implementing class matches (for example, match-all or match-any) can also appear next to the traffic class. |
Match |
Match criteria specified for the class map. Criteria include the Frame Relay DLCI number, Layer 3 packet length, IP precedence, IP differentiated services code point (DSCP) value, Multiprotocol Label Switching (MPLS) experimental value, access groups, and quality of service (QoS) groups. |
Related Commands
|
|
class-map |
Creates a class map to be used for matching packets to a specified class. |
match fr-dlci |
Specifies the Frame Relay DLCI number as a match criterion in a class map. |
match packet length (class-map) |
Specifies and uses the length of the Layer 3 packet in the IP header as a match criterion in a class map. |
show policy-map |
Displays the configuration of all classes for a specified service policy map or all classes for all existing policy maps. |
show policy-map interface |
Displays the packet statistics of all classes that are configured for all service policies either on the specified interface or subinterface or on a specific PVC on the interface. |
show class-map type nat
To display network address translation (NAT) class maps and their matching criteria, use the show class-map type nat command in privileged EXEC mode.
show class-map type nat [class-map-name]
Syntax Description
class-map-name |
(Optional) Name of the NAT class map. The name can be a maximum of 40 alphanumeric characters. |
Command Default
Information for all NAT class maps is displayed.
Command Modes
Privileged EXEC (#)
Command History
|
|
12.4(11)T |
This command was introduced. |
Usage Guidelines
The show class-map type nat command displays all NAT class maps and their matching criteria. To display a particular NAT class map and its matching criteria, specify the class-map name.
Examples
The following is sample output from the show class-map type nat command that disaplays all the class maps:
Router# show class-map type nat
Class Map match-all ipnat-class-acl-we (id 5)
Table 43 describes the significant fields shown in the display.
Table 43 show class-map type nat Field Descriptions
|
|
Class Map |
Displays the name of the class map along with the conditions applied for the class map to match the incoming packets. |
Match |
Match criteria specified for the class map. |
Related Commands
|
|
show class-map type inspect |
Displays Layer 3 and Layer 4 or Layer 7 (application-specific) inspect type class maps and their matching criteria. |
show class-map type port-filter |
Displays port-filter class maps and their matching criteria. |
show class-map type port-filter
To display class maps for port filters and their matching criteria, use the show class-map type port-filter command in privileged EXEC mode.
show class-map type port-filter [class-map-name]
Syntax Description
class-map-name |
(Optional) Name of the port-filter class map. The name can be a maximum of 40 alphanumeric characters. |
Command Default
If no argument is specified, information for all port-filter class maps is displayed.
Command Modes
Privileged EXEC (#)
Command History
|
|
12.4(11)T |
This command was introduced. |
Usage Guidelines
Use the show class-map type port-filter command to display TCP/UDP port policing of control plane packets. The show class-map type port-filter command displays all port-filter class maps and their matching criteria. To display class maps for a particular port-filter class map, specify the class map name.
Examples
The following is sample output from the show class-map type port-filter command that displays all the class maps:
Router# show class-map type port-filter
Class Map type port-filter match-all pf-policy (id 9)
Class Map type port-filter match-any cl1 (id 4)
Class Map type port-filter match-all pf-class (id 8)
The following is sample output from the show class-map type port-filter command that displays the class map pf-class:
Router# show class-map type port-filter pf-class
Class Map type port-filter match-all pf-class (id 8)
Table 44 describes the significant fields shown in the display.
Table 44 show class-map type port-filter Field Descriptions
|
|
Class Map |
Port-filter class maps being displayed. Output is displayed for each configured class map. The choice for implementing class matches (for example, match-all or match-any) appears next to the traffic class. |
Match |
Match criteria specified for the class map. Valid matching criteria are closed-ports, not, and port. |
Related Commands
|
|
class-map |
Creates a class map to be used for matching packets to a specified class. |
show control-plane cef-exception counters
To display the control-plane packet counters for the control-plane cef-exception subinterface, use the show control-plane cef-exception counters command in privileged EXEC mode.
show control-plane cef-exception counters
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
|
|
12.4(4)T |
This command was introduced. |
Usage Guidelines
The show control-plane cef-exception counters command displays the following packet counts for features configured on the control-plane cef-exception subinterface:
•Total number of packets that were processed by the cef-exception subinterface
•Total of packets that were dropped
•Total number of errors
Examples
The following is sample output from the show control-plane cef-exception counters command:
Router# show control-plane cef-exception counters
Control plane cef-exception path counters:
Feature Packets Processed/Dropped/Errors
Control Plane Policing 63456/9273/0
Table 45 describes the significant fields shown in the display.
Table 45 show control-plane cef-exception counters Field Descriptions
|
|
Feature |
Name of the configured feature on this subinterface. |
Packets Processed |
Total number of packets that were processed by the feature. |
Dropped |
Total number of packets that were dropped by the feature. |
Errors |
Total number of errors detected by the feature. |
Related Commands
|
|
clear control-plane |
Clears packet counters for control-plane interfaces and subinterfaces. |
control-plane |
Enters control-plane configuration mode, which allows you to associate or modify attributes or parameters that are associated with the control-plane of the device. |
debug control-plane |
Displays debugging output from the control-plane routines. |
show control-plane cef-exception features |
Displays the configured features for the control-plane CEF-exception subinterface. |
show control-plane counters |
Displays the control-plane packet counters for the aggregate control-plane interface. |
show control-plane features |
Displays the configured features for the aggregate control-plane interface. |
show control-plane host counters |
Displays the control-plane packet counters for the control-plane host subinterface. |
show control-plane host features |
Displays the configured features for the control-plane host subinterface. |
show control-plane host open-ports |
Displays a list of open TCP/UDP ports that are registered with the port-filter database. |
show control-plane transit counters |
Displays the control-plane packet counters for the control-plane transit subinterface. |
show control-plane cef-exception features
To display the control-plane features for control-plane cef-exception subinterface, use the show control-plane cef-exception features command in privileged EXEC mode.
show control-plane cef-exception features
Syntax Descriptionshow control-plane cef-exception features
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
|
|
12.4(4)T |
This command was introduced. |
Usage Guidelines
The show control-plane cef-exception features command displays the following aggregate feature configurations for the control-plane cef-exception subinterface:
•Number of features configured for the control-plane cef-exception subinterface.
•Name of the feature
•Date and time the feature was activated
Examples
The following is sample output from the show control-plane cef-exception features command:
Router# show control-plane cef-exception features
Total 1 features configure
Control plane cef-exception path features:
Control Plane Policing activated Nov 09 2005 12:40
Table 46 describes the significant fields shown in the display.
Table 46 show control-plane cef-exception features Field Descriptions
|
|
Total features configured |
Number of features configured. |
Feature Name |
Name of the configured features. |
Activated |
Date and time the feature was activated. |
Related Commands
|
|
clear control-plane |
Clears packet counters for control-plane interfaces and subinterfaces. |
control-plane |
Enters control-plane configuration mode, which allows you to associate or modify attributes or parameters that are associated with the control-plane of the device. |
debug control-plane |
Displays debugging output from the control-plane routines. |
show control-plane cef-exception counters |
Displays the control-plane packet counters for the control-plane CEF-exception subinterface. |
show control-plane counters |
Displays the control-plane packet counters for the aggregate control-plane interface. |
show control-plane features |
Displays the configured features for the aggregate control-plane interface. |
show control-plane host counters |
Displays the control-plane packet counters for the control-plane host subinterface. |
show control-plane host features |
Displays the configured features for the control-plane host subinterface. |
show control-plane host open-ports |
Displays a list of open TCP/UDP ports that are registered with the port-filter database. |
show control-plane transit counters |
Displays the control-plane packet counters for the control-plane transit subinterface. |
show control-plane counters
To display the control-plane counters for all control-plane interfaces, use the show control-plane counters command in privileged EXEC mode.
show control-plane counters
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
|
|
12.4(4)T |
This command was introduced. |
Usage Guidelines
The show control-plane counters command displays the following aggregate packet counts for all control-plane interfaces and subinterface:
•Total number of packets that were processed by control-plane aggregate host, transit, and cef-exception subinterfaces
•Total number of packets that were dropped
•Total number of errors
Examples
The following is sample output from the show control-plane counters command:
Router# show control-plane counters
Feature Path Packets Processed/Dropped/Errors
cef-exception path 6345/0/0
Table 47 describes the significant fields shown in the display.
Table 47 show control-plane counters Field Descriptions
|
|
Feature |
Name of the interface or subinterface displayed. |
Packets Processed |
Total number of packets that were processed by the subinterface. |
Dropped |
Total number of packets that were dropped. |
Errors |
Total number of errors detected. |
Related Commands
|
|
clear control-plane |
Clears packet counters for control-plane interfaces and subinterfaces. |
control-plane |
Enters control-plane configuration mode, which allows you to associate or modify attributes or parameters that are associated with the control-plane of the device. |
debug control-plane |
Displays debugging output from the control-plane routines. |
show control-plane cef-exception counters |
Displays the control-plane packet counters for the control-plane CEF-exception subinterface. |
show control-plane cef-exception features |
Displays the configured features for the control-plane CEF-exception subinterface. |
show control-plane features |
Displays the configured features for the aggregate control-plane interface. |
show control-plane host counters |
Displays the control-plane packet counters for the control-plane host subinterface. |
show control-plane host features |
Displays the configured features for the control-plane host subinterface. |
show control-plane host open-ports |
Displays a list of open TCP/UDP ports that are registered with the port-filter database. |
show control-plane transit counters |
Displays the control-plane packet counters for the control-plane transit subinterface. |
show control-plane transit features |
Displays the configured features for the control-plane transit subinterface. |
show control-plane features
To display the configured control-plane features, use the show control-plane features command in privileged EXEC mode.
show control-plane features
Syntax Description
This command has no arguments or keywords
Command Modes
Privileged EXEC
Command History
|
|
12.4(4)T |
This command was introduced. |
Usage Guidelines
The show control-plane features command displays control-plane features enabled on the control-plane aggregate sub-interfaces. Information includes the following:
•Number of features configured for the control plane
•Name of the feature
•Date and time the feature was activated
Examples
The following is sample output from the show control-plane features command:
Router# show control-plane features
Total 1 features configured
Control plane host path features:
TCP/UDP Portfilter activated Nov 09 2005 12:40
Table 48 describes the significant fields shown in the display.
Table 48 show control-plane features Field Descriptions
|
|
Total features configured |
Number of features configured. |
Feature Name |
Name of the configured features. |
activated |
Date and time the feature was activated. |
Related Commands
|
|
clear control-plane |
Clears packet counters for control-plane interfaces and subinterfaces. |
control-plane |
Enters control-plane configuration mode, which allows you to associate or modify attributes or parameters that are associated with the control-plane of the device. |
debug control-plane |
Displays debugging output from the control-plane routines. |
show control-plane cef-exception counters |
Displays the control-plane packet counters for the control-plane CEF-exception subinterface. |
show control-plane cef-exception features |
Displays the configured features for the control-plane CEF-exception subinterface. |
show control-plane counters |
Displays the control-plane packet counters for the aggregate control-plane interface. |
show control-plane host counters |
Displays the control-plane packet counters for the control-plane host subinterface. |
show control-plane host features |
Displays the configured features for the control-plane host subinterface. |
show control-plane host open-ports |
Displays a list of open TCP/UDP ports that are registered with the port-filter database. |
show control-plane transit counters |
Displays the control-plane packet counters for the control-plane transit subinterface. |
show control-plane transit features |
Displays the configured features for the control-plane transit subinterface. |
show control-plane host counters
To display the control-plane packet counters for the control-plane host subinterface, use the show control-plane host counters command in privileged EXEC mode.
show control-plane host counters
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
|
|
12.4(4)T |
This command was introduced. |
Usage Guidelines
The show control-plane host counters command displays the following packet counts for the control-plane host subinterface:
•Total number of packets that were processed by features configured on the host subinterface
•Total number of packets that were dropped
•Total number of errors
Examples
The following is sample output from the show control-plane host counters command:
Router# show control-plane host counters
Control plane host path counters:
Feature Packets Processed/Dropped/Errors
TCP/UDP portfilter 46/46/0
Table 49 describes the significant fields shown in the display.
Table 49 show control-plane host counters Field Descriptions
|
|
Feature |
Name of the feature configured on the host subinterface. |
Packets Processed |
Total number of packets that were processed by the feature. |
Dropped |
Total number of packets that were dropped. |
Errors |
Total number of errors detected. |
Related Commands
|
|
clear control-plane |
Clears packet counters for control-plane interfaces and subinterfaces. |
control-plane |
Enters control-plane configuration mode, which allows you to associate or modify attributes or parameters that are associated with the control-plane of the device. |
debug control-plane |
Displays debugging output from the control-plane routines. |
show control-plane cef-exception counters |
Displays the control-plane packet counters for the control-plane CEF-exception subinterface. |
show control-plane cef-exception features |
Displays the configured features for the control-plane CEF-exception subinterface. |
show control-plane counters |
Displays the control-plane packet counters for the aggregate control-plane interface. |
show control-plane features |
Displays the configured features for the aggregate control-plane interface. |
show control-plane host features |
Displays the configured features for the control-plane host subinterface. |
show control-plane host open-ports |
Displays a list of open TCP/UDP ports that are registered with the port-filter database. |
show control-plane transit counters |
Displays the control-plane packet counters for the control-plane transit subinterface. |
show control-plane transit features |
Displays the configured features for the control plane transit subinterface. |
show control-plane host features
To display the configured control-plane features for the control-plane host sub-interface, use the show control-plane host features command in privileged EXEC mode.
show control-plane host features
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
|
|
12.4(4)T |
This command was introduced. |
Usage Guidelines
The show control-plane host features command displays the features configured for the control-plane host subinterface. Information includes the following:
•Number of features configured for the control plane
•Name of the feature
•Date and time the feature was activated
Examples
The following is sample output from the show control-plane host features command:
Router# show control-plane host features
Control plane host path features:
TCP/UDP Portfilter activated Nov 09 2005 12:40
Table 50 describes the significant fields shown in the display.
Table 50 show control-plane host features Field Descriptions
|
|
Feature Name |
Name of the configured features. |
activated |
Date and time the feature was activated. |
Related Commands
|
|
clear control-plane |
Clears packet counters for control-plane interfaces and subinterfaces. |
control-plane |
Enters control-plane configuration mode, which allows you to associate or modify attributes or parameters that are associated with the control plane of the device. |
debug control-plane |
Displays debugging output from the control-plane routines. |
show control-plane cef-exception counters |
Displays the control plane packet counters for the control-plane CEF-exception subinterface. |
show control-plane cef-exception features |
Displays the configured features for the control-plane CEF-exception subinterface. |
show control-plane counters |
Displays the control-plane packet counters for the aggregate control-plane interface. |
show control-plane features |
Displays the configured features for the aggregate control-plane interface. |
show control-plane host counters |
Displays the control-plane packet counters for the control-plane host subinterface. |
show control-plane host open-ports |
Displays a list of open TCP/UDP ports that are registered with the port-filter database. |
show control-plane transit counters |
Displays the control-plane packet counters for the control-plane transit subinterface. |
show control-plane transit features |
Displays the configured features for the control-plane transit subinterface. |
show control-plane host open-ports
To display a list of open TCP/UDP ports that are registered with the port-filter database, use the show control-plane host open-ports command in privileged EXEC mode.
show control-plane host open-ports
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
|
|
12.4(4)T |
This command was introduced. |
Usage Guidelines
The show control-plane host open-ports command displays a list of open TCP/UDP ports that are registered with the port-filter database.
Examples
The following is sample output from the show control-plane host open-ports command.
Router# show control-plane host open-ports
Active internet connections (servers and established)
Port Local Address Foreign Address Service State
tcp *:23 *:0 Telnet LISTEN
tcp *:53 *:0 DNS Server LISTEN
tcp *:80 *:0 HTTP CORE LISTEN
tcp *:1720 *:0 H.225 LISTEN
tcp *:5060 *:0 SIP LISTEN
tcp *:23 192.0.2.18:58714 Telnet ESTABLISHED
udp *:53 *:0 DNS Server LISTEN
udp *:67 *:0 DHCPD Receive LISTEN
udp *:52824 *:0 IP SNMP LISTEN
udp *:161 *:0 IP SNMP LISTEN
udp *:162 *:0 IP SNMP LISTEN
udp *:5060 *:0 SIP LISTEN
udp *:2517 *:0 CCH323_CT LISTEN
Table 51 describes the significant fields shown in the display.
Table 51 show control-plane host open-ports Field Descriptions
|
|
Port |
Port type, either TCP or UDP. |
Local Address |
Local IP address and port number. An asterisk (*) indicates that the service is listening on all configured network interfaces. |
Foreign Address |
Remote IP address and port number. An asterisk (*) indicates that the service is listening on all configured network interfaces. |
Service |
Name of the configured Cisco IOS service listening on the port. |
State |
Listen or Established. |
Related Commands
|
|
clear control-plane |
Clears packet counters for control-plane interfaces and subinterfaces. |
control-plane |
Enters control-plane configuration mode, which allows you to associate or modify attributes or parameters that are associated with the control plane of the device. |
debug control-plane |
Displays debugging output from the control-plane routines. |
show control-plane cef-exception counters |
Displays the control-plane packet counters for the control-plane CEF-exception subinterface. |
show control-plane cef-exception features |
Displays the configured features for the control-plane CEF-exception subinterface. |
show control-plane counters |
Displays the control-plane packet counters for the aggregate control-plane interface. |
show control-plane features |
Displays the configured features for the aggregate control-plane interface. |
show control-plane host counters |
Displays the control plane packet counters for the control-plane host subinterface. |
show control-plane host features |
Displays the configured features for the control-plane host subinterface. |
show control-plane transit counters |
Displays the control plane packet counters for the control-plane transit subinterface. |
show control-plane transit features |
Displays the configured features for the control-plane transit subinterface. |
show control-plane transit counters
To display the control-plane packet counters for the control-plane transit sub-interface, use the show control-plane transit counters command in privileged EXEC mode.
show control-plane transit counters
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
|
|
12.4(4)T |
This command was introduced. |
Usage Guidelines
The show control-plane transit counters command displays the following packet counts for the control-plane transit subinterface:
•Total number of packets that were processed by the transit subinterface
•Total number of packets that were dropped
•Total number of errors
Examples
The following is sample output from the show control-plane transit counters command.
Router# show control-plane transit counters
Control plane transit path counters:
Feature Packets Processed/Dropped/Errors
Control Plane Policing 63456/2391/0
Table 52 describes the significant fields shown in the display.
Table 52 show control-plane transit counters Field Descriptions
|
|
Feature |
Name of the feature configured on the transit sub-interface. |
Packets Processed |
Total number of packets that were processed by the configured feature. |
Dropped |
Total number of packets that were dropped. |
Errors |
Total number of errors detected. |
Related Commands
|
|
clear control-plane |
Clears packet counters for control-plane interfaces and subinterfaces. |
control-plane |
Enters control-plane configuration mode, which allows you to associate or modify attributes or parameters that are associated with the control plane of the device. |
debug control-plane |
Displays debugging output from the control-plane routines. |
show control-plane cef-exception counters |
Displays the control plane packet counters for the control-plane CEF-exception subinterface. |
show control-plane cef-exception features |
Displays the configured features for the control-plane CEF-exception subinterface. |
show control-plane counters |
Displays the control-plane packet counters for the aggregate control-plane interface. |
show control-plane features |
Displays the configured features for the aggregate control-plane interface. |
show control-plane host counters |
Displays the control plane packet counters for the control-plane host subinterface. |
show control-plane host features |
Displays the configured features for the control-plane host subinterface. |
show control-plane host open-ports |
Displays a list of open TCP/UDP ports that are registered with the port-filter database. |
show control-plane transit features |
Displays the configured features for the control-plane transit subinterface. |
show control-plane transit features
To display the configured control-plane features for the control-plane transit subinterface, use the show control-plane transit features command in privileged EXEC mode.
show control-plane transit features
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
|
|
12.4(4)T |
This command was introduced. |
Usage Guidelines
The show control-plane transit features command displays the control-plane features configured for the control-plane transit subinterface. Information includes the following:
•Number of features configured for the control plane
•Name of the feature
•Date and time the feature was activated
Examples
The following is sample output from the show control-plane transit features command:
Router# show control-plane transit features
Control plane transit path features:
Control Plane Policing activated Nov 09 2005 12:40
Table 53 describes the significant fields shown in the display.
Table 53 show control-plane transit features Field Descriptions
|
|
Total Features Configured |
Number of features configured. |
Feature Name |
Name of the configured features. |
Activated |
Date and time the feature was activated. |
Related Commands
|
|
clear control-plane |
Clears packet counters for control-plane interfaces and subinterfaces. |
control-plane |
Enters control-plane configuration mode, which allows you to associate or modify attributes or parameters that are associated with the control plane of the device. |
debug control-plane |
Displays debugging output from the control-plane routines. |
show control-plane cef-exception counters |
Displays the control-plane packet counters for the control-plane CEF-exception subinterface. |
show control-plane cef-exception features |
Displays the configured features for the control-plane CEF-exception subinterface. |
show control-plane counters |
Displays the control-plane packet counters for the aggregate control-plane interface. |
show control-plane features |
Displays the configured features for the aggregate control-plane interface. |
show control-plane host counters |
Displays the control plane packet counters for the control-plane host subinterface. |
show control-plane host features |
Displays the configured features for the control-plane host subinterface. |
show control plane host open-ports |
Displays a list of open ports that are registered with the port-filter database. |
show control-plane transit counters |
Displays the control-plane packet counters for the control-plane transit subinterface. |
show cops servers
To display the IP address and connection status of the policy servers for which the router is configured, use the show cops servers command in EXEC mode.
show cops servers
Syntax Description
This command has no keywords or arguments.
Command Modes
EXEC
Command History
|
|
12.1(1)T |
This command was introduced. |
12.2(33)SRA |
This command was integrated into Cisco IOS Release 12.2(33)SRA. |
12.2SX |
This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware. |
Usage Guidelines
You can also use the show cops server command to display information about the Common Open Policy Service (COPS) client on the router.
Examples
In the following example, information is displayed about the current policy server and client. When Client Type appears followed by an integer, 1 stands for Resource Reservation Protocol (RSVP) and 2 stands for Differentiated Services Provisioning. (0 indicates keepalive.)
Router# show cops servers
COPS SERVER: Address: 10.0.0.1. Port: 3288. State: 0. Keepalive: 120 sec
Number of clients: 1. Number of sessions: 1.
COPS CLIENT: Client type: 1. State: 0.
Related Commands
|
|
show ip rsvp policy cops |
Displays policy server address(es), ACL IDs, and current state of the router-server connection. |
show crypto eng qos
To monitor and maintain low latency queueing (LLQ) for IPSec encryption engines, use the show crypto eng qos command in privileged EXEC mode.
show crypto eng qos
Syntax Description
This command has no keywords or arguments.
Command Modes
Privileged EXEC
Command History
|
|
12.2(13)T |
This command was introduced in Cisco IOS Release 12.2(13)T. |
12.2(14)S |
This command was integrated into Cisco IOS Release 12.2(14)S. |
12.2(33)SRA |
This command was integrated into Cisco IOS release 12.(33)SRA. |
12.2SX |
This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware. |
Usage Guidelines
Use the show crypto eng qos command to determine if QoS is enabled on LLQ for IPSec encryption engines.
Examples
The following example shows how to determine if LLQ for IPSec encryption engines is enabled:
Router# show crypto eng qos
crypto engine name: Multi-ISA Using VAM2
crypto engine type: hardware
visible bandwidth: 30000 kbps
default queue size/max: 0/64
FastEthernet0/0 (3), iftype 1, ctable size 16, input filter:ip
class voice (1/3), match ip precedence 5
bandwidth 500 kbps, max token 100000
IN match pkt/byte 0/0, police drop 0
OUT match pkt/byte 0/0, police drop 0
class default, match pkt/byte 0/0, qdrop 0
crypto engine bandwidth:total 30000 kbps, allocated 500 kbps
The field descriptions in the above display are self-explanatory.
show frame-relay ip rtp header-compression
To display Frame Relay Real-Time Transport Protocol (RTP) header compression statistics, use the show frame-relay ip rtp header-compression command in user EXEC or privileged EXEC mode.
show frame-relay ip rtp header-compression [interface type number] [dlci]
Syntax Description
interface type number |
(Optional) Specifies an interface for which information will be displayed. A space between the interface type and number is optional. |
dlci |
(Optional) Specifies a data-link connection identifier (DLCI) for which information will be displayed. The range is from 16 to 1022. |
Command Default
RTP header compression statistics are displayed for all DLCIs on interfaces that have RTP header compression configured.
Command Modes
User EXEC
Privileged EXEC
Command History
|
|
11.3 |
This command was introduced. |
12.2(13)T |
This command was integrated into Cisco IOS Release 12.2(13)T. The output for this command was modified to display RTP header compression statistics for Frame Relay permanent virtual circuit (PVC) bundles. |
12.2(27)SBC |
This command was integrated into Cisco IOS Release 12.2(27)SBC, and the dlci argument was added. |
12.2(28)SB |
This command was integrated into Cisco IOS Release 12.2(28)SB. |
12.4(9)T |
The dlci argument was added. |
12.2(33)SRA |
This command was integrated into Cisco IOS Release 12.2(33)SRA. |
12.4(11)T |
The output for this command was modified to display Enhanced Compressed Real-Time Transport Protocol (ECRTP) header compression statistics for Frame Relay permanent virtual circuit (PVC) bundles. |
12.2SX |
This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware. |
Examples
The following is sample output from the show frame-relay ip rtp header-compression command:
Router# show frame-relay ip rtp header-compression
DLCI 21 Link/Destination info: ip 10.1.4.1
Interface Serial3/0 DLCI 21 (compression on, Cisco)
Rcvd: 0 total, 0 compressed, 0 errors, 0 status msgs
0 dropped, 0 buffer copies, 0 buffer failures
Sent: 0 total, 0 compressed, 0 status msgs, 0 not predicted
0 bytes saved, 0 bytes sent
Connect: 256 rx slots, 256 tx slots,
0 misses, 0 collisions, 0 negative cache hits, 256 free contexts
DLCI 20 Link/Destination info: ip 10.1.1.1
Interface Serial3/1 DLCI 20 (compression on, Cisco)
Rcvd: 0 total, 0 compressed, 0 errors, 0 status msgs
0 dropped, 0 buffer copies, 0 buffer failures
Sent: 0 total, 0 compressed, 0 status msgs, 0 not predicted
0 bytes saved, 0 bytes sent
Connect: 256 rx slots, 256 tx slots,
0 misses, 0 collisions, 0 negative cache hits, 256 free contexts
DLCI 21 Link/Destination info: ip 10.1.2.1
Interface Serial3/1 DLCI 21 (compression on, Cisco)
Rcvd: 0 total, 0 compressed, 0 errors, 0 status msgs
0 dropped, 0 buffer copies, 0 buffer failures
Sent: 0 total, 0 compressed, 0 status msgs, 0 not predicted
0 bytes saved, 0 bytes sent
Connect: 256 rx slots, 256 tx slots,
0 misses, 0 collisions, 0 negative cache hits, 256 free contexts
DLCI 22 Link/Destination info: ip 10.1.3.1
Interface Serial3/1 DLCI 22 (compression on, Cisco)
Rcvd: 0 total, 0 compressed, 0 errors, 0 status msgs
0 dropped, 0 buffer copies, 0 buffer failures
Sent: 0 total, 0 compressed, 0 status msgs, 0 not predicted
0 bytes saved, 0 bytes sent
Connect: 256 rx slots, 256 tx slots,
0 misses, 0 collisions, 0 negative cache hits, 256 free contexts
The following is sample output from the show frame-relay ip rtp header-compression command when ECRTP is enabled:
Router# show frame-relay ip rtp header-compression
DLCI 16 Link/Destination info: ip 10.0.0.1
Interface Serial4/1 DLCI 16 (compression on, IETF, ECRTP)
Rcvd: 0 total, 0 compressed, 0 errors, 0 status msgs
0 dropped, 0 buffer copies, 0 buffer failures
Sent: 0 total, 0 compressed, 0 status msgs, 0 not predicted
0 bytes saved, 0 bytes sent
Connect: 16 rx slots, 16 tx slots,
0 misses, 0 collisions, 0 negative cache hits, 16 free contexts
In the following example, the show frame-relay ip rtp header-compression command displays information about DLCI 21:
Router# show frame-relay ip rtp header-compression 21
DLCI 21 Link/Destination info: ip 10.1.4.1
Interface Serial3/0 DLCI 21 (compression on, Cisco)
Rcvd: 0 total, 0 compressed, 0 errors, 0 status msgs
0 dropped, 0 buffer copies, 0 buffer failures
Sent: 0 total, 0 compressed, 0 status msgs, 0 not predicted
0 bytes saved, 0 bytes sent
Connect: 256 rx slots, 256 tx slots,
0 misses, 0 collisions, 0 negative cache hits, 256 free contexts
DLCI 21 Link/Destination info: ip 10.1.2.1
Interface Serial3/1 DLCI 21 (compression on, Cisco)
Rcvd: 0 total, 0 compressed, 0 errors, 0 status msgs
0 dropped, 0 buffer copies, 0 buffer failures
Sent: 0 total, 0 compressed, 0 status msgs, 0 not predicted
0 bytes saved, 0 bytes sent
Connect: 256 rx slots, 256 tx slots,
0 misses, 0 collisions, 0 negative cache hits, 256 free contexts
In the following example, the show frame-relay ip rtp header-compression command displays information for all DLCIs on serial interface 3/1:
Router# show frame-relay ip rtp header-compression interface serial3/1
DLCI 20 Link/Destination info: ip 10.1.1.1
Interface Serial3/1 DLCI 20 (compression on, Cisco)
Rcvd: 0 total, 0 compressed, 0 errors, 0 status msgs
0 dropped, 0 buffer copies, 0 buffer failures
Sent: 0 total, 0 compressed, 0 status msgs, 0 not predicted
0 bytes saved, 0 bytes sent
Connect: 256 rx slots, 256 tx slots,
0 misses, 0 collisions, 0 negative cache hits, 256 free contexts
DLCI 21 Link/Destination info: ip 10.1.2.1
Interface Serial3/1 DLCI 21 (compression on, Cisco)
Rcvd: 0 total, 0 compressed, 0 errors, 0 status msgs
0 dropped, 0 buffer copies, 0 buffer failures
Sent: 0 total, 0 compressed, 0 status msgs, 0 not predicted
0 bytes saved, 0 bytes sent
Connect: 256 rx slots, 256 tx slots,
0 misses, 0 collisions, 0 negative cache hits, 256 free contexts
DLCI 22 Link/Destination info: ip 10.1.3.1
Interface Serial3/1 DLCI 22 (compression on, Cisco)
Rcvd: 0 total, 0 compressed, 0 errors, 0 status msgs
0 dropped, 0 buffer copies, 0 buffer failures
Sent: 0 total, 0 compressed, 0 status msgs, 0 not predicted
0 bytes saved, 0 bytes sent
Connect: 256 rx slots, 256 tx slots,
0 misses, 0 collisions, 0 negative cache hits, 256 free contexts
In the following example, the show frame-relay ip rtp header-compression command displays information only for DLCI 21 on serial interface 3/1:
Router# show frame-relay ip rtp header-compression interface serial3/1 21
DLCI 21 Link/Destination info: ip 10.1.2.1
Interface Serial3/1 DLCI 21 (compression on, Cisco)
Rcvd: 0 total, 0 compressed, 0 errors, 0 status msgs
0 dropped, 0 buffer copies, 0 buffer failures
Sent: 0 total, 0 compressed, 0 status msgs, 0 not predicted
0 bytes saved, 0 bytes sent
Connect: 256 rx slots, 256 tx slots,
0 misses, 0 collisions, 0 negative cache hits, 256 free contexts
The following sample output from the show frame-relay ip rtp header-compression command shows statistics for a PVC bundle called MP-3-static:
Router# show frame-relay ip rtp header-compression interface Serial1/4
vc-bundle MP-3-static Link/Destination info:ip 10.1.1.1
Rcvd: 14 total, 13 compressed, 0 errors
0 dropped, 0 buffer copies, 0 buffer failures
Sent: 15 total, 14 compressed,
474 bytes saved, 119 bytes sent
4.98 efficiency improvement factor
Connect:256 rx slots, 256 tx slots,
1 long searches, 1 misses 0 collisions, 0 negative cache hits
93% hit ratio, five minute miss rate 0 misses/sec, 0 max
Table 54 describes the significant fields shown in the displays.
Table 54 show frame-relay ip rtp header-compression Field Descriptions
|
|
Interface |
Type and number of the interface and type of header compression. |
Rcvd: |
Table of details concerning received packets. |
total |
Number of packets received on the interface. |
compressed |
Number of packets with compressed headers. |
errors |
Number of errors. |
dropped |
Number of dropped packets. |
buffer copies |
Number of buffers that were copied. |
buffer failures |
Number of failures in allocating buffers. |
Sent: |
Table of details concerning sent packets. |
total |
Total number of packets sent. |
compressed |
Number of packets sent with compressed headers. |
bytes saved |
Total savings in bytes because of compression. |
bytes sent |
Total bytes sent after compression. |
efficiency improvement factor |
Compression efficiency. |
Connect: |
Table of details about the connections. |
rx slots |
Total number of receive slots. |
tx slots |
Total number of transmit slots. |
long searches |
Searches that needed more than one lookup. |
misses |
Number of new states that were created. |
hit ratio |
Number of times that existing states were revised. |
five minute miss rate |
Average miss rate. |
max |
Maximum miss rate. |
Related Commands
|
|
frame-relay ip rtp compression-connections |
Specifies the maximum number of RTP header compression connections on a Frame Relay interface. |
frame-relay ip rtp header-compression |
Enables RTP header compression for all Frame Relay maps on a physical interface. |
frame-relay map ip compress |
Enables both RTP and TCP header compression on a link. |
frame-relay map ip nocompress |
Disables both RTP and TCP header compression on a link. |
frame-relay map ip rtp header-compression |
Enables RTP header compression per DLCI. |
show ip rpf events |
Displays RTP header compression statistics. |
show frame-relay ip tcp header-compression
To display Frame Relay Transmission Control Protocol (TCP)/IP header compression statistics, use the show frame-relay ip tcp header-compression command in user EXEC or privileged EXEC mode.
show frame-relay ip tcp header-compression [interface type number] [dlci]
Syntax Description
interface type number |
(Optional) Specifies an interface for which information will be displayed. A space is optional between the type and number. |
dlci |
(Optional) Specifies a data-link connection identifier (DLCI) for which information will be displayed. Range is from 16 to 1022. |
Command Modes
User EXEC
Privileged EXEC
Command History
|
|
10.3 |
This command was introduced. |
12.2(13)T |
This command was integrated into Cisco IOS Release 12.2(13)T. The command was modified to support display of RTP header compression statistics for Frame Relay permanent virtual circuit (PVC) bundles. |
12.2(27)SBC |
This command was integrated into Cisco IOS Release 12.2(27)SBC, and the dlci argument was added. |
12.2(28)SB |
This command was integrated into Cisco IOS Release 12.2(28)SB. |
12.4(9)T |
The dlci argument was added. |
12.2(33)SRA |
This command was integrated into Cisco IOS Release 12.2(33)SRA. |
12.2SX |
This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware. |
Examples
The following is sample output from the show frame-relay ip tcp header-compression command:
Router# show frame-relay ip tcp header-compression
DLCI 200 Link/Destination info: ip 10.108.177.200
Rcvd: 40 total, 36 compressed, 0 errors
0 dropped, 0 buffer copies, 0 buffer failures
Sent: 0 total, 0 compressed
0 bytes saved, 0 bytes sent
Connect: 16 rx slots, 16 tx slots, 0 long searches, 0 misses, 0% hit ratio
Five minute miss rate 0 misses/sec, 0 max misses/sec
The following sample output from the show frame-relay ip tcp header-compression command shows statistics for a PVC bundle called "MP-3-static":
Router# show frame-relay ip tcp header-compression interface Serial1/4
vc-bundle MP-3-static Link/Destination info:ip 10.1.1.1
Rcvd: 14 total, 13 compressed, 0 errors
0 dropped, 0 buffer copies, 0 buffer failures
Sent: 15 total, 14 compressed,
474 bytes saved, 119 bytes sent
4.98 efficiency improvement factor
Connect:256 rx slots, 256 tx slots,
1 long searches, 1 misses 0 collisions, 0 negative cache hits
93% hit ratio, five minute miss rate 0 misses/sec, 0 max
In the following example, the show frame-relay ip tcp header-compression command displays information about DLCI 21:
Router# show frame-relay ip tcp header-compression 21
DLCI 21 Link/Destination info: ip 10.1.2.1
Interface POS2/0 DLCI 21 (compression on, VJ)
Rcvd: 0 total, 0 compressed, 0 errors, 0 status msgs
0 dropped, 0 buffer copies, 0 buffer failures
Sent: 0 total, 0 compressed, 0 status msgs, 0 not predicted
0 bytes saved, 0 bytes sent
Connect: 256 rx slots, 256 tx slots,
0 misses, 0 collisions, 0 negative cache hits, 256 free contexts
DLCI 21 Link/Destination info: ip 10.1.4.1
Interface Serial3/0 DLCI 21 (compression on, VJ)
Rcvd: 0 total, 0 compressed, 0 errors, 0 status msgs
0 dropped, 0 buffer copies, 0 buffer failures
Sent: 0 total, 0 compressed, 0 status msgs, 0 not predicted
0 bytes saved, 0 bytes sent
Connect: 256 rx slots, 256 tx slots,
0 misses, 0 collisions, 0 negative cache hits, 256 free contexts
The following is sample output from the show frame-relay ip tcp header-compression command for a specific DLCI on a specific interface:
Router# show frame-relay ip tcp header-compression pos2/0 21
DLCI 21 Link/Destination info: ip 10.1.2.1
Interface POS2/0 DLCI 21 (compression on, VJ)
Rcvd: 0 total, 0 compressed, 0 errors, 0 status msgs
0 dropped, 0 buffer copies, 0 buffer failures
Sent: 0 total, 0 compressed, 0 status msgs, 0 not predicted
0 bytes saved, 0 bytes sent
Connect: 256 rx slots, 256 tx slots,
0 misses, 0 collisions, 0 negative cache hits, 256 free contexts
Table 55 describes the fields shown in the display.
Table 55 show frame-relay ip tcp header-compression Field Descriptions
|
|
Rcvd: |
Table of details concerning received packets. |
total |
Sum of compressed and uncompressed packets received. |
compressed |
Number of compressed packets received. |
errors |
Number of errors caused by errors in the header fields (version, total length, or IP checksum). |
dropped |
Number of packets discarded. Seen only after line errors. |
buffer failures |
Number of times that a new buffer was needed but was not obtained. |
Sent: |
Table of details concerning sent packets. |
total |
Sum of compressed and uncompressed packets sent. |
compressed |
Number of compressed packets sent. |
bytes saved |
Number of bytes reduced because of the compression. |
bytes sent |
Actual number of bytes transmitted. |
Connect: |
Table of details about the connections. |
rx slots, tx slots |
Number of states allowed over one TCP connection. A state is recognized by a source address, a destination address, and an IP header length. |
long searches |
Number of times that the connection ID in the incoming packet was not the same as the previous one that was processed. |
misses |
Number of times that a matching entry was not found within the connection table and a new entry had to be entered. |
hit ratio |
Percentage of times that a matching entry was found in the compression tables and the header was compressed. |
Five minute miss rate |
Miss rate computed over the most recent 5 minutes and the maximum per-second miss rate during that period. |
show interfaces fair-queue
Note Effective with Cisco IOS XE Release 2.6, Cisco IOS Release 15.0(1)S, and Cisco IOS Release 15.1(3)T, the show interfaces fair-queue command is hidden. Although this command is still available in Cisco IOS software, the CLI interactive Help does not display it if you attempt to view it by entering a question mark at the command line.
This command will be completely removed in a future release, which means that you will need to use the appropriate replacement command (or sequence of commands). For more information (including a list of replacement commands), see the Legacy QoS Command Deprecation feature document in the Cisco IOS XE Quality of Service Solutions Configuration Guide or the Legacy QoS Command Deprecation feature document in the Cisco IOS Quality of Service Solutions Configuration Guide.
Note Effective with Cisco IOS XE Release 3.2S, the show interfaces fair-queue command is replaced by a modular QoS CLI (MQC) command (or sequence of MQC commands). For the appropriate replacement command (or sequence of commands), see the Legacy QoS Command Deprecation feature document in the Cisco IOS XE Quality of Service Solutions Configuration Guide.
To display information and statistics about weighted fair queueing (WFQ) for a Versatile Interface Processor (VIP)-based interface, use the show interfaces fair-queue command in EXEC mode.
show interfaces [type number] fair-queue
Syntax Description
type |
(Optional) The type of the interface. |
number |
(Optional) The number of the interface. |
Command Modes
EXEC
Command History
|
|
11.1CC |
This command was introduced. |
12.2(33)SRA |
This command was integrated into Cisco IOS Release 12.2(33)SRA. |
12.2SX |
This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware. |
Cisco IOS XE Release 2.6 |
This command was modified. This command was hidden. |
15.0(1)S |
This command was modified. This command was hidden. |
15.1(3)T |
This command was modified. This command was hidden. |
Cisco IOS XE Release 3.2S |
This command was replaced by an MQC command (or sequence of MQC commands). |
Examples
The following is sample output from the show interfaces fair-queue command for VIP-distributed WFQ (DWFQ):
Router# show interfaces fair-queue
packets output 1417079, drops 2
WFQ: aggregate queue limit 54, individual queue limit 27
Class 0: weight 10 limit 27 qsize 0 packets output 1150 drops 0
Class 1: weight 20 limit 27 qsize 0 packets output 0 drops 0
Class 2: weight 30 limit 27 qsize 0 packets output 775482 drops 1
Class 3: weight 40 limit 27 qsize 0 packets output 0 drops 0
Table 56 ddescribes the significant fields shown in the display.
Table 56 show interfaces fair-queue Field Descriptions
|
|
queue size |
Current output queue size for this interface. |
packets output |
Number of packets sent out this interface or number of packets in this class sent out the interface. |
drops |
Number of packets dropped or number of packets in this class dropped. |
aggregate queue limit |
Aggregate limit, in number of packets. |
individual queue limit |
Individual limit, in number of packets. |
max available buffers |
Available buffer space allocated to aggregate queue limit, in number of packets. |
Class |
QoS group or type of service (ToS) class. |
weight |
Percent of bandwidth allocated to this class during periods of congestion. |
limit |
Queue limit for this class in number of packets. |
qsize |
Current size of the queue for this class. |
Related Commands
|
|
show interfaces |
Displays statistics for all interfaces configured on the router or access server. |
show interfaces random-detect
Note Effective with Cisco IOS XE Release 2.6, Cisco IOS Release 15.0(1)S, and Cisco IOS Release 15.1(3)T, the show interfaces random-detect command is hidden. Although this command is still available in Cisco IOS software, the CLI interactive Help does not display it if you attempt to view it by entering a question mark at the command line.
This command will be completely removed in a future release, which means that you will need to use the appropriate replacement command (or sequence of commands). For more information (including a list of replacement commands), see the Legacy QoS Command Deprecation feature document in the Cisco IOS XE Quality of Service Solutions Configuration Guide or the Legacy QoS Command Deprecation feature document in the Cisco IOS Quality of Service Solutions Configuration Guide.
Note Effective with Cisco IOS XE Release 3.2S, the show interfaces random-detect command is replaced by a modular QoS CLI (MQC) command (or sequence of MQC commands). For the appropriate replacement command (or sequence of commands), see the Legacy QoS Command Deprecation feature document in the Cisco IOS XE Quality of Service Solutions Configuration Guide.
To display information about Weighted Random Early Detection (WRED) for a Versatile Interface Processor (VIP)-based interface, use the show interfaces random-detect command in EXEC mode.
show interfaces [type number] random-detect
Syntax Description
type |
(Optional) The type of the interface. |
number |
(Optional) The number of the interface. |
Command Modes
EXEC
Command History
|
|
11.1CC |
This command was introduced. |
12.2(33)SRA |
This command was integrated into Cisco IOS Release 12.2(33)SRA. |
12.2SX |
This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware. |
Cisco IOS XE Release 2.6 |
This command was modified. This command was hidden. |
15.0(1)S |
This command was modified. This command was hidden. |
15.1(3)T |
This command was modified. This command was hidden. |
Cisco IOS XE Release 3.2S |
This command was replaced by an MQC command (or sequence of MQC commands). |
Examples
The following is sample output from the show interfaces random-detect command for VIP-distributed WRED (DWRED):
Router# show interfaces random-detect
FastEthernet1/0/0 queue size 0
packets output 29692, drops 0
Precedence 0: 109 min threshold, 218 max threshold, 1/10 mark weight
1 packets output, drops: 0 random, 0 threshold
Precedence 1: 122 min threshold, 218 max threshold, 1/10 mark weight
Precedence 2: 135 min threshold, 218 max threshold, 1/10 mark weight
14845 packets output, drops: 0 random, 0 threshold
Precedence 3: 148 min threshold, 218 max threshold, 1/10 mark weight
Precedence 4: 161 min threshold, 218 max threshold, 1/10 mark weight
Precedence 5: 174 min threshold, 218 max threshold, 1/10 mark weight
Precedence 6: 187 min threshold, 218 max threshold, 1/10 mark weight
14846 packets output, drops: 0 random, 0 threshold
Precedence 7: 200 min threshold, 218 max threshold, 1/10 mark weight
Table 57 describes the significant fields shown in the display.
Table 57 show interfaces random-detect Field Descriptions
|
|
queue size |
Current output queue size for this interface. |
packets output |
Number of packets sent out this interface. |
drops |
Number of packets dropped. |
queue average |
Average queue length. |
weight |
Weighting factor used to determine the average queue size. |
Precedence |
WRED parameters for this precedence. |
min threshold |
Minimum threshold for this precedence. |
max threshold |
Maximum length of the queue. When the average queue is this long, any additional packets will be dropped. |
mark weight |
Probability of a packet being dropped if the average queue is at the maximum threshold. |
packets output |
Number of packets with this precedence that have been sent. |
random |
Number of packets dropped randomly through the WRED process. |
threshold |
Number of packets dropped automatically because the average queue was at the maximum threshold length. |
(no traffic) |
No packets with this precedence. |
Related Commands
|
|
random-detect (interface) |
Enables WRED or DWRED. |
random-detect flow |
Enables flow-based WRED. |
show interfaces |
Displays statistics for all interfaces configured on the router or access server. |
show queueing |
Lists all or selected configured queueing strategies. |
show interfaces rate-limit
To display information about committed access rate (CAR) for an interface, use the show interfaces rate-limit command in EXEC mode.
show interfaces [type number] rate-limit
Syntax Description
type |
(Optional) The type of the interface. |
number |
(Optional) The number of the interface. |
Command Modes
EXEC
Command History
|
|
11.1CC |
This command was introduced. |
12.2(33)SRA |
This command was integrated into Cisco IOS Release 12.2(33)SRA. |
12.2SX |
This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware. |
Examples
The following is sample output from the show interfaces rate-limit command:
Router# show interfaces fddi2/1/0 rate-limit
matches: access-group rate-limit 100
params: 800000000 bps, 64000 limit, 80000 extended limit
conformed 0 packets, 0 bytes; action: set-prec-continue 1
exceeded 0 packets, 0 bytes; action: set-prec-continue 0
last packet: 4737508ms ago, current burst: 0 bytes
last cleared 01:05:47 ago, conformed 0 bps, exceeded 0 bps
matches: access-group 101
params: 80000000 bps, 56000 limit, 72000 extended limit
conformed 0 packets, 0 bytes; action: set-prec-transmit 5
exceeded 0 packets, 0 bytes; action: set-prec-transmit 0
last packet: 4738036ms ago, current burst: 0 bytes
last cleared 01:02:05 ago, conformed 0 bps, exceeded 0 bps
params: 50000000 bps, 48000 limit, 64000 extended limit
conformed 0 packets, 0 bytes; action: set-prec-transmit 5
exceeded 0 packets, 0 bytes; action: set-prec-transmit 0
last packet: 4738036ms ago, current burst: 0 bytes
last cleared 01:00:22 ago, conformed 0 bps, exceeded 0 bps
params: 80000000 bps, 64000 limit, 80000 extended limit
conformed 0 packets, 0 bytes; action: transmit
exceeded 0 packets, 0 bytes; action: drop
last packet: 4809528ms ago, current burst: 0 bytes
last cleared 00:59:42 ago, conformed 0 bps, exceeded 0 bps
Table 58 describes the significant fields shown in the display.
Table 58 show interfaces rate-limit Field Descriptions
|
|
Input |
These rate limits apply to packets received by the interface. |
matches |
Packets that match this rate limit. |
params |
Parameters for this rate limit, as configured by the rate-limit command. |
bps |
Average rate, in bits per second. |
limit |
Normal burst size, in bytes. |
extended limit |
Excess burst size, in bytes. |
conformed |
Number of packets that have conformed to the rate limit. |
action |
Conform action. |
exceeded |
Number of packets that have exceeded the rate limit. |
action |
Exceed action. |
last packet |
Time since the last packet, in milliseconds. |
current burst |
Instantaneous burst size at the current time. |
last cleared |
Time since the burst counter was set back to zero by the clear counters command. |
conformed |
Rate of conforming traffic. |
exceeded |
Rate of exceeding traffic. |
Output |
These rate limits apply to packets sent by the interface. |
Related Commands
|
|
access-list rate-limit |
Configures an access list for use with CAR policies. |
clear counters |
Clears the interface counters. |
shape |
Specifies average or peak rate traffic shaping. |
show access-lists |
Displays the contents of current IP and rate-limit access lists. |
show interfaces |
Displays statistics for all interfaces configured on the router or access server. |
show iphc-profile
To display configuration information for one or more IP Header Compression (IPHC) profiles, use the show iphc-profile command in user EXEC or privileged EXEC mode.
show iphc-profile [profile-name]
Syntax Description
profile-name |
(Optional) Name of an IPHC profile to display. |
Command Default
If you do not specify an IPHC profile name, all IPHC profiles are displayed.
Command Modes
User EXEC (>)
Privileged EXEC (#)
Command History
|
|
12.4(9)T |
This command was introduced. |
12.4(24)T |
This command was modified. The output was enhanced to display recoverable loss when EcRTP is configured. |
Usage Guidelines
Information Included in Display
The display includes information such as the profile type, the type of header compression enabled, the number of contexts, the refresh period (for Real-Time Transport [RTP] header compression), whether feedback messages are disabled, and the interfaces to which the IPHC profile is attached.
For More Information About IPHC Profiles
An IPHC profile is used to enable and configure header compression on your network. For more information about using IPHC profiles to configure header compression, see the "Header Compression" module and the "Configuring Header Compression Using IPHC Profiles" module of the Cisco IOS Quality of Service Solutions Configuration Guide.
Examples
The following is sample output from the show iphc-profile command. In the output, information about two IPHC profiles, profile19 and profile20, is displayed.
Router# show iphc-profile
Compressing: NON-TCP (RTP)
Contexts : NON-TCP fixed at 0
Refresh : NON-TCP every 5 seconds or 256 packets
EcRTP : recoverable loss enabled 1
Controlled interfaces: (0)
Compressing: NON-TCP (RTP)
Contexts : NON-TCP fixed at 0
Refresh : NON-TCP every 5 seconds or 256 packets
EcRTP : recoverable loss enabled 4 (dynamic)
Controlled interfaces: (0)
Table 59 describes the significant fields shown in the display.
Table 59 show iphc-profile Field Descriptions
|
|
IPHC Profile |
IPHC profile name. |
Type |
IPHC profile type: either VJ (for van-jacobson) or IETF. |
Compressing |
Type of header compression used, such as TCP, non-TCP, or RTP. |
Contexts |
Number of contexts and setting used to calculate the context number. |
Refresh |
Indicates maximum number of packets or maximum time between context refresh. |
EcRTP |
Indicates if recoverable loss is enabled and if EcRTP recoverable loss is configured to dynamic. |
Controlled interfaces |
Interfaces to which the IPHC profile is attached. |
Reference Count |
Indicates the number of active IPHC-profile submodes. |
Related Commands
|
|
iphc-profile |
Creates an IPHC profile. |
show ip nbar link-age
To display the protocol linkage by network-based application recognition (NBAR), use the show ip nbar link-age command in privileged EXEC mode.
show ip nbar link-age [protocol-name]
Syntax Description
protocol-name |
(Optional) Displays the linkage for only the specified protocol name. |
Command Modes
Privileged EXEC (#)
Command History
|
|
12.4(20)T |
This command was introduced. |
Cisco IOS XE Release 2.1 |
This command was implemented on Cisco ASR 1000 series routers. |
Usage Guidelines
The show ip nbar link-age command displays the linkage of all the NBAR protocols. The protocol-name argument can be used to limit the display for a specific protocol.
Examples
The following is sample output from the show ip nbar link-age command:
Router# show ip nbar link-age
System Link Age: 30 seconds
No. Protocol Link Age (seconds)
The following is sample output from the show ip nbar link-age command for a specific protocol:
Router# show ip nbar link-age eigrp
System Link Age: 30 seconds
Protocol Link Age (seconds)
Table 60 describes the significant fields shown in the display.
Table 60 show ip nbar link-age Field Descriptions
|
|
No. |
Serial number of the list of protocols displayed. |
Protocol |
Name of the NBAR protocol. |
Link Age (seconds) |
Time, in seconds, at which the links for a protocol are aged (expire). |
Related Commands
|
|
ip nbar resources protocol |
Sets the expiration time for NBAR flow-link tables on a protocol basis. |
show ip nbar pdlm
To display the Packet Description Language Module (PDLM) in use by network-based application recognition (NBAR), use the show ip nbar pdlm command in privileged EXEC mode.
show ip nbar pdlm
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
|
|
12.0(5)XE2 |
This command was introduced. |
12.1(1)E |
This command was integrated into Cisco IOS Release 12.1(1)E. |
12.1(5)T |
This command was integrated into Cisco IOS Release 12.1(5)T. |
12.1(13)E |
This command was implemented on Catalyst 6000 family switches without FlexWAN modules. |
12.2(14)S |
This command was integrated into Cisco IOS Release 12.2(14)S. |
12.2(17a)SX1 |
This command was integrated into Cisco IOS Release 12.2(17a)SX1. |
12.2(33)SRA |
This command was integrated into Cisco IOS Release 12.2(33)SRA. |
Usage Guidelines
This command is used to display a list of all the PDLMs that have been loaded into NBAR using the ip nbar pdlm command.
Examples
In this example of the show ip nbar pdlm command, the citrix.pdlm PDLM has been loaded from Flash memory:
Router# show ip nbar pdlm
The following PDLMs have been loaded:
Related Commands
|
|
ip nbar pdlm |
Extends or enhances the list of protocols recognized by NBAR through a Cisco-provided PDLM. |
show ip nbar port-map
To display the current protocol-to-port mappings in use by network-based application recognition (NBAR), use the show ip nbar port-map command in privileged EXEC mode.
show ip nbar port-map [protocol-name [protocol-type]]
Syntax Description
protocol-name |
(Optional) Name of the protocol. For more information on the available protocols, use the question mark (?) online help function. |
protocol-type |
(Optional) Type of the protocol. Two types of protocols can be specified: •tcp—Displays information related to Transmission Control Protocol (TCP) ports. •udp—Displays information related to User Datagram Protocol (UDP) ports. |
Command Modes
Privileged EXEC (#)
Command History
|
|
12.0(5)XE2 |
This command was introduced. |
12.1(1)E |
This command was integrated into Cisco IOS Release 12.1(1)E. |
12.1(13)E |
This command was implemented on Catalyst 6000 family switches. The FlexWAN modules were removed. |
12.2(14)S |
This command was integrated into Cisco IOS Release 12.2(14)S. |
12.2(17a)SX1 |
This command was integrated into Cisco IOS Release 12.2(17a)SX1. |
12.2(33)SRA |
This command was integrated into Cisco IOS Release 12.2(33)SRA. |
12.4(22)T |
This command was integrated into Cisco IOS Release 12.4(22)T. |
15.1(3)T |
This command was integrated into Cisco IOS Release 15.1(3)T. |
Usage Guidelines
The show ip nbar port-map command displays port assignments for NBAR protocols.
You can use the show ip nbar port-map command to display the current protocol-to-port mappings in use by NBAR. When you use the ip nbar port-map command, the show ip nbar port-map command displays the ports you have assigned to the protocol. If you do not use the ip nbar port-map command to configure any protocol, the show ip nbar port-map command displays the default ports. Use the protocol-name argument to limit the display to a specific protocol. You can either use the UDP or the TCP protocol-type argument type.
Examples
The following is sample output from the show ip nbar port-map command:
Router# show ip nbar port-map
port-map cuseeme udp 7648 7649 24032
port-map cuseeme tcp 7648 7649
Table 61 describes the significant fields shown in the display.
Table 61 show ip route track-table Field Descriptions
|
|
port-map |
Specifies the ports assigned. |
cuseeme |
Specifies that the CU-SeeMe Protocol is used. |
udp |
Specifies the User Datagram Protocol type. |
tcp |
Specifies the Transmission Control Protocol type. |
dhcp |
Specifies the Dynamic Host Configuration Protocol type. |
Related Commands
|
|
ip nbar port-map |
Configures NBAR to search for a protocol or protocol name using a port number other than the well-known port number. |
show ip nbar protocol-discovery
To display the statistics gathered by the Network-Based Application Recognition (NBAR) Protocol Discovery feature, use the show ip nbar protocol-discovery command in privileged EXEC mode.
show ip nbar protocol-discovery [interface type number] [stats {byte-count | bit-rate | packet-count | max-bit-rate}] [protocol protocol-name] [top-n number]
Syntax Description
interface |
(Optional) Specifies that Protocol Discovery statistics for the interface are to be displayed. |
type |
Type of interface or subinterface whose policy configuration is to be displayed. |
number |
Port, connector, VLAN, or interface card number. |
stats |
(Optional) Specifies that the byte count, byte rate, or packet count is to be displayed. |
byte-count |
(Optional) Specifies that the byte count is to be displayed. |
max-bit-rate |
(Optional) Specifies that the maximum bit rate is to be displayed. |
packet-count |
(Optional) Specifies that the packet count is to be displayed. |
protocol |
(Optional) Specifies that statistics for a specific protocol are to be displayed. |
protocol-name |
(Optional) User-specified protocol name for which the statistics are to be displayed. |
top-n |
(Optional) Specifies that a top-n is to be displayed. A top-n is the number of most active NBAR-supported protocols, where n is the number of protocols to be displayed. For instance, if top-n 3 is entered, the three most active NBAR-supported protocols will be displayed. |
number |
(Optional) Specifies the number of most active NBAR-supported protocols to be displayed. |
Command Default
Statistics for all interfaces on which the NBAR Protocol Discovery feature is enabled are displayed.
Command Modes
Privileged EXEC (#)
Command History
|
|
12.0(5)XE2 |
This command was introduced. |
12.1(1)E |
This command was integrated into Cisco IOS Release 12.1(1)E. |
12.1(5)T |
This command was integrated into Cisco IOS Release 12.1(5)T. |
12.1(13)E |
This command was implemented on Catalyst 6000 family switches without FlexWAN modules. |
12.2(14)S |
This command was integrated into Cisco IOS Release 12.2(14)S. |
12.2(17a)SX1 |
This command was integrated into Cisco IOS Release 12.2(17a)SX1. |
12.3(7)T |
The command output was modified to include Max Bit Rate. |
12.2(33)SRA |
This command was integrated into Cisco IOS Release 12.2(33)SRA. |
12.2(18)ZYA |
This command was integrated into Cisco IOS Release 12.2(18)ZYA. This command was modified to include information about VLANs (as applicable) and to provide support for both Layer 2 and Layer 3 Etherchannels (Catalyst switches only). |
15.1(3)T |
This command was integrated into Cisco IOS Release 15.1(3)T. |
Usage Guidelines
Use the show ip nbar protocol-discovery command to display statistics gathered by the NBAR Protocol Discovery feature. This command, by default, displays statistics for all interfaces on which protocol discovery is currently enabled. The default output of this command includes, in the following order, input bit rate (in bits per second), input byte count, input packet count, and protocol name.
Protocol discovery can be used to monitor both input and output traffic and may be applied with or without a service policy enabled. NBAR protocol discovery gathers statistics for packets switched to output interfaces. These statistics are not necessarily for packets that exited the router on the output interfaces, because packets may have been dropped after switching for various reasons, including policing at the output interface, access lists, or queue drops.
Layer 2/3 Etherchannel Support
With Cisco IOS Release 12.2(18)ZYA, intended for use on the Cisco 6500 series switch that is equipped with a Supervisor 32/programmable intelligent services accelerator (PISA), the show ip nbar protocol-discovery command is supported on both Layer 2 and Layer 3 Etherchannels.
Examples
The following example displays output from the show ip nbar protocol-discovery command for the five most active protocols on an Ethernet interface:
Router# show ip nbar protocol-discovery top-n 5
Protocol Packet Count Packet Count
30sec Bit Rate (bps) 30sec Bit Rate (bps)
30sec Max Bit Rate (bps) 30sec Max Bit Rate (bps)
--------------------------- ------------------------ ------------------------
Table 62 describes the significant fields shown in the display.
Table 62 show ip nbar protocol-discovery Field Descriptions
|
|
Interface |
Type and number of an interface. |
Input |
Incoming traffic on an interface. |
Output |
Outgoing traffic on an interface. |
Protocol |
The protocols being used. Unknown is the sum of all the protocols that NBAR could not classify for some reason. |
Packet Count |
Number of packets coming in and going out the interface. |
Byte Count |
Number of bytes coming in and going out the interface. |
30sec Bit Rate |
Average value of the bit rate in bits per second (bps) since protocol discovery was enabled, per protocol, over the last 30 seconds. |
30sec Max Bit Rate |
Highest value of the bit rate in bits per second (bps) since protocol discovery was enabled, per protocol, over the last 30 seconds. |
Total |
Total input and output traffic. |
Related Commands
|
|
ip nbar protocol-discovery |
Configures NBAR to discover traffic for all protocols known to NBAR on a particular interface. |
show ip nbar protocol-id
To display information about Network-Based Application Recognition (NBAR) protocol IDs, use the show ip nbar protocol-id command in privileged EXEC mode.
show ip nbar protocol-id [protocol-name]
Syntax Description
protocol-name |
(Optional) Name of the protocol. |
Command Default
If the optional argument is not specified, NBAR protocol IDs for all protocols are displayed.
Command Modes
Privileged EXEC (#)
Command History
|
|
15.0(1)M |
This command was introduced. |
12.2(33)SRE |
This command was integrated into Cisco IOS Release 12.2(33)SRE. |
15.1(1)S |
This command was integrated into Cisco IOS Release 15.1(1)S. |
Cisco IOS XE Release 3.2S |
This command was modified. Support for additional IANA protocols was added. |
Examples
The following is sample output from the show ip nbar protocol-id command:
Router# show ip nbar protocol-id
----------------------------------------------
secure-telnet 992 L4 IANA
directconnect 70 Standard
msn-messenger 75 Standard
yahoo-messenger 77 Standard
aol-messenger 79 Standard
telepresence-media 113 Standard
telepresence-control 114 Standard
cloanto-net-1 356 L4 IANA
hp-managed-node 382 L4 IANA
synotics-relay 391 L4 IANA
synotics-broker 392 L4 IANA
synoptics-trap 412 L4 IANA
opc-job-start 423 L4 IANA
opc-job-track 424 L4 IANA
mobileip-agent 434 L4 IANA
decvms-sysmgt 441 L4 IANA
creativeserver 453 L4 IANA
contentserver 3365 L4 IANA
creativepartnr 455 L4 IANA
datasurfsrvsec 462 L4 IANA
nest-protocol 489 L4 IANA
asa-appl-proto 502 L4 IANA
dhcpv6-client 546 L4 IANA
dhcpv6-server 547 L4 IANA
openvms-sysipc 557 L4 IANA
sntp-heartbeat 580 L4 IANA
http-rpc-epmap 593 L4 IANA
ptcnameservice 597 L4 IANA
sco-websrvrmg3 598 L4 IANA
sco-websrvrmgr 620 L4 IANA
passgo-tivoli 627 L4 IANA
dhcp-failover 647 L4 IANA
mac-srvr-admin 660 L4 IANA
mdc-portmapper 685 L4 IANA
msexch-routing 691 L4 IANA
hyperwave-isp 692 L4 IANA
accessnetwork 699 L4 IANA
multiling-http 777 L4 IANA
dhcp-failover2 847 L4 IANA
iclcnet-locate 886 L4 IANA
iclcnet_svinfo 887 L4 IANA
accessbuilder 888 L4 IANA
omginitialrefs 900 L4 IANA
rmiactivation 1098 L4 IANA
rdb-dbs-disp 1571 L4 IANA
oraclenet8cman 1630 L4 IANA
micromuse-lm 1534 L4 IANA
orbix-locator 3075 L4 IANA
orbix-config 3076 L4 IANA
orbix-loc-ssl 3077 L4 IANA
sitaraserver 2629 L4 IANA
net-assistant 3283 L4 IANA
directv-soft 3335 L4 IANA
directv-tick 3336 L4 IANA
directv-catlg 3337 L4 IANA
wap-pushsecure 2949 L4 IANA
wap-push-http 4035 L4 IANA
wap-push-https 4036 L4 IANA
wap-wsp-wtp-s 9203 L4 IANA
subntbcst_tftp 247 L4 IANA
personal-link 281 L4 IANA
novastorbakcup 308 L4 IANA
asip-webadmin 311 L4 IANA
magenta-logic 313 L4 IANA
pkix-timestamp 318 L4 IANA
Table 63 describes the significant fields shown in the display.
Table 63 show ip nbar protocol-id Field Descriptions
|
|
Protocol Name |
Name of the NBAR protocol. |
id |
Unique identifier assigned to the NBAR protocol. |
type |
Indicates whether the protocol is standard or customized. |
Related Commands
|
|
ip nbar custom |
Extends the capability of NBAR Protocol Discovery to classify and monitor additional static port applications or allows NBAR to classify nonsupported static port traffic. |
show ip nbar protocol-pack
To display protocol pack information, use the show ip nbar protocol-pack command in user EXEC or privileged EXEC mode.
show ip nbar protocol-pack {protocol-pack | active} [detail]
Syntax Description
protocol-pack |
Protocol pack file path and name. |
active |
Displays active protocol pack information. |
detail |
(Optional) Displays detailed protocol pack information. |
Command Modes
User EXEC (>)
Privileged EXEC (#)
Command History
|
|
Cisco IOS XE Release 3.3S |
This command was introduced. |
Usage Guidelines
The protocol pack is a single compressed file that contains multiple Protocol Description Language (PDL) files and a manifest file. Before the protocol pack was introduced, PDLs had to be loaded separately. Now a set of required protocols can be loaded, which helps network-based application recognition (NBAR) to recognize additional protocols for classification on your network.
Examples
The following sample output from the show ip nbar protocol-pack command shows information about the active protocol pack:
Router# show ip nbar protocol-pack active
Name: Default Protocol Pack
Publisher: Cisco Systems Inc.
The following sample output from the show ip nbar protocol-pack command shows detailed information about the active protocol pack:
Router# show ip nbar protocol-pack active detail
Name: Default Protocol Pack
Publisher: Cisco Systems Inc.
Table 64 describes the significant fields shown in the display.
Table 64 show ip nbar protocol-pack Field Descriptions
|
|
Name |
Name of the protocol pack. |
Version |
Protocol pack version. |
Publisher |
Name of the publisher of the protocol pack. |
Protocols |
List of protocols present in the protocol pack. |
Related Commands
|
|
default ip nbar protocol-pack |
Loads the base version of the protocol pack and removes all other loaded protocol packs. |
ip nbar protocol-pack |
Loads a protocol pack. |
show ip nbar unclassified-port-stats
To display the network-based application recognition (NBAR) port statistics for unclassified packets, use the show ip nbar unclassified-port-stats command in privileged EXEC mode.
show ip nbar unclassified-port-stats [top-talkers | ip [protocol-number [number-protocols] | top top-talkers] | [tcp | udp] [port-number [number-ports] | top top-talkers | bottom bottom-talkers]]
Syntax Description
top-talkers |
(Optional) Number of top talkers to show. |
ip |
(Optional) Displays port statistics for unclassified non-TCP/non-UDP packets. |
protocol-number |
(Optional) Starting IP protocol number. |
number-protocols |
(Optional) Number of protocols to show. |
top |
(Optional) Specifies that a top-n is to be displayed. A top-n is the number of most active NBAR-supported protocols, where n is the number of protocols to be displayed. For instance, if top-n 3 is entered, the three most active NBAR-supported protocols are displayed. |
tcp |
(Optional) Displays port statistics for unclassified TCP packets. |
udp |
(Optional) Displays port statistics for unclassified UDP packets. |
port-number |
(Optional) Starting TCP or UDP port number. |
number-ports |
(Optional) Number of ports to show. |
bottom |
(Optional) Specifies that a bottom-n is to be displayed. A bottom-n is the number of least active NBAR-supported protocols, where n is the number of protocols to be displayed. For instance, if bottom-n 3 is entered, the three least active NBAR-supported protocols are displayed. |
bottom-talkers |
(Optional) Number of bottom talkers to show. |
Command Modes
Privileged EXEC (#)
Command History
|
|
12.0(5)XE2 |
This command was introduced. |
12.1(1)E |
This command was integrated into Cisco IOS Release 12.1(1)E. |
12.1(5)T |
This command was integrated into Cisco IOS Release 12.1(5)T. |
12.1(13)E |
This command was implemented on Cisco Catalyst 6000 family switches without FlexWAN modules. |
12.2(14)S |
This command was integrated into Cisco IOS Release 12.2(14)S. |
12.2(17a)SX1 |
This command was integrated into Cisco IOS Release 12.2(17a)SX1. |
12.2(33)SRA |
This command was integrated into Cisco IOS Release 12.2(33)SRA. |
12.2(18)ZYA |
This command was integrated into Cisco IOS Release 12.2(18)ZYA. This command was modified to include information about VLANs (as applicable) and to provide support for both Layer 2 and Layer 3 Etherchannels (Cisco Catalyst switches only). |
Usage Guidelines
By default, NBAR unclassified mechanisms are not enabled. Use the debug ip nbar unclassified-port-stats command to enable the router to begin tracking the ports on which packets arrive. Then use the show ip nbar unclassified-port-stats command to verify the collected information.
Examples
The following is sample output from show ip nbar unclassified-port-stats command.
Note The output displays the port number, the protocol and the number of packets. For example, in 80/tcp:48, 80 represents the port number; tcp, the protocol, and 48, the number of packets.
Router# show ip nbar unclassified-port-stats
Table 65 describes the significant fields shown in the display.
Table 65 show ip nbar unclassified-port-stats Field Descriptions
|
|
-tcp- |
TCP Protocol. |
80/tcp:48 |
80 represents the port number, tcp the protocol and 48 the number of packets. |
-udp- |
UDP protocol. |
1985/udp:158 |
1855 represents the port number, udp the protocol and 158 the number of packets. |
Related Commands
|
|
debug ip nbar unclassified-port-stats |
Enables the router to begin tracking the ports on which packets arrive. |
ip nbar custom |
Extends the capability of NBAR Protocol Discovery to classify and monitor additional static port applications or to allow NBAR to classify nonsupported static port traffic. |
ip nbar pdlm |
Extends or enhances the list of protocols recognized by NBAR through a Cisco-provided PDLM. |
ip nbar port-map |
Configures NBAR to search for a protocol or protocol name using a port number other than the well-known port number. |
ip nbar protocol-discovery |
Configures NBAR to discover traffic for all protocols that are known to NBAR on a particular interface. |
ip nbar resources protocol |
Sets the expiration time for NBAR flow-link tables on a protocol basis. |
ip nbar resources system |
Sets the expiration time and memory requirements for NBAR flow-link tables on a systemwide basis. |
show ip nbar pdlm |
Displays the PDLM in use by NBAR. |
show ip nbar port-map |
Displays the current protocol-to-port mappings in use by NBAR. |
show ip nbar protocol-discovery |
Displays the statistics gathered by the NBAR Protocol Discovery feature. |
show ip nbar version |
Displays information about the version of the NBAR software in your Cisco IOS release or the version of an NBAR PDLM on your Cisco IOS router. |
show ip nbar version
To display information about the version of the network-based application recognition (NBAR) software in your Cisco IOS release or the version of an NBAR Packet Description Language Module (PDLM) on your Cisco IOS router, use the show ip nbar version command in privileged EXEC mode.
show ip nbar version [PDLM-name]
Syntax Description
PDLM-name |
(Optional) Specifies the name of a specific PDLM whose information will be displayed. |
Command Modes
Privileged EXEC
Command History
|
|
12.3(4)T |
This command was introduced. |
12.2(14)S |
This command was integrated into Cisco IOS Release 12.2(14)S. |
12.2(17a)SX1 |
This command was integrated into Cisco IOS Release 12.2(17a)SX1. |
15.1(3)T |
This command was integrated into Cisco IOS Release 15.1(3)T. |
Usage Guidelines
The show ip nbar version command treats all protocols that were added to NBAR after the initial NBAR release as PDLMs, including protocols that were added into the Cisco IOS software without a user having to download a PDLM from Cisco.com. PDLMs downloaded from Cisco.com and incorporated into NBAR by the user also appear when the show ip nbar version command is entered.
When using NBAR, various elements within NBAR are assigned versioning numbers. These versioning numbers become significant when you want to download a PDLM. PDLMs, which are also versioned, can be downloaded only to NBAR on a particular Cisco IOS release if the PDLM versioning numbers are compatible with the NBAR version numbers in the Cisco IOS software.
The following NBAR-related version information is available:
•NBAR Software Version—Version of NBAR software running on the current version of Cisco IOS software.
•Resident Module Version—Version of the NBAR-supported PDLM protocol.
The following version number is kept by the PDLM:
•NBAR Software Version—Minimum version of the NBAR software that is required to load this PDLM.
The show ip nbar version command provides version information for PDLMs already loaded onto the Cisco IOS software.
Examples
The following is sample output from the show ip nbar version command:
Router# show ip nbar version
3 http Mv: 7, Nv: 3; slot1:http_vers.pdlm
16 kazaa Mv: 6, Nv: 3; slot1:kazaa2_vers.pdlm
17 custom-protocols Mv: 1
Table 66 describes the significant fields shown in the display.
Table 66 show ip nbar version Command Field Descriptions
|
|
NBAR Software Version |
NBAR software version running in the current Cisco IOS software. In this particular example, version 3 is the NBAR software running on the current version of the Cisco IOS software. |
Mv |
Resident Module Version. The Resident Module Version is the version of the NBAR-supported PDLM protocol and, therefore, varies by protocol. The Resident Module Version of TFTP, for example, is 1. |
Nv |
Minimum version of the NBAR software that is required to load a nonnative PDLM. This number is available only for nonnative PDLMs that were loaded onto the router such as the Kazaa PDLM (protocol 17); in that case, the Nv version is 3. |
For the same network setup, the following example shows the output if a specific protocol with a PDLM is specified in the show ip nbar version CLI:
Router# show ip nbar version http
http Mv: 7, Nv: 3; slot1:http_vers.pdlm
Related Commands
|
|
ip nbar pdlm |
Downloads a PDLM onto a router to add support for additional protocols in NBAR. |
show ip rsvp
To display information about the Resource Reservation Protocol (RSVP), use the show ip rsvp command in user EXEC or privileged EXEC mode.
show ip rsvp
Syntax Description
This command has no arguments or keywords.
Command Modes
User EXEC (>)
Privileged EXEC (#)
Command History
|
|
12.0(3)T |
This command was introduced. |
12.2(13)T |
This command was modified. The listeners and policy keywords were added, and this command was modified to display RSVP global settings when no keywords or arguments are entered. |
12.2(33)SRB |
This command was modified. The command output was modified to display fast local repair (FLR) information. |
12.2SX |
This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware. |
12.2(33)SRC |
This command was modified. The command output was modified to display the following: •RSVP quality of service (QoS) and Multiprotocol Label Switching (MPLS) traffic engineering (TE) information. •RSVP aggregation information. |
15.0(1)M |
This command was modified. The [atm-peak-rate-limit | counters | host | installed | interface | listeners | neighbor | policy | precedence | request | reservation | sbm | sender | signalling | tos] syntax was removed from the command. The keyword options are represented in the following individual command files: show ip rsvp atm-peak-rate-limit, show ip rsvp counters, show ip rsvp host, show ip rsvp installed, show ip rsvp interface, show ip rsvp listeners, show ip rsvp neighbor, show ip rsvp policy, show ip rsvp precedence, show ip rsvp request, show ip rsvp reservation, show ip rsvp sbm, show ip rsvp sender, show ip rsvp signalling, and show ip rsvp tos commands. |
Cisco IOS XE Release 2.6 |
This command was integrated into Cisco IOS XE Release 2.6. |
Examples
The following is sample output from the show ip rsvp command:
RSVP: enabled (on 1 interface(s))
RSVP QoS signalling enabled
MPLS/TE signalling enabled
Refresh interval (msec): 30000
Refresh Reduction: disabled
Initial retransmit delay (msec): 1000
Message IDs: in use 0, total allocated 0, total freed 0
Raw IP encap: 0 UDP encap: 0 Raw IP, UDP encap: 0
RFC 3175 Aggregation: Enabled
Default QoS service: Controlled-Load
Number of signaled aggregate reservations: 0
Number of signaled E2E reservation: 0
Number of configured map commands: 0
Number of configured reservation commands: 0
RSVP Hello for Fast-Reroute/Reroute: Disabled
BFD for Fast-Reroute/Reroute: Disabled
RSVP Hello for Graceful Restart: Disabled
Graceful Restart: Disabled
Refresh interval: 10000 msecs
Advertised restart time: 5 msecs
Advertised recovery time: 0 msecs
Maximum wait for recovery: 3600000 msecs
PSBs w/ Local protection desired
Fast Local Repair: enabled
Max repair rate (paths/sec): 400
Max processed (paths/run): 1000
Default policy: Accept all
Table 67 describes the significant fields shown in the display.
Table 67 show ip rsvp Field Descriptions
|
|
RSVP |
The state of RSVP, QoS, and MPLS TE signaling; values are enabled (activated) or disabled (deactivated). Note This field is disabled only if an internal error occurred when registering with RIB. |
Signalling |
The RSVP signaling parameters in effect are as follows: •Refresh interval—Time, in milliseconds (ms), between sending refreshes for each RSVP state. •Refresh misses—Number of successive refresh messages that can be missed before RSVP considers the state expired and tears it down. |
Rate Limiting: enabled or disabled |
The RSVP rate-limiting parameters in effect are as follows: •Burst—Maximum number of RSVP messages allowed to be sent to a neighboring router during an interval. •Limit—Maximum number of RSVP messages to send per queue interval. •Maxsize—Maximum size of the message queue, in bytes. •Period—Length of an interval (time frame), in milliseconds (ms). •Max rate—Maximum number of messages allowed to be sent per second. |
Refresh Reduction: enabled or disabled |
The RSVP refresh-reduction parameters in effect are as follows: •ACK delay (msec)—How long, in milliseconds, before the receiving router sends an acknowledgment (ACK). •Initial retransmit delay (msec)—How long, in milliseconds, before the router retransmits a message. •Local epoch—The RSVP message identifier (ID); randomly generated each time a node reboots or the RSVP process restarts. •Message IDs—The number of message IDs in use, the total number allocated, and the total number available (freed). |
Neighbors |
The total number of neighbors and the types of encapsulation in use including RSVP and User Datagram Protocol (UDP). |
RFC 3175 Aggregation |
The state of aggregation as defined in RFC 3175, Aggregation of RSVP for IPv4 and IPv6 Reservations; values are the following: •Enabled—Active. •Disabled—Inactive. |
Level |
Aggregation level of the reservations; common values are the following: •0 = End-to-end (E2E) reservations. •1 = Aggregated reservations. Level x reservations can be aggregated to form reservations at level x +1. |
Default QoS service |
Type of QoS configured; values are the following: •Controlled-Load—Allows applications to reserve bandwidth to meet their requirements. For example, RSVP with Weighted Random Early Detection (WRED) provides this kind of service. •Guaranteed-Rate—Allows applications to have low delay and high throughput even during times of congestion. For example, weighted fair queueing (WFQ) with RSVP provides this kind of service. |
Number of signaled aggregate reservations |
Cumulative number of signaled aggregate reservations. |
Number of signaled E2E reservations |
Cumulative number of signaled E2E reservations. |
Number of configured map commands |
Cumulative number of configured map commands. |
Number of configured reservation commands |
Cumulative number of configured reservation commands. |
Hello |
Subsequent fields describe the processes for which hello is enabled or disabled. Choices are Fast Reroute, reroute (hello for state timer), bidirectional forwarding detection (BFD), and Graceful Restart for a node with restart capability. |
Statistics |
Status of hello statistics. Valid values are as follows: •Enabled—Statistics are configured. Hello packets are time-stamped when they arrive in the hello input queue for the purpose of recording the time it takes until they are processed. •Disabled—Hello statistics are not configured. •Shutdown—Hello statistics are configured, but not operational. The input queue is too long (that is, more than 10,000 packets are queued). |
Graceful Restart: Enabled or Disabled |
The RSVP Graceful Restart parameters in effect are as follows: •Refresh interval—Frequency, in milliseconds (ms), with which a node sends a hello message to its neighbor. •Refresh misses—Number of missed hello messages that trigger a neighbor-down event upon which stateful switchover (SSO) procedures are started. •DSCP—Differentiated services code point (DSCP) value in the IP header of a hello message. •Advertised restart time—Time, in milliseconds, required for the sender to restart the RSVP-traffic engineering component and exchange hello messages after a failure. •Advertised recovery time—Time, in milliseconds, within which a recovering node wants its neighbor router to resynchronize the RSVP or MPLS forwarding state after SSO. A zero value indicates that the RSVP or MPLS forwarding state is not preserved after SSO. •Maximum wait for recovery—Maximum amount of time, in milliseconds, that a router waits for a neighbor to recover. |
Fast-Reroute |
The Fast Reroute parameters in effect are as follows: •PSBs w/ Local protection desired—Yes means that path state blocks (PSBs) are rerouted when a tunnel goes down and packet flow is not interrupted; No means that PSBs are not rerouted. |
Fast Local Repair: enabled or disabled |
The Fast Local Repair parameters in effect are as follows: •Max repair rate (paths/sec)—Maximum repair rate, in paths per second. •Max processed (paths/run)—Maximum notification elements processed, in paths per run. |
Local policy |
The local policy currently configured. |
COPS |
The Common Open Policy Service (COPS) currently in effect. |
Generic policy settings |
Policy settings that are not specific to COPS or the local policy. •Default policy: `Accept all' means that all RSVP messages are accepted and forwarded. `Reject all' means all RSVP messages are rejected. •Preemption: `Disabled' means that RSVP is not prioritizing reservations and allocating bandwidth accordingly. `Enabled' means that RSVP is prioritizing reservations and allocating more bandwidth to those with the highest priority. |
Related Commands
|
|
debug ip rsvp |
Displays debug messages for RSVP categories. |
show ip rsvp atm-peak-rate-limit |
Displays the current peak rate limit set for an interface or for all interfaces. |
show ip rsvp counters |
Displays the number of RSVP messages sent and received on each interface. |
show ip rsvp host |
Displays specific information for an RSVP host. |
show ip rsvp installed |
Displays RSVP related installed filters and corresponding bandwidth information. |
show ip rsvp interface |
Displays information about interfaces on which RSVP is enabled. |
show ip rsvp listeners |
Displays the RSVP listeners for a specified port or protocol. |
show ip rsvp neighbor |
Displays information about the current RSVP neighbors. |
show ip rsvp policy |
Displays information about the currently configured RSVP policies. |
show ip rsvp precedence |
Displayes IP precedence information about the interfaces on which RSVP is enabled. |
show ip rsvp request |
Displays current RSVP-related request information. |
show ip rsvp reservation |
Displays current RSVP-related receiver information. |
show ip rsvp sbm |
Displays SBM configuration information about RSVP-enabled interfaces. |
show ip rsvp sender |
Displays the RSVP PATH-related sender information |
show ip rsvp signalling |
Displays RSVP signaling information. |
show ip rsvp tos |
Displayes IP ToS information about the interfaces on which RSVP is enabled. |
show ip rsvp aggregation ip
To display Resource Reservation Protocol (RSVP) summary aggregation information, use the show ip rsvp aggregation ip command in user EXEC or privileged EXEC mode.
show ip rsvp aggregation ip [endpoints [detail] [dscp value] [remote ip-address] [role {aggregator | deaggregator}] | interface [if-name] | map [dscp value] | reservation [dscp value [aggregator ip-address]]
Syntax Description
endpoints |
(Optional) Specifies the aggregator and deaggregator nodes for the aggregation region. |
interface if-name |
(Optional) Specifies the interface name. |
map |
(Optional) Displays the map configuration rules. |
dscp value |
(Optional) Specifies the differentiated services code point (DSCP) for the map keyword. Values can be the following: •0 to 63—Numerical DSCP values. The default value is 0. •af11 to af43—Assured forwarding (AF) DSCP values. •cs1 to cs7—Type of service (ToS) precedence values. •default—Default DSCP value. •ef—Expedited forwarding (EF) DSCP values. |
reservation |
(Optional) Displays the reservation configuration. |
dscp value |
(Optional) Specifies the differentiated services code point (DSCP) for the reservation keyword. Values can be the following: •0 to 63—Numerical DSCP values. The default value is 0. •af11 to af43—Assured forwarding (AF) DSCP values. •cs1 to cs7—Type of service (ToS) precedence values. •default—Default DSCP value. •ef—Expedited forwarding (EF) DSCP values. |
aggregator ip-address |
(Optional) Specifies the IP address of the aggregator. |
Command Default
If you enter the show ip rsvp aggregation ip command without an optional keyword, the command displays summary information for all aggregate reservations.
Command Modes
User EXEC (>)
Privileged EXEC (#)
Command History
|
|
12.2(33)SRC |
This command was introduced. |
Cisco IOS XE Release 2.6 |
This command was integrated into Cisco IOS XE Release 2.6. |
Usage Guidelines
Use the show ip rsvp aggregation ip command to display summary information for aggregation, including the number of aggregate, map, and reservation configurations.
Examples
show ip rsvp aggregation ip command Example
The following is sample output from the show ip rsvp aggregation ip command:
Router# show ip rsvp aggregation ip
RFC 3175 Aggregation: Enabled
Default QoS service: Controlled-Load
Number of signaled aggregate reservations: 2
Number of signaled E2E reservations: 8
Number of configured map commands: 4
Number of configured reservation commands: 1
Table 68 describes the significant fields shown in the display.
Table 68 show ip rsvp aggregation ip Field Descriptions
|
|
RFC 3175 Aggregation |
The state of aggregation as defined in RFC 3175, Aggregation of RSVP for IPv4 and IPv6 Reservations; values are the following: •Enabled—Active. •Disabled—Inactive. |
Level |
Aggregation level of the reservations; common values are the following: •0 = End-to-end (E2E) reservations. •1 = Aggregated reservations. Note Level x reservations can be aggregated to form reservations at the next higher level; for example, level x+1. |
Default QoS service |
Type of quality of service (QoS) configured; values are the following: •Controlled-Load—Allows applications to reserve bandwidth to meet their requirements. For example, RSVP with Weighted Random Early Detection (WRED) provides this kind of service. •Guaranteed-Rate—Allows applications to have low delay and high throughput even during times of congestion. For example, Weighted Fair Queueing (WFQ) with RSVP provides this kind of service. |
Number of signaled aggregate reservations |
Cumulative number of signaled aggregate reservations. |
Number of signaled E2E reservations |
Cumulative number of signaled E2E reservations. |
Number of configured map commands |
Cumulative number of configured map commands. |
Number of configured reservation commands |
Cumulative number of configured reservation commands. |
show ip rsvp aggregation ip interface Examples
The following is sample output from the show ip rsvp aggregation ip interface command:
Router# show ip rsvp aggregation ip interface
-------------------- --------
Table 69 describes the significant fields shown in the display.
Table 69 show ip rsvp aggregation ip interface Field Descriptions
|
|
Interface Name |
Name and number of the interface. |
Role |
Configuration of a router's interfaces; values are interior and exterior. |
The following is sample output from the show ip rsvp aggregation ip interface command with a specified interface:
Router# show ip rsvp aggregation ip interface Ethernet0/0
-------------------- --------
Related Commands
|
|
ip rsvp aggregation ip |
Enables RSVP aggregation on a router. |
show ip rsvp aggregation ip endpoints
To display Resource Reservation Protocol (RSVP) information about aggregator and deaggregator routers, use the show ip rsvp aggregation ip endpoints command in user EXEC or privileged EXEC mode.
show ip rsvp aggregation ip endpoints [detail] [dscp value] [remote ip-address] [role {aggregator | deaggregator}]
Syntax Description
detail |
(Optional) Displays additional information about the aggregators and deaggregators. |
dscp value |
(Optional) Specifies the differentiated services code point (DSCP) for the aggregator and deaggregator routers. Values can be the following: •0 to 63—Numerical DSCP values. The default value is 0. •af11 to af43—Assured forwarding (AF) DSCP values. •cs1 to cs7—Type of service (ToS) precedence values. •default—Default DSCP value. •ef—Expedited forwarding (EF) DSCP values. |
remote |
(Optional) Specifies the remote deaggregator. |
ip-address |
IP address of the remote deaggregator. |
role |
(Optional) Specifies a router's position in the aggregation region. |
aggregator |
(Optional) Specifies the router at the beginning of the aggregation region. |
deaggregator |
(Optional) Specifies the router at the end of the aggregation region. |
Command Default
If you enter the show ip rsvp aggregation ip endpoints command without an optional keyword, the command displays information for all aggregate reservations.
Command Modes
User EXEC (>)
Privileged EXEC (#)
Command History
|
|
12.2(33)SRC |
This command was introduced. |
Cisco IOS XE Release 2.6 |
This command was integrated into Cisco IOS XE Release 2.6. |
Usage Guidelines
Use the show ip rsvp aggregation ip endpoints command to display any of the following output at aggregator and deaggregator routers:
•All aggregate reservations.
•All aggregate reservations for which a node is the aggregator.
•All aggregate reservations for which a node is the deaggregator.
•All aggregate reservations for which the remote node is identified with an IP address.
•All aggregate reservations for a given DSCP.
•Any combination of the preceding options; for example, all aggregates with a given DSCP for which a node is an aggregator and the remote node as specified in the IP address.
•Any of the preceding options with detailed information.
Examples
The following is sample output from the show ip rsvp aggregation ip endpoints detail command:
Router# show ip rsvp aggregation ip endpoints detail
Role DSCP Aggregator Deaggregator State Rate Used QBM PoolID
----- ---- --------------- --------------- ------ ------- ------- ----------
Agg 46 10.3.3.3 10.4.4.4 ESTABL 100K 100K 0x00000003
Aggregate Reservation for the following E2E Flows (PSBs):
To From Pro DPort Sport Prev Hop I/F BPS
10.4.4.4 10.1.1.1 UDP 1 1 10.23.20.3 Et1/0 100K
Aggregate Reservation for the following E2E Flows (RSBs):
To From Pro DPort Sport Next Hop I/F Fi Serv BPS
10.4.4.4 10.1.1.1 UDP 1 1 10.4.4.4 Se2/0 FF RATE 100K
Aggregate Reservation for the following E2E Flows (Reqs):
To From Pro DPort Sport Next Hop I/F Fi Serv BPS
10.4.4.4 10.1.1.1 UDP 1 1 10.23.20.3 Et1/0 FF RATE 100K
Table 68 describes the significant fields shown in the display.
Table 70 show ip rsvp aggregation ip endpoints detail Field Descriptions
|
|
Role |
The router's function; values are aggregator or deaggregator. |
DSCP |
DSCP value. |
Aggregator |
IP address of the aggregator. |
Deaggregator |
IP address of the deaggregator. |
State |
Status of the reservation. Each aggregate reservation can be in one of the following states: •PATH_WAIT—Valid at the deaggregator only. The aggregate reservation at the deaggregator enters this state after the deaggregator has sent a PATHERROR message requesting a new aggregate needed. •RESV_WAIT—Valid at the aggregator only. The aggregate reservation at the aggregator enters this state after the aggregator has sent a PATH message for the aggregate reservation. •RESVCONF_WAIT—Valid at the deaggregator only. The aggregate reservation at the deaggregator enters this state after the deaggregator has sent a RESV message for the aggregate reservation. •ESTABLISHED—Valid at both the aggregator and the deaggregator. The aggregator enters this state after a RESVCONF message has been sent. The deaggregator enters this state after it receives a RESVCONF message for the aggregate reservation. •SHUT_DELAY—Valid at both the aggregator and the deaggregator. The aggregator and the deaggregator enter this state after the last end-to-end (E2E) reservation has been removed. |
Rate |
Allocated bandwidth in bits per second (BPS). |
Used |
Amount of bandwidth used in bits per second (BPS). |
QBM Pool ID |
The quality of service (QoS) bandwidth manager (QBM) ID for the reservation. |
Aggregate Reservation for the following E2E Flows |
Information for the reservation: PSB—path state block. Contains data used for forwarding PATH messages downstream; RSB—reservation state block. Contains data for the incoming RESV message. Reqs—requests. Contain data required to forward a RESV message upstream to the node that sent the PATH message. |
To |
IP address of the receiver. |
From |
IP address of the sender. |
Pro |
Protocol code. Code indicates IP protocol such as TCP or User Datagram Protocol (UDP). |
DPort |
Destination port number. |
Sport |
Source port number. |
Prev Hop or Next Hop |
IP address of the previous or next hop. |
I/F |
Interface of the previous or next hop. |
Fi |
Filter (Wildcard Filter, Shared-Explicit, or Fixed-Filter). |
Serv |
Service (RATE or LOAD). |
BPS |
Bandwidth used by the aggregate reservation in bits per second (BPS). |
Related Commands
|
|
ip rsvp aggregation ip |
Enables RSVP aggregation on a router. |
show ip rsvp atm-peak-rate-limit
To display the current peak rate limit set for an interface or for all interfaces, if any, use the show ip rsvp atm-peak-rate-limit command in EXEC mode.
show ip rsvp atm-peak-rate-limit [interface-type interface-number]
Syntax Description
interface-type interface-number |
(Optional) Interface type and interface number. |
Command Modes
EXEC
Command History
|
|
12.0(3)T |
This command was introduced. |
12.2(33)SRA |
This command was integrated into Cisco IOS Release 12.2(33)SRA. |
Usage Guidelines
The show ip rsvp atm-peak-rate-limit command displays the configured peak rate using the following notations for brevity:
•Kilobytes is shown as K bytes; for example, 1200 kilobytes is displayed as 1200K bytes.
•1000 kilobytes is displayed as 1M bytes.
If no interface name is specified, configured peak rates for all Resource Reservation Protocol (RSVP)-enabled interfaces are displayed.
Examples
The following example depicts results of the show ip rsvp atm-peak-rate-limit command, presuming that the ATM subinterface 2/0/0.1 was configured with a reservation peak rate limit of 100 KB using the ip rsvp atm-peak-rate-limit command.
The following is sample output from the show ip rsvp atm-peak-rate-limit command using the interface-type interface-number arguments:
Router# show ip rsvp atm-peak-rate-limit atm2/0/0.1
RSVP: Peak rate limit for ATM2/0/0.1 is 100K bytes
The following samples show output from the show ip rsvp atm-peak-rate-limit command when no interface name is given:
Router# show ip rsvp atm-peak-rate-limit
Interface name Peak rate limit
Router# show ip rsvp atm-peak-rate-limit
Interface name Peak rate limit
Related Commands
|
|
ip rsvp atm-peak-rate-limit |
Sets a limit on the peak cell rate of reservations for all newly created RSVP SVCs established on the current interface or any of its subinterfaces. |
show ip rsvp authentication
To display the security associations that Resource Reservation Protocol (RSVP) has established with other RSVP neighbors, use the show ip rsvp authentication command in user EXEC or privileged EXEC mode.
show ip rsvp authentication [detail] [from {ip-address | hostname}] [to {ip-address | hostname}]
Syntax Description
detail |
(Optional) Displays additional information about RSVP security associations. |
from |
(Optional) Specifies the starting point of the security associations. |
to |
(Optional) Specifies the ending point of the security associations. |
ip-address |
(Optional) Information about a neighbor with a specified IP address. |
hostname |
(Optional) Information about a particular host. |
Command Modes
User EXEC (>)
Privileged EXEC (#)
Command History
|
|
12.2(15)T |
This command was introduced. |
12.0(29)S |
The optional from and to keywords were added. |
12.2(33)SRA |
This command was integrated into Cisco IOS Release 12.2(33)SRA. |
12.2(33)SXH |
This command was integrated into Cisco IOS Release 12.2(33)SXH. |
Usage Guidelines
Use the show ip rsvp authentication command to display the security associations that RSVP has established with other RSVP neighbors. You can display all security associations or specify an IP address or hostname of a particular RSVP neighbor, which restricts the size of the display.
The difference between the ip-address and hostname arguments is whether you specify the neighbor by its IP address or by its name.
Examples
The following is sample output from the show ip rsvp authentication command:
Router# show ip rsvp authentication
Codes: S - static, D - dynamic, N - neighbor, I -interface, C - chain
From To I/F Mode Key-Source Key-ID Code
192.168.102.1 192.168.104.3 Et2/2 Send RSVPKey 1 DNC
192.168.104.1 192.168.104.3 Et2/2 Send RSVPKey 1 DNC
192.168.104.1 192.168.104.3 AT1/0.1 Send RSVPKey 1 DNC
192.168.106.1 192.168.104.3 AT1/0.1 Send RSVPKey 1 DNC
192.168.106.1 192.168.106.2 AT1/0.1 Send RSVPKey 1 DNC
192.168.106.2 192.168.104.1 AT1/0.1 Receive RSVPKey 1 DNC
192.168.106.2 192.168.106.1 AT1/0.1 Receive RSVPKey 1 DNC
Table 71 describes the significant fields shown in the display.
Table 71 show ip rsvp authentication Field Descriptions
|
|
Codes |
Keys can be either static (manually configured) or dynamic (created from a per-ACL key or obtained from a key management server such as Kerberos). Cisco IOS software does not currently support dynamic keys from key management servers. If the field contains the string per-neighbor, it means the security association is using a per-neighbor key; if the field contains the string per-interface, it means the security association is using a per-interface key. If the field contains the string chain, it means the key for the security association comes from the key chain specified in the Key Source. |
From |
Starting point of the security association. |
To |
Ending point of the security association. |
I/F |
Name and number of the interface over which the security association is being maintained. |
Mode |
Separate associations maintained for sending and receiving RSVP messages for a specific RSVP neighbor. Possible values are Send or Receive. |
Key-Source |
Indicates where the key was configured. |
Key-ID |
A string which, along with the IP address, uniquely identifies a security association. The key ID is automatically generated in Cisco IOS software by using the per-interface ip rsvp authentication key command, but it is configured in Cisco IOS software when using key chains for per-neighbor or per-interface RSVP keys. The key ID may be configurable on other RSVP platforms. A key ID is provided in every RSVP authenticated message initiated by a sender and is stored by every RSVP receiver. Note Key Expired in this field means that all possible keys used for this neighbor have expired. |
Code |
Indicates the type of key ID used. |
The following is sample output from the show ip rsvp authentication detail command:
Router# show ip rsvp authentication detail
Key Source: RSVPKey (enabled)
Key Type: Dynamic per-neighbor chain
Last seq # sent: 14167519095569779135
Key Source: RSVPKey (enabled)
Key Type: Dynamic per-neighbor chain
Last seq # sent: 14167520384059965440
Key Source: RSVPKey (enabled)
Key Type: Dynamic per-neighbor chain
Last seq # sent: 14167518979605659648
Key Source: RSVPKey (enabled)
Key Type: Dynamic per-neighbor chain
Last seq # sent: 14167517691115473376
Key Source: RSVPKey (enabled)
Key Type: Dynamic per-neighbor chain
Last seq # sent: 14167808344437293057
Key Source: RSVPKey (enabled)
Key Type: Dynamic per-neighbor chain
Challenge: Not configured
Last seq # rcvd: 14167808280012783626
Key Source: RSVPKey (enabled)
Key Type: Dynamic per-neighbor chain
Challenge: Not configured
Last seq # rcvd: 14167808280012783619
Table 72 describes the significant fields shown in the display.
Table 72 show ip rsvp authentication detail Field Descriptions
|
|
From |
Starting point of the security association. |
To |
Ending point of the security association. |
Neighbor |
IP address of the RSVP neighbor with which the security association is being maintained. |
Interface |
Name and number of the interface over which the security association is being maintained. |
Mode |
Separate associations maintained for sending and receiving RSVP messages for a specific RSVP neighbor. Possible values are Send or Receive. |
Key ID |
A string which, along with the IP address, uniquely identifies a security association. The key ID is automatically generated in Cisco IOS software by using the per-interface ip rsvp authentication key command, but it is configured in Cisco IOS software when using key chains for per-neighbor or per-interface RSVP keys. The key ID may be configurable on other RSVP platforms. A key ID is provided in every RSVP authenticated message initiated by a sender and is stored by every RSVP receiver. Note Key Expired in this field means that all possible keys used for this neighbor have expired. |
Key ACL |
For key types that say dynamic and chain, this field indicates which ACL matched that neighbor, and therefore, which key chain to use. Possible values include: •populated = ACL has entries in it. •removed = ACL has been removed from the configuration. |
Key Source |
Indicates where the key was configured and whether it is enabled or disabled. For key chains, this indicates the name of the key chain; the Key ID field indicates which key in the chain is currently being used. For per-interface keys, this field contains the name of the interface that was configured with the key. |
Key Type |
Static (manually configured) or dynamic (created from a per-ACL key or obtained from a key management server such as Kerberos). Note Cisco IOS software does not currently support dynamic keys from key management servers. |
Handle |
Internal database ID assigned to the security association by RSVP for bookkeeping purposes. |
Hash Type |
Type of secure hash algorithm being used with that neighbor. |
Lifetime |
Maximum amount of time (in hours, minutes, and seconds) that can elapse before a security association is expired. Note This is not how long a key is valid; to obtain duration times for keys, use the show key chain command. |
Expires |
Amount of time remaining (in days, hours, minutes, and seconds) before the security association expires. Note This is not when the current key expires; to obtain expiration times for keys, use the show key chain command. |
Challenge |
For receive-type security associations, possible values are Not Configured, Completed, In Progress, and Failed. For send-type security associations, the value is Supported. Cisco IOS software can always respond to challenges; however, there may be non-Cisco neighbors that do not implement challenges. |
Window size |
Indicates the size of the window for receive-type security associations and the maximum number of authenticated RSVP messages that can be received out-of-order before a replay attack is to be suspected. |
Last seq # sent |
Displayed only for send-type security associations. It indicates the sequence number used to send the last authenticated message to the RSVP neighbor. Use this information to troubleshoot certain types of authentication problems. |
Last valid seq # rcvd |
Displayed only for receive-type security associations. It indicates the authentication sequence number of the last valid RSVP message received from the neighbor. By default, it shows only one sequence number. However, if you use the ip rsvp authentication window-size command to increase the authentication window size to n, then the last n valid received sequence numbers are displayed. Use this information to troubleshoot certain types of authentication problems. |
Related Commands
|
|
clear ip rsvp authentication |
Eliminates RSVP security associations before their lifetimes expire. |
show ip rsvp counters
To display the number of Resource Reservation Protocol (RSVP) messages that were sent and received on each interface, use the show ip rsvp counters command in user EXEC or privileged EXEC mode.
show ip rsvp counters [authentication] [interface type number | neighbor [vrf {* | vrf-name}] | state teardown | summary]
Syntax Description
authentication |
(Optional) Displays a list of RSVP authentication counters. |
interface type number |
(Optional) Displays the number of RSVP messages sent and received for the specified interface name. |
neighbor |
(Optional) Displays the number of RSVP messages sent and received by the specified neighbor. |
vrf * |
(Optional) Displays all the configured virtual routing and forwarding (VRF) instances. |
vrf vrf-name |
(Optional) Displays the name of a specified VRF. |
state teardown |
(Optional) Displays the number of RSVP message states and the reasons for teardown. |
summary |
(Optional) Displays the cumulative number of RSVP messages sent and received by the router over all interfaces. |
Command Default
If you enter the show ip rsvp counters command without an optional keyword, the command displays the number of RSVP messages that were sent and received for each interface on which RSVP is configured.
Command Modes
User EXEC (>)
Privileged EXEC (#)
Command History
|
|
12.0(14)ST |
This command was introduced. |
12.2(13)T |
The neighbor keyword was added, and the command was integrated into Cisco IOS Release 12.2(13)T. |
12.2(15)T |
The command output was modified to show the errors counter incrementing whenever an RSVP message is received on an interface with RSVP authentication enabled, but the authentication checks failed on that message. |
12.2(11)S |
This command was integrated into Cisco IOS Release 12.2(11)S. |
12.0(22)S |
This command was integrated into Cisco IOS Release 12.0(22)S. |
12.0(29)S |
The authentication keyword was added, and the command output was modified to include hello and message queues information. |
12.2(28)SB |
This command was integrated into Cisco IOS Release 12.2(28)SB. |
12.2(33)SRA |
This command was integrated into Cisco IOS Release 12.2(33)SRA. |
12.2(33)SXH |
This command was integrated into Cisco IOS Release 12.2(33)SXH. |
12.4(20)T |
This command was integrated into Cisco IOS Release 12.4(20)T. |
15.0(1)M |
This command was modified. The vrf and * keywords and the vrf-name argument were added. |
Examples
Summary Example
The following example shows the values for the number of RSVP messages of each type that were sent and received by the router over all interfaces, including the hello and message queues information:
Router# show ip rsvp counters summary
All Interfaces Recv Xmit Recv Xmit
PathError 0 0 ResvError 0 0
PathTear 0 0 ResvTear 0 0
ResvConf 0 0 RTearConf 0 0
Hello 5555 5554 IntegrityChalle 0 0
IntegrityRespon 0 0 DSBM_WILLING 0 0
Recv Msg Queues Current Max
Awaiting Authentication 0 0
Table 73 describes the significant fields shown in the display.
Table 73 show ip rsvp counters summary Field Descriptions
|
|
All Interfaces |
Types of messages displayed for all interfaces. Note Hello is a summary of graceful restart, reroute (hello state timer), and Fast Reroute messages. |
Recv |
Number of messages received on the specified interface or on all interfaces. |
Xmit |
Number of messages transmitted from the specified interface or from all interfaces. |
Recv Msg Queues |
Queues for received messages for RSVP, hello per interface, and awaiting authentication. •Current—Number of messages queued. •Max—Maximum number of messages ever queued. |
VRF Example
The following example shows the values for the number of RSVP messages for a specified neighbor with a VRF named myvrf:
Router# show ip rsvp counters neighbor vrf myvrf
Output queue overflow, number of dropped RSVP messages: 0
Number of RSVP messages received out of order: 0
Number of retransmitted RSVP messages: 0
Table 74 describes the significant fields shown in the display.
Table 74 show ip rsvp counters neighbor vrf Field Descriptions
|
|
VRF |
Name of the VRF. |
Neighbor |
IP address of the neighbor. |
Rate-Limiting |
The rate-limiting parameters in effect are as follows: •Output queue overflow, number of dropped RVSP messages—Number of messages dropped by the neighbor when the queue overflowed. |
Refresh-Reduction |
The refresh-reduction parameters in effect are as follows: •Number of RSVP messages received out of order—Messages that were dropped because they were out of sequential order. •Number of retransmitted RSVP messages—Number of messages retransmitted to the neighbor. |
Related Commands
|
|
clear ip rsvp counters |
Clears (sets to zero) all IP RSVP counters that are being maintained. |
show ip rsvp counters state teardown
To display counters for Resource Reservation Protocol (RSVP) events that caused a state to be torn down, use the show ip rsvp counters state teardown command in user EXEC or privileged EXEC mode.
show ip rsvp counters state teardown
Syntax Description
This command has no arguments or keywords.
Command Modes
User EXEC (>)
Privileged EXEC (#)
Command History
|
|
12.0(29)S |
This command was introduced. |
12.2(33)SRA |
This command was integrated into Cisco IOS Release 12.2(33)SRA. |
12.2(33)SXH |
This command was integrated into Cisco IOS Release 12.2(33)SXH. |
12.4(20)T |
This command was integrated into Cisco IOS Release 12.4(20)T. |
Usage Guidelines
Use the show ip rsvp counters state teardown command when a label-switched path (LSP) is down. If graceful restart triggered the state teardown, the numbers in the Path, Resv-In, and Resv-Out columns in the "Examples" section are greater than 0.
Examples
The following is sample output from the show ip rsvp counters state teardown command:
Router# show ip rsvp counters state teardown
Reason for Teardown State torn down
Local application requested tear 0 0 0
Output or Input I/F went down 0 0 0
Backup tunnel failed for FRR Active LSP 0 0 0
Reroutabilty changed for FRR Active LSP 0 0 0
Hello RR Client (HST) requested tear 0 0 0
Graceful Restart (GR) requested tear 0 0 0
Downstream neighbor SSO-restarting 0 0 0
Resource unavailable 0 0 0
Policy server sync failed 0 0 0
Traffic control error 0 0 0
Error in received message 0 0 0
Non RSVP HOP upstream, TE LSP 0 0 0
Table 75 describes the significant fields shown in the display.
Table 75 show ip rsvp counters state teardown Field Descriptions
|
|
States |
RSVP state, including path state block (PSB) and reservation state block (RSB) information. |
Reason for Teardown |
Event triggering the teardown. |
Related Commands
|
|
clear ip rsvp counters |
Clears (sets to zero) the IP RSVP counters that are being maintained. |
show ip rsvp fast bw-protect
To display information about whether backup bandwidth protection is enabled and the status of backup tunnels that may be used to provide that protection, use the show ip rsvp fast bw-protect command in user EXEC or privileged EXEC mode.
show ip rsvp fast bw-protect [detail] [filter [destination ip-address | hostname] [dst-port port-number] [source ip-address | hostname] [src-port port-number]]
Syntax Description
detail |
(Optional) Specifies additional receiver information. |
filter |
(Optional) Specifies a subset of the receivers to display. |
destination ip-address |
(Optional) Specifies the destination IP address of the receiver. |
hostname |
(Optional) Specifies the hostname of the receiver. |
dst-port port-number |
(Optional) Specifies the destination port number. Valid destination port numbers must be in the range from 0 to 65535. |
source ip-address |
(Optional) Specifies the source IP address of the receiver. |
src-port port-number |
(Optional) Specifies the source port number. Valid source port numbers must be in the range from 0 to 65535. |
Command Default
The backup bandwidth protection and backup tunnel status information is not displayed.
Command Modes
User EXEC (>)
Privileged EXEC (#)
Command History
|
|
12.0(29)S |
This command was introduced. |
12.2(33)SRA |
This command was integrated into Cisco IOS Release 12.2(33)SRA. |
12.2SX |
This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware. |
12.4(20)T |
This command was integrated into Cisco IOS Release 12.4(20)T |
Examples
The following is sample output from the show ip rsvp fast bw-protect command:
Router# show ip rsvp fast bw-protect
Primary Protect BW Backup
Tunnel I/F BPS:Type Tunnel:Label State BW-P Type
-------------- ------- -------- ---------- ----- ---- ----
PRAB-72-5_t500 PO2/0 500K:S Tu501:19 Ready ON Nhop
PRAB-72-5_t601 PO2/0 103K:S Tu501:20 Ready OFF Nhop
PRAB-72-5_t602 PO2/0 70K:S Tu501:21 Ready ON Nhop
PRAB-72-5_t603 PO2/0 99K:S Tu501:22 Ready ON Nhop
PRAB-72-5_t604 PO2/0 100K:S Tu501:23 Ready OFF Nhop
PRAB-72-5_t605 PO2/0 101K:S Tu501:24 Ready OFF Nhop
Table 76 describes the significant fields shown in the display.
Table 76 show ip rsvp fast bw-protect Field Descriptions
|
|
Primary Tunnel |
Identification of the tunnel being protected. |
Protect I/F |
Interface name. |
BW BPS:Type |
Bandwidth, in bits per second, and type of bandwidth. Possible values are the following: •S—Subpool •G—Global pool |
Backup Tunnel:Label |
Identification of the backup tunnel. |
State |
Status of backup tunnel. Valid values are the following: •Ready—Data is passing through the primary tunnel, but the backup tunnel is ready to take over if the primary tunnel goes down. •Active—The primary tunnel is down, so the backup tunnel is used for traffic. •None—There is no backup tunnel. |
BW-P |
Status of backup bandwidth protection. Possible values are ON and OFF. |
Type |
Type of backup tunnel. Possible values are the following: •Nhop—Next hop •NNHOP—Next-next hop |
Related Commands
|
|
tunnel mpls traffic-eng fast-reroute bw-protect |
Enables an MPLS TE tunnel to use an established backup tunnel in the event of a link or node failure. |
show ip rsvp fast detail
To display specific information for Resource Reservation Protocol (RSVP) categories, use the show ip rsvp fast detail command in user EXEC or privileged EXEC mode.
show ip rsvp fast detail [filter [destination ip-address | hostname] [dst-port port-number] [source ip-address | hostname] [src-port port-number]]
Syntax Description
filter |
(Optional) Specifies a subset of the receivers to display. |
destination ip-address |
(Optional) Specifies the destination IP address of the receiver. |
hostname |
(Optional) Specifies the hostname of the receiver. |
dst-port port-number |
(Optional) Specifies the destination port number. Valid destination port numbers must be in the range from 0 to 65535. |
source ip-address |
(Optional) Specifies the source IP address of the receiver. |
src-port port-number |
(Optional) Specifies the source port number. Valid source port numbers must be in the range from 0 to 65535. |
Command Default
Specific information for RSVP categories is not displayed.
Command Modes
User EXEC (>)
Privileged EXEC (#)
Command History
|
|
12.0(24)S |
This command was introduced. |
12.0(29)S |
Bandwidth Prot desired was added in the Flag field of the command output. |
12.2(33)SRA |
This command was integrated into Cisco IOS Release 12.2(33)SRA. |
12.4(20)T |
This command was integrated into Cisco IOS Release 12.4(20)T. |
Examples
The following is sample output from the show ip rsvp fast detail command:
Router# show ip rsvp fast detail
Tun Dest: 10.0.0.7 Tun ID: 500 Ext Tun ID: 10.0.0.5
Tun Sender: 10.0.0.5 LSP ID: 8
sent: to NHOP 10.5.6.6 on POS2/0
Setup Prio: 7, Holding Prio: 7
Flags: Local Prot desired, Label Recording, SE Style, Bandwidth Prot desired
Session Name: PRAB-72-5_t500
10.0.0.5 (Strict IPv4 Prefix, 8 bytes, /32)
10.0.5.6 (Strict IPv4 Prefix, 8 bytes, /32)
10.6.7.7 (Strict IPv4 Prefix, 8 bytes, /32)
10.0.0.7 (Strict IPv4 Prefix, 8 bytes, /32)
10.5.6.6 (Strict IPv4 Prefix, 8 bytes, /32)
10.6.7.7 (Strict IPv4 Prefix, 8 bytes, /32)
10.0.0.7 (Strict IPv4 Prefix, 8 bytes, /32)
Traffic params - Rate: 500K bits/sec, Max. burst: 1K bytes
Min Policed Unit: 0 bytes, Max Pkt Size 4294967295 bytes
Fast-Reroute Backup info:
Outbound FRR: Ready -- backup tunnel selected
Backup Tunnel: Tu501 (label 19)
Tun Sender: 10.5.6.5 LSP ID: 8
Tun Sender: 10.5.6.5, LSP ID: 8
Path ID handle: 04000405.
Incoming policy: Accepted. Policy source(s): MPLS/TE
Output on POS2/0. Policy status: Forwarding. Handle: 02000406
Table 77 describes the significant fields shown in the display.
Table 77 show ip rsvp fast detail Field Descriptions
|
|
Tun Dest |
IP address of the receiver. |
Tun ID |
Tunnel identification number. |
Ext Tun ID |
Extended tunnel identification number. |
Tun Sender |
IP address of the sender. |
LSP ID |
Label-switched path identification number. |
Setup Prio |
Setup priority. |
Holding Prio |
Holding priority. |
Flags |
Backup bandwidth protection has been configured for the label-switched path (LSP). |
Session Name |
Name of the session. |
ERO (incoming) |
EXPLICIT_ROUTE object of incoming path messages. |
ERO (outgoing) |
EXPLICIT_ROUTE object of outgoing path messages. |
Traffic params Rate |
Average rate, in bits per second. |
Max. burst |
Maximum burst size, in bytes. |
Min Policed Unit |
Minimum policed units, in bytes. |
Max Pkt Size |
Maximum packet size, in bytes. |
Inbound FRR |
Status of inbound Fast Reroute (FRR) backup tunnel. If this node is downstream from a rerouted LSP (for example, at a merge point for this LSP), the state is Active. |
Outbound FRR |
Status of outbound FRR backup tunnel. If this node is a point of local repair (PLR) for an LSP, there are three possible states: •Active—This LSP is actively using its backup tunnel, presumably because there has been a downstream failure. •No Backup—This LSP does not have local (Fast Reroute) protection. No backup tunnel has been selected for it to use in case of a failure. •Ready—This LSP is ready to use a backup tunnel in case of a downstream link or node failure. A backup tunnel has been selected for it to use. |
Backup Tunnel |
If the Outbound FRR state is Ready or Active, this field indicates the following: •Which backup tunnel has been selected for this LSP to use in case of a failure. •The inbound label that will be prepended to the LSP's data packets for acceptance at the backup tunnel tail (the merge point). |
Bkup Sender Template |
If the Outbound FRR state is Ready or Active, SENDER_TEMPLATE and FILTERSPEC objects are shown. These objects will be used in RSVP messages sent by the backup tunnel if or when the LSP starts actively using the backup tunnel. They differ from the original (prefailure) objects only in that the node (the PLR) substitutes its own IP address for that of the original sender. For example, path and pathTear messages will contain the new SENDER_TEMPLATE. Resv and resvTear messages will contain the new FILTERSPEC object. If this LSP begins actively using the backup tunnel, the display changes. |
Bkup FilerSpec |
If the Outbound FRR state is Ready or Active, SENDER_TEMPLATE and FILTERSPEC objects are shown. These objects will be used in RSVP messages sent by the backup tunnel if or when the LSP starts actively using the backup tunnel. They differ from the original (prefailure) objects only in that the node (the PLR) substitutes its own IP address for that of the original sender. For example, path and pathTear messages will contain the new SENDER_TEMPLATE. Resv and resvTear messages will contain the new FILTERSPEC object. If this LSP begins actively using the backup tunnel, the display changes. |
Path ID handle |
Protection Switch Byte (PSB) identifier. |
Incoming policy |
Policy decision of the LSP. If RSVP policy was not granted for the incoming path message for the tunnel, the LSP does not come up. Accepted is displayed. |
Policy source(s) |
For FRR LSPs, this value always is MPLS/TE for the policy source. |
Status |
For FRR LSPs, valid values are as follows: •Proxied—Headend routers. •Proxied Terminated—Tailend routers. For midpoint routers, the field always is blank. |
Related Commands
|
|
mpls traffic-eng fast-reroute backup-prot-preemption |
Changes the backup protection preemption algorithm to minimize the amount of bandwidth that is wasted. |
show ip rsvp fast-reroute
To display information about fast reroutable primary tunnels and their corresponding backup tunnels that provide protection, use the show ip rsvp fast-reroute command in user EXEC or privileged EXEC mode.
show ip rsvp fast-reroute [filter [session-type {session-type-number | all}]]
Syntax Description
filter |
(Optional) Specifies a subset of the tunnel to display. |
session-type session-type-number |
(Optional) Specifies the type of tunnels to display. Valid values are: •7 for IPv4 point-to-point (P2P) traffic engineering (TE) label switched path (LSP) tunnel sessions. •13 for IPv4 point-to-multipoint (P2MP) TE LSP tunnel sessions. |
session-type all |
(Optional) Specifies all types of tunnel sessions. |
Command Default
If no arguments are specified, the display information about all fast reroutable primary tunnels is displayed.
Command Modes
User EXEC (>)
Privileged EXEC (#)
Command History
|
|
12.0(27)S |
This command was introduced. |
12.2(33)SRA |
This command was integrated into Cisco IOS Release 12.2(33)SRA. |
12.2(33)SXH |
This command was integrated into Cisco IOS Release 12.2(33)SXH. |
12.4(20)T |
This command was integrated into Cisco IOS Release 12.4(20)T. |
12.2(33)SRE |
This command was modified. The filter keyword was added to display tunnel information categorized by point-to-point and point-to-multipoint. The output was updated to display Multiprotocol Label Switching (MPLS) TE P2MP information. |
15.0(1)M |
This command was modified. Support for classic IP RSVP (session type 1) was removed. |
Examples
The following is sample output of fast reroutable primary tunnels and their corresponding backup tunnels that provide protection:
Router# show ip rsvp fast-reroute
Primary Protect BW Backup
Tunnel I/F BPS:Type Tunnel:Label State Level Type
------ ------- -------- ------------- ------ ----- ---
GSR1---R2---_t65336 PO1/0 0:G Tu1002:0 Ready any-unl Nhop
GSR1---R2---_t65338 PO4/0 0:G Tu1004:0 Ready any-unl Nhop
Table 78 describes the significant fields shown in the display.
Table 78 show ip rsvp fast-reroute Field Descriptions
|
|
Primary Tunnel |
Hostname and tunnel ID. |
Protect I/F |
Interface that is being protected. |
BW BPS:Type |
Bandwidth, in bits per second, and the pool from which the bandwidth comes. Valid values are G, global pool, S, and subpool. |
Backup Tunnel:Label |
Backup tunnel ID and label. |
State |
Status of protection. Valid values are Ready, Active, and None. |
Level |
Level of bandwidth. Valid values are any and unl (unlimited). |
Type |
Type of backup tunnel: Nhop (next hop) or NNhop (next-next hop). |
The following example shows fast reroutable primary tunnels and their corresponding backup tunnels. The information is organized by P2P LSPs and P2MP sub-LSPs. The following example shows that Tunnel 22 has six sub-LSPs, three that are protected on Ethernet interface 0/0, and three that are not protected on Ethernet interface 0/1:
Router# show ip rsvp fast-reroute
Protected LSP I/F BPS:Type Tunnel:Label State Level Type
------------- ------- -------- ------------- ------ ----- ------
R201_t1 Et0/1 500K:G Tu777:16 Ready any-lim Nhop
Protected Sub-LSP Protect BW Backup
src_lspid[subid]->dst_tunid I/F BPS:Type Tunnel:Label State
--------------------------- ------- -------- ------------- ------
10.1.1.201_1[1]->10.1.1.203_22 Et0/0 500K:G Tu666:20 Ready
10.1.1.201_1[2]->10.1.1.206_22 Et0/0 500K:G Tu666:20 Ready
10.1.1.201_1[3]->10.1.1.213_22 Et0/0 500K:G Tu666:20 Ready
10.1.1.201_1[4]->10.1.1.214_22 Et0/1 500K:G None None
10.1.1.201_1[5]->10.1.1.216_22 Et0/1 500K:G None None
10.1.1.201_1[6]->10.1.1.217_22 Et0/1 500K:G None None
The following example displays information about fast reroutable primary tunnels and their corresponding backup tunnels for Cisco IOS Release 12.4(24)T and earlier releases. The output is organized by session type.
Rrouter# show ip rsvp fast-reroute filter session-type all
Protected LSP I/F BPS:Type Tunnel:Label State Level Type
------------- ------- -------- ------------- ------ ----- ------
Session Type 7 (te-p2p-lsp)
Protected LSP I/F BPS:Type Tunnel:Label State Level Type
------------- ------- -------- ------------- ------ ----- ------
R201_t1 Et0/1 500K:G Tu777:16 Ready any-lim Nhop
Session Type 13 (te-p2mp-lsp)
Protected Sub-LSP Protect BW Backup
src_lspid[subid]->dst_tunid I/F BPS:Type Tunnel:Label State
--------------------------- ------- -------- ------------- ------
10.1.1.201_1[1]->10.1.1.203_22 Et0/0 500K:G Tu666:20 Ready
10.1.1.201_1[2]->10.1.1.206_22 Et0/0 500K:G Tu666:20 Ready
10.1.1.201_1[3]->10.1.1.213_22 Et0/0 500K:G Tu666:20 Ready
10.1.1.201_1[4]->10.1.1.214_22 Et0/1 500K:G None None
10.1.1.201_1[5]->10.1.1.216_22 Et0/1 500K:G None None
10.1.1.201_1[6]->10.1.1.217_22 Et0/1 500K:G None None
Table 79 describes the significant fields shown in the display.
Table 79 show ip rsvp fast-reroute Point-to-Multipoint Field Descriptions
|
|
Protected LSP |
LSP being protected and the tunnel ID. |
Protected Sub-LSP src_lspid[subid]->dst_tunid |
The source and destination address of the sub-LSP being protected. The P2MP ID is appended to the source address. The tunnel ID is appended to the destination address. |
The following example displays information about fast reroutable primary tunnels and their corresponding backup tunnels that provide protection for Cisco IOS Release 15.0(1)M and later releases.
Rrouter# show ip rsvp fast-reroute filter session-type all
Session Type 7 (te-p2p-lsp)
Protected LSP I/F BPS:Type Tunnel:Label State Level Type
------------- ------- -------- ------------- ------ ----- ------
p2mp-2_t12 Se3/0 500K:G Tu700:0 Ready any-unl Nhop
p2mp-2_t13 Se3/0 500K:G Tu700:0 Ready any-unl Nhop
Session Type 13 (te-p2mp-lsp)
*Protected Sub-LSP Protect BW Backup
src_lspid[subid]->dst_tunid I/F BPS:Type Tunnel:Label State
--------------------------- ------- -------- ------------- ------
10.2.0.1_12[1]->10.1.0.1_1 Se5/0 1M:G None None
10.2.0.1_12[3]->10.2.3.3_1 Se3/0 1M:G Tu700:16 Ready
10.2.0.1_12[5]->10.3.0.1_1 Se3/0 1M:G Tu700:16 Ready
10.2.0.1_12[6]->10.3.4.3_1 Se3/0 1M:G Tu700:16 Ready
10.2.0.1_12[8]->10.2.5.3_1 Se6/0 1M:G Tu100:17 Ready
Related Commands
|
|
mpls traffic-eng auto-tunnel primary config |
Enables IP processing without an explicit address. |
mpls traffic-eng auto-tunnel primary config mpls ip |
Enables LDP on primary autotunnels. |
mpls traffic-eng auto-tunnel primary onehop |
Automatically creates primary tunnels to all next hops. |
mpls traffic-eng auto-tunnel primary timers |
Configures how many seconds after a failure primary autotunnels are removed. |
mpls traffic-eng auto-tunnel primary tunnel-num |
Configures the range of tunnel interface numbers for primary autotunnels. |
show ip rsvp fast-reroute bw-protect
To display information about whether backup bandwidth protection is enabled and the status of backup tunnels that may be used to provide that protection, use the show ip rsvp fast-reroute bw-protect command in user EXEC or privileged EXEC mode.
show ip rsvp fast-reroute bw-protect [detail] [filter [session-type {session-type-number | all}] [destination ip-address | hostname] [dst-port port-number] [source ip-address | hostname] [src-port port-number]]
Syntax Description
detail |
(Optional) Specifies additional receiver information. |
filter |
(Optional) Specifies a subset of the receivers to display. |
session-type session-type-number |
(Optional) Specifies the type of Resource Reservation Protocol (RSVP) sessions to display. Valid values are: •1 for IPv4 sessions •7 for IPv4 point-to-point traffic engineering (TE) label switched path (LSP) tunnel sessions •13 for IPv4 point-to-multipoint TE LSP tunnel sessions |
all |
(Optional) Specifies all types of RSVP sessions. |
destination ip-address |
(Optional) Specifies the destination IP address of the receiver. |
hostname |
(Optional) Specifies the hostname of the receiver. |
dst-port port-number |
(Optional) Specifies the destination port number. Valid destination port numbers must be in the range from 0 to 65535. |
source ip-address |
(Optional) Specifies the source IP address of the receiver. |
src-port port-number |
(Optional) Specifies the source port number. Valid source port numbers must be in the range from 0 to 65535. |
Command Default
The backup bandwidth protection and backup tunnel status information is not displayed.
Command Modes
User EXEC (>)
Privileged EXEC (#)
Command History
|
|
12.0(29)S |
This command was introduced. |
12.2(33)SRA |
This command was integrated into Cisco IOS Release 12.2(33)SRA. |
12.2SX |
This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware. |
12.4(20)T |
This command was integrated into Cisco IOS Release 12.4(20)T. |
12.2(33)SRE |
This command was modified. The session-type keyword was added to display specific types of tunnels. The output was modified to display Multiprotocol Label Switching (MPLS) traffic engineering (TE) point-to-multipoint (P2MP) information. |
Examples
The following is sample output from the show ip rsvp fast-reroute bw-protect command:
Router# show ip rsvp fast-reroute bw-protect
Primary Protect BW Backup
Tunnel I/F BPS:Type Tunnel:Label State BW-P Type
-------------- ------- -------- ---------- ----- ---- ----
PRAB-72-5_t500 PO2/0 500K:S Tu501:19 Ready ON Nhop
PRAB-72-5_t601 PO2/0 103K:S Tu501:20 Ready OFF Nhop
PRAB-72-5_t602 PO2/0 70K:S Tu501:21 Ready ON Nhop
PRAB-72-5_t603 PO2/0 99K:S Tu501:22 Ready ON Nhop
PRAB-72-5_t604 PO2/0 100K:S Tu501:23 Ready OFF Nhop
PRAB-72-5_t605 PO2/0 101K:S Tu501:24 Ready OFF Nhop
Table 80 describes the significant fields shown in the display.
Table 80 show ip rsvp fast-reroute bw-protect Field Descriptions
|
|
Primary Tunnel |
Identification of the tunnel being protected. |
Protect I/F |
Interface name. |
BW BPS:Type |
Bandwidth, in bits per second, and type of bandwidth. Possible values are the following: •S—Subpool •G—Global pool |
Backup Tunnel:Label |
Identification of the backup tunnel. |
State |
Status of backup tunnel. Valid values are the following: •Ready—Data is passing through the primary tunnel, but the backup tunnel is ready to take over if the primary tunnel goes down. •Active—The primary tunnel is down, so the backup tunnel is used for traffic. •None—There is no backup tunnel. |
BW-P |
Status of backup bandwidth protection. Possible values are ON and OFF. |
Type |
Type of backup tunnel. Possible values arethe following: •Nhop—Next hop •NNHOP—Next-next hop |
The following example shows fast reroutable primary tunnels and their corresponding backup tunnels that provide protection. The information is organized by point-to-point (P2P) labe switched paths (LSPs) and P2MP sub-LSPs. The following example shows that Tunnel 22 has six sub-LSPs, three that are protected on Ethernet interface 0/0, and three that are not protected on Ethernet interface 0/1:
Router# show ip rsvp fast-reroute bw-protect
Protected LSP I/F BPS:Type Tunnel:Label State BW-P Type
------------- ------- -------- ------------- ------ ----- ------
R201_t1 Et0/1 500K:G Tu777:16 Ready ON Nhop
Protected Sub-LSP Protect BW Backup
src_lspid[subid]->dst_tunid I/F BPS:Type Tunnel:Label BW-P
--------------------------- ------- -------- ------------- ------
10.1.1.201_1[1]->10.1.1.203_22 Et0/0 500K:G Tu666:20 ON
10.1.1.201_1[2]->10.1.1.206_22 Et0/0 500K:G Tu666:20 ON
10.1.1.201_1[3]->10.1.1.213_22 Et0/0 500K:G Tu666:20 ON
10.1.1.201_1[4]->10.1.1.214_22 Et0/1 500K:G None None
10.1.1.201_1[5]->10.1.1.216_22 Et0/1 500K:G None None
10.1.1.201_1[6]->10.1.1.217_22 Et0/1 500K:G None None
Table 79 describes the significant fields shown in the display.
Table 81 show ip rsvp fast-reroute bw-protect Point-to-Multipoint Field Descriptions
|
|
Protected LSP |
LSP being protected and the tunnel ID. |
Protected Sub-LSP src_lspid[subid]->dst_tunid |
The source and destination address of the sub-LSP being protected. The P2MP ID is appended to the source address. The tunnel ID is appended to the destination address. |
Related Commands
|
|
tunnel mpls traffic-eng fast-reroute bw-protect |
Enables an MPLS TE tunnel to use an established backup tunnel in the event of a link or node failure. |
show ip rsvp fast-reroute detail
To display specific information for Resource Reservation Protocol (RSVP) categories, use the show ip rsvp fast-reroute detail command in user EXEC or privileged EXEC mode.
show ip rsvp fast-reroute detail [filter [session-type {session-type-number | all}] [destination ip-address | hostname] [dst-port port-number] [source ip-address | hostname] [src-port port-number]]
Syntax Description
filter |
(Optional) Specifies a subset of the receivers to display. |
session-type session-type-number |
(Optional) Specifies the type of RSVP sessions to display. Valid values are: •1 for IPv4 sessions •7 for IPv4 point-to-point (P2P) traffic engineering (TE) label switched path (LSP) tunnel sessions •13 for IPv4 point-to-multipoint (P2MP) TE LSP tunnel sessions. |
all |
(Optional) Specifies all types of RSVP sessions. |
destination ip-address |
(Optional) Specifies the destination IP address of the receiver. |
hostname |
(Optional) Specifies the hostname of the receiver. |
dst-port port-number |
(Optional) Specifies the destination port number. Valid destination port numbers must be in the range from 0 to 65535. |
source ip-address |
(Optional) Specifies the source IP address of the receiver. |
src-port port-number |
(Optional) Specifies the source port number. Valid source port numbers must be in the range from 0 to 65535. |
Command Modes
User EXEC (>)
Privileged EXEC (#)
Command History
|
|
12.0(24)S |
This command was introduced. |
12.0(29)S |
Bandwidth Prot desired was added in the Flag field of the command output. |
12.2(33)SRA |
This command was integrated into Cisco IOS Release 12.2(33)SRA. |
12.4(20)T |
This command was integrated into Cisco IOS Release 12.4(20)T. |
12.2(33)SRE |
This command was modified. The session-type keyword was added to display specific types of tunnels. The output was modified to display MPLS TE P2MP information. |
Examples
The following is sample output from the show ip rsvp fast-reroute detail command:
Router# show ip rsvp fast-reroute detail
Tun Dest: 10.0.0.7 Tun ID: 500 Ext Tun ID: 10.0.0.5
Tun Sender: 10.0.0.5 LSP ID: 8
sent: to NHOP 10.5.6.6 on POS2/0
Setup Prio: 7, Holding Prio: 7
Flags: Local Prot desired, Label Recording, SE Style, Bandwidth Prot desired
Session Name: PRAB-72-5_t500
10.0.0.5 (Strict IPv4 Prefix, 8 bytes, /32)
10.0.5.6 (Strict IPv4 Prefix, 8 bytes, /32)
10.6.7.7 (Strict IPv4 Prefix, 8 bytes, /32)
10.0.0.7 (Strict IPv4 Prefix, 8 bytes, /32)
10.5.6.6 (Strict IPv4 Prefix, 8 bytes, /32)
10.6.7.7 (Strict IPv4 Prefix, 8 bytes, /32)
10.0.0.7 (Strict IPv4 Prefix, 8 bytes, /32)
Traffic params - Rate: 500K bits/sec, Max. burst: 1K bytes
Min Policed Unit: 0 bytes, Max Pkt Size 4294967295 bytes
Fast-Reroute Backup info:
Outbound FRR: Ready -- backup tunnel selected
Backup Tunnel: Tu501 (label 19)
Tun Sender: 10.5.6.5 LSP ID: 8
Tun Sender: 10.5.6.5, LSP ID: 8
Path ID handle: 04000405.
Incoming policy: Accepted. Policy source(s): MPLS/TE
Output on POS2/0. Policy status: Forwarding. Handle: 02000406
Table 82 describes the significant fields shown in the display.
Table 82 show ip rsvp fast-reroute detail Field Descriptions
|
|
Tun Dest |
IP address of the receiver. |
Tun ID |
Tunnel identification number. |
Ext Tun ID |
Extended tunnel identification number. |
Tun Sender |
IP address of the sender. |
LSP ID |
Label switched path identification number. |
Setup Prio |
Setup priority. |
Holding Prio |
Holding priority. |
Flags |
Backup bandwidth protection has been configured for the label switched path. |
Session Name |
Name of the session. |
ERO (incoming) |
EXPLICIT_ROUTE object of incoming path messages. |
ERO (outgoing) |
EXPLICIT_ROUTE object of outgoing path messages. |
Traffic params Rate |
Average rate, in bits per second. |
Max. burst |
Maximum burst size, in bytes. |
Min Policed Unit |
Minimum policed units, in bytes. |
Max Pkt Size |
Maximum packet size, in bytes. |
Inbound FRR |
Status of inbound Fast Reroute (FRR) backup tunnel. If this node is downstream from a rerouted LSP (for example, at a merge point for this LSP), the state is Active. |
Outbound FRR |
Status of outbound FRR backup tunnel. If this node is a point of local repair (PLR) for an LSP, there are three possible states: •Active—This LSP is actively using its backup tunnel, presumably because there has been a downstream failure. •No Backup—This LSP does not have local (Fast Reroute) protection. No backup tunnel has been selected for it to use in case of a failure. •Ready—This LSP is ready to use a backup tunnel in case of a downstream link or node failure. A backup tunnel has been selected for it to use. |
Backup Tunnel |
If the Outbound FRR state is Ready or Active, this field indicates the following: •Which backup tunnel has been selected for this LSP to use in case of a failure. •The inbound label that will be prepended to the LSP's data packets for acceptance at the backup tunnel tail (the merge point). |
Bkup Sender Template |
If the Outbound FRR state is Ready or Active, SENDER_TEMPLATE and FILTERSPEC objects are shown. These objects will be used in RSVP messages sent by the backup tunnel if or when the LSP starts actively using the backup tunnel. They differ from the original (prefailure) objects only in that the node (the PLR) substitutes its own IP address for that of the original sender. For example, path and pathTear messages will contain the new SENDER_TEMPLATE. Resv and resvTear messages will contain the new FILTERSPEC object. If this LSP begins actively using the backup tunnel, the display changes. |
Bkup FilerSpec |
If the Outbound FRR state is Ready or Active, SENDER_TEMPLATE and FILTERSPEC objects are shown. These objects will be used in RSVP messages sent by the backup tunnel if or when the LSP starts actively using the backup tunnel. They differ from the original (prefailure) objects only in that the node (the PLR) substitutes its own IP address for that of the original sender. For example, path and pathTear messages will contain the new SENDER_TEMPLATE. Resv and resvTear messages will contain the new FILTERSPEC object. If this LSP begins actively using the backup tunnel, the display changes. |
Path ID handle |
Protection Switch Byte (PSB) identifier. |
Incoming policy |
Policy decision of the LSP. If RSVP policy was not granted for the incoming path message for the tunnel, the LSP does not come up. Accepted is displayed. |
Policy source(s) |
For FRR LSPs, this value always is MPLS/TE for the policy source. |
Status |
For FRR LSPs, valid values are as follows: •Proxied—Headend routers. •Proxied Terminated—Tailend routers. For midpoint routers, the field always is blank. |
The following example shows P2MP data:
Router# show ip rsvp fast-reroute detail
P2MP ID: 22 Tun ID: 22 Ext Tun ID: 10.1.1.201
Tun Sender: 10.1.1.201 LSP ID: 1 SubGroup Orig: 10.1.1.201
S2L Destination : 10.1.1.206
sent: to NHOP 10.0.0.205 on Ethernet0/0
Setup Prio: 7, Holding Prio: 7
Flags: (0xF) Local Prot desired, Label Recording, SE Style, Bandwidth Prot desired
10.1.1.201 (Strict IPv4 Prefix, 8 bytes, /32)
10.0.0.201 (Strict IPv4 Prefix, 8 bytes, /32)
10.0.0.205 (Strict IPv4 Prefix, 8 bytes, /32)
10.1.0.205 (Strict IPv4 Prefix, 8 bytes, /32)
10.1.0.206 (Strict IPv4 Prefix, 8 bytes, /32)
10.1.1.206 (Strict IPv4 Prefix, 8 bytes, /32)
10.0.0.205 (Strict IPv4 Prefix, 8 bytes, /32)
10.1.0.205 (Strict IPv4 Prefix, 8 bytes, /32)
10.1.0.206 (Strict IPv4 Prefix, 8 bytes, /32)
1o.1.1.206 (Strict IPv4 Prefix, 8 bytes, /32)
Traffic params - Rate: 500K bits/sec, Max. burst: 1K bytes
Min Policed Unit: 1 bytes, Max Pkt Size 2147483647 bytes
Fast-Reroute Backup info:
Outbound FRR: Ready -- backup tunnel selected
Backup Tunnel: Tu666 (label 20)
Tun Sender: 10.0.2.201 LSP ID: 1 SubGroup Orig: 10.1.1.201
Tun Sender: 10.0.2.201, LSP ID: 1, SubGroup Orig: 10.1.1.201
Path ID handle: 01000417.
Incoming policy: Accepted. Policy source(s): MPLS/TE
Table 83 describes the significant fields shown in the display.
Table 83 show ip rsvp fast-reroute detail P2MP Field Descriptions
|
|
P2MP ID |
A 32-bit number that identifies the set of destinations of the P2MP tunnel. |
Tun ID |
Tunnel identification number. |
Ext Tun ID |
Extended tunnel identification number. |
Tun Sender |
IP address of the sender. |
LSP ID |
Label switched path identification number. |
SubGroup Orig |
LSP headend router ID address. |
SubGroup ID |
An incremental number assigned to each sub-LSP signaled from the headend router. |
S2L Destination |
LSP tailend router ID address. |
Related Commands
|
|
mpls traffic-eng fast-reroute backup-prot-preemption |
Changes the backup protection preemption algorithm to minimize the amount of bandwidth that is wasted. |
show ip rsvp hello
To display hello status and statistics for Fast Reroute, reroute (hello state timer), and graceful restart, use the show ip rsvp hello command in user EXEC or privileged EXEC mode.
show ip rsvp hello
Syntax Description
This command has no arguments or keywords.
Command Modes
User EXEC (>)
Privileged EXEC (#)
Command History
|
|
12.0(22)S |
This command was introduced. |
12.0(29)S |
The command output was modified to include graceful restart, reroute (hello state timer), and Fast Reroute information. |
12.2(18)SXD1 |
This command was integrated into Cisco IOS Release 12.2(18)SXD1. |
12.2(33)SRA |
The command output was modified to show whether graceful restart is configured and full mode was added. |
12.2(31)SB2 |
This command was integrated into Cisco IOS Release 12.2(31)SB2. |
12.2(33)SRC |
The command output was modified to include Bidirectional Forwarding Detection (BFD) protocol information. |
12.4(20)T |
This command was integrated into Cisco IOS Release 12.4(20)T. |
Examples
The following is sample output from the show ip rsvp hello command:
Router# show ip rsvp hello
RSVP Hello for Fast-Reroute/Reroute: Enabled
BFD for Fast-Reroute/Reroute: Enabled
RSVP Hello for Graceful Restart: Disabled
Table 84 describes the significant fields shown in the display. The fields describe the processes for which hello is enabled or disabled.
Table 84 show ip rsvp hello Field Descriptions
|
|
RSVP Hello for Fast-Reroute/Reroute |
Status of Fast-Reroute/Reroute: •Enabled—Fast reroute and reroute (hello for state timer) are activated (enabled). •Disabled—Fast reroute and reroute (hello for state timer) are not activated (disabled). |
Statistics |
Status of hello statistics: •Enabled—Statistics are configured. Hello packets are time-stamped when they arrive in the hello input queue for the purpose of recording the time required until they are processed. •Disabled—Hello statistics are not configured. •Shutdown—Hello statistics are configured but not operational. The input queue is too long (that is, more than 10,000 packets are queued). |
BFD for Fast-Reroute/Reroute |
Status of BFD for Fast-Reroute/Reroute: •Enabled—BFD is configured. •Disabled—BFD is not configured. |
Graceful Restart |
Restart capability: •Enabled—Restart capability is activated for a router (full mode) or its neighbor (help-neighbor). •Disabled—Restart capability is not activated. |
Related Commands
|
|
ip rsvp signalling hello (configuration) |
Enables hello globally on the router. |
ip rsvp signalling hello statistics |
Enables hello statistics on the router. |
show ip rsvp hello statistics |
Displays how long hello packets have been in the hello input queue. |
show ip rsvp hello client lsp detail
To display detailed information about Resource Reservation Protocol (RSVP) traffic engineering (TE) client hellos for label-switched paths (LSPs), use the show ip rsvp hello client lsp detail command in user EXEC or privileged EXEC mode.
show ip rsvp hello client lsp detail [filter [destination hostname]]
Syntax Description
filter |
(Optional) Specifies filters to limit the display of output. |
destination |
(Optional) Displays the filters configured on the destination (tunnel tail). |
hostname |
(Optional) IP address or name of destination (tunnel tail). |
Command Modes
User EXEC (>)
Privileged EXEC (#)
Command History
|
|
12.0(33)S |
This command was introduced. |
12.2(33)SRC |
This command was integrated into Cisco IOS Release 12.2(33)SRC. |
Usage Guidelines
Use the show ip rsvp hello client lsp detail command to display information about the LSPs, including IP addresses and their types.
Examples
The following is sample output from the show ip rsvp hello client lsp detail command:
Router# show ip rsvp hello client lsp detail
Hello Client LSPs (all lsp tree)
Tun Dest: 10.0.1.1 Tun ID: 14 Ext Tun ID: 172.16.1.1
Tun Sender: 172.16.1.1 LSP ID: 31
Lsp GR DN nbr: 192.168.1.1
Lsp RR DN nbr: 10.0.0.3 HST
Table 85 describes the significant fields shown in the display.
Table 85 show ip rsvp hello client lsp detail Field Descriptions
|
|
Hello Client LSPs |
Current clients include graceful restart (GR), reroute (RR) (hello state timer), and fast reroute (FRR). |
Tun Dest |
IP address of the destination tunnel. |
Tun ID |
Identification number of the tunnel. |
Ext Tun ID |
Extended identification number of the tunnel. Usually, this is the same as the source address. |
Tun Sender |
IP address of the tunnel sender. |
LSP ID |
Identification number of the LSP. |
Lsp flags |
LSP database information. |
Lsp GR DN nbr |
IP address of the LSP graceful restart downstream neighbor. |
Lsp RR DN nbr |
IP address of the LSP reroute downstream neighbor; HST—hello state timer. |
Related Commands
|
|
show ip rsvp hello |
Displays hello status and statistics for fast reroute, reroute (hello state timer), and graceful restart. |