Junos Space Network Director Release Notes, Release 2.5

Junos®Space Network Director Release

Notes

Release 2.530 September 2015

Junos Space Network Director enables unified management of EX Series Ethernet

Switches, EX Series switches with ELS, QFX Series switches, QFX Series switches with

ELS, MX Series routers, Data Center fabrics (QFabrics, Virtual Chassis Fabrics, and Layer

3 Fabrics), cloud-based and bare-metal-based data centers, and Juniper NetworksWLC

SeriesWireless LAN Controllers (WLCs) in your network.

Contents Network Director Release Notes, Release 2.5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

New Features for Network Director . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

Junos Space Network Management Platform Requirements . . . . . . . . . . . . . . 5

Supported Platforms for Network Director Release 2.5 . . . . . . . . . . . . . . . . . . . 5

Junos Space DMI Schema Requirements for Network Director . . . . . . . . . . . . 8

Installation Instructions for Network Director Release 2.5 . . . . . . . . . . . . . . . . 10

Operational Notes on General Interface Use . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Operational Notes on Device Discovery and Management . . . . . . . . . . . . . . . 12

Third-Party Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Known Limitations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Known Issues in Network Director Release 2.5 . . . . . . . . . . . . . . . . . . . . . . . . . 15

Junos Space Documentation and Release Notes . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Documentation Feedback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Requesting Technical Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Self-Help Online Tools and Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Opening a Case with JTAC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Revision History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

1Copyright © 2016, Juniper Networks, Inc.

Network Director Release Notes, Release 2.5

• Overview

• New Features for Network Director

• Junos Space Network Management Platform Requirements

• Supported Platforms for Network Director Release 2.5

• Junos Space DMI Schema Requirements for Network Director

• Installation Instructions for Network Director Release 2.5

• Operational Notes on General Interface Use

• Operational Notes on Device Discovery andManagement

• Third-Party Integration

• Known Limitations

• Known Issues in Network Director Release 2.5

Overview

Junos Space Network Director enables unified management of EX Series Ethernet

Switches, EX Series switches with ELS, QFX Series switches, QFX Series switches with

ELS, MX Series routers, Data Center fabrics (QFabrics, Virtual Chassis Fabrics, and Layer

3 Fabrics), cloud-based and bare-metal-based data centers, and Juniper NetworksWLC

SeriesWireless LAN Controllers (WLCs) in your network. It provides for full network life

cycle management by simplifying the discovery, configuration, visualization, monitoring,

andadministrationof largenetworkscontainingphysical andvirtualdevices. Thesoftware

images for Network Director, Junos Space Management Platform, management packs,

and the release notes for Network Director Release 2.5 are available at the Junos Space

and Junos Space Network Director Download page.

New Features for Network Director

• Multichassis link aggregation groups (MC-LAGs) support—Network Director supports

MC-LAG configuration andmanagement. MC-LAG enables a device to form a logical

LAG interface with two other peer switches. Some of the key features in this

implementation of MC-LAG are, support for:

• Layer 3 networks through VRRP (Virtual Router Redundancy Protocol)

• Active-Standbymode

• Configuring LAG in the client device

• Standalone aggregation switches, such as EX9200 and QFX10002 devices

• NewHardware Support—Network Director now supports discovery andmanagement

of QFX10002-36Q and QFX10002-72Q switches. QFX10002 switches are designed

to be deployed as core or aggregation switches in data centers. These feature-rich

switches are fixed format and can be used as 40 Gigabit Ethernet. Depending on the

switch model, these switches can support either 36 or 72 top-of-rack switches. You

can create and assign the following profiles on QFX10002 switches:

Copyright © 2016, Juniper Networks, Inc.2

Junos Space Network Director Release Notes, Release 2.5

http://www.juniper.net/support/downloads/space.html

http://www.juniper.net/support/downloads/space.html

• Port Profile

• VLAN Profile

• Filter Profile

• Device Profile

• CoS Profile

Inaddition to theseprofiles, theLAGfunctionality isalsoextended tosupportQFX10002

switches.

• Enhancements to the Layer 3 Fabric feature—The Layer 3 Fabric feature is enhanced

with the following changes:

• QFX10002-72Q or QFX10002-36Q can be added as a spine device.

• QFX5100-48T, QFX5100-48S, andQFX5100-96SVirtual Chassis (2members) can

be added as leaf devices.

• TheCablingPlanpagealsodisplays theVirtual Chassis connections andaccess LAG

ports.

• JuniperNetworksDataCenterSwitchingManagementPackforvROps—VMwarevRealize

Operations (vROps) is a component of VMware's vRealize suite of products. vROps

provides an integrated, single-pane of glass view into the performance, capacity, and

configuration management capabilities of VMware vSphere and physical cloud

environments. Juniper Networks Management Pack for vROps is a plugin from Juniper

Networks that you can install and integrate with vROps. Once installed, the

managementpackobtainsall thenecessarymonitoringandcapacitydata fromNetwork

Director and displays the data in vROps.

• Network Traffic Analysis—Network Traffic Analysis is a monitoring technology for

high-speed switched or routed networks. Once enabled, Network Director randomly

samples network packets and sends the samples to a data learning engine (DLE) for

analysis. DLE uses this sampling information to create a picture of the network traffic,

which includes the applications that contribute to the traffic, traffic statistics, and the

top applications, and displays these details in the Device & Port Utilization Dashboard

widget in Network Director.

NOTE:• Network Traffic Analysis is supported only on QFX5100 and EX4600switches.

• This featuresupportsonlyTCPandUDPtraffic for this releaseofNetworkDirector.

• Ensure that the DLE is running Release 14.1X53-D30 for the networktraffic analysis feature to work as expected.

• Auto-Synchronization of Device Configurations—Network Director automatically

resynchronizes its configuration record to match the device configuration and set the

device configuration state to In Sync when the synchronization completes. Network

Director performs auto-synchronization when it is operating in the network as System



Of Record (NSOR)mode. Auto-synchronization occurs if out-of-band changes of the

device does not conflict with Network Director, Network Director automatically

resynchronizes thenetwork changesand retains the local changes inNetworkDirectory.

• EnhancementstoPortProfile—Portprofileworkflow isenhanced to include the following

new options:

• Quick Setup and CustomSetup—Port profile workflow now has two options—Quick

Setup and Custom Setup. Quick setup option enables you to create initial

configuration settings for a Port profile including selecting or create in line VLAN

profile. Custom setup option enables you to configure all the advanced settings and

create any inline subprofiles. By using theCustomSetupoption, apart fromselecting

the existing VLAN, CoS, and Authentication subprofiles, and you can create these

subprofiles. You can assign profiles that you create using both these options from

the Assignment page.

• New port scheduling type—A new port scheduling type, Non-hierarchical (Fusion),

is added in theCoSSettings tab inCustomSetup,which is availablewhen you create

