3par error from SSH in response to any command

[Hector1988]

Hello

I have an error appear at the SSH for one of our storage system 3PAR 7400

in response to almost any command says " showsys: Error: Could not find request handler: EAIPC_NOPHANDLE --no phandle is available or found "

SSMC is also disconnected and in administration console, the status is Connection Lost.

Thanks for your time.

[Hector1988]

Hello All

I appreciate if you give me any ideas about this problem.

[sbhat09]

Hello @Hector1988,

Please check you have network connectivity between the 3PAR and SSMC host (VM). Make sure there is physical network connectivity, management ports are intact and IPs of the management port and SSMC host are able to communicate.

Then try:

• In SSMC login screen, Select the Administrator Console check box.
• Enter the SSMC administrator username and password and login
(This is different than SSMC main console credentials)
• Select the system you want to connect.
• Go to the Actions menu and select ‘Connect’.

Regards,
Srinivas Bhat

If you feel this was helpful please click the KUDOS! thumb below!
Note: All of my comments are my own and are not any official representation of HPE.

[Hector1988]

Hello @sbhat09

my network connectivity is ok and I can SSH to 3par but in response to almost any command, the cli return this error. " showsys: Error: Could not find request handler: EAIPC_NOPHANDLE --no phandle is available or found "

also i did your procedure in SSMC but not work for me.

Thanks for your response.

[Hector1988]

Hello

any suggestion about this error?

Thanks.

[sbhat09]

Hello @Hector1988,

What is the version of SSMC? What is the current 3PAR OS version and patches installed in the 3PAR system?

Regards,
Srinivas Bhat

[Hector1988]

Hello @sbhat09 

Many thanks for your helpful support, SSMC(version 3.5) is not my concern right now, 3PAR os version is 3.2.2 MU4

i have another 3PAR with same version and connect to same SSMC without problem.

could you please give ullistration for the follwoing errors:

showsys: Error: Could not find request handler: EAIPC_NOPHANDLE       --no phandle is available or found

What does this mean?

Thanks.

[sbhat09]

Hello @Hector1988,

Thanks for the details.

Root cause for the issue is at OS processes level. As per one of the instances I came across, the 'cachesvr' process is stuck in an infinite loop. The procedure to terminate the process is a critical operation. It is not advisable to perform over the instructions here without complete diagnosis. So, I recommend you to contact HPE support.

In another instance of this error, it fixed with OS upgrade (For 3PAR 7000 - 3.2.2MU6 with P119, for 3PAR 8000 - 3.3.1).

So, check if you want to go for OS upgrade or report it to HPE support.

Regards,
Srinivas Bhat

If you feel this was helpful please click the KUDOS! thumb below!
Note: All of my comments are my own and are not any official representation of HPE.

[sbhat09]

Hello @Hector1988,

If it is fine for your 3PAR array to go offline for sometime, you can try the system reboot. Both the nodes will go offline and reboot together. If there are no connected hosts and no data that shouldn't be a problem.

The command is 'shutdownsys reboot'. Then 'yes' in the next prompt.

Regards,
Srinivas Bhat

If you feel this was helpful please click the KUDOS! thumb below!
Note: All of my comments are my own and are not any official representation of HPE.

[Hector1988]

Hello @sbhat09 

thanks for your helpful support,

i tried "shutdownsys reboot" command, but like other commands, the 3par reject this command too with same error.

Could not find request handler: EAIPC_NOPHANDLE       --no phandle is available or found

do you have any suggestion to kill 'cachesvr' process directly?

many Thanks.

[sbhat09]

Hello @Hector1988 

You can try the command with the option '-f'. (However, I haven't personally tried. Not sure if it works or not.)

shutdownsys -f reboot.

If you still face the same issue, please try to physically powersycle the the system. Manually shutdown or disconnect the power supply and then restart after several minutes.

Regards,
Srinivas Bhat

If you feel this was helpful please click the KUDOS! thumb below!
Note: All of my comments are my own and are not any official representation of HPE.

[sbhat09]

Hello @Hector1988,

Have you tried any of the above (shutdownsys -f or manually powercycling the system)?

Was that helpful?

Regards,
Srinivas Bhat

If you feel this was helpful please click the KUDOS! thumb below!
Note: All of my comments are my own and are not any official representation of HPE.

[veeyarvi]

Hello Hector1988

This needs a deeper analysis and might need the root access. Did you contact support for this issue?

Regards,

Veeyaarvi