1 MAXDATA Modular System Firmware Update

(1)

1 MAXDATA Modular System Firmware Update

This document will help you to update the firmware from a MAXDATA Modular System. Modular Systems which was purchased before 1st_{April 2009 with Microsoft Windows 2008 Preload, should not} updated with the firmware from our ftp server. Please contact the Server support for the required firmware package file for these systems.

Attention: Backup your data and your OS installation before you start a Firmware upgrade. Data loss or data unavailability during or after an update cannot be excluded. It is not recommended to update firmware or driver on productive systems, because some updates needs a system shutdown.

1.1 Connection

Normally the firmware update will be done over the embedded web based GUI. If an update over the web GUI is not possible e.g. caused from a corrupted Web GUI or firmware, it is possible to update or repair the firmware with the Firmware Recovery procedure. The Recovery Update needs a serial connection with a serial cable (not included in the delivery). The serial cable is also needed to find out the IP address if it is unknown. More Information to find out the IP address can be found in the section 1.6 Firmware Update with Emergency Firmware Recovery

1.2 Required driver / software on the server

- Modular System firmware package v2.7 or higher (before update, please refer to the file release_notes.txt for firmware and software dependencies)

- DOS Update ISO only needed by Microsoft Windows 2003 preloaded systems (see 1.5 Systems with Microsoft Windows 2003 Preload

)

1.3 Notice

If you will use 2 controller please read the document MAXDATA Modular System Dual SCM MPIO Software Installation

(2)

1. Unzip the downloaded firmware package in a folder. The file CMM_Core.zip is needed from the package

2. Type in the IP address in the address bar of a browser (e.g. Firefox or Internet Explorer). The default IP address 192.168.150.150

3. Type in the user name and password to login. The default user name and password is admin

Abb. 1 4. After login click in the left menu on Firmware

5. Click on Browse and search for the CMM_Core.zip file

(3)

Abb. 3

7. Follow the instruction from the update procedure e.g. restart Server, start Controller to safe mode etc., otherwise the update cannot start

Attention: The systems should not be in use, because the restart of the controller to safe mode will deactivate the access to the hard disk drives

8. First shutdown all server modules and then the controller modules (Abb.5/6)

Abb. 4

(4)

9. After the shutdown or the restart of all needed components are done, the update can be started with click on Start Update

Abb. 7

Abb. 8

(5)

see the status of all updates (Server, controller, LAN-switches etc.)

Abb. 9

12. The Status of the server modules is Update Pending power on required. Power on of the servers is not possible if the controller update is not finished (Abb.10). So you have to wait for the controller update to finish.

Abb. 10

13. After update of all internal chassis modules, click on power on required to start the update of the server modules (a simultaneous system update needs approx. 5 minutes). If needed, the server update status can be viewed with the Remote KVM & CD console

(6)

14. Check the status of the firmware update with click on Firmware. If user actions required please follow these instructions. If all updates are done, check the viewed firmware versions with the versions listed in the Release Notes text file (included in the zip package)

(7)

This section is only relevant for systems with Microsoft Windows 2003 preload. A bios DMI update is required for those systems.

1. Web GUI: Click on Servers in the left menu 2. Click on a server module

3. Click on Remote KVM & CD

4. Choose your preferred settings for the KVM console and click on Apply to start the remote console

Abb. 13 5. Choose Devices in the menu and select CD-ROM

Abb. 14

6. Select Redirect CDROMImage and use Browse to search for the ISO file from the downloaded zip package

(8)

Normal Update with version chek (updates only if necessary)

Abb. 16 9. Wait for update to finish

Abb. 17 10. Choose Devices in the menu and select CD-ROM, to stop the redirection of the ISO

Abb. 18

11. Now choose Keyboard in the menu and select Ctrl+Alt+Del, to restart the server module. You can also use the web GUI to reset the systems

Abb. 19

(9)

If you have problems with firmware update caused from corrupted web GUI or firmware, you can use the Firmware Recovery procedure to update your Modular System. The Firmware Recovery update is done by a serial connection (e.g. Hyperterminal) and a LAN connection (cross-over recommended) to the Compute Management Module (CMM).

Tip: If the serial connection fails, try to disconnect the Modular systems from AC power for approx. 5 minutes

Attention: The server modules must be powered off e.g. with a windows remote connection, to avoid data loss when the update procedure deactivates the controller.

1. Connect the CMM with a serial cable to an administrative system (see 1.1 Connection). Also connect the CMM with a LAN cable to the administrative system (cross-over RJ45

recommended)

2. Open a hyperterminal session (bps:115200; datenbits:8; Party:none; stoppbits:1; flow control:none)

Abb. 20

3. Use the reset button or remove and reinsert the CMM for reboot. Change to the hyperterminal window and press the ENTER-Key within the next 5 seconds, after you see the message Press [ENTER] within 5 seconds for CLI, or wait for Normal boot: After pressing the ENTER-Key the message Starting CLI must appear and the boot must stop in the CMM EBF> prompt. Otherwise you must repeat this step.

(10)

CMM EBF>get net ext ip

Network interface "ext" has IP address 192.168.150.150 (Static) Status: OK

5. Open a CMD window and connect the administrative system to the CMM with the command ftp xxx.xxx.xxx.xxx (e.g. ftp 192.168.150.150) and login with username and password. The default user is admin and the default password is admin (on EBF Version older than v1.21 the default password is default). You can view the EBF version with the command get version on the CMM EBF prompt

C:\>ftp 192.168.150.150 Connected to 192.168.150.150 220 Connection Ready

User (192.168.150.150:(none)): admin 331 Enter password

Password: admin 230 Logged in

6. Use the ftp command bin for binary data transfer and hash for status monitoring ftp> bin

200 Type Binary ftp> hash

Hash…. ON FTP: (2048 Bytes/Hash).

7. Transfer the CMM_core.zip firmware file with the ftp command put "path\CMM_Core.zip" to the CMM. After transfer (approx. 10 minutes) use quit to disconnect the ftp connection to the CMM.

Attention: Use “ if you have spaces in the pathname ftp> put „C:\Modular System\Firmware\CMM_Core.zip“ 200 Port set

125 File Open for Write

###################################...################################### 250 File Received. See console for write status. New firmware will boot automatically. FTP: 64d Bytes transfered in 23,22 seconds 1999,28KB/s

ftp> quit

8. If you have an EBF version older than v1.30, you have to use the exit command to boot the CMM with the new firmware (see boot screens from EBF v1.26 and v1.30)

Boot screen EBF version 1.26

CMM EBF>Erasing file, please wait... FTP client may timeout. Erase complete.

CMM EBF>exit

CMM EBF>Mounting local storage: OK! Searching for firmware bundle...

(11)

CMM EBF>-FTP: User admin logged on. All keyboard inputs disabled.

Received 45105k...

FTP: File Upload Successful. Total file size 45207k

Starting firmware update

Erasing file, please wait. This can take a while. Erase complete.

Update is 100% complete. Update successful!

Starting new firmware now. Mounting local storage: OK! Searching for firmware bundle...

-Processing firmware bundle: CMM_Core.zip ……

-New EBF image detected. Writing... Verifying... Ok ……