Port profiles. This scheduling type is available for Port profiles that you create for

QFX10002 devices.

• Enhancements to Cos Profile—A new port scheduling type, Non-hierarchical (Fusion),

is added to the Create Data Center ELS CoS Profile page. This scheduling type is

available for CoS profiles that you create for QFX10002 devices.

• Enhancements toMonitoring Routing Instances—Network Director enables you to

monitor routing instances on MX Series routers. This functionality is further enhanced

to enable you to view the routing table entries and the MAC table entries for a given

routing instance.

• Enhancements totheDatacenterView—DatacenterView is enhancedwith the following

features:

• A new task, Manage IP connectivity, is included in the Datacenter View of Network

Director. This task enables you to configure the L3 routing protocol BGP for a data

center.

• You can now create a data center in Network Director that uses VMware NSX-V as

the cloud infrastructure provider. VMware NSX-V enables you to leverage the full

potential of a Software-Defined Data Center (SDDC) bymaking it easier to create

and run a logical network on top of a physical network.

• Enhancements to RBAC—Role-based access control (RBAC) is enhanced to grant or

restrict user access to individual tasks and dashboard widgets in Network Director.

Earlier this feature was limited to the various modes in Network Director.

The following new user roles are added:

• Network Director-ImageAdmin—Grants access to all the imagemanagement tasks.

• NetworkDirector-ConfigAdmin—Grants access to create, edit, delete, assign, deploy

profiles, andmanage fabrics (VCFs, QFabric systems, and Layer 3 Fabric systems).

• Network Director-Cloud Admin—Grants access to create data centers and perform

other data center related tasks



Name of the following user roles have changed:

• Network Director Monitor is changed to Monitor Admin

• Network Director Approver is changed to Config Approver

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

• IPv6 Support

• Network Director can now be deployed in an IPv6 dual-stack environment.

• Network Director now supports discovery andmanagement of devices with IPv6

addresses.

For information about these features, see the product documentation that is available

from the Network Director user interface or see the Junos Space Network Director

Documentation page.

Junos Space Network Management Platform Requirements

Network Director Release 2.5 is supported on the Junos Space Network Management

Platform Release 15.1R1.

Network Director is supported on a Junos Space JA2500 Appliance or a Junos Space

Virtual Appliance that meets the hardware requirements specified in the Junos Space

documentation. The Junos Space Appliance that suits your requirement depends on the

number of devices you plan to manage by using Network Director. Contact Juniper

Networks support to knowmore about the Junos SpaceAppliancemodel that is suitable

for your network. Network Director is not supported on a Junos Space instance running

on a Juniper Networks NSM3000 appliance.

Supported Platforms for Network Director Release 2.5

Table 1 on page 5 lists the supported platforms for Network Director Release 2.5 and

thecorrespondingqualified JunosOS releases,MobilitySystemSoftware (MSS) releases,

or other third party releases.

Table 1: Supported Platforms and the Software Versions for Network Director

Qualified Junos OS, MSS, or ESXi ReleasesSupported Platforms

QFX Series Switches and Datacenter Fabrics

Junos OS Release 15.1X53-D10QFX10002-36QQFX10002-72Q



http://www.juniper.net/techpubs/en_US/release-independent/junos-space-apps/network-director/information-products/pathway-pages/index.html


Table 1: Supported Platforms and the Software Versions for Network Director (continued)


JUNOS OS Releases 14.1X53-D15 and 14.1X53-D27QFX5100 switches with the following product SKUs:

QFX5100-48S-3AFIQFX5100-24Q-3AFIQFX5100-24Q-3AFOQFX5100-24Q-D-3AFIQFX5100-24Q-D-3AFO

Junos OS Release 15.1X53-D10 for QFX10002Junos OS Release 14.1X53-D27 for QFX5100Junos OS Release 14.1X53-D27 for EX4300

QFX10002 as Layer 3 Fabric spine deviceQFX5100 as Layer 3 Fabric spine or leaf deviceEX4300 as Layer 3 Fabric spine or leaf device

Junos OS Releases 14.1X53-D16 and 14.1X53-D27QFX5100 switches with the following product SKUs:

QFX5100-48T-AFIQFX5100-48T-AFOQFX5100-48T-DC-AFIQFX5100-48T-DC-AFO

Junos OS Releases 12.3X50-D35 and 12.3X50-D40QFX3500 (non-ELS)QFX3600 (non-ELS)

Junos OS Releases 14.1X53-D15 through 14.1X53-D27QFX3500with ELS (standalone and Virtual Chassis)QFX3600with ELS (standalone and Virtual Chassis)QFX5100-48S with ELS (standalone and Virtual Chassis)QFX5100-24Qwith ELS (standalone and Virtual Chassis)QFX5100-96S with ELS (standalone and Virtual Chassis)

JunosOSReleases 14.1X53-D15, 14.1X53-D27, and 13.2X51-D20Virtual Chassis Fabric

Junos OS Releases 14.1X53-D15 and 13.2X52-D20QFabric systems (QFX3000-G and QFX3000-M)

EX Series Switches

JunosOSReleases 11.4, 12.1, 12.2, 12.3, 13.2X50-D10, 13.2X50-D15,13.2X51-D15, 13.2X51-D20, 13.2X51-D30, 14.1X53-D15,14.1X53-D25, and 15.1R1

EX2200 and EX2200-C (standalone and Virtual Chassis) andEX3200EX3300 (standalone and Virtual Chassis)EX4200 (standalone and Virtual Chassis)EX4500 (standalone and Virtual Chassis)EX4550 (standalone and Virtual Chassis)Mixed EX4200, EX4500, and EX4550 Virtual ChassisEX6200EX8200 (standalone and Virtual Chassis)

EX Series Switches with ELS

JUNOS OS Releases 13.2X51-D25 and 14.1X53-D27EX4600

JunosOSReleases 13.2X51-D15, 13.2X51-D20, 13.2X51-D30,and14.1X53-D27

EX4300 (standalone)





JunosOSReleases 13.2X51-D15, 13.2X51-D20, 13.2X51-D30,and14.1X53-D27

NOTE: Themaster switch in EX4300 Virtual Chassis must berunning JunosOSRelease 13.2X51-D20 or later for auto VirtualChassis Resync towork. If this is not the case, the role changesand the addition or deletion of members will not reflect inNetwork Director.

EX4300 Virtual Chassis

Junos OS Releases 13.2R1, 13.2R2, 13.3R2, 14.1R4, 14.2R2, and15.1R1

EX9200 (standalone and Virtual Chassis)

MXSeries Routers

Junos OS Releases 13.2R2.4, 14.1R4, 14.2R2, and 15.1R1MX 240, 480, 960 (ELS)

Junos OS Release 14.1R4 and 15.1R1MX 80, 104, 240, 480, 960, 2010, and 2020 (non-ELS)

