IBM LTO - Belisarius Code Version Not Displayed Properly Under VOP

Asset ID:	1-72-2009035.1
Update Date:	2018-01-03
Keywords:

Solution Type Problem Resolution Sure

Solution 2009035.1 : IBM LTO - Belisarius Code Version Not Displayed Properly Under VOP

Applies to:

IBM LTO6 Tape Drive - Version All Versions to All Versions [Release All Releases]
IBM LTO5 Tape Drive - Version All Versions to All Versions [Release All Releases]
Information in this document applies to any platform.

Symptoms

IBM LTO Belisarius code version not displayed properly under LTO VOP.

Originally Belisarius code was a combination of three different numbers, separated by a dot. For example: 2.38.24

This style of firmware version, our LTO VOP did display properly, when connecting to the card and checking it's firmware version.

However, when we moved to the new 4.xx.xx.xx style of firmware, it seems that LTO VOP does not display the firmware level correctly. Also the way it is displayed, will vary between LDI and ADI mode.

4.17.12.35 version is displayed in LDI mode like this: 04.17.35

4.17.18.36 version is displayed in LDI mode like this: 04.17.36

4.17.18.36 version is displayed in ADI mode like this: 04.17.18

See the attachment for more details.

Cause

This is under investigation in IBM why the ADI mode is not displayed the same way as the LDI mode. However, this seems to be related to the fact that the firmware length is different and this can also be VOP related.

Solution

One can still figure out the correct firmware version as we only have two different versions of the 4.xx.xx.xx format available. See the difference, and you can still figure out from the VOP output, what version is been used:

4.17.12.35

4.17.18.36

Attachments

This solution has no attachment