emcp:Mp:Error

[Rahul Rai_1]

Hi Team,

I need your help, I get an error from a server
emcp:Mp:Error: Path c12t9d3 to Symm 000190102161 vol 22b4 is dead. please find the attachment which is from syslog for details.

Regards,
Rahul Rai.

[George_Dodds]

Looks like the link between the server and the EMC array has a problem, i'd theck the HBA for port port 3aA

ru vgdisplay -v to check all of the physical volumes you have in vg's are still attached

Check the powermt display as well for the path status's

[Michal Kapalka (mikap) · Accepted solution]

hi,

that a information about missing some alternate path from SYMMETRIX storage box,
if you are using EMC powerpath, them check the status of presented lun to the server

powermt check ( check if som disk are dead )

- you could delete the dead paths and them using this command powermt config

powermt display

powermt display dev=all |more

- if you need more information just type powermt without switches and the help will be displaied.


#============================================

the message from your syslog :

May 15 08:09:07 devpag04 vmunix: emcp:Mp:Error: Killing bus 12 to Symm 000190102161 port 3aA.

means that yor deirector on port 3aA Symmetrix Storage wasn't available.

#============================================

If think it was a temorary outage, if you see it periodically, the you shold contact the EMC technikian to check remotely the box.

hope it was helpfull.

mikap

[Rahul Rai_1]

Thanks Mikap/George for immediate reply,

here is the output:-

==============================================================================
---------------- Host --------------- - Stor - -- I/O Path - -- Stats ---
### HW Path I/O Paths Interf. Mode State Q-IOs Errors
==============================================================================
12 0/2/1/0.140.0.49.6.9.2 unknown FA 3aA active dead 0 1

Symmetrix ID=000190102161
Logical device ID=22B4
state=alive; policy=BasicFailover; priority=0; queued-IOs=0

I have ran ioscan -fnkC disk | grep 0/2/1/0.140.0.49.6.9.2
but no output, please find the attachment from vgdisplay

Regards,
Rahul Rai.

[Michal Kapalka (mikap)]

Hi,

at first the question is about your SAN infrastructure, how many SAN switch do you have, is there a redudant fabric, how many HBA-s are in the server,

ioscan -fnC fc

them ioscan -fn |grep NO_HW - is there some disk missing.

- are you using powerpath or PV links because on some VG-tre was alternate link.

mikap

[Rahul Rai_1]

Hi Mikap,

It seems like that the problem is not from my side, so for futher investigation I have transferring this issue to SAN team because it could be a regular outage,

as you asked:-

#ioscan -fnkC fc
Class I H/W Path Driver S/W State H/W Type Description
=================================================================
fc 0 0/2/1/0 td CLAIMED INTERFACE HP Tachyon XL2 Fibre Channel Mass Storage Adapter
/dev/td0
fc 1 0/5/2/0 td CLAIMED INTERFACE HP Tachyon XL2 Fibre Channel Mass Storage Adapter
/dev/td1

there is two fc driver and both are claimed and online.

and here is the status for No_HW:-

# ioscan -fn |grep NO_HW
target 35 0/2/1/0.140.0.49.6.2 tgt NO_HW DEVICE
target 36 0/2/1/0.140.0.49.6.3 tgt NO_HW DEVICE
target 37 0/2/1/0.140.0.49.6.4 tgt NO_HW DEVICE
target 38 0/2/1/0.140.0.49.6.5 tgt NO_HW DEVICE
target 39 0/2/1/0.140.0.49.6.6 tgt NO_HW DEVICE
target 40 0/2/1/0.140.0.49.6.7 tgt NO_HW DEVICE
target 41 0/2/1/0.140.0.49.6.8 tgt NO_HW DEVICE
target 42 0/2/1/0.140.0.49.6.9 tgt NO_HW DEVICE
target 43 0/2/1/0.140.0.49.6.10 tgt NO_HW DEVICE
target 44 0/2/1/0.140.0.49.6.11 tgt NO_HW DEVICE
target 45 0/2/1/0.140.0.49.6.12 tgt NO_HW DEVICE
disk 427 0/2/1/0.140.0.49.6.12.3 sdisk NO_HW DEVICE EMC SYMMETRIX
target 53 0/2/1/0.140.0.49.7.11 tgt NO_HW DEVICE
target 85 0/5/2/0.130.0.55.6.2 tgt NO_HW DEVICE
target 86 0/5/2/0.130.0.55.6.3 tgt NO_HW DEVICE
target 87 0/5/2/0.130.0.55.6.4 tgt NO_HW DEVICE
target 88 0/5/2/0.130.0.55.6.5 tgt NO_HW DEVICE
target 89 0/5/2/0.130.0.55.6.6 tgt NO_HW DEVICE
target 90 0/5/2/0.130.0.55.6.7 tgt NO_HW DEVICE
target 91 0/5/2/0.130.0.55.6.8 tgt NO_HW DEVICE
target 92 0/5/2/0.130.0.55.6.9 tgt NO_HW DEVICE
target 93 0/5/2/0.130.0.55.6.10 tgt NO_HW DEVICE
target 94 0/5/2/0.130.0.55.6.11 tgt NO_HW DEVICE
target 95 0/5/2/0.130.0.55.6.12 tgt NO_HW DEVICE
target 103 0/5/2/0.130.0.55.7.11 tgt NO_HW DEVICE

Regards,
Rahul Rai.

[Michal Kapalka (mikap)]

hi,

it seems that somebody from SAN admin cut some zones between your server and storage or, some masking was change on the Storage.

mikap

[Rahul Rai_1]

yes Mikap I hope so,


well thanks to all of you guys.

Regards,
Rahul Rai.