When you make configuration changes in Build mode, the changes are not deployed to devices automatically. You must manually deploy the changes to devices in Deploy mode.
To start deploying configuration changes:
Depending upon the type of approval mode you select different windows are displayed.
If you select the Auto Approval mode, the Devices with Pending Changes page opens in the main window, listing the devices within the selected node that have pending configuration changes.
If you select the Manual Approval mode, the following two sections open in the main window:
This topic describes:
Based on the approval mode, you can choose to deploy the device configuration changes in the following ways:
Table 261 describes the information provided in the table on the Devices with Pending Changes page. Only the subset of devices within the selected object that have pending configuration changes are listed in the table.
Table 261: Devices with Pending Changes Page
Table Column | Description |
|---|---|
Check box | Select to perform an action on the device in that row |
Name | Device name |
IP Address | Device IP address |
Model | Device Model |
OS Version | Operating system version running on device |
Connection State | State of the connection to the device:
|
Configuration State | Indicates whether the device’s configuration is in sync with Network Director’s version:
|
Configuration Changes | Click to view pending configuration changes for a device. The Pending Changes window opens. |
If you select the Manual Approval mode, the windows Devices with recent configuration changes and Change Requests opens.
From the Devices with recent configuration changes window, you can:
Note: You cannot delete a device from the Devices with Pending Changes list. To remove a device from the list, you must undo the Build mode configuration changes that placed the device on the list.
Table 262 describes the information provided in the table on the Devices with recent configuration changes page.
Table 262: Devices with recent configuration changes
Table Column | Description |
|---|---|
Name | Indicates the name of the device and profile node. Below each device node, a profile node is listed. |
Change Type | Indicates the type of the configuration change done to the device. |
Associations Added | Lists the ports that are added to that profile. |
Associations Deleted | Lists the ports that are deleted from that profile. |
Configuration | Click to view pending configuration changes for a device. The Pending Changes window opens. |
Deployment State | Indicates the deployment state of a change request. |
From the Change Requests window, you can:
Table 263 describes the information provided in the table on the change requests submitted for the devices for which configuration changes are sought.
Table 263: Change Requests
Table Column | Description |
|---|---|
Check Box | Select to perform an action on the device in that row. |
Change Request No | Indicates the change request number of the change request that is waiting to be deployed. |
Title | Indicates the title name of the change request. |
Created On | Indicates the change request creation date. |
Approver | Indicates the username of the configuration approver. |
Last Action On | Indicates the date on which the change request status is changed. |
Approval Status | Indicates whether a change request is approved or rejected by the approver. |
Deployment Status | Indicates whether a change request is deployed after the approval. |
History Icon | Records the audit trial details of a change request, such as operation performed on a change request during a given period of time, username of the approver or operator, and so on. |
Use the Change Request Details window to view the details of the change request before you either approve or reject a change request. This window provides you the details such as change request number, title, username of the user who created the change request, change request creation date and so on. A Devices table is also displayed showing the deployment status. Table 264 describes the fields in this table.
Table 264: Change Request Details
Column | Description |
Name | Indicates the name of the device and profile node. Below each device node, a profile node is listed. |
Change Type | Indicates the type of the configuration change done to the device. |
Associations Added | Lists the ports that are added to that profile. |
Associations Deleted | Lists the ports that are deleted from that profile. |
Configuration | Click to view pending configuration changes for a device. The Pending Changes window opens. |
Deployment Status | Indicates the deployment state of a change request. |
To create a change request for device configurations approval:
The Create Change Request page opens.
You can either enter a number or retain the autogenerated number in this field.
The Create Change Request page opens, listing the change request details such as change request number, title, and comment, along with the change request submission job details. A Devices table is also displayed showing the validation status of the device and configuration generated for that device.
A new change request entry with the status Pending Approval is added to the Change Request section.
When you deploy configuration changes to a device, validation checks are performed to validate that the pending changes are compatible with the device. You can also perform this validation without deploying.
Note: You can also verify the configuration from the Build mode by clicking Tasks > Domain Management > Validate Pending Configuration.
To validate that the pending changes for devices are compatible with the device configuration:
Note: For Manual Approval mode, you cannot choose the devices for which validation needs to be done. All the configuration changes for all the devices are validated.
The Configuration Validation window opens. See Using the Configuration Validation Window for a description of the window.
Use the Discard Local Configuration Changes Results window to discard all the pending configurations that were made on a device. Once you discard the local configuration changes on a device, the configuration state of the device changes to In Sync or Out of Sync based on the system of record (SOR) mode set for the Junos Space Network Management Platform. If the SOR mode is set to Network as system of record (NSOR), then the configuration state changes to In Sync and if the SOR mode is set to Junos Space as system of record (SSOR), then the configuration state changes to Out of Sync.
To discard the configuration changes:
The Discard Local Configuration Changes Results window opens displaying the status of the discard pending configuration job.
To view pending configuration changes for a device, click View in the Pending Changes column.
The Pending Changes window opens. See Using the Pending Changes Window for a description of the window.
Use the Pending Changes window to view the pending Network Director changes for a device. Table 265 describes the fields in this window.
Table 265: Pending Changes Window
Field | Description |
|---|---|
Name | Lists each selected device. Expand a device by clicking its plus sign to see its pending changes. Each pending change to a profile or other configuration object for the device is listed. |
State | Describes the nature of the pending change to the configuration object. These are the possible states:
|
Configuration | Click View to view the pending configuration changes for a device. The Pending Configuration window opens. See Using the Configuration or Pending Configuration Window for information about the window. Note: The device configuration state must be In Sync for you to view the pending configuration changes. |
Close | Click to close the window. |
Use the Pending Configuration window to view the configuration changes that will be deployed to a device when a job runs. Use the Configuration window to see changes that were deployed to a device when a completed job ran. The configuration changes are shown in these formats:
In both views, the content is color-coded for easier reading:
Use the Deploy Configuration Errors/Warnings window to view the results of deploying configuration to a device. The Errors/Warnings in validating the device configuration pane shows the results of configuration validation by Network Director. The Errors/Warnings in Updating Device configuration pane shows the results of configuration validation on the device.
Use the Configuration Validation window to validate that the pending changes for a device are compatible with the device’s configuration. Table 266 describes this window.
Table 266: Configuration Validation Window
Table Column | Description |
|---|---|
Object name | Lists the devices you selected for validation. Click the arrow next to a device to expand it. If there are no errors or warnings, one item labeled No Validation warnings appears. If the device has errors or warnings, they appear under the device. The device contains a list of the profiles that caused errors or warnings. Expand a profile name to see the of errors and warnings it caused. |
Errors/Warnings | Describes the error or warning. |
To deploy configuration changes to devices immediately:
The Deploy Options window opens.
The configuration deployment job runs. The Deploy Configuration window opens and shows the results of the deployment job. For a description of fields in this window, see Deploy Configuration Window.
To schedule configuration deployment to devices:
The Deploy Options window opens.
Use the Deploy Options window to schedule configuration deployment jobs. Table 267 describes the actions for the fields in this window.
Table 267: Deploy Options Window
Field | Action |
|---|---|
Deployment Job Name | Enter a job name. |
Date and Time | Enter the job’s start date and time. |
OK | Click to accept changes and exit the window. |
Cancel | Click to cancel changes and exit the window. |
You can edit a change request to change the profile that was added to a device or delete some of the profile associations. After editing a change request, you can resubmit the change request for approval. While editing a change request, if you try to delete all the profile associations in a given change request, the system prompts a message that a change request should have at least one valid association. Deleting all the associations in a change request makes it invalid. Hence, you cannot delete all the associations in a given change request. However, you can delete a change request itself to delete all the associations for that change request.
Note: You are unable to delete a change request or an association of a change request if an association is in pending removal state.
You are unable to edit a change request that is in Cancelled, Deployed, Rollback Success, or Rollback Failed state.
To change a profile or delete the profile associations of a change request:
The Edit Change Request window opens.
The Edit Change Request window opens, listing the change request details such as change request number, title, and comment, along with the change request submission job details. A Devices table is also displayed showing the validation status of the device and configuration generated for that device.
Sometimes you might need to delete a change request from the change request list. A change request is assigned with profile associations. If you delete a change request, all the associations of that change request are also deleted.
To delete a change request:
The Delete Change Request window opens, displaying the message: Are you sure you want to delete Change Request?.
If you clicked Yes, the message: Change Request deleted successfully appears.
You can resubmit only those change requests that are in Pending Approval, Pending Deployment, Deploy Failed, and Create Failed state. You are unable to resubmit change requests in Deployed, Cancelled, Rollback Success, or Rollback Failure state.
In certain situations, a device can go out of sync while a user is creating a change request for that device. The change request is created, but the configuration changes for that change request are not generated. You can select the change request and resubmit it after the device is in sync again, which generates the configuration for this change request. You can resubmit change requests only for devices that have pending configuration changes.
To resubmit a change request:
A warning message pops up indicating if you want to resubmit the change request.
The Resubmit Change Request window opens, listing the change request details such as change request number, title, and comment, along with the change request submission job details. A Devices table is also displayed showing the validation status of the device and configuration generated for that device.
In case of any misconfigurations, you can choose to roll back a configuration that has already been deployed to the device. The following conditions apply for a rollback operation:
To roll back a device:
You can view the stored configuration also user can view the difference of the current device configuration and stored configuration.
Note: You can choose only one rollback configuration out of the available configurations per device however you can choose multiple devices.
A rollback job is started with all the selected devices and all the devices are resynchronized after the configuration is pushed.