IPTV / IGMP / Multicast / HP 5412zl

[cenk sasmaztin]

hi Darren
I can see many error log on your switch for PIM

I think you make Enable
Rendezvous Point on switch (statically)

for example
5406zl_A(config)# router pim
5406zl_A(pim)# rp-candidate source-vlan 68(must be server vlan)

5406zl_A# show ip pim rp-candidate
Status and Counters - PIM-SM Candidate-RP Information
C-RP Admin Status : This system is a Candidate-RP
C-RP Address : 10.1.68.1
C-RP Hold Time : 150
C-RP Advertise Period : 60
C-RP Priority : 192
C-RP Source IP VLAN : 68
Group Address Group Mask
--------------- ---------------
224.0.0.0 240.0.0.0

cenk
-----------------------------------------
your error log
E 08/06/08 00:17:55 00630 PIM: No RP for group 224.0.1.24(2533)
E 08/06/08 00:18:11 00630 PIM: No RP for group 239.255.2.2(1900)
E 08/06/08 00:18:50 00630 PIM: No RP for group 239.255.255.250(66358)
E 08/06/08 00:18:56 00630 PIM: No RP for group 224.0.1.24(2594)
E 08/06/08 00:19:12 00630 PIM: No RP for group 239.255.2.2(1961)
E 08/06/08 00:19:50 00630 PIM: No RP for group 239.255.255.250(66478)
E 08/06/08 00:19:56 00630 PIM: No RP for group 224.0.1.24(2654)
E 08/06/08 00:20:12 00630 PIM: No RP for group 239.255.2.2(2021)
E 08/06/08 00:20:50 00630 PIM: No RP for group 239.255.255.250(66598)
E 08/06/08 00:20:56 00630 PIM: No RP for group 224.0.1.24(2714)
E 08/06/08 00:21:12 00630 PIM: No RP for group 239.255.2.2(2081)
E 08/06/08 00:21:50 00630 PIM: No RP for group 239.255.255.250(66718)

[Darren Tickle]

Thanks for the reply again.

