HPE EVA Storage
cancel
Showing results for 
Search instead for 
Did you mean: 

Re: EVA4400 not visible in CVE

 
Highlighted
Frequent Advisor

Re: EVA4400 not visible in CVE

Name Server gives me this information about the EVA ports:
Device name "HSV300 - NO SCELL - CR11EF". Is that correct?
Highlighted
Regular Advisor

Re: EVA4400 not visible in CVE

There is a difference between Smartstart for servers and Smartstart for EVA.

If you select the line in the nameserver with either a EVA or the server object you would normaly get access to a button called "Accessible devices". This will show the devices this wwn is able to access.

kurtg
Highlighted
Frequent Advisor

Re: EVA4400 not visible in CVE

According to "accessible devices" the CVE-server can see EVA and vice versa. Strange...
Highlighted
Regular Advisor

Re: EVA4400 not visible in CVE

You need to provide som more in depth information about youre configuration.

os/patchlevel, hba, driverversion, switchtype/foslevel and so on.
Highlighted
Occasional Advisor

Re: EVA4400 not visible in CVE

Hi,

The services are running ok?
Do you see any errors in logs?

Cheers,
George
Highlighted
New Member

Re: EVA4400 not visible in CVE

Hi Panzer,

We recently had exactly the same problem, the only solution (both ours and HP's) was to do an online reboot of the controllers. The system could still be managed by the WOCP and from there rebooted. After rebooting the primary controller we were able to see it in the CVE, but only as a secondary controller. Once we reboot the second controller it all came up with no problems and no errors, of course just make sure all your servers are attached to both fabrics otherwise... We did however have HP on standby in the event that it didn't come up again, which wouldn't have been the first time.

Hope that helps

Adrian
Highlighted
Regular Advisor

Re: EVA4400 not visible in CVE

Hi Panzer!

Youre stats "I have assigned points to 6 of 62 responses to"

This is not how the support forumes is supposed to work........