The variable, SM_ENABLE_SNMP_SET, must be set to TRUE in order for remote ping to work. Starting with MPLS Management Suite 4.0, this variable is set to TRUE by default in the runcmd_env.sh file.

For releases prior to MPLS Management Suite 4.0, the remote ping functionality is disabled for the MPLS Topology Server and the MPLS Monitoring Server.

If you copied the runcmd_env.sh file from an older release to use with MPLS Management Suite 4.0 or higher, check to determine whether this variable is set properly. If not, enable the remote ping functionality by adding the following environment variable definition to the runcmd_env.sh file:

SM_ENABLE_SNMP_SET=TRUE

The runcmd_env.sh file in the MPLS Management Suite installation area will automatically set the SM_ENABLE_SNMP_SET environment variable, along with any other environment variables in the file, for each application or utility that is started from the installation area.

To enable the remote ping functionality:

  1. Go to the BASEDIR/smarts/bin directory in the MPLS Management Suite installation area and type the following command to open the runcmd_env.sh file:

                   sm_edit conf/runcmd_env.sh

  2. Add the following line to the file:

                   SM_ENABLE_SNMP_SET=TRUE

  3. Save and close the file.

    The modified version of the runcmd_env.sh file is saved to the BASEDIR/smarts/local/conf directory.

  4. If the MPLS Topology Server and the MPLS Monitoring Server were running before you edited the runcmd_env.sh file, restart each server.

    The VMware Smart Assurance MPLS Management Suite User Guide provides information about invoking an on-demand remote ping and deploying a periodic remote ping instance. Chapter 9, “Configuring Polling and Remote Ping Groups,” provides the procedure for deploying periodic remote ping instances.