Network ports used for discovery communications
Base device discovery
For efficiency, the Discovery Port uses ICMP ping to locate a device. It is possible to use other ping techniques if ICMP Echo is suppressed in your environment. To do so, scroll down to the Discovery section on the Administration tab and click Discovery Configuration. In the Scanning section, enable the Use TCP ACK 'ping' before scanning and Use TCP SYN 'ping' before scanning check boxes, and enter the port numbers in the TCP ports to use for the initial scan and UDP ports to use for the initial scan fields.
If you do not allow ICMP pings through the firewall and do not enable TCP Ack and Syn pings, you might lose performance. This is because the system performs a full "Access Method" nmap port scan to determine whether the host is actually present, which causes delays as it waits for requests to timeout. You must alter the "Ping hosts before scanning" setting to "No" in this situation. If there is a limited range if IPs for which ICMP Echo is suppressed, you can disable the ping behavior for these IPs by using the Exclude ranges from ping. For more information
**** Important
To scan networks that do not permit ICMP ping packets, you may set Use TCP ACK ping before scanning or Use TCP SYN ping before scanning (or both of these) in your discovery settings to Yes. If Discovery pings an IP address where there is no device and some firewall in your environment is configured to respond for that IP address, it may result in reporting a device that does not exist on the network rather than dark space (NoResponse). To avoid this, it is recommended to either alter such firewall configurations or not to enable TCP ACK ping or TCP SYN ping.
The discovery ports listed in the following table are used to determine what device is present.
Port number | Port assignment |
---|---|
4 | Closed Port |
21 | FTP |
22 | SSH |
23 | telnet |
80 | HTTP |
135 | Windows RPC |
161 | SNMP |
443 | HTTPS |
513 | rlogin |
902 | VMware Authentication Daemon |
3940 | Discovery for z/OS Agent |
5985 | PowerShell HTTP |
5986 | PowerShell HTTPS |
5988 | WBEM HTTP |
5989 | WBEM HTTPS |
Source | Default Port | Protocol | Directionality | Reason |
---|---|---|---|---|
Main Appliance (MA) | 389 (TCP/UDP) | LDAP | MA to targets | Active Directory Sync |
Remote Collector(s) RC | 53 (TCP) | DNS | Device to targets | DNS Zone Discovery |
Remote Collector(s) RC | 623 (UDP) | IPMI | RC to targets | IPMI-based discovery of management interfaces |
Remote Collector(s) RC | 22 (TCP) | SSH | RC to targets | SSH-based discovery of Linux and Unix systems |
Remote Collector(s) RC | 161 (UDP) | SNMP | RC to targets | SNMP discovery of network equipment |
Intelligent PDUS
Sunbirds Data Center DCIM provides Outlet-metered intelligent rack PDUs that enable monitoring and management of power consumption at each outlet, providing device-level data that offers a granular view of power usage and capacity in the data center.
Some even integrate with temperature and humidity sensors to provide environmental information at the rack.
Sunbird’s DCIM software complements outlet-metered intelligent rack PDUs by collecting, storing, alerting, and reporting on the data they generate, delivering actionable insights and enabling more informed decision-making.
In this eBook, we will explain the practical advantages of deploying intelligent rack PDUs and Sunbird DCIM. By leveraging these tools, you can maximize the value of both investments and dramatically simplify how you manage your data center.
Data Center Infrastructure Management
Why DCIM?
Power and cooling expenses alone were projected to increase from $25 billion in 2005 to $45 billion by 2010. Data center managers consistently cite rack density, cooling, and power usage as top concerns.
As responsibilities across facilities, networking, and systems have evolved, aligning these functions to reliably, securely, and cost-effectively support the business has become increasingly difficult—making DCIM tools a critical necessity.