How to Configure and Run xCAT PortListScan for Network Discovery
xCAT (Extreme Cluster Administration Tool) scales large cluster environments by automating bare-metal provisioning and system management. A key challenge in provisioning newly added hardware is identifying its Baseboard Management Controller (BMC) or Flexible Service Processor (FSP) on the network.
The PortListScan method in xCAT solves this by scanning targeted subnet ranges, discovering open management ports (like standard IPMI, HTTPS, or SSH), and automatically mapping discovered devices into the xCAT database. This article details how to configure and execute PortListScan for seamless infrastructure discovery. 1. Prerequisites and Network Planning
Before initiating a port scan discovery session, ensure your environment meets the following requirements:
Static Management Node: Your xCAT management node must have a statically configured IP address on the provisioning/management VLAN.
Firewall Accessibility: Open firewall restrictions between the xCAT management node and target hardware subnets. The scanning engine needs outbound permissions to probe target ports.
Target Network Definition: Ensure the subnet you plan to scan is already defined in the xCAT networks database table. 2. Configuring the xCAT Environment
You must instruct xCAT on which discovery methods are allowed and how to process the found machines. Step 1: Enable Discovery in the Site Table
Open the global site configuration using tabedit or chtab to enable automatic discovery processes: chtab key=nodediscovermode value=portsync Use code with caution. Step 2: Define Pre-configured Node Attributes (Optional)
If you want xCAT to automatically map a discovered IP address or MAC to a specific hostname upon detection, define your stub nodes ahead of time. If you prefer a completely dynamic approach where xCAT records raw discovered nodes for later assignment, you can skip this step. 3. Running PortListScan Discovery
The nodediscoverstart command initializes scanning modules in the xCAT daemon. For port-list scanning, pass the network ranges and port specifications. Step 1: Start the Scanning Engine
Execute nodediscoverstart and specify the discovery method as portscan or explicit IP sweeps:
nodediscoverstart method=portscan range=192.168.100.1-192.168.100.254 ports=623,443 Use code with caution. range: Defines the IP bounds for the sweep.
ports: Probes specific ports. Port 623 checks for IPMI (RMCP) capabilities, while port 443 checks for secure web-based vendor consoles. Step 2: Monitor Discovery Status
As the scan progresses, check what hardware devices have responded and been cached by running: nodediscoverls -t portscan Use code with caution.
This command outputs the discovered IP addresses, their detected open ports, and potential hardware vendors extracted from the responses. Step 3: Stop the Scanning Engine
Once all target hardware endpoints appear in the list, close the scanning window to release management node network resources: nodediscoverstop Use code with caution. 4. Troubleshooting and Verification
If target hardware fails to appear during a PortListScan session, check these diagnostic vectors:
Hardware Discovery & Define Node — xCAT 2.17.0 documentation
Leave a Reply