The BMC Management Utility is a collection of software applications that enable remote management and configuration of systems equipped with a BMC. The BMC Management Utility includes the following components:
Command Line Interface (IPMI Shell)
The IPMI Shell is a scriptable console application program for the control and management of remote systems using the IPMI 1.5 protocol. The IPMI Shell supports both serial access and LAN access to the BMC. It allows administration of one or more managed systems from a command line shell, rather than a graphical user interface (GUI). Use the IPMI Shell to perform the following tasks:
System power management
System identification
Access to the event log
System identifier control
Serial-Over-LAN Proxy (SOL Proxy)
The SOL Proxy is a telnet daemon that allows LAN-based administration of remote systems using the Serial Over LAN (SOL) and IPMI 1.5 protocols. Any standard telnet client application, such as HyperTerminal on Microsoft® Windows® or telnet on Red Hat® Enterprise Linux, can be used to access the daemon's features. The SOL protocol coupled with the remote system's BIOS console redirection allows administrators to remotely view and change a managed system's BIOS settings over a LAN. The Red Hat Enterprise Linux serial console and Microsoft's EMS/SAC interfaces can also be accessed over a LAN using SOL.
NOTICE: All versions of the Microsoft Windows operating system include Hilgraeve's HyperTerminal
terminal emulation software. However, the included version does not provide many functions required
during console redirection. Instead, you can use any terminal emulation software that supports VT100 or
ANSI emulation mode. One example of a full VT100 or ANSI terminal emulator that supports console
redirection on your system is Hilgraeve's HyperTerminal Private Edition 6.1 or later.
NOTE: See your system User's Guide for more information about console redirection, including
hardware and software requirements and instructions for configuring host and client systems to use
console redirection.
NOTE: HyperTerminal and telnet settings must be consistent with the settings on the managed system.
For example, the baud rates and terminal modes should match.
Installing the BMC Management Utility
The BMC Management Utility is installed on a management station system in order to remotely connect to the managed system's BMC. See Figure 3-1.
Installation Prerequisites
Before using the BMC Management Utility, you must perform at least the basic BIOS and BMC configuration tasks described in "Configuring Your Managed System."
In addition, to access the BMC using the IPMI serial feature, you must have a working connection between the management station and the correct serial I/O port of the managed system's BMC using a null modem cable.
Figure 3-1. Installing on a Management Station
Supported Operating Systems
The management station must be running one of the following supported operating systems:
Red Hat Enterprise Linux AS (version 2.1)
Red Hat Enterprise Linux AS, ES, WS (version 3)
Microsoft Windows 2000
Microsoft Windows XP
Microsoft Windows Server 2003 Web, Standard, and Enterprise Editions
Also ensure that the following conditions are met:
No version of IT Assistant may be installed on your system.
SQL server is up and running.
Installation Procedures
The following installation procedures provide step-by-step instructions for installing and uninstalling the BMC Management Utility for each supported operating system:
Installing/Uninstalling on Systems Running Supported Windows Operating Systems
Installing/Uninstalling on Systems Running Supported Red Hat Linux Operating Systems
Installing on Systems Running Supported Windows Operating Systems
To install the BMC Management Utility on a management station running the Windows operating system, perform the following steps:
Log on with administrator privileges to the system where you want to install the system
management software components.
Exit any open application programs and disable any virus-scanning software.
Insert the Systems Management Consoles CD into your system's CD drive.
If the CD does not automatically start the setup program, click the Start button, click Run, and then typex:\windows\setup.exe (where x is the drive letter of your CD drive).
The Dell OpenManage Management Station Installation Version 4.3 screen appears.
Click Install, Modify, Repair or Remove Management Station.
The Welcome to Install Wizard for Dell OpenManage Management Station screen appears.
Click Next.
A software license agreement appears.
Select I accept the terms in the license agreement,if you agree.
The Setup Type screen appears.
Select Custom Setupand click Next.
The Custom Setup screen appears.
From the drop-down, which appears on the left side of BMC Console, select This feature, and
all subfeatures will be installed on the local hard drive.
To accept the default directory path, click Next. Otherwise, click Browse and navigate to the directory where you want to install your software, and then click Next.
The Ready to Install the Program screen appears.
Ensure that all information is correct and click Install.
The Installing Dell OpenManage Management Station screen appears and displays the status of the installation.
When installation is complete, the Install Wizard Completed screen appears. Click Finish.
See the Dell OpenManage™ Version 2.0 User's Guide for additional information about installing the BMC Management Utility on a management station.
By default, the installation program copies the files to the following directory: C:\Program Files\ Dell\SysMgt\bmc.
The SOL Proxy service does not auto-start after installation. To start the SOL Proxy service after installation, you can either reboot the system (SOL Proxy automatically starts on a reboot), or manually start the service by going to the bmc directory and entering the following command:
solproxy start
Uninstalling on Systems Running Supported Windows Operating Systems
To uninstall the BMC Management Utility, use the Add/Remove Programs utility in the Control Panel.
Installing on Systems Running Supported Red Hat Linux Enterprise Operating Systems
To install the BMC Management Utility on a management station running the Red Hat Linux Enterprise operating system, perform the following steps:
Log on as root to the system where you want to install the management station components.
If necessary, mount the Systems Management Consoles CD using the mount /mnt/cdrom command.
Install the BMC Management Utility with the following command: rpm -ivh /linux/bmc/osabmcutil*.rpm
By default, the installation program copies the files to the following locations:
/etc/init.d/solproxy
/etc/solproxy.cfg
/usr/sbin/solproxyd
/usr/bin/solconfig
/usr/bin/ipmish
The SOL Proxy will start automatically during system startup. Alternatively, you can go to directory /etc/init.d and use the following commands to manage the SOL Proxy service:
solproxy status
solproxy start
solproxy stop
solproxy restart
Uninstalling on Systems Running Supported Red Hat Linux Enterprise Operating Systems
To uninstall the BMC Management Utility, perform the following steps:
Log in as root.
Enter the following command to remove all the installed packages.
rpm -e osabmcutil
If the BMC Management Utility has been uninstalled, you will receive a success message.
IPMI Shell
IPMI Shell is a CLI console application and has no graphical user interface. Its commands and options are specified using command line arguments only.
IPMI Shell supports out-of-band (OOB) access (over a LAN or through the serial port) to a single system at a time, however, multiple IPMI Shell sessions can run simultaneously on the same managed system. See Figure 3-2.
IPMI Shell allows a user with user-level BMC user privileges to:
Display the current power status.
Display the 16-byte system GUID of the managed system.
Display information from the system's field replaceable unit (FRU).
Display the BMC firmware information.
Display summary information about the event log.
Display the logged events.
In addition to the operations that can be performed by a user with user-level BMC user privileges, IPMI Shell allows a user with operator-level and administrator-level BMC user privileges to:
Power on, reset, or cycle a managed system.
Simulate a hard power off on a managed system (forcing the system to turn off without shutting down the operating system).
Delete the system event log (SEL).
Turn on/off the blinking system identification LED.
To facilitate command scripting, upon successful execution, IPMI Shell terminates with an exit code of zero, and will output the execution results in a parsable format. If an error is encountered, the program exits with a non-zero error code and outputs the error in a parsable format. See "BMC Management Utility Error Codes" for a complete list of possible BMC Management Utility error codes.
Figure 3-2. IPMI Shell Diagram
Using IPMI Shell
To use IPMI Shell, perform the following steps:
On systems running a supported Microsoft Windows operating system:
Start a Command Prompt window.
Go to the directory where the file ipmish.exe is located. By default, ipmish.exe is located at
the directory: C:\Program Files\ Dell\SysMgt\bmc.
Enter IPMI Shell commands (see "IPMI Shell Command Syntax") to manage the remote
system. Go to "IPMI Shell Commands" for a complete list of valid options, commands,
subcommands, and arguments.
On systems running a supported Red Hat Enterprise Linux operating system:
Start an operating system (OS) shell.
Enter IPMI Shell commands (see "IPMI Shell Command Syntax") to manage the remote
system. Go to "IPMI Shell Commands" for a complete list of valid options, commands,
subcommands, and arguments.
IPMI Shell Command Syntax
The general syntax of IPMI Shell CLI commands is as follows:
command [subcommand] [command option and argument] ...
Both global options and command-specific options are always in the following form:
-option argument
For example:
-help
-max 20
-u John
Arguments with embedded tabs or spaces must be enclosed in matching double quotation marks ("). For example:
-user "John Smith"
Every command has one default action. The default action is typically, but not always, the equivalent of reading and displaying the current setting or status for the command.
This option is used to establish a connection to a remote managed system using the LAN channel. The IP port specified in installation (default value is 623) is used unless another port has been configured.
Options
NOTE: The following options cannot be used independently. One or more IPMISH commands must
follow the option.
-ip bmc_ip_address | bmc_hostname
Specifies the IP address or hostname of the remote managed system.
This option establishes a connection to a remote managed system using the serial channel.
Options
NOTE: The following options cannot be used independently. One or more IPMISH commands must
follow the option.
-com serial_port
Specifies the serial port used when establishing an IPMI session to the managed system. For a system running Windows, the management station port can be 1, 2, 3, and so on. For systems running Red Hat Enterprise Linux, the management station port can be ttyS0, ttyS1, ttyS2, and so on.
-baud baud_rate
Specifies the communication baud rate over the serial channel, such as 9600 or 19200. The baud rate for the serial channel should match the baud rate set in the managed system.
-flow flow_control
Specifies the data flow control method. There are two flow control options: CTS (hardware flow control) and NONE (no flow control).
-u username
Specifies the BMC username.
-p password
Specifies the BMC user password.
IPMI Help Option -help
Synopsis
ipmish -help [command]
Description
This option displays the following information:
A summary page for all commands
A summary of all subcommands for a single command
A detailed description of a command-subcommand combination
Options
-help command
A command list and a capsule description of options are printed if no argument is given. When there is an argument specifying a valid command, the help option displays a detailed description of the command. See Figure 3-3 and Figure 3-4.
Figure 3-3. IPMI Help Option Example 1
Figure 3-4. IPMI Help Option Example 2
IPMI Shell Commands
Table 3-1 lists IPMI Shell commands with a brief description.
Table 3-1. IPMI Shell Commands
Command
Description
identify
Controls the identification LED on the front panel.
sysinfo
Retrieves and displays managed system information.
power
Controls the power state of the managed system.
sel
Displays or deletes information from the SEL.
identify
Synopsis
identify [on [-tseconds] | off]
Description
This command controls the identification LED on the front panel. See Figure 3-5.
Subcommands
on
off
Turns the managed system's front panel LED on or off. If the BMC supports the IPMI extension Chassis Identify On command, then the identify on command turns the LED on indefinitely until the identify off command is used to turn the LED off.
Options
-t seconds
Specifies how long the LED is on. It should be no longer than 255 seconds.
Default Subcommand
If a subcommand is not specified, this command acts the same as the identify on command.
Figure 3-5. identify Option Example
sysinfo
Synopsis
sysinfo [fru | id]
Description
This command retrieves and displays the system information, including field replaceable unit (FRU) and BMC information for the managed system. See Figure 3-6.
Subcommands
fru — Returns FRU related information
id — Returns BMC related information
Default Subcommand
If a subcommand is not specified, this command acts the same as sysinfo id. See Figure 3-6.
Figure 3-6. sysinfo Option Example
power
Synopsis
power status
power off [-force] | on | cycle | reset
Description
This command displays the current power status of the managed system, turns the system on or off, or resets the system. See Figure 3-7.
Subcommands
status — Displays the current power status of the system, the returned value is "on" or "off".
on — Turns on the managed system.
off — Issues a "graceful shutdown" IPMI command.
NOTE: The off subcommand does not function while the operating system is booting on the managed
system or if the operating system is locked up. Additionally, this suboption does not function if you are not
currently logged in the managed system.
cycle — Turns off the system, pauses, then turns the system back on.
reset — Pulses the system reset signal, regardless of the power state.
Options
-force
This option simulates pressing the power button, forcing the system to turn off without shutting down the operating system.
Default Subcommand
If a subcommand is not specified, this command acts the same as power status. See Figure 3-7.
Figure 3-7. power Option Example
sel
Synopsis
sel status
sel get [ [-begin index1 ] [-end index2 | -max count] ] | [-last n]
sel clear
Description
This command displays event log information, displays the contents of the event log, and deletes all the event log records. See Figure 3-8.
Subcommands
status — Displays the total number of system event log records.
get — Prints all or part of the event log.
clear — Deletes all the records in the event log.
Options
-begin index1
Specifies the first record to display.
-end index2
Specifies the last record to display.
-max count
Specifies the maximum number of records to display.
If the value of the argument count is bigger than the total number of the records, the last record displayed will be the last one in the event log.
-last n
Specifies the number of records to be displayed, starting from the last record and counting backwards.
Default Subcommand
If a subcommand is not specified, this command acts the same as sel status.
Display Format
System event log records are displayed using a tabular format. The column headers are: Ordinal Number, Date, Time, Sensor Number, Sensor Type, and Brief Description. See Figure 3-8.
Figure 3-8. sel Option Example
SOL Proxy
SOL Proxy is a simple telnet server. It allows a telnet client to interact with the hardware-designated serial port of a remote managed system using the LAN communication channel. See Figure 3-9. With SOL Proxy, administrators can view and change the BIOS settings over a shared LAN. In addition, you can also access your managed system's BMC using SOL Proxy using the Red Hat Enterprise Linux serial console and Microsoft's EMS/SAC interfaces. SOL Proxy does not support in-band or serial connection to the managed system's BMC.
When BIOS console redirection to serial port is enabled on the remote managed system, any application that uses the BIOS to read from or write to the system console will have its I/O redirected to the designated serial I/O port. When SOL is activated, the BMC firmware reads any data written to the serial port and transmits it to the SOL Proxy as LAN packets. SOL Proxy then forwards the data to the telnet client as TCP/IP packets.
Conversely, any keyboard activity at the telnet client is sent to the BMC by SOL Proxy. BMC then writes the packets to the system serial I/O port.
NOTE: See your system User's Guide for more information about console redirection, including
hardware and software requirements and instructions for configuring host and client systems to use
console redirection.
Figure 3-9. SOL Proxy Diagram
The SOL Proxy communication scheme enables you to view and configure the BIOS settings of a managed system, as well as to reset the managed system remotely using a telnet client. SOL Proxy is installed as a daemon service and automatically starts each time the system boots. SOL Proxy can accommodate only one telnet session at a time.
You can use a variety of telnet clients to access SOL Proxy features. For example:
In a Windows environment, you can use a Command Prompt window as your console. However, function keys such as <F1> and <F2> will not operate correctly with this client except on systems running Windows Server 2003.
In a Windows environment, you can also use any telnet application that supports VT100 or ANSI emulation mode (such as HyperTerminal) as your console. HyperTerminal key mappings are based on the supported terminal emulation modes and do not support some useful terminal types. For example, HyperTerminal does not support the "Linux" terminal mode (a modified VT100 terminal). If you use HyperTerminal to connect to a Red Hat Enterprise Linux console (redirected by SOL) the function and arrow keys may not work, based on the "tty" settings of the remote application.
NOTICE: All versions of the Microsoft Windows operating system include Hilgraeve's HyperTerminal
terminal emulation software. However, the included version does not provide many functions required
during console redirection. Instead, you can use any terminal emulation software that supports VT100 or
ANSI emulation mode. One example of a full VT100 or ANSI terminal emulator that supports console
redirection on your system is Hilgraeve's HyperTerminal Private Edition 6.1 or later.
NOTE: When using HyperTerminal, you must deselect the Wrap lines that exceed terminal width
check box to avoid console redirected data that may appear to be corrupted or garbled. To deselect
this feature, click File→ Properties→ Settings→ ASCII Setup...→ Wrap lines that exceed terminal
width.
NOTE: See your system User's Guide for more information about console redirection, including
hardware and software requirements and instructions for configuring host and client systems to
use console redirection.
In a Red Hat Enterprise Linux environment, you can use a shell such as csh or ksh as your console, or you can use any telnet application supporting VT100 or ANSI emulation mode.
NOTE: HyperTerminal and telnet settings must be consistent with the settings on the managed system.
For example, the baud rates and terminal modes should match.
You can also send the terminal break function while in console redirection. The use of this functionality requires that the specific terminal program in use has the ability to send the break function. For example, Red Hat Enterprise Linux telnet modules have the capability of sending the break signal by typing:
Ctrl+]send brk<Enter>
The Red Hat Enterprise Linux SysRq function is one example of an advanced debugging feature that is enabled by use of the break function. Refer to the Red Hat Enterprise Linux documentation to see how to use this feature.
Using SOL Proxy
Depending on the console you use, there are different steps for accessing SOL Proxy. Throughout this section, the management station where the SOL Proxy is running is referred to as the SOL Proxy Server.
Using the Windows Command Prompt
To connect and use SOL Proxy:
Open a Command Prompt window on your management station.
Enter the telnet command in the command-line and provide the IP address of the SOL Proxy
server and the port number that you specified in the SOL Proxy installation (the default value
is 623). Such as:
If you are prompted for a username, provide the operating system login credentials of the
SOL Proxy Server.
Provide a password when prompted. SOL Proxy will use this combination of operating system
username and password to authenticate you on SOL Proxy Server. The specific authentication
scheme will depend on the operating system configuration for the SOL Proxy Server.
However, if localhost or an IP address of 127.0.0.1 is used, it is assumed that the user has login
privileges to the current host, and is not prompted for a username and password.
After authentication is performed, you will see a login successful message and the SOL Proxy
main menu prompt. You are ready to use SOL Proxy. See "SOL Proxy Main Menu" for further
instructions.
Using Windows HyperTerminal Console
To connect and use SOL Proxy:
Open a HyperTerminal session on your management station.
Create a new TCP/IP connection, providing the IP address of SOL Proxy Server and the port
number you specified in SOL Proxy installation (the default value is 623). The Emulation
mode is VT100 and ANSI.
Click the Connect button in the toolbar to try the newly defined connection.
If you are prompted for a username, provide the operating system login credentials for SOL
Proxy Server.
Provide a password when prompted. SOL Proxy uses this combination of operating system
username and password to authenticate you on SOL Proxy Server. The specific authentication
scheme depends on the operating system configuration for the SOL Proxy Server. However, if
localhost or an IP address of 127.0.0.1 is used, it is assumed that the user has login privileges
to the current host, and is not prompted for a username and password.
After authentication is performed, you will see a login successful message and the SOL Proxy
main menu prompt. You are ready to use SOL Proxy. See "SOL Proxy Main Menu" for further
instructions.
Using a Red Hat Enterprise Linux Shell
To connect and use SOL Proxy:
Open a Red Hat Enterprise Linux shell on your management station.
Enter the telnet command and provide the IP address of the SOL Proxy Server and the port
number you specified in SOL Proxy installation. For example:
If you are prompted for a username, provide the operating system login credentials of SOL
Proxy Server.
Provide a password when prompted. SOL Proxy will use this combination of operating system
username and password to authenticate you on SOL Proxy Server. The specific authentication
scheme will depend on the operating system configuration for the SOL Proxy Server.
However, if localhost or an IP address of 127.0.0.1 is used, it is assumed that the user has login
privileges to the current host, and is not prompted for a username and password.
After authentication is performed, you will see a login successful message and the SOL Proxy
main menu prompt. You are ready to use SOL Proxy. See "SOL Proxy Main Menu" for further
instructions.
SOL Proxy Main Menu
After the telnet connection with SOL Proxy is successfully established, you are presented with the following menu of choices. See Figure 3-10.
Figure 3-10. SOL Proxy Main Menu Example
The SOL Proxy main menu allows you to change the SOL settings of a remote managed system's BMC, reboot the remote BMC, or activate console redirection.
When you select menu option 1, Connect to the Remote Server's BMC, you are prompted for the BMC IP address and BMC login. After you enter the required information and make a successful connection, the internal state SLP is changed to "connected." If you select menu options 2, 3, or 4, and the application state is not "connected," you are prompted to connect to a BMC.
Menu option 2 allows you to enable, disable, and configure the SOL defaults, including the minimum user privilege level required for activating SOL and the communication baud-rate.
Menu options 3 and 4 allow you to establish a SOL remote console session through the SOL Proxy main menu. Menu option 3 establishes a SOL session without changing the remote system's state. This option is ideal for connecting to the Microsoft SAC/EMS or the Red Hat Enterprise Linux console. Menu option 4 reboots the remote managed system and establishes a SOL session. This option is best suited for performing BIOS setup and system configuration tasks.
To exit an active SOL session, use the <~><.> character sequence. This sequence terminates SOL and returns you to the top-level menu.
Connecting to the Remote Managed System's BMC
NOTE: While multiple SOL sessions can be active at the same time, only one console redirection session
can be active at any given time for a managed system.
Select option 1 in the main menu.
Enter the BMC IP address of the remote managed system.
Provide the BMC username and password for the BMC on the managed system. The BMC
username and password must be assigned and stored in the BMC non-volatile storage. See
"Configuring Your Managed System" for more information about configuring BMC users.
Only one SOL session with one BMC is permitted at one time.
The connection status displays on the main menu. See Figure 3-11.
Figure 3-11. Connecting to the Remote System's BMC
Configuring the SOL for the Remote Managed System
Select option 2 in the main menu.
NOTE: You must be connected to the managed system's BMC before you can configure the SOL
features. If SOL Proxy is not yet connected to the managed system's BMC, you are prompted for an IP
address and a username/password combination. See "Connecting to the Remote Managed System's
BMC" for more information.
The SOL configuration menu appears. According to the current SOL status, the content of the SOL configuration menu varies:
If SOL is already enabled, the current settings are displayed and you are presented with three choices. See Figure 3-12.
Figure 3-12. Configuring the Serial-Over-LAN for the Remote System, Example 1
If SOL is currently disabled, the options shown in Figure 3-13 are displayed. Type Y to enable SOL or N to keep SOL disabled. See Figure 3-13.
Figure 3-13. Configuring the Serial-Over-LAN for the Remote System, Example 2
If SOL is enabled, two BMC settings are displayed:
The communication baud-rate between the system serial port and the BMC
The minimum BMC user privilege level required for activating console redirection
SOL Proxy displays a list of valid values for each feature, as well as the current value of the feature enclosed in a pair of brackets. Select the number before a value to set it as the new setting, and press <Enter> to confirm your changes. The new BMC settings are then displayed. See Figure 3-14.
Figure 3-14. Configuring the Serial-Over-LAN for the Remote System, Example 3
Activating Console Redirection
Select option 3 in the main menu.
NOTE: You must be connected to the managed system's BMC before you can configure the SOL
features. If SOL Proxy is not yet connected to the managed system's BMC, you are prompted for an IP
address and a username/password combination. See "Connecting to the Remote Managed System's
BMC" for more information.
The remote managed system's text console is redirected to your management station. See Figure 3-15.
NOTE: BIOS Console Redirection must be enabled on the managed system and correctly configured
before SOL can be successfully activated. See "Configuring Your Managed System" for more information.
Figure 3-15. Console Redirection Example
Rebooting the Managed System and Activating Console Redirection
Select option 4 in the main menu.
NOTE: You must be connected to the managed system's BMC before you can configure the SOL
features. If SOL Proxy is not yet connected to the managed system's BMC, you are prompted for an IP
address and a username/password combination. See "Connecting to the Remote Managed System's
BMC" for more information.
The power state of the remote managed system is confirmed. If power is on, you are asked to decide between a graceful or forceful shutdown.
Next, the power state is monitored until the status changes to off. Console redirection begins, and the remote managed system text console is redirected to your management station. Use the escape character sequence <~><.> to terminate console redirection and return to the top-level menu.
While the managed system reboots, you can enter the BIOS system setup program to view or configure BIOS settings. See Figure 3-16.
NOTE: Before activating the console redirection, you must first enable the console redirection features.
See "Configuring Your Managed System" for more information.
Figure 3-16. Reboot Example
Getting Help
Select option 5 in the main menu to display detailed descriptions for each option. See Figure 3-17.
Figure 3-17. Sample Help Screen
Exit
Select option 6 to end your telnet session and disconnect from SOL Proxy.
Configuring SOL Proxy with the SOL Proxy Configuration File
SOL Proxy must be correctly configured and running before you can establish a telnet connection.
There are certain SOL parameters that the user can set by modifying the solproxy.cfg file. The parameters and their descriptions are as follows:
Comments
Any line starting with a "#" is treated as a comment. For example:
#The file is an example.
IP address
ip — Specifies the specific IP address used to connect to SOL Proxy. This item defines what kind of connection can be accepted to establish a SOL Proxy telnet session. There are three possible values:
INADDR_ANY — SOL Proxy accepts the telnet request to any system.
127.0.0.1 — SOL Proxy accepts the telnet request to the localhost.
IP address — SOL Proxy accepts the telnet request to the specified IP address.
For example:
ip=INADDR_ANY
Port binding
port — Specifies the port at which the SOL Proxy listens for incoming connections. By default, the port is set to 623 and can be modified by the user.
This item defines the port when you telnet SOL Proxy. If this item is absent, 623 is set as the default port. For example:
port=623
Session Timeout
session_timeout — Specifies the time in minutes before the SOL Proxy session times out.
If there is no keyboard activity for the specified timeout period, the telnet session and the SOL session will be closed. The timeout value is specified in minutes and can be changed during SOL Proxy installation. For example:
session_timeout=30
Power-off Timeout
power_off_timeout — Specifies the time in seconds before the SOL Proxy gives up polling for the managed system's power status. If the SOL Proxy issues the power off command and the system does not power off within the specified interval, the SOL Proxy returns with a message, indicating that the SOL Proxy was unable to power off the system due to the timeout interval.
NOTE: When Reboot and Activate Console Redirection is selected and power for the remote managed
system is on, a power off IPMI command is issued. The power status is then continually monitored until
the power status reports "off." If power status remains "on" longer than this timeout period, Reboot and
Activate Console Redirection reports an error and returns to the top-level menu. This timeout value is
specified in seconds and can be changed during SOL Proxy installation.
For example:
power_off_timeout=60
Retry Interval
retry_interval — Specifies the period of time in seconds that the BMC waits before it tries to resend a packet. The retry_interval unit is half a second. Therefore, a value of 2 means that the software waits one second for the BMC to respond before it tries to resend the packet, a value of 4 means that it waits two seconds, and so on. For example:
retry_interval=2
Retry Count
retry_count — Specifies the maximum number of times that the software tries to resend a packet if it does not receive a response from the BMC. Before each retry, the software waits for the interval specified by the retry_interval parameter. For example:
