Support Support Downloads Knowledge Base Case Manager My Juniper Community

Knowledge Base

Search our Knowledge Base sites to find answers to your questions.

Ask All Knowledge Base Sites All Knowledge Base Sites JunosE Defect (KA)Knowledge BaseSecurity AdvisoriesTechnical BulletinsTechnotes Sign in to display secure content and recently viewed articles

How to interpret the Delta Config Summary output?

0

0

Article ID: KB9847 KB Last Updated: 05 Jul 2010Version: 5.0
Summary:
The Delta Config Summary output consist of 3 sections which allows the administrator to determine what is currently configured on the device, what is currently configured in NSM and what commands would be sent to the device in order to make the device consistent with NSM.
Symptoms:
Symptoms & Errors:
  • Delta Config contains Unset and Set commands
  • How to confirm "Currently on device" is correct
Solution:
The Delta Config Summary allows the administrator to determine:
  • What is currently configured on the device
  • What is currently configured in NSM
  • What commands would be sent to the device in order to make the device consistent with NSM.

Typical the commands to be sent to the device can include  “unset” followed by “set” commands for the same policy.    This usually means that the policy has to be recreated in order to correct it.    The same can apply for VPN configurations.  If some settings have changed, it is possible that NSM tries to unset then set the VPN to reconfigure the parameters.

If the output from the section “currently on the device” does not seem accurate, compare this information to the output from the WebUI or CLI command “get config” .  Confirm the corresponding parameter is set correctly.    If the WebUI and CLI show the setting is correct but NSM still reports the device has a different value, the problem is most likely a result of the  XML style configuration provided to NSM by the device.  To confirm, use the ScreenOS command:  “get config datafile”.      This will confirm whether the value reported by the device is incorrect.  If it is,  contact JTAC; consult KB9846 - What information do I need to Collect before Opening an NSM case?

Related Links

Comment on this article > Affected Products Browse the Knowledge Base for more articles related to these product categories. Select a category to begin.

Getting Up and Running with Junos

Getting Up and Running with Junos Security Alerts and Vulnerabilities Product Alerts and Software Release Notices Problem Report (PR) Search Tool EOL Notices and Bulletins JTAC User Guide Customer Care User Guide Pathfinder SRX High Availability Configurator SRX VPN Configurator Training Courses and Videos End User Licence Agreement Global Search