Multicast VPN with MDT
OK..you are the man
I inserted the given command, and it seems ok now the reason , i guess , was that my router has IBGP peering to its domain neighbors and also EBGP to another AS , for some reason the MDT was picking the EBGP address (which is not the loopback) and use that to intiate the tunnel , probably because its higher IP address? thanks a lot for the help
— On Wed, 6/4/08, Roman Rodichev <roman@iementor.com> wrote:
From: Roman Rodichev <roman@iementor.com> Subject: RE: Multicast VPN with MDT To: “‘Peter Svidler’” <doubleccie@yahoo.com>, ccielab@groupstudy.com, security@groupstudy.com Date: Wednesday, June 4, 2008, 3:52 PM
Are you sure you have “neighbor x.x.x.x update-source loopback0″ in BGP
If for some reason you can’t use update-source command (if PE is an eBGP neighbor), you can also use “bgp next-hop loopback0″ command under VRF to force MVPN mGRE tunnel to source from loopback.
Roman Rodichev 5xCCIE #7927 (R&S, Security, Voice, Storage, Service Provider) Instructor, Content Developer. ieMentor Corporation http://www.iementor.com Y!M: roman7927
—–Original Message—– From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of Peter Svidler Sent: Wednesday, June 04, 2008 6:31 AM To: ccielab@groupstudy.com; security@groupstudy.com Subject: Multicast VPN with MDT
Folks I have a scenario where I am trying to build Multicast VPN using MDT between PE’s . one of my routers , strangely , is not using the loopback address to initiate the tunnel (using MDT as explained in documentation should usually use the BGP peer address , which in my case is the loopback to intiate the tunnel ) I wonder if anyone came across similar problem and explain why it happens? thanks
























