Routing between VRF and GRT to Core Layer. Dual-Hub Dual-ISP
I'm having issues in routing from vrf to grt ( global routing table ) to the core router and vice versa.
Here's a quick overview of my setup:
HUB1: Primary for RED
HUB2: Primary for BLUE
iVRF: RED and BLUE
fVRF: ISP1 and ISP2
Hub to Core: 10.250.250.0/24
T0: 192.168.100.1 tunnel vrf isp1 - RED
T1: 192.168.101.1 tunnel vrf isp1 - BLUE
T2: 192.168.200.1 tunnel vrf isp2 - RED
T3: 192.168.201.1 tunnel vrf isp2 - BLUE
2 Tunnels always remain shutdown at the spokes, but whenever the connections fails at one of the ISP's, the spoke automatically shuts down the corresponding tunnel and brings up the Backup tunnel which registers through ISP2, but at the Hub1.
My setup is in the following order:
What I want to achieve is, I want to be able to access the VRF's from my core router, without involving anymore VRF's down the core layer.I want to terminate the VRF at the Hub's, and continue with normal routing below the Hub's without having too much routes on my Core routers , I want to advertise a summary route from the Hub's down to my Core routers ( Each Hub will advertise 2 Routers, for example Hub1 will advertise 10.100.x.x as its primary route, and possible 10.105.x.x as a secondary route , in the case if Hub2 fails ).
The only way to achieve this , it seems that the Spokes, Hub and the Core router need to know about each other in their GRT, otherwise it won't route.
I tried Route leaking from VRF to GRT, but it didn't go as expected.
I could easily redistribute static routes for my Tunnel interfaces to my core layer, and my core routers would always be able to access the Tunnel interfaces, because they all reside in a different Subnet, and they are static and never change their way, but as for RED and BLUE, if one ISP goes down at the spoke, the Spoke would switch to the other Tunnel, and the Hub would still be routing through the old tunnel because it doesn't know the spoke changed his way.That is for static route distributing to the core ,its too dynamic to go with static routes.
Here's a link to an example of what i'm doing, with a few changes:
Cisco Defense Orchestrator (CDO) is a cloud-based, multi-device manager that manages security products like Adaptive Security Appliance (ASA), Firepower Threat Defense next-generation firewall, and Meraki devices, to name a few.
We make improvement...
Bonjour,Je cherche à acceder l'interface de management de l'ASA, depuis l'Anyconnect.Malegré que j'ai ajouté les ACLs necessaires, mais l'acces management ASA en SSH depuis le vpn nomade ne passse.Je me demande si on peut manager l'ASA en ssh ou autres pr...
I am involved in rolling out about 40 wifi networks using cisco 3602/2802 aps and cisco 5508 ISE. Our network offers a 2 step authentication with user and machine certificates as well as users needing to be in correct AD groups. The problem we have i...
August 13, 2020Custom Conflict Detected Polling IntervalCustom FTD Templates July 30, 2020Object OverridesImproved Network Group WizardJuly 9, 2020Customize the RA VPN and Events ViewsJuly 2, 2020SecureXCisco Security Analytics and Logging Event Downloads...
Dear Community, So, according to the Cisco ISE Release 2.7 Administrator Guide, it should be possible to use a remote lock/wipe on MDM-devices that connect through ISE on the network( see the screenshot in the attachment).The problem is that th...