Table Of Contents
DOCSIS 3.0 Multicast Support on the CMTS Routers
Prerequisites for the DOCSIS 3.0 Multicast Support Feature
Restrictions for the DOCSIS 3.0 Multicast Support Feature
Information About the DOCSIS 3.0 Multicast Support Feature
Multicast Forwarding on Bonded CM
Multicast Quality of Service Enhancement
Multicast Secondary Bonding Group
How to Configure the DOCSIS 3.0 Multicast Support on Cisco CMTS Routers
Configuring Basic Multicast Forwarding
Configuring Multicast DSID Forwarding
Configuring a Multicast BPI+ Support
Configuring a Multicast Join Authorization
Selecting a Forwarding Interface Based on Service Flow Attribute
How to Monitor the DOCSIS 3.0 Multicast Support on Cisco CMTS Routers
Verifying the Basic Multicast Forwarding
Verifying the Multicast DSID Forwarding
Verifying the Explicit Tracking Feature
Verifying the Multicast QoS Feature
Verifying the Multicast BPI+ Support Feature
Verifying the Multicast Join Authorization
Verifying the Service Flow Attributes
Verifying the Multicast Group Classifiers
Configuration Examples for DOCSIS 3.0 Multicast Support
Configuring Basic Multicast Forwarding: Example
Configuring Multicast QoS: Example
Configuring Multicast BPI+: Example
Configuring Multicast Join Authorization: Example
Configuring Forwarding Interface Selection Based on Service Flow Attribute: Example
Feature Information for DOCSIS 3.0 Multicast Support on the CMTS Routers
DOCSIS 3.0 Multicast Support on the CMTS Routers
First Published: December 18, 2008Last Updated: November 13, 2009Cisco IOS Release 12.2(33)SCB introduces multicast improvements as mandated by Data-over-Cable Service Interface Specifications (DOCSIS) 3.0 specifications on the Cisco Cable Modem Termination System (CMTS) Routers. DOCSIS 3.0 multicast support improves bandwidth efficiency and allows service providers to offer differentiated quality of service for different types of traffic.
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 for DOCSIS 3.0 Multicast Support on the CMTS Routers" section.
Use Cisco Feature Navigator to find information about platform support and Cisco IOS, Catalyst OS, and Cisco IOS XE software image support. To access Cisco Feature Navigator, go to http://www.cisco.com/go/cfn. An account on Cisco.com is not required.
Contents
•
Prerequisites for the DOCSIS 3.0 Multicast Support Feature
•
•
•
•
•
•
Prerequisites for the DOCSIS 3.0 Multicast Support Feature
•
•
•
Table 1 shows the Cisco CMTS hardware compatibility prerequisites for this feature.
Table 1
DOCSIS 3.0 Multicast Support Hardware Compatibility Matrix
Restrictions for the DOCSIS 3.0 Multicast Support Feature
•
•
•
•
•
•
•
•
–
–
–
–
–
–
Information About the DOCSIS 3.0 Multicast Support Feature
IP multicast, an integral technology in networked applications, is the transmission of the same information to multiple recipients. Any network application, including cable networks, can benefit from the bandwidth efficiency of multicast technology. Two new technologies—Channel Bonding and single source multicast—are expected to dramatically accelerate multicast deployment.
These technologies dramatically increase the operational efficiency of the existing Hybrid Fiber Coaxial (HFC) network. Using the multicast improvements, the cable operators can seamlessly deliver advanced services like video on demand (VoD), internet protocol television (IPTV), and facilitate interactive video and audio, and data services.
The following features explain the benefits of DOCSIS 3.0 Multicast Support:
•
•
•
Multicast DSID Forwarding
DOCSIS 3.0 multicast support introduces centralized control at the CMTS to provide flexibility and scalability to support a large array of multicast protocols. It replaces the Internet Group Management Protocol (IGMP), version 2 snooping infrastructure, which was part of the DOCSIS 1.1 and 2.0 models. Now, the CMTS allocates an unique Downstream Service Identifier (DSID) to identify every multicast stream. These DSIDs are sent to the CMs that use these DSIDs to filter and forward Multicast traffic to the CPEs.
The multicast DSID forwarding provides the following benefits:
•
•
•
•
•
•
•
•
•
–
–
–
–
–
•
Multicast Forwarding on Bonded CM
Multicast packets to the DOCSIS 3.0-enabled CMs are transmitted as bonded packets with DSID extension header on the primary bonding group if the Secondary Multicast Bonding Group is disabled. Multicast packets for MDF-disabled or pre-DOCSIS 3.0 CMs are transmitted as non-bonded without DSID extension header. For more information on this feature, refer to "Multicast Secondary Bonding Group" section.
In a network, where only MDF-enabled or MDF-disabled CMs exist, the traffic is segregated using field types. The MDF-enabled CM forwards the frame with the field type and the MDF-disabled CM drops it. The DSID labeling ensures that MDF-enabled CM gets a copy of the multicast session to prevent "cross talk".
For hybrid CMs (MDF-enabled and MDF-disabled CMs) that do not support field type forwarding, you should configure per session encryption or security association identifier (SAID) isolation to ensure traffic segregation. DOCSIS 3.0 mandates that if the hybrid CM fails to forward field type frames, the CMTS should employ multicast security association identifier (MSAID) isolation. This isolation is achieved by assigning different MSAID to each replication, one to bonded CM and another to the non-bonded or hybrid CM. This helps to prevent CMs from receiving duplicate traffic.
Static TLV Forwarding
As per DOCSIS 3.0 specifications, the CMTS must support Static Multicast. When the CM tries to register with the CMTS, the CMTS checks whether Static Multicast Encoding is present in the CM configuration file. If the Static Multicast Encoding is present, the CMTS sends a DSID corresponding to each Static Multicast channel in the Registration-Response (REG-RSP) message.
The Multicast DSID management is located at RP and the cable line card (CLC) has to contact the RP for proper DSID assignment. The CLC also caches the response from RP to eliminate the need to communicate to the RP for subsequent Static Multicast encoding. Refer BPI+ Support for more details on SAID assignment for Static Multicast functionality.
IPv6 Multicast
The Cisco CMTS routers support both IPv4 and IPv6 protocol stacks. The basic multicast character of IPv6 is similar to that of IPv4 multicast. Multicast in IPv6 can be either a Multicast Listener Discovery (MLD), version 1 that supports ASM or MLDv2 that supports SSM. DOCSIS 3.0 specifications demand support for both MLDv1 and MLDv2.
The MLD component uses the protocol descriptor block (PDB) for the multicast. The PDB contains all information about the session, including source, group, and number of sources. IPv6 mandates that all information, such as source MAC and CMTS service identifier (SID), should be accessed from the PDB.
The packet header in IPv6 contains the correct forwarding interface and DSID information. When the packet arrives at the CMTS, it is identified as an IPv6 packet and sent to the correct bundle.
For more details on IPv6, refer to the IPv6 on Cable document available at the following location: http://www.cisco.com/en/US/docs/ios/cable/configuration/guide/cmts_ipv6.html
Explicit Tracking
The CMTS can perform explicit tracking with IGMPv3 support. The IGMPv3 removes the report suppression feature associated with IGMPv2 specification enabling the CMTS to get the complete information on session and host information. This benefits the Internet Group Management Protocol (IGMP) Fast Leave processing and DSID management for each CM.
A Host or Session database is used to track Hosts (IP/MAC) joining a particular Multicast session (ASM/SSM). From the Host, you can track the CM based on the SID and Cable downstream interface. This database also helps to determine whether the CMTS should remove the DSID from a particular CM when the multicast session is over.
BPI+ Support
The DOCSIS Baseline Privacy Interface (BPI) feature is based on the DOCSIS BPI Specification (SP-BPI-I02-990319 or later revision). It provides data privacy across the HFC network by encrypting traffic flows between the router and the cable operator's CMTS.
The BPI+ (BPI Plus) feature is an enhancement to the BPI feature and is based on the DOCSIS BPI+ Specification (SP-BPI+-I04-000407 or later revision). In addition to the regular BPI features, BPI+ provides more secure authentication of cable modems through the use of digital certificates. Also, a cable modem can use a digital signature to verify that the software image it has downloaded has not been altered or corrupted in transit.
Dynamic Multicast Encryption
The CMTS encrypts downstream multicast traffic to the CMs with a security association (SA), which is previously signaled to the CM. The security association identifier is defined per session and communicated in a SA encoding through the MAC management message sent to the CM. The CMTS uses dynamic SA mechanism for DSID multicast forwarding in MDF-disabled CMs.
During a dynamic multicast join event, through IGMP or Multicast Listener Discovery (MLD), the CMTS checks the configuration table to see whether the session must be encrypted. If it requires encryption, the CMTS creates a multicast security association identifier (MSAID) and includes it in SA encoding with an add action in the Dynamic Bonding Change Request (DBC-REQ).
Static Multicast Encryption
During a static multicast encoding from Registration Request (REG-REQ), CMTS checks the configuration table at RP through Inter-Process Communication (IPC) to ascertain the need for encryption. If it requires encryption, the CMTS creates an MSAID and includes it in the SA encoding with an add action in the REG-RSP. The cable line card (CLC) can also cache the MSAID mapping for subsequent requests.
Multicast Join Authorization
DOCSIS 3.0 introduces the IP Multicast Join Authorization feature to control the IP multicast sessions joined by the IP multicast clients. The set of IP multicast clients reached through the CM includes the CM IP host stack itself. This feature controls only the joining of downstream IP multicast sessions and not the ability of any client to transmit IP multicast traffic upstream.
General guidelines for multicast join authorization are as follows:
•
•
•
•
•
•
With the above guidelines, static MAC multicast and static IP multicast are authorized by default. The CMTS enforces IP multicast join authorization by signaling or not signaling multicast DSIDs and /or SAs. For a pre-DOCSIS 3.0 CM, multicast BPI+ must be used.
The cable multicast auth enable default-action command is used to enable or disable Multicast Join Authorization feature.
Multicast Session Limits
DOCSIS 3.0 supports per CM multicast session where you can configure Multicast Session Encoding in the CM configuration file as specified in the DOCSIS 3.0 specifications.
The CMTS receives the encoding of REG-REQ from the CLC and the CLC would notify the Route Processor through Inter-Process Communication about CM registration.
The CMTS supports a session limit between 0 and 65535 per CM. If the CM does not include encoding, the CMTS uses the default Maximum Multicast Sessions. The multicast session limit only enforces the dynamic join session and does not restrict Static Multicast sessions.
IP Multicast Profile
In IP Multicast Profile, the CMTS provides the capability to store 16 profiles, each with 256 session rules. Each session rule consists of the Source prefix, Group prefix, Priority, and "Permit" or "Deny" action. The rule priority is used to determine the best matching rule.
The CM can store up to 16 IP Multicast Profiles and the CMTS makes use of them to configure a Multicast Profile for the CM. If the CM does not have any IP Multicast Profile defined, the CMTS uses the Default IP Multicast Profile name. If the IP Multicast Profile defined in the CM configuration file is not available in the CMTS, an empty Multicast Profile with the same name is created by the CMTS, which can be configured later by the operator.
If the join request of a CM to a multicast session does not match any of the session rules, the CMTS uses the Default IP Multicast Join Authorization Action, which can be either "Permit" or "Deny." When you change the session rules, the CMTS reapplies the latest rules on all subsequent join requests.
Default Multicast Authorization Profiles
Cisco IOS Release 12.2(33)SCC introduces the option to create default multicast authorization profiles. These profiles are used to register modems without an authorization profile in their configuration file. Like other profiles, the default profile group can store up to 16 default multicast authorization profiles. The default profile group also maintains a sorted list of session rules from all default profiles, based on priority. Each configured default profile can store up to 256 session rules.
The session rules are used to authorize modems without a profile name in their configuration file. When an IGMP join for a group is received from such a modem, it is matched against the rules in the default profile group. If the rules match, the join action is permitted, else the globally configured default action is taken.
When a session rule is created, the CMTS assigns an ID to that rule. These session rule IDs are assigned sequentially and are unique per profile. If there are 5 session rules in a profile, they are assigned IDs ranging from 0 to 4. If a session rule is deleted, the next rule in the profile is assigned with that ID. For example, when a session rule with ID 3 is deleted, the next rule in the profile will be assigned ID 3.
The DOCSIS 3.0 operations support system (OSS) specification mandates that the session rules have to be identified within a profile using an identifier value that has a range of 1 to 4,294,967,295 (32 bit).
The cable multicast auth profile-name command is used to define a cable multicast authorization profile and to set it as the default profile.
MDF-Disabled CM
To enforce multicast authorization in MDF-disabled and pre-DOCSIS 3.0 CMs, the CMTS should configure per-session encryption based on Security Association-Multicast Authorization Profile (SA-MAP) authorization. The CMTS should check the SA-MAP request against the Multicast Authorization Profile of the CM to verify whether it is an authorized flow and reply with a SAID accordingly.
Multicast Quality of Service Enhancement
DOCSIS 3.0 mandates that the CMTS should not admit any flow exceeding the session limit. Though the current Multicast QoS (MQoS) session limit admits the session, it fails to provide any QoS for sessions exceeding the session limit.
Note
As part of DOCSIS 3.0 requirements for Multicast QoS, Cisco IOS Release 12.2(33)SCC provides support for Group Classifier Rules (GCR). The CMTS determines the set of Group Configurations (GCs) whose session range matches the multicast group address. For SSM, the source address is also used to identify the matching GCs. A GCR is created for each matching GC and linked to the multicast session. The GCR is assigned also with an unique identifier, SAID, and Group Service Flow (GSF).
The following conditions are used to select the GC entries:
•
•
The GCR classification is done based on type of service (TOS) fields. The TOS specifier in the GCR is used to choose the correct GCR when multiple GCRs match a single multicast session.
Non-IP multicasts and broadcast packets use Group Service Flows (GSF). They are similar to individual service flows and shared by all the CMs on a particular Digital Command Signal (DCS) matching the same GCR. A single GSF is used for multicast sessions matching different GCs using the same aggregate GQC.
The legacy multicast QoS cable match address command is replaced from Cisco IOS Release 12.2(33)SCB onwards to allow multiple system operators (MSOs) to move to the new Multicast QoS model. The old command is automatically translated to the new command during system bootup while parsing the startup configuration. After system configuration, the old command is disabled from the parser chain.
Multicast Secondary Bonding Group
The DOCSIS 3.0-compliant CM can receive multicast packets from non-primary (or bonded) channels using the MDF support at the CMTS.
The Multicast Secondary Bonding Group is defined as a shared bonding group or radio frequency (RF) channel that feeds more than one fiber node through an optical split. This allows CMs from different primary bonding groups and channels to listen to one or more shared sets. The multicast packets are replicated to the shared downstream channel set only, which helps to conserve the downstream bandwidth.
DOCSIS 3.0 defines attribute-based service flow creation, which allows the CMTS to make more "intelligent" decisions on the selection of bonding group or individual channel for unicast and multicast forwarding.
The Multicast Secondary Bonding Group provides the following benefits:
•
•
•
–
–
–
–
•
–
–
•
Load Balancing
The Load Balancing feature modified in Cisco IOS Release 12.2(33)SCB will not load balance a CM while a multicast stream is going on for that particular CM. It utilizes the Explicit Tracking Database, which holds complete information on the CM subscription to achieve this. For more information on Load Balancing, refer to the Configuring Load Balancing and Dynamic Channel Change on the Cisco CMTS Routers document.
Bonded DS Admission Control
Multiple MAC domains may share a single DS bonding group. Similarly, CPEs from multiple MAC domains could listen to a Wideband multicast service flow. The devices could join or leave the multicast group in any order.
The bonded multicast service flows are admitted and created on the Guardian line card rather than on a specific host line card.
The admission control for Wideband DS interfaces should also take into account the multicast service flow bandwidth usage. The entire DS bonding group bandwidth is available for every single MAC domain and the multicast traffic for committed information rate (CIR) reservations is based on the current CIR bandwidth usage of the sharing MAC domains.
The aggregate use of CIR bandwidth is limited by the bonding group definition. However, a single MAC domain could reserve the entire bandwidth if other MAC domains are not using it for CIR purposes.
The following criteria is used for DS bonding group bandwidth distribution:
•
•
When the number of MAC domains sharing the DS bonding group increases, the available bandwidth decreases proportionally. It also limits the service flow CIR that can be admitted on the Guardian line card or MAC domain host.
Based on the example given in Table 2, three MAC domain hosts are sharing a DS bonded interface with 60 Mbps bandwidth. Initially, the Guardian line card is getting 30 Mbps and the other MAC domain hosts are getting 10 Mbps each. If the multicast usage goes up by 30 Mbps, the available bandwidth will be
60 - 30 = 30 Mbps. This new bandwidth will be shared between the Guardian line card and MAC domain hosts. Now, the Guardian line card would get 15 Mbps and the MAC domains would get 5 Mbps each. This limits the highest CIR service flow that can be admitted to MAC domain hosts to 5 Mbps, although the available bandwidth is still 30 Mbps. If any of the MAC domain hosts keeps admitting service flows much smaller (for example, 100 Kbps) compared to 5 Mbps, it could reserve close to 30 Mbps provided the service flow admission is spaced apart by 3 seconds.Table 2
Sharing a DS Bonded Interface Between Guardian Line Card and Three MAC Domains
How to Configure the DOCSIS 3.0 Multicast Support on Cisco CMTS Routers
This section describes the following tasks that are required to implement DOCSIS 3.0 Multicast Support on Cisco CMTS Routers:
•
•
•
•
•
•
Configuring Basic Multicast Forwarding
To configure a basic multicast forwarding profile that can be applied to a DOCSIS 3.0 multicast configuration, use the ip multicast-routing command. You must configure a multicast routing profile before you can proceed with a multicast group.
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
7.
DETAILED STEPS
Configuring Multicast DSID Forwarding
The multicast DSID forwarding is enabled by default. You cannot configure this feature.
Configuring Explicit Tracking
The Explicit Tracking feature is enabled by default. You cannot configure it.
Configuring Multicast QoS
To configure a Multicast QoS profile that can be applied to a DOCSIS 3.0 configuration, use the cable multicast group-qos command. You must configure a Multicast QoS profile before you can add a Multicast QoS profile to a QoS multicast group.
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
14.
DETAILED STEPS
Configuring a Multicast BPI+ Support
To configure a multicast BPI+ profile that can be applied to a QoS group configuration, use the cable multicast qos group command.
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
DETAILED STEPS
Configuring a Multicast Join Authorization
To configure a multicast join authorization to control the IP multicast sessions joined by the IP multicast clients, use the cable multicast authorization command.
SUMMARY STEPS
1.
2.
3.
4.
5.
DETAILED STEPS
Selecting a Forwarding Interface Based on Service Flow Attribute
The Service Flow Attribute feature allows a bonded CM to listen to multiple bonding groups, and using the interface-specific bit-masks, the CM can select the best route to receive multicast traffic.
Service Flow Attribute
The Service Flow Attribute feature allows selection of a forwarding interface based on the DOCSIS 3.0 construct named "service flow attribute mask." Every interface has an attribute bit-mask depicting attributes of that interface. The multicast service class specified in the group QoS configuration contains required and forbidden attribute bit-masks. If a bonded CM can listen to multiple bonding groups (wideband interfaces), using specific bit-masks in the service class as well as on the bonding group, then one of these bonding groups can be selected for forwarding of multicast traffic.
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
14.
DETAILED STEPS
How to Monitor the DOCSIS 3.0 Multicast Support on Cisco CMTS Routers
To monitor the DOCSIS 3.0 Multicast Support feature, use the following procedures:
•
•
•
•
•
•
•
•
Verifying the Basic Multicast Forwarding
To show the configuration parameters for basic multicast forwarding, use the show ip multicast-routing command as shown in the following example:
Router# show ip mroute
IP Multicast Routing TableFlags: D - Dense, S - Sparse, B - Bidir Group, s - SSM Group, C - Connected,L - Local, P - Pruned, R - RP-bit set, F - Register flag,T - SPT-bit set, J - Join SPT, M - MSDP created entry, E - Extranet,X - Proxy Join Timer Running, A - Candidate for MSDP Advertisement,U - URD, I - Received Source Specific Host Report,Z - Multicast Tunnel, z - MDT-data group sender,Y - Joined MDT-data group, y - Sending to MDT-data group,V - RD & Vector, v - VectorOutgoing interface flags: H - Hardware switched, A - Assert winnerTimers: Uptime/ExpiresInterface state: Interface, Next-Hop or VCD, State/Mode(*, 230.1.1.1), 00:00:03/00:02:55, RP 30.1.1.1, flags: SIncoming interface: Null, RPF nbr 0.0.0.0Outgoing interface list:Bundle1, Forward/Sparse, 00:00:03/00:02:55, H(*, 224.0.1.40), 00:12:02/00:02:19, RP 30.1.1.1, flags: SJCLIncoming interface: Null, RPF nbr 0.0.0.0Outgoing interface list:Bundle1, Forward/Sparse, 00:12:02/00:02:19To show multicast information for the specified virtual interface bundle, based on IGMPv3, use the show cable bundle multicast command as shown in the following example:
Router# show cable bundle 1 multicast
CableBundle Interface Source IP Multicast IP MAC Address1 Bundle1.1 * 230.1.1.1 0100.5e00.0001To show the MAC forwarding table for the specified virtual interface bundle, based on IGMPv3, use the show cable bundle forwarding command as shown in the following example:
Router# show cable bundle 1 forwarding
MAC address Interface Flags Location link sublink00c0.5e01.0203 Cable8/0/0 3 64E5BF60 0 64E5BE0000c0.5e01.0203 Cable7/0/0 3 64E5BE00 0 000c0.5e01.0101 Cable8/0/0 3 64E5BEE0 0 64E5BE40To show multicast routing table in the PXF processor for a specified group, use the show pxf cpu mroute command as shown in the following example:
Router# show pxf cpu mroute 0.0.0.0
Shadow G/SG[5624]: s: 0.0.0.0 g: 224.0.1.40 uses: 0 bytes 0 flags: [D ] LNJInterface vcci offset rw_index mac_headerIn : 0 0x000004Shadow G/SG[3195]: s: 0.0.0.0 g: 234.5.6.7 uses: 0 bytes 0 flags: [5 ] NJInterface vcci offset rw_index mac_headerIn : 0 0x000008Out: Cable5/1/0 5 0x00002C 1B 00000026800001005E05060700010Out: Cable6/1/1 9 0x000028 1A 00000026800001005E05060700010Out: Cable6/0/0 6 0x000024 19 00000026800001005E05060700010Out: Cable5/0/0 3 0x000020 18 00000026800001005E05060700010Out: Cable7/0/0 A 0x00001C 17 00000026800001005E05060700010Out: Cable7/1/1 C 0x000018 16 00000026800001005E05060700010Out: Cable7/1/0 B 0x000014 15 00000026800001005E05060700010Out: Cable6/1/0 8 0x000010 14 00000026800001005E05060700010Out: Cable6/0/1 7 0x00000C 13 00000026800001005E05060700010Out: Cable5/0/1 4 0x000008 12 00000026800001005E05060700010To show multicast routes (mroute) in the PXF processor for a specified group, use the show pxf cable multicast command as shown in the following example:
Router# show pxf cable multicast 0.0.0.0
MDB Flags: L - Local, F - Register flag, T - SPT-bit set, J - Join SPTZ - Multicast Tunnel, N- No FastSwitchingOIF Flags: P - Prune Flag, A - Assert FlagPXF multicast switching for vrf default is enabled.Mdb at index= 3 hash= 0xE9F7:next_mdb_idx: 0, fib_root: 0x0001, source_addr: 0.0.0.0, group_addr: 230.1.1.1uses: 0, bytes: 0, vcci_in: 0, oif: 0x000002rpf_failed: 0, drop_others: 0rp_bit_mask:0x00, flags: [0xA0]Ref Count=0, MDB Flags=0x0082, MDB FastFlags=0x10Verifying the Multicast DSID Forwarding
To show the entire DSID database content and all the SIP/SPA indexes assigned for a multicast session, use the show cable multicast dsid command as shown in the following example:
Router# show cable multicast dsidMulticast Group : 230.1.2.3Source : *IDB : Bu2 Interface: Mo1/1/0:0 Dsid: 0x1F078StatIndex : 2 SAID: DEFAULTMulticast Group : 230.1.2.3Source : *IDB : Bu2 Interface: Mo1/1/0:0 Dsid: 0x1F078StatIndex : 3 SAID: 8196Multicast Group : 230.1.2.3Source : *IDB : Bu2 Interface: Mo1/1/0:0 Dsid: 0x1F078StatIndex : 4 SAID: 8197
To show the entire database content, use the show cable multicast db command as shown in the following example:
Router# show cable multicast db
interface : Bundle1Session (S,G) : (*,230.1.1.1)Fwd Intfc Sub Intfc Host Intfc CM Mac HostsWi1/1/0:0 Bundle1 Ca5/0/0 0018.6852.8056 1To show information for the registered and unregistered CMs, use the show cable modem verbose command as shown in the following example:
Router# show cable modem 0010.7bb3.fcd1 verbose
MAC Address : 00C0.7bb3.fcd1IP Address : 10.20.113.2Prim Sid : 1QoS Profile Index : 6Interface : C5/0/U5sysDescr : Vendor ABC DOCSIS 2.0 Cable ModemUpstream Power : 0 dBmV (SNR = 33.25 dBmV)Downstream Power : 0 dBmV (SNR = ----- dBmV)Timing Offset : 1624Initial Timing Offset : 2812Received Power : 0.25MAC Version : DOC1.0Qos Provisioned Mode : DOC1.0Enable DOCSIS2.0 Mode : YPhy Operating Mode : atdmaCapabilities : {Frag=N, Concat=N, PHS=N, Priv=BPI}Sid/Said Limit : {Max Us Sids=0, Max Ds Saids=0}Optional Filtering Support : {802.1P=N, 802.1Q=N}Transmit Equalizer Support : {Taps/Symbol= 0, Num of Taps= 0}Number of CPE IPs : 0(Max CPEs = 1)CFG Max-CPE : 1Flaps : 373(Jun 1 13:11:01)Errors : 0 CRCs, 0 HCSesStn Mtn Failures : 0 aborts, 3 exhaustedTotal US Flows : 1(1 active)Total DS Flows : 1(1 active)Total US Data : 1452082 packets, 171344434 bytesTotal US Throughput : 0 bits/sec, 0 packets/secTotal DS Data : 1452073 packets, 171343858 bytesTotal DS Throughput : 0 bits/sec, 0 packets/secActive Classifiers : 0 (Max = NO LIMIT)DSA/DSX messages : reject allDynamic Secret : A3D1028F36EBD54FDCC2F74719664D3FSpoof attempt : Dynamic secret check failedTotal Time Online : 16:16Verifying the Explicit Tracking Feature
To show information for the explicit tracking, use the show cable multicast db command as shown in the following example:
Router# show cable multicast db
Interface : Bundle1Session (S,G) : (*,230.1.1.1)Fwd Intfc Sub Intfc Host Intfc CM Mac HostsMo1/1/0:0 Bundle1 Ca5/0/0 0018.6852.8056 1Verifying the Multicast QoS Feature
To show the cable multicast QoS details, use the show cable multicast qos command as shown in the following example:
Router# show cable multicast qos ?group-config Display Multicast Group Config informationgroup-encryption Display Multicast Group Encryption informationgroup-qos Display Multicast Group QOS informationRouter# show cable multicast qos group-configMulticast Group Config 1 : Priority 1Group QOS - 1Group Encryption - 1Session Range - Group Prefix 230.0.0.0 Mask 255.0.0.0 Source Prefix 0.0.0.0 Mask 0.0.0.0Router# show cable multicast qos group-encryptionMulticast Group Encryption 1 : Algorithm 56bit-desRouter# show cable multicast qos group-qosGroup QOS Index Service Class Control Igmp Limit OverrideDEFAULT MQOS_DEFAULT Aggregate NO-LIMIT 1 MQOS Aggregate NO-LIMITTo show information about the multicast sessions on a specific virtual forwarding interface, use the show interface multicast-session command as shown in the following example:
Router# show interface bundle1 multicast-session
Multicast Sessions on Bundle1Group Interface GC SAID SFID GQC GEn RefCount GC-Interface State224.1.1.45 Bundle1.1 1 8193 --- 1 5 1 Bundle1 ACTIVE224.1.1.46 Bundle1.1 1 8193 --- 1 5 1 Bundle1 ACTIVE224.1.1.47 Bundle1.1 1 8193 --- 1 5 1 Bundle1 ACTIVETo show DOCSIS service flows on a given cable interface, use the show interface service-flow command as shown in the following example:
Router# show interface cable 6/0 service-flow
Sfid Sid Mac Address QoS Param Index Type Dir Curr ActiveBG/CHProv Adm Act State Time4 8193 ffff.ffff.ffff 3 3 3 sec(S) DS act 21h57m5 8196 ffff.ffff.ffff 4 4 4 sec(S) DS act 00:17To show parallel express forwarding (PXF) queueing and link queue statistics, use the show pxf cpu queue command as shown in the following example:
Router# show pxf cpu queue
FP queue statistics for Cable5/0/0FP queue statistics for Cable6/0/0Queue algorithm 0x0Queue number 0 Sharedwq_avg_qlen 0 wq_flags_pd_offset 18A0001wq_drop_factor 40wq_buffer_drop 0 wq_limit_drop 0wq_invalid_enq_wqb_drop 0 wq_invalid_deq_wqb_drop 0wq_rnd_pkt_drop 0 wq_rnd_byte_drop 0wq_static_qlen_drop 0wq_len 0Packet xmit 56414 Byte xmit 14322357Queue number 15 Shared High prioritywq_avg_qlen 0 wq_flags_pd_offset 18A8001wq_drop_factor 1000wq_buffer_drop 0 wq_limit_drop 0wq_invalid_enq_wqb_drop 0 wq_invalid_deq_wqb_drop 0wq_rnd_pkt_drop 0 wq_rnd_byte_drop 0wq_static_qlen_drop 0wq_len 0Packet xmit 0 Byte xmit 0Verifying the Multicast BPI+ Support Feature
To show information about the multicast sessions on a specific virtual forwarding interface, use the show interface multicast-sessions command as shown in the following example:
Router# show interface w1/1/0:0 multicast-sessions
Multicast Sessions on Bundle1Group Interface GC SAID SFID GQC GEn RefCount GC-Interface State224.1.1.45 Bundle1.1 1 8193 --- 1 5 1 Bundle1 ACTIVE224.1.1.46 Bundle1.1 1 8193 --- 1 5 1 Bundle1 ACTIVE224.1.1.47 Bundle1.1 1 8193 --- 1 5 1 Bundle1 ACTIVETo show service identifier (SID) information about the multicast sessions on a specific virtual forwarding interface, use the show interface key sid command as shown in the following example:
Router# show interface c5/1/0:0 key sid 0
Wideband SPA: 1/0 total index assigned: 0 multicast: 0Wideband SPA: 1/1 total index assigned: 1 multicast: 1SID : 8197 Latest : 2 Current : 1Wideband SPA: WB channel : 0 blaze_index: 1Status[0] : 1 DES Key[0] : 1C7619321C8F0D73 DES IV[0] :166D1A291375011AKey Life[0]: 43171 secStatus[1] : 1 DES Key[1] : E5B0B2C23EA07B6 DES IV[1] :209E105D13E91F73Key Life[1]: 21571 secReq : 0 Rply : 0 Rej : 0 Inv : 0 RxErr : 0Verifying the Multicast Join Authorization
To verify multicast profile information, use the show cable modem auth-profile command as shown in the following example:
Router# show cable modem 0019.474a.d518 auth-profileMulticast Profile Information for 0019.474a.d518 IP: 20.1.2.3Multicast Profile Group # : 0This CM's Session Limit : 5Profile Id Profile0 goldservice1 platinumservice2 silverserviceTo verify multicast profile group, use the show cable multicast authorization profile-group command as shown in the following example:
Router# show cable multicast authorization profile-group 0ProfileGroup: 0, CMs using this group: 4ProfileId CMs Profile------------------------------0 4 goldservice1 4 platinumservice2 4 silverserviceAuth Rule List for prof_group_index: 0Src Grp Priority Action----------------------------------------------------------------------0.0.0.0/0 230.1.1.1/24 255 permitTo verify multicast profile list, use the show cable multicast authorization profile-list command as shown in the following example:
Router# show cable multicast authorization profile-list 0CMTS Authorization Profile List-------------------------------Profile Name: goldservice at index: 0Number of CMs using this Profile: 4Src Grp Priority Action----------------------------------------------------------------------0.0.0.0/0 230.1.1.1/24 255 permitVerifying the Service Flow Attributes
To verify correct configuration of service flow attributes on the service class configuration, use the show cable service-class verbose command as shown in the following example:
Router# show cable service-class 10 verboseIndex: 10Name: mcast10Direction: DownstreamTraffic Priority: 0Maximum Sustained Rate: 1000000 bits/secMax Burst: 3044 bytesMinimum Reserved Rate: 1000000 bits/secMinimum Packet Size 0 bytesAdmitted QoS Timeout 200 secondsActive QoS Timeout 0 secondsRequired Attribute Mask 8000000FForbidden Attribute Mask 7FFFFFF0Scheduling Type: UndefinedMax Latency: 0 usecsParameter Presence Bitfield: {0x3148, 0x0}To verify correct configuration of SF attributes on the Wideband interface configuration, use the show running-config interface command as shown in the following example:
Router# show running-config interface Wideband-Cable 1/0/0:2interface Wideband-Cable1/0/0:2cable bundle 1cable bonding-group-id 3cable rf-channel 3cable downstream attribute-mask 8000000FendVerifying the Multicast Group Classifiers
To verify the details of the Group Classifier Rule, use the show interface wideband-cable multicast-gcr command as shown in the following example:
Router# show interface wideband-cable 1/1/0:0 multicast-gcrGroup Classifier Rules on Wideband-Cable1/1/0:0:Classifier_id Group_id Group_Qos_id Sid SFID ref_count7 1 1 8196 10 18 2 1 8197 11 1Troubleshooting Tips
Make sure that CM can listen to the RF-frequencies specified for the Wideband interfaced chosen for forwarding multicast traffic.
Configuration Examples for DOCSIS 3.0 Multicast Support
This section provides the following configuration examples:
•
•
•
•
•
Configuring Basic Multicast Forwarding: Example
Note
In the following example, a Basic Multicast Forwarding profile is configured.
ip multicast-routingint g1/0/0ip pim sparse-dense-modeint Bundle 1ip pim sparse-modeip igmp version 3Configuring Multicast QoS: Example
Note
In the following example, Multicast QoS is configured. You should define three objects and templates and then associate these to a particular bundle or forwarding interface. The objects are Service-Class, Group-QoS-Config (GQC), and Group-Config.
cable service class 1 name MQOS_DEFAULTcable service class 1 downstreamcable service class 1 max-rate 10000000cable service class 1 min-rate 1000000cable multicast group-qos default scn MQOS_DEFAULT aggregatecable multicast group-qos 10 scn MQOS singlecable multicast qos group 20 priority 1application-id 10session-range 230.0.0.0 255.0.0.0tos 1 6 15vrf name1cable multicast qos group 20 priority 63 globalConfiguring Multicast BPI+: Example
In the following example, Multicast BPI+ is configured. The Multicast BPI+ basically reuses the Multicast QoS CLI model under Group-Config object.
cable multicast group-encryption 30 algorithm 56bit-descable multicast qos group 40 priority 2 globalsession-range 230.0.0.0 255.0.0.0group-encryption 30interface Cable5/0/0cable multicast-qos group 40Configuring Multicast Join Authorization: Example
In the following example, Multicast Join Authorization is configured:
cable multicast auth enable default-action deny max-sessions 10cable multicast auth profile GOLDmatch rule ipv4 source 0.0.0.0/0 230.0.0.0/16 128 permitmatch rule ipv4 source 10.1.1.1/8 232.0.0.0/8 128 permitendConfiguring Forwarding Interface Selection Based on Service Flow Attribute: Example
In the following example, the service flow attribute-based Forwarding Interface Selection is configured. To send multicast traffic for group 230.1.1.1, interface W1/0/0:2 is selected. The multicast QoS parameters are taken from group qos 1 (effectively from service class "mcast10").
cable service class 10 name mcast10cable service class 10 downstreamcable service class 10 max-rate 1000000cable service class 10 min-rate 1000000cable service class 10 req-attr-mask 8000000Fcable service class 10 forb-attr-mask 7FFFFFF0cable multicast group-qos 1 scn mcast10 aggregatecable multicast qos group 1 priority 1session-range 230.1.1.1 255.255.255.255group-qos 1interface Bundle1ip address 40.1.1.1 255.255.255.0ip pim sparse-modeip helper-address 2.39.16.1cable multicast-qos group 1endinterface Wideband-Cable1/0/0:0description cable rf-channel 0 bandwidth-percent 40cable bundle 1cable bonding-group-id 1cable rf-channel 0 bandwidth-percent 10cable rf-channel 1 bandwidth-percent 10cable rf-channel 2 bandwidth-percent 10cable downstream attribute-mask 8000FF00interface Wideband-Cable1/0/0:1cable bundle 1cable bonding-group-id 2 secondarycable rf-channel 0 bandwidth-percent 40cable rf-channel 1 bandwidth-percent 40cable downstream attribute-mask 8000FFF0interface Wideband-Cable1/0/0:2cable bundle 1cable bonding-group-id 3 secondarycable rf-channel 1 bandwidth-percent 40cable rf-channel 2 bandwidth-percent 40cable downstream attribute-mask 8000000FWhere to Go Next
For further information on the commands required to configure, maintain, and troubleshoot Cisco uBR7200 series universal broadband routers, the Cisco uBR10012 universal broadband routers, and Cisco cable modems, see the Cisco IOS CMTS Cable Command Reference at http://www.cisco.com/en/US/docs/ios/cable/command/reference/cbl_book.html
Additional References
The following sections provide references related to the DOCSIS 3.0 Multicast Support on the CMTS Routers.
Related Documents
CMTS cable commands
DOCSIS 1.1 as it relates to Cisco CMTS
Multicast VPN and DOCSIS 3.0 Multicast QoS
Standards
CM-SP-SECv3.0-I08-080522
CM-SP-CMCIv3-I01-080320
Cable Modem to Customer Premise Equipment Interface Specification
CM-SP-PHYv3.0-I07-080522
CM-SP-MULPIv3.0-I08-080522
CM-SP-OSSIv3.0-I07-080522
MIBs
RFCs
No new or modified RFCs are supported by this feature, and support for existing RFCs has not been modified by this feature.
—
Technical Assistance
Feature Information for DOCSIS 3.0 Multicast Support on the CMTS Routers
Table 3 lists the features in this module and provides links to specific configuration information. Only features that were introduced or modified in Cisco IOS Release 12.2(33)SCB or a later release appear in the table.
Not all commands may be available in your Cisco IOS software release. For release information about a specific command, see the command reference documentation.
Use Cisco Feature Navigator to find information about platform support and software image support. Cisco Feature Navigator enables you to determine which Cisco IOS and Catalyst OS software images support a specific software release, feature set, or platform. To access Cisco Feature Navigator, go to http://www.cisco.com/go/cfn. An account on Cisco.com is not required.
Note
Table 3 Feature Information for DOCSIS 3.0 Multicast Support on the Cisco CMTS Routers
Multicast DSID Forwarding
12.2(33)SCB
The Multicast DSID Forwarding makes use of the DSID to identify the CMs intended to join the CMTS for the multicast session. It filters and forwards the multicast packets from the CM to the CMTS.
The following sections provide information about this feature:
•
•
The following commands were introduced or modified: show cable multicast dsid.
Multicast Forwarding on Bonded CM
12.2(33)SCB
Multicast packets are sent to the CM on the primary bonding group it has registered, if Secondary Multicast Bonding Group feature is disabled.
The following sections provide information about this feature:
•
The following commands were introduced or modified: show cable modem verbose.
Explicit Tracking
12.2(33)SCB
IGMPv3 support removes report suppression enabling the CMTS to get the complete session and host information.
The following sections provide information about this feature:
The following commands were introduced or modified: show cable multicast db.
BPI+ Support
12.2(33)SCB
The BPI feature provides data privacy across the HFC network by encrypting traffic flows between the router and the cable operator's CMTS. The BPI+ (BPI Plus) feature provides more secure authentication of cable modems through the use of digital certificates.
The following sections provide information about this feature:
•
Multicast Join Authorization
12.2(33)SCB
The Multicast Join Authorization feature allows control of the IP multicast sessions joined by the IP multicast clients.
The following sections provide information about this feature:
•
The following commands were introduced or modified: cable multicast authorization, cable multicast authorization profile, match rule.
Multicast Quality of Service Enhancement
12.2(33)SCB
DOCSIS 3.0 mandates that the CMTS should not admit any flow exceeding the session limit. The current Multicast QoS session limit admits the session, however, it fails to provide any QoS for sessions exceeding the session limit.
The following sections provide information about this feature:
•
The following command is introduced: cable multicast group-qos.
Multicast Secondary Bonding Group
12.2(33)SCB
The Multicast Secondary Bonding Group is defined as a shared bonding group or RF channel that feeds more than one fiber node through an optical split. This allows CMs from different primary bonding groups and channels to listen to one or more shared sets.
The following sections provide information about this feature:
Default Multicast Authorization Profile
12.2(33)SCC
The Default Multicast Authorization Profile feature allows to create default multicast authorization profile group to authorize modems without a profile name in their configuration file.
The following sections provide information about this feature:
•
The following commands were introduced or modified: cable multicast auth profile-name.
Group Classifier Rules
12.2(33)SCC
Group Classifier Rules allows the CMTS to determine the set of GC entries whose session range matches the new SSM session.
The following sections provide information about this feature:
•
•
The following command is introduced: show interface multicast-gcr.
CCDE, CCENT, CCSI, Cisco Eos, Cisco HealthPresence, Cisco IronPort, the Cisco logo, Cisco Nurse Connect, Cisco Pulse, Cisco SensorBase, Cisco StackPower, Cisco StadiumVision, Cisco TelePresence, Cisco Unified Computing System, Cisco WebEx, DCE, Flip Channels, Flip for Good, Flip Mino, Flipshare (Design), Flip Ultra, Flip Video, Flip Video (Design), Instant Broadband, and Welcome to the Human Network are trademarks; Changing the Way We Work, Live, Play, and Learn, Cisco Capital, Cisco Capital (Design), Cisco:Financed (Stylized), Cisco Store, Flip Gift Card, and One Million Acts of Green are service marks; and Access Registrar, Aironet, AllTouch, AsyncOS, Bringing the Meeting To You, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, CCSP, CCVP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Lumin, Cisco Nexus, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Collaboration Without Limitation, Continuum, EtherFast, EtherSwitch, Event Center, Explorer, Follow Me Browsing, GainMaker, iLYNX, IOS, iPhone, IronPort, the IronPort logo, Laser Link, LightStream, Linksys, MeetingPlace, MeetingPlace Chime Sound, MGX, Networkers, Networking Academy, PCNow, PIX, PowerKEY, PowerPanels, PowerTV, PowerTV (Design), PowerVu, Prisma, ProConnect, ROSA, SenderBase, SMARTnet, Spectrum Expert, StackWise, WebEx, and the WebEx logo are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the United States and certain other countries.
All other trademarks mentioned in this document or website are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (0910R)
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.
© 2008-2009 Cisco Systems, Inc. All rights reserved.
Guest
