From: Con Spathas (ccie19226@googlemail.com)
Date: Tue Nov 11 2008 - 11:50:00 ARST
Petr - taking it to the next level as always! :-)
Backbone - if you can't do the things Petr explained in a lab because you
haven't been asked to etc... here's an example of what I do to ping over the
MDT on a PE.
For this example I setup a basic VPN network (R1 - R2 - R3 - R4 - R5 - R6)
R1 and R5 are the CE routers
R2 and R4 are the PE routers
R3 is the P router
R6 issued an IGMP join for 226.6.6.6 on its connection to R5
R5 is the RP within the VPN (via AutoRP)
R2-R5 on the SP side just running PIM-SM with SSM.
I built an MDT tunnel between R2 and R4 using group 232.1.1.1
So here's a ping from R1 to make sure things are working:
R1#ping 226.6.6.6 rep 5
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 226.6.6.6, timeout is 2 seconds:
Reply to request 0 from 56.56.56.6, 92 ms
Reply to request 1 from 56.56.56.6, 112 ms
Reply to request 2 from 56.56.56.6, 132 ms
Reply to request 3 from 56.56.56.6, 128 ms
Reply to request 4 from 56.56.56.6, 144 ms
Okay that's what we want.
Let's try a ping on R2 (PE router)
R2#ping vrf R1 226.6.6.6 rep 5
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 226.6.6.6, timeout is 2 seconds:
.....
Okay not so good. So let's try an extended ping with the MDT tunnel as the
interface.
No configuration changes have been made on R2.
R2#ping vrf R1
Protocol [ip]:
Target IP address: 226.6.6.6
Repeat count [1]: 5
Datagram size [100]:
Timeout in seconds [2]:
Extended commands [n]: y
Interface [All]: tunnel0 <----- here
Time to live [255]:
Source address: 12.12.12.2 <----- R2's address in the VPN
Type of service [0]:
Set DF bit in IP header? [no]:
Validate reply data? [no]:
Data pattern [0xABCD]:
Loose, Strict, Record, Timestamp, Verbose[none]:
Sweep range of sizes [n]:
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 226.6.6.6, timeout is 2 seconds:
Packet sent with a source address of 12.12.12.2
Reply to request 0 from 56.56.56.6, 80 ms
Reply to request 1 from 56.56.56.6, 112 ms
Reply to request 2 from 56.56.56.6, 80 ms
Reply to request 3 from 56.56.56.6, 104 ms
Reply to request 4 from 56.56.56.6, 104 ms
Excellent!
On Mon, Nov 10, 2008 at 8:20 PM, Alexey Tolstenok <alextols@gmail.com>wrote:
> Hello, backbone
> Try to add "ip igmp static-group 225.1.1.1" under PE1 vrf interface
> configuration.
>
> 2008/11/9 backbone systems <backbone.systems@gmail.com>
>
> > CUST A-1----PE1----P-----PE2-----CUST A -2--225.1.1.1
> >
> > I am trying to Ping from CUST A site 1 to site 2 and the reply is
> > successful.
> > But when try to ping the destination from my PE1 router i dont get
> replies,
> >
> > PE1------ping vrf ABC 225.1.1.1
> >
> > wen i do debug ip mpack... i can see on PE1 that the source of the
> > packet is lo0 of PE1 bc mdt by default take the source interface as
> > the MBGP interface used for connectivity.
> >
> > is there any way i can change this default behaviour? How can i make
> > my ping successful sitting on PE1
> >
> > Any gud references on this topic will be helpful.
> >
> >
> > Blogs and organic groups at http://www.ccie.net
> >
> > _______________________________________________________________________
> > Subscription information may be found at:
> > http://www.groupstudy.com/list/CCIELab.html
> >
> >
> >
> >
> >
> >
> >
> >
>
>
> --
> Alexey Tolstenok
> CCIEx2 (R&S, SP) #17405, JNCIE-M #313, CCSI #31737
>
>
> 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
This archive was generated by hypermail 2.1.4 : Mon Dec 01 2008 - 08:18:30 ARST