The OnBoard administrator configures connected devices by assigning parameters that are described in the following table. Where more information is needed, the table provides links to where the parameters are described in more detail.
Also referred to as an alias. A meaningful string that helps identify the device and possibly its location, such as rack1_dev1_ibm306_rsa for an IBM 306 in the bottom row of rack 1. The assigned name can be used to access the device by entering the name with the ssh command on the command line.See the AlterPath OnBoard User’s Guide for the syntax for using ssh with a device’s name to perform device management functions on the server or other device. Login name and password Obtained from the server’s or device’s administrator. Can be different from the user name and password pair that the user enters used to access the OnBoard. If an OnBoard administrator has configured one or more device groups, the device can be assigned to a device groups. The type of service-processor-management protocol or type of access. The following lists each of the defined service processor and device types.
• iLO
•
•
•
•
•
• See Device Type Differences” for more information about assigning the correct device type. Used by the OnBoard to communicate with devices on the private network. See Private Subnets on the OnBoard and Why Define Private Subnets? for more information about planning and implementing subnets and assigning them to devices. Private subnets can be configured in the Web Manager on the Wizard Subnets screen or on the Network Private Subnets screen as described in the following sections: An IP address used by the OnBoard to communicate with the device. See Preparing an Addressing Scheme, Address Configuration for Connected Devices, and Options for Assigning IP Addresses to Connected Devices for more information about assigning IP addresses. Virtual IP address (optional) A virtual IP address to assign to the device, which can be used hide the real IP address from certain types of authorized users. (Users who have native IP access, service processor console, or device console access cannot be prevented from discovering the IP address of the dedicated Ethernet port that is connected to the OnBoard.) Virtual addresses are available only if a virtual network has been configured using DNAT. See Why Define Virtual (DNAT) Addresses? for more information about when virtual addresses are needed and how the administrator creates them. A description that helps identify the device, such as “IBM xSeries 306 RSA II.” The authentication method to be used whenever a user accesses the device. Can be different from the authentication method used for the OnBoard, unless SSH tunneling is used to create a secure path for users who are authorized for Native IP access. When an SSH tunnel is used, the OnBoard and the device must be using the same authorization method. See OnBoard Authentication Options. See also Supported Authentication Types (Sheet 1 of 3) for a detailed list of authentication types supported for devices. Command template (where required for the selected device type) A template that contains text commands that manage communications between the user and the connected device and that perform device management actions. See Command Templates in Appendix 14, “Advanced Device Configuration,” which provides additional background information and a procedure for choosing or creating a command template to work with a device.Caution! Be careful not to allow any PPP user to use the same IP address that is assigned to any connected device under control of the OnBoard.Note: The OnBoard has been tested with the service processor and device types and firmware versions listed in the release notes. If the firmware on a service processor being managed by the OnBoard is at another level, or if the service processor is not listed in the release notes, the administrator needs to follow the instructions in Appendix 14 to configure support for the device.