1-57
Cisco uBR10012 Universal Broadband Router Software Configuration Guide
OL-1520-05
Chapter 1 Overview of Cisco uBR10012 Universal Broadband Router Software
Supported Software Features for the Cisco uBR10012 Router
http://www.cisco.com/en/US/docs/cable/cmts/feature/guide/ufg_cmon.html
•
PacketCable and PacketCable Multimedia on the Cisco CMTS
http://www.cisco.com/en/US/docs/cable/cmts/feature/guide/ufg_pkcb.html
•
Cisco PacketCable Primer White Paper
http://www.cisco.com/en/US/netsol/ns341/ns121/ns342/ns343/networking_solutions_white_paper
09186a0080179138.shtml
IP Broadcast and Multicast Features
The Cisco uBR10012 router supports the following IP broadcast and Multicast features:
•
IP Broadcast Echo
•
IP Multicast Echo
•
Multicast QoS Support on the Cisco uBR10012 CMTS
•
SSM Mapping
IP Broadcast Echo
You can activate upstream IP broadcast echo so that the Cisco uBR10012 router can echo broadcast
packets. For configuration information, refer to the
“Setting Optional Broadcast and Cable IP Multicast
Echo” section on page 3-29
.
IP Multicast Echo
With this feature, you can send a copy of each multicast packet (received from a cable line card) to the
downstream ports associated with the MAC domain of the receiving US port. This feature allows for all CMs
within a MAC domain to receive multicast packets sent by a CM in the same MAC domain. For additional
information, refer to the
“Setting Optional Broadcast and Cable IP Multicast Echo” section on page 3-29
.
Multicast QoS Support on the Cisco uBR10012 CMTS
Cisco IOS Release 12.3(13a)BC introduces support for Multicast downstream QoS feature. This feature
provides the ability to assign static mapping to a multicast group. The Multicast downstream QoS feature
uses the existing infrastructure (DOCSIS 1.1 service flow) to assign a multicast service identifier (SID)
to a multicast group used in the Baseline Privacy Interface (BPI) encryption feature.
When disabled, the Multicast downstream QoS feature does not impact any other features. The multicast
packets to downstream cable interfaces are sent to the default service flow.
This feature is being implemented in response to CSCeg22989 which states, multicast traffic is not
classified to any service flow, and therefore ends up queued on the default service flow. The default
service flow has no specific QoS guarantees assigned to it. So once the interface approaches congestion
level, multicast packets may be dropped.
Restrictions
•
The multicast definitions are per-bundle, not per interface. This means that all downstreams in a
bundle share the same multicast to QoS association. The downstreams will create their own service
flows according to the same QoS parameters.
•
Multicast to QoS definitions can not be assigned per sub-interface
•
Multicast SIDs are not deleted when a group becomes idle (no response to IGMP reports).
