I am currently working for a client and helping them redesign part of their network. The client has a pretty nice network scheme in that they have their Headquarters connected to their Disaster Recovery site with an MPLS circuit, and then also a Frame Relay which was the legacy circuit prior to the MPLS.
Last week I configured a new Cisco Switch for them at the Disaster Recover site. We are configuring a new WAN network with IP address 192.168.36.0. I have a management address configured on the new switch of 192.168.36.5. Currently this switch connects to the ASA which has an address of 192.168.36.1. I have eigrp configured on the WAN switch. When I check the ASA it shows that it has the network 192.168.36.0 directly connected. From there is where everything seems strange.
I need for the Headquarters site to use the MPLS circuit to route to the new switch. For whatever reason, the path is taking the Frame Relay network. Eigrp is configured on most devices. In some places, RIP is used. I think EIGRP is distrubuted into RIP at some point. What I do know is that I wish I could stop the network 192.168.36.0 from being advertised over the Frame so It would choose the MPLS circuit on the Headquarters side.
I made one change on the Headquarters side last week thinking that it would have the effect of forcing the route to traverse the MPLS circuit. But instead what happened was the traceroute from headquarters to the 192.168.36.0 network showed the packet hit the Headquarters MPLS router, but instead of taking the MPLS over, the MPLS router then shipped the packet to the Frame router and sent it over the Frame Relay network.
Jon or Guiseppe if you get this I could really use your guys help!
I am including a diagram of the network...
Thanks for this. Yes i missed that from your previous post and was actually thinking along those lines ie. it had not been advertised from the DR site under the BGP config.
The config is a bit confusing and i need to lab something up to test. I looked at the DR config and noticed there is no network statement under EIGRP for 192.168.36.0 hence when you redsitribute EIGRP into BGP it won't add that one. But then for some reason there is also a network statement under the address-family for 172.16.132.0/30 even though there is a network statement under EIGRP for that. Bit confusing.
However your solution is valid, it's just that with EIGRP redistribution you shouldn't need that network statement under the address-family. However if you didn't want EIGRP to start on that interface so it wasn't advertised out, possibly via the frame-relay network then your solution is a better one.
As for the loopback, how does the loopback appear in the routing table ie. if you do a "sh ip route" on the DR MPLS router does it show
Whatever it shows in the routing table must match your network statement so if it says 192.168.38.0 255.255.255.0 in the routing table the network statement needs to be -
network 192.168.38.0 mask 255.255.255.0