Configuration pull returns hierarchical format instead of “display set” format

Products

• Network Observability

Issue/Introduction

You observe that a configuration pull in NCM returns the configuration in a hierarchical format rather than the expected "display set" format for Juniper Networks devices running Junos OS.

Environment

All supported releases of NCM

Cause

The global variable responsible for using "set" configurations is disabled by default in the standard Juniper configuration variables file.

Resolution

Follow these steps to enable the "display set" format for Juniper configuration pulls:

1. Create the Custom Directory: Create the folder $VOYENCE_HOME/custompackage/juniper/ if it does not already exist. You must ensure that this folder's permissions, owner, and group match those of the original directory at $VOYENCE_HOME/package/juniper/.

2. Copy the Configuration File: Copy the stdjunipervars.inc file from $VOYENCE_HOME/package/juniper/ to the newly created $VOYENCE_HOME/custompackage/juniper/ folder. You must ensure the file permissions, owner, and group are identical to the original source file.

3. Modify the Variable: Open the file $VOYENCE_HOME/custompackage/juniper/stdjunipervars.inc and locate the following line: var<const> glblUseSetConfigs = false;

   Change the line to: var<const> glblUseSetConfigs = true;

   Save your changes to the file.

4. Restart Services: You restart the services by executing the following command: service vcmaster restart

5. Verify Results: If the display does not update automatically, you pull a new configuration from the device and verify the format.

Note: The difference between hierarchical and display set formats typically applies only to Juniper Networks devices running the Junos OS.