From: Brian McGahan (bmcgahan@internetworkexpert.com)
Date: Sun Sep 04 2005 - 01:40:49 GMT-3
> It seems to be working correctly, but I found it weird the absence of
the
> source on the result of show ip mroute.
The point of bidirectional pim is that you do not install (S,G)
pairs, instead you install just (*,G) pairs. The feature is used for
networks with a lot of multicast sources.
HTH,
Brian McGahan, CCIE #8593
bmcgahan@internetworkexpert.com
Internetwork Expert, Inc.
http://www.InternetworkExpert.com
Toll Free: 877-224-8987 x 705
Outside US: 775-826-4344 x 705
24/7 Support: http://forum.internetworkexpert.com
Live Chat: http://www.internetworkexpert.com/chat/
> -----Original Message-----
> From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf
Of
> gladston@br.ibm.com
> Sent: Saturday, September 03, 2005 1:53 PM
> To: ccielab@groupstudy.com
> Subject: Bidirectional PIM
>
> Is the result of 'ip mroute x.x.x.x' when using Bidirectional PIM this
> way?
>
> Rack2R11#sh ip mrou 239.6.6.6
>
> (*, 239.6.6.6), 00:41:34/00:02:55, RP 148.5.4.1, flags: BP
> Bidir-Upstream: FastEthernet3/0, RPF nbr 148.5.114.4
> Outgoing interface list:
> FastEthernet3/0, Bidir-Upstream/Sparse-Dense, 00:41:23/00:00:00
>
>
> It seems to be working correctly, but I found it weird the absence of
the
> source on the result of show ip mroute.
>
>
> **RP**
> R11------R4--------R2
>
> source---->(f0/0)R11(f3/0)------(f1/1.80)R4(s0/1)--------(s0/1)R2
>
>
> R4 is the RP.
> R2 joined the group 239.6.6.6
>
> When using PIM-SM I can see the register process.
> R11 receives the multicast from the source but there is no indication
that
> it forwards it to the RP when I see the result of 'show ip mrout
> 239.6.6.6; but 'debug ip mpacket' show that R11 is forwarding the
> multicast toward RP.
> Also, 'debug ip mpacket' on RP shows it is forwarding traffic toward
the
> receiver, R2.
>
>
> Rack2R4#sh ip mrou 239.6.6.6
>
> (*, 239.6.6.6), 00:30:28/00:02:58, RP 148.5.4.1, flags: BCL
> Bidir-Upstream: Null, RPF nbr 0.0.0.0
> Outgoing interface list:
> Loopback0, Forward/Sparse-Dense, 00:26:08/00:02:54
> Serial0/1, Forward/Sparse-Dense, 00:30:28/00:02:34
>
> Debug on R11
>
> Rack2R11(config-if)#deb ip mpack
>
> *Sep 3 12:15:07: IP(0): s=150.100.1.254 (FastEthernet0/0) d=239.6.6.6
> (FastEthernet3/0) id=1610, prot=1, len=100(100), mforward
> Rack2R11#
> *Sep 3 12:15:09: IP(0): s=150.100.1.254 (FastEthernet0/0) d=239.6.6.6
> (FastEthernet3/0) id=1611, prot=1, len=100(100), mforward
> Rack2R11#
> *Sep 3 12:15:11: IP(0): s=150.100.1.254 (FastEthernet0/0) d=239.6.6.6
> (FastEthernet3/0) id=1612, pr
>
>
> Debug on R4
>
> IP multicast packets debugging is on
> Rack2R4#
> *Mar 15 22:23:22: IP(0): s=150.100.1.254 (FastEthernet1/1.80)
d=239.6.6.6
> (Serial0/1) id=1689, prot=1, len=100(100), mforward
> Rack2R4#
> *Mar 15 22:23:24: IP(0): s=150.100.1.254 (FastEthernet1/1.80)
d=239.6.6.6
> (Serial0/1) id=1690, prot=1, len=100(100), mforward
> Rack2R4#
> *Mar 15 22:23:26: IP(0): s=150.100.1.254 (FastEthernet1/1.80)
d=239.6.6.6
> (Serial0/1) id=1691, prot=1, len=100(100), mforward
>
>
>
> R4 config:
>
> ip pim rp-address 24.24.24.24
> ip pim rp-address 148.5.4.1 5 bidir
>
>
> Rack2R4#sh ip pim ne
> PIM Neighbor Table
> Neighbor Interface Uptime/Expires Ver DR
> Address
> Prio/Mode
> 148.5.24.2 Serial0/1 00:35:23/00:01:16 v2 1 /
B S
> 148.5.114.11 FastEthernet1/1.80 00:49:54/00:01:33 v2 1 /
DR
> B S
>
>
> R2 config:
> ip pim bidir-enable
> ip pim rp-address 148.5.4.1 bidir
>
> Rack2R2#sh ip mrout 239.6.6.6
> (*, 239.6.6.6), 00:35:00/00:02:59, RP 148.5.4.1, flags: BCL
> Bidir-Upstream: Serial0/1, RPF nbr 148.5.24.4
> Outgoing interface list:
> Loopback0, Forward/Sparse-Dense, 00:35:00/00:02:58
> Serial0/1, Bidir-Upstream/Sparse-Dense, 00:35:00/00:00:00
>
>
> R11 config:
>
> ip pim bidir-enable
> ip pim rp-address 148.5.4.1 bidir
>
> Rack2R11#sh ip mrou 239.6.6.6
>
>
> (*, 239.6.6.6), 00:36:18/00:02:50, RP 148.5.4.1, flags: BP
> Bidir-Upstream: FastEthernet3/0, RPF nbr 148.5.114.4
> Outgoing interface list:
> FastEthernet3/0, Bidir-Upstream/Sparse-Dense, 00:36:08/00:00:00
>
>
This archive was generated by hypermail 2.1.4 : Sun Oct 02 2005 - 14:40:14 GMT-3