Operational Notes on Device Discovery and Management
The administrator username that you specify for discovering the OpenStack server must have admin privileges and must belong to an admin tenant in the OpenStack server.
In a data center network, changes that you make 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 you must perform a manual resynchronization for the changes to be updated in Network Director.
While discovering a CPE switch for a QFabric system, we recommend that you use the root user credentials.
You must 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
For Network Director to be able to discover and manage devices, the following protocol 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, you must change the SSH ports on your managed devices to the port that the Network Management Platform uses.
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.
Port 8282 for connecting to the DLE.
Ports 8774, 9696, 9292, 8777, 35357, and 8776 for accessing OpenStack and VMware 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
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.
For wired devices, you might not be able to specify the SNMP community string from Network Director. However, the Refresh Discovery task from Topology View requires the SNMP community string to be configured on the device to proceed with the refresh discovery task. As a workaround, use the CLI to configure the required community string on the device before you use the Refresh Discovery task.