Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Navigation  Back up to About Overview 

Known Behavior

This section lists the known behavior in Network Director:

  • When you install Network Director Release 3.2R1 on Junos Space Network Management Platform Release 17.2R1.4 with Security Director Release 17.2R1 already installed, Network Director is not listed in the drop-down list for selecting Junos Space applications and on the Applications page (Network Management Platform > Administration > Applications) though Network Director installation job is successful.

    Workaround: You can use one of the following options to install Network Director Release 3.2R1 along with Security Director:

    Note: If you are using Security Director Release 17.2R1 with Junos Space Platform Release 17.2R1.3, install the 17.2R1-hotpatch-v1 patch and restart JBoss on all Junos Space nodes and perform the listed options.

    You can download the patch from https://webdownload.juniper.net/swdl/dl/secure/site/1/record/75246.html.

    • For a fresh or new installation of Junos Space Platform, Network Director and Security Director, use Junos Space Platform Release 17.2R1.4, Network Director Release 3.2R1, and Security Director Release 17.2R2.

    • To install Network Director Release 3.2R1 on an existing installation of Junos Space Platform Release 17.2R1.4 and Security Director Release 17.2R1, upgrade Security Director to Release 17.2R2 and then install Network Director Release 3.2R1

    • If you have already installed Network Director Release 3.2R1 on an existing installation of Junos Space Platform Release 17.2R1.4 and Security Director Release 17.2R1, perform the following steps:

      1. Upgrade Security Director to Release 17.2R2.
      2. Execute the following commands on the VIP node of the Junos Space fabric to deploy the cm.ear file.
        /usr/local/jboss/bin/jboss-cli.sh --connect --controller=jmp-Cluster "deploy /usr/local/jboss/standalone/deployments/11/cm.ear --server-groups=platform"
  • For EX4300 satellite devices to be part of a Junos Fusion Enterprise, ensure that you use U-Boot 2011.12-00062-gf837a99 (Jul 11 2014 - 13:47:59) and FreeBSD/PowerPC U-Boot bootstrap loader 2.4 as the boot loader, with PoE firmware version 2.6.3.92.1, and 10G PIC-2 ports as cluster ports.

  • Juniper Networks Data Center Switching Management Pack for vROps does not display the following:

    • Layer 3 Fabric devices under Fabric option in the Juniper Infrastructure Overview Dashboard.

    • Data in the Health, Risk and Efficiency badges for Layer 3 Fabric devices.

  • When defining your network configuration in quick templates by using a particular command, ensure that you define the subcommands individually. Stating subcommands as a single command causes errors. For example, the commands set snmp location sunnyvale and set snmp contact admin@example.com are valid when defined individually. However, if you combine these commands into the single command set snmp location sunnyvale contact admin@example.com, schema validation treats the last command contact as an extra entry and causes an error.

  • In an OpenStack+NSX based data center, the flow analysis feature is not supported for virtual machines that are part of more than one network or VNI.

  • Network Director does not support Junos Space domains and subdomains. Do not assign devices to domains and subdomains in Junos Space.

  • EX4300 switch running Junos OS Release 14.1X53-D10 or 14.1X53-D15 cannot be managed using Network Director.

  • If you are using Microsoft Internet Explorer version 9.0 or 10.0, the View Connectivity task in the Datacenter View and the Flow Analysis > View Details subtask in the Dashboard View might not work as expected. Use a supported version of Google Chrome or Mozilla Firefox to perform these tasks.

  • EX4600 switches are grouped under Campus Switching ELS platform in Network Director even though the device family for EX4600 displays as JUNOS-QFX in the Inventory page. All Campus Switching ELS profiles can be associated with these switches.

    You must use the QFX schema to manage this device instead of the EX ELS schema.

  • In Location View, if you assign all the members of a Virtual Chassis, Virtual Chassis Fabric, or QFabric system to buildings or floors, then none of the Device level tasks are available. We recommend that you assign the entire logical device—the QFabric system, Virtual Chassis, or the Virtual Chassis Fabric—to any given location.

  • For Data Center switching ELS Port profile, profile assignment might fail for single and multiple devices after you specify the port range of channelized interfaces even if the range you specified is within the range available on the device (or devices).

  • When an EX4300 switch is used as a member switch in a QFX5100 mixed mode Virtual Chassis or Virtual Chassis Fabric, Network Director does not consider the configurations that you make on DCBX and Device Count fields, and configuration commits fail.

  • If QFX3500, QFX3600, or EX4300 Virtual Chassis are running releases earlier than Junos OS Release 13.2X51-D20, any changes made to the Virtual Chassis, such as adding or deleting members or changing the role of members, might not reflect in Network Director.

  • Deploying a Fabric profile that has the same name as an already deployed Fabric profile, but a different Fabric ID, removes the interface association of the first Fabric profile from the device. Therefore, do not deploy Fabric profiles with the same name on a device.

  • With QFabric systems that are running Junos OS releases earlier than Release 13.1X50-D20, the Control Plane Topology does not work if the CPE switches are used in Virtual Chassis mode. If you need assistance with an earlier release, contact Juniper Networks support.

  • Network Director does not support access points that are directly connected to a controller.

  • Nonstop software upgrade (NSSU) for EX8200 Virtual Chassis might not work as expected.

  • The Access profile configuration and the port security configuration that are part of the Port profile configuration might not work on EX9200 switches running Junos OS Release 12.3R2.5.

  • Alarms generated on individual QFabric nodes do not display in Topology View. Bandwidth utilization value for VCP and aex interfaces might not be displayed in the Topology View.

  • Network Director might not display:

    • Unprovisioned members added to a Virtual Chassis or a Virtual Chassis Fabric.

    • The Not Present status for members removed from a Virtual Chassis or a Virtual Chassis Fabric.

  • For Data Center Switching ELS Port profile, a profile assignment might fail for channelized interfaces in a port range even when the channelized interfaces in that port range are available on the devices.

  • The Validate Pending Configuration task does not validate the unsupported configurations on data center devices.

  • In the manual mode, when out-of-band changes are resynchronized, the conflicting CR might not be listed for quick templates.

  • In the Edit Layer 3 Fabric workflow, the deployment status might display as Failed for replaced or deleted QFX5100 or EX4300 switches (running Junos OS Release 13.2X51-Dnn) even if the configuration is successfully deployed on the device. Also, it might take more than 10 minutes for the device status to be updated in the Edit Layer 3 Fabric job.

  • During a cluster switchover, if a backup configuration job or a device discovery job is running in Network Director, the switchover status might display as In progress even after the switchover is complete.

  • In a Junos Fusion setup, you might need to assign two aggregation devices for an auto-profile policy. For example, if a satellite device has 65 ports, then you might need to add two aggregation devices as  
    AD1: ge-65/0/1- ge-65/0/10 and AD2 : ge-65/0/1 - ge-65/0/10. To assign both the aggregation devices, select the aggregation devices at the group level and do not select the satellite device.

  • When editing a MACsec profile that is already deployed in Network Director, you can modify all the configuration parameters in the MACsec profile, except the Connection Association Name and MACsec mode.

  • The resynchronization job for the MX Series device fails if the VLAN ID for the device is configured as none from the device CLI.

  • You cannot modify the configuration for a Layer 3 Fabric from Network Director if the Layer 3 Fabric was created using the brownfield process during device discovery in Network Director.

Modified: 2018-05-10