Re: monitor P router loopback address

From: jack daniels <jckdaniels12_at_gmail.com>
Date: Fri, 3 Jul 2009 09:02:57 +0530

Hi Brayan ,

thanks I got it now :) ....just tested the same also working ...

Regards
J.Daniels

On Thu, Jul 2, 2009 at 9:05 PM, Bryan Bartik <bbartik_at_ipexpert.com> wrote:

> For an example, consider this topology:
>
> CE1---s1/1[PE1]---P
>
> CE1-PE1: 200.0.0.1 and .2
> PE-P: 200.0.0.5 and .6
> CE1 belongs to a VRF, and it has a default route pointing to PE1.
> P's Loopback is 100.0.0.2
>
> On PE1 add 2 routes:
>
> ! This is so CE1's traffic gets routed to P1
> ip route vrf VPNA 100.0.0.2 255.255.255.255 200.0.0.6 global
> ! This is so PE1 can route the return traffic back to the VRF (notice it is
> the connected interface in the VRF)
> ip route 200.0.0.0 255.255.255.252 Serial1/1
>
> On P add this route:
>
> ip route 200.0.0.0 255.255.255.252 200.0.0.5
>
> Now CE1 can communicate with P1:
>
> CE1#ping 100.0.0.2
>
> Type escape sequence to abort.
> Sending 5, 100-byte ICMP Echos to 100.0.0.2, timeout is 2 seconds:
> !!!!!
> Success rate is 100 percent (5/5), round-trip min/avg/max = 12/32/84 ms
> CE1#
>
>
>
> On Thu, Jul 2, 2009 at 8:38 AM, Bryan Bartik <bbartik_at_ipexpert.com> wrote:
>
>> Take a look here:
>>
>> *
>> http://www.cisco.com/en/US/tech/tk436/tk832/technologies_configuration_example09186a0080231a3e.shtml
>> *
>>
>>
>> 2009/7/2 Alex H. Ryu <r.hyunseog_at_ieee.org>
>>
>>> I don't think so.
>>> Routing should be bi-directional, and if it happens, it is security
>>> issue for VRF.
>>> Between VRFs, using import/export RT, it can share routes between
>>> different VRFs if you carefully design it.
>>> But not with Global Default routing table.
>>>
>>> Alex
>>>
>>>
>>>
>>> Bhuvanesh Rajput wrote:
>>> > Hi,
>>> >
>>> > If routes are in Global Routing table...can't these be injected in
>>> vrf....??
>>> >
>>> > Brgds
>>> > Bhuvanesh
>>> >
>>> >
>>> > On Thu, Jul 2, 2009 at 3:03 PM, jack daniels<jckdaniels12_at_gmail.com>
>>> wrote:
>>> >
>>> >> Hi,
>>> >>
>>> >> P router has loopback and has no vrf , so it belongs to Default global
>>> >> routing table.
>>> >>
>>> >> Regards
>>> >>
>>> >>
>>> >>
>>> >> 2009/7/2 Alex H. Ryu <r.hyunseog_at_ieee.org>
>>> >>
>>> >>
>>> >>> What routing table does loopback ip address belong to ?
>>> >>>
>>> >>> VRF stands for Virtual Routing and Forwarding instance.
>>> >>> Between VRFs, you may import/expot routing table to share the
>>> connectivity.
>>> >>>
>>> >>> But if loopback ip address are belong to Default_Routing table, which
>>> is
>>> >>> not VRF,
>>> >>> I don't think so.
>>> >>>
>>> >>> Alex
>>> >>>
>>> >>>
>>> >>> jack daniels wrote:
>>> >>>
>>> >>>> Hi group ,
>>> >>>>
>>> >>>> I have a vrf X and I'm monitoring the LOOPBACKs of PE routers , now
>>> to
>>> >>>> monitor P routers how can we make it ......
>>> >>>> Monitoring is done on a server which is connected on VRF X
>>> >>>>
>>> >>>> Regards
>>> >>>> J.Daniels
>>> >>>>
>>> >>>>
>>> >>>> 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
>>> >>
>>> >>
>>> _______________________________________________________________________
>>> >> Subscription information may be found at:
>>> >> http://www.groupstudy.com/list/CCIELab.html
>>>
>>>
>>> Blogs and organic groups at http://www.ccie.net
>>>
>>> _______________________________________________________________________
>>> Subscription information may be found at:
>>> http://www.groupstudy.com/list/CCIELab.html
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>
>>
>> --
>> Bryan Bartik
>> CCIE #23707 (R&S), CCNP
>> Sr. Support Engineer - IPexpert, Inc.
>> URL: http://www.IPexpert.com <http://www.ipexpert.com/>
>>
>
>
>
> --
> Bryan Bartik
> CCIE #23707 (R&S), CCNP
> Sr. Support Engineer - IPexpert, Inc.
> URL: http://www.IPexpert.com <http://www.ipexpert.com/>

Blogs and organic groups at http://www.ccie.net
Received on Fri Jul 03 2009 - 09:02:57 ART

This archive was generated by hypermail 2.2.0 : Sat Aug 01 2009 - 13:10:21 ART