Command View not discovering second EVA4400

[David_Phillips]

I have an existing EVA4400 configuration, which is working correctly. I've added a second EVA4400 controller unit and discs in a second office, connected to a fabric switch and passed over a FC link back to the main office. This is then connected to the existing fabric in the main office.

From the fabric configuration I can see the controller units from the second EVA, and have added them in to the zone which includes the Command View server.

When I attempt to discover the second EVA from the existing command view server, it does not discover the new EVA. There is currently no TCP/IP based connectivity between sites - does command view require a IP link to the management module, or will it work solely over the FC link?

If it will work over the FC link, does anyone have an idea what the problem might be?

Cheers,
David

[Torsten.]

Communication works over FC only. Did you try to stop/stat CV service already?

[David_Phillips]

Yep - I've restarted the server just to make sure.

[Torsten.]

This did cost me half a day some time ago: the zone was added, but not activated!


;-))


Double check this.

[David_Phillips]

Yep... That's exactly what it was. I noticed that the SCSI device hadn't been picked up on the CV server, so checked the zoning again. Although I'd clicked the "Save Config" button, I hadn't clicked the "Enable Config" button.

All sorted and working fine now...

[Torsten.]

You are not alone David.