Cloud Infrastructure Providers

vCenter versions 5.0, 5.1, 5.5, and 6.0VMware ESXi versions 5.0, 5.1, 5.5, and 6.0

VMware vCenter ServerVMware Host

Supported Releases—Icehouse and Juno

Ensure that the APIs listed in Table 2 on page 8 are running.

OpenStack

Version 6.1NSX-V

Version 4.1NSX-MH

Juniper Networks Management Pack

Versions 6.0VMware vRealize Operations (vROps)

WLCSeriesWireless LAN Controllers

MSS Releases 7.7, 8.0, 9.0, and 9.1WLC8WLC800WLC880WLC2800WLC200

MSS Releases 7.7 and 8.0WLC2

MSS Releases 9.0 and 9.1JunosVWireless LAN ControllerWLC100

WLASeriesWireless LAN Access Points





MSS Releases 7.7, 8.0, 9.0, and 9.1WLA321WLA322WLA422WLA432WLA522WLA532WLA620WLA622WLA632

Aruba Devices Running Aruba Airwave

Version 8.0.7Aruba Airwave

Table 2: API Requirements for OpenStack

OpenStack + NSX Based data centerOpenStack Based Data centerName of the API

YesYesKeystone API v2

YesYesNova API v2

YesNoNeutron API v2

Yes, if you want to run the VM stats monitoringfeature

Yes, if you want to run the VM statsmonitoring feature

Ceilometer API v2

NOTE: Network Director does not support OpenStack with Neutron-basedVXLANs.

Junos Space DMI Schema Requirements for Network Director

Inmost installations, JunosSpaceautomaticallymatchesDMI schemas todevice families.

But there might be certain situations where your network uses a device for which Junos

Space does not have the latest or supported schema available. In such instances, you

must obtain and upload the requisite schema and set it as the default DMI schema for

each device family. Set a default DMI schema for each device family to enable Junos

Space to apply the appropriate schema to a device family.

If you cannot find the schema equivalent, use the latest schema from themain release

or contact the Juniper Support. For example, for an EX4500 switch running Junos OS

Release 13.2X51-D20, youmustuse the JUNOS13.2X51-D20schema. If this isnotavailable,

you can use the latest schema available from the JUNOS 13.2X51 releases. Use

Table 3 on page 9 as a guideline for the fallback schema that you can obtain and upload

in Junos Space before you start working on Network Director Release 2.5.



If youdonot findanappropriate schema for your devicemodel listed inTable 3onpage9,

contact Juniper Support.

Table 3: DMI Schemas

Device FamilyName of the DMI SchemaDevice

junos-qfxJUNOS 15.1X53-D10QFX10002

junosJUNOS 14.1X53-D26EX4300

junosJUNOS 15.1R1EX9200

junos-qfxJUNOS 14.1X53-D26EX4600

junos-exJUNOS 13.2X51-D30EX2200 and EX2200-C(standaloneandVirtualChassis)andEX3200EX3300(standaloneandVirtualChassis)EX4200(standaloneandVirtualChassis)EX4500(standaloneandVirtualChassis)EX4550(standaloneandVirtualChassis)Mixed EX4200, EX4500, andEX4550 Virtual ChassisEX6200EX8200(standaloneandVirtualChassis)

junos-qfJUNOS 14.1X53-D15QFabric devices

junos-qfxJUNOS 12.3X50-D35QFX3500 (non-ELS)QFX3600 (non-ELS)

junos-qfxJUNOS 14.1X53-D26QFX3500with ELS (standaloneand Virtual Chassis)QFX3600withELS(standaloneand Virtual Chassis)

junos-qfxJUNOS 14.1X53-D26QFX5100-48S with ELS(standaloneandVirtualChassis)QFX5100-24Qwith ELS(standaloneandVirtualChassis)QFX5100-96S with ELS(standaloneandVirtualChassis)



Table 3: DMI Schemas (continued)

Device FamilyName of the DMI SchemaDevice

junos-qfxJUNOS 14.1X53-D26QFX5100 switches with thefollowing product SKUs:

QFX5100-48S-3AFIQFX5100-24Q-3AFIQFX5100-24Q-3AFOQFX5100-24Q-D-3AFIQFX5100-24Q-D-3AFO

junos-qfxJUNOS 14.1X53-D26QFX5100 switches with thefollowing product SKUs:

QFX5100-48T-AFIQFX5100-48T-AFOQFX5100-48T-DC-AFIQFX5100-48T-DC-AFO

junosJUNOS 15.1R1MX Series Routers

MX80MX104MX240MX480MX960MX2010MX2020 Series routers

Fordetailedsteps foracquiringanduploading theschemafiles, seeManagingDMISchemas

Overview.

Installation Instructions for Network Director Release 2.5

Before you begin to install Network Director Release 2.5, ensure that the Network

Management Platform is at the required release with the latest patch release installed.

See Junos Space Network Management Platform Requirements on page 5 forrequirements information.

NOTE: If you have installed Network Director Release 2.5 Beta on the sameJunos Space appliance, then youmust uninstall it and restart JBOSS beforeinstalling Network Director Release 2.5.

A prescribed order is always required for installing or upgrading Network Director. Follow

the steps given in Table 4 on page 11 to determine the prescribed order of tasks for your

installation or upgrade.



http://www.juniper.net/techpubs/en_US/junos-space13.1/platform/topics/concept/junos-space-network-application-platform-schema-management-overview.html

http://www.juniper.net/techpubs/en_US/junos-space13.1/platform/topics/concept/junos-space-network-application-platform-schema-management-overview.html

Table 4: Network Director—Installation and Upgrade Steps

Order of Installation RequiredType of Upgrade or Installation

1. Install or upgrade toa supported releaseofNetworkManagementPlatform.See Junos Space Network Management Platform Requirements on page 5for requirements information.

2. Install Network Director Release 2.5 from the Junos Space user interface.

Once the installation is successful, the system lists Network Director in thelist of installed applications in Junos Space.

New installation—Network Director

1. Upgrade to a supported release of Network Management Platform. SeeJunos Space Network Management Platform Requirements on page 5 forrequirements information.

2. Ensure that you have Network Director Release 1.6R1, 1.6R2, or 2.0 running.You can perform an upgrade to Release 2.5 only from one of these releases.

NOTE: If the current release of Network Director is Release 1.0, 1.1, or 1.5,upgrade to Network Director Release 1.6R1 or 1.6R2. For detailed steps, seeNetwork Director Release 1.6R1 Quick Start Guide.

3. Upgrade to Network Director Release 2.5. For detailed steps, seeNetworkDirector Release 2.5 Quick Start Guide.

4. Restart the JBoss server from the Junos Space console.

Upgrade from earlier releases of NetworkDirector—Network Director Release 2.5

For detailed instructions about installing and upgrading Network Director, see Network

