Table Of Contents
Versatile Interface Processor-Based Distributed FRF.11 and FRF.12 for Cisco IOS Release 12.1 T
Supported Standards, MIBs, and RFCs
Configuring Dial Peer Digit Manipulation
Disabling Dial Peer Hunting on a Specific Dial Peer
Configuring a Frame Relay Map Class to Support Voice over Frame Relay Fragmentation
Configuring Voice over Frame Relay Connections
Overview of Voice over Frame Relay Connection Types
Configuring Switched Calls (User-Dialed or Auto-Ringdown)
Configuring Switched Calls to Other Voice over Frame Relay Routers
Configuring Switched Calls to a Cisco MC3810 Running Cisco IOS Releases Before 12.1(2)T
Configuring Cisco-Trunk Permanent (Private Line) Calls
Configuring Voice over Frame Relay Dial Peers for Cisco-Trunk (Private Line) Calls
Configuring Cisco-Trunk Permanent Calls
Configuring Cisco-Trunk Permanent Calls to a Cisco MC3810 Running Cisco IOS Releases Before 12.1(2)T
Configuring FRF.11 Trunk (Private Line) Calls
Configuring Connections for Tandem Nodes
Verifying Your Voice Connections
Two Routers Using Frame Relay Fragmentation
Router Using a VoFR PVC to a Cisco MC3810 Running Cisco IOS Releases Before 12.1(2)T
Cisco-Trunk (Private Line) Calls Between Two Routers
FRF.11 Trunk Calls Between Two Routers
Tandem Configuration with Three Routers for Switched Calls
Tandem Configuration with a Cisco MC3810 Tandem Node for Switched Calls
Tandem Configuration with a Cisco MC3810 Endpoint Node for Cisco-Trunk (Private Line) Calls
Cisco-Trunk Call with Hunt Groups
Versatile Interface Processor-Based Distributed FRF.11 and FRF.12 for Cisco IOS Release 12.1 T
Feature Overview
The Voice Over Frame Relay (VoFR) capabilities that were introduced in Cisco IOS Release 11.3 were extended to Cisco 2600, 3600, and 7200 series routers in Cisco IOS Release 12.0(4)T. In Cisco IOS Release 12.1(2)T, the Voice Over Frame Relay Using FRF.11 and FRF.12 feature was updated to standardize the configuration procedures across all platforms. After Cisco IOS Release 12.1(2)T, configuration procedures for the Cisco 2600, 3600, and 7200 series routers and the Cisco MC3810 multiservice access concentrator were nearly identical.
Versatile Interface Processor-Based Distributed FRF.11 and FRF.12 (VIP-Based FRF.11 and FRF.12) is now available in Cisco IOS Release 12.1(5)T. VIP-Based FRF.11 and FRF.12 brings the functionality of the Voice over Frame Relay Using FRF.11 and FRF.12 feature to VIP-enabled Cisco 7500 series routers running Cisco IOS Release 12.1 T.
Because VIP-Based Distributed FRF.11 and FRF.12 was not available in Cisco IOS Release 12.1 T until Cisco IOS Release 12.1(5)T, the configuration procedures for enabling FRF.11 and FRF.12 on the other supported platforms are almost identical to the procedures for enabling VIP-Based FRF.11 and FRF.12 on VIP-enabled Cisco 7500 series routers.
The one major difference between the other platforms and the VIP-enabled Cisco 7500 series router is the difference in map class configuration. The map class configuration procedure for VIP-enabled Cisco 7500 series routers is detailed in the "Configuring a Frame Relay Map Class to Support Voice over Frame Relay Fragmentation" section of this document.
This document describes the configuration procedures for VIP-enabled Cisco 7500 series routers enabling the VIP-Based FRF.11 and FRF.12 feature.
Benefits
Introduces Voice over Frame Relay Using FRF.11 and FRF.12 for VIP-Enabled Cisco 7500
VIP-Based FRF.11 and FRF.12 brings the functionality of the Voice over Frame Relay Using FRF.11 and FRF.12 feature to VIP-enabled Cisco 7500 series routers running Cisco IOS Release 12.1 T.
Restrictions
The following restrictions and limitations apply to the VIP-Based FRF.11 and FRF.12 feature:
•
VIP-Based FRF.12 does not function properly with some of the older port adapters. The following list charts the port adapters that don't function properly with VIP-Based FRF.12 and also recommends updated versions of these port adapters that support VIP-Based FRF.12.
Table 1 Port Adapters that do not Support VIP-Based FRF.12
•
•
•
•
•
•
•
•
•
Related Documents
For complete information about Voice over Frame Relay configuration, see the Cisco IOS Multiservice Applications Configuration Guide for Cisco IOS Release 12.1.
For information about VIP-Based Distributed FRF.11 and FRF.12 in Cisco IOS Release 12.1(1)E, see the Versatile Interface Processor-Based Distributed FRF.11 and FRF.12 feature module that is located in the Cisco IOS Release 12.1(1)E new features documentation index.
For information about Voice over Frame Relay Using FRF.11 and FRF.12 for Cisco 2600, 3600, and 7200 series routers, as well as the Cisco MC3810 concentrator, see the Voice Over Frame Relay Using FRF.11 and FRF.12 feature module on the 12.0(4)T new features documentation index and the Voice Over Frame Relay Using FRF.11 and FRF.12 feature module on the 12.1(2)T new features documentation index. Both of these documents are available online on Cisco Connection Online (CCO).
For more information about voice technologies, refer to the Cisco IOS Multiservice Applications Configuration Guide, and the Cisco IOS Multiservice Command Reference, for
Cisco IOS Release 12.1.Supported Platforms
The VIP-Based FRF.11 and FRF.12 is only available for Cisco 7500 series routers with a Versatile Interface Processor (VIP).
Supported Standards, MIBs, and RFCs
Standards
None
MIBs
None
For descriptions of supported MIBs and how to use MIBs, see the Cisco MIB web site on CCO at http://www.cisco.com/public/sw-center/netmgmt/cmtk/mibs.shtml.
RFCs
None
Prerequisites
Before you can configure a Cisco router to use Voice over Frame Relay, you must do the following:
•
•
•
–
–
After you have analyzed your dial plan and decided how to integrate it into your existing Frame Relay network, you are ready to configure your network devices to support Voice over Frame Relay.
Configuration Tasks
This section describes the following new and modified configuration procedures for Voice over Frame Relay in this release:
•
•
•
•
•
For all remaining Voice over Frame Relay procedures, see the "Configuring Voice over Frame Relay" chapter in Cisco IOS Multiservice Applications Configuration Guide for Cisco IOS Release 12.1.
Configuring Dial Peer Digit Manipulation
To configure dial peer digit manipulation to forward digits, perform the following steps beginning in global configuration mode:
Step 1
Enter dial peer configuration mode for a POTS dial peer.
Step 2
Router(config-dial-peer)# forward-digits {num-digit | all | extra}or
Router(config-dial-peer)# default forward-digitsor
Router(config-dial-peer)# no forward-digitsIf using the forward-digits feature, configure the digit-forwarding method. The range for the number of digits forwarded (num-digit) is 0 through 32.
See the "Command Reference" section for an explanation of the command options.
In the default condition, dialed digits not matching the destination pattern are forwarded.
Note
Configuring Dial Peer Hunting
After you have configured dial peers, you can configure how the router performs dial peer hunting functions. To configure the dial peer hunting behavior on the router, perform the following steps beginning in global configuration mode:
Disabling Dial Peer Hunting on a Specific Dial Peer
If using dial peer hunting, there may be situations when you want to disable dial peer hunting on a specific dial peer. To disable dial peer hunting on a dial peer, use the following commands beginning in global configuration mode:
To reenable dial peer hunting on a dial peer, enter the no huntstop command.
Configuring a Frame Relay Map Class to Support Voice over Frame Relay Fragmentation
To configure a map class to support FRF.11 on a VIP-enabled Cisco 7500 series router, use the following commands to configure a service policy and apply this service policy in map class configuration mode:
Configuring Voice over Frame Relay Connections
After you have configured the Frame Relay data-link connection identifier (DLCI) settings and you have configured your dial plan, you are ready to configure specific VoFR connections.
There are many different scenarios for VoFR connections. For information on the different connection types, see the next section, "Overview of Voice over Frame Relay Connection Types."
For procedures on how to configure the different connection types, see the following sections:
•
•
•
In addition, special consideration is required for configuring calls for tandem nodes. For more information, see the "Configuring Connections for Tandem Nodes" section.
Note
Overview of Voice over Frame Relay Connection Types
When you configure VoFR connections, you can use many different connection types depending on the hardware platform, whether the call is to be a regular switched (user-dialed or auto-ringdown) call, or whether the call is a permanent call (Cisco-trunk or FRF.11-trunk). You configure these specific connection types by using combinations of several commands.
Table 1Table 2 lists the different connection types for VoFR connections supported on the VIP-enabled Cisco 7500 series routers, and the combinations of commands to enter for each call type.
Table 2 Supported Voice over Frame Relay Connection Types
Switched call
(user-dialed or auto-ringdown) to other routers supporting VoFRvofr [data cid]
[call-control [cid]]1FRF.11 Annex C
session protocol cisco-switched2
For user-dialed calls: none
For auto-ringdown calls:
connection plar destination-stringSwitched call
(user-dialed or auto-ringdown)
to a Cisco MC3810 running
Cisco IOS Releases before 12.1(2)Tvofr cisco3
Cisco proprietary4
session protocol cisco-switched
For user-dialed calls: none
For auto-ringdown calls:
connection plar destination-stringCisco-trunk
permanent call (private line) to other routers supporting VoFRvofr data cid
call-control cidFRF.11 Annex C
session protocol cisco-switched
connection trunk destination-string [answer mode]
Cisco-trunk
permanent call
(private line)
to a Cisco MC3810 running
Cisco IOS Releases before 12.1(2)Tvofr cisco
Cisco proprietary
session protocol cisco-switched
connection trunk destination-string [answer mode]
FRF.11 trunk call (private line) to other routers supporting VoFR
vofr [data cid] [call-control cid]5
FRF.11 Annex C
session protocol frf11-trunk
connection trunk destination-string [answer mode]
1 The recommended use of this command is vofr data 4 call-control 5.
2 The session protocol cisco-switched option is the default setting. If you do not enter this command, the setting still applies.
3 This command consumes data CID 4 and call-control CID 5.
4 Cisco proprietary fragmentation is based on an early draft of FRF.12 and is compatible with Cisco MC3810 concentrators running software releases before Cisco IOS Release 12.0(3)XG or Release 12.0(4)T.
5 For FRF.11 trunk calls, the call-control option is not required. It is only required if you mix FRF.11 trunk calls with other types of voice calls on the same PVC.
Configuring Switched Calls (User-Dialed or Auto-Ringdown)
This section describes how to configure switched calls (user-dialed or auto-ringdown) on the different router platforms. This section is divided into the following procedures:
•
•
Configuring Switched Calls to Other Voice over Frame Relay Routers
To configure switched calls on routers that support VoFR, use the following commands from interface configuration mode:
This configuration uses standard FRF.11 Annex C fragmentation.
Configuring Switched Calls to a Cisco MC3810 Running Cisco IOS Releases Before 12.1(2)T
You can configure switched calls to Cisco MC3810 concentrators running Cisco IOS releases before 12.1(2)T. However, the configuration is different from standard switched calls because earlier Cisco MC3810 releases used the Cisco proprietary version of FRF.12.
Note
To configure switched calls to a Cisco MC3810 running Cisco IOS releases before 12.1(2)T, use the following commands beginning in interface configuration mode:
This configuration uses Cisco proprietary data fragmentation.
Configuring Cisco-Trunk Permanent (Private Line) Calls
This section describes how to configure Cisco-trunk permanent (private line) calls on the different router platforms. This section is divided into the following procedures:
•
•
•
Configuring Voice over Frame Relay Dial Peers for Cisco-Trunk (Private Line) Calls
If you are sending Cisco-trunk (private line) calls over the Frame Relay network, you must configure the Voice over Frame Relay dial peers to specifically support Cisco-trunk (private line) calls. Cisco-trunk (private line) calls are permanent calls.
One key task when you configure Cisco-trunk (private line) connections is to configure the signal type for the dial peer. The signal-type dial peer command supports the following options:
•
•
•
•
Configure the signal type so that the signal type that is selected in the dial peers on the routers at both ends of the permanent voice call are the same.
To configure a VoFR dial peer to support Cisco-trunk permanent (private line) calls, use the following commands beginning in global configuration mode:
Configuring Cisco-Trunk Permanent Calls
You can configure Cisco-trunk permanent calls on VIP-enabled Cisco 7500 series routers.
Note
To configure Cisco-trunk permanent calls, use the following commands from interface configuration mode:
This configuration uses standard FRF.11 Annex C fragmentation.
Note
Configuring Cisco-Trunk Permanent Calls to a Cisco MC3810 Running Cisco IOS Releases Before 12.1(2)T
To configure Cisco-trunk permanent calls to a Cisco MC3810 running Cisco IOS releases before 12.1(2)T, use the following commands from interface configuration mode:
This configuration uses Cisco proprietary data fragmentation.
Note
Configuring FRF.11 Trunk (Private Line) Calls
On a VIP-enabled Cisco 7500 series router, you can configure FRF.11 trunk calls to a second router.
You cannot configure FRF.11 trunk calls for tandem VoFR configurations.
Note
To configure FRF.11 trunk (private line) calls, use the following commands from interface configuration mode:
This configuration uses FRF.11 Annex C data fragmentation.
Note
Configuring Connections for Tandem Nodes
Tandeming is switching incoming VoFR calls on a Frame Relay DLCI to an outgoing VoFR enabled DLCI. Tandeming works for switched calls and Cisco-trunk permanent calls only. You cannot tandem FRF.11 trunk calls over a multi-hop network.
Tandeming is supported on all platforms that support Voice over Frame Relay Using FRF.11 and FRF.12, including VIP-enabled Cisco 7500 series routers.
Depending on which router is used as the end node and which router is used as the tandem node, you must use the correct Frame Relay PVC type when configuring your connections. Table 3 shows the different combinations of routers that can serve as end nodes and tandem nodes, and the Frame Relay PVC type required.
When you configure a tandem node, you must configure two VoFR dial peers, one for each tandem connection.
Verifying Your Voice Connections
Verify that the voice connection for switched calls is working by following these steps:
Step 1
Step 2
Verify that the voice connection for FXO-FXS trunk calls from a telephone to a remote PBX is working by doing the following:
Step 1
Step 2
You can check the validity of your dial peer and voice port configurations by performing the following tasks:
•
•
•
You can check the validity of your VoFR configuration on the DLCI by performing the following task:
•
Troubleshooting Tips
If you are having trouble connecting a call, you can try to resolve the problem by performing the following tasks:
•
•
•
•
•
•
•
•
Configuration Examples
This section provides specific configuration examples for different VoFR connections and call type scenarios. This section includes the following examples:
•
•
•
•
•
•
•
•
Note
The examples do not provide complete configurations, but show the required commands to configure Voice over Frame Relay.
For examples of Voice over Frame Relay connections for non-Cisco 7500 series routers, see the Voice Over Frame Relay Using FRF.11 and FRF.12 Configuration Updates document on CCO or the Documentation CD-ROM.
Two Routers Using Frame Relay Fragmentation
Figure 1 shows an example of Frame Relay fragmentation between a Cisco 3600 and a VIP-enabled Cisco 7500 series router. This configuration uses FRF.12 fragmentation.
Figure 1 Two Routers Using Frame Relay Fragmentation
This example assumes that a map class called frf12-class was previously configured.
For information on low latency queueing on the VIP, see the Distributed Low Latency Queueing feature module on CCO. For information on distributed traffic shaping, see the Distributed Traffic Shaping feature module on CCO.
Two Routers Using a VoFR PVC
This example shows an example of Frame Relay fragmentation between a Cisco 7500 series router with a VIP and a Cisco 3600 series router.
Figure 2 .
Two Routers Using a VoFR PVC
This configuration uses FRF.11 Annex C fragmentation.
Router Using a VoFR PVC to a Cisco MC3810 Running Cisco IOS Releases Before 12.1(2)T
Figure 3 shows an example of a Cisco 3600 series router with connections to a Cisco MC3810 running a Cisco IOS Releases before12.1(2)T. In this example, the Voice over Frame Relay interface on both the Cisco 3600 and the Cisco MC3810 is configured by using the vofr cisco command.
Figure 3 Router Using a VoFR PVC to a Cisco MC3810 Running Cisco IOS Releases Before 12.1(2)T
This configuration uses FRF.11 Annex C fragmentation.
Cisco-Trunk (Private Line) Calls Between Two Routers
Figure 4 shows an example of VoFR Cisco-trunk (private line) calls between two routers.
Figure 4 Cisco-Trunk (Private Line) Calls Between Two Routers
FRF.11 Trunk Calls Between Two Routers
Figure 5 shows an example of FRF.11 trunk calls configured between two routers.
Figure 5 FRF.11 Trunk Calls Between Two Routers
Tandem Configuration with Three Routers for Switched Calls
Figure 6 shows an example of a tandem configuration with a Cisco 3600 router and a VIP-enabled Cisco 7500 series router as endpoints and a Cisco 3600 as a tandem node.
Figure 6 Tandem Configuration with Three Routers for Switched Calls
Tandem Configuration with a Cisco MC3810 Tandem Node for Switched Calls
Figure 7 shows an example of a tandem configuration with a Cisco MC3810 acting as a tandem node.
Figure 7 Tandem Configuration with a Cisco MC3810 Tandem Node for Switched Calls
Tandem Configuration with a Cisco MC3810 Endpoint Node for Cisco-Trunk (Private Line) Calls
Figure 8 shows an example of a tandem configuration with a Cisco MC3810 acting as an endpoint node for Cisco-trunk (private line) calls.
Figure 8 Tandem Configuration with a Cisco MC3810 Endpoint Node for Permanent Switched Calls
Cisco-Trunk Call with Hunt Groups
Figure 9 shows an example of a Cisco-trunk (private line) call that is configured with hunt groups. In this example, the two routers are in master-slave mode with a backup path. Router B is configured as a slave and Router A is configured as the master. The master makes periodic attempts to establish the trunk until the trunk is established. Two dial peers match the destination string configured in the voice port, but because one dial peer has a higher preference than the other dial peer, the call setup is attempted through that dial peer. If the call setup fails, the master can continue attempting call setups by using the next available dial peer. After all dial peers are exhausted, the master can continue following the list cyclically by starting again from the dial peer with the highest preference.
Figure 9 Cisco-Trunk (Private Line) Call with Hunt Groups
Command Reference
This section documents new or modified commands. All other commands used with this feature are documented in the Cisco IOS Release 12.1 command reference publications.
The following new and modified commands are described in this section:
Note
frame-relay fragment
To enable fragmentation of Frame Relay frames for a Frame Relay map class, use the frame-relay fragment command. Use the no form of this command to disable Frame Relay fragmentation.
frame-relay fragment fragment_size
no frame-relay fragment
Syntax Description
Defaults
Disabled
Command Modes
Map class configuration
Command History
Usage Guidelines
Frame Relay fragmentation is enabled on a per-PVC basis. Before enabling Frame Relay fragmentation, you must first associate a Frame Relay map class with a specific data link connection identifier (DLCI), then enter map class configuration mode and enable or disable fragmentation for that map class. In addition, you must enable Frame Relay traffic shaping on the interface in order for fragmentation to work.
A Cisco 7500 series router requires a Versatile Interface Processor to utilize this command.
Frame Relay frames are fragmented using one of the following formats, depending on how the PVC is configured:
•
•
•
Cisco recommends pure end-to-end FRF.12 fragmentation on PVCs that are carrying VoIP packets and on PVCs that are sharing the link with other PVCs carrying VoFR traffic.
In pure end-to-end FRF.12 fragmentation, Frame Relay frames with a payload less than the fragment size configured for that PVC are transmitted without the fragmentation header.
FRF.11 Annex C and Cisco proprietary fragmentation are used when VoFR frames are transmitted on a PVC. When fragmentation is enabled on a PVC, FRF.11 Annex C format is triggered when vofr is configured on that PVC; Cisco proprietary format is triggered when vofr cisco is configured.
In FRF.11 Annex C and Cisco proprietary fragmentation, VoFR frames are never fragmented, and all data packets (including VoIP packets) contain the fragmentation header regardless of the payload size.
Examples
The following example shows how to enable pure end-to-end FRF.12 fragmentation for the frag map class on a Cisco 2600, 3600, or 7200 starting from global configuration mode. The fragment payload size is set to 40 bytes. Frame Relay traffic shaping is required on the PVC; the only queuing type supported on the PVC when fragmentation is configured is weighted fair queuing (WFQ).
router(config)# interface serial 1/0/0router(config-if)# frame-relay traffic-shapingrouter(config-if)# frame-relay interface-dlci 100router(config-fr-dlci)# class fragrouter(config-fr-dlci)# exitrouter(config)# map-class frame-relay fragrouter(config-map-class)# frame-relay cir 128000router(config-map-class)# frame-relay bc 1000router(config-map-class)# frame-relay fragment 40router(config-map-class)# frame-relay fair-queuerouter(config-map-class)#The following example shows how to enable pure end-to-end FRF.12 fragmentation for the frag map class on a VIP-enabled Cisco 7500 series router from global configuration mode. The fragment payload size is set to 40 bytes. Frame Relay traffic shaping is required on the PVC and is configured through the use of a hierarchical service policy (which is configured using the Modular QoS CLI and applied to the map class using the service-policy command. See the service-policy command reference for additional information on hierarchical service policies).
router(config)# class-map frfrouter(config-cmap)# match protocol vofrrouter(config-cmap)# exitrouter(config)# policy-map llqrouter(config-pmap)# class frfrouter(config-pmap-c)# priority 2000router(config-pmap-c)# exitrouter(config-pmap)# exitrouter(config)# policy-map llq-shaperouter(config-pmap)# class class-defaultrouter(config-pmap-c)# shape average 1000 128000router(config-pmap-c)# service-policy llqrouter(config-pmap-c)# exitrouter(config-pmap)# exitrouter(config)# interface serial 1/0/0.1router(config-if)# frame-relay interface-dlci 100router(config-fr-dlci)# class fragrouter(config-fr-dlci)# exitrouter(config)# map-class frame-relay fragrouter(config-map-class)# frame-relay fragment 40router(config-map-class)# service-policy llq-shaperouter(config-map-class)#The following example shows how to enable FRF.11 Annex C fragmentation for data on a Cisco MC3810 PVC configured for VoFR. Note that fragmentation must be configured if a VoFR PVC is to carry data. The fragment payload size is set to 40 bytes. Frame Relay traffic shaping is required on the PVC; the only queuing type supported on the PVC when fragmentation is configured is weighted fair queuing (WFQ).
router(config)# interface serial 1/1router(config-if)# frame-relay traffic-shapingrouter(config-if)# frame-relay interface-dlci 101router(config-fr-dlci)# vofrrouter(config-fr-dlci)# class fragrouter(config-fr-dlci)# exitrouter(config)# map-class frame-relay fragrouter(config-map-class)# frame-relay cir 128000router(config-map-class)# frame-relay bc 1000router(config-map-class)# frame-relay fragment 40router(config-map-class)# frame-relay fair-queuerouter(config-map-class)#The following example is for the same configuration on a VIP-enabled Cisco 7500 series router:
router(config)# class-map frfrouter(config-cmap)# match protocol vofrrouter(config-cmap)# exitrouter(config)# policy-map llqrouter(config-pmap)# class frfrouter(config-pmap-c)# priority 2000router(config-pmap-c)# exitrouter(config-pmap)# exitrouter(config)# policy-map llq-shaperouter(config-pmap)# class class-defaultrouter(config-pmap-c)# shape average 1000 128000router(config-pmap-c)# service-policy llqrouter(config-pmap-c)# exitrouter(config-pmap)# exitrouter(config)# interface serial 1/1/0.1router(config-if)# frame-relay interface-dlci 101router(config-fr-dlci)# class fragrouter(config-fr-dlci)# exitrouter(config)# map-class frame-relay fragrouter(config-map-class)# frame-relay fragment 40router(config-map-class)# service-policy llq-shaperouter(config-map-class)#The following example shows how to enable Cisco proprietary Frame Relay fragmentation for the frag Frame Relay map class on a Cisco 2600, 3600, 7200, or 7500 series router, starting from global configuration mode. The fragment payload size is set to 40 bytes. Frame Relay traffic shaping is required on the PVC; the only queuing type supported on the PVC when fragmentation is configured is weighted fair queuing (WFQ).
router(config)# interface serial 2/0/0router(config-if)# frame-relay traffic-shapingrouter(config-if)# frame-relay interface-dlci 102router(config-fr-dlci)# vofr ciscorouter(config-fr-dlci)# class fragrouter(config-fr-dlci)# exitrouter(config)# map-class frame-relay fragrouter(config-map-class)# frame-relay cir 128000router(config-map-class)# frame-relay bc 1000router(config-map-class)# frame-relay fragment 40router(config-map-class)# frame-relay fair-queuerouter(config-map-class)#The following example is for the same configuration on a VIP-enabled Cisco 7500 series router:
router(config)# class-map frfrouter(config-cmap)# match protocol vofrrouter(config-cmap)# exitrouter(config)# policy-map llqrouter(config-pmap)# class frfrouter(config-pmap-c)# priority 2000router(config-pmap-c)# exitrouter(config-pmap)# exitrouter(config)# policy-map llq-shaperouter(config-pmap)# class class-defaultrouter(config-pmap-c)# shape average 1000 128000router(config-pmap-c)# service-policy llqrouter(config-pmap-c)# exitrouter(config-pmap)# exitrouter(config)# interface serial 2/0/0.1router(config-if)# frame-relay interface-dlci 102router(config-fr-dlci)# class fragrouter(config-fr-dlci)# exitrouter(config)# map-class frame-relay fragrouter(config-map-class)# frame-relay fragment 40router(config-map-class)# service-policy llq-shapeRelated Commands
service-policy
To use a service policy as a QoS policy within a policy map (called a hierarchical service policy), use the service-policy policy map class configuration command. To disable a particular service policy as a QoS policy within a policy map, use the no form of this command.
service-policy policy-map-name
no service-policy policy-map-name
Syntax Description
Defaults
No default behavior or values.
Command Modes
Policy map class configuration
Command History
12.1(2)E
This command was introduced.
12.1(5)T
This command was introduced for Cisco IOS Release 12.1 T.
Usage Guidelines
This command is used to create hierarchical service policies in policy map class configuration mode.
This command is different from the service-policy [input | output] policy-map-name command used in interface configuration mode. The purpose of the service-policy [input | output] policy-map-name is to attach service policies to interfaces.
The child policy is the previously defined service policy that is being associated with the new service policy through the use of the service-policy command. The new service policy using the preexisting service policy is the parent policy. In the example in the next section, service policy child is the child policy and service policy parent is the parent policy.
This command has the following restrictions:
•
•
•
•
Examples
The following example creates a hierarchical service policy in service policy parent:
Router(config)# policy-map childRouter(config-pmap)# class voiceRouter(config-pmap-c)# priority 50Router(config)# policy-map parentRouter(config-pmap)# class class-defaultRouter(config-pmap-c)# shape average 10000000Router(config-pmap-c)# service-policy childFRF.11 and FRF.12 configurations on a VIP-enabled Cisco 7500 series routers often require a hierarchical service policy for configuration. A hierarchical service policy for FRF.11 and FRF.12 requires the following elements:
Requirement A. A traffic class that uses VoFR protocol as the only match criterion.
Requirement B. A traffic policy that insures Low Latency Queueing (LLQ, which is achieved using the priority command) for all VoFR protocol traffic
Requirement C. A traffic policy that defines the shaping parameters and includes the elements listed in Requirement B.
Requirement C can only be fulfilled through the use of a hierarchical service policy (which is configured using the service-policy command).
In the following example, requirement A is configured in traffic class frf, requirement B is configured in traffic policy llq, and requirement C is configured in traffic policy llq-shape.
router(config)# class-map frfrouter(config-cmap)# match protocol vofrrouter(config-cmap)# exitrouter(config)# policy-map llqrouter(config-pmap)# class frfrouter(config-pmap-c)# priority 2000router(config-pmap-c)# exitrouter(config-pmap)# exitrouter(config)# policy-map llq-shaperouter(config-pmap)# class class-defaultrouter(config-pmap-c)# shape average 1000 128000Router(config-pmap-c)# service-policy llqThe final step in using a hierarchical service policy for FRF.11 and FRF.12 is using the service policy in map class configuration mode. In the following example, the llq-shape traffic policy is attached to map class frag:
router(config)# map-class frame-relay fragrouter(config-map-class)# frame-relay fragment 40router(config-map-class)# service-policy llq-shapeRelated Commands
show frame-relay fragment
To display information about the Frame Relay fragmentation taking place in your Cisco router, use the show frame-relay fragment command from privileged EXEC mode.
show frame-relay fragment [interface interface [dlci]]
Syntax Description
Command Modes
Privileged EXEC
Command History
Usage Guidelines
When no parameters are specified with this command, the output displays a summary of each DLCI configured for fragmentation. The information displayed includes the fragmentation type, the configured fragment size, and the number of fragments transmitted, received, and dropped.
When a specific interface and DLCI are specified, additional details are displayed.
Note
Examples
The following is sample output for the show frame-relay fragment command without any parameters specified:
router# show frame-relay fragmentinterface dlci frag-type frag-size in-frag out-frag dropped-fragSerial0 108 VoFR-cisco 100 1261 1298 0Serial0 109 VoFR 100 0 243 0Serial0 110 end-to-end 100 0 0 0The following is sample output for the show frame-relay fragment command when an interface and DLCI are specified:
router# show frame-relay fragment interface Serial1/0fragment-size 45 fragment type end-to-endin fragmented pkts 0 out fragmented pkts 0in fragmented bytes 0 out fragmented bytes 0in un-fragmented pkts 0 out un-fragmented pkts 0in un-fragmented bytes 0 out un-fragmented bytes 0in assembled pkts 0 out pre-fragmented pkts 0in assembled bytes 0 out pre-fragmented bytesin dropped reassembling pkts 0 out dropped fragmenting pkts 0in timeouts 0in out-of-sequence fragments 0in fragments with unexpected B bit set 0out interleaved packets 0Table 4 describes the significant fields in this output.
Related CommandsRelated Commands
Glossary
ABCD signaling—4-bit telephony line signaling coding in which each letter of "ABCD" represents one of the 4 bits. This is often associated with CAS or robbed-bit signaling on a T1 or E1 telephony trunk.
CID—Channel ID. Designates the Frame Relay subchannel ID for Voice over Frame Relay.
CIR—Committed information rate. The average rate of information transfer a subscriber (for example, a network administrator) has stipulated for a Frame Relay PVC.
Cisco-trunk (private line) call—A Cisco-trunk (private line) call is established by the forced connection of a dynamic switched call. A Cisco-trunk call is established during configuration of the trunk and stays up for the duration of the configuration. It optionally provides a pass-through connection path to pass signaling information between the two telephony interfaces at either end of the connection.
Codec—Coder-decoder. (i) An integrated circuit device that typically uses pulse code modulation to transform analog signals into a digital bit stream and digital signals back into analog signals. (ii) In Voice over IP, Voice over Frame Relay, and Voice over ATM, a DSP software algorithm used to compress/decompress speech or audio signals.
DLCI—Data-link connection identifier.
Dial peer—An addressable call endpoint that contains configuration information including voice protocol, codec type, and telephone number associated with the call endpoint. There are four kinds of dial peers: POTS, VoIP, VoFR, and VoATM.
DS0—A 64-kbps B channel on an E1 or T1 WAN interface.
DTMF—Dual-tone multifrequency. Uses two simultaneous voice-band tones for dial (such as touch tone).
DTMF relay—Enables the generation of FRF.11 Annex A frames for a VoFR dial peer. The DSP generates Annex A frames instead of passing a DTMF tone through the network as a voice sample.
Dynamic switched call—A telephone call dynamically established across a packet data network based on a dialed telephone number. In the case of VoFR, a Cisco proprietary session protocol similar to Q.931 is used to achieve call switching and negotiation between calling endpoints. The proprietary session protocol runs over FRF.11-compliant subchannels.
E&M—Stands for recEive and transMit (or Ear and Mouth). E&M is a trunking arrangement generally used for two-way switch-to-switch or switch-to-network connections. Cisco's analog E&M interface is an RJ-48 connector that allows connections to PBX trunk lines (tie lines). E&M is also available on E1 and T1 digital interfaces.
FIFO—First-in, first-out. In data communication, FIFO refers to a buffering scheme where the first byte of data entering the buffer is the first byte retrieved by the CPU. In telephony, FIFO refers to a queuing scheme where the first calls received are the first calls processed.
FRF—Frame Relay Forum. An association of corporate members consisting of vendors, carriers, users, and consultants committed to the implementation of Frame Relay in accordance with national and international standards. Go to http://www.frforum.com.
FRF.11—Frame Relay Forum implementation agreement for Voice over Frame Relay (v1.0 May 1997). This specification defines multiplexed data, voice, fax, DTMF digit-relay and CAS/robbed-bit signaling frame formats, but does not include call setup, routing, or administration facilities. Go to http://www.frforum.com.
FRF.11 Annex C—See FRF.12.
FRF11-trunk—A point-to-point permanent voice connection (private line) conforming to the FRF.11 specification.
FRF.12—The FRF.12 Implementation Agreement (also known as FRF.11 Annex C) was developed to allow long data frames to be fragmented into smaller pieces and interleaved with real-time frames. In this way, real-time voice and non-real-time data frames can be carried together on lower-speed links without causing excessive delay to the real-time traffic. Go to http://www.frforum.com.
FXO—Foreign Exchange Office. An FXO interface connects to the Public Switched Telephone Network's (PSTN) central office and is the interface offered on a standard telephone. Cisco's FXO interface is an RJ-11 connector that allows an analog connection to be directed at the PSTN's central office or to a station interface on a PBX.
FXS—Foreign Exchange Station. An FXS interface connects directly to a standard telephone and supplies ring, voltage, and dial tone. Cisco's FXS interface is an RJ-11 connector that allows connections to basic telephone service equipment, keysets, and PBXs.
Hookflash—A short on-hook period usually generated by a telephone-like device during a call to Mercury Exchange Limited (MEL) Channel Associated Signaling (CAS). A voice signaling protocol used primarily in the United Kingdom.
PBX—Private branch exchange. Privately owned central switching office.
Permanent calls—Permanent calls are private line calls used for fixed point-to-point calls, connections between PBXs (E&M to E&M), or for remote telephone extensions (FXO to FXS).
PLAR—Private line, automatic ringdown. A leased voice circuit that connects two single endpoints together. When either telephone handset is taken off-hook, the remote telephone automatically rings.
POTS—Plain old telephone service. Basic telephone service supplying standard single line telephones, telephone lines, and access to the PSTN.
POTS dial peer—Dial peer connected via a traditional telephony network. POTS peers point to a particular voice port on a voice network device.
PSTN—Public Switched Telephone Network. PSTN refers to the local telephone company.
PVC—Permanent virtual circuit.
SVC—Switched virtual circuit.
Switched calls—Switched calls are normal telephone calls in which a user picks up a telephone, hears dial tone, enters the destination telephone number to reach the other telephone. Switched calls can also be private line auto-ringdown (PLAR) calls, or tie-line calls for fixed E&M to E&M fixed point-to-point connections.
Tandem switching—The dynamic switching of voice calls between VoFR or VoATM PVCs and subchannels; also called tandeming. Tandem switching is often encountered in multi-hop VoFR call connection paths.
Trunk—Service that allows quasi-transparent connections between two PBXs, a PBX and a local extension, or some other combination of telephony interfaces with signaling passed transparently through the packet data network.
VoFR—Voice over Frame Relay.
VoFR dial peer—Dial peer connected via a Frame Relay network. VoFR peers point to specific VoFR devices.
Voice over Frame Relay—Voice over Frame Relay enables a router to carry voice traffic (for example, telephone calls and faxes) over a Frame Relay network. When sending voice traffic over Frame Relay, the voice traffic is segmented and encapsulated for transit across the Frame Relay network by using FRF.12 encapsulation.
Guest
