-
null
- Prerequisites for Mapping Service Flows to MPLS-VPN
- Restrictions for Mapping Service Flows to MPLS-VPN
- Information About Mapping Service Flows to MPLS-VPN
Service Flow Mapping to MPLS-VPN on the Cisco CMTS
First Published: February 14, 2008Last Updated: July 11, 2012
This document describes the Service Flow Mapping to MPLS-VPN feature, which enhances the existing multiprotocol label switching (MPLS) VPNs support to provide more flexible managed access for multiple ISP support over a hybrid fiber-coaxial (HFC) cable network.
 Note | Cisco IOS Release 12.2(33)SCA integrates support for this feature on the Cisco CMTS routers. This feature is also supported in Cisco IOS Release 12.3BC, and this document contains information that references many legacy documents related to Cisco IOS 12.3BC. In general, any references to Cisco IOS Release 12.3BC also apply to Cisco IOS Release 12.2SC. |
Finding Feature Information
Your software release may not support all the features documented in this module. For the latest feature information and caveats, see the release notes for your platform and software release. To find information about the features documented in this module, and to see a list of the releases in which each feature is supported, see the Feature Information Table at the end of this document.
Use Cisco Feature Navigator to find information about platform support and Cisco software image support. To access Cisco Feature Navigator, go to http://tools.cisco.com/ITDIT/CFN/. An account on http://www.cisco.com/ is not required.
Contents
- Prerequisites for Mapping Service Flows to MPLS-VPN
- Restrictions for Mapping Service Flows to MPLS-VPN
- Information About Mapping Service Flows to MPLS-VPN
- How to Configure the Service Flow Mapping to MPLS-VPN feature
- Monitoring and Maintaining Examples for Service Flow Mapping to MPLS-VPN Feature
- Configuration Examples
- Additional References
- Feature Information for Service Flow Mapping to MPLS-VPN on the Cisco CMTS Routers
Prerequisites for Mapping Service Flows to MPLS-VPN
- To support static service-flow to MPLS-VPN functionality, the Cisco uBR7200 series routers must be running Cisco IOS Release 12.2(11)BC2 or later releases and the Cisco uBR10000 series routers must be running Cisco IOS Release 12.3(13)BC or later releases.
- To support dynamic service-flow to MPLS-VPN functionality, the Cisco CMTS routers must be running Cisco IOS Release 12.3(13)BC or later releases.
- All Cisco CMTSes must be configured for the proper virtual routing and forwarding (VRF) interfaces, as specified by the documentation in the Additional References.
- To support static service-flow to MPLS VPN mapping, the DOCSIS configuration file editor must support the inclusion of Vendor-specific Options (TLV subtype 43) in the Upstream Service Flow Encodings parameter set (TLV type 24). The new option to be added is called the VPN Route Distinguisher (RD) parameter (TLV subtype 4) and must be preceded by the Cisco Vendor ID (00000C).
For example, using the Cisco DOCSIS Configurator tool, you would specify the following fields in the ASCII configuration file:
24 (Upstream Service Flow Block) S43 (Vendor Specific Options) T08 (Vendor ID) = 00 00 0c T04 (VPN Route Distinguisher) = xx xx xx xx xx xx xx xx
where the VPN RD contains eight hexadecimal bytes. The first two hexadecimal bytes specify the format of the remaining six bytes:
-
- If bytes 1 and 2 are 00 00, bytes 3 and 4 specify the 16-bit autonomous system (AS) number, and bytes 5 to 8 specify a unique 32-bit identifier.
- If bytes 1 and 2 are 00 01, bytes 3 to 6 specify the 32-bit IP address, and bytes 7 and 8 specify a unique 16-bit identifier.
Configure the VPN RD parameter to the same route-distinguisher ID that you have specified on the Cisco CMTS using the rd command in VRF configuration submode.
- To support DOCSIS configuration file-based dynamic service-flow to MPLS VPN mapping, the DOCSIS configuration file editor must support the inclusion of the Cisco Vendor-specific Dynamic Flow VPN RD parameter (TLV subtype 13).
For example, using the Cisco DOCSIS Configurator tool, you would specify the following fields in the ASCII configuration file:
43 (Vendor Specific Info)
S8 (Vendor ID) = 0-0-c
S13 (Dynamic Flow VPN RD) = xx xx xx xx xx xx xx xx
where the eight-byte VPN RD uses the same format as specified above.
The table shows the Cisco CMTS hardware compatibility prerequisites for this feature.
Note | The hardware components introduced in a given Cisco IOS Release will be supported in all subsequent releases unless otherwise specified. |
|
CMTS Platform |
Processor Engine |
Cable Interface Cards |
|---|---|---|
|
Cisco uBR10012 Universal Broadband Router |
Cisco IOS Release 12.2(33)SCA and later
Cisco IOS Release 12.2(33)SCB and later
Cisco IOS Release 12.2(33)SCH and later
|
Cisco IOS Release 12.2(33)SCB and later
Cisco IOS Release 12.2(33)SCC and later
Cisco IOS Release 12.2(33)SCE and later
|
|
Cisco uBR7246VXR Universal Broadband Router |
Cisco IOS Release 12.2(33)SCA and later
|
Cisco IOS Release 12.2(33)SCA and later
Cisco IOS Release 12.2(33)SCD and later
|
|
Cisco uBR7225VXR Universal Broadband Router |
Cisco IOS Release 12.2(33)SCA and later
Cisco IOS Release 12.2(33)SCB and later
|
Cisco IOS Release 12.2(33)SCA and later
Cisco IOS Release 12.2(33)SCD and later
|
Note | The combination of a PRE4 and Cisco Half-Height Gigabit Ethernet (HHGE) is not supported in the same chassis. |
Restrictions for Mapping Service Flows to MPLS-VPN
- Cable modems using this feature should use a unique DOCSIS configuration file that creates an upstream packet classifier and service flow corresponding to each customer premises equipment (CPE) or media terminal adapter (MTA) device that needs to have its traffic routed to a different MPLS VPN than to the one the cable modem natively belongs.
- The DOCSIS configuration file for a cable modem must be updated whenever a CPE device that needs to use a different MPLS VPN than the cable modem’s native MPLS VPN is added or removed, or whenever the MAC address for a CPE device changes. The cable modem must also be reset to execute the changes in the DOCSIS configuration file.
-
By default, dynamically generated upstream service flows use the MPLS VPN with which a cable modem is natively associated. In order to specify a different MPLS VPN for use by dynamically generated upstream service flows, it is necessary to do one of the following:
- Specify an RD in the Cisco Vendor-specific Info Subtype Option 13 within the cable modem’s DOCSIS configuration file.
- Use the global or cable interface command cable dynamic-flow vrf to specify an MPLS VPN name.
Information About Mapping Service Flows to MPLS-VPN
The Service Flow Mapping to MPLS-VPN feature provides the following benefits to cable service providers and their partners and customers:
- Allows the service provider to maintain full control over the cable modems and other devices that are directly connected to the cable plant.
- Provides a highly flexible, scalable, and easy to manage system.
- Supports overlapping IP address ranges.
- Provides secure support for multiple intranets and extranets.
- Supports multiple IP Quality of Service (QoS) classes.
- Enables the Cisco CMTS router to support the mapping of dynamic service flows to an MPLS VPN by using the cable dynamic-flow vrf command, or the Dynamic Flow VPN RD parameter (Cisco Vendor-specific Info Subtype 13) in a DOCSIS configuration file.
The Cisco CMTS routers provide managed access by means of MPLS VPNs configured over cable subinterfaces, with each subinterface configured for a specific ISP and each cable modem associating itself and all connected CPE to a specific subinterface. This use of MPLS VPNs gives service providers a manageable way to offer users access to multiple ISPs over the same physical HFC cable network.
This system works very well when all CPE devices behind a cable modem are using the same ISP. However, users are increasingly requesting more complex networks that would allow multiple CPE devices to access different ISPs through the same cable modem. For example, different users in one household might want to use different PCs to access different ISPs. Another increasingly common situation is that one user requires a secure VPN connection for telecommuting through one ISP, while other users in the household use other computers to access the public Internet through a separate ISP.
As another example, a service provider offering a PacketCable voice-over-IP (VoIP) service may wish to allow one ISP to manage and operate the voice component of the cable network, and another to manage and operate the data component.
The Service Flow Mapping to MPLS-VPN feature solves this problem by using DOCSIS 1.1 upstream packet classifiers and service flow IDs (SFIDs) to map individual CPE devices to separate MPLS-VPN interfaces. The SFID to MPLS-VPN mapping occurs as follows:
- The service provider creates for each cable modem a DOCSIS
configuration file that contains the following information:
- Secondary upstream service flows that specify QoS profiles for CPE devices that must be associated with a particular MPLS VPN where that MPLS VPN is different from the cable modem’s native MPLS VPN assignment.
- For each upstream service flow, a Vendor-specific QoS Parameter (TLV type 43, subtype 04) that identifies the MPLS VPN RD for packets using this particular service flow.
- Upstream packet classifiers that correspond to the secondary upstream service flows, so that the cable modem may direct packets from the CPE in question to the correct service flows. To accomplish this, each classifier must contain the MAC address of CPE that are to be associated with the service flow and consequently with the MPLS VPN. This would typically be accomplished by making use of the Source MAC Address parameter (TLV type 10, subtype 2).
Note
The DOCSIS configuration file also must create a primary downstream (DS) and a primary upstream (US) service flow and packet classifier, as well as other required parameters, but these are not used for the SFID to MPLS-VPN mapping. - The cable modem downloads the DOCSIS configuration file during its registration process and configures itself for the proper service flows and packet classifiers.
- The cable modem then comes online, at which point it begins receiving packets from its CPE devices. The cable modem uses the packet’s source MAC address to match the packet to the proper packet classifier, which then identifies the correct SFID to use. The cable modem then transmits the packet to the Cisco CMTS using this upstream SFID.
- The Cisco CMTS examines the packet to determine its SFID, and then uses the Vendor-specific QoS Parameter associated with that service flow to route the packet to the appropriate MPLS-VPN interface.
- When a dynamic upstream
service flow is generated, as in the case with a PacketCable VoIP phone call,
the Cisco CMTS determines the MPLS VPN to associate the new upstream service
flow by one of several methods in the following order of precedence:
- If the cable modem’s DOCSIS configuration file contains the Dynamic Flow VPN RD parameter (Cisco Vendor-specific Info Subtype 13), then the dynamic service flow’s VPN is set to the one using the RD as specified in the parameter.
- If the cable interface on which the modem is online has had the cable dynamic-flow vrf command applied, then the dynamic service flow’s VPN is set to the MPLS VPN specified by that command.
- If the global cable dynamic-flow vrf command is applied, then the dynamic service flow’s VPN is set to the MPLS VPN specified by this command.
- Finally, the dynamic service flow’s VPN is set to the VPN to which the cable modem is associated.
If the DOCSIS configuration file for the cable modem does not contain an MPLS-VPN route, the packets from that cable modem are routed according to the routing tables on the Cisco CMTS.
MPLS QoS via TLV for non-L2VPN Service Flow
The MPLS QoS via TLV for non-L2VPN Service Flow feature is a QoS enhancement based on MPLS Traffic Class (TC) bits for MPLS L3VPN. This feature is introduced in Cisco IOS Release 12.2(33)SCG to mark TC bits for MPLS L3VPN imposition packets and classify DS packets based on TC bits of MPLS disposition packets, using vendor-specific TLVs.
The MPLS TC bits were previously known as MPLS EXP bits. RFC 5462 has renamed the MPLS EXP field to MPLS TC field.
VoIP SFID Mapping
The introduction of WB MTAs and the resequencing delays with the DS bonded traffic are pushing voice traffic towards non-bonded channels.
Starting with Cisco IOS Release 12.2(33)SCB, as the WB MTA uses the cable interface line card (CLC) DS interface as the primary interface, it can also protect voice traffic from edge quadrature amplitude modulation (e-QAM) and shared port adapter (SPA) failures. It also helps in leveraging the CLC redundancy feature to protect voice calls.
The VoIP Service Flow ID (SFID) Mapping feature leverages Data-over-Cable Service Interface Specifications (DOCSIS) 3.0 Service Flow (SF) Attribute-based assignment, which allows forwarding to Bonding groups or to single channel on a per-SF basis.
The CPE constructs DSX (Dynamic-service DOCSIS mac-management) messages that does not conform to DOCSIS 3.0 specifications and does not includes the SF Attribute parameters. However, the Cisco CMTS should control these factors and whenever voice calls are initiated; the Cisco CMTS must add SF Attributes, configured by the user, to the DSX messages.
Prerequisites for VOIP SFID Mapping
- DOCSIS 3.0-compatible voice CPE and DOCSIS 3.0-compatible PacketCable specifications.
- The Required Attribute Mask and Forbidden Attribute Mask should be configured globally.
- Mask values above zero must be inserted to all dynamic voice DS requests from WB CMs.
- The SF assignment must follow the mask values inserted in DSX message to determine forwarding.
- The Type-Length-Values (TLVs) inserted at the Required Attribute Mask and Forbidden Attribute Mask should not be sent back. They are not supported while sending Dynamic Service Response (DSx-RSP) through embedded media terminal adapter (eMTA) and could lead to cable modem (CM) error.
Restrictions for VOIP SFID Mapping
How to Configure the Service Flow Mapping to MPLS-VPN feature
The following section provides information on how to configure the Service Flow Mapping to MPLS-VPN feature. Each task in the list is identified as either required or optional.
Note | This section describes only the configuration tasks needed to enable the Service Flow Mapping to MPLS-VPN feature. It does not describe the basic MPLS-VPN configuration tasks. For information on configuring MPLS-VPN routes, see the documentation listed in the Additional References. |
- Creating a DOCSIS Configuration File
- Mapping Dynamic Service Flows
- Configuring MPLS QoS via TLV for non-L2VPN Service Flow
- Traffic Class for MPLS Imposition Packets
- Traffic Classification for MPLS Disposition Packets
- Using Vendor-Specific TLVs with AToM L2VPN and MPLS L3VPN
Creating a DOCSIS Configuration File
The Cisco CMTS automatically maps service flows to MPLS-VPN interfaces when an upstream service flow includes the VPN RD parameter as a vendor-specific TLV. The VPN RD parameter points to the route-distinguisher ID that has been specified using the rd command in VRF configuration submode.
You must create a corresponding upstream packet classifier that identifies the source MAC address that will use this SFID-to-MPLS VPN mapping. To create a DOCSIS configuration file that contains both of these parameters, use the following procedure.
Note | This procedure uses the Cisco DOCSIS Configurator tool to create the DOCSIS configuration file. However, you can use any tool that creates DOCSIS-compatible configuration files. |
Note | For information about the rd command, see the command reference. |
Mapping Dynamic Service Flows
If the MPLS VPN to which dynamic service flows are mapped must be set on a per-cable-modem basis, rather than on a per-cable-interface or per-Cisco-CMTS basis, then the Dynamic Flow VPN RD parameter (Cisco Vendor-specific Info Subtype 13) must be added to the DOCSIS configuration. The Dynamic Flow VPN RD parameter is used to specify the route-distinguisher ID for the VRF route that has been created for use by dynamic service flows.
Note | In general, the MPLS VPN to which dynamic service flows must be mapped should be the same MPLS VPN as specified for static service-flow to MPLS VPN mapping. |
| Step 1 | Refer to Step 3 of Creating a DOCSIS Configuration File. |
| Step 2 | Configure the VPN RD parameter to the same route-distinguisher ID
that you have specified on the Cisco CMTS by means of the
rd command in VRF configuration submode.
For example, if you configured a type 0 route by means of the following CLI
commands:
Example: ip vrf isp1 rd 64000:1 Configure the matching Dynamic Flow VPN RD parameter as follows: Example: 43 (Vendor Specific Info)
S8 (Vendor ID) = 0-0-c
S13 (Dynamic Flow VPN RD) = 0-0-fa-0-0-0-0-1
The Vendor-specific Options field translates into two TLVs:
Similarly, if you configured a type 1 route by means of the following CLI commands: Example: ip vrf isp2 rd 10.10.10.15:1 Configure the matching upstream service flow with the following parameters: Example: 43 (Vendor Specific Info)
S8 (Vendor ID) = 0-0-c
S13 (Dynamic Flow VPN RD) = 0-1-a-a-a-f-0-1
Similarly, the Vendor-specific Options field translates into two TLVs:
The per-cable-modem Dynamic Flow VPN RD parameter takes precedence over any per-cable-interface or per-Cisco-CMTS dynamic service flow to MPLS VPN configuration. |
| Step 3 | If the MPLS VPN to which dynamic service flows are mapped must be
set on a per-cable-interface basis, as opposed to per cable modem or
per-Cisco-CMTS, then use the following the cable interface configuration
command:
Example: Router# interface cable x/y/zRouter(config-if)# cable dynamic-flow vrf vrf-name For example, if you configured the following VRF for use with dynamically generated service flows: Example: ip vrf isp1 rd 64000:1 Then you could use the following per-cable-interface command to ensure that dynamic service flows are mapped: Example: Router# interface cable x/y/zRouter(config-if)# cable dynamic-flow vrf isp1 The per-cable-interface dynamic service flow to MPLS VPN configuration takes precedence over the global per-Cisco-CMTS dynamic service flow to MPLS VPN configuration, but not over the per-cable-modem Dynamic Flow VPN RD parameter. |
| Step 4 | If the MPLS VPN to which dynamic service flows are mapped must be
set on a per-Cisco-CMTS basis, as opposed to per cable modem or per cable
interface, then use the global configuration command:
Example: Router# cable dynamic-flow vrf
vrf-name
For example, if you configured the following VRF for use with dynamically generated service flows: Example: ip vrf isp2 rd 10.10.10.15:1 Then you could use the following per-cable-interface command to ensure that dynamic service flows are mapped: Example: Router# interface cable x/y/zRouter(config-if)# cable dynamic-flow vrf isp2 |
Configuring MPLS QoS via TLV for non-L2VPN Service Flow
Note | This feature is configured using a cable modem configuration file and is dependent on the general configuration of the L3VPN. |
This section describes how to configure traffic class bits for MPLS imposition and disposition packets and on how to use vendor-specific TLVs with AToM L2VPN and MPLS L3VPN.
Restrictions for Configuring MPLS QoS via TLV
- This feature supports only PRE4. It will not support PRE2.
- This feature supports only IPv4. It will not support IPv6.
- This feature supports only Cisco uBR10012 routers. The Cisco uBR7200 series routers is not supported.
- This feature does not support SNMP.
- This feature does not support dynamic service flows.
- Only up to four VPNs and eight upstream service flows per CM can be configured.
- For a VPN, only a maximum of eight DS classifiers (using TC bits in the range from 0 to 7) can be configured.
- If TC bits downstream classifiers are configured for a VPN, then the downstream MPLS packets belonging to the VPN are processed only on TC bits classification. It will not process general IP header field classification.
Traffic Class for MPLS Imposition Packets
The table lists the vendor-specific TLV to be included in the cable modem configuration file to configure TC bits for MPLS imposition packets. The MPLS-TC-SET TLV is defined in the upstream and is associated with the VPN RD in upstream service flow encoding.
|
TLV Name |
SubType |
Length |
Value |
|---|---|---|---|
|
MPLS-TC-SET TLV |
43.5.43.34 |
1 |
Imposition MPLS-TC-SET bits |
Traffic Classification for MPLS Disposition Packets
The table lists the vendor-specific TLV to be included in the cable modem configuration file to classify DS packets based on TC bits of MPLS disposition packets.
The MPLS-TC-RANGE TLV is defined only under DS classifier encodings. It supports multi-downstream flow in a CM belonging to the same MPLS L3VPN, associated with the VPN RD in downstream classifier encoding.
|
TLV Name |
SubType |
Length |
Value |
|---|---|---|---|
|
MPLS-TC-RANGE |
43.5.43.35 |
2 |
MPLS-TC-low and MPLS-TC-high |
Using Vendor-Specific TLVs with AToM L2VPN and MPLS L3VPN
If both AToM L2VPN (L2 MPLS) and MPLS L3VPN (L3 MPLS) are using the same set of TLVs (MPLS-TC-SET and MPLS-TC-RANGE), then you should differentiate them. Configure the TLVs for upstream service flow encoding and downstream classifier encodings as indicated below:
Upstream Service Flow Encoding
- For L2VPN, configure MPLS-TC-SET (43.5.43.34) and L2VPN ID (43.5.1).
- For MPLS L3VPN, configure MPLS-TC-SET (43.5.43.34) and VPN RD (43.5.1).
Note | Do not configure the TLVs for L2VPN and MPLS L3VPN at the same time for upstream service flow encodings, as it will result in a TLV error. |
Downstream Classifier Encoding
- L2VPN—Configure MPLS-TC-RANGE (43.5.43.35) and L2VPN ID (43.5.1).
- MPLS L3VPN—Configure MPLS-TC-RANGE (43.5.43.35) and VPN RD (43.5.1).
Monitoring and Maintaining Examples for Service Flow Mapping to MPLS-VPN Feature
This section provides examples of the commands that show the configuration and current status of the cable modems (CMs) that are using the Service Flow Mapping to MPLS-VPN feature. These examples display a number of CMs that are online, and the last CM (with the primary service identifier [SID] of 6) has three CPE devices connected to separate ISPs.
- Displaying CMs and CPE devices
- Displaying SID and MPLS Mappings
- Displaying Service Flow Configurations
Displaying CMs and CPE devices
To display the number of CMs that are currently registered and online, use the show cable modem command:
Router# show cable modem
MAC Address IP Address I/F MAC Prim RxPwr Timing Num BPI
State Sid (db) Offset CPE Enb
0030.8047.b41f 5.108.1.21 C3/0/U2 online(pt) 1 0.75 2821 0 Y
0007.0e03.1349 5.109.1.9 C3/0/U0 online 2 *0.00 2816 0 N
0007.0e03.12bd 5.108.1.18 C3/0/U0 online(pt) 3 -0.25 2812 0 Y
0030.80bc.22d5 5.108.1.20 C3/0/U0 online(pt) 4 0.25 2819 0 Y
0007.0e03.1331 5.111.1.6 C3/0/U0 online 5 -0.25 2816 0 N
00a0.73b0.4cc1 5.110.1.6 C3/0/U0 online(pt) 6 -0.25 2990 3 Y
To display the CPE devices that are associated with each CM, use the show interface cable modem command:
Router# show interface cable 3/0 modem 0 SID Priv bits Type State IP address method MAC address 1 11 modem up 5.108.1.21 dhcp 0030.8047.b41f 2 00 modem up 5.109.1.9 dhcp 0007.0e03.1349 3 11 modem up 5.108.1.18 dhcp 0007.0e03.12bd 4 11 modem up 5.108.1.20 dhcp 0030.80bc.22d5 5 00 modem up 5.111.1.6 dhcp 0007.0e03.1331 6 11 modem up 5.110.1.6 dhcp 00a0.73b0.4cc1 6 11 host unknown 131.1.2.30 dhcp 0002.e323.ac08 6 11 host unknown 129.1.2.18 dhcp 0050.046b.8b97 6 11 host unknown 130.1.2.24 dhcp 0050.da80.c13e
To display the MPLS VPN RD to be used by dynamic service flows from a cable modem using the Dynamic Flow VPN RD parameter (Cisco Vendor-specific Info Subtype 13), use the show cable modem verbose command:
Router# show cable modem 0007.0e02.afa5 verbose
MAC Address : 00a0.73b0.4cc1
IP Address : 5.110.1.6
Prim Sid : 6
Interface : C3/0/U0
sysDescr :
Upstream Power : 0.00 dBmV (SNR = 33.83 dB)
Downstream Power : 0.00 dBmV (SNR = ----- dB)
Timing Offset : 2290
Initial Timing Offset : 2290
Received Power : 0.00 dBmV
MAC Version : DOC1.1
QoS Provisioned Mode : DOC1.1
Enable DOCSIS2.0 Mode : Y
Phy Operating Mode : tdma
Capabilities : {Frag=Y, Concat=Y, PHS=Y, Priv=BPI+}
Sid/Said Limit : {Max US Sids=4, Max DS Saids=0}
Optional Filtering Support : {802.1P=N, 802.1Q=N}
Transmit Equalizer Support : {Taps/Symbol= 1, Num of Taps= 8}
Number of CPE IPs : 0(Max CPE IPs = 16)
CFG Max-CPE : 5
Flaps : 0()
Errors : 0 CRCs, 0 HCSes
Stn Mtn Failures : 0 aborts, 0 exhausted
Total US Flows : 1(1 active)
Total DS Flows : 1(1 active)
Total US Data : 1606 packets, 129106 bytes
Total US Throughput : 43 bits/sec, 0 packets/sec
Total DS Data : 28 packets, 1792 bytes
Total DS Throughput : 0 bits/sec, 0 packets/sec
Active Classifiers : 0 (Max = NO LIMIT)
DSA/DSX messages : permit all
Dynamic Secret : 4E7AD0AEA48F94DE0EB773494B57EA74
Dynamic flows mapped to VPN RD : 64000:1
! The dynamic mapping is listed above.
Total Time Online : 1d3h
Displaying SID and MPLS Mappings
To display the mapping of currently used SIDs to SFIDs and their current state, use the show interface cable sid verbose command:
Router# show interface cable 3/0 sid verbose
Sid Prim MAC Address IP Address Type Age Admin Sched Sfid
State Type
1 0030.8047.b41f 5.108.1.21 stat 3h43m enable RSVD 3
2 0007.0e03.1349 5.109.1.9 stat 3h43m enable RSVD 5
3 0007.0e03.12bd 5.108.1.18 stat 3h43m enable BE 7
4 0030.80bc.22d5 5.108.1.20 stat 3h43m enable BE 9
5 0007.0e03.1331 5.111.1.6 stat 3h42m enable BE 11
6 00a0.73b0.4cc1 5.110.1.6 stat 08:19 enable BE 13
7 6 00a0.73b0.4cc1 5.110.1.6 stat 08:19 enable BE 15
8 6 00a0.73b0.4cc1 5.110.1.6 stat 08:19 enable BE 16
9 6 00a0.73b0.4cc1 5.110.1.6 stat 08:19 enable BE 17
10 6 00a0.73b0.4cc1 5.110.1.6 dyn 02:35 enable UGS 18
To display the mappings between SFIDs and the MPLS VPN subinterface, use the show interface cable sid association command:
Router# show interface cable 3/0 sid association Sid Prim Online IP Address MAC Address Interface VRF Name 1 online(pt) 5.108.1.21 0030.8047.b41f Bu1.101 isp1 2 online 5.109.1.9 0007.0e03.1349 Bu1.102 isp2 3 online(pt) 5.108.1.18 0007.0e03.12bd Bu1.101 isp1 4 online(pt) 5.108.1.20 0030.80bc.22d5 Bu1.102 isp1 5 online 5.111.1.6 0007.0e03.1331 Bu1.102 isp2 6 online(pt) 5.110.1.6 00a0.73b0.4cc1 Bu1.103 isp3 7 6 Bu1.101 isp1 8 6 Bu1.102 isp2 9 6 Bu1.103 isp3 10 6 Bu1.102 isp2
Displaying Service Flow Configurations
To display the basic mapping of service flows and packet classifiers, use the show interface cable service-flow command. To display complete service flow configuration information, add the verbose keyword.
The following examples display the service flow information for the CM that is using the primary SID of 6 and the SFID of 13:
Router# show interface cable 3/0 service-flow 13
Sfid Sid Mac Address QoS Param Index Type Dir Curr Active
Prov Adm Act State Time
13 6 00a0.73b0.4cc1 7 7 7 prim US act 12:59
Router# show interface cable 3/0 13 verbose Sfid : 13 Mac Address : 00a0.73b0.4cc1 Type : Primary Direction : Upstream Current State : Active Current QoS Indexes [Prov, Adm, Act] : [7, 7, 7] Active Time : 13:02 Sid : 6 Traffic Priority : 0 Maximum Sustained rate : 0 bits/sec Maximum Burst : 3044 bytes Minimum Reserved Rate : 0 bits/sec Admitted QoS Timeout : 200 seconds Active QoS Timeout : 0 seconds Packets : 13 Bytes : 1833 Rate Limit Delayed Grants : 8 Rate Limit Dropped Grants : 0 Current Throughput : 0 bits/sec, 0 packets/sec Classifiers: NONE
The following examples display the service flow information for the first CPE device that is using the CM, which is using the primary SID of 6. This CPE device is using a secondary SID of 7 and the SFID of 15, and is using the VRF configuration named isp1.
Router# show interface cable 3/0 15
Sfid Sid Mac Address QoS Param Index Type Dir Curr Active
Prov Adm Act State Time
15 7 00a0.73b0.4cc1 8 8 8 sec(S) US act 13:33
Router# show interface cable 3/0 15 verbose Sfid : 15 Mac Address : 00a0.73b0.4cc1 Type : Secondary(Static) Direction : Upstream Current State : Active Current QoS Indexes [Prov, Adm, Act] : [8, 8, 8] Active Time : 13:36 Sid : 7 Traffic Priority : 0 Maximum Sustained rate : 1000000 bits/sec Maximum Burst : 65224 bytes Minimum Reserved Rate : 0 bits/sec Admitted QoS Timeout : 0 seconds Active QoS Timeout : 0 seconds Packets : 56 Bytes : 8608 Rate Limit Delayed Grants : 0 Rate Limit Dropped Grants : 0 Current Throughput : 0 bits/sec, 0 packets/sec Classifiers: Classifier Id : 1 Service Flow Id : 15 CM Mac Address : 00a0.73b0.4cc1 Direction : upstream Activation State : active Classifier Matching Priority : 0 PHSI : 0 Number of matches : - Ethernet/LLC Classifier Parameters : Source MAC : 0000.0CA1.B2C3
The following example displays the service flow information for the second CPE device that is using the CM, which is using the primary SID of 6. This CPE device is using a secondary SID of 8 and the SFID of 16, and is using the VRF configuration named isp2.
Router# show interface cable 3/0 service-flow 16
Sfid Sid Mac Address QoS Param Index Type Dir Curr Active
Prov Adm Act State Time
16 8 00a0.73b0.4cc1 8 8 8 sec(S) US act 14:04
Router# show interface cable 3/0 service-flow 16 verbose Sfid : 16 Mac Address : 00a0.73b0.4cc1 Type : Secondary(Static) Direction : Upstream Current State : Active Current QoS Indexes [Prov, Adm, Act] : [8, 8, 8] Active Time : 14:08 Sid : 8 Traffic Priority : 0 Maximum Sustained rate : 1000000 bits/sec Maximum Burst : 65224 bytes Minimum Reserved Rate : 0 bits/sec Admitted QoS Timeout : 0 seconds Active QoS Timeout : 0 seconds Packets : 155 Bytes : 20418 Rate Limit Delayed Grants : 0 Rate Limit Dropped Grants : 0 Current Throughput : 0 bits/sec, 0 packets/sec Classifiers: Classifier Id : 2 Service Flow Id : 16 CM Mac Address : 00a0.73b0.4cc1 Direction : upstream Activation State : active Classifier Matching Priority : 0 PHSI : 0 Number of matches : - Ethernet/LLC Classifier Parameters : Source MAC : 0000.0CA1.B2D4
The following example displays the service flow information for the third CPE device that is using the CM, which is using the primary SID of 6. This CPE device is using a secondary SID of 9 and the SFID of 17, and is using the VRF configuration named isp3.
Router# show interface cable 3/0 service-flow 17
Sfid Sid Mac Address QoS Param Index Type Dir Curr Active
Prov Adm Act State Time
17 9 00a0.73b0.4cc1 8 8 8 sec(S) US act 14:33
Router# show interface cable 3/0 service-flow 17 verbose Sfid : 17 Mac Address : 00a0.73b0.4cc1 Type : Secondary(Static) Direction : Upstream Current State : Active Current QoS Indexes [Prov, Adm, Act] : [8, 8, 8] Active Time : 14:36 Sid : 9 Traffic Priority : 0 Maximum Sustained rate : 1000000 bits/sec Maximum Burst : 65224 bytes Minimum Reserved Rate : 0 bits/sec Admitted QoS Timeout : 0 seconds Active QoS Timeout : 0 seconds Packets : 141 Bytes : 16152 Rate Limit Delayed Grants : 0 Rate Limit Dropped Grants : 0 Current Throughput : 33 bits/sec, 0 packets/sec Classifiers: Classifier Id : 3 Service Flow Id : 17 CM Mac Address : 00a0.73b0.4cc1 Direction : upstream Activation State : active Classifier Matching Priority : 0 PHSI : 0 Number of matches : - Ethernet/LLC Classifier Parameters : Source MAC : 0000.0CA1.B2E5
The following example displays the service flow information for a dynamically generated PacketCable service flow on the modem with a primary SID of 6. The dynamic service flow is using a secondary SID of 10 and an SFID of 18, and is using the VRF configuration named isp2.
Router# show interface cable 3/0 service-flow 18 verbose Sfid : 18 Mac Address : 00a0.73b0.4cc1 Type : Secondary(Dynamic) Direction : Upstream Current State : Active Current QoS Indexes [Prov, Adm, Act] : [0, 5, 5] Active Time : 02:59 Sid : 10 Admitted QoS Timeout : 200 seconds Active QoS Timeout : 0 seconds Packets : 8967 Bytes : 2080344 Rate Limit Delayed Grants : 0 Rate Limit Dropped Grants : 0 Current Throughput : 92399 bits/sec, 49 packets/sec Classifiers: Classifier Id : 1 Service Flow Id : 18 CM Mac Address : 00a0.73b0.4cc1 Direction : upstream Activation State : active Classifier Matching Priority : 64 PHSI : 0 Number of matches : - IP Classification Parameters : IP Source Address : 4.22.96.99 Source IP Address Mask : 255.255.255.255 Destination IP Address : 4.18.39.12 Destination IP Address Mask : 255.255.255.255 IP Protocol Type : 17 Source Port Low : 16622 Source Port High : 16622 Destination Port Low : 17640 Destination Port High : 17640
Configuration Examples
This section provides the following configuration examples:
- Example: DOCSIS Configuration File
- Example: MPLS VPN Interface Configuration
- Example: Upstream Service Flow Marking TLV
- Example: Downstream Packet Classification TLV
- Example: MPLS QoS Configuration File
Example: DOCSIS Configuration File
The following example shows a cable modem being configured to support three MPLS VPN routes. This includes three upstream packet classifiers and three upstream service-flow parameter sets. It also shows the configuration required to have dynamic service flows associated with a particular MPLS VPN:
CM-CONFIG
=========
03 (Net Access Control) = 1
18 (Maximum Number of CPE) = 100
28 (Max Number of Classifiers) = 4
29 (Privacy Enable) = 1
22 (Upstream Packet Classification Encoding Block)
S01 (Classifier Reference) = 10
S03 (Service Flow Reference) = 3
S10 (Ethernet LLC Packet Classification Encodings)
T02 (Source MAC Address) = 00 00 0C A1 B2 C3
22 (Upstream Packet Classification Encoding Block)
S01 (Classifier Reference) = 12
S03 (Service Flow Reference) = 5
S10 (Ethernet LLC Packet Classification Encodings)
T02 (Source MAC Address) = 00 00 0C A1 B2 D4
22 (Upstream Packet Classification Encoding Block)
S01 (Classifier Reference) = 14
S03 (Service Flow Reference) = 7
S10 (Ethernet LLC Packet Classification Encodings)
T02 (Source MAC Address) = 00 00 0C A1 B2 E5
24 (Upstream Service Flow Encodings)
S01 (Service Flow Reference) = 1
S06 (QoS Parameter Set Type) = 7
25 (Downstream Service Flow Encodings)
S01 (Service Flow Reference) = 2
S06 (QoS Parameter Set Type) = 7
24 (Upstream Service Flow Encodings)
S01 (Service Flow Reference) = 3
S06 (QoS Parameter Set Type) = 7
S08 (Max Sustained Traffic Rate) = 1000000
S09 (Maximum Traffic Burst) = 65224
S12 (Timeout Active QoS Parms) = 0
S13 (Timeout Admitted QoS Parms) = 0
S15 (Service Flow Sched Type) = 2
S43 (Vendor Specific Options) = 8.3.0.0.12.4.8.0.0.250.0.0.0.0.1
24 (Upstream Service Flow Encodings)
S01 (Service Flow Reference) = 5
S06 (QoS Parameter Set Type) = 7
S08 (Max Sustained Traffic Rate) = 1000000
S09 (Maximum Traffic Burst) = 65224
S12 (Timeout Active QoS Parms) = 0
S13 (Timeout Admitted QoS Parms) = 0
S15 (Service Flow Sched Type) = 2
S43 (Vendor Specific Options) = 8.3.0.0.12.4.8.0.0.246.24.0.0.0.1
24 (Upstream Service Flow Encodings)
S01 (Service Flow Reference) = 7
S06 (QoS Parameter Set Type) = 7
S08 (Max Sustained Traffic Rate) = 1000000
S09 (Maximum Traffic Burst) = 65224
S12 (Timeout Active QoS Parms) = 0
S13 (Timeout Admitted QoS Parms) = 0
S15 (Service Flow Sched Type) = 2
S43 (Vendor Specific Options) = 8.3.0.0.12.4.8.0.0.253.232.0.0.0.1
43 (Vendor Specific Info)
S8 (Vendor ID) = 0-0-c
S13 (Dynamic Flow VPN RD) = 0-0-fa-0-0-0-0-1
#<EOF>
Example: MPLS VPN Interface Configuration
The following example shows the corresponding VRF configurations with the three VRF route-designators that match the MPLS-VPN configuration that is used on the cable modem:
ip vrf MGMT rd 1:1 route-target export 62000:1 route-target import 62000:1 route-target import 63000:1 route-target import 64000:1 route-target import 65000:1 ! ip vrf isp1 rd 64000:1 route-target export 64000:1 route-target import 64000:1 route-target import 62000:1 ! ip vrf isp2 rd 63000:1 route-target export 63000:1 route-target import 63000:1 route-target import 62000:1 ! ip vrf isp3 rd 65000:1 route-target export 65000:1 route-target import 65000:1 route-target import 62000:1 ! interface Bundle1 no ip address hold-queue 1024 in ! interface Bundle1.100 ip vrf forwarding MGMT ip address 10.22.32.1 255.255.255.0 cable dhcp-giaddr policy cable helper-address 4.104.0.66 ! interface Bundle1.101 ip vrf forwarding isp1 ip address 10.22.64.1 255.255.224.0 ip address 4.22.64.1 255.255.224.0 secondary cable dhcp-giaddr policy cable helper-address 4.104.0.66 ! interface Bundle1.102 ip vrf forwarding isp2 ip address 10.22.96.1 255.255.224.0 ip address 4.22.96.1 255.255.224.0 secondary cable dhcp-giaddr policy cable helper-address 4.104.0.66 ! interface Bundle1.103 ip vrf forwarding isp3 ip address 10.22.128.1 255.255.224.0 ip address 4.22.128.1 255.255.224.0 secondary cable dhcp-giaddr policy cable helper-address 4.104.0.66 !
Example: Upstream Service Flow Marking TLV
The following example shows a sample CM configuration TLV for the provisioning of TC bits for MPLS imposition packets:
24 (Upstream Service Flow Encoding)
S01 (Service Flow Reference) = 2
S06 (QoS Parameter Set Type) = 7
S43 (Vendor Specific Options)
T08 (Vendor ID) = 00 00 0c
T004 (VPN Route Distinguisher) = xx xx xx xx xx xx xx xx
S005 (Vendor specific L2VPN TLV)
S043 (Cisco Vendor Specific)
T034 (MPLS-TC-SET) = 04 # MPLSTC-SET = 4
Example: Downstream Packet Classification TLV
The following example shows a sample CM configuration TLV for classifying downstream packets based on TC bits of MPLS disposition packets:
23 (Downstream Packet Classification Encoding)
S01 (Classifier Reference) = 13
S03 (Service Flow Reference) = 13
S11 (IEEE 802.1P/Q Packet Classification Encodings)
S43 (Vendor Specific Options)
T08 (Vendor ID) = 00 00 0c
S004 (VPN Route Distinguisher) = xx xx xx xx xx xx xx xx
S005 (Vendor specific L2VPN TLV)
S043 (Cisco Vendor Specific)
S035 (MPLS-TC-RANGE) = 04 05 # MPLSTC-EGRESS_RANGE= 4 – 5
Example: MPLS QoS Configuration File
The following example shows a cable modem being configured to mark TC bits for MPLS L3VPN imposition packets and classify downstream packets based on TC bits of MPLS L3VPN disposition packets, using vendor-specific TLVs:
CM-CONFIG
=========
03 (Net Access Control) = 1
18 (Maximum Number of CPE) = 16
22 (Upstream Packet Classification Encoding Block)
S01 (Classifier Reference) = 2
S03 (Service Flow Reference) = 2
S05 (Rule Priority) = 2
S09 (IP Packet Encodings)
T01 (IP Type of Srv Rng & Mask) = 00 20 ff
22 (Upstream Packet Classification Encoding Block)
S01 (Classifier Reference) = 3
S03 (Service Flow Reference) = 3
S05 (Rule Priority) = 3
S09 (IP Packet Encodings)
T01 (IP Type of Srv Rng & Mask) = 40 80 ff
22 (Upstream Packet Classification Encoding Block)
S01 (Classifier Reference) = 4
S03 (Service Flow Reference) = 4
S05 (Rule Priority) = 4
S09 (IP Packet Encodings)
T01 (IP Type of Srv Rng & Mask) = a0 e0 ff
23 (Downstream Packet Classification Encoding Block)
S01 (Classifier Reference) = 12
S03 (Service Flow Reference) = 12
S05 (Rule Priority) = 2
S09 (IP Packet Encodings)
T01 (IP Type of Srv Rng & Mask) = 00 ff ff
S43 (Vendor Specific Options)
T08 (Vendor ID) = 00 00 0c
T004 (Unknown sub-type) = 00 00 00 01 00 00 00 01
T005 (Unknown sub-type) = 2b 09 08 03 00 00 0c 23 02 01 01
23 (Downstream Packet Classification Encoding Block)
S01 (Classifier Reference) = 13
S03 (Service Flow Reference) = 13
S05 (Rule Priority) = 3
S09 (IP Packet Encodings)
T01 (IP Type of Srv Rng & Mask) = 00 ff ff
S43 (Vendor Specific Options)
T08 (Vendor ID) = 00 00 0c
T004 (Unknown sub-type) = 00 00 00 01 00 00 00 01
T005 (Unknown sub-type) = 2b 09 08 03 00 00 0c 23 02 02 02
23 (Downstream Packet Classification Encoding Block)
S01 (Classifier Reference) = 14
S03 (Service Flow Reference) = 14
S05 (Rule Priority) = 4
S09 (IP Packet Encodings)
T01 (IP Type of Srv Rng & Mask) = 00 ff ff
S43 (Vendor Specific Options)
T08 (Vendor ID) = 00 00 0c
T004 (Unknown sub-type) = 00 00 00 01 00 00 00 01
T005 (Unknown sub-type) = 2b 09 08 03 00 00 0c 23 02 03 03
24 (Upstream Service Flow Encodings)
S01 (Service Flow Reference) = 1
S06 (QoS Parameter Set Type) = 7
24 (Upstream Service Flow Encodings)
S01 (Service Flow Reference) = 2
S06 (QoS Parameter Set Type) = 7
S43 (Vendor Specific Options)
T08 (Vendor ID) = 00 00 0c
T004 (Unknown sub-type) = 00 00 00 01 00 00 00 01
T005 (Unknown sub-type) = 2b 08 08 03 00 00 0c 22 01 04
24 (Upstream Service Flow Encodings)
S01 (Service Flow Reference) = 3
S06 (QoS Parameter Set Type) = 7
S43 (Vendor Specific Options)
T08 (Vendor ID) = 00 00 0c
T004 (Unknown sub-type) = 00 00 00 01 00 00 00 01
T005 (Unknown sub-type) = 2b 08 08 03 00 00 0c 22 01 05
24 (Upstream Service Flow Encodings)
S01 (Service Flow Reference) = 4
S06 (QoS Parameter Set Type) = 7
S43 (Vendor Specific Options)
T08 (Vendor ID) = 00 00 0c
T004 (Unknown sub-type) = 00 00 00 01 00 00 00 01
T005 (Unknown sub-type) = 2b 08 08 03 00 00 0c 22 01 06
25 (Downstream Service Flow Encodings)
S01 (Service Flow Reference) = 11
S06 (QoS Parameter Set Type) = 7
S07 (Traffic Priority) = 7
25 (Downstream Service Flow Encodings)
S01 (Service Flow Reference) = 12
S06 (QoS Parameter Set Type) = 7
25 (Downstream Service Flow Encodings)
S01 (Service Flow Reference) = 13
S06 (QoS Parameter Set Type) = 7
25 (Downstream Service Flow Encodings)
S01 (Service Flow Reference) = 14
S06 (QoS Parameter Set Type) = 7
25 (Downstream Service Flow Encodings)
S01 (Service Flow Reference) = 15
S06 (QoS Parameter Set Type) = 7
25 (Downstream Service Flow Encodings)
S01 (Service Flow Reference) = 16
S06 (QoS Parameter Set Type) = 7
25 (Downstream Service Flow Encodings)
S01 (Service Flow Reference) = 17
S06 (QoS Parameter Set Type) = 7
25 (Downstream Service Flow Encodings)
S01 (Service Flow Reference) = 18
S06 (QoS Parameter Set Type) = 7
23 (Downstream Packet Classification Encoding Block)
S01 (Classifier Reference) = 19
S03 (Service Flow Reference) = 19
S09 (IP Packet Encodings)
T01 (IP Type of Srv Rng & Mask) = 00 ff ff
S43 (Vendor Specific Options)
T08 (Vendor ID) = 00 00 0c
T004 (Unknown sub-type) = 00 00 00 01 00 00 00 01
T005 (Unknown sub-type) = 2b 09 08 03 00 00 0c 23 02 00 00
23 (Downstream Packet Classification Encoding Block)
S01 (Classifier Reference) = 15
S03 (Service Flow Reference) = 15
S05 (Rule Priority) = 3
S09 (IP Packet Encodings)
T01 (IP Type of Srv Rng & Mask) = 00 ff ff
S43 (Vendor Specific Options)
T08 (Vendor ID) = 00 00 0c
T004 (Unknown sub-type) = 00 00 00 01 00 00 00 01
T005 (Unknown sub-type) = 2b 09 08 03 00 00 0c 23 02 04 04
23 (Downstream Packet Classification Encoding Block)
S01 (Classifier Reference) = 16
S03 (Service Flow Reference) = 16
S05 (Rule Priority) = 3
S09 (IP Packet Encodings)
T01 (IP Type of Srv Rng & Mask) = 00 ff ff
S43 (Vendor Specific Options)
T08 (Vendor ID) = 00 00 0c
T004 (Unknown sub-type) = 00 00 00 01 00 00 00 01
T005 (Unknown sub-type) = 2b 09 08 03 00 00 0c 23 02 05 05
23 (Downstream Packet Classification Encoding Block)
S01 (Classifier Reference) = 17
S03 (Service Flow Reference) = 17
S05 (Rule Priority) = 3
S09 (IP Packet Encodings)
T01 (IP Type of Srv Rng & Mask) = 00 ff ff
S43 (Vendor Specific Options)
T08 (Vendor ID) = 00 00 0c
T004 (Unknown sub-type) = 00 00 00 01 00 00 00 01
T005 (Unknown sub-type) = 2b 09 08 03 00 00 0c 23 02 06 06
23 (Downstream Packet Classification Encoding Block)
S01 (Classifier Reference) = 18
S03 (Service Flow Reference) = 18
S09 (IP Packet Encodings)
T01 (IP Type of Srv Rng & Mask) = 00 ff ff
S43 (Vendor Specific Options)
T08 (Vendor ID) = 00 00 0c
T004 (Unknown sub-type) = 00 00 00 01 00 00 00 01
T005 (Unknown sub-type) = 2b 09 08 03 00 00 0c 23 02 07 07
25 (Downstream Service Flow Encodings)
S01 (Service Flow Reference) = 19
S06 (QoS Parameter Set Type) = 7
#<EOF>
Additional References
The following sections provide references related to the Cisco CMTS routers.
Related Documents
|
Related Topic |
Document Title |
|---|---|
|
Cisco CMTS command reference |
Cisco IOS CMTS Cable Command Reference Guide, at the following URL: http://www.cisco.com/c/en/us/td/docs/cable/cmts/cmd_ref/b_cmts_cable_cmd_ref.html |
|
Cisco IOS Release 12.2 |
Cisco IOS Release 12.2 Configuration Guides and Command References, at the following URLs: http://www.cisco.com/c/en/us/support/ios-nx-os-software/ios-software-releases-12-2-mainline/products-installation-and-configuration-guides-list.html
|
|
Configuring cable features |
Cisco IOS CMTS Cable Software Configuration Guide , Release 12.2SC , at the following URL: http://www.cisco.com/web/techdoc/cable/Config/Sw_conf.html |
|
Installing and configuring Cisco uBR7200 Series Universal Broadband Routers |
Cisco uBR7200 Universal Broadband Routers, at the following URL: |
|
Installing and configuring the Cisco uBR10012 Router |
Cisco uBR10012 Universal Broadband Router, at the following URL: http://www.cisco.com/c/en/us/td/docs/cable/cmts/ubr10012/quick/start/10kqsg_2.html |
|
Service provider solution |
Cisco Cable-Ready High Speed Data (HSD) Managed Access Solution for Service Providers, at the following URL: |
|
MPLS VPN |
Cisco uBR7200 Series MPLS VPN Cable Enhancements, which is at the following URL: http://www.cisco.com/c/en/us/td/docs/ios/cable/configuration/guide/12_2sc/Cisco_CMTS_Layer2_VPN/u72_mpls_vpn_cbl.html |
Standards
|
Standard |
Title |
|---|---|
|
DOCSIS |
Data-Over-Cable Service Interface Specifications Radio Frequency Interface Specification (SP-RFIv1.1-I08-020301) |
MIBs
|
MIB |
MIBs Link |
|---|---|
|
None |
To locate and download MIBs for selected platforms, Cisco software releases, and feature sets, use Cisco MIB Locator found at the following URL: |
RFCs
|
RFC |
Title |
|---|---|
|
A Border Gateway Protocol |
|
|
Application of the Border Gateway Protocol in the Internet |
|
|
DOCSIS OSSI Objects Support |
|
|
Multiprotocol Extensions for BGP-4 |
|
|
BGP/MPLS VPNs |
|
|
DOCSIS Ethernet MIB Objects Support |
|
|
Cable Device MIB |
|
|
Multiprotocol Label Switching (MPLS) Label Stack Entry: “EXP” Field Renamed to “Traffic Class” Field |
Technical Assistance
|
Description |
Link |
|---|---|
|
The Cisco Support and Documentation website provides online resources to download documentation, software, and tools. Use these resources to install and configure the software and to troubleshoot and resolve technical issues with Cisco products and technologies. Access to most tools on the Cisco Support and Documentation website requires a Cisco.com user ID and password. |
Feature Information for Service Flow Mapping to MPLS-VPN on the Cisco CMTS Routers
Use Cisco Feature Navigator to find information about platform support and software image support. Cisco Feature Navigator enables you to determine which software images support a specific software release, feature set, or platform. To access Cisco Feature Navigator, go to http://tools.cisco.com/ITDIT/CFN/. An account on http://www.cisco.com/ is not required.
Note | The below table lists only the software release that introduced support for a given feature in a given software release train. Unless noted otherwise, subsequent releases of that software release train also support that feature. |
|
Feature Name |
Releases |
Feature Information |
|---|---|---|
|
Service Flow Mapping to MPLS-VPN on the Cisco CMTS Routers |
12.2(11)BC2 |
This feature was supported on the Cisco uBR7100 series and Cisco uBR7200 series universal broadband routers. |
|
Mapping Dynamic Service Flows |
12.3(13)BC |
Support was added for mapping dynamic service flows on the Cisco uBR7200 series and the Cisco uBR10000 series. |
|
VoIP SFID Mapping |
12.2(33)SCB |
Support was added for the VoIP SFID Mapping feature. |
|
MPLS QoS via TLV for non-L2VPN SF |
12.2(33)SCG |
This feature allows to mark TC bits for MPLS L3VPN imposition packets and classify downstream packets based on TC bits of MPLS disposition packets, using vendor-specific TLVs. The following sections provide information about this feature: |
Feedback