Raritan Computer SX4 사용자 설명서

다운로드
페이지 172
C
HAPTER 
11:
 
F
IRMWARE 
U
PGRADE 
I
NSTRUCTIONS
 87 
 
 
Chapter 11: Firmware Upgrade Instructions 
Firmware Image Upgrade Instructions for DSX16/DSX32  
Important: These instructions do NOT apply to DSX4 and DSX8 units: 
To upgrade the DOM disk with firmware image: 
1.  Remove the DOM disk from the Dominion SX unit.  
2.  Plug the DOM disk into an empty “secondary IDE slot” on a Linux machine.  
3.  Determine the device file used to access this IDE slot.  
4.  Login as root on the Linux machine.  
5.  Copy the firmware image (dom2.x.y) and script file [program_dom_image.sh] onto the Linux 
machine.  
6.  Update the script file [program_dom_image.sh] with the appropriate device file name. 
DOM_DEVICE variable is currently assigned to /dev/hdd in this script file. This variable should be 
updated to reflect the correct device file name.  
7.  Run the script as follows: ./program_dom_image.sh  dom2.1.8 (please note that the “.” (period mark)  
preceding the “/” (forward slash) before the script name is required). 
8.  Shut down the Linux machine, remove the power cord, and remove the DOM disk.  
9.  Plug the DOM disk into the Dominion SX unit, reconnect the power cable to the DOM, close the unit 
cover, install the screws, and power ON the unit. 
10.  The Dominion SX unit can be accessed using http://192.0.0.192 address. [Note: From release 2.2.4 
onwards the factory default address is changed to 192.168.0.192. So after upgrading to 2.2.4, if a 
factory reset is done, then the Dominion SX unit can be accessed using http://192.168.0.192].  
 
 
Troubleshooting Notes 
1.  After upgrading to 2.2.x from 2.0.x, close ALL open browser windows and start a new browser session. 
Browsers cache the Java session information, so upgrading to the new release will not take effect 
unless ALL browser sessions are closed (if LDAP or NTP configuration menu is not visible after 
upgrading to 2.1.x then this is the most likely reason). 
2.  If the DSX4/8 unit is taking more time to reboot after the upgrade is complete, this happens only one 
time after the upgrade is complete. It is caused by the unpacking of some of the upgrade packages. 
Flash writing is a slow process, so it will take approximately 5-7min longer than the usual boot-up time 
after the upgrade is done. After one reboot the reboot time will return to normal.