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 

Preparing Devices for Management by Connectivity Services Director

To discover and manage devices, Connectivity Services Director requires the following minimum device configuration as a prerequisite for installation on a device. 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. Issue the set system services ssh protocol-version v2 command to enable SSH v2 on M, MX, and PTX Series routers.
  • Has a user ID with the superuser class configured. Junos Space, and Connectivity Services Director use 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; Connectivity Services Director configures traps as a deployment task.

In addition, the following protocol ports must be open for Connectivity Services 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 10162 for SNMP traps. Connectivity Services Director receives traps from managed devices on this port. (After you install Connectivity Services Director, use Connectivity Services Director to configure SNMP on your devices to send traps to Connectivity Services Director on this port.)
  • Port 162 for service-level SNMP traps. Connectivity Services Director uses OpenNMS for SNMP trap collection and correlation.
  • Port 21 (TCP) and port 69 (UDP) for uploading the software image and configuration file to the FTP server.

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

Modified: 2016-07-14