Ive attached a new show tech now i have made the changes. Sadly its still not working :(

[Darren Tickle]

I notice im still getting

"PIM: No RP for group 239.255.255.250(134963)"

[cenk sasmaztin]

please you read


----------------------------------------
Enable IP Multicast Routing
and PIM Sparse
----------------------------------------

5406zl_A(config)# ip routing
5406zl_A(config)# ip multicast-routing
5406zl_A(config)# router pim
5406zl_A(pim)# vlan 65
5406zl_A(vlan-65)# ip pim-sparse
5406zl_A(vlan-65)# vlan 68
5406zl_A(vlan-68)# ip pim-sparse
5406zl_A(vlan-68)# vlan 200
5406zl_A(vlan-200)# ip igmp
5406zl_A(vlan-200)# ip pim-sparse

â ¢ Enable PIM at the global configuration and VLAN configuration context
Global: IP routing, IP multicast, RIP, PIM
VLAN 65: RIP, PIM
VLAN 68: RIP, PIM
VLAN 200: IGMP, PIM
VLAN 65
VLAN 68
VLAN 200
5406zl_A
VLAN 200 (Layer 2 link)
VLAN 200: IGMP
2824
â ¢ Enable IP unicast and multicast routing within the global configuration
context
IP multicast routing is enabled at the global configuration level on the ProVision
ASIC switches. PIM routing can work with either dynamic or static IP unicast
routing. A multicast-enabled router will not be able to add or remove itself from
the multicast distribution tree without an entry for the source network in its unicast
IP route table.
A multicast router also needs a multicast routing protocol enabled to provide a
standard method to communicate with other multicast routers. ProVision ASIC
switches can use PIM Dense or PIM Sparse to establish relationships with other
routers, learn about available multicast groups, and to send Graft, Join, and Prune
messages to upstream routers.
PIM is enabled globally and is also enabled within the VLAN configuration
context for networks that will support end users and also for networks that lead to
PIM neighbors, any links that will carry multicast traffic between routers and lead
to IGMP hosts. Of course, IGMP also must be enabled on VLANs that connect to
potential group members, as described earlier in this module. In this case, VLAN
200 connects to a Layer 2 switch that has IGMP enabled. Without IGMP on this
VLAN, IGMP joins issued by hosts connected to the 2824 switch would not cause
the multicast traffic to be sent to those hosts.
As with OSPF and other protocols that use a Hello mechanism to establish and
maintain neighbor relationships, the ProCurve switch PIM implementation offers
the show ip pim neighbor command to provide information about PIM topologies.
To configure IGMP high-priority forwarding for a VLAN, issue the following
command: vlan ip igmp high-priority-forward.
Supporting IP Multicast

-------------------------------------------
PIM Sparse: Enable Rendezvous Point Candidate
-------------------------------------------

PIM Sparse: Enable
Rendezvous Point Candidate
5406zl_A(config)# router pim
5406zl_A(pim)# rp-candidate source-vlan 68
â ¢ Optionally enable Rendezvous Point candidacy within the PIM router
configuration context
Student Guide: 7â 49
â ¢ The routing switch uses IP address associated with source-vlan
parameter in its RP-Candidate advertisements
5406zl_A# show ip pim rp-candidate
Status and Counters - PIM-SM Candidate-RP Information
C-RP Admin Status : This system is a Candidate-RP
C-RP Address : 10.1.68.1
C-RP Hold Time : 150
C-RP Advertise Period : 60
C-RP Priority : 192
C-RP Source IP VLAN : 68
Group Address Group Mask

224.0.0.0 240.0.0.0
Not all PIM routers will be suitable candidates for Rendezvous Point. This PIM
router has been configured as an RP candidate for the entire range of multicast
addresses. In the show ip pim rp-candidate output, notice that the address
associated with this RP and its candidate advertisements is the address associated
with VLAN 68. The rp-candidate command requires a source VLAN to provide
an IP address for the RP candidate. The default priority for RP candidates is 192. If
you define a lower priority using the command rp-candidate priority , it
will make this router less likely to become the RP than other routers with a default
priority setting.
Because no Bootstrap Router has been defined, the distribution tree cannot be
built. This is because of the Bootstrap routerâ s responsibility to supply all PIM
Sparse routers in the domain with RP Candidate information.
Building ProCurve Resilient, Adaptive Networks

-------------------------------------------
PIM Sparse: Specify Range for RP Candidate
-------------------------------------------

PIM Sparse: Specify Range for
RP Candidate

â ¢ To cause this routing switch to advertise RP candidacy for the
multicast address range 239.32.0.0 â 239.63.255.255
5406zl_A(pim)# rp-candidate source-vlan 68 group-prefix
239.32.0.0/11
5406zl_A(pim)# show ip pim rp-candidate
Status and Counters - PIM-SM Candidate-RP Information
C-RP Admin Status : This system is a Candidate-RP
C-RP Address : 10.1.68.1
C-RP Hold Time : 150
C-RP Advertise Period : 60
C-RP Priority : 192
C-RP Source IP VLAN : 68
Group Address Group Mask
--------------- ---------------
224.0.0.0 240.0.0.0
239.32.0.0 255.224.0.0


This router has now been configured to advertise RP candidacy for a smaller range
of multicast addresses, in addition to the range defined earlier. As an RP-candidate
for a smaller group as well as a larger group, this router might be elected for the
smaller range of addresses but remain an RP candidate for the larger address
range.
Note that the priority setting is per-router, not per multicast address range. This
routerâ s RP candidate advertisements for both ranges will use the priority value
192.

[Darren Tickle]

Thanks again for the information. As far as i can see I have got it setup the same as how your expample shows.

Ive taken out my access lists just incase of any problems there and i have attached a new show tech. If anyone could see the problem that would be great.

[Darren Tickle]

Thx guys for all the help i got it working.

was missing a IP Route :)