Re: Re: Multicast Loopback strange behaviour

From: <nrafia_at_gmail.com>
Date: Tue, 01 Dec 2009 14:53:21 +0000

hi thanks for your valued input...

output of ip mpacket detail on both

Aluminum#debug ip mpacket detail
IP multicast packets debugging is on (detailed)
Aluminum#ping 236.82.134.23

Type escape sequence to abort.
Sending 1, 100-byte ICMP Echos to 236.82.134.23, timeout is 2 seconds:

*Mar 1 00:07:04.107: IP(0): MAC sa=**Unknown SNPA type** (Loopback0)
*Mar 1 00:07:04.107: IP(0): IP tos=0x0, len=100, id=5, ttl=254, prot=1
*Mar 1 00:07:04.107: IP(0): s=172.16.1.1 (Loopback0) d=236.82.134.23
(Serial1/0) id=5, ttl=254, prot=1, len=100(100), mforward
Reply to request 0 from 172.16.2.241, 12 ms
Reply to request 0 from 172.16.2.241, 12 ms
Aluminum#

source is sending only traffic from loopback, which is emulating a host.

Iron#
*Mar 1 00:07:04.015: IP(0): MAC sa=*HDLC* (Serial1/0)
*Mar 1 00:07:04.015: IP(0): IP tos=0x0, len=100, id=5, ttl=251, prot=1
*Mar 1 00:07:04.035: IP(0): MAC sa=*HDLC* (Serial1/0)
*Mar 1 00:07:04.035: IP(0): IP tos=0x0, len=100, id=5, ttl=250, prot=1

on iron looback is emulating a host by using ip igmp join-group. its
sending to echo replies for each ping.

Aluminum#mstat 172.16.1.1 20.20.20.20 236.82.134.23
Type escape sequence to abort.
Mtrace from 172.16.1.1 to 20.20.20.20 via group 236.82.134.23
 From source (?) to destination (?)
Waiting to accumulate statistics......
Results after 10 seconds:

Source Response Dest Packet Statistics For Only For Traffic
172.16.1.1 172.16.1.1 All Multicast Traffic From 172.16.1.1
| __/ rtt 15 ms Lost/Sent = Pct Rate To 236.82.134.23
v / hop 119 ms --------------------- --------------------
172.16.1.1
172.16.2.233 ?
| ^ ttl 0
v | hop 12 ms -1/0 = --% 0 pps 0/0 = --% 0 pps
172.16.2.234
172.16.2.246 ?
| ^ ttl 1
v | hop -645 ms -1/1 = --% 0 pps 0/0 = --% 0 pps
172.16.2.245
172.16.2.237 ? Reached RP/Core
| ^ ttl 2
v | hop 248 ms -1/1 = --% 0 pps -1/0 = --% 0 pps
172.16.2.238
172.16.2.242 ?
| ^ ttl 3
v | hop 384 ms -1/1 = --% 0 pps 1/1 = --% 0 pps
172.16.2.241 ?
| \__ ttl 4
v \ hop -105 ms 0 0 pps 0 0 pps
20.20.20.20 172.16.1.1
Receiver Query Source

Iron#mstat 20.20.20.20 172.16.1.1 236.82.134.23
Type escape sequence to abort.
Mtrace from 20.20.20.20 to 172.16.1.1 via group 236.82.134.23
 From source (?) to destination (?)
Waiting to accumulate statistics....* .* .
Results after 13 seconds:

Source Response Dest Packet Statistics For Only For Traffic
20.20.20.20 20.20.20.20 All Multicast Traffic From 20.20.20.20
| __/ rtt 44 ms Lost/Sent = Pct Rate To 236.82.134.23
v / hop -72 ms --------------------- --------------------
20.20.20.20
172.16.2.241 ?
| ^ ttl 0
v | hop -289 ms -2/0 = --% 0 pps 0/0 = --% 0 pps
172.16.2.242
172.16.2.238 ?
| ^ ttl 1
v | hop -256 ms -1/1 = --% 0 pps 0/0 = --% 0 pps
172.16.2.237
172.16.2.245 ? Reached RP/Core
| ^ ttl 2
v | hop 647 ms 0/0 = --% 0 pps 0/0 = --% 0 pps
172.16.2.246
172.16.2.234 ? Prune sent upstream
| ^ ttl 3
v | hop -104 ms 0/0 = --% 0 pps 0/0 = --% 0 pps
172.16.2.233 ? Prune sent upstream
| \__ ttl 4
v \ hop 115 ms 0 0 pps 0 0 pps
172.16.1.1 20.20.20.20
Receiver Query Source

Aluminum#mtrace 172.16.1.1 20.20.20.20 236.82.134.23
Type escape sequence to abort.
Mtrace from 172.16.1.1 to 20.20.20.20 via group 236.82.134.23
 From source (?) to destination (?)
Querying full reverse path...
0 20.20.20.20
-1 172.16.2.241 PIM [172.16.1.0/24]
-2 172.16.2.242 PIM [172.16.1.0/24]
-3 172.16.2.237 PIM Reached RP/Core [172.16.1.0/24]
-4 172.16.2.246 PIM [172.16.1.0/24]
-5 172.16.2.233 PIM [172.16.1.0/24]
Aluminum#