Director Release 2.5 Quick Start Guide.

Operational Notes on General Interface Use

• Theminimum supported screen resolution for Network Director is 1280 x 1024. If your

screen resolution is less than the supported resolution, the Network Director UI might

not be displayed properly. For example, icons might not be displayed on the Network

Director banner, pagesmight appear truncated, or scroll barsmight not work correctly.

• The supportedWeb browsers are Google Chrome version 17 and later, Mozilla Firefox

version 14.0 and later, and Microsoft Internet Explorer versions 9.0, 10.0, and 11.0..

• After you upgrade to the latest release of Network Director, youmust restart the JBoss

server from the Junos Space console.

• Network Director does not support cold migration of virtual machines. Cold migration

is the migration of a virtual machine that is powered-off.

• You can log in directly to Network Director without logging in to the Network

Management Platform first. To do so, use the URL:

https://junos-space-host/networkdirector

For example: https://10.20.30.40/networkdirector

The default username and password are super and juniper123.

• If you have been logged in to Network Director for a long period of time, the connection

to the server might time out. Monitoring screens might go blank or youmight not be

able to access tasks. To resolve this, log out of Network Director and then log in again.



http://www.juniper.net/techpubs/en_US/network-director1.6/information-products/topic-collections/network-director-quick-start-guide.pdf

http://www.juniper.net/techpubs/en_US/junos-space-apps/network-director2.5/information-products/topic-collections/network-director-quick-start-guide/index.html




• If you receive Java exception error message when you perform an operation, retry the

operation. The error condition is usually temporary and harmless.

• In large-scale environments, it might take some time for the network tree in the View

pane to reflect changes such as newly discovered devices or newly created locations.

• Deployment of configurations to QFX5100 switches fromNetwork Director is possible

only after you run the following commands by using the CLI of the QFX5100 switch:

[edit]user@switch# setsystemextensionsproviders juniper license-type juniperdeployment-scopecommercialuser@switch# set system extensions providers chef license-type juniper deployment-scopecommercial

Operational Notes on Device Discovery andManagement

• The administrator username that you specify for discovering the OpenStack server

must have admin privileges andmust belong to an admin tenant in the OpenStack

server.

• In a data center network, changes that youmake to a vCenter network are dynamically

updated in Network Director. However, changes that are made on an OpenStack

network require you to wait for the periodic synchronization job to run or youmust

performamanual resynchronization for thechanges tobeupdated inNetworkDirector.

• While discovering a CPE switch for a QFabric system, we recommend that you use the

root user credentials.

• Youmust run the following command on all the switches that are connected to a

vCenter server for LLDP discovery to work.

user@switch#set protocols lldp port-id-subtype interface-name

• ForNetworkDirector tobeable todiscover andmanagedevices, the followingprotocol

ports must be open between the Junos Space Network Management Platform server

and the devices:

• Port 22 for SSH connections. If you have changed the SSH port to a port other than

port 22 on your Network Management Platform, youmust change the SSH ports on

your managed devices to the port that the Network Management Platform uses.

• Port443 for virtualizationandRingMaster import support.Useport 443 for outbound

traffic to vCenter servers.

NOTE: If your RingMaster server uses any port other than port 443, thenyoumust open that port from the Junos Space Network ManagementPlatform server.

• Port 10162 for SNMP traps. Network Director receives traps frommanaged devices

on this port. (After you install Network Director, use Network Director to configure

SNMP on your devices to send traps to Network Director on this port.)

• Port 8889 for the management of wireless LAN controllers.



• Port 21 (TCP)andport69 (UDP) for uploading the software imageandconfiguration

file to the FTP server.

• Port 8282 for connecting to the DLE.

• Ports8774,9696,9292,8777, 35357,and8776 foraccessingOpenStackandVMware

NSX APIs.

You can verify that the ports are open to the devices by logging in to the Network

Management Platform CLI and executing the nmap command. For example, to verify

that port 8889 is open to a controller, enter:

root@space# nmap <controller-ip-address> -p 8889

Third-Party Integration

• JuniperNetworksDataCenterSwitchingManagementPackforvROps—VMwarevRealize

Operations (vROps) is a component of VMware's vRealize suite of products. vROps

provides an integrated, single-pane of glass view into the performance, capacity, and

configuration management capabilities of VMware vSphere, physical and cloud

environments.

Juniper Networks Data Center SwitchingManagement Pack for vROps is a plugin from

Juniper Networks that you can install and integrate with vROps. Once installed, the

management pack obtains all the necessary monitoring data from Juniper Networks

devices and displays the data in vROps.

• Juniper Networks plugin for VMware vCenter—You can discover andmanage VMware

vCenter servers by using Network Director. Network Director enables you to visualize

and perform certain management tasks on the vCenter severs. If you primarily use the

VMware vSphere to manage your virtual network and want to view details about the

Juniper Networks devices that are connected to your virtual network, you can do so by

installing the JuniperNetworksplugin forVMwarevCenter.After you install andconfigure

this plugin on the vCenter server, you can start viewing data about the connected

Juniper Networks devices by using the following widgets:

• Physical Networking widget—To open this widget, select a Host in the vSphere user

interface and select Summary. This widget displays the virtual NIC that the host

connects to, the physical switch and the port number that the virtual switch uses to

connect to the physical network, and the VLAN that is configured on the physical

switch port.

• vMotionHistorywidget—Toopen thiswidget, select a virtualmachine in the vSphere

user interface and select Summary. This widget displays the vMotion history of the

selected virtual machine along with details of the Juniper Networks switches that

were involved in the vMotion.

You can download the Juniper Networks Data Center Switching Management Pack for

vROps and the Juniper Networks plugin for VMware vCenter from theSoftwareDownload

page. See the Juniper Networks Data Center Switching Management Pack for vROps

documentationandREADMEfile that is included in the JuniperNetworksplugin forVMware

vCenter zip file for detailed steps on installing the plugin.



https://www.juniper.net/support/downloads/?p=spacenetdir#sw

http://www.juniper.net/techpubs/en_US/junos-space-apps/network-director2.5/information-products/topic-collections/juniper-management-pack-vrops.pdf

http://www.juniper.net/techpubs/en_US/junos-space-apps/network-director2.5/information-products/topic-collections/juniper-management-pack-vrops.pdf

Known Limitations

This section lists the known limitations in Network Director:

• Uploadingacustomconfig fileaspartof theSetupZTPtaskmightnotworkasNetwork

Director fails to upload the file to the FTP or the TFTP server.

As a workaround, youmust do the following before proceeding with ZTP:

1. Manually replace the file that Network Director uploads to the FTP or the TFTP

server with the custom configuration file.

2. In the DHCP server, modify the option NEW_OP.config-file-name in the dhcpd.conf

file and restart the DHCP server.

• JuniperNetworksDataCenterSwitchingManagementPack for vROpsdoesnot support

