I'm going to plan to extend L2 using LISP in the on-premises version of Cisco's C8300 series and Azure cloud.
The target segment for the L2 extension between these locations will be defined by an Endpoint Identifier (EID). I am considering the introduction of multiple segments for definition. However, I have found that Cisco documentation and examples typically only show a target segment being defined for the segment to which the LISP-enabled router is connected. My question is: would it be possible, for instance, to extend multiple VLAN segments?
If this is possible, could you confirm if the following is correct as an example of setting up an xTR
vlan10 10.0.10.0/24
vlan20 10.0.20.0/24
Instance ID 0
Database Mapping 10.0.10.0/24 172.16.1.2
Database Mapping 10.0.20.0/24 172.16.1.2
If the on-premises L3 switch and router connection can cover multiple segments
Which pattern would you use?
Pattern 1. Router on a Stick (ROAS)
Physical connection is done with a single LAN cable.
L3 is trunk-connected on vlan10 and 20 ports.
The router gives vlan10.20 to the sub-interface.
In the case of 0vlna10
R1(config)#Interface Ethernet 0/0.10
R1(config-subif)#encapsulation dot1Q 10
R1(config-subif)#ip address 10.0.10.254 255.255.255.0
R1(config-subif)#no shutdown
Pattern 2. Separate interfaces by VLAN
Physical connection is done with two LAN cables.
L3 creates vlan10, 20 on the access port.
The router has IFs of vlan10 and 20.
For vlan10
R1(config)#interface ethernet 0/0/1
R1(config-if)#ip address10.0.10.254 255.255.255.0
R1(config-if)#no shutdown
