
UNSOLVED
ESX 3.5 and CX3-10
hi all,
i want to connect some vmware hosts (ESX 3.5U4) to my CX3-10c.
On the ESX side drivers are installed correctly and i can see fc devices, the port for the Naviagent management is open, on the san side, the machine is correctly zoned.
When i try to register the esx service console with naviserverutil (latest version, downloaded 10 mins ago), the esx does not find the clariion.
On the clariion side, with Navisphere under the Hosts tab i see the two hba's of the esx (unregistered, unknown).
Basically i'm not able to register the esx console on my storage system.
Reading "Installation Roadmap for CLARiiON Storage Systems" under the ESX Checklist i noticed some requirements:
"A CX3 series storage system running FLARE OE version 03.26.xxx.5.014 or later"
My CX3-10 has a firmware revision of 3.24.10.5.016, is this the cause of my problems ? Should i upgrade the Flare on my cx ?
thanks
marco
i want to connect some vmware hosts (ESX 3.5U4) to my CX3-10c.
On the ESX side drivers are installed correctly and i can see fc devices, the port for the Naviagent management is open, on the san side, the machine is correctly zoned.
When i try to register the esx service console with naviserverutil (latest version, downloaded 10 mins ago), the esx does not find the clariion.
On the clariion side, with Navisphere under the Hosts tab i see the two hba's of the esx (unregistered, unknown).
Basically i'm not able to register the esx console on my storage system.
Reading "Installation Roadmap for CLARiiON Storage Systems" under the ESX Checklist i noticed some requirements:
"A CX3 series storage system running FLARE OE version 03.26.xxx.5.014 or later"
My CX3-10 has a firmware revision of 3.24.10.5.016, is this the cause of my problems ? Should i upgrade the Flare on my cx ?
thanks
marco
Responses (1)
Solutions (0)

Allen Ward
6 Operator
•
2124 Posts
379
0
Posted May 20th, 2009 03:00
So lets start with the FLARE code version. For best support and the best feature set with the latest fixes available EMC is always going to recomend that you run the latest FLARE code. So from an official EMC perspective the answer to "Should I upgrade my FLARE code" is almost always going to be a resounding "Yes".
From a customer perspective though, you should carefully read the release note between where you are and where you think you should (maybe) be and determine if the changes/fixes are important in your environment. FLARE code upgrades can be done non-disruptively, but sometimes it takes a lot of disruptive preparation to ensure a non-disruptive upgrade on the array itself. Hosts may need patches, settings changed, firmware or driver updates, etc. Fortunately you are only talking about a CX3-10, so it won't likely be as painful as when we prep to upgrade one of our CX3-480 arrays!
Another thing you have to consider is the balance between the advantages of the upgrade against any potential negative impacts. You might have some older hosts that are no longer supported by a current version of PowerPath. The OS might be so old that you can't get a newer version of PP running on it, but the older versions might not be certified for interoperability with the new FLARE version. In this case you might decide to stay where you are to maintain the "status quo" (since you know they work together now).
Now, after all that, we get to the real root of your question... Will the FLARE code version on your array prevent the naviserverutil from communicating with your array? That question I can't answer without some more research. Honestly the first place I would check (and I'm no ESX guru so bear with me if this doesn't sound right) is that I've heard ESX has a built in "firewall" of some type that occasionally causes some issues with IP connectivity for ESX itself communicating with things for management functionality. You can either look into this, or you can go another route to bypass the troubleshooting steps entirely.
That other route involves simply bypassing the automated registration of the initiators and jumping straight to manual registration on the host itself. I have not done this for ESX before, but I'm fairly certain that there should be a section in the host connectivity guide that will give you details on doing this properly. Once you have manually registered the host initiators, you are good to go and have no need to have the ESX server communicate over IP with the array.
Hope this helps.