monitoring QFabric systems.

• When defining your network configuration in quick templates by using a particular

command,ensure thatyoudefinethesubcommands individually.Statingsubcommands

as a single command causes errors. For example, the commands set snmp location

bangalore and set snmp contact [email protected] are valid when defined

individually. However, if you combine these commands into the single command set

snmp location bangalore contact [email protected], schema validation treats the

last command contact as an extra entry and causes an error.

• If you have an OpenStack+NSX based data center, then for virtual machines that are

part of more than one network or VNI, the flow analysis feature is not supported.

• 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 Viewmight 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 view. All Campus Switching ELS profiles can be associated with these

switches.

Youmust use the QFX schema tomanage 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 youassign theentire logical device—theQFabric system,

Virtual Chassis, or the Virtual Chassis Fabric—to any given location.

• For Data Center switching ELS Port Profile, profile assignmentmight 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).



• WhenanEX4300switch is usedasamember switch inaQFX5100mixedmodeVirtual

Chassis orVirtualChassis Fabric,NetworkDirector doesnot consider theconfigurations

that youmake 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.

Known Issues in Network Director Release 2.5

The following are known issues in Network Director Release 2.5.

Problem DescriptionPR Number

General User Interface and Preferences Issues

If you open Network Director in multiple tabs of the same browser window, autorefresh worksonly for the latest tab.

Workaround: For autorefresh to work on all sessions, use different browsers.

978137

In the Manage IP Connectivity task, if the same interface and logical unit combination of a devicehas more than one BGP neighbor relationship with different devices and different policies areapplied to neighbors, then only one policy gets deployed.

For example, consider that a device D1 has the following BGP neighbor relationships(interface.logical unit combination) with neighbor devices D2 and D3:D1(lo0.0) --> D2(lo0.0)D1(lo0.0) --> D3(lo0.0)If you enter a policy, say P1, for D1 in the relationship between D1 and D2 and enter another policyP2 for D1 for the relationship between D1 and D3, then only one of the two policies, P1 or P2, isdeployed on D1.

Workaround: None available at present.

1121691




Network Director promotes duplicate VLAN profiles to VLANwith VRRP profiles when youmakeout-of-band changes to a device.

Workaround: Delete the unassigned profile from Network Director.

1120850

When using Microsoft Internet Explorer 11, the View Virtual Network Connectivity page in theDatacenter Viewmight not display the Zoom In, ZoomOut, and Refresh icons.

Workaround: Scroll to the left of the screen to use the Zoom In, ZoomOut, and Refresh icons.

1098365

When you create a ZTP (zero touch provisioning) profile, you are unable to add a default routeor gateway address.

Workaround:

1. Open the dhcpd.conf file on the DHCP server.

2. Add an entry for option routers, between the subnet and option subnet-mask entries of theappropriate subnet, and specify the gateway IP address as shown in the example below:

An example code snippet:

