Thursday, June 18, 2020

Cisco DMVPN: using two crypto keyrings and ISAKAMP profiles on Hub router

We have two different company DMVN hubs (phase 3), that need to connect to provide connectivity.

Each company needs to preserve the crypto keyring and crypto isakmp profile on each Hub, to maintain connectivity with their existing "spokes". 

What is the best practice to for CompanyB to add Company A's crypto keyring and isakamp profile to the config?

Can't seem to find anything that  points how to do this. Found something close, but it was 8yrs old using 12.x code, so no thank you.

Anybody have links, examples ?

Will adding another keyring and profile "disrupt" our existing CompB endpoints?

Running Cisco IOS 15 code, not IOS-XE code on CompB dmvpn hub.

yes we will be creating another "tunnel" on CompB router.  Also ACL's will be used to limit routes passed between the two endpoints



No comments:

Post a Comment