The MPLS-OPS Archive

Cell Relay Retreat>MPLS-OPS Archive>month:2004-Mar> msg00056



[Date Prev][Date Next][Thread Prev][Thread Next]  
  [Date Index][Thread Index][Author Index][Subject Index]

Re: GRE tunnel with vrf

  • From: Phill <mpls@tasmail.com>
  • Date: Wed, 17 Mar 2004 16:22:11 +1100
  • Resent-Date: Wed, 17 Mar 2004 00:48:50 -0500
  • To: mpls-ops@mplsrc.com
  • User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.5) Gecko/20031007

Many thanks for the out of office replies that I received, but I have 
resolved this issue myself.

Phill.

Phill wrote:

> G'day,
> 
> I have a case where ISDN connected CE's from muliple customers are 
> behind a "cloud" that is out of my control and only allows me to route 
> one subnet to each CE. Since I need to route at least two subnets per CE 
> I want to use a GRE tunnel for the second/third etc subnets.
> 
> The "cloud" terminates on a PE ATM subinterface so I am useing vrf 
> selection based on source IP to get the packets into the correct vrf.
> 
> I have configured the tunnels on the PE and put the tunnel interface 
> into the vrf. There are static vrf routes for the tunnel endpoints 
> pointing at the "cloud".
> 
> The tunnels won't come up. They remain up/down. I can ping via the vrf 
> from the PE to the CE tunnel endpoint. I can ping from the CE to the PE 
> tunnel endpoint.
> 
> I assume this is because the tunnel at the PE end is trying to establish 
> outside of the vrf however the GRE packets from the CE are going 
> straight into the vrf.
> 
> If I remove the vrf config from the ATM subinterface and the tunnel 
> interface the tunnel establishes and pings OK.
> 
> Adding a route for the tunnel endpoint to the PE global routing table 
> doesn't fix it (although it is required if I remove the vrf config).
> 
> Any ideas?
> 
> Phill.
> 
> !----PE router 7206 connected to cloud via ATM c7200-k91p-mz.122-18.S1
> !----Only one vrf shown for clarity
> !
> vrf selection source 172.26.49.0 255.255.255.252 vrf Test1
> !
> interface ATM3/0.33 point-to-point
>  description link to "cloud"
>  ip vrf select source
>  ip vrf receive Test1
> ! ip vrf receive Test2 etc etc
>  ip address 172.26.166.1 255.255.255.252
>  pvc Cloud 0/33
>   vbr-nrt blaah blaah
> !
> interface Tunnel0
>  description Tunnel from PE to CE
>  ip vrf forwarding Test1
>  ip address 172.26.249.73 255.255.255.252
>  tunnel source ATM3/0.33
>  tunnel destination 172.26.49.1
> !
> ip route vrf Test1 172.26.49.1 255.255.255.255 172.26.166.2
> 
> 
> !----CE router 1003 connected to cloud via ISDN c1000-y-mz.120-3d
> interface Tunnel0
>  description Tunnel from CE to PE
>  ip address 172.26.249.74 255.255.255.252
>  no ip directed-broadcast
>  tunnel source Ethernet0
>  tunnel destination 172.26.166.1
> !
> interface Dialer0
>  description link to Cloud
>  ip unnumbered Ethernet0
> !
> interface Ethernet0
>  ip address 172.26.49.1 255.255.255.252
>  no ip directed-broadcast
> !
> ip route 0.0.0.0 0.0.0.0 Dialer0
> 
> -------
> The MPLS-OPS Mailing List
> Subscribe/Unsubscribe:  http://www.mplsrc.com/mplsops.shtml
> Archive: http://www.mplsrc.com/mpls-ops_archive.shtml
> 
> 


-------
The MPLS-OPS Mailing List
Subscribe/Unsubscribe:  http://www.mplsrc.com/mplsops.shtml
Archive: http://www.mplsrc.com/mpls-ops_archive.shtml