Configuring IP Multicast Routing
IP Multicast Configuration Examples
IPC-455
Cisco IOS IP Configuration Guide
atm nsap-address 47.00918100000000410B0A1981.333333333333.00
atm pvc 1 0 5 qsaal
atm pvc 2 0 16 ilmi
atm multipoint-signalling
map-group mpvc
router ospf 9
network 171.69.214.0 0.0.0.255 area 0
!
ip classless
ip pim rp-address 171.69.10.13 98
!
map-list mpvc
ip 171.69.214.41 atm-nsap 47.00918100000000410B0A1981.111111111111.00 broadcast
ip 171.69.214.42 atm-nsap 47.00918100000000410B0A1981.222222222222.00 broadcast
ip 171.69.214.43 atm-nsap 47.00918100000000410B0A1981.333333333333.00 broadcast
Administratively Scoped Boundary Example
The following example shows how to set up a boundary for all administratively scoped addresses:
access-list 1 deny 239.0.0.0 0.255.255.255
access-list 1 permit 224.0.0.0 15.255.255.255
interface ethernet 0
ip multicast boundary 1
IP Multicast Helper Example
Figure 73 illustrates how a helper address on two routers converts from broadcast to multicast and back
to broadcast.
Figure73 IP Multicast Helper Scenario
The configuration on the first hop router converts a broadcast stream arriving at incoming Ethernet
interface 0 destined for UDP port 4000 to a multicast stream. The access list denies other traffic from
being forwarded into the multicast cloud. The traffic is sent to group address 224.5.5.5. Because fast
switching does not perform such a conversion, the ip forward-protocol global configuration command
causes the proper process level to perform the conversion.
The second configuration on the last hop router converts the multicast stream at Ethernet interface 2 back
to broadcast. Again, all multicast traffic emerging from the multicast cloud should not be converted to
broadcast, only the traffic destined for UDP port 4000.
Router A
Router B
Broadcast-only
LAN or internet Broadcast-only
LAN or internet
43282
Broadcast
traffic
First hop
router
Router C
Last hop
router
178.21.34.0
178.21.34.15
Client
UDP
port 4000
Ethernet 0
Ethernet 2
Ethernet 1
IP multicast network cloud
Broadcast
traffic Client