Table Of Contents
Frame Relay PVC Bundles with QoS Support for IP and MPLS
Prerequisites for Frame Relay PVC Bundles with QoS Support for IP and MPLS
Restrictions for Frame Relay PVC Bundles with QoS Support for IP and MPLS
Information About Frame Relay PVC Bundles with QoS Support for IP and MPLS
Benefits of Frame Relay PVC Bundles with QoS Support for IP and MPLS
Frame Relay PVC Bundle Support
Service Levels and PVC Selection Criteria
Frame Relay PVC Bundle Management
How to Configure Frame Relay PVC Bundles with QoS Support for IP and MPLS
Configuring Frame Relay PVC Bundles with IP QoS Support
Configuring Frame Relay PVC Bundles with MPLS QoS Support
Verifying Frame Relay PVC Bundles Configuration
Monitoring and Maintaining Frame Relay PVC Bundles
Configuration Examples for Frame Relay PVC Bundles with QoS Support for IP and MPLS
PVC Bundles with IP QoS Support on Main, Multipoint, and Point-to-Point Interfaces Example
PVC Bundle with IP QoS Support with Multiple QoS Parameters Example
PVC Bundle with MPLS QoS Support Example
Verifying Frame Relay PVC Bundle Configuration Examples
Monitoring and Maintaining Frame Relay PVC Bundles Examples
bump (Frame Relay VC-bundle-member)
dscp (Frame Relay VC-bundle-member)
encapsulation (Frame Relay VC-bundle)
inarp (Frame Relay VC-bundle-member)
precedence (Frame Relay VC-bundle-member)
protect (Frame Relay VC-bundle-member)
show frame-relay ip rtp header-compression
show frame-relay ip tcp header-compression
Frame Relay PVC Bundles with QoS Support for IP and MPLS
First Published: November 25, 2002Last Updated: February 28, 2006Frame Relay permanent virtual circuit (PVC) bundle functionality allows you to associate a group of Frame Relay PVCs with a single next-hop address. When Frame Relay PVC bundles are used with IP, packets are mapped to specific PVCs in the bundle on the basis of the precedence value or differentiated services code point (DSCP) settings in the type of service (ToS) field of the IP header. Each packet is treated differently according to the QoS configured for each PVC.
MPLS QoS support for Frame Relay PVC bundles extends Frame Relay PVC bundle functionality to support the mapping of Multiprotocol Label Switching (MPLS) packets to specific PVCs in the bundle. MPLS packets are mapped to PVCs according to the settings of the experimental (EXP) bits in the MPLS packet header.
History for the Frame Relay PVC Bundles with QoS Support for IP and MPLS Feature
12.2(13)T
This feature was introduced.
12.2(28)SB
This feature was integrated into Cisco IOS Release 12.2(28)SB.
Finding Support Information for Platforms and Cisco IOS Software Images
Use Cisco Feature Navigator to find information about platform support and Cisco IOS software image support. Access Cisco Feature Navigator at http://www.cisco.com/go/fn. You must have an account on Cisco.com. If you do not have an account or have forgotten your username or password, click Cancel at the login dialog box and follow the instructions that appear.
Contents
•
Prerequisites for Frame Relay PVC Bundles with QoS Support for IP and MPLS
•
•
•
•
Prerequisites for Frame Relay PVC Bundles with QoS Support for IP and MPLS
To implement Frame Relay PVC bundles between two routers, you must enable IP Cisco Express Forwarding switching on the routers.
To configure MPLS EXP levels on bundle member PVCs, you must have tag-switching enabled on the interface.
It is recommended (but not required) that you implement PVC Interface Priority Queueing (PIPQ) in conjunction with Frame Relay PVC bundles. This will ensure that if the interface becomes congested, higher-priority traffic can exit the interface ahead of lower-priority traffic.
Restrictions for Frame Relay PVC Bundles with QoS Support for IP and MPLS
•
•
•
•
•
•
•
Information About Frame Relay PVC Bundles with QoS Support for IP and MPLS
Before configuring and implementing Frame Relay PVC Bundles with QoS Support for IP and MPLS, you should understand the following concepts:
•
•
•
Benefits of Frame Relay PVC Bundles with QoS Support for IP and MPLS
•
•
•
Frame Relay PVC Bundle Support
The use of Frame Relay PVC bundles allows you to configure multiple PVCs with different QoS characteristics between any pair of Frame Relay-connected routers. As shown in Figure 1, a PVC bundle may contain up to eight PVCs. The individual PVCs within a bundle are called bundle members.
To determine which PVC in a bundle will be used to forward a specific type of traffic, the router maps the IP precedence level or DSCP value in an IPv4 packet header to a PVC configured with the same value. In the case of MPLS, packets are mapped to specific PVCs in a bundle based on the settings of the EXP bits in the MPLS packet headers.
Once you define a Frame Relay bundle and add PVCs to it, you can configure attributes and characteristics to discrete PVC bundle members, or you can apply them collectively at the bundle level. Frame Relay traffic shaping may be applied to every PVC within a bundle. As with individual PVCs, you can enable rate adaptation to occur in response to incoming backward explicit congestion notifications (BECN) from the network.
Figure 1 Frame Relay PVC bundle
You can create differentiated service using PVC bundles by distributing IP precedence levels or DSCP values over the various bundle members. You can map either a single precedence level or a range of precedence levels to each PVC in the bundle. Thus, either you can limit an individual PVC to carry only packets marked with a specific precedence level or you can enable a PVC to carry packets marked with different precedence levels.
Service Levels and PVC Selection Criteria
The DSCP and Precedence bits classify IP packet service levels. The Precedence field consists of the first three bits of the ToS octet in the IPv4 header. These bits define eight precedence levels. When DSCP mapping is used, the DSCP octet replaces the ToS octet in the IPv4 header. Currently the first six bits are used, defining 64 service levels.
Using precedence-based or DSCP-based mapping, each IPv4 packet is mapped to a specific PVC in the bundle, according to the value of the ToS or DSCP octet in the IP header. There is no special treatment for broadcast or multicast or IP routing packets; the only differentiation in treatment is a result of the ToS or DSCP octet settings.
The MPLS EXP bits make up a three-bit experimental field in the MPLS packet header. They are a bit-by-bit copy of the IP Precedence bits and provide the same eight QoS levels. Under MPLS EXP-based mapping, each MPLS packet is mapped to a specific PVC in the bundle, according the setting of the EXP bits.
Frame Relay PVC Bundle Management
In addition to mapping specific traffic types to specific PVCs according to QoS parameters designated by the ToS or DSCP values in the IPv4 headers or EXP values in the MPLS headers, PVC bundle management takes care of handling non-IP traffic and determining what happens if a PVC goes down.
By default, Inverse Address Resolution Protocol (ARP) traffic and other critical non-IP traffic is carried by the PVC configured for carrying IP Precedence or EXP level 6 or DSCP level 63. You can select a PVC with a different QoS to carry Inverse ARP traffic if required. Noncritical non-IP traffic is carried by the PVC that configured for carrying IP precedence, EXP, or DSCP level 0.
It is important during configuration to account for every precedence, EXP, or DSCP level in the configuration of the PVC bundle members. If all the packet service levels are not accounted for, the PVC bundle will never come up.
Once a PVC bundle is up, if an individual bundle member goes down, an attempt is made to identify an alternate PVC to handle the packet service level or levels that were carried by the downed PVC. If no alternate PVC is found, the entire PVC bundle is brought down.
Traffic Bumping
You can configure each PVC bundle member to bump traffic to another PVC in the bundle in the event that the bundle member goes down. You can specify whether the bumping will be implicit or explicit bumping. You can also specify that a particular PVC will never accept bumped traffic from another PVC. The default conditions are to perform implicit traffic bumping and to accept bumped traffic.
Implicit bumping diverts the traffic from a failed PVC to the PVC having the next-lower service level. Explicit bumping forces the traffic to a specific PVC rather than allowing it to find a PVC carrying traffic of the next-lower service level. For example, PVC x, responsible for carrying precedence level 3 traffic, can be configured to bump its traffic to PVC y, responsible for carrying precedence level 6 traffic—provided that PVC y is configured to accept bumped traffic. If PVC x goes down, PVC y takes over. If PVC y is already down or goes down later, the alternate PVC selected will depend on the bumping rule for PVC y. If no alternate PVC can be found for bumped traffic, the entire PVC bundle goes down.
PVC-Bundle Protection Rules
Traffic bumping provides a way to keep a PVC bundle up and traffic flowing even though some individual PVCs may be down. Protection rules provide a way to force the PVC bundle down even though some individual PVCs are up and might be able to handle all the traffic, though perhaps not in a satisfactory manner.
You can configure a PVC bundle member as an individually protected PVC or as part of a PVC bundle protected group. Only one protected group may exist within a PVC bundle; however, many individually protected PVCs may exist. The protection rules add flexibility for controlling the PVC bundle state.
When any one individually protected PVC goes down, the entire bundle goes down. If all the PVCs in a protected group go down, the entire bundle goes down.
If no protection rule is specified, the PVC bundle goes down only when all the PVCs go down. However, protection is overridden if a PVC that has no place to bump its traffic goes down. In this case, the entire bundle will go down despite any protection rules that have been set up.
MPLS EXP-based Mapping
To enable MPLS EXP-based mapping, tag-switching must be enabled on the interface or subinterface by using the tag-switching ip command. When tag-switching is enabled, MPLS and IP packets can flow across the interface and PVC bundles that are configured for IP Precedence mapping are converted to MPLS EXP mapping. The PVC bundle functionality remains the same with respect to priority levels, bumping, and so on, but the match precedence command is replaced by match exp, and each precedence command is replaced by the exp command. The effect is that a bundle member PVC previously configured to carry precedence level 1 IP traffic now carries EXP level 1 MPLS traffic.
PVC bundles configured for DSCP mapping go down when tag-switching is enabled. The DSCP configuration for each bundle member PVC is reset, resulting in the PVCs being unmapped and Inverse ARP, bumping, and protection settings being unconfigured. The match dscp command is replaced by match exp command.
When tag-switching is disabled, the match precedence and match dscp commands are restored and the exp commands are replaced by precedence commands.
When tag-switching is enabled or disabled, PVC bundles configured for IP precedence mapping or MPLS EXP mapping will stay up and traffic will transmit over the appropriate bundle member PVCs.
How to Configure Frame Relay PVC Bundles with QoS Support for IP and MPLS
This section contains the following configuration tasks.
•
•
•
•
Configuring Frame Relay PVC Bundles with IP QoS Support
To configure Frame Relay PVC bundles for handling IP packets, perform the following steps:
SUMMARY STEPS
1.
2.
3.
4.
5.
or
interface type number.subinterface-number [multipoint | point-to-point]6.
7.
8.
9.
10.
11.
12.
13.
14.
or
dscp {level | other}15.
16.
17.
18.
19.
DETAILED STEPS
Configuring Frame Relay PVC Bundles with MPLS QoS Support
To configure Frame Relay PVC bundles for handling MPLS packets, perform the following steps:
SUMMARY STEPS
1.
2.
3.
4.
5.
or
interface {type slot | port-adapter | port.subinterface-number}[multipoint | point-to-point]
6.
7.
8.
9.
10.
11.
12.
13.
14.
15.
16.
17.
18.
19.
DETAILED STEPS
Verifying Frame Relay PVC Bundles Configuration
To verify the configuration and operation of Frame Relay PVC bundles with QoS support, perform the following optional steps:
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
7.
DETAILED STEPS
Monitoring and Maintaining Frame Relay PVC Bundles
To monitor and maintain Frame Relay PVC bundles, perform this task.
SUMMARY STEPS
1.
2.
3.
DETAILED STEPS
Configuration Examples for Frame Relay PVC Bundles with QoS Support for IP and MPLS
This section provides the following configuration examples:
•
•
•
•
•
PVC Bundles with IP QoS Support on Main, Multipoint, and Point-to-Point Interfaces Example
The following example shows the configuration of five PVC bundles with IP precedence and DSCP mapping. Two bundles are configured on the main interface, one bundle with static mapping and one with dynamic mapping. Two bundles are configured on a multipoint subinterface, one bundle with static mapping and one with dynamic mapping. One bundle is configured on a point-to-point subinterface.
configure terminalip routingip cefinterface Serial 1/4encapsulation frame-relayframe-relay intf-type dteip address 10.1.1.1 255.0.0.0frame-relay map ip 192.168.2.2 vc-bundle MAIN-1-staticframe-relay vc-bundle MAIN-1-staticmatch precedencepvc 100 1aprecedence otherpvc 101 1bprecedence 1pvc 102 1cprecedence 2pvc 103 1dprecedence 3pvc 104 1eprecedence 4pvc 105 1fprecedence 5pvc 106 1gprecedence 6pvc 107 1hframe-relay vc-bundle MAIN-2-dynamicmatch precedencepvc 200precedence 0pvc 201precedence 1pvc 202precedence 2pvc 203precedence 3pvc 204precedence 4pvc 205precedence 5pvc 206precedence 6pvc 207precedence 7interface Serial 1/4.1 multipointip address 172.16.1.1 255.0.0.0frame-relay map ip 172.17.2.2 vc-bundle MP-3-staticframe-relay vc-bundle MP-3-staticmatch precedencepvc 300 3aprecedence 0pvc 301 3bprecedence 1pvc 302 3cprecedence 2pvc 303 3dprecedence 3pvc 304 3eprecedence 4pvc 305 3fprecedence 5pvc 306 3gprecedence 6pvc 307 3hprecedence 7interface Serial 1/4.1 multipointframe-relay vc-bundle MP-4-dynamicmatch precedencematch dscppvc 400 4adscp otherpvc 401 4bdscp 10-19pvc 402 4cdscp 20-29pvc 403 4ddscp 30-39pvc 404 4edscp 40-49pvc 405 4fdscp 50-59pvc 406 4gdscp 60-62pvc 407 4hdscp 63endinterface Serial 1/4.2 point-to-pointip address 192.168.2.1 255.0.0.0frame-relay vc-bundle P2P-5match precedencepvc 500 5aprecedence 0pvc 501 5bprecedence 1pvc 502 5cprecedence 2pvc 503 5dprecedence 3pvc 504 5eprecedence 4pvc 505 5fprecedence 5pvc 506 5gprecedence 6pvc 507 5hprecedence 7PVC Bundle with IP QoS Support with Multiple QoS Parameters Example
The following example shows the configuration of a Frame Relay PVC bundle with DSCP-based mapping. The bundle member PVCs are configured with bumping, protection, and other parameters.
interface Serial 1/4.2 point-to-pointframe-relay vc-bundle BUNDLE-SEFENencapsulation ietfmatch dscppvc 301dscp otherbump explicit 45protect groupclass CIR-64000pvc 302dscp 40-49bump explicit 20no bump trafficprotect vcinarppvc 303dscp 30-39bump implicitprotect groupPVC Bundle with MPLS QoS Support Example
The following example shows the configuration of four Frame Relay PVC bundle members with MPLS EXP level support in the PVC bundle named "user1".
interface serial 0.1 point-to-pointencapsulation frame-relayip address 10.1.1.1tag-switching ipframe-relay vc-bundle user1pvc 100 ny-controlclass controlexp 7protect vcpvc 101 ny-premiumclass premiumexp 6-5bump explicit 7no bump trafficprotect grouppvc 102 my-priorityclass priorityexp 4-2protect grouppvc 103 ny-basicclass basicexp otherprotect group
Verifying Frame Relay PVC Bundle Configuration Examples
The following examples show output for the commands that can be used to verify Frame Relay PVC bundle configuration.
Sample Output for the show frame-relay vc-bundle Command
The following example shows the Frame Relay PVC bundle named "MP-4-dynamic" with PVC protection applied. Note that in this PVC bundle, DLCI 400 is configured to bump traffic explicitly to the PVC that handles DSCP level 40, which is DLCI 404. All the other DLCIs are configured for implicit bumping. In addition, all the DLCIs are configured to accept bumped traffic.
The asterisk (*) before PVC 4a indicates that this PVC was configured with the precedence other command, which means the PVC will handle all levels that are not explicitly configured on other PVCs.
In this example all PVCs are up so the values in the "Active level" fields match the values in the "Config level" fields. If a PVC goes down and its traffic is bumped, the "Active level" field value for the PVC that went down is cleared. The "Active level" field values for the PVC that the traffic bumped to will be updated to include the levels of the PVC that went down.
The first three PVCs in the following example make up a protected group. All three of these PVCs must go down before the bundle will go down. The last two PVCs are protected PVCs: if either of these PVCs go down, the bundle will go down.
Router# show frame-relay vc-bundle MP-4-dynamicMP-4-dynamic on Serial 1/4.1 - Status: UP Match-type: DSCPName DLCI Config. Active Bumping PG/ CIR Statuslevel level to/accept PV kbps*4a 400 0-9 0-9 40/Yes pg up4b 401 10-19 10-19 9/Yes pg up4c 402 20-29 20-29 19/Yes pg up4d 403 30-39 30-39 29/Yes - up4e 404 40-49 40-49 39/Yes - up4f 405 50-59 50-59 49/Yes - up4g 406 60-62 60-62 59/Yes pv up4h 407 63 63 62/Yes pv upPackets sent out on vc-bundle MP-4-dynamic : 0:Router#The following example shows the detail output of a PVC bundle. Note in this example that because all packet service levels are not handled, and because the PVCs are currently down, this bundle can never come up.
Router# show frame-relay vc-bundle x41 detailx41 on Serial1/1 - Status: DOWN Match-type: DSCPName DLCI Config. Active Bumping PG/ CIR Statuslevel level to/accept PV kbps410 50-62 49/Yes - down411 30,32,34,36,3.. 29/Yes - downPackets sent out on vc-bundle x41 : 0Active configuration and statistics for each member PVCDLCI Output pkts Active level410 0 50-62411 0 30,32,34,36,38-40Router#Sample Output for the show frame-relay map Command
The following sample output displays map and connection information for a PVC bundle called "MAIN-1-static":
Router# show frame-relay mapSerial1/4 (up):ip 10.2.2.2 vc-bundle MAIN-1-static, static,CISCO, status upSample Output for the show frame-relay pvc Command
The following sample output indicates that PVC 202 is a member of VC bundle "MAIN-1-static":
Router# show frame-relay pvc 202PVC Statistics for interface Serial1/4 (Frame Relay DTE)DLCI = 202, DLCI USAGE = LOCAL, PVC STATUS = STATIC, INTERFACE = Serial1/4input pkts 0 output pkts 45 in bytes 0out bytes 45000 dropped pkts 0 in FECN pkts 0in BECN pkts 0 out FECN pkts 0 out BECN pkts 0in DE pkts 0 out DE pkts 0out bcast pkts 0 out bcast bytes 05 minute input rate 0 bits/sec, 0 packets/sec5 minute output rate 2000 bits/sec, 2 packets/secpvc create time 00:01:25, last time pvc status changed 00:01:11VC-Bundle MAIN-1-staticSample Output for the show adjacency Command
The following is sample output for the show adjacency command for a PVC bundle configured on serial subinterface 1/4.1. Each bundle member is listed. The bundle itself is indicated by "incomplete" because no traffic actually transmitted on that entry.
Router# show adjacencyProtocol Interface AddressIP Serial1/4.1 10.2.2.2(4)IP Serial1/4.1 10.2.2.2(4)IP Serial1/4.1 10.2.2.2(4)IP Serial1/4.1 10.2.2.2(4)IP Serial1/4.1 10.2.2.2(4)IP Serial1/4.1 10.2.2.2(4)IP Serial1/4.1 10.2.2.2(4)IP Serial1/4.1 10.2.2.2(4)IP Serial1/4.1 10.2.2.2(5) (incomplete)Monitoring and Maintaining Frame Relay PVC Bundles Examples
The following examples show output for the debug frame-relay adjacency and debug frame-relay vc-bundle commands, which can be used to troubleshoot Frame Relay PVC bundle operation. "FR-VCB" indicates output from the debug frame-relay vc-bundle command, and "FR-ADJ" indicates output from the debug frame-relay adjacency command.
Note
The following is sample output that shows a PVC bundle that uses static map coming up. PVC bundle member 100 comes up first, then the PVC bundle itself can come up.
Router# debug frame-relay vc-bundle state-changeRouter# debug frame-relay adjacency vc-bundle00:35:58:FR-VCB:MAIN-1-static:member 100 state changed to UP 00:35:58:FR-VCB:MAIN-1-static:state changed to UP00:35:58:FR-ADJ:vcb MAIN-1-static:ip 10.2.2.2:adding primary adj00:35:58:FR-ADJ:vcb MAIN-1-static:member 100:adding adj00:35:58:FR-ADJ:vcb MAIN-1-static:member 100:locking adj at index 0 00:35:58:FR-ADJ:vcb MAIN-1-static:member 100:locking adj at index 100:35:58:FR-ADJ:vcb MAIN-1-static:member 100:locking adj at index 200:35:58:FR-ADJ:vcb MAIN-1-static:member 100:locking adj at index 300:35:58:FR-ADJ:vcb MAIN-1-static:member 100:locking adj at index 400:35:58:FR-ADJ:vcb MAIN-1-static:member 100:locking adj at index 500:35:58:FR-ADJ:vcb MAIN-1-static:member 100:locking adj at index 600:35:58:FR-ADJ:vcb MAIN-1-static:member 100:locking adj at index 700:35:58:%FR-5-DLCICHANGE:Interface Serial1/4 - DLCI 100 state changed to ACTIVE 00:35:58:FR-VCB:MAIN-1-static:member 101 state changed to UP00:35:58:FR-ADJ:vcb MAIN-1-static:ip 10.2.2.2:updating primary adj00:35:58:FR-ADJ:vcb MAIN-1-static:member 100:updating adj00:35:58:FR-ADJ:vcb MAIN-1-static:member 101:adding adj00:35:58:FR-ADJ:vcb MAIN-1-static:member 100:unlocking adj at index 100:35:58:FR-ADJ:vcb MAIN-1-static:member 101:locking adj at index 1The following is sample output that shows a PVC bundle going down. Each bundle member PVC is marked for removal from Cisco Express Forwarding adjacency table, and then the adjacency for the PVC bundle itself is marked for removal. The adjacencies are actually removed from the table later when a background clean-up process runs.
00:38:35:FR-VCB:MP-3-static:state changed to DOWN00:38:35:FR-ADJ:vcb MP-3-static:ip 172.17.2.2:member 300:removing adj00:38:35:FR-ADJ:vcb MP-3-static:ip 172.17.2.2:member 301:removing adj00:38:35:FR-ADJ:vcb MP-3-static:ip 172.17.2.2:member 302:removing adj00:38:35:FR-ADJ:vcb MP-3-static:ip 172.17.2.2:member 303:removing adj00:38:35:FR-ADJ:vcb MP-3-static:ip 172.17.2.2:member 304:removing adj00:38:35:FR-ADJ:vcb MP-3-static:ip 172.17.2.2:member 305:removing adj00:38:35:FR-ADJ:vcb MP-3-static:ip 172.17.2.2:removing primary adjThe following is sample output that shows Inverse ARP information for the PVC bundle. PVC bundle member 406 is the only PVC in the bundle to handle Inverse ARP packets. The Inverse ARP packets coming in on other bundle member PVCs are dropped.
00:23:48:FR-VCB:MP-4-dynamic:inarp received on elected member 40600:23:48:FR-VCB:MP-4-dynamic:installing dynamic map00:23:48:FR-VCB:MP-4-dynamic:dropping inarp received on member 40700:23:52:FR-VCB:MP-4-dynamic:sending inarp pkt on member 406In the following example the PVC bundle goes down because the protected group goes down. All information about active transmission on each PVC is removed.
00:58:27:FR-VCB:MP-4-dynamic:member 402 state changed to DOWN00:58:27:FR-VCB:MP-4-dynamic:protected group is DOWN00:58:27:FR-VCB:MP-4-dynamic:state changed to DOWN00:58:27:FR-VCB:MP-4-dynamic:active table resetAdditional References
The following sections provide references related to Frame Relay PVC Bundles with QoS Support for IP and MPLS.
Related Documents
Frame Relay configuration tasks
"Configuring Frame Relay" chapter in the Cisco IOS Wide-Area Networking Configuration Guide, Release 12.2
Frame Relay commands
"Frame Relay Commands" chapter in the Cisco IOS Wide-Area Networking Command Reference, Release 12.2
Frame Relay PVC interface priority queueing configuration tasks
"Configuring Weighted Fair Queueing" section in the Congestion Management chapter in the Cisco IOS Quality of Service Configuration Guide, Release 12.2
Standards
MIBs
None
To locate and download MIBs for selected platforms, Cisco IOS releases, and feature sets, use Cisco MIB Locator found at the following URL:
RFCs
Technical Assistance
Command Reference
This section documents modified commands only.
•
•
•
•
•
•
•
•
•
bump (Frame Relay VC-bundle-member)
To configure the bumping rules for a Frame Relay permanent virtual circuit (PVC) bundle member, use the bump command in Frame Relay VC-bundle-member configuration mode. To specify that the PVC bundle member does not accept any bumped traffic, use the no bump traffic command.
bump {explicit level | implicit | traffic}
no bump traffic
Syntax Description
Defaults
Implicit bumping rule stipulates that bumped traffic is to be carried by a PVC.
Command Modes
Frame Relay VC-bundle-member configuration
Command History
12.2(13)T
This command was introduced.
12.2(28)SB
This command was integrated into Cisco IOS Release 12.2(28)SB.
Usage Guidelines
Use the bump command to configure bumping rules for a discrete PVC bundle member. To change the configured bumping rules for a PVC bundle member, override the current configuration with a new bump command entry.
To return to the default condition of implicit bumping, use the bump implicit command.
The effects of different bumping configuration approaches are as follows:
•
•
•
•
Note
The following warnings appear during configuration and let you know about configuration problems that may prevent the bundle from coming up or cause the bundle to go down unexpectedly:
•
%DLCI 300 could end up bumping traffic to itself
•
%DLCI 306 is configured for bumping traffic to level 7
•
%DLCI(s) configured for explicitly bumping traffic to DLCI 300
•
%Presently no member is configured for level 3
•
%DLCI configured for level 0 does not accept bumping
Examples
The following example configures PVC 101 in the Frame Relay PVC bundle "bundle1" with explicit bumping to the PVC bundle member having a precedence level of 7. PVC 101 is also configured to prohibit traffic from other PVCs from being bumped to it.
frame-relay vc-bundle bundle1match precedencepvc 101precedence 5no bump trafficbump explicit 7Related Commands
class
To associate a map class with a specified data-link connection identifier (DLCI), use the class command in Frame Relay DLCI configuration mode or Frame Relay VC-bundle-member configuration mode. To remove the association between the DLCI and the map class, use the no form of this command.
class name
no class name
Syntax Description
Defaults
No map class is defined.
Command Modes
Frame Relay DLCI configuration
Frame Relay VC-bundle-member configurationCommand History
Usage Guidelines
This command applies to DLCIs that are created using the frame-relay interface-dlci command and to DLCIs that are created as permanent virtual circuit (PVC) bundle members within a specified Frame Relay PVC bundle. The PVC bundle is created using the frame-relay vc-bundle command. The Frame Relay PVC bundle member DLCIs are then created using the pvc command in Frame Relay VC-bundle configuration mode.
A map class applied to the interface will be applied to all PVC members in a PVC bundle. A class applied to an individual PVC-bundle member supersedes the class applied at the interface level.
The map class is created using the map-class frame-relay command in global configuration mode.
Examples
The following example shows how to define a map class called "slow-vcs" and apply it to DLCI 100:
interface serial 0.1 point-to-pointframe-relay interface-dlci 100class slow-vcsmap-class frame-relay slow-vcsframe-relay cir out 9600The following example shows how to apply a map class to a DLCI for which a frame-relay map statement exists. The frame-relay interface-dlci command must also be used.
interface serial 0.2 point-to-multipointframe-relay map ip 172.16.13.2 100frame-relay interface-dlci 100class slow_vcsmap-class frame-relay slow_vcsframe-relay traffic-rate 56000 128000frame-relay idle-timer 30The following example creates a Frame Relay map-class "class1" and shows how to assign it to PVC 300 in a Frame Relay PVC bundle called "MP-3-static":
map-class frame-relay HIinterface serial 1/4frame-relay map ip 10.2.2.2 vc-bundle MP-3-staticframe-relay vc-bundle MP-3-staticpvc 300class class1Related Commands
debug frame-relay adjacency
To display information pertaining to an adjacent node that has one or more Frame Relay permanent virtual circuit (PVC) bundles, use the debug frame-relay adjacency command in privileged EXEC mode. To stop displaying the adjacent node information, use the no form of this command.
debug frame-relay adjacency {pvc [dlci] | vc-bundle [vc-bundle-name]}
no debug frame-relay adjacency {pvc [dlci] | vc-bundle [vc-bundle-name]}
Syntax Description
Defaults
No default behaviors or values.
Command Modes
Privileged EXEC
Command History
12.2(13)T
This command was introduced.
12.2(28)SB
This command was integrated into Cisco IOS Release 12.2(28)SB.
Usage Guidelines
Use this command to monitor adjacency activity and status for an adjacent node.
Note
Examples
The following sample output from the debug frame-relay adjacency vc-bundle command shows PVC bundle "MP-4-dynamic" going down. Each bundle member PVC is marked for removal from the Cisco Express Forwarding adjacency table, and then the adjacency for the PVC bundle itself is marked for removal. The adjacencies are actually removed from the table later when a background clean-up process runs.
Router# debug frame-relay adjacency vc-bundle MP-4-dynamic00:46:35: FR-ADJ: vcb MP-4-dynamic: ip 10.2.2.2: member 400: removing adj00:46:35: FR-ADJ: vcb MP-4-dynamic: ip 10.2.2.2: member 401: removing adj00:46:35: FR-ADJ: vcb MP-4-dynamic: ip 10.2.2.2: member 402: removing adj00:46:35: FR-ADJ: vcb MP-4-dynamic: ip 10.2.2.2: member 403: removing adj00:46:35: FR-ADJ: vcb MP-4-dynamic: ip 10.2.2.2: member 404: removing adj00:46:35: FR-ADJ: vcb MP-4-dynamic: ip 10.2.2.2: member 405: removing adj00:46:35: FR-ADJ: vcb MP-4-dynamic: ip 10.2.2.2: member 406: removing adj00:46:35: FR-ADJ: vcb MP-4-dynamic: ip 10.2.2.2: member 407: removing adj00:46:35: FR-ADJ: vcb MP-4-dynamic: ip 10.2.2.2: removing primary adjRelated Commands
debug frame-relay vc-bundle
Displays information pertaining to all the PVC bundles configured on the router.
debug frame-relay vc-bundle
To display information about the Frame Relay permanent virtual circuit (PVC) bundles that are configured on a router, use the debug frame-relay vc-bundle command in privileged EXEC mode. To stop the display, use the no form of this command.
debug frame-relay vc-bundle {detail | state-change} [vc-bundle-name]
no debug frame-relay vc-bundle {detail | state-change} [vc-bundle-name]
Syntax Description
Command Modes
Privileged EXEC
Command History
12.2(13)T
This command was introduced.
12.2(28)SB
This command was integrated into Cisco IOS Release 12.2(28)SB.
Usage Guidelines
Use this command to monitor state changes and Inverse Address Resolution Protocol (ARP) activity for one or all of the PVC bundles and bundle members configured on a router.
Note
Examples
The following is sample output from the debug frame-relay vc-bundle command that shows Inverse ARP information for the PVC bundle. PVC bundle member 406 is the only PVC in the bundle to handle Inverse ARP packets. The Inverse ARP packets coming in on other bundle member PVCs are dropped.
Router# debug frame-relay vc-bundle detail00:23:48:FR-VCB:MP-4-dynamic:inarp received on elected member 40600:23:48:FR-VCB:MP-4-dynamic:installing dynamic map00:23:48:FR-VCB:MP-4-dynamic:dropping inarp received on member 40700:23:52:FR-VCB:MP-4-dynamic:sending inarp pkt on member 406In the following example the PVC bundle goes down because the protected group goes down. All information about active transmission on each PVC is removed.
00:58:27:FR-VCB:MP-4-dynamic:member 402 state changed to DOWN00:58:27:FR-VCB:MP-4-dynamic:protected group is DOWN00:58:27:FR-VCB:MP-4-dynamic:state changed to DOWN00:58:27:FR-VCB:MP-4-dynamic:active table resetThe following is sample output from the debug frame-relay vc-bundle detail command. State change and Inverse ARP activity is displayed for all PVC bundles and bundle members on the router.
Router# debug frame-relay adjacency vc-bundle detail00:33:40: FR-VCB: MP-4-dynamic: member 404 state changed to UP00:33:40: FR-VCB: MP-4-dynamic: active table update00:33:40: FR-VCB: MP-3-static: sending inarp pkt on member 30000:33:41: FR-VCB: MP-3-static: inarp received on elected member 30000:33:48: FR-VCB: MP-3-static: inarp received on elected member 30000:33:48: FR-VCB: MAIN-1-static: dropping inarp received on member 10000:33:48: FR-VCB: MP-4-dynamic: dropping inarp received on member 40400:33:48: FR-VCB: MP-4-dynamic: dropping inarp received on member 40500:33:48: FR-VCB: P2P-5: dropping inarp received on member 50700:33:48: FR-VCB: MP-3-static: dropping inarp received on member 30300:33:48: FR-VCB: MAIN-2-dynamic: dropping inarp received on member 20200:33:48: FR-VCB: MAIN-1-static: dropping inarp received on member 10700:33:48: FR-VCB: MP-3-static: dropping inarp received on member 30500:33:48: FR-VCB: MAIN-1-static: dropping inarp received on member 10500:33:49: FR-VCB: P2P-5: dropping inarp received on member 50500:33:49: FR-VCB: P2P-5: dropping inarp received on member 50400:33:49: FR-VCB: P2P-5: dropping inarp received on member 50300:33:49: FR-VCB: P2P-5: dropping inarp received on member 50200:33:49: FR-VCB: P2P-5: dropping inarp received on member 501Related Commands
debug frame-relay adjacency
Displays information pertaining to an adjacent node that has one or more Frame Relay PVC bundles.
dscp (Frame Relay VC-bundle-member)
To configure the differentiated services code point (DSCP) levels for a Frame Relay permanent virtual circuit (PVC) bundle member, use the dscp command in Frame Relay VC-bundle-member configuration mode. To remove the DSCP level configuration from the PVC, use the no form of this command.
dscp {level | other}
no dscp level
Syntax Description
Defaults
DSCP levels are not configured.
Command Modes
Frame Relay VC-bundle-member configuration
Command History
12.2(13)T
This command was introduced.
12.2(28)SB
This command was integrated into Cisco IOS Release 12.2(28)SB.
Usage Guidelines
Assignment of DSCP levels to PVC bundle members allows you to create differentiated service because you can distribute the DSCP levels over the various PVC bundle members. You can map a single DSCP level or range of levels to each discrete PVC in the bundle, thereby enabling PVCs in the bundle to carry packets marked with different DSCP levels. Use the dscp other command to configure a PVC to carry traffic marked with DSCP levels not specifically configured on other PVCs. Only one PVC in the bundle can be configured with the dscp other command.
This command is available only when the match type for the PVC bundle is set to dscp using the match dscp command in Frame Relay VC-bundle configuration mode.
You can overwrite the DSCP level configuration on a PVC by reentering the dscp command with a new level value.
There is no default value for this command. When the PVC bundle is set to dscp using the match dscp command, all PVCs in the bundle are reset to remove any existing DSCP values. If one or more DSCP values are not specifically configured, the bundle will not come up.
Note, however, that a PVC may exist in a bundle but have no DSCP value associated with it. As long as all valid DSCP values are handled by one or more of the other PVCs in the bundle, the bundle can come up, but the PVC that has no DSCP value configured will not participate in it.
A DSCP level can be configured on one PVC-bundle member per bundle. If you configure the same DSCP level on more than one PVCs within a bundle, the following error warning appears on the console:
%Overlapping diff-serv code pointsExamples
The following example assigns DSCP levels 0 through 9 to PVC bundle member 300 in a Frame Relay PVC bundle called "MP-3-static":
interface serial 1/4frame-relay map ip 10.2.2.2 vc-bundle MP-3-staticframe-relay vc-bundle MP-3-staticpvc 300dscp 0-9The following example changes the DSCP levels in the above example from 0 through 9 to 0, 9, and 20 through 29:
interface serial 1/4frame-relay map ip 10.2.2.2 vc-bundle MP-3-staticframe-relay vc-bundle MP-3-staticpvc 300dscp 0,9,20-29Related Commands
encapsulation (Frame Relay VC-bundle)
To override the encapsulation for a point-to-point subinterface and configure Frame Relay encapsulation for an individual Frame Relay permanent virtual circuit (PVC) bundle, use the encapsulation command in Frame Relay VC-bundle configuration mode. To disable the encapsulation for the individual PVC bundle and revert to the encapsulation for the point-to-point subinterface, use the no form of this command.
encapsulation [cisco | ietf]
no encapsulation [cisco | ietf]
Syntax Description
Defaults
Encapsulation type that is configured on the main interface.
Command Modes
Frame Relay VC-bundle configuration
Command History
12.2(13)T
This command was introduced.
12.2(28)SB
This command was integrated into Cisco IOS Release 12.2(28)SB.
Usage Guidelines
Use this command to override the encapsulation at a point-to-point subinterface for an individual Frame Relay PVC bundle. This command is available for point-to-point subinterfaces only; it cannot be used on multipoint interfaces.
Examples
The following example configures RFC 1490 encapsulation for the Frame Relay PVC bundle named "P2P-5":
interface serial 1/4.2 point-to-pointip address 10.1.1.1 255.0.0.0frame-relay vc-bundle P2P-5encapsulation ietfRelated Commands
exp
To configure Multiprotocol Label Switching (MPLS) experimental (EXP) levels for a Frame Relay permanent virtual circuit (PVC) bundle member, use the exp command in Frame Relay VC-bundle-member configuration mode. To remove the EXP level configuration from the PVC, use the no form of this command.
exp {level | other}
no exp
Syntax Description
Defaults
EXP levels are not configured.
Command Modes
Frame Relay VC-bundle-member configuration
Command History
12.2(13)T
This command was introduced.
12.2(28)SB
This command was integrated into Cisco IOS Release 12.2(28)SB.
Usage Guidelines
Assignment of MPLS EXP levels to Frame Relay PVC bundle members allows you to create differentiated service because you can distribute the levels over the various PVC bundle members. You can map a single level or a range of levels to each discrete PVC in the bundle, thereby enabling PVCs in the bundle to carry packets marked with different levels. Use the exp other command to indicate that a PVC can carry traffic marked with EXP levels not specifically configured for other PVCs. Only one PVC in the bundle can be configured using the exp other command.
All EXP levels must be accounted for in the PVC bundle configuration, or the bundle will not come up. Note, however, that a PVC may be a bundle member but have no EXP level associated with it. As long as all valid EXP levels are handled by other PVCs in the bundle, the bundle can come up, but the PVC that has no EXP level configured will not participate in it.
The exp command is available only when tag switching is configured on the interface with the tag-switching ip command.
You can overwrite the EXP level configuration on a PVC by reentering the exp command with a new value.
The MPLS experimental bits are a bit-by-bit copy of the IP precedence bits. When Frame Relay PVC bundles are configured for IP precedence and tag switching is enabled, the precedence command is replaced by the exp command. When tag switching is disabled, the exp command is replaced by the precedence command.
Examples
The following example shows the configuration of four Frame Relay PVC bundle members in PVC bundle "bundle1" configured with MPLS EXP level support:
interface serial 0.1 point-to-pointencapsulation frame-relayip address 10.1.1.1tag-switching ipframe-relay vc-bundle bundle1pvc 100 ny-controlclass controlexp 7protect vcpvc 101 ny-premiumclass premiumexp 6-5protect groupno bump trafficbump explicit 7pvc 102 my-priorityclass priorityexp 4-2protect grouppvc 103 ny-basicclass basicexp otherprotect groupRelated Commands
frame-relay inverse-arp
To reenable Inverse Address Resolution Protocol (Inverse ARP) on a specified interface, subinterface, data-link connection identifier (DLCI), or Frame Relay permanent virtual circuit (PVC) bundle if Inverse ARP was previously disabled, use the frame-relay inverse-arp command in interface configuration mode. To disable Inverse ARP, use the no form of this command.
frame-relay inverse-arp [protocol] [dlci | vc-bundle vc-bundle-name]
no frame-relay inverse-arp [protocol] [dlci | vc-bundle vc-bundle-name]
Syntax Description
Defaults
Inverse ARP is enabled.
Command Modes
Interface configuration
Command History
Usage Guidelines
To enable Inverse ARP for all protocols that were enabled before the prior no frame-relay inverse-arp command was issued, use the frame-relay inverse-arp command without arguments. To disable Inverse ARP for all protocols supported on an interface, use the no frame-relay inverse-arp command without arguments.
To enable or disable Inverse ARP for a specific protocol and DLCI pair, use both the protocol and dlci arguments. To enable or disable Inverse ARP for a specific protocol and Frame Relay PVC bundle (consisting of up to eight DLCIs), use both the protocol and vc-bundle vc-bundle-name elements.
To enable or disable Inverse ARP for all protocols on a DLCI or Frame Relay PVC bundle, use either the dlci argument by itself or the vc-bundle vc-bundle-name keyword and argument pair by itself. To enable or disable Inverse ARP for a specific protocol for all DLCIs on the specified interface or subinterface, use only the protocol argument.
When a Frame Relay PVC bundle is specified, only one member of the PVC bundle will handle Inverse ARP packets. By default, the bundle member PVC that handles precedence or EXP level 6 or DSCP level 63 handles Inverse ARP packets. Use the inarp command to configure a different PVC bundle member to handle Inverse ARP packets.
This implementation of Inverse ARP is based on RFC 1293. It allows a router or access server running Frame Relay to discover the protocol address at the other side of a virtual circuit.
The show frame-relay map command displays the word "dynamic" to flag virtual circuits that are created dynamically by Inverse ARP.
Examples
The following example sets Inverse ARP on DLCI 100 on an interface running Internetwork Packet Exchange (IPX):
interface serial 0frame-relay inverse-arp ipx 100Related Commands
frame-relay map
To define the mapping between a destination protocol address and the data-link connection identifier (DLCI) or Frame Relay permanent virtual circuit (PVC) bundle that connects to the destination address, use the frame-relay map command in interface configuration mode. To delete the map entry, use the no form of this command.
frame-relay map protocol protocol-address {dlci | vc-bundle vc-bundle-name}[broadcast] [ietf | cisco] [payload-compression {packet-by-packet | frf9 stac [one-way-negotiation] [ratio level] [skip-zero-sync] [software | hardware-options] | data-stream stac [one-way-negotiation] [ratio level] [software | hardware-options]}]
no frame-relay map protocol protocol-address
Syntax Description
protocol
One of the following values: appletalk, decnet, dlsw, ip, ipx, llc2, and rsrb.
protocol-address
Destination protocol address.
dlci
DLCI number used to connect to the specified protocol address on the interface. Acceptable numbers are integers from 16 through 1007, inclusive.
vc-bundle vc-bundle-name
A specific Frame Relay PVC bundle configured on the interface.
broadcast
(Optional) Forwards broadcasts to this address when multicast is not enabled (see the frame-relay multicast-dlci command for more information about multicasts). This keyword also simplifies the configuration of Open Shortest Path First (OSPF) (see the "Usage Guidelines" section for more detail).
ietf
(Optional) Internet Engineering Task Force (IETF) form of Frame Relay encapsulation, based on RFC 1490 and RFC 2427. Used when the router or access server is connected to another vendor's equipment across a Frame Relay network.
cisco
(Optional) Cisco-proprietary encapsulation method consisting of a four-byte header, with two bytes to identify the DLCI and two bytes to identify the packet type.
payload-compression
(Optional) Enables payload compression.
packet-by-packet
(Optional) Packet-by-packet payload compression using the Stacker method.
frf9 stac
(Optional) Enables FRF.9 compression using the Stacker method.
•
•
•
one-way-negotiation
(Optional) Enables one-way negotiation. Use this keyword if your router will be negotiating compression with another device that is running Cisco IOS Release 12.1(9) or earlier releases. Later Cisco IOS releases use a two-way handshake by default to negotiate compression.
ratio level
(Optional) Sets throughput versus compression ratio. This option is available only with hardware compression. Values for the level argument are as follows:
high—high compression versus low throughput
medium—medium compression versus medium throughput
low—low compression versus high throughput (default)
skip-zero-sync
(Optional) Causes compression frames to be numbered starting from 1 rather than 0. Use this keyword if your router will be interoperating with a device conforming to IBM partner conventions.
software
(Optional) Specifies that compression is implemented in the Cisco IOS software installed in the main processor of the router.
hardware-options
(Optional) Choose one of the following hardware options:
caim element-number—Enables the CAIM3 to perform compression.
distributed—Specifies that compression is implemented in the software that is installed in a VIP2. If the VIP2 is not available, compression is performed in the main processor of the router (software compression). This option applies only to the Cisco 7500 series routers. This option is not supported with data-stream compression.
csa csa-number—Specifies the CSA to use for a particular interface. This option applies only to Cisco 7200 series routers.
data-stream stac
(Optional) Enables data-stream compression using the Stacker method.
•
•
1 CSA = compression service adapter
2 VIP2 = second-generation Versatile Interface Processor
3 CAIM = compression Advanced Interface Module
Defaults
No mapping is defined.
Command Modes
Interface configuration
Command History
Usage Guidelines
Many DLCIs can be known by a router or access server and can send data to many different places, but they are all multiplexed over one physical link. The Frame Relay map defines the logical connection between a specific protocol and address pair and the correct DLCI or PVC bundle.
The optional ietf and cisco keywords allow flexibility in the configuration. If no keywords are specified, the map inherits the attributes set with the encapsulation frame-relay command. You can also use the encapsulation options to specify, for example, that all interfaces use IETF encapsulation except one, which needs the original Cisco encapsulation method and can be configured through use of the cisco keyword with the frame-relay map command.
Data-stream compression is supported on interfaces and virtual circuits (VCs) using Cisco proprietary encapsulation. When the data-stream stac keyword is specified, Cisco encapsulation is automatically enabled. FRF.9 compression is supported on IETF-encapsulated VCs and interfaces. When the frf9 stac keyword is specified, IETF encapsulation is automatically enabled.
Packet-by-packet compression is Cisco-proprietary and will not interoperate with routers of other manufacturers.
You can disable payload compression by entering the no frame-relay map payload command and then entering the frame-relay map command again with one of the other encapsulation keywords (ietf or cisco).
Use the frame-relay map command to enable or disable payload compression on multipoint interfaces. Use the frame-relay payload-compression command to enable or disable payload compression on point-to-point interfaces.
We recommend that you shut down the interface before changing encapsulation types. Although shutting down the interface is not required, it ensures that the interface is reset for the new encapsulation.
The broadcast keyword provides two functions: it forwards broadcasts when multicasting is not enabled, and it simplifies the configuration of OSPF for nonbroadcast networks that will use Frame Relay.
The broadcast keyword may also be required for some routing protocols—for example, AppleTalk—that depend on regular routing table updates, especially when the router at the remote end is waiting for a routing update packet to arrive before adding the route.
By requiring selection of a designated router, OSPF treats a nonbroadcast multiaccess network such as Frame Relay in much the same way as it treats a broadcast network. When the frame-relay map command (with the broadcast keyword) and the ip ospf network command (with the broadcast keyword) are configured, there is no need to configure any neighbors manually. OSPF will run automatically over the Frame Relay network as a broadcast network. (See the ip ospf network interface command for more detail.)
Note
Examples
IP Address to DLCI Mapping Example
The following example maps the destination IP address 172.16.123.1 to DLCI 100:
interface serial 0frame-relay map ip 172.16.123.1 100 broadcastOSPF will use DLCI 100 to broadcast updates.
IP Address to Frame Relay PVC Bundle Mapping Example
The following example maps the destination IP address 172.16.123.1 to the Frame Relay PVC bundle named "MAIN-1":
interface serial 0frame-relay map ip 172.16.123.1 vc-bundle MAIN-1 broadcastFRF.9 Compression Example
The following example shows FRF.9 compression configuration using the frame-relay map command:
interface serial2/0/1ip address 172.16.1.4 255.255.255.0no ip route-cacheencapsulation frame-relay ietfno keepaliveshutdownframe-relay map ip 172.16.1.1 105 ietf payload-compression frf9 stacData-Stream Compression Example
The following example shows data-stream compression configuration using the frame-relay map command:
interface serial0/0frame-relay map ip 10.0.0.1 100 payload-compression data-stream stacRelated Commands
frame-relay vc-bundle
To create a Frame Relay permanent virtual circuit (PVC) bundle if it does not already exist, and to enter Frame Relay VC-bundle configuration mode, use the frame-relay vc-bundle command in interface configuration mode. To remove a Frame Relay PVC bundle, use the no form of this command.
frame-relay vc-bundle vc-bundle-name
no frame-relay vc-bundle vc-bundle-name
Syntax Description
Defaults
A bundle is not created.
Command Modes
Interface configuration
Command History
12.2(13)T
This command was introduced.
12.2(28)SB
This command was integrated into Cisco IOS Release 12.2(28)SB.
Usage Guidelines
Use this command to create a unique Frame Relay PVC bundle if one has not already been created using the frame-relay map command. Also use this command to enter Frame Relay VC-bundle configuration mode so you can configure PVC bundle attributes and PVC bundle members.
Examples
The following example creates a PVC bundle named "MAIN-1":
interface serial 0frame-relay vc-bundle MAIN-1Related Commands
frame-relay map
Defines mapping between a destination protocol address and the DLCI or Frame Relay PVC bundle that connects to the destination address.
inarp (Frame Relay VC-bundle-member)
To override the default permanent virtual circuit (PVC) bundle member used for Inverse Address Resolution Protocol (ARP) and specify a different PVC bundle member to handle the Inverse ARP packets, use the inarp command in Frame Relay VC-bundle-member configuration mode. To disable Inverse ARP on the PVC bundle member, use the no form of this command.
inarp
no inarp
Syntax Description
This command has no arguments or keywords.
Defaults
Inverse ARP is handled by the PVC that handles precedence or EXP level 6 or DSCP level 63.
Command Modes
Frame Relay VC-bundle-member configuration
Command History
12.2(13)T
This command was introduced.
12.2(28)SB
This command was integrated into Cisco IOS Release 12.2(28)SB.
Usage Guidelines
In each Frame Relay PVC bundle, Inverse ARP by default is handled by the PVC that handles precedence or EXP level 6 or DSCP level 63. In the default case, if the PVC handling Inverse ARP traffic goes down, the Inverse ARP packets are diverted to the PVC that has been configured to handle the bumped traffic for precedence level 6 or DSCP level 63.
Inverse ARP packets arriving on PVCs that are not configured to handle Inverse ARP will be dropped.
If you override the default packet service levels and enable Inverse ARP on a PVC that handles a different precedence or DSCP level, and that PVC goes down, the Inverse ARP packets will be dropped even if another PVC accepts the bumped traffic from the failed PVC.
If the inarp command is entered on two different PVC bundle members, Inverse ARP traffic will be handled by the second entry.
Examples
The following example shows Inverse ARP enabled on PVC 250, which handles DSCP level 60:
interface serial 1/4.1 multipointframe-relay vc-bundle MP-4-dynamicmatch dscppvc 100dscp otherpvc 250dscp 60inarpRelated Commands
match
To specify match criteria for the NetFlow MIB and Top Talkers feature, use the match command in NetFlow top talkers configuration mode. To remove match criteria for the NetFlow MIB and Top Talkers feature, use the no form of this command.
match [[source address | destination address | nexthop address] [ip-address] [mask | /nn]] [[source port | destination port] [port-number | min port | max port | min port max port]] [[source as | destination as] as-number] [[input-interface | output-interface] interface] [tos [tos-value | dscp dscp-value | precedence precedence-value]] [protocol [protocol-number | tcp | udp]] [flow-sampler flow-sampler-name] [class-map class] [packet-range | byte-range [[min-range-number max-range-number] [min minimum-range | max maximum-range | min minimum-range max maximum-range]]]
no match [[source address | destination address | nexthop address] [ip-address] [mask | /nn]] [[source port | destination port] [port-number | min port | max port | min port max port]] [[source as | destination as] as-number] [[input-interface | output-interface] interface] [tos [tos-value | dscp dscp-value | precedence precedence-value]] [protocol [protocol-number | tcp | udp]] [flow-sampler flow-sampler-name] [class-map class] [packet-range | byte-range [[min-range-number max-range-number] [min minimum-range | max maximum-range | min minimum-range max maximum-range]]]
Syntax Description
Defaults
No matching criteria are specified by default. All top talkers will be displayed.
Command Modes
NetFlow top talkers configuration
Command History
Usage Guidelines
Use this command to specify match criteria for the NetFlow MIB and Top Talkers feature. Using matching criteria is useful to restrict the list of top talkers.
If you are using a MIB and using simple network management protocol (SNMP) commands to configure this feature, refer to the following table for a mapping of the command-line interface (CLI) commands to the MIB SNMP commands:
Table 1 Router CLI Commands and Equivalent SNMP Commands
match source address [ip-address] [mask | /nn]
cnfTopFlowsMatchSrcAddress ip-address
cnfTopFlowsMatchSrcAddressType type1
cnfTopFlowsMatchSrcAddressMask mask
match destination address [ip-address] [mask | /nn]
cnfTopFlowsMatchDstAddress ip-address
cnfTopFlowsMatchDstAddressType type1
cnfTopFlowsMatchDstAddressMask mask
match nexthop address [ip-address] [mask | /nn]]
cnfTopFlowsMatchNhAddress ip-address
cnfTopFlowsMatchNhAddressType type1
cnfTopFlowsMatchNhAddressMask mask
match source port min port
cnfTopFlowsMatchSrcPortLo port
match source port max port
cnfTopFlowsMatchSrcPortHi port
match destination port min port
cnfTopFlowsMatchDstPortLo port
match destination port max port
cnfTopFlowsMatchDstPortHi port
match source as as-number
cnfTopFlowsMatchSrcAS as-number
match destination as as-number
cnfTopFlowsMatchDstAS as-number
match input-interface interface
cnfTopFlowsMatchInputIf interface
match output-interface interface
cnfTopFlowsMatchOutputIf interface
match tos [tos-value | dscp dscp-value | precedence precedence-value]
cnfTopFlowsMatchTOSByte tos-value2
match protocol [protocol-number | tcp | udp]
cnfTopFlowsMatchProtocol protocol-number
match flow-sampler flow-sampler-name
cnfTopFlowsMatchSampler flow-sampler-name
match class-map class
cnfTopFlowsMatchClass class
match packet-range min minimum-range
cnfTopFlowsMatchMinPackets minimum-range
match packet-range max maximum-range
cnfTopFlowsMatchMaxPackets maximum-range
match byte-range min minimum-range
cnfTopFlowsMatchMinBytes minimum-range
match byte-range max maximum-range
cnfTopFlowsMatchMaxPackets maximum-range
1 The only IP version type that is currently supported is IPv4 (type 1).
2 tos-value is 6 bits for DSCP, 3 bits for precedence, and 8 bits (one byte) for ToS.
Examples
The following example enters NetFlow top talkers configuration mode and specifies that the top talkers will contain the following characteristics:
•
•
Router(config)# ip flow-top-talkersRouter(config-flow-top-talkers)# match source address 10.1.1.17/28Router(config-flow-top-talkers)# match destination as 64512Related Commands
precedence (Frame Relay VC-bundle-member)
To configure the precedence levels for a Frame Relay permanent virtual circuit (PVC) bundle member, use the precedence command in Frame Relay VC-bundle-member configuration mode. To remove the precedence level configuration from the PVC, use the no form of this command.
precedence {level | other}
no precedence
Syntax Description
Defaults
Precedence levels are not configured.
Command Modes
Frame Relay VC-bundle-member configuration
Command History
12.2(13)T
This command was introduced.
12.2(28)SB
This command was integrated into Cisco IOS Release 12.2(28)SB.
Usage Guidelines
Assignment of precedence levels to PVC bundle members allows you to create differentiated service because you can distribute the IP precedence levels over the various PVC bundle members. You can map a single precedence level or a range of levels to each discrete PVC in the bundle, thereby enabling PVCs in the bundle to carry packets marked with different precedence levels. Use the precedence other command to indicate that a PVC can carry traffic marked with precedence levels not specifically configured for other PVCs. Only one PVC in the bundle can be configured using the precedence other command.
This command is available only when the match type for the PVC bundle is set to precedence using the match precedence command in Frame Relay VC-bundle configuration mode.
You can overwrite the precedence level configuration on a PVC by reentering the precedence command with a new level value.
All precedence levels must be accounted for in the PVC bundle configuration, or the bundle will not come up. Note, however, that a PVC may be a bundle member but have no precedence level associated with it. As long as all valid precedence levels are handled by other PVCs in the bundle, the bundle can come up, but the PVC that has no precedence level configured will not participate in it.
A precedence level can be configured on one PVC bundle member per bundle. If you configure the same precedence level on more than one PVC within a bundle, the following error warning appears on the console:
%Overlapping precedence levelsWhen tag switching is enabled on the interface by using the tag-switching ip command, MPLS and IP packets can flow across the interface, and PVC bundles that are configured for IP precedence mapping are converted to MPLS experimental (EXP) mapping. The PVC bundle functionality remains the same with respect to priority levels, bumping, and so on, but the match precedence command is replaced by "match exp," and each precedence command is replaced by the exp command. The result is that a bundle-member PVC previously configured to carry precedence level 1 IP traffic now carries EXP level 1 MPLS traffic.
When tag switching is disabled, the match precedence and match dscp commands are restored, and the exp commands are replaced by precedence commands.
When tag switching is enabled or disabled, PVC bundles configured for IP precedence mapping or MPLS EXP mapping will stay up, and traffic will be sent over the appropriate bundle-member PVCs.
Examples
The following example configures Frame Relay PVC bundle member 101 to carry traffic with IP precedence level 5:
frame-relay vc-bundle bundle1match precedencepvc 101precedence 5Related Commands
protect (Frame Relay VC-bundle-member)
To configure a Frame Relay protected permanent virtual circuit (PVC) bundle member with protected group or protected PVC status, use the protect command in Frame Relay VC-bundle-member configuration mode. To remove the protected status from the PVC, use the no form of this command.
protect {group | vc}
no protect {group | vc}
Syntax Description
group
Configures the PVC bundle member as part of a collection of protected PVCs within the PVC bundle.
vc
Configures the PVC member as individually protected.
Defaults
The PVC neither belongs to the protected group nor is an individually protected PVC.
Command Modes
Frame Relay VC-bundle-member configuration
Command History
12.2(13)T
This command was introduced.
12.2(28)SB
This command was integrated into Cisco IOS Release 12.2(28)SB.
Usage Guidelines
When an individually protected PVC goes down, it takes the bundle down. When all members of a protected group go down, the bundle goes down.
Despite any protection configurations, the PVC bundle will go down if a downed PVC has no PVC to which to bump its traffic or if the last PVC that is up in a PVC bundle goes down.
Examples
The following example configures Frame Relay PVC bundle member 101 as an individually protected PVC:
frame-relay vc-bundle bundle1pvc 101protect vcRelated Commands
pvc (Frame Relay VC-bundle)
To create a permanent virtual circuit (PVC) that is a Frame Relay PVC bundle member, and to enter Frame Relay VC-bundle-member configuration mode, use the pvc command in Frame Relay VC-bundle configuration mode. To delete the PVC from the Frame Relay PVC bundle, use the no form of this command.
pvc dlci [vc-name]
no pvc dlci [vc-name]
Syntax Description
dlci
Data-link connection identifier (DLCI) number used to identify the PVC.
vc-name
(Optional) An alphanumeric name for the PVC.
Defaults
No PVC is defined.
Command Modes
Frame Relay VC-bundle configuration
Command History
12.2(13)T
This command was introduced.
12.2(28)SB
This command was integrated into Cisco IOS Release 12.2(28)SB.
Usage Guidelines
To use this command, you must first create a Frame Relay PVC bundle and enter Frame Relay VC-bundle configuration mode.
A PVC bundle must have at least one PVC for the bundle to come up. A PVC bundle cannot have more than eight PVCs. If you try to configure more than eight PVCs in a bundle, the following message will appear on the console:
%FR vc-bundle contains 8 members. Cannot add another.Dynamic PVCs can be specified as PVC bundle members; however, if a PVC has already been created by using some other configuration command, you will not be able to add it to a PVC bundle. If you try to add it to a bundle, the following message will appear on the console:
%DLCI 200 is not a dynamic PVC. Cannot add to VC-Bundle.If a PVC is already a member of a PVC bundle, any attempt to reuse that same PVC in a command that creates a PVC (for example, frame-relay interface-dlci, frame-relay local-dlci) will result in the following error message:
%Command is inapplicable to vc-bundle PVCs.Examples
The following example creates PVC 101 belonging to the Frame Relay PVC bundle named "bundle1":
frame-relay vc-bundle bundle1pvc 101Related Commands
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
Command Modes
User EXEC
Privileged EXECCommand History
Examples
The following is sample output from the show frame-relay ip rtp header-compression command:
Router# show frame-relay ip rtp header-compressionDLCI 17 Link/Destination info: ip 10.1.1.1Interface Serial0:Rcvd: 0 total, 0 compressed, 0 errors0 dropped, 0 buffer copies, 0 buffer failuresSent: 6000 total, 5998 compressed,227922 bytes saved, 251918 bytes sent1.90 efficiency improvement factorConnect: 16 rx slots, 16 tx slots, 2 long searches, 2 misses99% hit ratio, five minute miss rate 0 misses/sec, 0 maxDLCI 21 Link/Destination info: ip 10.1.4.1Interface Serial 3/0 DLCI 21 (compression on, Cisco)Rcvd: 0 total, 0 compressed, 0 errors, 0 status msgs0 dropped, 0 buffer copies, 0 buffer failuresSent: 0 total, 0 compressed, 0 status msgs, 0 not predicted0 bytes saved, 0 bytes sentConnect: 256 rx slots, 256 tx slots,0 misses, 0 collisions, 0 negative cache hits, 256 free contextsDLCI 20 Link/Destination info: ip 10.1.1.1Interface Serial 3/1 DLCI 20 (compression on, Cisco)Rcvd: 0 total, 0 compressed, 0 errors, 0 status msgs0 dropped, 0 buffer copies, 0 buffer failuresSent: 0 total, 0 compressed, 0 status msgs, 0 not predicted0 bytes saved, 0 bytes sentConnect: 256 rx slots, 256 tx slots,0 misses, 0 collisions, 0 negative cache hits, 256 free contextsDLCI 21 Link/Destination info: ip 10.1.2.1Interface Serial 3/1 DLCI 21 (compression on, Cisco)Rcvd: 0 total, 0 compressed, 0 errors, 0 status msgs0 dropped, 0 buffer copies, 0 buffer failuresSent: 0 total, 0 compressed, 0 status msgs, 0 not predicted0 bytes saved, 0 bytes sentConnect: 256 rx slots, 256 tx slots,0 misses, 0 collisions, 0 negative cache hits, 256 free contextsDLCI 22 Link/Destination info: ip 10.1.3.1Interface Serial 3/1 DLCI 22 (compression on, Cisco)Rcvd: 0 total, 0 compressed, 0 errors, 0 status msgs0 dropped, 0 buffer copies, 0 buffer failuresSent: 0 total, 0 compressed, 0 status msgs, 0 not predicted0 bytes saved, 0 bytes sentConnect: 256 rx slots, 256 tx slots,0 misses, 0 collisions, 0 negative cache hits, 256 free contextsIn 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 21DLCI 21 Link/Destination info: ip 10.1.4.1Interface Serial 3/0 DLCI 21 (compression on, Cisco)Rcvd: 0 total, 0 compressed, 0 errors, 0 status msgs0 dropped, 0 buffer copies, 0 buffer failuresSent: 0 total, 0 compressed, 0 status msgs, 0 not predicted0 bytes saved, 0 bytes sentConnect: 256 rx slots, 256 tx slots,0 misses, 0 collisions, 0 negative cache hits, 256 free contextsDLCI 21 Link/Destination info: ip 10.1.2.1Interface Serial 3/1 DLCI 21 (compression on, Cisco)Rcvd: 0 total, 0 compressed, 0 errors, 0 status msgs0 dropped, 0 buffer copies, 0 buffer failuresSent: 0 total, 0 compressed, 0 status msgs, 0 not predicted0 bytes saved, 0 bytes sentConnect: 256 rx slots, 256 tx slots,0 misses, 0 collisions, 0 negative cache hits, 256 free contextsIn 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 serial 3/1DLCI 20 Link/Destination info: ip 10.1.1.1Interface Serial 3/1 DLCI 20 (compression on, Cisco)Rcvd: 0 total, 0 compressed, 0 errors, 0 status msgs0 dropped, 0 buffer copies, 0 buffer failuresSent: 0 total, 0 compressed, 0 status msgs, 0 not predicted0 bytes saved, 0 bytes sentConnect: 256 rx slots, 256 tx slots,0 misses, 0 collisions, 0 negative cache hits, 256 free contextsDLCI 21 Link/Destination info: ip 10.1.2.1Interface Serial 3/1 DLCI 21 (compression on, Cisco)Rcvd: 0 total, 0 compressed, 0 errors, 0 status msgs0 dropped, 0 buffer copies, 0 buffer failuresSent: 0 total, 0 compressed, 0 status msgs, 0 not predicted0 bytes saved, 0 bytes sentConnect: 256 rx slots, 256 tx slots,0 misses, 0 collisions, 0 negative cache hits, 256 free contextsDLCI 22 Link/Destination info: ip 10.1.3.1Interface Serial 3/1 DLCI 22 (compression on, Cisco)Rcvd: 0 total, 0 compressed, 0 errors, 0 status msgs0 dropped, 0 buffer copies, 0 buffer failuresSent: 0 total, 0 compressed, 0 status msgs, 0 not predicted0 bytes saved, 0 bytes sentConnect: 256 rx slots, 256 tx slots,0 misses, 0 collisions, 0 negative cache hits, 256 free contextsIn the following example, the show frame-relay ip rtp header-compression command displays information for only DLCI 21 on serial interface 3/1:
Router# show frame-relay ip rtp header-compression interface serial 3/1 21DLCI 21 Link/Destination info: ip 10.1.2.1Interface Serial 3/1 DLCI 21 (compression on, Cisco)Rcvd: 0 total, 0 compressed, 0 errors, 0 status msgs0 dropped, 0 buffer copies, 0 buffer failuresSent: 0 total, 0 compressed, 0 status msgs, 0 not predicted0 bytes saved, 0 bytes sentConnect: 256 rx slots, 256 tx slots,0 misses, 0 collisions, 0 negative cache hits, 256 free contextsThe 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 Serial 1/4vc-bundle MP-3-static Link/Destination info:ip 10.1.1.1Interface Serial 1/4:Rcvd: 14 total, 13 compressed, 0 errors0 dropped, 0 buffer copies, 0 buffer failuresSent: 15 total, 14 compressed,474 bytes saved, 119 bytes sent4.98 efficiency improvement factorConnect:256 rx slots, 256 tx slots,1 long searches, 1 misses 0 collisions, 0 negative cache hits93% hit ratio, five minute miss rate 0 misses/sec, 0 maxTable 2 describes the significant fields shown in the display.
Related Commands
show frame-relay ip tcp header-compression
To display Frame Relay TCP/IP header compression information, 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
Command Modes
User EXEC
Privileged EXECCommand History
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.200Interface Serial0:Rcvd: 40 total, 36 compressed, 0 errors0 dropped, 0 buffer copies, 0 buffer failuresSent: 0 total, 0 compressed0 bytes saved, 0 bytes sentConnect: 16 rx slots, 16 tx slots, 0 long searches, 0 misses, 0% hit ratioFive minute miss rate 0 misses/sec, 0 max misses/secThe 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 tcp header-compression interface Serial 1/4
vc-bundle MP-3-static Link/Destination info:ip 10.1.1.1Interface Serial1/4:Rcvd: 14 total, 13 compressed, 0 errors0 dropped, 0 buffer copies, 0 buffer failuresSent: 15 total, 14 compressed,474 bytes saved, 119 bytes sent4.98 efficiency improvement factorConnect:256 rx slots, 256 tx slots,1 long searches, 1 misses 0 collisions, 0 negative cache hits93% hit ratio, five minute miss rate 0 misses/sec, 0 maxIn 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.1Interface POS2/0 DLCI 21 (compression on, VJ)Rcvd: 0 total, 0 compressed, 0 errors, 0 status msgs0 dropped, 0 buffer copies, 0 buffer failuresSent: 0 total, 0 compressed, 0 status msgs, 0 not predicted0 bytes saved, 0 bytes sentConnect: 256 rx slots, 256 tx slots,0 misses, 0 collisions, 0 negative cache hits, 256 free contextsDLCI 21 Link/Destination info: ip 10.1.4.1Interface Serial3/0 DLCI 21 (compression on, VJ)Rcvd: 0 total, 0 compressed, 0 errors, 0 status msgs0 dropped, 0 buffer copies, 0 buffer failuresSent: 0 total, 0 compressed, 0 status msgs, 0 not predicted0 bytes saved, 0 bytes sentConnect: 256 rx slots, 256 tx slots,0 misses, 0 collisions, 0 negative cache hits, 256 free contextsThe 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 pos 2/0 21DLCI 21 Link/Destination info: ip 10.1.2.1Interface POS2/0 DLCI 21 (compression on, VJ)Rcvd: 0 total, 0 compressed, 0 errors, 0 status msgs0 dropped, 0 buffer copies, 0 buffer failuresSent: 0 total, 0 compressed, 0 status msgs, 0 not predicted0 bytes saved, 0 bytes sentConnect: 256 rx slots, 256 tx slots,0 misses, 0 collisions, 0 negative cache hits, 256 free contextsTable 3 describes the significant fields shown in the display.
show frame-relay map
To display current Frame Relay map entries and information about connections, use the show frame-relay map command in privileged EXEC mode.
show frame-relay map [interface type number] [dlci]
Syntax Description
Command Modes
Privileged EXEC
Command History
Examples
This section contains the following examples:
•
•
•
•
•
•
Sample Router Configuration
This configuration example corresponds to the following examples of output for the show frame-relay map command:
interface POS2/0no ip addressencapsulation frame-relayframe-relay map ip 10.1.1.1 20 tcp header-compressionframe-relay map ip 10.1.2.1 21 tcp header-compressionframe-relay map ip 10.1.3.1 22 tcp header-compressionframe-relay map bridge 23frame-relay interface-dlci 25frame-relay interface-dlci 26bridge-group 1interface POS2/0.1 point-to-pointframe-relay interface-dlci 24 protocol ip 10.1.4.1interface Serial3/0no ip addressencapsulation frame-relayserial restart-delay 0frame-relay map ip 172.16.3.1 20frame-relay map ip 172.16.4.1 21 tcp header-compression activeframe-relay map ip 172.16.1.1 100frame-relay map ip 172.16.2.1 101interface Serial3/0.1 multipointframe-relay map ip 192.168.11.11 24frame-relay map ip 192.168.11.22 105Display All Maps: Example
Router# show frame-relay mapPOS2/0 (up): ip 10.1.1.1 dlci 20(0x14,0x440), static,CISCO, status deletedTCP/IP Header Compression (enabled), connections: 256POS2/0 (up): ip 10.1.2.1 dlci 21(0x15,0x450), static,CISCO, status deletedTCP/IP Header Compression (enabled), connections: 256POS2/0 (up): ip 10.1.3.1 dlci 22(0x16,0x460), static,CISCO, status deletedTCP/IP Header Compression (enabled), connections: 256POS2/0 (up): bridge dlci 23(0x17,0x470), static,CISCO, status deletedPOS2/0.1 (down): point-to-point dlci, dlci 24(0x18,0x480), broadcaststatus deletedSerial3/0 (down): ip 172.16.3.1 dlci 20(0x14,0x440), static,CISCO, status deletedSerial3/0 (down): ip 172.16.4.1 dlci 21(0x15,0x450), static,CISCO, status deletedTCP/IP Header Compression (enabled), connections: 256Serial3/0.1 (down): ip 192.168.11.11 dlci 24(0x18,0x480), static,CISCO, status deletedSerial3/0 (down): ip 172.16.1.1 dlci 100(0x64,0x1840), static,CISCO, status deletedSerial3/0 (down): ip 172.16.2.1 dlci 101(0x65,0x1850), static,CISCO, status deletedSerial3/0.1 (down): ip 192.168.11.22 dlci 105(0x69,0x1890), static,CISCO, status deletedSerial4/0/1:0.1 (up): point-to-point dlci, dlci 102(0x66,0x1860), broadcast, CISCOstatus defined, active,RTP Header Compression (enabled), connections: 256Display Maps for a Specific DLCI: Example
Router# show frame-relay map 20POS2/0 (up): ip 10.1.1.1 dlci 20(0x14,0x440), static,CISCO, status deletedTCP/IP Header Compression (enabled), connections: 256Serial3/0 (down): ip 172.16.3.1 dlci 20(0x14,0x440), static,CISCO, status deletedDisplay Maps for a Specific Interface: Example
Router# show frame-relay map interface pos 2/0POS2/0 (up): ip 10.1.1.1 dlci 20(0x14,0x440), static,CISCO, status deletedTCP/IP Header Compression (enabled), connections: 256POS2/0 (up): ip 10.1.2.1 dlci 21(0x15,0x450), static,CISCO, status deletedTCP/IP Header Compression (enabled), connections: 256POS2/0 (up): ip 10.1.3.1 dlci 22(0x16,0x460), static,CISCO, status deletedTCP/IP Header Compression (enabled), connections: 256POS2/0 (up): bridge dlci 23(0x17,0x470), static,CISCO, status deletedPOS2/0.1 (down): point-to-point dlci, dlci 24(0x18,0x480), broadcaststatus deletedDisplay Map for a Specific DLCI on a Specific Interface: Example
Router# show frame-relay map interface pos 2/0 20POS2/0 (up): ip 10.1.1.1 dlci 20(0x14,0x440), static,CISCO, status deletedTCP/IP Header Compression (enabled), connections: 256Display Maps for a Specific Subinterface: Example
Router# show frame-relay map interface pos 2/0.1POS2/0.1 (down): point-to-point dlci, dlci 24(0x18,0x480), broadcaststatus deletedDisplay Maps for a Specific DLCI on a Specific Subinterface: Example
Router# show frame-relay map interface pos 2/0.1 24POS2/0.1 (down): point-to-point dlci, dlci 24(0x18,0x480), broadcaststatus deletedMaps with IPV6 Addresses: Example
The following sample output from the show frame-relay map command shows that the link-local and global IPv6 addresses (FE80::E0:F727:E400:A and 3ffe:1111:2222:1044::73; FE80::60:3E47:AC8:8 and 3ffe:1111:2222:1044::72) of two remote nodes are explicitly mapped to data-link connection identifier (DLCI) 17 and DLCI 19, respectively. Both DLCI 17 and DLCI 19 are terminated on interface serial 3 of this node; therefore, interface serial 3 of this node is a point-to-multipoint interface.
Router# show frame-relay map
Serial3 (up): ipv6 FE80::E0:F727:E400:A dlci 17(0x11,0x410), static,broadcast, CISCO, status defined, activeSerial3 (up): ipv6 3ffe:1111:2222:1044::72 dlci 19(0x13,0x430), static,CISCO, status defined, activeSerial3 (up): ipv6 3ffe:1111:2222:1044::73 dlci 17(0x11,0x410), static,CISCO, status defined, activeSerial3 (up): ipv6 FE80::60:3E47:AC8:8 dlci 19(0x13,0x430), static,broadcast, CISCO, status defined, activeMaps for VC Bundles: Example
The following sample output displays mapping information for two PVC bundles. The PVC bundle "MAIN-1-static" is configured with a static map. The map for PVC bundle "MAIN-2-dynamic" is created dynamically using Inverse Address Resolution Protocol (ARP).
Router# show frame-relay map
Serial1/4 (up): ip 10.1.1.1 vc-bundle MAIN-1-static, static,CISCO, status upSerial1/4 (up): ip 10.1.1.2 vc-bundle MAIN-2-dynamic, dynamic,broadcast, status upTable 4 describes the significant fields shown in the displays.
Related Commands
show frame-relay pvc
To display statistics about Frame Relay permanent virtual circuits (PVCs), use the show frame-relay pvc command in privileged EXEC mode.
show frame-relay pvc [[interface interface] [dlci] [64-bit] | summary [all]]
Syntax Description
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Use this command to monitor the PPP link control protocol (LCP) state as being open with an up state or closed with a down state.
When the vofr command or the vofr with the cisco keyword has been configured on the PVC, and a voice bandwidth has been allocated to the class associated with this PVC, configured voice bandwidth and used voice bandwidth are also displayed.
Statistics Reporting
To obtain statistics about PVCs on all Frame Relay interfaces, use this command with no arguments.
To obtain statistics about a PVC that include policy-map configuration or the priority configured for that PVC, use this command with the dlci argument.
To display a summary of all PVCs on the system, use the show frame-relay pvc command with the summary keyword. To display a summary of all PVCs per interface, use the summary all keywords.
Per-VC counters are not incremented at all when either autonomous or silicon switching engine (SSE) switching is configured; therefore, PVC values will be inaccurate if either switching method is used.
You can change the period of time over which a set of data is used for computing load statistics. If you decrease the load interval, the average statistics are computed over a shorter period of time and are more responsive to bursts of traffic. To change the length of time for which a set of data is used to compute load statistics for a PVC, use the load-interval command in Frame-Relay DLCI configuration mode.
Traffic Shaping
Congestion control mechanisms are currently not supported on terminated PVCs nor on PVCs over ISDN. Where congestion control mechanisms are supported, the switch passes forward explicit congestion notification (FECN) bits, backward explicit congestion notification (BECN) bits, and discard eligible (DE) bits unchanged from entry points to exit points in the network.
Examples
The various displays in this section show sample output for a variety of PVCs. Some of the PVCs carry data only; some carry a combination of voice and data. This section contains the following examples:
•
•
•
•
•
•
•
•
•
•
•
•
•
•
Summary of Frame Relay PVCs Example
The following example shows sample output from the show frame-relay pvc command with the summary keyword. The summary keyword displays all PVCs on the system.
Router# show frame-relay pvc summaryFrame-Relay VC SummaryActive Inactive Deleted StaticLocal 0 12 0 0Switched 0 0 0 0Unused 0 0 0 0The following example shows sample output from the show frame-relay pvc command with the summary and all keywords. The summary and all keywords display all PVCs per interface.
Router# show frame-relay pvc summary allVC Summary for interface Serial3/0 (Frame Relay DTE)Active Inactive Deleted StaticLocal 0 7 0 0Switched 0 0 0 0Unused 0 0 0 0VC Summary for interface Serial3/1 (Frame Relay DTE)Active Inactive Deleted StaticLocal 0 5 0 0Switched 0 0 0 0Unused 0 0 0 0Frame Relay Generic Configuration Example
The following sample output shows a generic Frame Relay configuration on DLCI 100:
Router# show frame-relay pvc 100
PVC Statistics for interface Serial4/0/1:0 (Frame Relay DTE)DLCI = 100, DLCI USAGE = LOCAL, PVC STATUS = ACTIVE (EEK UP), INTERFACE = Serial4/0/1:0.1input pkts 4360 output pkts 4361 in bytes 146364out bytes 130252 dropped pkts 3735 in pkts dropped 0out pkts dropped 3735 out bytes dropped 1919790late-dropped out pkts 3735 late-dropped out bytes 1919790in FECN pkts 0 in BECN pkts 0 out FECN pkts 0out BECN pkts 0 in DE pkts 0 out DE pkts 0out bcast pkts 337 out bcast bytes 1020845 minute input rate 0 bits/sec, 0 packets/sec5 minute output rate 0 bits/sec, 0 packets/secpvc create time 05:34:06, last time pvc status changed 05:33:38Frame Relay Voice-Adaptive Fragmentation Example
The following sample output indicates that Frame Relay voice-adaptive fragmentation is active on DLCI 202 and there are 29 seconds left on the deactivation timer. If no voice packets are detected in the next 29 seconds, Frame Relay voice-adaptive fragmentation will become inactive.
Router# show frame-relay pvc 202
PVC Statistics for interface Serial3/1 (Frame Relay DTE)DLCI = 202, DLCI USAGE = LOCAL, PVC STATUS = STATIC, INTERFACE = Serial3/1.2input pkts 0 output pkts 479 in bytes 0out bytes 51226 dropped pkts 0 in pkts dropped 0out pkts dropped 0 out bytes dropped 0in FECN pkts 0 in BECN pkts 0 out FECN pkts 0out BECN pkts 0 in DE pkts 0 out DE pkts 0out bcast pkts 0 out bcast bytes 05 minute input rate 0 bits/sec, 0 packets/sec5 minute output rate 5000 bits/sec, 5 packets/secpvc create time 00:23:36, last time pvc status changed 00:23:31fragment type end-to-end fragment size 80 adaptive active, time left 29 secsFrame Relay PVC Bundle Example
The following sample output indicates that PVC 202 is a member of VC bundle MAIN-1-static:
Router# show frame-relay pvc 202
PVC Statistics for interface Serial1/4 (Frame Relay DTE)DLCI = 202, DLCI USAGE = LOCAL, PVC STATUS = STATIC, INTERFACE = Serial1/4input pkts 0 output pkts 45 in bytes 0out bytes 45000 dropped pkts 0 in FECN pkts 0in BECN pkts 0 out FECN pkts 0 out BECN pkts 0in DE pkts 0 out DE pkts 0out bcast pkts 0 out bcast bytes 05 minute input rate 0 bits/sec, 0 packets/sec5 minute output rate 2000 bits/sec, 2 packets/secpvc create time 00:01:25, last time pvc status changed 00:01:11VC-Bundle MAIN-1-staticFrame Relay 64-Bit Counter Example
The following sample output displays the Frame Relay 64-bit counters:
Router# show frame-relay pvc 35 64-bit
DLCI = 35, INTERFACE = Serial0/0input pkts 0 output pkts 0in bytes 0 out bytes 0Frame Relay Fragmentation and Hardware Compression Example
The following is sample output from the show frame-relay pvc command for a PVC configured with Cisco-proprietary fragmentation and hardware compression:
Router# show frame-relay pvc 110
PVC Statistics for interface Serial0/0 (Frame Relay DTE)DLCI = 110, DLCI USAGE = LOCAL, PVC STATUS = STATIC, INTERFACE = Serial0/0input pkts 409 output pkts 409 in bytes 3752out bytes 4560 dropped pkts 1 in FECN pkts 0in BECN pkts 0 out FECN pkts 0 out BECN pkts 0in DE pkts 0 out DE pkts 0out bcast pkts 0 out bcast bytes 0pvc create time 3d00h, last time pvc status changed 2d22hService type VoFR-ciscoVoice Queueing Stats: 0/100/0 (size/max/dropped)Post h/w compression queue: 0Current fair queue configuration:Discard Dynamic Reservedthreshold queue count queue count64 16 2Output queue size 0/max total 600/drops 0configured voice bandwidth 16000, used voice bandwidth 0fragment type VoFR-cisco fragment size 100cir 64000 bc 640 be 0 limit 80 interval 10mincir 32000 byte increment 80 BECN response nofrags 428 bytes 4810 frags delayed 24 bytes delayed 770shaping inactivetraffic shaping drops 0ip rtp priority parameters 16000 32000 20000Switched PVC Example
The following is sample output from the show frame-relay pvc command for a switched Frame Relay PVC. This output displays detailed information about Network-to-Network Interface (NNI) status and why packets were dropped from switched PVCs.
Router# show frame-relay pvc
PVC Statistics for interface Serial2/2 (Frame Relay NNI)DLCI = 16, DLCI USAGE = SWITCHED, PVC STATUS = INACTIVE, INTERFACE = Serial2/2LOCAL PVC STATUS = INACTIVE, NNI PVC STATUS = INACTIVEinput pkts 0 output pkts 0 in bytes 0out bytes 0 dropped pkts 0 in FECN pkts 0in BECN pkts 0 out FECN pkts 0 out BECN pkts 0in DE pkts 0 out DE pkts 0out bcast pkts 0 out bcast bytes 0switched pkts0Detailed packet drop counters:no out intf 0 out intf down 0 no out PVC 0in PVC down 0 out PVC down 0 pkt too big 0shaping Q full 0 pkt above DE 0 policing drop 0pvc create time 00:00:07, last time pvc status changed 00:00:07Frame Relay Congestion Management on a Switched PVC Example
The following is sample output from the show frame-relay pvc command that shows the statistics for a switched PVC on which Frame Relay congestion management is configured:
Router# show frame-relay pvc 200
PVC Statistics for interface Serial3/0 (Frame Relay DTE)DLCI = 200, DLCI USAGE = SWITCHED, PVC STATUS = ACTIVE, INTERFACE = Serial3/0input pkts 341 output pkts 390 in bytes 341000out bytes 390000 dropped pkts 0 in FECN pkts 0in BECN pkts 0 out FECN pkts 0 out BECN pkts 0in DE pkts 0 out DE pkts 390out bcast pkts 0 out bcast bytes 0 Num Pkts Switched 341pvc create time 00:10:35, last time pvc status changed 00:10:06Congestion DE threshold 50shaping activecir 56000 bc 7000 be 0 byte limit 875 interval 125mincir 28000 byte increment 875 BECN response nopkts 346 bytes 346000 pkts delayed 339 bytes delayed 339000traffic shaping drops 0Queueing strategy:fifoOutput queue 48/100, 0 drop, 339 dequeuedFrame Relay Policing on a Switched PVC Example
The following is sample output from the show frame-relay pvc command that shows the statistics for a switched PVC on which Frame Relay policing is configured:
Router# show frame-relay pvc 100
PVC Statistics for interface Serial1/0 (Frame Relay DCE)DLCI = 100, DLCI USAGE = SWITCHED, PVC STATUS = ACTIVE, INTERFACE = Serial1/0input pkts 1260 output pkts 0 in bytes 1260000out bytes 0 dropped pkts 0 in FECN pkts 0in BECN pkts 0 out FECN pkts 0 out BECN pkts 0in DE pkts 0 out DE pkts 0out bcast pkts 0 out bcast bytes 0 Num Pkts Switched 1260pvc create time 00:03:57, last time pvc status changed 00:03:19policing enabled, 180 pkts marked DEpolicing Bc 6000 policing Be 6000 policing Tc 125 (msec)in Bc pkts 1080 in Be pkts 180 in xs pkts 0in Bc bytes 1080000 in Be bytes 180000 in xs bytes 0Frame Relay PVC Priority Queueing Example
The following is sample output for a PVC that has been assigned high priority:
Router# show frame-relay pvc 100
PVC Statistics for interface Serial0 (Frame Relay DTE)DLCI = 100, DLCI USAGE = LOCAL, PVC STATUS = ACTIVE, INTERFACE = Serial0input pkts 0 output pkts 0 in bytes 0out bytes 0 dropped pkts 0 in FECN pkts 0in BECN pkts 0 out FECN pkts 0 out BECN pkts 0in DE pkts 0 out DE pkts 0out bcast pkts 0 out bcast bytes 0pvc create time 00:00:59, last time pvc status changed 00:00:33priority highLow Latency Queueing for Frame Relay Example
The following is sample output from the show frame-relay pvc command for a PVC shaped to a 64000 bits per second committed information rate (CIR) with fragmentation. A policy map is attached to the PVC and is configured with a priority class for voice, two data classes for IP precedence traffic, and a default class for best-effort traffic. Weighted Random Early Detection (WRED) is used as the drop policy on one of the data classes.
Router# show frame-relay pvc 100
PVC Statistics for interface Serial1/0 (Frame Relay DTE)DLCI = 100, DLCI USAGE = LOCAL, PVC STATUS = INACTIVE, INTERFACE = Serial1/0.1input pkts 0 output pkts 0 in bytes 0out bytes 0 dropped pkts 0 in FECN pkts 0in BECN pkts 0 out FECN pkts 0 out BECN pkts 0in DE pkts 0 out DE pkts 0out bcast pkts 0 out bcast bytes 0pvc create time 00:00:42, last time pvc status changed 00:00:42service policy mypolicyClass voiceWeighted Fair QueueingStrict PriorityOutput Queue: Conversation 72Bandwidth 16 (kbps) Packets Matched 0(pkts discards/bytes discards) 0/0Class immediate-dataWeighted Fair QueueingOutput Queue: Conversation 73Bandwidth 60 (%) Packets Matched 0(pkts discards/bytes discards/tail drops) 0/0/0mean queue depth: 0drops: class random tail min-th max-th mark-prob0 0 0 64 128 1/101 0 0 71 128 1/102 0 0 78 128 1/103 0 0 85 128 1/104 0 0 92 128 1/105 0 0 99 128 1/106 0 0 106 128 1/107 0 0 113 128 1/10rsvp 0 0 120 128 1/10Class priority-dataWeighted Fair QueueingOutput Queue: Conversation 74Bandwidth 40 (%) Packets Matched 0 Max Threshold 64 (packets)(pkts discards/bytes discards/tail drops) 0/0/0Class class-defaultWeighted Fair QueueingFlow Based Fair QueueingMaximum Number of Hashed Queues 64 Max Threshold 20 (packets)Output queue size 0/max total 600/drops 0fragment type end-to-end fragment size 50cir 64000 bc 640 be 0 limit 80 interval 10mincir 64000 byte increment 80 BECN response nofrags 0 bytes 0 frags delayed 0 bytes delayed 0shaping inactivetraffic shaping drops 0PPP over Frame Relay Example
The following is sample output from the show frame-relay pvc command that shows the PVC statistics for serial interface 5 (slot 1 and DLCI 55 are up) during a PPP session over Frame Relay:
Router# show frame-relay pvc 55
PVC Statistics for interface Serial5/1 (Frame Relay DTE)DLCI = 55, DLCI USAGE = LOCAL, PVC STATUS = ACTIVE, INTERFACE = Serial5/1.1input pkts 9 output pkts 16 in bytes 154out bytes 338 dropped pkts 6 in FECN pkts 0in BECN pkts 0 out FECN pkts 0 out BECN pkts 0in DE pkts 0 out DE pkts 0out bcast pkts 0 out bcast bytes 0pvc create time 00:35:11, last time pvc status changed 00:00:22Bound to Virtual-Access1 (up, cloned from Virtual-Template5)Voice over Frame Relay Example
The following is sample output from the show frame-relay pvc command for a PVC carrying Voice over Frame Relay (VoFR) traffic configured via the vofr cisco command. The frame-relay voice bandwidth command has been configured on the class associated with this PVC, as has fragmentation. The fragmentation type employed is proprietary to Cisco.
A sample configuration for this situation is shown first, followed by the output for the show frame-relay pvc command.
interface serial 0encapsulation frame-relayframe-relay traffic-shapingframe-relay interface-dlci 108vofr ciscoclass vofr-classmap-class frame-relay vofr-classframe-relay fragment 100frame-relay fair-queueframe-relay cir 64000frame-relay voice bandwidth 25000Router# show frame-relay pvc 108
PVC Statistics for interface Serial0 (Frame Relay DTE)DLCI = 108, DLCI USAGE = LOCAL, PVC STATUS = STATIC, INTERFACE = Serial0input pkts 1260 output pkts 1271 in bytes 95671out bytes 98604 dropped pkts 0 in FECN pkts 0in BECN pkts 0 out FECN pkts 0 out BECN pkts 0in DE pkts 0 out DE pkts 0out bcast pkts 1271 out bcast bytes 98604pvc create time 09:43:17, last time pvc status changed 09:43:17Service type VoFR-ciscoconfigured voice bandwidth 25000, used voice bandwidth 0voice reserved queues 24, 25fragment type VoFR-cisco fragment size 100cir 64000 bc 64000 be 0 limit 1000 interval 125mincir 32000 byte increment 1000 BECN response nopkts 2592 bytes 205140 pkts delayed 1296 bytes delayed 102570shaping inactiveshaping drops 0Current fair queue configuration:Discard Dynamic Reservedthreshold queue count queue count64 16 2Output queue size 0/max total 600/drops 0FRF.12 Fragmentation Example
The following is sample output from the show frame-relay pvc command for an application employing pure FRF.12 fragmentation. A sample configuration for this situation is shown first, followed by the output for the show frame-relay pvc command.
interface serial 0encapsulation frame-relayframe-relay traffic-shapingframe-relay interface-dlci 110class fragmap-class frame-relay fragframe-relay fragment 100frame-relay fair-queueframe-relay cir 64000Router# show frame-relay pvc 110
PVC Statistics for interface Serial0 (Frame Relay DTE)DLCI = 110, DLCI USAGE = LOCAL, PVC STATUS = STATIC, INTERFACE = Serial0input pkts 0 output pkts 243 in bytes 0out bytes 7290 dropped pkts 0 in FECN pkts 0in BECN pkts 0 out FECN pkts 0 out BECN pkts 0in DE pkts 0 out DE pkts 0out bcast pkts 243 out bcast bytes 7290pvc create time 04:03:17, last time pvc status changed 04:03:18fragment type end-to-end fragment size 100cir 64000 bc 64000 be 0 limit 1000 interval 125mincir 32000 byte increment 1000 BECN response nopkts 486 bytes 14580 pkts delayed 243 bytes delayed 7290shaping inactiveshaping drops 0Current fair queue configuration:Discard Dynamic Reservedthreshold queue count queue count64 16 2Output queue size 0/max total 600/drops 0Note that when voice is not configured, voice bandwidth output is not displayed.
Multipoint Subinterfaces Transporting Data Example
The following is sample output from the show frame-relay pvc command for multipoint subinterfaces carrying data only. The output displays both the subinterface number and the DLCI. This display is the same whether the PVC is configured for static or dynamic addressing. Note that neither fragmentation nor voice is configured on this PVC.
Router# show frame-relay pvc
DLCI = 300, DLCI USAGE = LOCAL, PVC STATUS = ACTIVE, INTERFACE = Serial0.103input pkts 10 output pkts 7 in bytes 6222out bytes 6034 dropped pkts 0 in FECN pkts 0in BECN pkts 0 out FECN pkts 0 out BECN pkts 0in DE pkts 0 out DE pkts 0outbcast pkts 0 outbcast bytes 0pvc create time 0:13:11 last time pvc status changed 0:11:46DLCI = 400, DLCI USAGE = LOCAL, PVC STATUS = ACTIVE, INTERFACE = Serial0.104input pkts 20 output pkts 8 in bytes 5624out bytes 5222 dropped pkts 0 in FECN pkts 0in BECN pkts 0 out FECN pkts 0 out BECN pkts 0in DE pkts 0 out DE pkts 0outbcast pkts 0 outbcast bytes 0pvc create time 0:03:57 last time pvc status changed 0:03:48PVC Shaping When HQF Is Enabled Example
The following is sample output from the show frame-relay pvc command for a PVC when HQF is enabled:
Router# show frame-relay pvc 16PVC Statistics for interface Serial4/1 (Frame Relay DTE)DLCI = 16, DLCI USAGE = LOCAL, PVC STATUS = ACTIVE, INTERFACE = Serial4/1input pkts 1 output pkts 1 in bytes 34out bytes 34 dropped pkts 0 in pkts dropped 0out pkts dropped 0 out bytes dropped 0in FECN pkts 0 in BECN pkts 0 out FECN pkts 0out BECN pkts 0 in DE pkts 0 out DE pkts 0out bcast pkts 1 out bcast bytes 34pvc create time 00:09:07, last time pvc status changed 00:09:07shaping inactivePVC Transporting Voice and Data Example
The following is sample output from the show frame-relay pvc command for a PVC carrying voice and data traffic, with a special queue specifically for voice traffic created using the frame-relay voice bandwidth command queue keyword:
Router# show frame-relay pvc interface serial 1 45
PVC Statistics for interface Serial1 (Frame Relay DTE)DLCI = 45, DLCI USAGE = LOCAL, PVC STATUS = STATIC, INTERFACE = Serial1input pkts 85 output pkts 289 in bytes 1730out bytes 6580 dropped pkts 11 in FECN pkts 0in BECN pkts 0 out FECN pkts 0 out BECN pkts 0in DE pkts 0 out DE pkts 0out bcast pkts 0 out bcast bytes 0pvc create time 00:02:09, last time pvc status changed 00:02:09Service type VoFRconfigured voice bandwidth 25000, used voice bandwidth 22000fragment type VoFR fragment size 100cir 20000 bc 1000 be 0 limit 125 interval 50mincir 20000 byte increment 125 BECN response nofragments 290 bytes 6613 fragments delayed 1 bytes delayed 33shaping inactivetraffic shaping drops 0Voice Queueing Stats: 0/100/0 (size/max/dropped)~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~Current fair queue configuration:Discard Dynamic Reservedthreshold queue count queue count64 16 2Output queue size 0/max total 600/drops 0Table 5 describes the significant fields shown in the displays.
Table 5 show frame-relay pvc Field Descriptions
DLCI
One of the DLCI numbers for the PVC.
DLCI USAGE
Lists SWITCHED when the router or access server is used as a switch, or LOCAL when the router or access server is used as a DTE device.
PVC STATUS
Status of the PVC: ACTIVE, INACTIVE, or DELETED.
INTERFACE
Specific subinterface associated with this DLCI.
LOCAL PVC STATUS1
Status of PVC configured locally on the NNI interface.
NNI PVC STATUS1
Status of PVC learned over the NNI link.
input pkts
Number of packets received on this PVC.
output pkts
Number of packets sent on this PVC.
in bytes
Number of bytes received on this PVC.
out bytes
Number of bytes sent on this PVC.
dropped pkts
Number of incoming and outgoing packets dropped by the router at the Frame Relay level.
in pkts dropped
Number of incoming packets dropped. Incoming packets may be dropped for a number of reasons, including the following:
•
•
•
•
•
•
out pkts dropped
Number of outgoing packets dropped, including shaping drops and late drops.
out bytes dropped
Number of outgoing bytes dropped.
late-dropped out pkts
Number of outgoing packets dropped because of QoS policy (such as with VC queuing or Frame Relay traffic shaping). This field is not displayed when the value is zero.
late-dropped out bytes
Number of outgoing bytes dropped because of QoS policy (such with as VC queuing or Frame Relay traffic shaping). This field is not displayed when the value is zero.
in FECN pkts
Number of packets received with the FECN bit set.
in BECN pkts
Number of packets received with the BECN bit set.
out FECN pkts
Number of packets sent with the FECN bit set.
out BECN pkts
Number of packets sent with the BECN bit set.
in DE pkts
Number of DE packets received.
out DE pkts
Number of DE packets sent.
out bcast pkts
Number of output broadcast packets.
out bcast bytes
Number of output broadcast bytes.
switched pkts
Number of switched packets.
no out intf2
Number of packets dropped because there is no output interface.
out intf down2
Number of packets dropped because the output interface is down.
no out PVC2
Number of packets dropped because the outgoing PVC is not configured.
in PVC down2
Number of packets dropped because the incoming PVC is inactive.
out PVC down2
Number of packets dropped because the outgoing PVC is inactive.
pkt too big2
Number of packets dropped because the packet size is greater than media MTU3 .
shaping Q full2
Number of packets dropped because the Frame Relay traffic-shaping queue is full.
pkt above DE2
Number of packets dropped because they are above the DE level when Frame Relay congestion management is enabled.
policing drop2
Number of packets dropped because of Frame Relay traffic policing.
pvc create time
Time at which the PVC was created.
last time pvc status changed
Time at which the PVC changed status.
VC-Bundle
PVC bundle of which the PVC is a member.
priority
Priority assigned to the PVC.
pkts marked DE
Number of packets marked DE because they exceeded the Bc.
policing Bc
Committed burst size.
policing Be
Excess burst size.
policing Tc
Measurement interval for counting Bc and Be.
in Bc pkts
Number of packets received within the committed burst.
in Be pkts
Number of packets received within the excess burst.
in xs pkts
Number of packets dropped because they exceeded the combined burst.
in Bc bytes
Number of bytes received within the committed burst.
in Be bytes
Number of bytes received within the excess burst.
in xs bytes
Number of bytes dropped because they exceeded the combined burst.
Congestion DE threshold
PVC queue percentage at which packets with the DE bit are dropped.
Service type
Type of service performed by this PVC. Can be VoFR or VoFR-cisco.
Post h/w compression queue
Number of packets in the post-hardware-compression queue when hardware compression and Frame Relay fragmentation are configured.
configured voice bandwidth
Amount of bandwidth in bits per second (bps) reserved for voice traffic on this PVC.
used voice bandwidth
Amount of bandwidth in bps currently being used for voice traffic.
service policy
Name of the output service policy applied to the VC.
Class
Class of traffic being displayed. Output is displayed for each configured class in the policy.
Output Queue
The WFQ4 conversation to which this class of traffic is allocated.
Bandwidth
Bandwidth in kbps or percentage configured for this class.
Packets Matched
Number of packets that matched this class.
Max Threshold
Maximum queue size for this class when WRED is not used.
pkts discards
Number of packets discarded for this class.
bytes discards
Number of bytes discarded for this class.
tail drops
Number of packets discarded for this class because the queue was full.
mean queue depth
Average queue depth, based on the actual queue depth on the interface and the exponential weighting constant. It is a moving average. The minimum and maximum thresholds are compared against this value to determine drop decisions.
drops:
WRED parameters.
class
IP precedence value.
random
Number of packets randomly dropped when the mean queue depth is between the minimum threshold value and the maximum threshold value for the specified IP precedence value.
tail
Number of packets dropped when the mean queue depth is greater than the maximum threshold value for the specified IP precedence value.
min-th
Minimum WRED threshold in number of packets.
max-th
Maximum WRED threshold in number of packets.
mark-prob
Fraction of packets dropped when the average queue depth is at the maximum threshold.
Maximum Number of Hashed Queues
(Applies to class default only) Number of queues available for unclassified flows.
fragment type
Type of fragmentation configured for this PVC. Possible types are as follows:
•
•
•
fragment size
Size of the fragment payload in bytes.
time left
Number of seconds left on the Frame Relay voice-adaptive fragmentation deactivation timer. When this timer expires, Frame Relay fragmentation turns off.
cir
Current CIR in bps.
bc
Current committed burst (Bc) size, in bits.
be
Current excess burst (Be) size, in bits.
limit
Maximum number of bytes sent per internal interval (excess plus sustained).
interval
Interval being used internally (may be smaller than the interval derived from Bc/CIR; this happens when the router determines that traffic flow will be more stable with a smaller configured interval).
mincir
Minimum CIR for the PVC.
byte increment
Number of bytes that will be sustained per internal interval.
BECN response
Indication that Frame Relay has BECN adaptation configured.
pkts
Number of packets associated with this PVC that have gone through the traffic-shaping system.
frags
Total number of fragments shaped on this VC.
bytes
Number of bytes associated with this PVC that have gone through the traffic-shaping system.
pkts delayed
Number of packets associated with this PVC that have been delayed by the traffic-shaping system.
frags delayed
Number of fragments delayed in the shaping queue before being sent.
bytes delayed
Number of bytes associated with this PVC that have been delayed by the traffic-shaping system.
shaping
Indication that shaping will be active for all PVCs that are fragmenting data; otherwise, shaping will be active if the traffic being sent exceeds the CIR for this circuit.
shaping drops
Number of packets dropped by the traffic-shaping process.
Queueing strategy
Per-VC queueing strategy.
Output queue
48/100
0 drop
300 dequeued
State of the per-VC queue.
•
•
•
Voice Queueing Stats
Statistics showing the size of packets, the maximum number of packets, and the number of packets dropped in the special voice queue created using the frame-relay voice bandwidth command queue keyword.
Output queue size
Size in bytes of each output queue.
max total
Maximum number of packets of all types that can be queued in all queues.
drops
Number of frames dropped by all output queues.
1 The LOCAL PVC STATUS and NNI PVC STATUS fields are displayed only for PVCs configured on Frame Relay NNI interface types. These fields are not displayed if the PVC is configured on DCE or DTE interface types.
2 The detailed packet drop fields are displayed for switched Frame Relay PVCs only. These fields are not displayed for terminated PVCs.
3 MTU = maximum transmission unit.
4 WFQ = weighted fair queueing.
Related Commands
show frame-relay vc-bundle
To display attributes and other information about a Frame Relay permanent virtual circuit (PVC) bundle, use the show frame-relay vc-bundle command in privileged EXEC mode.
show frame-relay vc-bundle vc-bundle-name [detail]
Syntax Description
Command Modes
Privileged EXEC
Command History
12.2(13)T
This command was introduced.
12.2(28)SB
This command was integrated into Cisco IOS Release 12.2(28)SB.
Usage Guidelines
Use this command to display packet service levels, bumping attributes, and other information about a specific Frame Relay PVC bundle. To display packet counts for each PVC in the bundle in addition to the other attributes, use the detail keyword.
Examples
General Example
The following example shows the Frame Relay PVC bundle named "MP-4-dynamic" with PVC protection applied. Note that in this PVC bundle, data-link connection identifier (DLCI) 400 is configured to explicitly bump traffic to the PVC that handles DSCP level 40, which is DLCI 404. All the other DLCIs are configured for implicit bumping. In addition, all the DLCIs are configured to accept bumped traffic.
The asterisk (*) before PVC 4a indicates that this PVC was configured with the precedence command with the other keyword, which means the PVC will handle all levels that are not explicitly configured on other PVCs.
In this example all PVCs are up, so the values in the "Active leve"l fields match the values in the "Config level" fields. If a PVC goes down and its traffic is bumped, the "Active level" field value for the PVC that went down is cleared. The "Active level" field values for the PVC that the traffic bumped to will be updated to include the levels of the PVC that went down.
The first three PVCs in the following example make up a protected group. All three of these PVCs must go down before the bundle will go down. The last two PVCs are protected PVCs; if either of these PVCs goes down, the bundle will go down.
Router# show frame-relay vc-bundle MP-4-dynamic
MP-4-dynamic on Serial1/4.1 - Status: UP Match-type: DSCPName DLCI Config. Active Bumping PG/ CIR Statuslevel level to/accept PV kbps*4a 400 0-9 0-9 40/Yes pg up4b 401 10-19 10-19 9/Yes pg up4c 402 20-29 20-29 19/Yes pg up4d 403 30-39 30-39 29/Yes - up4e 404 40-49 40-49 39/Yes - up4f 405 50-59 50-59 49/Yes - up4g 406 60-62 60-62 59/Yes pv up4h 407 63 63 62/Yes pv upPackets sent out on vc-bundle MP-4-dynamic : 0:Router#Bumping Example
The following example shows that although some DLCIs are down, the bumping rules and the remaining DLCIs keep the bundle up and running for all traffic types.
Note that DLCI 304 is handling the traffic being bumped from the three DLCIs that are down. The "Active level" field indicates the levels that the PVC is actually handling, not just which levels are configured.
Router# show frame-relay vc-bundle MP-3-static
MP-3-static on Serial1/4.1 - Status: UP Match-type: DSCPName DLCI Config. Active Bumping PG/ CIR Statuslevel level to/accept PV kbps3a 300 0-9 0-9 -/Yes - up3b 301 10-19 10-19 9/Yes - up3c 302 20-29 20-29 19/Yes - up3d 303 30-39 40/Yes - deleted3e 304 40-49 30-59,63 39/Yes - up3f 305 50-59 49/Yes - deleted3g 306 60-62 60-62 59/No - up3h 307 63 62/Yes - deletedPackets sent out on vc-bundle MP-3-static : 335Router#Traffic-Shaping Example
The following example shows output for a PVC bundle configured with traffic shaping. The same rules of class inheritance apply to PVC-bundle members as to regular PVCs.
Router# show frame-relay vc-bundle 26k
26k on Serial1/4.1 - Status:UP Match-type:PRECEDENCEName DLCI Config. Active Bumping PG/ CIR Statuslevel level to/ accept PV kbps521 0,2,4 0,2,4 -/Yes - 20 up522 1,3,5-6 1,3,5-6 0/Yes - 26 up523 7 7 6/Yes - 20 upPackets sent out on vc-bundle 26k :0Router#Detail Example
The following example shows the detail output of a PVC bundle. Note in this example that because all packet service levels are not handled, and because the PVCs are currently down, this bundle can never come up.
Router# show frame-relay vc-bundle x41 detail
x41 on Serial1/1 - Status: DOWN Match-type: DSCPName DLCI Config. Active Bumping PG/ CIR Statuslevel level to/accept PV kbps410 50-62 49/Yes - down411 30,32,34,36,3.. 29/Yes - downPackets sent out on vc-bundle x41 : 0Active configuration and statistics for each member PVCDLCI Output pkts Active level410 0 50-62411 0 30,32,34,36,38-40Router#Table 6 describes the significant fields shown in the displays.
Related Commands
Glossary
DLCI—Data-link connection identifier.
DSCP—Differentiated services code point.
PVC—Permanent virtual circuit.
PVC bundle—A set of parallel VCs between two CPEs.
RTP—Real-Time Transport Protocol. Protocol that is designed to provide end-to-end network transport functions for applications transmitting real-time data, such as audio, video, or simulation data, over multicast or unicast network services.
QoS—Quality of service. Generic term for differentiated network services.
ToS—Type of service. A one-byte field in an IP header.
Note
Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. Any examples, command display output, and figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses in illustrative content is unintentional and coincidental.
© 2002-2003, 2005-2006, Cisco Systems, Inc. All rights reserved.
Guest
