Unsolved
This post is more than 5 years old
6 Posts
0
2206
EMC PowerPath/VE 5.4 SP2 support MSCS shared RDMs
We have installed PowerPath/VE 5.4 SP2 on about 50 ESXi hosts, some with MSCS shared RDMs VM's.
Ques 1. ESXi reporting the following error:-
Error:emcp:PowerPlatformScsiIoErrorIsRetryable: Sense Info S:5 ASC:80 ASCQ:21 May 30 00:04:14 vmkernel: 7:06:41:37.639
Ques 2. rpowermnt display reports the following: alot of erros on all the RDM's reported by powerpath, Any idea what these erros could be? I have an sr with EMC, but still waiting..
Pseudo name=emcpower0
Symmetrix ID=000192601794
Logical device ID=1896
Standard UID=naa.60000970000192601794533031383936
state=alive; policy=SymmOpt; queued-IOs=0
==============================================================================
--------------- Host --------------- - Stor - -- I/O Path -- -- Stats ---
### HW Path I/O Paths Interf. Mode State Q-IOs Errors
==============================================================================
2 vmhba0 C0:T1:L40 FA 7hA active alive 0 1
1 vmhba1 C0:T2:L40 FA 6gB active alive 0 0
2 vmhba0 C0:T0:L40 FA 5hA active alive 0 1
1 vmhba1 C0:T1:L40 FA 8hA active alive 0 0
1 vmhba1 C0:T0:L40 FA 6hA active alive 0 0
2 vmhba0 C0:T3:L40 FA 7gB active alive 0 1
2 vmhba0 C0:T2:L40 FA 5gB active alive 0 1
1 vmhba1 C0:T3:L40 FA 8gB active alive 0 1
Pseudo name=emcpower1
Symmetrix ID=000192601794
Logical device ID=1A49
Standard UID=naa.60000970000192601794533031413439
state=alive; policy=SymmOpt; queued-IOs=0
==============================================================================
--------------- Host --------------- - Stor - -- I/O Path -- -- Stats ---
### HW Path I/O Paths Interf. Mode State Q-IOs Errors
==============================================================================
2 vmhba0 C0:T1:L41 FA 7hA active alive 0 1
1 vmhba1 C0:T2:L41 FA 6gB active alive 0 0
2 vmhba0 C0:T0:L41 FA 5hA active alive 0 1
1 vmhba1 C0:T1:L41 FA 8hA active alive 0 0
1 vmhba1 C0:T0:L41 FA 6hA active alive 0 0
2 vmhba0 C0:T3:L41 FA 7gB active alive 0 1
2 vmhba0 C0:T2:L41 FA 5gB active alive 0 1
1 vmhba1 C0:T3:L41 FA 8gB active alive 0 1
Brion2
154 Posts
0
June 4th, 2012 07:00
Hello. The error that you are seeing is informational only. It will not provide any useful information to the end user with regards to path state or status. A Primus case is being prepared.
The error count that you see in the output of the rpowermt display indicates the number of times a path has transitioned from a live to a dead state. That can occur for a variety of reasons on the host, SAN, or storage side. If you begin to see a rise in the number of errors, you may want to use vCenter or PowerPath Viewer alert capability to identify when these outages are occuring to help find a root cause.
I hope this helps.
Thanks, Brion
Brion2
154 Posts
1
June 4th, 2012 08:00
The PowerPath Viewer console is installed on a Windows physical server or guest OS. There is no reboot required to install the console. In the case of ESX, you don’t need to install anything on the hypervisor. There is no agent to install. Once the console is installed, you simply discover the ESX server by FQDN or IP address.
For this particular logged message, you will continue to see it in 5.4.x. You would not see it with 5.7. However, PP/VE 5.7 is supported only on ESX5.
-Brion
wamatha
6 Posts
0
June 4th, 2012 08:00
Thank you for response Brion, I will install PowerPath Viewer, does it require a reboot?
I was told The PowerPath/VE 5.4 SP2 P01 package that runs on ESX 4.1 includes the fix for this behavior, which am yet to install.