07-09-2015 06:35 PM
I am looking for a configuration guide for OTV using the ASR platform where the ASR is not the main routing platform.
I would like to deploy OTV between two sites which already have L3 connectivity.
The ASRs have been purchased to provide L2 between two sites.
One requirement I have seen with the ASRs is they have to have 2 physical interfaces.
Question:
How do I use the ASR's for OTV with regards to traffic flow?
I was thinking I could use them like router on a stick as in the N7K deployment, but all the topologies I have seen so far have the routers in the traffic path - I cannot break the traffic path to put the routers in so can I configure them on a stick?
Thanks
Roger
Solved! Go to Solution.
07-12-2015 02:31 AM
Hi Roger,
I've done something along the lines of the attached, albeit with Nexus 7000 rather than ASR, but the principle should be the same.
The configuration (taken from a CSR) would be as follows:
! interface GigabitEthernet1 description Join interface towards L3 core mtu 1600 ip address A.B.C.D 255.255.255.252 load-interval 30 negotiation auto ! bridge-domain 51 bridge-domain 52 ! interface GigabitEthernet2 description Internal interface no ip address negotiation auto service instance 51 ethernet encapsulation dot1q 51 bridge-domain 51 ! service instance 52 ethernet encapsulation dot1q 52 bridge-domain 52 ! ! interface Overlay1 no ip address load-interval 30 otv join-interface GigabitEthernet1 otv use-adjacency-server 192.168.11.241 unicast-only otv adjacency-server unicast-only service instance 51 ethernet encapsulation dot1q 51 bridge-domain 51 ! service instance 52 ethernet encapsulation dot1q 52 bridge-domain 52 ! !
There will obviously be a little more configuration (otv site bridge-domain and otv site-identifier) if using a pair of ASR per site for resilience.
You should be able to develop a working setup entirely with CSR 1000V to at least get some hands on. And from what I see you've dabbled with the CSR a little bit :-)
Not on a stick exactly, but you don't have to alter the existing traffic path.
Regards
07-12-2015 02:31 AM
Hi Roger,
I've done something along the lines of the attached, albeit with Nexus 7000 rather than ASR, but the principle should be the same.
The configuration (taken from a CSR) would be as follows:
! interface GigabitEthernet1 description Join interface towards L3 core mtu 1600 ip address A.B.C.D 255.255.255.252 load-interval 30 negotiation auto ! bridge-domain 51 bridge-domain 52 ! interface GigabitEthernet2 description Internal interface no ip address negotiation auto service instance 51 ethernet encapsulation dot1q 51 bridge-domain 51 ! service instance 52 ethernet encapsulation dot1q 52 bridge-domain 52 ! ! interface Overlay1 no ip address load-interval 30 otv join-interface GigabitEthernet1 otv use-adjacency-server 192.168.11.241 unicast-only otv adjacency-server unicast-only service instance 51 ethernet encapsulation dot1q 51 bridge-domain 51 ! service instance 52 ethernet encapsulation dot1q 52 bridge-domain 52 ! !
There will obviously be a little more configuration (otv site bridge-domain and otv site-identifier) if using a pair of ASR per site for resilience.
You should be able to develop a working setup entirely with CSR 1000V to at least get some hands on. And from what I see you've dabbled with the CSR a little bit :-)
Not on a stick exactly, but you don't have to alter the existing traffic path.
Regards
07-12-2015 08:50 AM
Thanks Steve,
I will be joining connecting the ASRs to a 6880 core so will have to have one L2 interface and one L3 interface.
The configs are helpful and yes I will be labbing this on the CSRs first.
Once I have it up and running I will post more details
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide