Chickens and Eggs (and XIV )
anthonyv 2000004B9K Comments (4) Visits (4517)
In my last post I talked about the versions of XIV code and XIV Management GUI needed for QoS.
It leads to the question of how to match the Management GUI version to the XIV code version.... which goes with which?
Many storage products have management software that is separate from the software that runs inside the box (more commonly known as the firmware).
So for XIV, is there a best practice? What if I have multiple XIVs.... do I need them all to be on the same firmware version?
The good news is that you can simply use the highest available version of Management GUI, regardless of what code versions the XIVs are on.
In other words, if you see a new version of XIV GUI on the download site.... just upgrade to it.
Check out the screen capture below. This was taken with version 2.4.4 of the Management GUI (which is the latest at February 2011):
The XIV on the left is running the GA XIV code, version 10.0.0.a (which came out well over two years ago).
So I am able to run one of the oldest versions of XIV code, with the latest Management GUI. This is very good.
But why is the right hand machine greyed out?
To mix things up. the XIV on the right is running a brand new development (and thus un-released) version of code.
Because I am running a (relatively) older GUI version against a (relatively) newer XIV code version, the GUI is protecting us from a potential mismatch.
This means the GUI is always backward compatible, but is not always forward compatible.
Now speaking of greyed out, we saw a bug on previous versions of the GUI code, where a read-only user id would be confronted with a similar sight.
The machine would be greyed out and thus unmanageable. The work around was to use the older 2.4.2b build 10 version of the GUI.
The good news is that 2.4.4 contains the fix for this bug (so its another reason to upgrade).
That is all for now. Don't forget you can always logon as p10demomode to get a demo mode view of the XIV GUI.