No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search


To have a better experience, please upgrade your IE browser.


How to View the Software Version of the S5000 Storage Device?

Publication Date:  2012-07-20 Views:  127 Downloads:  0

Issue Description

The controller information of the S2000/S5000 displayed on the OSM varies with version changes.
How to view the controller version from the collected information about the storage device?
For version changes, there are two different methods for viewing the controller version of the V1000/S5000/S2000 on the Web page.
Method 1: Log in to the OSM and choose System > Controller Information to view the versions of both controller A and controller B, as shown in the following figure.

Method 2: Click About on the upper right corner of the OSM to display a window in which the controller version is displayed, as shown in the previous page.

Alarm Information


Handling Process

There are three methods for viewing the controller version:
1. OSM: Log in to the Web page to view the controller version.
2. CLI: Log in to the CLI by using the serial port or the management port and run the showallver command to view the controller version, SES version, product version, and logical version.
3. Log: Run commands or decompress the log by using the log collection tool to find the messages file, and search "Firmware version : " (including the space) by using the test file to Firmware version : 0x12345678. The eight digits behind 0x respectively corresponds to the eight red digits in the actual version
For example, if the searched version is version : 0x20121201, the actual software version is
The compressed log package collected by using the log collection tool contains a System_information file in which the version can be viewed.

Root Cause



If the messages log is be flushed by the history information, view the messages_bak log. If the messages_bak log is flushed too, try to view the messages in his_tar_powerlost_time.tgz under \OSM\log_conf_local\log\his_debug.
View the messages after the OSM is restarted. The first a few lines of the log file contains syslogd:
Mar 29 11:51:00 OceanStor syslogd 1.4.1: restart.