Multipathing reports LUNs as failed at the DR end in a Disaster Recovery solution using EMC Unity 300 replicated link

Solution Verified - Updated -


The LUN state of a replicated LUN is reported by multipathing as "failed" on the Disaster Recovery node.

The paths are listed as "failed", then "active", then "failed" and so on in a circular fashion and they change their status every 5 seconds.

mpathr (3600601602ed04400b28b035e9f5e7c3b) dm-11 DGC     ,VRAID           
size=150G features='1 queue_if_no_path' hwhandler='1 emc' wp=rw
|-+- policy='service-time 0' prio=4 status=active
| |- 14:0:0:8 sdal 66:80  failed ready running
| `- 13:0:0:8 sdak 66:64  failed ready running
`-+- policy='service-time 0' prio=1 status=enabled
  |- 12:0:0:8 sdai 66:32  failed ready running
  `- 11:0:0:8 sdag 66:0   failed ready running

Each path to the replicated LUN is also triggering console/syslog messages like

Feb 24 03:11:03 db-dr01 multipathd: mpathr: sdag - emc_clariion_checker: Active path to inactive snapshot WWN 600601602ed04400b28b035e9f5e7c3b.


  • Red Hat Enterprise Linux 7.3
  • Kernel version 3.10.0-514.el7.x86_64 x86_64
  • device mapper multipathing
  • 2 x EMC Unity 300 arrays connected via iSCSI, one array hosting primary LUNs, the other disaster recovery replicated LUNs using native async replication between the production and DR LUNs.

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content