Hi all,
I am currently fighting with the "correct" way to attach an third party managed
dual homed internal customer to our mpls backbone. (See below for diagram)
Due to license costs we have decided (and I am starting to regret it) using
EIGRP between the "customer" CEs (6500s) and our two PEs(asr1001s) we have
located at their location.
The links between the PEs and CEs are ethernet with 802.1Q trunks for the
different VPNS/ VRFs.
As there is a third party managing the CEs would would like to protect our
network and theirs as best we can by only configuring the PEs.
I am currently using "distribute-list prefix in" on the PES to protect EIGRP
process. Without this, the "other" PE will end up learning the default route
via EIGRP from the first PE.
I am also worried about the backdoor link being ignored as I have currently not
configured site of origin. I am also thinking about tagging the BGP routes I
export to EIGRP to ensure that they are not re-imported on the PE itself, or
the "other" PE.
Is there a "correct/ cisco way" of doing this? I have been checking the
documentation, but haven't found a "complete" solution.
I have set up the config below in GNS3 - and I hope it reacts close to what the
real boxes will do later in my lab.
Thanks for any comments/ suggestions,
Regards
Andrew
---
PS: and use eBGP is not helpful :)
The routers and switches are connected as below with 2x 1G WAN links, and 1G
ethernet between PsE and CEs
10G
ce1-----------ce2
| \ / |
| \ / |
| \ / |
| \ / |
| \ / |
| \ |
| / \ |
| / \ |
| / \ |
| / \ |
pe1 pe2
| |
| 1G WAN | 1G WAN
MPLS CLOUD MPLS CLOUD
MPLS CLOUD
------------Default from cloud for CUST1 vrf
Currently I have configured (simplified meta config)
router eigrp 1
address-family ipv4 vrf CUST1 autonomous-system 10
redistribute bgp 65000 metric 100000 10 255 1 1500
distribute-list prefix CUST1IN in
network 10.0.0.0
exit-address-family
!
router bgp 65000
address-family ipv4 vrf CUST1
no synchronization
redistribute connected
redistribute eigrp 10
exit-address-family
_______________________________________________
cisco-nsp mailing list [email protected]
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/
