A tunnel between two VEdge instances can run through an MPLS core network. Smarts MPLS Manager has capability to discovery core MPLS physical/logical entities in the MPLS network. The Server manager can be configured to import this topology into Server Manager and create a VEdge to VEdge tunnel using a user defined configuration.

To configure a Smarts MPLS Manager for Server Manager run sm_edit conf/sdwan/esm-mpls.conf and specify the MPLS topology server details.
Note: Type value must be MPLS, only one MPLS topology server can be configured for topology import.

To define user defined connection run sm_edit conf/sdwan/user-defined-connection.conf. The format of the file and an example is given below:

# Tunnel-A      Tunnel-Z       Tunnel-A-end    Tunnel-Z-end     
#  -end-IP      -end-IP           -PE-IP       -PE-IP

For each of the Edge to Edge tunnel that goes over the MPLS network feed in the four IP address given above. Tunnel-A-end-IP is the IP address on the VEdge instance that connects to the PE Router. Tunnel-Z-end-IP is the other end where the Tunnel terminates. The Tunnel-A-End-PE-IP and Tunnel-Z-end-PE-IP are the A and Z End PE Router IP addresses. These IP addresses are the ones where the VRF are configured.

With the esm-mpls.conf and user-defined-connnection.conf properly configured a Tunnel instance between two VEdge instances will be created. The Tunnel will have a LayeredOverIFs relationship through which all the MPLS core network Interfaces that are used to carry this Tunnel traffic are associated. Also, two NetworkConnection instances, for A and Z end, are created between the edge and PE Router. Whenever any of the MPLS LayeredOverIFs goes down or the device itself goes does an impact will be shown to the Velocloud Tunnel.