Raritan Computer 4.3.1 Cable Box User Manual


 
CHAPTER 6: MANAGING IBM BLADECENTER SERVERS 99
Chapter 6: Managing IBM BladeCenter Servers
Paragon II connects to all blade servers installed in one IBM BladeCenter® chassis via one single
CIM so only one user can access servers in one chassis at one time. The CIM specific to IBM
BladeCenter is either P2CIM-APS2-B for PS/2 keyboard and mouse, or P2CIM-AUSB-B for
USB keyboard and mouse.
Paragon treats one IBM BladeCenter chassis as one tier device similar to the Z-CIM chain.
However, Paragon II does not detect and display the real-time blade server status in the OSUI as
it does to the Z-CIM chain. You must issue a refresh command for the following scenarios:
Connection of the IBM BladeCenter to the Paragon system for the first time
There have been changes made to BladeCenter’s hardware configuration, such as unplugging,
plugging or swapping any blade server(s), or powering off any blade server(s)
The refresh command updates the OSUI channel information of blade servers to reflect current
blade server status.
Note: BladeCenter Management Modules (MM) that have been tested to be supported include the
PS/2 module with the part number 39M4945, and the USB module with the part number 39Y9659.
Support for other BladeCenter Management Modules is not guaranteed.
Refreshing Channel Status
1. Log into the Paragon system as an administrator. Type admin in the User Name field, press
Enter, and type the password (default: raritan, all lowercase) in the Password field.
2. Make sure you are in the channel number view. If not, press F12 to toggle the view.
3. Press F5 to enter the Administration Menu.
4. Select the Channel Configuration submenu, and press Enter.
5. Use the Ç and È or the Page Up and Page Down keys to select the channel port to which
the IBM BladeCenter is connected, and press Enter.
6. Type RefreshBLD-I. Please note this is a case-sensitive command.
Figure 80 Refresh IBM BladeCenter Servers
7. Press Enter.
8. Press S to refresh the BladeCenter channel status. It takes 2 to 4 minutes to complete
refreshing, depending on your blade servers’ installation status.