subnet 10.222.210.0 netmask 255.255.254.0{option routers 10.222.210.1;option subnet-mask 255.255.254.0;

3. Restart the dhcpd service from the Junos Space console by issuing the following command:service dhcpd restart

1103325

Port profile deployment on interfaces configured on logical system and routing instances mightfail if port security is enabled by default in Network Director.

Workaround: Disable port security in Port profile and deploy the configuration.

1100699

After youmake out-of-band changes on authentication details that are part of a VRRP profile,refreshing the configuration does not create a new profile.

Workaround:Make the out-of-band changes as part of the VRRPprofile, deploy the VRRPprofile,and resynchronize the configuration from Network Director.

1100717

Network Director might not create the LAG if the Layer 3 Fabric - Dynamic Access LAG creation jobfails for some reason.

Workaround: Run the Refresh Topology task. This will initiate the Layer 3 Fabric - Dynamic AccessLAG creation job.

1105281

All the Manage IP Connectivity page changes that are saved, but not deployed to the devices arelost after a new device is added to the data center.

Workaround: Before adding anewdevice to thedata center, deploy all the changes that youmadein the Manage IP Connectivity page.

1109046

After you deploy a policy from Network Director, if you clear the policy options and remove thecorresponding Route Filters, only the association of the policy with BGP is deleted. The policy assuch is not deleted from the device.


1109827




Network Director might delete the L3 interface association with a VLAN if the L3 interface is notconfigured with a static IP address.


1111373

IfManageMC-LAGpeers and known clients aremapped by using the Refresh Topology task, afterdismantling the MC-LAG setup in the Manage MC-LAG page or deleting the known clients fromthe Edit MC-LAG page, the known client details might not appear in the Deploy ConfigurationChanges page in the Deploy mode.

Workaround:Alwaysmodify theMC-LAGdetails fromtheEditMC-LAGpagebefore youdismantletheMC-LAG setup in theManageMC-LAG page or delete the known client from the Edit MC-LAGpage.

1113862

Port profile assignment might not work after launching the Manage Layer 3 Fabric task.

Workaround: Clear the browser cache and reopen Network Director.

1114065

VLAN and Port profile configurations cannot be deployed from Network Director as the schemaknobs are missing in the Junos-ex 14.1X53-D25.2 and Junos-ex 15.1R1.9 schemas.

Workaround:Use thedefault schema in JunosSpaceor install the Junos-ex 13.2X51-D30.4 schemaand deploy the configuration.

1118417

If you have VRRP version 3, after you edit an already deployed Device Common Settings profileand deploy the changes, the deployment fails. This occurs because Network Director appendsthe VRRP version 3 configuration also to the changed configuration, whereas only the changedconfiguration must be deployed.

Workaround: Disable VRRP version 3 or make VRRP configuration compatible with version 3.

1118766

After you upgrade from Network Director 1.6R1 to Network Director 2.5R1, deployment of somedevices might fail with a validation error.

Workaround: Delete and rediscover the devices that fail deployment.

1118864

In the Manage IP Connectivity workflow, if you opted not to resynchronize devices that are Outof Sync, then all new Save or Deploy operations might fail with a message thatManage IPConnectivity Fails.

Workaround: Synchronize the devices once prompted

1119978

During a cluster switch over, if a backup configuration job or a device discovery job is running inNetwork Director, the switch over status might display as In progress even after the switch overis complete.


1094610

Network Director sends a blank dhcpd.conf file to Ubuntu DHCP server after a ZTP profile issuccessfully deployed.

Workaround: Remove any comments with single quotes from the dhcpd.conf configuration filebeforedeploying theZTPprofile fromNetworkDirector. In case theZTPprofile is alreadydeployed,copy the relevant sections from the backup file dhcpddebugnd.conf to the dhcpd.conf file.

1105932




Deleting configuration files in Junos Space for devices also removes the baseline for the devices.


1107121

If an image upgrade job and a cluster fail job runs simultaneously, the image upgrade job statusmight show as Success, but the imagemight not have been upgraded.

Workaround: Retry the image upgrade after cluster fail over is complete.

1109072

Device might continue to remain in the Synchronising state after some deployments.

Workaround: Initiate a manual resynchronization for the devices using the Resynchronize DeviceConfiguration task.

1111410

During ZTP, device autodiscovery might fail if the device takes some extra time to reboot afterupgrading to the new image.

Workaround: Discover the device manually if autodiscovery failed after ZTP.

1114186

After upgrading to Network Director Release 2.5 from Release 2.0, the user with privileges toapprove change requests in Network Director Release 2.0 might not be able to approve changerequests in Network Director Release 2.5.

Workaround: After upgrading to Network Director Release 2.5, assign the role Network Director -Config Approver or assign the task Approve change requests to the user.

1116314

Virtualization and Topology features might not work for devices managed through IPv6.


1097801

General Build Mode and DeployMode Issues

Brownfield fails if both the apply-groups and the interface description CLI are present under theinterface-range stanza. This type of configuration mostly seen for QFabric CPE.

Workaround: Delete the apply-groups configuration under the interface-range stanza and specifythe groups configuration directly under the interface-range stanza.

For example in the QFabric CPE configuration, do the following:

1. Delete the apply-groups configuration under the interface ranges Node_Device_Interfaces andInterconnect_Device_Interfaces:

user@device#delete interfaces interface-range Node_Device_Interfaces apply-groupsqfabric-intuser@device#delete interfaces interface-rangeInterconnect_Device_Interfacesapply-groupsqfabric-int

2. Specify theconfigurationunder thegroupsqfabric-int directlywithin the interface-range stanza:

user@device#set interfaces interface-range Node_Device_Interfacesmtu 9216user@device#set interfaces interface-range Node_Device_Interfaces unit 0 familyethernet-switching port-mode access vlanmembers qfabricuser@device#set interfaces interface-range Interconnect_Device_Interfacesmtu 9216user@device#set interfaces interface-range Interconnect_Device_Interfaces unit 0 familyethernet-switching port-mode access vlanmembers qfabric

3. Commit the changes:

user@device#commit

1125950




After a brownfield job if you refresh the topology of twoMC-LAG client devices, Network Directorrefreshes and displays the client to peer connections. However, when you edit the Client to PeersLink Settings of a known client, as part of the edit MC-LAGworkflow, Network Director mightdisplay the interface connections of the client to peer1 and peer2 even if these interfaces are notaggregated for MC-LAG configuration.

Workaround: From the Edit Client to Peers Link Setting of known client, remove the interfacesconnection of client to peer1 and peer2 using the Remove Port button and save the MC LAGconfiguration.

1119928

In the Edit Client to Peer Link Settings window, after modifying the configured Routed InterfaceAddress and themask of peer1 and Peer2, deployment might fail for both peer devices.

Workaround: In the Edit Assignment workflow for VLAN Profiles, change the IRB andmaskattributes of MC-LAG VLANs and try deploying the peer device configurations.

1119968

In the Datacenter Connectivity View, the zoom pane that appears at the bottom right might nothighlight the area that is zoomed.


1100350

If you physically connect a new Virtual Chassis leafmember before adding the leafmember fromNetwork Director, the leaf member might not bemapped to Layer 3 Fabrics as expected.

Workaround: Plug and play is not supported for Virtual Chassis leaf members. Therefore, beforeyou physically connect the Virtual Chassis members, make sure that you add the Virtual Chassisleaf members by using the Layer 3 Fabric wizard.

1098910

The Connectivity Check Report (in PDF) that you generate from the Manage Layer 3 Fabric pagemight display incorrect color coding if the devices have some unknown links.


1054869

NetworkDirectormight not autodiscover devices thatweredeletedandaddedagain intoaLayer 3Fabric.

Workaround:Discover thedevicemanually andperformanout-of-bandchangeso that thedeviceis mapped to the Layer 3 Fabric.

1058092

While editing Layer 3 Fabric profiles (Port, VLAN, and Device profiles) users are not warned byanynotification that changingLayer 3Fabricprofile configurationsmight impact theLayer 3Fabricfunctionality.

Workaround: After the profiles are modified, you can discard the changes from the Deploy task.

1058811

For Layer 3 Fabrics, if a plug-and-play leaf device is added andmapped to the Fabric, the Cablingpage in the Edit Layer 3 Fabric workflowmight not update the cabling plan for that leaf in thegraph and grid views.

Workaround:When you edit the Layer 3 Fabric, modify the description in the Fabric Requirementspage and then navigate to the Cabling page. The Cabling page updates the proper cabling planfor the plug-and-play leaf device.

1058827




Settings made in the Dashboard View before a Network Director upgrade are not retained afterthe upgrade.


1060028

In themanualmode,when out-of-band changes are resynchronized, the conflicting CRmight notbe listed for quick templates.


1046833

Cluster controllers go out of Mobility Domain > Cluster when resynchronization is performed tosynchronize the out-of-band changes.


1059895

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


1061773

When you create the first data center in Network Director, the View panemight not be updateddynamically with the data center components and devices.

Workaround: Navigate to any other View and then back to the Datacenter View.

1061337

Discovery of aQFabric device that has some system logmessages in thedefault-log-messagesfile might trigger multiple resynchronization jobs.

Workaround: Clear the system logmessages in the default-log-messages file before discovery.The CLI command for clearing default log messages is clear log default-log-messages.

1027051

NetworkDirectordoesnotperformVirtualChassis resynchronization for standalonedeviceswhenthe device status changes from DOWN to UP or when Network Director restarts.

Workaround: Delete and rediscover the devices from Network Director.

1001626

Network Director might not display:

• Unprovisionedmembers added to a Virtual Chassis or a Virtual Chassis Fabric.

• TheNotPresent status formembers removed fromaVirtual Chassis or aVirtual Chassis Fabric.


973541

In Topology View, Network Director does not display LAG details between QFabric and otherdevices.


967224

Alarms generated on individual QFabric nodes do not display in Topology View.

Workaround: View alarms at the QFabric level.

960716




If devicediscovery fails,NetworkDirectordoesnotdisplay theLLDPdata related tovirtual networks.

Workaround: LLDP data is resynchronized periodically—every 1 hour. The LLDP data that wasmissed during a device discovery failure situation is refreshed and updated in Network Directoras part of the next resynchronization. Alternatively, you can initiate a manual vNetworkResynchronization from the Manage vNetwork page.

887143

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

Workaround: In the Assign to Port window, select the channelized interfaces from the Ports table.

979545

If the JunosSpace server is poweredoff or restartedwhile a virtual networkdiscovery job is running,Network Director does not discover virtual networks even after the Junos Space server restarts.

Workaround: Do the following:

a. Ensure that there are no virtual network discovery jobs running.

b. Log in to the Junos Space console as an Admin user and run shell.

c. Type the following command at the shell prompt:mysql –p build_db

d. Enter the database password when prompted. (Default is netscreen).

e. In the SQL prompt that appears, type the following command and press Enter:Select * fromVCNETWORKwhere ipaddress=ipaddressReplace ipaddresswith the IP address of the virtual network that was not discoveredsuccessfully.

Note the virtual network ID that is displayed after you execute this command.

f. Type the following command with id replaced with the virtual network ID noted from Step eand press Enter:delete fromVCNETWORKEVENTLISTENERwhere vNetwork_id=id

g. Type the following command with id replaced with the virtual network ID noted from Step eand press Enter:delete fromVCNETWORKwhere id=id

1003758

For wired devices, you are unable to specify the SNMP community string from Network Director.However, the Refresh Discovery task from Topology View requires the SNMP community stringto be configured on the device to proceed with the refresh discovery task.

Workaround: Use the CLI to configure the required community string on the device before you usethe Refresh Discovery task.

1014926

If you associate a hierarchical Data Center switching or Campus switching ELS CoS Profile thathas Priority Flow Control configuration with an interface of an EX4300 switch that is part of anEX4600 Virtual Chassis, QFX Virtual Chassis, or Virtual Chassis Fabric, the deployment fails.

Workaround:Clone theCoSprofile, remove thePFCsettings fromtheclonedprofile, andassociatethe cloned profile with the EX4300 interfaces.

1017364

ND virtualization databasemight get corrupted if you have one ormore vCenter servers that havehosts in Disconnected or in Not Responding states.

Workaround: Log in to the vSphere client and remove the hosts that are in Disconnected or in NotResponding states.

1022953




Whenadevice is removed fromoneVirtual Chassis or Virtual Chassis Fabric andadded toanotherVirtual Chassis or Virtual Chassis Fabric respectively, the show virtual-chassis status outputcommand fromNetwork Director might not display the expected information for that member ineither, the Virtual Chassis or the Virtual Chassis Fabric.

Workaround: Before you discover that member from Network Director, recycle that member inthe Virtual Chassis or Virtual Chassis Fabric in which the member device information is notdisplayed.

970798

Topology View > View Device Connectivity task does not display bandwidth utilization value forbackup and linecard member ports in a Virtual Chassis.


1005113

The Validate Pending Configuration task does not validate the unsupported configurations ondata center devices.


981866

If the IP address of space nodes change after installing Network Director, the Layer 3 Fabricconfiguration might still retain the old IP address of space nodes as the SNMP trap target.

Workaround: Log in to Junos Space console and select the (Debug) run shell option. Run thefollowing commands at the shell prompt:

• python2.7/opt/configure_for_ND.py-ndvip<VIP>-nodeip<nodemanagement ip>-restport20080-traptgt <nodemanagement ip> -dbuser <DB user> -dbpass <DB password> -ndtrapport 10162

• If there is a device management interface configured, run the same command using devicemanagement ip option as follows:python2.7 /opt/configure_for_ND.py -ndvip <VIP> -nodeip <devicemanagement ip> -restport20080-traptgt<devicemanagement ip>-dbuser<DBuser> -dbpass<DBpassword>-ndtrapport10162

• If it is a cluster environment, thecommandneeds tobe runoneachnode.Theargument -traptgtmust be repeated the same number of times as the number of nodes present. Assuming thereare four nodes, run the following command on each of the four nodes:python2.7/opt/configure_for_ND.py-ndvip<VIP>-nodeip<nodemanagement ip>-restport20080-traptgt<node1management ip>-traptgt<node2management ip>-traptgt<node3managementip> -traptgt <node4management ip> -dbuser <DB user> -dbpass <DB password> -ndtrapport10162

• If it is a cluster environment and each node has a device management interface configured,the command needs to be run on each node. The argument -traptgtmust be repeated thesame number of times as the number of nodes present. Assuming there are four nodes, run thefollowing command on each of the four nodes.python2.7 /opt/configure_for_ND.py -ndvip <VIP> -nodeip <devicemanagement ip> -restport20080 -traptgt <node1 devicemanagement ip> -traptgt <node2 devicemanagement ip> -traptgt<node3 devicemanagement ip> -traptgt <node4 devicemanagement ip> -dbuser <DB user>-dbpass <DB password> -ndtrapport 10162

1062066

Issues related to Juniper Networks Data Center SwitchingManagement Pack for vROps

Juniper Top Network Fabric widget does not refresh automatically.

Workaround: Initiate a manual refresh by clicking the Refresh button.

1102111




If the forecast value goes above 100%, vROps resizes the CPU and Memory Utilization graph tofit the data. As a result the data in the graphmight not be readable.


1102120

vROps dashboard widget behavior is inconsistent.


1093116

Monitor, Fault, and Report Mode Issues

Monitor widgets such as Status, Resource Utilization, Power, and Fan details display no datawhen a few devices are deleted and re-discovered from Network Director.


1122181

Network Director might not display any data in the System Statusmonitoring widget for MX40-Tdevices.


1146558

Whenyouview real timenetwork traffic analysis data for aVirtualChassis,NetworkDirectormightdisplay a java.lang.NullPointerException error and display no data in the NTA page in Logical View.

Workaround: Mouse over the port in the Device & Port Utilization dashboard widget, and clickAnalyze Traffic on this Port in the popup window.

1120230

While in Logical View, Network Director does not display any data for network traffic analysisdetails for a Virtual Chassis device, for specified time range.

Workaround: You can view this data from the Device & Port Utilization dashboard widget.

1122811

You will not be able to disable the collector and change the polling interval while the polling is inprogress.


1112060

Whenyouclick theAlarms toolbar in theSystempage,NetworkDirectordisplays theerrormessage:The current user does not have permissions to navigate to Fault mode.

Workaround: Close the System page and click the Alarms toolbar from any other mode.

1098678

Devices that have a large number of route entries in the routing table might not be displayed inthe Show Routing Table task.


1111427

If you have aNetwork Director setupwith 1000devices and if the setup runs formore than 2 days,the session trenddata for 1 hour keeps fluctuating.Asa result of this, theCurrentSessionbyVLANsmonitor is not displayed.


1113336




TheShowRouting Instance taskmightnot load thepagecompletely for the first time in theMozillaFirefox browser.

Workaround: Close and rerun the task.

1116019

In theMonitormode, theSummaryand theEquipment tabsdisplayNodata forResourceutilizationand Port Status widgets at the node level for QFabric systems.

1118578

Network Director does not display data in any of the Monitor mode widgets for Virtual Chassismembers that are part of a Layer 3 Fabric.

Workaround: After all the Layer 3 Fabrics with Virtual Chassis members are created, restart theJBoss server from the Junos Space console. For detailed steps on restarting JBoss, seeNetworkDirector Release 2.5 Quick Start Guide.

1102412

The Client Sessions and Session Trend widgets might not show any data when a Virtual Chassismember is assigned under Location View or Custom Group View.

Workaround: Assign the Virtual Chassis logical device as a whole under Location View or CustomGroup View.

1012400

Negative latency valuesmight display in Flow Analysis if the time on the compute agent and thaton the switches are out of sync.


1048099

Running a VM to VM flow analysis might fail or show latency values as 0/0/0 if there are otherflows on the VMs being analyzed.


1062477

Bandwidth utilization value for VCP and aex interfaces are not displayed in the Topology View.


967754

The Port Statistics task in the Monitor modemight show the Link Type column as blank.


984190

When theport statistics countersonadeviceare reset eithermanually or duringan imageupgrade,the traffic widgets might show incorrect values for some time.

Workaround: Wait for 2 to 3 poll intervals. This issue resolves itself after a few poll intervals.

1009912

When a QFabric node device alias is changed, Historical Monitoring data will be lost and portentries might be duplicated.

Workaround: Delete QFabric from Network Director and rediscover the node devices.

926912

Network Director does not display alarms at the member or node level for a Virtual Chassis or aVirtual Chassis Fabric.

Workaround: Select the Virtual Chassis or the Virtual Chassis Fabric device in Logical View to viewthe alarms.

991298






Flow path analysis might fail to start for bare-metal servers or virtual machines that are kept inthe watch list over a long time.


1062541

RelatedDocumentation

Network Director•

• Junos Space

Junos Space Documentation and Release Notes

For a list of related Junos Space documentation, see http://www.juniper.net/techpubs/.

If the information in the latest release notes differs from the information in the

documentation, follow the Junos Space Release Notes.

To obtain the most current version of all Juniper Networks®technical documentation,

see the product documentation page on the Juniper Networks website at

http://www.juniper.net/techpubs/.

JuniperNetworkssupportsa technicalbookprogramtopublishbooksby JuniperNetworks

engineers and subject matter experts with book publishers around the world. These

books go beyond the technical documentation to explore the nuances of network

architecture, deployment, and administration using the Junos operating system (Junos

OS) and Juniper Networks devices. In addition, the Juniper Networks Technical Library,

published in conjunction with O'Reilly Media, explores improving network security,

reliability, and availability using Junos OS configuration techniques. All the books are for

sale at technical bookstores and book outlets around the world. The current list can be

viewed at http://www.juniper.net/books.

Documentation Feedback

We encourage you to provide feedback, comments, and suggestions so that we can

improve the documentation. You can provide feedback by using either of the following

methods:

• Online feedback rating system—On any page of the Juniper Networks TechLibrary site

athttp://www.juniper.net/techpubs/index.html, simply click the stars to rate thecontent,

and use the pop-up form to provide us with information about your experience.

Alternately, you can use the online feedback form at

http://www.juniper.net/techpubs/feedback/.

• E-mail—Sendyourcommentsto [email protected]. Includethedocument

or topic name, URL or page number, and software version (if applicable).


Junos Space Documentation and Release Notes


http://www.juniper.net/techpubs/en_US/junos-space15.1/index.html

http://www.juniper.net/techpubs/


http://www.juniper.net/books

http://www.juniper.net/techpubs/index.html

http://www.juniper.net/techpubs/feedback/

mailto:[email protected]?subject=

Requesting Technical Support

Technical product support is available through the JuniperNetworksTechnicalAssistance

Center (JTAC). If you are a customer with an active J-Care or Partner Support Service

support contract, or are covered under warranty, and need post-sales technical support,

you can access our tools and resources online or open a case with JTAC.

• JTAC policies—For a complete understanding of our JTAC procedures and policies,

review the JTAC User Guide located at

http://www.juniper.net/us/en/local/pdf/resource-guides/7100059-en.pdf.

• Product warranties—For product warranty information, visit

http://www.juniper.net/support/warranty/.

• JTAC hours of operation—The JTAC centers have resources available 24 hours a day,

7 days a week, 365 days a year.

Self-Help Online Tools and Resources

For quick and easy problem resolution, Juniper Networks has designed an online

self-service portal called the Customer Support Center (CSC) that provides youwith the

following features:

• Find CSC offerings: http://www.juniper.net/customers/support/

• Search for known bugs: http://www2.juniper.net/kb/

• Find product documentation: http://www.juniper.net/techpubs/

• Find solutions and answer questions using our Knowledge Base: http://kb.juniper.net/

• Download the latest versions of software and review release notes:

http://www.juniper.net/customers/csc/software/

• Search technical bulletins for relevant hardware and software notifications:

http://kb.juniper.net/InfoCenter/

• Join and participate in the Juniper Networks Community Forum:

http://www.juniper.net/company/communities/

• Open a case online in the CSC Case Management tool: http://www.juniper.net/cm/

Toverify serviceentitlementbyproduct serial number, useourSerialNumberEntitlement

(SNE) Tool: https://tools.juniper.net/SerialNumberEntitlementSearch/

Opening a Casewith JTAC

You can open a case with JTAC on theWeb or by telephone.

• Use the Case Management tool in the CSC at http://www.juniper.net/cm/.

• Call 1-888-314-JTAC (1-888-314-5822 toll-free in the USA, Canada, and Mexico).

For international or direct-dial options in countries without toll-free numbers, see

http://www.juniper.net/support/requesting-support.html.



http://www.juniper.net/us/en/local/pdf/resource-guides/7100059-en.pdf

http://www.juniper.net/support/warranty/

http://www.juniper.net/customers/support/

http://www2.juniper.net/kb/


http://kb.juniper.net/

http://www.juniper.net/customers/csc/software/

http://kb.juniper.net/InfoCenter/

http://www.juniper.net/company/communities/

http://www.juniper.net/cm/

https://tools.juniper.net/SerialNumberEntitlementSearch/

http://www.juniper.net/cm/

http://www.juniper.net/support/requesting-support.html

Revision History

1 Sept 2015—Revision 1, Junos Space Network Director Release 2.5

Copyright © 2016, Juniper Networks, Inc. All rights reserved.

Juniper Networks, Junos, Steel-Belted Radius, NetScreen, and ScreenOS are registered trademarks of Juniper Networks, Inc. in the UnitedStates and other countries. The Juniper Networks Logo, the Junos logo, and JunosE are trademarks of Juniper Networks, Inc. All othertrademarks, service marks, registered trademarks, or registered service marks are the property of their respective owners.

Juniper Networks assumes no responsibility for any inaccuracies in this document. Juniper Networks reserves the right to change, modify,transfer, or otherwise revise this publication without notice.


Requesting Technical Support

Date post:	19-Dec-2016
Category:	Documents
Upload:	vutu
View:	231 times
Download:	0 times

Junos Space Network Director Release Notes, Release 2.5

Documents