Iron#mtrace 20.20.20.20 172.16.1.1 236.82.134.23
Type escape sequence to abort.
Mtrace from 20.20.20.20 to 172.16.1.1 via group 236.82.134.23
 From source (?) to destination (?)
Querying full reverse path... * switching to hop-by-hop:
0 172.16.1.1
-1 * 172.16.2.233 PIM Prune sent upstream [20.20.20.0/24]
-2 * 172.16.2.234 PIM Prune sent upstream [20.20.20.0/24]
-3 * 172.16.2.245 PIM Reached RP/Core [20.20.20.0/24]
-4 * 172.16.2.238 PIM [20.20.20.0/24]
-5 * 172.16.2.241 PIM [20.20.20.0/24]
-6 * Route must have changed...try again

any help will be appreciated... Thanks in advance

Best Regards,

On Dec 1, 2009 5:05pm, backbone systems <backbone.systems_at_gmail.com> wrote:
> Checkout with "debug ip mpacket" to see wat exactly ur sending to the

> destination......

> Also use "mstat" and "mtrace" commands for further information......

> On Tue, Dec 1, 2009 at 1:26 PM, nrafia_at_gmail.com> wrote:

> > Hi GS,

> >

> > i have configured few routers in series Aluminum-->Platinum -->Brass
> (RP)

> > -->TIN -->Iron (Jeff-vol-2 chapter 5,page:505). On Aluminum i have

> > configured one l0 ip add 172.16.1.1 255.255.255.0 instead of attaching
> host.

> >

> > when i ping 236.82.134.23 (iron multicast group joined by loopback). i
> got

> > following output...

> >

> > Aluminum#ping 236.82.134.23 rep 3

> >

> > Type escape sequence to abort.

> > Sending 3, 100-byte ICMP Echos to 236.82.134.23, timeout is 2 seconds:

> >

> > Reply to request 0 from 172.16.2.241, 20 ms

> > Reply to request 0 from 172.16.2.241, 24 ms

> > Reply to request 1 from 172.16.2.241, 12 ms

> > Reply to request 1 from 172.16.2.241, 16 ms

> > Reply to request 2 from 172.16.2.241, 8 ms

> > Reply to request 2 from 172.16.2.241, 12 ms

> >

> > why i am getting duplicate replies?

> >

> >

> > second sh ip mroute on Aluminum (ping originator) shows

> >

> > Aluminum#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

> >

> > (*, 236.82.134.23), 00:02:08/stopped, RP 172.16.224.1, flags: SPF

> > Incoming interface: Serial1/0, RPF nbr 172.16.2.234

> > Outgoing interface list: Null

> >

> > (172.16.1.1, 236.82.134.23), 00:02:08/00:03:21, flags: FT

> > Incoming interface: Loopback0, RPF nbr 0.0.0.0

> > Outgoing interface list:

> > Serial1/0, Forward/Sparse, 00:01:48/00:02:40

> >

> > (*, 224.0.1.40), 00:02:11/00:02:19, RP 172.16.224.1, flags: SJCL

> > Incoming interface: Serial1/0, RPF nbr 172.16.2.234

> > Outgoing interface list:

> > Loopback0, Forward/Sparse, 00:02:11/00:02:19

> >

> > all other routers shows

> >

> > Iron#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

> >

> > (*, 236.82.134.23), 00:09:04/stopped, RP 172.16.224.1, flags: SJCL

> > Incoming interface: Serial1/0, RPF nbr 172.16.2.242

> > Outgoing interface list:

> > Loopback0, Forward/Sparse, 00:09:04/00:02:46

> >

> > (172.16.2.233, 236.82.134.23), 00:06:34/00:02:52, flags: LJT

> > Incoming interface: Serial1/0, RPF nbr 172.16.2.242

> > Outgoing interface list:

> > Loopback0, Forward/Sparse, 00:06:34/00:02:46

> >

> > (172.16.1.1, 236.82.134.23), 00:06:34/00:02:52, flags: LJT

> > Incoming interface: Serial1/0, RPF nbr 172.16.2.242

> > Outgoing interface list:

> > Loopback0, Forward/Sparse, 00:06:34/00:02:46

> >

> > (*, 224.0.1.40), 00:09:04/00:02:49, RP 172.16.224.1, flags: SJCL

> > Incoming interface: Serial1/0, RPF nbr 172.16.2.242

> > Outgoing interface list:

> > Loopback0, Forward/Sparse, 00:09:04/00:02:49

> >

> > my second question. why on originator its mapping to loopback
> 172.16.1.1,

> > instead of serial interface? and why on all the rest of the routers i
> can

> > see two mapping, one for loopback and one for serial?

> >

> > Thanks in advance for any help.

> >

> >

> > Best Regards,

> >

> > Nadeem Rafi

> >

> >

> > Blogs and organic groups at http://www.ccie.net

> >

> > _______________________________________________________________________

> > Subscription information may be found at:

> > http://www.groupstudy.com/list/CCIELab.html

Blogs and organic groups at http://www.ccie.net
Received on Tue Dec 01 2009 - 14:53:21 ART

This archive was generated by hypermail 2.2.0 : Sat Jan 02 2010 - 11:11:07 ART