I`ll try and explain the best I can
Site B
Router 1`s serial interface is connected to the MPLS
Router 1`s Ethernet is on a Local Lan in an OSPF AS ( lets call that B )
Router 2`s Ethernet is on the Local lan in AS B also
Router 2`s Etherne 2 is connected to a Firewall which has a VPN across the internet
Site A
Router 1`s serial interface is connected to the MPLS
Router 1`s Ethernet is on a Local Lan in an OSPF AS ( lets call that A )
Router 2`s Ethernet is on the Local lan in AS A also
Router 2`s Etherne 2 is connected to a Firewall which has a VPN across the internet
Basicaly both sites edge devices are virtualy a mirror image
The MPLS Connection is simple
Site B learns a default route from Site A redistributed between protcols.
( IE Site A - AS A into the BGP cloud and then into Site B - AS B )
Site A learns all routes from Site B redistributed between protocols
( IE Site B - AS B into the BGP Cloud and then into Site A - AS A )
The backup link is a 3Des Connection between two firewalls on the edge of the
network connected to the internet
Routers 2 at each site connect directly to each firewall, these Routers have a GRE
Tunnel between then over the VPN over the internet ( GRE To carry OSPF )
At Site B, Router 2, both the local ethetet interface and the GRE Tunnel interface
are both in Area 0 of the Local AS B
At site A, Router 2, the local ethernet interface is in AS A, but the Tunnel interface
is in AS B.
Thats the setup, here is the issue.
The network with the issue is for example 129.29.x.x / 16
129.29 lives at Site B, it is redistributed into the MPLS and site A then propergates
this via OSPF througout site A
Router 2 at site A learns about this route locally and via the GRE Backup link on its
tunnel interface
So from Router 2A`s perspective
it sees 129.29 via its tunnel, as an Intra Area route.
This route is redistributed on that router from AS B into AS A however with a metric
of 500
So all other routers in site A see the 129.29 via the BGP with a cost of 200, if that
route disapears it knows about 129.29 via the Tunnel at a cost of 500.
If you look at router 2`s routing table it states
129.29.0.0 /16 via tunnel 0
If I kill the BGP connection, everything routes to Site B via the Tunnel 0
If I bring the MPLS backup, everything routes fine via the MPLS including 129.29.x.x
However once that is done, if I look at router 2A its routing table has lost the local
intra area 129.29.x.x and its been replaced with a External 129.29.x.x type 1 address as
all other routers on site A see, even through its tunnel interface is directly connected
to AS B with a Intra area Route for it.
If I run a show ip route 129.29.0.0 on Router 1B sometimes it states ( self originated )
I cannot figure this out, sorry for the complicated explanation.
Thanks, Lee
LEEroy
MCNE6,CCNA2,CWNA, Project+, CCSA
Site B
Router 1`s serial interface is connected to the MPLS
Router 1`s Ethernet is on a Local Lan in an OSPF AS ( lets call that B )
Router 2`s Ethernet is on the Local lan in AS B also
Router 2`s Etherne 2 is connected to a Firewall which has a VPN across the internet
Site A
Router 1`s serial interface is connected to the MPLS
Router 1`s Ethernet is on a Local Lan in an OSPF AS ( lets call that A )
Router 2`s Ethernet is on the Local lan in AS A also
Router 2`s Etherne 2 is connected to a Firewall which has a VPN across the internet
Basicaly both sites edge devices are virtualy a mirror image
The MPLS Connection is simple
Site B learns a default route from Site A redistributed between protcols.
( IE Site A - AS A into the BGP cloud and then into Site B - AS B )
Site A learns all routes from Site B redistributed between protocols
( IE Site B - AS B into the BGP Cloud and then into Site A - AS A )
The backup link is a 3Des Connection between two firewalls on the edge of the
network connected to the internet
Routers 2 at each site connect directly to each firewall, these Routers have a GRE
Tunnel between then over the VPN over the internet ( GRE To carry OSPF )
At Site B, Router 2, both the local ethetet interface and the GRE Tunnel interface
are both in Area 0 of the Local AS B
At site A, Router 2, the local ethernet interface is in AS A, but the Tunnel interface
is in AS B.
Thats the setup, here is the issue.
The network with the issue is for example 129.29.x.x / 16
129.29 lives at Site B, it is redistributed into the MPLS and site A then propergates
this via OSPF througout site A
Router 2 at site A learns about this route locally and via the GRE Backup link on its
tunnel interface
So from Router 2A`s perspective
it sees 129.29 via its tunnel, as an Intra Area route.
This route is redistributed on that router from AS B into AS A however with a metric
of 500
So all other routers in site A see the 129.29 via the BGP with a cost of 200, if that
route disapears it knows about 129.29 via the Tunnel at a cost of 500.
If you look at router 2`s routing table it states
129.29.0.0 /16 via tunnel 0
If I kill the BGP connection, everything routes to Site B via the Tunnel 0
If I bring the MPLS backup, everything routes fine via the MPLS including 129.29.x.x
However once that is done, if I look at router 2A its routing table has lost the local
intra area 129.29.x.x and its been replaced with a External 129.29.x.x type 1 address as
all other routers on site A see, even through its tunnel interface is directly connected
to AS B with a Intra area Route for it.
If I run a show ip route 129.29.0.0 on Router 1B sometimes it states ( self originated )
I cannot figure this out, sorry for the complicated explanation.
Thanks, Lee
LEEroy
MCNE6,CCNA2,CWNA, Project+, CCSA