============================================================================== Release Notes ============================================================================== ========================== [1] Known bugs & Issues ========================== 1. Some BMC maybe not support the graceful shutdown optional action. 2. Sysinfo fru get command will return Data Error if platform Device ID 0's FRU is invalide. ========================== [2] History ========================== Internal Release 1.0.0.2 Baseline on DELL solproxy 1.0.1.3 Release 1.0.1.3 on 2004-06-09 Release 1.0.1.4 on 2004-06-15 Release 1.0.1.5 on 2004-06-28 Release 1.0.1.6 on 2004-07-02 External Release 1.0.2.0 on 2004-07-16 Release 1.0.3.0 on 2004-09-24 External Release 1.0.3.1 on 2004-09-30 External Release 1.0.3.2 on 2004-12-06 Internal Release 1.0.3.3 on 2004-12-28 External Release 1.0.3.3 on 2005-01-10 External Release 1.0.3.4 on 2005-01-25 External Release 1.0.3.5 on 2005-02-05 External Release 1.0.3.6 on 2005-02-17 External Release 1.0.3.7 on 2005-02-22 External Release 1.0.3.8 on 2005-03-11 ========================== [3] Highlights of changes ========================== External Release 1.0.3.8 1. Fix the smbridge unfinished user authentication cause crash issue on winXP or lower platform. External Release 1.0.3.7 1. Fix code error when gernerate retry interval random. External Release 1.0.3.6 1. Change keep session alive heart-beat interval to a random value between 800ms to 1200ms. This will solve the SOL session lost when ping or two sessions established for one BMC. External Release 1.0.3.5 1. Change keep session alive heart-beat to 1100ms to solve the SOL session lost when ping. External Release 1.0.3.4 1. Fix the accident defect that smbridge report "Invalide data filed" when do console command. External Release 1.0.3.3 1. Implement the retry when BMC NACK SOL packet 2. Fix smbridge session timeout crashs smbridge when smbridge SOL session actived. Internal Release 1.0.3.3 1. Implement the retry when BMC NACK SOL packet External Release 1.0.3.2 1. Fix defect which send out IPMI retry packet and incorrectly increase the rqSeq Number. 2. Enable the enhance in Release 1.0.3.0 #2. that is support both ISOL and SOL1.0 over RMCP. ---------------------------------------------------------- External Release 1.0.3.1 1. Fix defect which send out error sol character. 2. To make sure the flawless performance erase new added feature #2 in release 1.0.3.0 ---------------------------------------------------------- Release 1.0.3.0 1. Implement SysRq feature 2. Enhance to support both ISOL and SOL1.0 over RMCP ---------------------------------------------------------- External Release 1.0.2.0 1. Implement all the feature of solproxy 1.0.1 ========================== [4] Configuration ========================== OSA SMBridge must be correctly configured and running before an incoming telnet connection can be accepted. The configuration file is a text file where the value of some runtime parameters is defined. For MS Windows operating systems the default configuration file is located in the Windows installation directory. For the Linux operating systems the default configuration file is installed in the /etc directory. The default SMBridge configuration file typically includes four key configuration parameters as depicted in the example configuration file below: Any line starting with "#" is treated as a comment. Possible configuration parameters are: # SMBridge Configuration File ip=INADDR_ANY port=623 session_timeout=30 ip This item defines what kind of connection can be accepted to establish an OSA SMBridge telnet session. There are three candidate values: "INADDR_ANY", "127.0.0.1" and a valid IP address, which respectively means that OSA SMBridge accepts the telnet request to any server, the localhost and the machine occupying the IP address specified. If this parameter is absent, system will use "127.0.0.1" (or localhost) as the default value of this parameter. port This item defines the port number when you telnet OSA SMBridge. If it is absent, system will use "623" as the default port. session_timeout If there is no keyboard activity for this timeout period, the telnet session will be closed. This timeout value is specified in minutes. If it is absent, system will use the value of 30 minutes as the default value. power_off_timeout "Power Off" timeout is only used during the reboot command, in order to abort waiting for the "Power Off" command to complete. If wait time exceeds the timeout value and the power status is still on, an error code will be returned to indicate the "Power Off" command has failed. This timeout value is specified in seconds. If it is absent, system will use the value of 45 seconds as the default value. sol_loss_silent This parameter specifies how the system behaves when one or more SOL packets are lost. Possible values are: 0 and 1. If it is set to be 0 or it is absent, system will print error message on the screen each time a SOL packet is lost. Otherwise, when the value is 1, system will silently ignore the error. The default value is 0. sol_loss_threshold This parameter specifies how many SOL packets can be lost before SOL is deactivated. The default value is 0, that is, system will deactivate sol and end the sol session when any SOL packet is lost. set_boot_option This parameter controls whether the "reboot" command sets the BIOS boot option to enable console redirection. Possible values are: on, off and auto. The default value is "auto" when the parameter is absent. If the value is "on", the reboot command will always set the BIOS flag to enable BIOS console redirection after reboot. If the value is "off", then the reboot command will not change BIOS settings. If the value is "auto", the reboot command will check whether BIOS supports this flag. If it is supported, then the system behaves as if the value is "on", otherwise behaves as if the value is "off". retry_count This parameter defines the number of times the system will retry an IPMI or SOL request when it does not get a reply from the BMC. The default value is 10. retry_interval This parameter defines the time interval between two system retries. The value is in ticks where each tick is 0.5 second long. The default value is 2, that is, the interval between two retries is 1 second long.Download Driver Pack
After your driver has been downloaded, follow these simple steps to install it.
Expand the archive file (if the download file is in zip or rar format).
If the expanded file has an .exe extension, double click it and follow the installation instructions.
Otherwise, open Device Manager by right-clicking the Start menu and selecting Device Manager.
Find the device and model you want to update in the device list.
Double-click on it to open the Properties dialog box.
From the Properties dialog box, select the Driver tab.
Click the Update Driver button, then follow the instructions.
Very important: You must reboot your system to ensure that any driver updates have taken effect.
For more help, visit our Driver Support section for step-by-step videos on how to install drivers for every file type.