The following table describes the management features for the different types of managed devices. These features are available a user through the Web Manager, through the onbdshell menu, and through the ssh utility on the command line. The first column shows the following:
• The option name for the feature in the onbdshell action menu
• The command name used with ssh on the command line to access the feature.The “Device” column shows the type of device that supports each feature (“dev” for device without a service processor and “SP” for a service processor).
Gives access to the service processor’s console (sometimes called the native command interface or NCI).
• A server that allows console access through its service processor
• A device without a service processor that presents a command line interface through its Ethernet port In the Web Manager, brings up a screen with the power management options. When access to the service processor goes through the OnBoard’s console, brings up a list of power management options. When the user performs power management directly on the service processor using the ssh command, power management options are performed using power management commands. Some types of service processors offer multiple options for powering off and power cycling a server. For details, see What the Power Commands Do on Different Servers.The following rows show the Web Manager and OnBoard shell menu options and the name of the power management commands that can be executed directly on the service processor using the ssh command from the user’s computer. Web Manager / onbdshell Option ssh Command Check power status /Get power status Resets the server where the service processor resides. Various type of resets are available on service processors. See What the Reset Command Does on Different Servers. Displays unformatted sensor data collected from the server by its service processor. The page provides a button that displays graphs of data from individual sensors. Displays the system event log (SEL) menu from the server where the service processor resides. Events are messages logged when system management events are detected. The events can be logged by the service processor or by the server. The user can view or clear event logs directly on the service processor using the ssh command. Web Manager / onbdshell Option ssh Command Used when a service processor supports access to a native web application or provides a management application that runs on the user’s computer. For “Native IP” to be available, a VPN connection must be active between the remote computer and the OnBoard. When the option to enable native IP is chosen, the user can then do one of the following:
• Launch a browser on the remote computer to bring up the native web application
• Launch the management application on the remote computerNote: Instead of using a VPN tunnel, a user may use a ssh tunnel to access a device’s native web application without going through the Web Manager or the OnBoard’s console. For more details, see Accessing a Device’s Native Management Features. Note: When a connected device does not have a service processor., “Device Console” and “Native IP” are the only management features available by default. The OnBoard command templates and device management Expect scripts can be customized to make other management features available.