Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?


Known Behavior

This section lists the known behavior in Network Director Release 7.1R1.

  • When you discover devices in Network Director for the first time, the syslog pattern BR_INFRA_DEVICE is pushed into the device for JUNOS and JUNOS-QFX device families.
  • The following alarms are cleared automatically when the corresponding clear event is received, and are available as part of the clear alarm list.
    • FanFailureAlarm
    • TemperatureAlarm
    • HardDiskFailedAlarm
    • PMonOverloadSetAlarm
    • DomAlertSetAlarm
    • POE Power usage High
    • VccpPortAlarm and VccpMemberAlarm
    • PowerSupplyFailureAlarm and PowerSupplyInputFailureAlarm
    • CosFabricQueueOverflowAlarm and CosWanQueueOverflowAlarm
    • FRUPowerOffAlarm, FRUFailedAlarm, and FRUOfflineAlarm
    • CollUnavailableDestAlarm, CollFlowOverloadAlarm, and CollMemoryUnavailableAlarm
    • JdhcpLocalServerIfLimitExceededAlarm and Jdhcpv6LocalServerIfLimitExceededAlarm
    • FabricPowerSupplyFailure, FabricFanFailure, FabricTemperatureAlarm, FabricFruPowerOffAlarm, FabricFruFailedAlarm, and FabricFruOfflineAlarm
  • Sometimes the CMEventAttributes table grows to several GBs and consumes disk space. To overcome this, execute the following steps after installing Network Director 3.8R1 or after upgrading Network Director to 3.8R1:
    1. Log in into Network Director.
    2. Go to Preference -> Fault -> Additional Setting.
    3. Modify the Number of Days to keep the alarm and event or alarm.

      Modify the Number of Days such that it triggers a purge event that clears all existing alarms and events. This is a one-time activity.

    4. Click OK.
  • If the alarms are not purged, truncate the tables CMEvent, CMEventAttributes, CMAlarm, CMAlarmAttributes using the following steps. This clears the tables of all existing alarms and events. You can view any new alarms and events generated thereafter in Network Director. The alarms will be purged as expected after you perform this procedure.

    1. Take a backup of the current database.

    2. Stop the JBoss server using the following commands:

    3. Run the following MySQL commands one after the other:

    4. Start the JBoss server using the following command:

    5. After JBoss started, execute the following steps:

      1. Log in into Network Director.

      2. Go to Preference -> Fault -> Additional Setting.

      3. Modify the Number of Days to keep the alarm and event or alarm.

        Modify the Number of Days such that it triggers a purge event that clears all existing alarms and events. This is a one-time activity.

      4. Click OK.
  • 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, and 10G PIC-2 ports as cluster ports.

  • 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 are valid when defined individually. However, if you combine these commands into the single command set snmp location sunnyvale contact, schema validation treats the last command contact as an extra entry and causes an error.

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

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

  • 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.

  • 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 devices.

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

  • 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.

  • When viewing real-time traffic analysis on a particular port, if Network Director configures the sflow command on the device, the command is deleted when you close the Real Time window. Similarly, if a third-party tool sets the sflow configuration on a particular port to view real-time traffic analysis on the port, the sflow configuration is removed when you close the Traffic Analysis page.

  • Network Director does not support cold migration of virtual machines. Cold migration is the migration of a virtual machine that is powered off.

  • When the port statistics counters on a device are reset either manually or during an image upgrade, the traffic widgets might show incorrect values for some time. If this happens, wait for 2 to 3 poll intervals, after which the issue resolves itself.

  • The following wireless application user interface screens are still available in Logical View > Monitor > Client. These user interface screens are not applicable to campus architecture.

    • Top Users

    • Top Sessions by MAC address

    • Session Trends

    • Current Sessions by Type