Storage Essentials - HP-UX servers

[Monikvm]

Hi,
I installed Storage Essentials ver5.0 but i had some problems with mapping and discovering EVA array, so I re-installed and updated to ver 5.0.1
Now I can map an discover the EVA, but I have problems to discovering and mapping the HP-UX server, that´s strange therefore previous version I can descover and obtain topology
I install:
Tachyon Fibre Channel Driver Patch
CIM extension
WBEM, SSH and update provider.
I defined locally the root user.

Some idea??
Thanks !!

[Stephen Kebbell · Accepted solution]

Hi,

I'm not sure if 5.0.1 came with updated CIM extensions. If so, have you updated them?
What errors do you get if you run a discovery for this server?
You can try the following on the HP-UX server:
Create a file in the folder where the CIM extensions are installed (default is /opt/APPQcime/tools), called cxws.host.parameters
In this file, add the following lines:
-credentials username:password
-on [public IP Address of server]

Username and Password can be anything you want, the user does not even have to exist on the HP-UX server. Just make sure you provide the same credentials in Storage Essentials when discovering the server. Once the CIM extension is started by a user with root-credentials (or is set to automatically start on boot), it should work OK.

Restart the CIM extension and try discovering it again.

Regards,
Stephen

[Monikvm]

Hi Stephen
I defined the parameters and updated the CIM extensions, but when I try to obtain the topology of HPUX server. I got this messages
[2006-10-31 20:31] Test Discovery Started
[2006-10-31 20:31]
ping -w 1000 -n 3 consaora


Pinging consaora [172.20.22.133] with 32 bytes of data:



Reply
from 172.20.22.133: bytes=32 time<1ms TTL=255

Reply from 172.20.22.133: bytes=32 time<1ms
TTL=255

Reply from 172.20.22.133: bytes=32 time<1ms TTL=255



Ping statistics
for 172.20.22.133:

Packets: Sent = 3, Received = 3, Lost = 0 (0% loss),

Approximate
round trip times in milli-seconds:

Minimum = 0ms, Maximum = 0ms, Average = 0ms


[2006-10-31 20:32]
Origin: consaora:
FAILED as Win32Provider for: consaora
Failed. Return code value
unknown. -2147024809

Origin: consaora:
ACCESS DENIED as CxwsProvider for: consaora

Login failed.
Login as failed.



Origin: consaora:
FAILED as BrocadeElementManager
for: consaora
Cannot connect

Origin: consaora:
FAILED as LSISSI_Provider for:
consaora
Failed to establish connection.

Origin: consaora:
FAILED as McDataSNMPProvider
for: consaora
Can't connect.

Origin: consaora:
FAILED as EmcProvider for: consaora

Can't connect
SymInitialize() failed with error code 510 (The remote connection
is refused. The symapi server is probably not running)

Origin: consaora:
FAILED as
NetAppFilerProvider for: consaora
Can't establish communication with filer

Origin:
consaora:
FAILED as ClariionProvider for: consaora
NaviCLI not installed

Origin:
consaora:
FAILED as SunDotHillProvider for: consaora
A non-blank password is required.

Origin:
consaora:
FAILED as HdsProvider for: consaora
Cannot connect
Cannot connect
to HiCommand server (unknown reason)

Origin: consaora:
FAILED as CiscoSNMPProvider
for: consaora
Can't connect.

Origin: consaora:
FAILED as SnmpSwitchProvider for:
consaora
Can't connect.

Origin: consaora: ERROR as SMI-S Server for: consaora

[2006-10-31 20:32] Test Discovery Completed
Test Discovery completed in 1 minute 2 seconds .


When I start the CIM Extension on HPUX server saids.
.....
CXWS [date] [IPADDRESS of Essential and SIM server] now accepting connections

Thanks in advance!!!!!!!!

[Stephen Kebbell]

Hi,

are you using a global username/password for SE's discovery? For some reason, using the Test Discovery (which you have used in the text you posted) does not use those credentials. You need to specify the credentials for the host for a "Test" discovery to work. A normal discovery will use the global usernames, not the Test (Bug in SE).
There should also be some sort of cxws.out file on the HP-UX host. Can you see any error messages there?

Regards,
Stephen

[Monikvm]

Stephen

I solved it, discovering first by SIM and then Storage Essentials steps. And I had to use the command line to define the username and password of ssh with mxagentconfig -a -n hostname -u root -p password.

I solved the HPUX server problems, but When I updated the Service PAck 3 and CIM Extension on Storage Essentials Server, the EVA array market (misisng) and I can´t get topology and details.


Thanks in advance

[Stephen Kebbell]

Try rediscovering the EVA (or at least, the server running Command View EVA) with SIM. Then perform a "Get Topology" on that server in SE,
What version of Command View EVA are you running?

Regards,
Stephen

[Monikvm]

The Command View server its the same with SIM and Storage Essentials. I can descover an obtain the topology on this server but I can not see the EVA.

The Command View Version is 5.0.

Thanks in advance

[Stephen Kebbell]

OK, 2 issues:

1) Command View EVA and SE/SIM are not supported on the same server. See Saket's response in this thread:
http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=1070955
The SE/SIM server does not even need to be in the SAN.

2) Command View EVA 5.0 and SE still seem to have problems. Not sure what the latest status on this is.

Regards,
Stephen

[Monikvm]

Hi,
I have a question about your replies,
If I´ll intall Command View version 4.1, Do I have the same problem?,

The update to 5.0 version was recently, and I think this affected the Essentials environment.

Where can i find yhis kink of compatibility matrix??
Thanks in advanced!!!

[Stephen Kebbell]

Hi,

I've attached the latest support matrix for Storage Essentials.
According to this, CV EVA 5.0 or higher is not yet supported. But was your upgrade only command view EVA? Was your EVA's firmware also updated? It might be that your EVA's firmware requires CV 5.0 to work, meaning you could not revert back to 4.1. Was your EVA SMI-S provider also updated? This is critical - the SMI-S provider must match the Command View version. You may have to uninstall the older SMI-S provider first.

In your discovery list, add a 2nd entry for the CV EVA server, using just its IP Address. Use the credentials for the SMI-S provider, and then run a discovery for that address.

Regards,
Stephen

[ALCS]

Hi,

I was just reading this thread
I am interested to know about
Command View 6.0 (EVA 8K with XC6.0) and SE 5.1 support.

1- Is it supported on the same server ?
2- Is it discovered via SMS-S ?

Thanks
Farid

[ALCS]

Is there a newer SE 5.1 compatibilty matrix
The one attached by stephen is dated Aug-06.

Many thanks
Farid