----------------
This is a protocol for communication multicast information between routers. The way it works is that any pim enabled interface in dense mode will recieve the multicast traffic it is then up to the interface to see if it has clients listening for the relevant multicast group if not it prunes the traffic. The flooding is intermittent.
RFC 3973
Use PUSH model or implicit join
- called flood and prune
- all traffic flooded through out entire network
- router that have no recursive prune (unjoin) unused links
Only suitable for small multicast implementations
- doesnt scale becaue of flooding and (S,G) state creation
PIM DENSE MODE OPERATION
-------------------------
Discover PIM neighbors
- 224.0.0.13 (PIM) to find neighbors on attached links
-flood all multicast traffic
-prune unwanted traffic
-multicast table maintenance
- graft
-assert
-state refresh
PIM uses protocol number 103
IGMP is protocol number 2
TO see if a link quickly supports multicast you could just ping 255.255.255.255 (all hosts
address)
if you recieve reply from recievers you know it supports it
TO enable
ip multicast-routing
on some switches they run multicasting on distributed cards so you need to specify this
ip multicast-routing distributed
sh ip pim interfaces - see what interfaces pim is enabled ion
Typically all interfaces that are running ip should have multicast enabled
Typically you do not run pim on the loopback interface The only time you really would if you
are RP and the loopback is the RP address
if using subinterfaces PIM needs to be enabled on the subint not the main int
Also on lan facing interfaces you need to enable pim as this also enables igmp there is no
other command for enabling igmp
WHen a reciever sends an igmp join to the group. The pim router servicing that segment will
add *,G in the multicast table for the mulitcast group.
Once it starts recieving traffic for that group it will add
(S,G) adding the source address the multicast traffic is coming from
When you look at the mroute of this you will also see a rpf neighbor
The rpf neighbor as previously discussed is used for loopchecking it will check that the
interface
recieved the traffic on is the interface the igp has in the table for the source address.
RFP address is also used for communication via PIM this neighbor i would send my pim control
plane messages (pim join etc) it would be sent as multicast 224.0.0.13 but a field in the
payload
of the packet is rfp where we would put the unicast address of our neighbor.
This can issues in say non broadcast topologys with multipoint non meshed so a router could
possible set the next hop to the address of the source even though it does not have layer 2
reachability to it. It may have layer 3 reachability via a hun router but 224.0.0. is link
local
meaning it has ttl of 1 so when the hub recieves it will not forward it on so we could have
situation
where the upstream rfp is not getting the pim messages.
PIM DENSE MODE FLOODING
-----------------------
Router attached to LAN listen for senders
- sender does not communucate multicast control plane
Once traffic is recieved
- insert (*,G) and (S,G) into routing table
- incoming interface is attached to sender
- oil is all other pim interface
- flood traffic to oil
Next downstream router continue the process
flooding results in shortest path tree (Spt)
- if the rpf fail a prune message is sent from that interface
PIM DENSE MODE ASSERT
---------------------
Used to prune duplicate multicast feed transmissions
-Typically needed when multiple routers attached to same multicast enabled LAN
-Triggered when (S,G) feed is recieved in an interface already in the oil
-Assert winner determined by
- lowest metric to source
-Highest Ip address if metric is equal
PIM DENSE MODE GRAFT
--------------------
What happens if i have a pruned an (S,G) but then i recieve an IGMP join from the reciever
Graft message used as dense mode "join" to un prune (S,G) from upstream neighbor
- Graft continues up reverse path back towards source until the tree is rebuilt
-Used to speed up convergence and not wait for perodic flooding
So bacially host doing a join from unpreviously pruned linked
PIM DENSE MODE STATE REFESH
----------------------------
Normally once an (S,G) is pruned traffic is reflooded about every 3 minutes
- Limits scalability of dense mode
State refresh is a keepalive for prune state
- originated by root of the SPT
-if downstream routers agree traffic is not reflooded
-still does not fix (S,G) state information in the routing table
LAB
----
OK for the lab SW3 will be the sender and R4 will be one of the recievers. We will set PIM
DENSE Mode in the full topology
The first thing as always you verify layer 3 reachabilty to ensure that you have no
underlying lower layer problems in the topology
by going to each interface and pinging
s3#ping 155.0.79.1
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 155.0.79.1, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 1/1/1 ms
s3#
i will do this for the rest of the topology
next starting on s3 i need to enable mulitcasting globally and on the interfaces
s3
---
s3(config)#ip multicast-routing distributed
s3(config)#int vlan 9
s3(config-if)#ip pim dense-mode
s3(config)#int vlan 79
s3(config-if)#ip pim dense-mode
s3(config-if)#
r4
---
r4(config)#ip multicast-routing
r4(config)#int fa0/1
r4(config-if)#ip pim dense-mode
r4(config-if)#int fa0/0
r4(config-if)#ip pim dense-mode
r4(config-if)#int s0/0/0
r4(config-if)#ip pim dense-mode
r4(config-if)#
r4(config-if)#int s0/1/0
r4(config-if)#ip pim dense-mode
r4(config-if)#
so basically i am going to repeat this on every router + ip interface in the toplogy
so it is distributed on the switches as they use there line cards for multicasting
we even enable on lan facing interface as ip pim enables igmp also
just configuring my way through doing r1 at the moment
R1
---
just though debug ip igmp
you see we enable pim dense mode and igmp v2 query is sent it found a PIM neighbor 155.0.13.3
which is r3
Interestingly enough even tough it dense mode it joins the multicast group for RP rendevous
point which is sparse mode technology this is tandard
r1(config-if)#int s0/1
r1(config-if)#ip pim dense-mode
r1(config-if)#
*Mar 1 03:22:44.859: IGMP(0): Send v2 init Query on Serial0/1
*Mar 1 03:22:44.871: %PIM-5-NBRCHG: neighbor 155.0.13.3 UP on interface Serial0/1
*Mar 1 03:22:54.127: IGMP(0): Send v2 general Query on FastEthernet0/0
*Mar 1 03:22:54.127: IGMP(0): Set report delay time to 4.4 seconds for 224.0.1.40 on
FastEthernet0/0
*Mar 1 03:22:55.127: IGMP(0): Send v2 general Query on Serial0/0
*Mar 1 03:22:59.127: IGMP(0): Send v2 Report for 224.0.1.40 on FastEthernet0/0
*Mar 1 03:22:59.127: IGMP(0): Received v2 Report on FastEthernet0/0 from 155.0.146.1 for
224.0.1.40
*Mar 1 03:22:59.127: IGMP(0): Received Group record for group 224.0.1.40, mode 2 from
155.0.146.1 for 0 sources
*Mar 1 03:22:59.127: IGMP(0): Updating EXCLUDE group timer for 224.0.1.40
*Mar 1 03:22:59.127: IGMP(0): MRT Add/Update FastEthernet0/0 for (*,224.0.1.40) by 0
OK so the topology is configured in dense mode
r4
---
r4#sh ip mroute
IP Multicast Routing Table
Flags: 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,
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
Outgoing interface flags: H - Hardware switched, A - Assert winner
Timers: Uptime/Expires
Interface state: Interface, Next-Hop or VCD, State/Mode
(*, 224.0.1.40), 00:23:31/00:02:54, RP 0.0.0.0, flags: DCL
Incoming interface: Null, RPF nbr 0.0.0.0
Outgoing interface list:
Serial0/1/0, Forward/Dense, 00:03:31/00:00:00
Serial0/0/0, Forward/Dense, 00:17:11/00:00:00
FastEthernet0/1, Forward/Dense, 00:23:31/00:00:00
we notice the only route we have *,224.0.1.40 which is for rp
this is the same currently on all network devices
OK we will do a simulation with r4 being the client or reciver and s3 being the source
so first of all on r4 we will put debugs on
r4#debug ip mp
IP multicast packets debugging is on
r4#debug ip igmp
IGMP debugging is on
r4#
r4
--
r4(config)#int fa0/0
r4(config-if)#ip igmp join-group 224.1.1.1
r4(config-if)#
we have done a igmp join group on r4
Feb 11 11:43:50.783: IGMP(0): WAVL Insert group: 224.1.1.1 interface:
FastEthernet0/0Successful
*Feb 11 11:43:50.783: IGMP(0): Send v2 Report for 224.1.1.1 on FastEthernet0/0
*Feb 11 11:43:50.783: IGMP(0): Received v2 Report on FastEthernet0/0 from 172.25.13.4 for
224.1.1.1
*Feb 11 11:43:50.783: IGMP(0): Received Group record for group 224.1.1.1, mode 2 from
172.25.13.4 for 0 sources
*Feb 11 11:43:50.783: IGMP(0): Switching to EXCLUDE mode for 224.1.1.1 on FastEthernet0/0
*Feb 11 11:43:50.783: IGMP(0): Updating EXCLUDE group timer for 224.1.1.1
*Feb 11 11:43:50.783: IGMP(0): MRT Add/Update FastEthernet0/0 for (*,224.1.1.1) by 0
*Feb 11 11:43:50.787: IGMP(0): MRT Add/Update FastEthernet0/0 for (*,224.1.1.1) by 4
from the debug we have sent a report to join the group
r4#sh ip mroute
IP Multicast Routing Table
Flags: 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,
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
Outgoing interface flags: H - Hardware switched, A - Assert winner
Timers: Uptime/Expires
Interface state: Interface, Next-Hop or VCD, State/Mode
(*, 224.1.1.1), 00:02:15/00:02:04, RP 0.0.0.0, flags: DCL
Incoming interface: Null, RPF nbr 0.0.0.0
Outgoing interface list:
Serial0/1/0, Forward/Dense, 00:02:15/00:00:00
Serial0/0/0, Forward/Dense, 00:02:15/00:00:00
FastEthernet0/0, Forward/Dense, 00:02:15/00:00:00
FastEthernet0/1, Forward/Dense, 00:02:15/00:00:00
(*, 224.0.1.40), 00:29:17/00:02:10, RP 0.0.0.0, flags: DCL
Incoming interface: Null, RPF nbr 0.0.0.0
Outgoing interface list:
Serial0/1/0, Forward/Dense, 00:09:17/00:00:00
Serial0/0/0, Forward/Dense, 00:22:57/00:00:00
FastEthernet0/1, Forward/Dense, 00:29:17/00:00:00
r4#
we now have a new entry for 224.1.1.1 in the mroute table it is
*.224.1.1.1 we have no rp or incoming interface as we have not recived traffic for it
s1
---
s1#sh ip mroute
IP Multicast Routing Table
Flags: 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,
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
Outgoing interface flags: H - Hardware switched, A - Assert winner
Timers: Uptime/Expires
Interface state: Interface, Next-Hop or VCD, State/Mode
(*, 224.0.1.40), 00:27:15/00:02:23, RP 0.0.0.0, flags: DCL
Incoming interface: Null, RPF nbr 0.0.0.0
Outgoing interface list:
FastEthernet0/3, Forward/Dense, 00:24:31/00:00:00
Vlan67, Forward/Dense, 00:25:29/00:00:00
Vlan79, Forward/Dense, 00:27:15/00:00:00
other devices in the transit path have not added an entry for this group this is normal
sw3
---
s3>en
s3#ping
Protocol [ip]: ip
Target IP address: 224.1.1.1
Repeat count [1]: 10000
Datagram size [100]:
Timeout in seconds [2]:
Extended commands [n]:
Sweep range of sizes [n]:
Type escape sequence to abort.
Sending 10000, 100-byte ICMP Echos to 224.1.1.1, timeout is 2 seconds:
Reply to request 0 from 155.0.146.4, 1 ms
Reply to request 1 from 155.0.146.4, 1 ms
Reply to request 2 from 155.0.146.4, 1 ms
Reply to request 3 from 155.0.146.4, 8 ms
Reply to request 4 from 155.0.146.4, 1 ms
Reply to request 5 from 155.0.146.4, 1 ms
Reply to request 6 from 155.0.146.4, 1 ms
Reply to request 7 from 155.0.146.4, 8 ms
Reply to request 8 from 155.0.146.4, 1 ms
Reply to request 9 from 155.0.146.4, 1 ms
Reply to request 10 from 155.0.146.4, 1 ms
Reply to request 11 from 155.0.146.4, 8 ms
Reply to request 12 from 155.0.146.4, 1 ms
Reply to request 13 from 155.0.146.4, 1 ms
I am sending traffic now to this group
r4#
*Feb 11 11:50:20.363: IP(0): s=155.0.79.3 (FastEthernet0/1) d=224.1.1.1 (FastEthernet0/0)
id=42, ttl=252, prot=1, len=100(100), mforward
*Feb 11 11:50:22.367: IP(0): s=155.0.79.3 (FastEthernet0/1) d=224.1.1.1 (FastEthernet0/0)
id=43, ttl=252, prot=1, len=100(100), mforward
*Feb 11 11:50:24.371: IP(0): s=155.0.79.3 (FastEthernet0/1) d=224.1.1.1 (FastEthernet0/0)
id=44, ttl=252, prot=1, len=100(100), mforward
*Feb 11 11:50:26.379: IP(0): s=155.0.79.3 (FastEthernet0/1) d=224.1.1.1 (FastEthernet0/0)
id=45, ttl=252, prot=1, len=100(100), mforward
*Feb 11 11:50:28.383: IP(0): s=155.0.79.3 (FastEthernet0/1) d=224.1.1.1 (FastEthernet0/0)
id=46, ttl=252, prot=1, len=100(100), mforward
*Feb 11 11:50:30.387: IP(0): s=155.0.79.3 (FastEthernet0/1) d=224.1.1.1 (FastEthernet0/0)
id=47, ttl=252, prot=1, len=100(100), mforward
we are getting the traffic on r4
and reply on s3 only from r4
Reply to request 79 from 155.0.146.4, 9 ms
Reply to request 80 from 155.0.146.4, 1 ms
Reply to request 804 from 155.0.146.4, 1 ms
Reply to request 805 from 155.0.146.4, 1 ms
Reply to request 806 from 155.0.146.4, 1 ms
Reply to request 807 from 155.0.146.4, 9 ms
Reply to request 808 from 155.0.146.4, 1 ms
as it is the only interface listening for the group
r4#sh ip mroute
IP Multicast Routing Table
Flags: 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,
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
Outgoing interface flags: H - Hardware switched, A - Assert winner
Timers: Uptime/Expires
Interface state: Interface, Next-Hop or VCD, State/Mode
(*, 224.1.1.1), 00:35:21/stopped, RP 0.0.0.0, flags: DCL
Incoming interface: Null, RPF nbr 0.0.0.0
Outgoing interface list:
Serial0/1/0, Forward/Dense, 00:35:21/00:00:00
Serial0/0/0, Forward/Dense, 00:35:21/00:00:00
FastEthernet0/0, Forward/Dense, 00:35:21/00:00:00
FastEthernet0/1, Forward/Dense, 00:35:21/00:00:00
(155.0.79.3, 224.1.1.1), 00:30:06/00:03:01, flags: LT
Incoming interface: FastEthernet0/1, RPF nbr 155.0.146.6
Outgoing interface list:
FastEthernet0/0, Forward/Dense, 00:30:06/00:00:00
Serial0/0/0, Prune/Dense, 00:00:01/00:02:58
Serial0/1/0, Prune/Dense, 00:30:06/00:03:01, A
(*, 224.0.1.40), 01:02:23/00:02:02, RP 0.0.0.0, flags: DCL
Incoming interface: Null, RPF nbr 0.0.0.0
Outgoing interface list:
Serial0/1/0, Forward/Dense, 00:42:23/00:00:00
Serial0/0/0, Forward/Dense, 00:56:05/00:00:00
FastEthernet0/1, Forward/Dense, 01:02:26/00:00:00
notice we know have a source specifc route for 224.1.1.1
if this was real network seceneio we would source the route from vlan 9 the access facing
subnet
if we look at the source specfic route
(155.0.79.3, 224.1.1.1), 00:39:44/00:02:59, flags: LT
Incoming interface: FastEthernet0/1, RPF nbr 155.0.146.6
Outgoing interface list:
FastEthernet0/0, Forward/Dense, 00:39:44/00:00:00
Serial0/0/0, Prune/Dense, 00:00:38/00:02:21
Serial0/1/0, Prune/Dense, 00:39:44/00:02:24, A
we have RPF neighbor of R6 this was decided by our routing underlying igp
r4#sh ip route 155.0.79.3
Routing entry for 155.0.79.0/24
Known via "eigrp 1", distance 90, metric 30976, type internal
Redistributing via eigrp 1
Last update from 155.0.146.6 on FastEthernet0/1, 01:32:58 ago
Routing Descriptor Blocks:
* 155.0.146.6, from 155.0.146.6, 01:32:58 ago, via FastEthernet0/1
Route metric is 30976, traffic share count is 1
Total delay is 210 microseconds, minimum bandwidth is 100000 Kbit
Reliability 255/255, minimum MTU 1500 bytes
Loading 1/255, Hops 2
so we would reject this traffic from other interfaces
P 155.0.79.0/24, 1 successors, FD is 30976
via 155.0.146.6 (30976/28416), FastEthernet0/1
via 155.0.0.3 (2172672/28416), Serial0/0/0
in the eigrp table we have 2 routes to
also now we have generated traffic all routers have specfic mroute for this
s1
---
s1#sh ip mroute
IP Multicast Routing Table
Flags: 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,
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
Outgoing interface flags: H - Hardware switched, A - Assert winner
Timers: Uptime/Expires
Interface state: Interface, Next-Hop or VCD, State/Mode
(*, 224.1.1.1), 00:54:20/stopped, RP 0.0.0.0, flags: D
Incoming interface: Null, RPF nbr 0.0.0.0
Outgoing interface list:
FastEthernet0/3, Forward/Dense, 00:54:20/00:00:00
Vlan67, Forward/Dense, 00:54:20/00:00:00
Vlan79, Forward/Dense, 00:54:20/00:00:00
(155.0.79.3, 224.1.1.1), 00:54:20/00:02:59, flags: T
Incoming interface: Vlan79, RPF nbr 0.0.0.0
Outgoing interface list:
Vlan67, Forward/Dense, 00:00:01/00:00:00
FastEthernet0/3, Forward/Dense, 00:42:16/00:00:00
(*, 224.0.1.40), 01:23:08/00:02:51, RP 0.0.0.0, flags: DCL
Incoming interface: Null, RPF nbr 0.0.0.0
Outgoing interface list:
FastEthernet0/3, Forward/Dense, 01:20:24/00:00:00
Vlan67, Forward/Dense, 01:21:22/00:00:00
Vlan79, Forward/Dense, 01:23:08/00:00:00
R5
---
r5#sh ip mroute
IP Multicast Routing Table
Flags: 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,
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
Outgoing interface flags: H - Hardware switched, A - Assert winner
Timers: Uptime/Expires
Interface state: Interface, Next-Hop or VCD, State/Mode
(*, 224.1.1.1), 00:55:11/stopped, RP 0.0.0.0, flags: D
Incoming interface: Null, RPF nbr 0.0.0.0
Outgoing interface list:
Serial0/1/0, Forward/Dense, 00:55:11/00:00:00
Serial0/0/0, Forward/Dense, 00:55:11/00:00:00
FastEthernet0/0, Forward/Dense, 00:55:11/00:00:00
(155.0.79.3, 224.1.1.1), 00:03:53/00:02:13, flags: T
Incoming interface: Serial0/0/0, RPF nbr 155.0.0.3
Outgoing interface list:
FastEthernet0/0, Forward/Dense, 00:03:53/00:00:00
Serial0/1/0, Prune/Dense, 00:00:49/00:02:13, A
(*, 224.0.1.40), 01:07:59/00:01:56, RP 0.0.0.0, flags: DCL
Incoming interface: Null, RPF nbr 0.0.0.0
Outgoing interface list:
Serial0/1/0, Forward/Dense, 01:07:28/00:00:00
Serial0/0/0, Forward/Dense, 01:07:42/00:00:00
FastEthernet0/0, Forward/Dense, 01:07:59/00:00:00
r4(config)#int fa0/1
r4(config-if)#shut
r4(config-if)#
(vrf default) non DR
*Feb 11 12:36:47.587: MRT(0): Delete Serial0/0/0/224.1.1.1 from the olist of (155.0.79.3,
224.1.1.1)
*Feb 11 12:36:47.587: MRT(0): set min mtu for (155.0.79.3, 224.1.1.1) 1500->1500
*Feb 11 12:36:47.587: MRT(0): WAVL Insert interface: FastEthernet0/1 in
(155.0.79.3,224.1.1.1) Successful
*Feb 11 12:36:47.587: MRT(0): set min mtu for (155.0.79.3, 224.1.1.1) 1500->1500
*Feb 11 12:36:47.587: MRT(0): Add FastEthernet0/1/224.1.1.1 to the olist of (155.0.79.3,
224.1.1.1), Forward state - MAC built
*Feb 11 12:36:49.039: MRT(0): Delete FastEthernet0/1/224.1.1.1 from (155.0.79.3/32,
224.1.1.1)
*Feb 11 12:36:49.039: MRT(0): Delete FastEthernet0/1/224.1.1.1 from the olist of (155.0.79.3,
224.1.1.1)
*Feb 11 12:36:49.039: MRT(0): set min mtu for (155.0.79.3, 224.1.1.1) 1500->1500
*Feb 11 12:36:49.039: MRT(0): Delete FastEthernet0/1/224.1.1.1 from (*, 224.1.1.1)
*Feb 11 12:36:49.039: MRT(0): Delete FastEthernet0/1/224.1.1.1 from the olist of (*,
224.1.1.1)
*Feb 11 12:36:49.039: MRT(0): set min mtu for (0.0.0.0, 224.1.1.1) 1500->1500
*Feb 11 12:36:49.075: %LINK-5-CHANGED: Interface FastEthernet0/1, changed state to
administratively down
*Feb 11 12:36:50.039: MRT(0): Delete FastEthernet0/1/224.0.1.40 from (*, 224.0.1.40)
*Feb 11 12:36:50.039: MRT(0): Delete FastEthernet0/1/224.0.1.40 from the olist of (*,
224.0.1.40)
*Feb 11 12:36:50.039: MRT(0): set min mtu for (0.0.0.0, 224.0.1.40) 1500->1500
*Feb 11 12:36:50.075: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/1,
changed state to down
*Feb 11 12:37:12.743: IGMP(0): Send v2 general Query on FastEthernet0/0
*Feb 11 12:37:12.743: IGMP(0): Set report delay time to 9.0 seconds for 224.1.1.1 on
FastEthernet0/0
*Feb 11 12:37:12.743: IGMP(0): Set report delay time to 4.9 seconds for 224.0.1.40 on
FastEthernet0/0
*Feb 11 12:37:14.655: IGMP(0): Received v2 Query on Serial0/0/0 from 155.0.0.1
*Feb 11 12:37:17.743: IGMP(0): Send v2 Report for 224.0.1.40 on FastEthernet0/0
*Feb 11 12:37:17.743: IGMP(0): Received v2 Report on FastEthernet0/0 from 172.25.13.4 for
224.0.1.40
*Feb 11 12:37:17.743: IGMP(0): Received Group record for group 224.0.1.40, mode 2 from
172.25.13.4 for 0 sources
*Feb 11 12:37:17.743: IGMP(0): Updating EXCLUDE group timer for 224.0.1.40
*Feb 11 12:37:17.743: IGMP(0): MRT Add/Update FastEthernet0/0 for (*,224.0.1.40) by 0
*Feb 11 12:37:17.743: MRT(0): Update (*,224.0.1.40), RPF /0.0.0.0
*Feb 11 12:37:17.743: MRT(0): Update FastEthernet0/0/224.0.1.40 in the olist of (*,
224.0.1.40), Forward state - MAC built
*Feb 11 12:37:21.743: IGMP(0): Send v2 Report for 224.1.1.1 on FastEthernet0/0
*Feb 11 12:37:21.743: IGMP(0): Received v2 Report on FastEthernet0/0 from 172.25.13.4 for
224.1.1.1
*Feb 11 12:37:21.743: IGMP(0): Received Group record for group 224.1.1.1, mode 2 from
172.25.13.4 for 0 sources
*Feb 11 12:37:21.743: IGMP(0): Updating EXCLUDE group timer for 224.1.1.1
*Feb 11 12:37:21.743: IGMP(0): MRT Add/Update FastEthernet0/0 for (*,224.1.1.1)
r4#sh ip mroute
IP Multicast Routing Table
Flags: 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,
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
Outgoing interface flags: H - Hardware switched, A - Assert winner
Timers: Uptime/Expires
Interface state: Interface, Next-Hop or VCD, State/Mode
(*, 224.1.1.1), 01:02:04/stopped, RP 0.0.0.0, flags: DCL
Incoming interface: Null, RPF nbr 0.0.0.0
Outgoing interface list:
FastEthernet0/0, Forward/Dense, 00:10:13/00:00:00
Serial0/1/0, Forward/Dense, 01:02:04/00:00:00
Serial0/0/0, Forward/Dense, 01:02:04/00:00:00
(155.0.79.3, 224.1.1.1), 00:05:31/00:02:59, flags: LT
Incoming interface: Serial0/0/0, RPF nbr 155.0.0.3
Outgoing interface list:
Serial0/1/0, Prune/Dense, 00:02:27/00:00:32
FastEthernet0/0, Forward/Dense, 00:05:31/00:00:00
(*, 224.0.1.40), 01:29:06/00:02:23, RP 0.0.0.0, flags: DCL
Incoming interface: Null, RPF nbr 0.0.0.0
Outgoing interface list:
FastEthernet0/0, Forward/Dense, 00:09:08/00:00:00
Serial0/1/0, Forward/Dense, 01:09:06/00:00:00
Serial0/0/0, Forward/Dense, 01:22:46/00:00:00
we can s0/0/0 becomes the source interface and is removed from the oil list so this is where
th traffic is recived on and no longer pruned
r4#sh ip route 155.0.67.0
Routing entry for 155.0.67.0/24
Known via "eigrp 1", distance 90, metric 2172672, type internal
Redistributing via eigrp 1
Last update from 155.0.0.3 on Serial0/0/0, 00:10:13 ago
Routing Descriptor Blocks:
* 155.0.0.3, from 155.0.0.3, 00:10:13 ago, via Serial0/0/0
Route metric is 2172672, traffic share count is 1
Total delay is 20110 microseconds, minimum bandwidth is 1544 Kbit
Reliability 255/255, minimum MTU 1500 bytes
Loading 1/255, Hops 2
r4#
based on the underlying igp reconvergence
ok we no a no shut on int fa0/1
OK no fa0/1 is backup we begin to build a graft message to unprune the interface to allow to
be the source of the multicast traffic on the router
Feb 11 12:57:36.295: PIM(0): Building Graft message for 224.1.1.1, FastEthernet0/1: no
entries
*Feb 11 12:57:36.295: PIM(0): Building Graft message for 224.1.1.1, Serial0/1/0: no entries
*Feb 11 12:57:36.295: PIM(0): Building Graft message for 224.1.1.1, Serial0/0/0: no entries
*Feb 11 12:57:36.523: IP(0): s=155.0.79.3 (FastEthernet0/1) d=224.1.1.1 (Serial0/0/0)
id=2055, ttl=252, prot=1, len=100(100), mforward
*Feb 11 12:57:36.523: IP(0): s=155.0.79.3 (FastEthernet0/1) d=224.1.1.1 (FastEthernet0/0)
id=2055, ttl=252, prot=1, len=100(100), mforward
We recieve an asset meesage from R3 with it metric and r3 loses so it pruned
*Feb 11 12:57:36.683: PIM(0): Received v2 Assert on Serial0/0/0 from 155.0.0.3
*Feb 11 12:57:36.683: PIM(0): Assert metric to source 155.0.79.3 is [90/28416]
*Feb 11 12:57:36.683: PIM(0): We lose, our metric [90/30976]
*Feb 11 12:57:36.683: PIM(0): Prune Serial0/0/0/224.1.1.1 from (155.0.79.3/32, 224.1.1.1)
so we look at adding fa0/1 back to the forward state
*Feb 11 12:57:54.455: PIM(0): Add FastEthernet0/1/155.0.146.1 to (*, 224.1.1.1), Forward
state, by PIM *G Join
Feb 11 12:57:54.455: PIM(0): Update FastEthernet0/1/155.0.146.1 to (*, 224.0.1.40), Forward
state, by PIM *G Join
No comments:
Post a Comment