I have a client, who has MPLS connecting all spoke sites back to the HUB or NOC. Obviously, we have 1 default route currently. The MPLS is currently running on 1.5M T1. Customer refuses to increase capacity and bring in Metro-E/Fiber. They brought in copper/cable ISP instead. Now, customer wants us to setup a site-to-site VPN between the ASA at the NOC and the router at the spoke site. Problem is, they want all the VDI traffic to ride the T1 MPLS, but the want all imaging (specific destination IP) traffic to ride the site-to-site VPN.
How can I make this happen? ATT MPLS is the current active MPLS connection. Earthlink was replaced by ATT.
How can I accomplish sending specific traffic destined for a specific IP address across the VPN tunnel, but all other traffic ride the MPLS?
! ! interface Embedded-Service-Engine0/0 no ip address shutdown ! interface GigabitEthernet0/0 description ***MPLS to Earthlink*** shutdown ip address 10.10.11.2 255.255.255.252 ip nbar protocol-discovery ipv4 duplex auto speed auto ! interface GigabitEthernet0/1 description ATT_MPLS ip address 10.100.11.2 255.255.255.0 duplex auto speed auto ! interface GigabitEthernet0/2 no ip address shutdown duplex auto speed auto ! interface GigabitEthernet1/0 ip address 192.168.11.1 255.255.255.0 ip helper-address 192.168.1.11 ip nbar protocol-discovery ipv4 ip flow ingress ip flow egress ip virtual-reassembly in ! interface GigabitEthernet1/1 description Internal switch interface connected to EtherSwitch Service Module no ip address ! interface Cellular0/0/0 no ip address encapsulation slip dialer in-band dialer string lte ! interface Vlan1 no ip address ! router bgp 65311 bgp log-neighbor-changes network 192.168.11.0 redistribute connected neighbor 10.10.11.1 remote-as 65311 ! ip forward-protocol nd ! no ip http server ip http authentication local ip http secure-server ip http timeout-policy idle 60 life 86400 requests 10000 ip flow-export source GigabitEthernet1/0 ip flow-export version 9 ip flow-export destination 192.168.1.20 2055 ! ip route 0.0.0.0 0.0.0.0 10.100.11.1 ip route 0.0.0.0 0.0.0.0 10.10.11.1 250 ip route 192.168.1.0 255.255.255.0 10.100.11.1 !
Listen: https://smarturl.it/CCRS9E25 Follow us: twitter.com/ciscochampions
With applications and users everywhere, the networks are now, more than ever, being tasked with delivering consistent protection while providing an exceptional user exper...
Listen: https://smarturl.it/CCRS9E24 Follow us: https://twitter.com/CiscoChampion
Cisco Radio Aware Routing addresses several of the challenges faced when merging IP routing and radio communications in mobile networks, especially those exhibiti...
Listen: https://smarturl.it/CCRS9E23 Follow us: https://twitter.com/CiscoChampion The Wi-Fi 6E Catalyst 9136 access point takes advantage of the 6-GHz band to produce a network that is more reliable and secure, with higher throughput, more ...
When moving from OSPFv2 to OSPFv3, there are many changes in the format of the LSAs Type, but the most known changes are: IP prefix informations are no longer carried in Type-1 LSA and Type-2 LSA, new LSAs Type 8 and 9 are added to carry these prefixes.