Specifying Remote VTEPs and their Reachability Statically

Syntax


path-group <name>
peer static router-ip <ip-address> 
ipv4 address <ip-addr1> 
ipv4 address <ip-addr2>
## more IP addresses through which the router can be reached

peer static is used to configure the remote VTEP reachability statically via routable IP addresses over the SP network. The router-IP is the VTEP IP address. In the case of Internet, the routable IP address is a public IP address. In the case of MPLS it is Enterprise specific private IP address that the MPLS provider knows how to reach. Typically customer edge routers (CEs) are configured to exchange subnets by running eBGP to the SP’s PE router.

Example

In the above deployment for the MPLS path group Router2’s router IP 10.2.2.2 is reachable via Router2’s MPLS IP address 172.16.2.1


switch(config-dynamic-path-selection)# path-group mpls
switch(config-path-group-mpls)# peer static router-ip 10.2.2.2
switch(config-peer-router-ip-10.2.2.2-mpls)# ipv4 address 172.16.2.1

For the Internet path group Router2’s router IP 10.2.2.2 is reachable via two IP addresses only via ISP1 3.3.3.3 and another through ISP2 4.4.4.4

switch(config-dynamic-path-selection)# path-group internet
switch(config-path-group-internet)# peer static router-ip 10.2.2.2
switch(config-peer-router-ip-10.2.2.2-internet)# ipv4 address 3.3.3.3
switch(config-peer-router-ip-10.2.2.2-internet)# ipv4 address 4.4.4.4

It is important to note that once local and remote IP addresses are specified for a path-group then all combinations of local and remote IP address is a potential path for load balancing.

Example

Consider the following configuration that corresponds to the topology in the above figure :


switch(config)#router path-selection 
switch(config-dynamic-path-selection)#path-group mpls
switch(config-path-group-mpls)#local interface et1
switch(config-path-group-mpls)#peer static router-ip 10.2.2.2
switch(config-peer-router-ip-10.2.2.2-mpls)#ipv4 address 172.16.2.1
switch(config-peer-router-ip-10.2.2.2-mpls)#path-group internet
switch(config-path-group-internet)#local interface et2
switch(config-path-group-internet)#local interface et3
switch(config-path-group-internet)#peer static router-ip 10.2.2.2
switch(config-peer-router-ip-10.2.2.2-internet)#ipv4 address 3.3.3.3
switch(config-peer-router-ip-10.2.2.2-internet)#ipv4 address 4.4.4.4
switch(config-peer-router-ip-10.2.2.2-internet)#

The paths defined are 
MPLS path - 172.16.1.1 -- 172.16.2.1
4 Internet paths 
1.1.1.1 -- 3.3.3.3
1.1.1.1 -- 4.4.4.4
2.2.2.2 -- 3.3.3.3
2.2.2.2 -- 4.4.4.4

However if ISP2 is a LTE and the customer does not want paths to cross over from ISP1 to LTE then the configuration should be

switch(config)#router path-selection 
switch(config-dynamic-path-selection)#path-group mpls
switch(config-path-group-mpls)#local interface et1
switch(config-path-group-mpls)#peer static router-ip 10.2.2.2
switch(config-peer-router-ip-10.2.2.2-mpls)#ipv4 address 172.16.2.1
switch(config-peer-router-ip-10.2.2.2-mpls)#path-group internet
switch(config-path-group-internet)#local interface et2
switch(config-path-group-internet)#peer static router-ip 10.2.2.2
switch(config-peer-router-ip-10.2.2.2-internet)#ipv4 address 3.3.3.3
switch(config-peer-router-ip-10.2.2.2-internet)#path-group lte
switch(config-path-group-lte)#local interface et3
switch(config-path-group-lte)#peer static router-ip 10.2.2.2
switch(config-peer-router-ip-10.2.2.2-lte)#ipv4 address 4.4.4.4
switch(config-peer-router-ip-10.2.2.2-lte)#

In the above case the paths are
MPLS path - 172.16.1.1 -- 172.16.2.1
Internet path 1.1.1.1 -- 3.3.3.3
LTE path 2.2.2.2 -- 4.4.4.4.