- 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
-
Understanding Deploy Mode in Network Director
The Deploy mode enables you to deploy configuration changes and software upgrades to devices and perform several device management and configuration file management tasks.
Deploy mode is enabled for devices in Logical View, Location View, Device View, Custom Group View, and Topology View.
This topic describes:
Deploying Configuration Changes
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.
Every time you make configuration changes in Build mode that affect a device, the device is automatically added to the list of devices with pending changes.
The device is added to the list of devices with pending changes only when you make the device configuration changes.
If you make changes to the configurations (associated with the device) that are specific only to Network Director, the device is not listed with pending changes. For example, when you make changes to the profile name associated with the device, the device is not added to the list of devices with pending changes.
Configuration changes are deployed to devices at the device level. When you deploy configuration changes to a device, all pending configuration changes for that device are deployed.
You can deploy the device configurations in the following two ways:
Auto Approval—In this mode, the device configuration changes are approved automatically by the system and do not require explicit (manual) approval by a configuration approver before they can be deployed. This is the default approval mode.
Manual Approval—In this mode, the device configuration changes are required to be explicitly approved by a configuration approver before the changes can be deployed to the device.
For more information about enabling these modes, see Setting Up User and System Preferences.
For manual approval, the Network Director - Configuration Approver role is available in Junos Space, which is specific to the Network Director. A user with this role reviews device configurations and proposed changes to device configurations and can either approve or reject them.
An operator performs device configurations and creates a change request for that configuration and submits it for approval to an approver. The approvers are notified by e-mail whenever a change request is created. If a configuration or a change to it is approved by an approver, then the operator is able to deploy it. If a configuration is rejected then the operator must make the necessary changes, resubmit the change request, and procure an approval before the configuration can be deployed. For more information, see Approving Change Requests
You can specify any number of approvers. If you specify more than one approver while configuring the Manual Approval mode, once an approver accepts or rejects the proposed change, the change request is not listed for the other approvers and they cannot approve or reject the same change request.
You can do the following configuration deployment tasks on devices that have pending changes:
Run configuration deployment jobs immediately or schedule them for future times.
Approve the change requests for pending configurations, if you have selected the Manual Approval mode.
Preview pending configuration changes before deploying the changes.
Validate that the pending changes are compatible with the device’s configuration.
Manage configuration deployment jobs.
Configuration changes are validated for each device both in Network Director and on the device. If any part of a configuration change for a device fails validation, no configuration changes are deployed to the device. You can see the results of each validation phase separately.
Network Director will not deploy configuration to a device with a configuration that is out of sync (meaning that the device’s configuration differs from Network Director’s version of that device’s configuration), or to a device that has uncommitted changes to its candidate configuration. Deployment to such devices will fail.
When you schedule a deployment job, that job and any profiles and devices assigned to that job are locked within Network Director. You cannot edit the job or any of its assigned profiles until the job runs or gets cancelled. This locking feature prevents you from deploying unintended configuration changes that could result from editing profiles and devices that are already scheduled to deploy. To change any properties of a scheduled job, cancel the job and create a new scheduled job with the desired properties. You cannot edit the profile assignments of a device that has scheduled pending configuration changes.
Managing Software Images
Network Director can manage software images on the nodes it manages. You can do the following software image management tasks:
Deploy a software image stored in an image repository on the Network Director server to multiple devices with a single job.
Track the status of software image management jobs.
Stage and install software images as separate tasks.
Schedule staging and installation to happen at independent future times.
Perform several software image upgrade options, such as rebooting devices automatically after the upgrade finishes.
Using nonstop software upgrade (NSSU) to upgrade EX Series switches is supported in Network Director.
Zero Touch Provisioning
Zero touch provisioning enables you to provision new Juniper Networks switches in your network automatically—without manual intervention. When you physically connect a switch to a network and boot it with the factory-default configuration, the switch attempts to upgrade the Junos OS software automatically and autoinstall a configuration file from the network.
Managing Devices
In Deploy mode you can perform several device management tasks, including:
View the device inventory.
Show a device’s current configuration.
Resynchronize the device configuration maintained in Build mode with the configuration on the device. For more information about resynchronization of device configuration, see Understanding Resynchronization of Device Configuration
Enable or disable switch network ports.
Convert QSFP+ port configuation.
Managing Device Configuration Files
You can back up device configuration files to the Network Director server. You can perform several actions on backed up configuration files, such as restoring configuration files to devices, and viewing and comparing configuration files.
Managing Baseline Configuration
You can create a baseline of the Network Director device configuration and the OS version on the Network Director server. You can perform several actions on the baseline configuration files, such as restoring configuration files to devices, and viewing and comparing configuration files.