- play_arrow Working With Network Director
- play_arrow About Network Director
- play_arrow Installing Network Director
- play_arrow Accessing Network Director
- play_arrow Understanding Network Director System Administration and Preferences
- play_arrow Getting Started with Network Director
-
- play_arrow Working with the Dashboard
- play_arrow About the Dashboard
- play_arrow Using the Dashboard
- play_arrow Dashboard Widget Reference
-
- play_arrow Working in Build Mode
- play_arrow About Build Mode
- play_arrow Discovering Devices
- play_arrow Setting Up Sites and Locations Using the Location View
- Understanding the Location View
- Setting Up the Location View
- Creating a Site
- Configuring Buildings
- Configuring Floors
- Setting Up Closets
- Assigning and Unassigning Devices to a Location
- Changing the Location of a Device
- Deleting Sites, Buildings, Floors, Wiring Closets, and Devices
- Configuring Outdoor Areas
- play_arrow Building a Topology View of the Network
- play_arrow Creating Custom Device Groups
- play_arrow Configuring Quick Templates
- play_arrow Configuring Device Settings
- play_arrow Configuring Authentication, Authorization, and Access for Your Network
- play_arrow Configuring Interfaces and VLANs
- Understanding Port Profiles
- Creating and Managing Port Profiles
- Assigning and Unassigning Port Profiles from Interfaces
- Managing Auto Assignment Policies
- Creating Auto Assignments
- Configuring Easy Config Setup
- Understanding Port Groups
- Creating and Managing Port Groups
- Understanding VLAN Profiles
- Creating and Managing VLAN Profiles
- Assigning a VLAN Profile to Devices or Ports
- play_arrow Configuring Firewall Filters (ACLs)
- play_arrow Configuring Class of Service (CoS)
- play_arrow Configuring Media Access Control Security (MACsec)
- play_arrow Configuring Link Aggregation Groups (LAGs)
- play_arrow Creating and Managing Fabrics
- Understanding Junos Fusion
- Understanding Junos Fusion Enterprise
- Software Requirements for Junos Fusion
- Creating and Managing Fusion Configuration Templates
- Managing Fusion Fabrics
- Creating and Managing Satellite Software Upgrade Groups
- Understanding Layer 3 Fabrics
- User Privileges Required for the DHCP and File Server While Using Zero Touch Provisioning
- Managing Layer 3 Fabrics
- Creating Layer 3 Fabrics
- Editing Layer 3 Fabrics
- Viewing Layer 3 Fabric Connectivity
- Performing Layer 3 Fabric Connectivity Checks
- play_arrow Configuring VRRP Profiles
- play_arrow Managing Network Devices
- Viewing the Device Inventory Page
- Physical Topology
- Viewing Profiles Assigned to a Device
- Viewing the Physical Inventory of Devices
- Viewing Licenses With Network Director
- Viewing a Device's Current Configuration from Network Director
- Assigning Devices to Logical Category
- Accessing a Device’s CLI from Network Director
- Accessing a Device’s Web-Based Interface from Network Director
- Deleting Devices
- Rebooting Devices
- Viewing Virtual Machines
-
- play_arrow Monitoring Devices and Traffic
- play_arrow About Monitor Mode
- play_arrow Monitoring Traffic
- play_arrow Monitoring Client Sessions
- play_arrow Monitoring Devices
- play_arrow Monitoring and Analyzing Fabrics
- play_arrow Monitoring Virtual Networks
- play_arrow General Monitoring
- play_arrow Monitor Reference
- 802.11 Packet Errors Monitor
- Access vs. Uplink Port Utilization Trend Monitor
- Current Sessions Monitor
- Current Sessions by Type Monitor
- Error Trend Monitor
- Equipment Summary By Type Monitor
- Node Device Summary Monitor
- Port Status Monitor
- Port Status for IP Fabric Monitor
- Port Utilization Monitor
- Power Supply and Fan Status Monitor
- Resource Utilization Monitor for Switches, Routers, and Virtual Chassis
- Status Monitor for Junos Fusion Systems
- Status Monitor for Layer 3 Fabrics
- Status Monitor for Switches and Routers
- Status Monitor for Virtual Chassis
- Status Monitor for Virtual Chassis Members
- Top Talker - Wired Devices Monitor
- Traffic Trend Monitor
- Unicast vs Broadcast/Multicast Monitor
- Unicast vs Broadcast/Multicast Trend Monitor
- User Session Details Window
- Virtual Chassis Topology Monitor
- VC Equipment Summary By Type Monitor
-
- play_arrow Using Fault Mode
- play_arrow About Fault Mode
- play_arrow Using Fault Mode
- play_arrow Fault Reference
-
- play_arrow Working in Report Mode
- play_arrow About Report Mode
- play_arrow Creating and Managing Reports
- play_arrow Report Reference
-
- play_arrow Working with Network Director Mobile
- play_arrow About Network Director Mobile
- play_arrow Getting Started with Network Director Mobile
- play_arrow Working in the Network Director Mobile Dashboard Mode
- play_arrow Working in the Network Director Mobile Devices Mode
-
Resynchronizing Device Configuration
A network managed by Network Director has three repositories of information about the configuration of a network device—the configuration stored on the device itself, the device configuration record maintained by Junos Space, and the Build mode configuration maintained by Network Director.
When the configuration contained in all three repositories match, the device configuration state is shown as In Sync in Network Director. When the repositories do not match, the configuration state is shown as Out of Sync. A common cause for this state is out-of-band configuration changes—that is, configuration changes made to a device outside of Network Director.
When a device state is Out of Sync, you cannot deploy configuration changes on the device in Deploy mode. Use the Resynchronize Device Configuration task to resynchronize the three configuration repositories and change the device configuration state back to In Sync.
How the Resynchronize Device Configuration task performs the resynchronization depends on the system of record (SOR) mode setting for the Junos Space Network Management Platform:
When Junos Space is in network as system of record (NSOR) mode, the device is considered the system of record for configuration. When you resynchronize a device when Junos Space is in NSOR mode, both the Junos Space configuration record and the Network Director Build mode configuration are updated to reflect the device configuration—in other words, the out-of-band configuration changes are incorporated into both the Junos Space and the Network Director configuration repositories.
When Junos Space is in Junos Space as system of record (SSOR) mode, you can choose whether accept or reject the out-of-band changes reflected in the device configuration. If you accept the changes, both the Junos Space configuration record and the Network Director Build mode configuration are updated to reflect the device configuration. If you reject the changes, the out-of-band changes are rolled back on the device so that the device configuration matches the Junos Space configuration record and the Network Director Build mode configuration.
For more information about out-of-band configuration changes, Junos Space SOR modes, and how Network Director resynchronizes device configuration, see Understanding Resynchronization of Device Configuration.
This topic covers:
The Resynchronize Device Configuration List of Devices
The Resynchronize Device Configuration page displays a list of all devices in the selected scope whose configuration was successfully imported during device discovery and whose configuration state is now Out Of Sync. You can select devices from this list and resynchronize them.
Table 1 describes the fields in the list of devices.
Field | Description |
---|---|
Name | Device hostname or device IP address. |
IP address | IP address of device. |
Model | Model number of the device. |
OS Version | Operating system version currently running on the device. |
Connection State | Connection state:
|
Configuration State | Shows the configuration state of the device:
If the resynchronization is successful, the device is removed from the table. |
Local Changes | Specifies whether configuration changes have been made in Build mode and are pending deployment on the device.
Note: The Pending Changes window that appears when you click View allows you to see what profiles have been added, modified, or changed. However, because the device is not in sync, you cannot view the specific changes in CLI or XML format. |
Network Changes | Indicates whether you can view the out-of-band changes:
|
Resynchronizing Devices When Junos Space Is in NSOR Mode
To resynchronize devices when the Junos Space Network Application Platform is in NSOR mode:
Resynchronizing Devices When Junos Space Is in SSOR Mode
To resynchronize devices when the Junos Space Network Management Platform is in SSOR mode:
Device changes made by the Junos Space configuration editor or device changes that have been accepted in Junos Space cannot be rejected. Even if you select Reject device changes, these changes will not be rejected and instead will be incorporated into the Build mode configuration.
Resynchronizing Devices in Manual Approval Mode
When out-of-band changes exist, device resynchronization merges the changes done by using the CLI with the local changes provided that there are no conflicts. If there are conflicting changes, the changes made using the CLI take precedence over the local changes. Therefore, configuration changes that are part of a change request might be lost. The configuration change requests that are lost are marked as Cancelled against the corresponding device. When device resynchronization is initiated for a device, a message is displayed that lists the change requests that will be lost because of conflicting CLI and local changes. All other changes remain unaffected.
Viewing the Network Changes
The Network Changes window shows the out-of-band configuration changes made to a device when Junos Space is in SSOR mode.
Not all out-of-band configuration changes are shown in this window. Configuration changes are shown only when the device configuration differs from the Junos Space configuration record—that is, when the device configuration state in Junos Space is not In Sync. For example, if the out-of-band changes were deployed from the Junos Space configuration editor or if the out-of-band changes were already accepted in Junos Space, the configuration changes will not appear in this window.
The configuration changes are shown in XML format. If there have been multiple out-of-band changes—that is, there has been more than one configuration commit, or save, on the device—the changes are grouped by each commit.
The following information is provided for each configuration commit:
junos:commit-seconds—Specifies the time when the configuration was committed as the number of seconds since midnight on 1 January 1970.
junos:commit-localtime—Specifies the time when the configuration was committed as the date and time in the device’s local time zone.
xmlns:junos—Specifies the URL for the DTD that defines the XML namespace for the tag elements.
junos:commit-user—Specifies the username of the user who requested the commit operation.
Viewing Resynchronization Job Status
The Resychronize Device Configuration Results window appears after you start a resynchronization job. This window is automatically updated with the resynchronization status for each device when the job completes.
You can also view the status of the resynchronization jobs using the Manage Jobs task in System mode. The following jobs are associated with resynchronization:
Resynch Network Elements—This job runs in NSOR mode and resynchronizes the Junos Space configuration record with the device configuration.
Resolve OOB Changes—This job runs in SSOR mode and resolves the out-of-band changes for Junos Space—either accepting the changes and updating the Junos Space configuration or rejecting the changes and rolling back the changes on the device.
Resynchronize devices—This job runs in both NSOR and SSOR mode and resynchronizes the Build mode configuration with the device configuration.