The MPLS Manager installation directory contains the configuration directories that are shown in Configuration directories for MPLS Manager.
![](images/GUID-3C8096CF-81F5-4D39-A517-CA1528C6EE4B-low.bmp)
BASEDIR, which is not an environment variable, is used in documentation to represent the top-level directory structure of an VMware Smart Assurance product installation. For the VMware Smart Assurance MPLS Management Suite, BASEDIR represents <root_dir>/MPLS.
Each configuration directory in Figure 6 contains the bootstrap and configuration files for its associated MPLS or VPN server. The --config option in a server startup command points to the appropriate configuration directory:
-
The --config=mpls-t option in an MPLS Topology Server startup command points to the bootstrap and configuration files in the mpls-t directory. The default name of the MPLS Topology Server is INCHARGE-MPLS-TOPOLOGY.
-
The --config=mpls-m option in an MPLS Monitoring Server startup command points to the bootstrap and configuration files in the mpls-m directory. The default name of the MPLS Monitoring Server is INCHARGE-MPLS-MONITORING.
-
The --config=mpls-a option in an MPLS Analysis Server startup command points to the bootstrap and configuration files in the mpls-a directory. The default name of the MPLS Analysis Server is INCHARGE-MPLS-ANALYSIS.
-
The --config=vpn-tagging option in an MPLS VPN-Tagging Server startup command points to the bootstrap and configuration files in the vpn-tagging directory. The default name of the optional MPLS VPN-Tagging Server is VPN-TAGGING.
The bootstrap and configuration files for an MPLS server or the MPLS VPN-Tagging Server determine the role of the server and set up the environment for the server.