I have a remote site (network 10.80.180.0) which is accessing two data centers through MPLS. Two data centers are running the same EIGRP on their network and both update carrier BGP with eigrp routes. Both data centers are connected with L2 (dark fiber) and with L3 MPLS. In data center AAA network is 10.80.100.0 and in data center BBB 10.80.150.0. Routers from both datacenters update carrier BGP with the same routes. It is causing some routing issues.
When PC from remote site on network 10.80.180.0 wants to access Mail Server (10.80.100.100) in data center AAA it goes directly to data center AAA. Then mail server replys to this PC by sending packets to default gateway 10.80.100.1. This router however learns route to 10.80.180.0 from router in datacenter BBB so it sends packets to router in datacenter BBB and he sends packets to 10.80.180.0 network. It creates asymetric routing. Packet leave network 10.80.180.0 and goes to network 10.80.100.0 and returns back from network 10.80.150.0.
Carriers wants me to tag eigrp routes leaving network 10.80.100.0 with different tag than routes leaving 10.80.150.0 network.
Should I do it? If yes, how this can be done?
I think it is complicated explanation. If required I can provide diagram.
This document gives several answers on frequently asked questions for PFRv3 channel state behavior.
Q1: What are all the channel operational states from a BR (border role) perspective and what are the rules/conditions to be in each st...
The need was to reach an host inside a LAN through a VPN connection managed by the LAN gateway (Cisco 1921).
The LAN gateway performs NAT and there was a dedicate nat rule for the host i wanted to reach through VPN.
I couldn't connect to the hos...