Preparing Devices for Management by Network Director
To discover and manage devices, Network Director requires the following minimum device configuration as a prerequisite. Ensure that the device:
Has a static management IP address. The address can be in-band or out-of-band, but must be reachable from the Junos Space server.
Is enabled for SSH v2. On wireless LAN controllers, SSH is enabled by default. However, on EX Series switches you need to enable SSH. Issue the set system services ssh protocol-version v2 command to enable SSH v2 on EX Series switches.
Has a user ID with the superuser class configured. Junos Space and Network Director uses this user ID to authenticate the SSH connection with the device.
Is enabled for SNMP with the appropriate read-only V1, V2, and V3 credentials created. You do not need to configure SNMP trap receivers; Network Director configures traps as a deployment task.
In addition, the following protocol ports must be open for Network Director communication:
Port 22 for SSH connections. If you have changed the SSH port to a port other than port 22 on your Network Management Platform, you must change the SSH ports on your managed devices to the port that the Network Management Platform is using.
Port 443 for virtualization and RingMaster import support. Use port 443 for outbound traffic to vCenter servers.
If your RingMaster server uses any port other than port 443, then you must open that port from the Junos Space Network Management Platform server.
Port 10162 for SNMP traps. Network Director receives traps from managed 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) and port 69 (UDP) for uploading the software image and configuration file to the FTP server.
Ports 8774, 9696, 9292, 8777, 35357, and 8776 for accessing OpenStack and VMware NSX APIs.
You can verify whether a port is open by logging in to the Junos Space CLI and using the nmap command. For example, to determine whether port 8889 is open on a controller, issue this command:
root@space# nmap <IP address of controller> -p 8889