FS System: SAN_EVENT_INM_MIRROR_FAILED Events Being Reported

Asset ID:	1-72-2285059.1
Update Date:	2017-07-20
Keywords:

Solution Type Problem Resolution Sure

Solution 2285059.1 : FS System: SAN_EVENT_INM_MIRROR_FAILED Events Being Reported

Applies to:

Oracle FS1-2 Flash Storage System - Version All Versions to All Versions [Release All Releases]
Pillar Axiom Replication Engine (MaxRep) - Version 3.0 to 3.0 [Release 3.0]
Information in this document applies to any platform.

Symptoms

The FS1-2 Event Log may report Warning message SAN_EVENT_INM_MIRROR_FAILED events such as the following:

2017-04-15T16:37:27.067 SAN_EVENT_INM_MIRROR_FAILED WARNING Source=/CONTROLLER-01
2017-04-15T16:37:27.068 SAN_EVENT_INM_MIRROR_FAILED WARNING Source=/CONTROLLER-01
2017-04-15T16:37:27.165 SAN_EVENT_INM_MIRROR_FAILED WARNING Source=/CONTROLLER-01
2017-04-15T16:37:27.265 SAN_EVENT_INM_MIRROR_FAILED WARNING Source=/CONTROLLER-01
2017-04-15T16:37:27.266 SAN_EVENT_INM_MIRROR_FAILED WARNING Source=/CONTROLLER-01

Cause

The SAN_EVENT_INM_MIRROR_FAILED events are due to a loss of paths to the MaxRep Engine. If the FS1-2 fails to find the MaxRep Engine logged into the switch these events will be reported.

Solution

The events indicated a SAN issue, viewing the details of the SAN_EVENT_INM_MIRROR_FAILED event will provide the LUID of the LUN that was impacted.

This can also be seen in the FS1-2 logs viewing the *.events.xml file, for example:

<GetSystemEventResponse>
<SystemEventInformation>
    <EventType>SAN_EVENT_INM_MIRROR_FAILED</EventType>
    <Severity>WARNING</Severity>
    <Category>SYSTEM</Category>
    <Time>2017-04-15T16:37:27.266</Time>
    <SourceNodeIdentity>
      <Id>508002000158EB90</Id>
      <Fqn>/CONTROLLER-01</Fqn>
    </SourceNodeIdentity>
    <EventParameterList>
      <ParameterName>EventInmMirrorStatus.slunGuid</ParameterName>
      <ParameterValue>6000B08414B3030333434393235002E6</ParameterValue>
    </EventParameterList>
    <EventParameterList>
      <ParameterName>EventInmMirrorStatus.mirrorStatus</ParameterName>
      <ParameterValue>CM_INM_MIRROR_STATUS_FAILED</ParameterValue>
    </EventParameterList>
    <EventParameterList>
      <ParameterName>EventInmMirrorStatus.additionalInfo</ParameterName>
      <ParameterValue>0x2</ParameterValue>
    </EventParameterList>
    <EventGuid>0010E08DA56A00000595AD229C871003</EventGuid>
</SystemEventInformation>
</GetSystemEventResponse>

From the LUN LUID you can view the LUN Name in the FS1-2 GUI by navigating to the "SAN" tab -> under "Storage" click "LUNs". In the main page far right column will show the LUID for each LUN, from this page you can view the LUN Name.

Tech Support Engineers can also use the FSInfo.pl -l command which will list all the LUNs on the FS1-2 displaying the LUN Name and LUID.

Knowing the LUN Name, view the Mapping details to verify which SAN Hosts and MaxRep Engines have access to the LUN.

Tech Support Engineers can also use FSInfo.pl -m -r command to print out the LUN to Host mapping relationship to see what SAN Hosts have access to the LUN.

If events SAN_EVENT_INM_MIRROR_FAILED occur frequently and none of the SAN Hosts or MaxRep Engines were Shutdown or Restarted then a SAN issue may be occurring and will need to be investigated:

From the FS1-2 GUI check if any of the Controllers report Channel Errors, in the GUI navigate to "SAN" tab -> under "Statistics and Trending" click "Controller Protocols". In the main page right mouse click on the Controller Port and select "View Details". Check to see if there are any Channel Errors seen. Recommend monitoring the screen to check if the counters continually increase. Channel errors may indicate a hardware issue on the SAN.

From a processed FS1-2 logset you can execute SanLogSummary.pl against the controller logs to see if there are any issues on the SAN such as Channel Errors (RND errors), Data Phase Errors, Physical FC Errors, etc. Such errors may indicate a bad FC cable or bad SFP.
Check the SAN switch port statistics for any errors that the SAN Hosts, MaxRep Engines, and FS1-2 Controller ports connect to. Check for bottlenecks and any frames that maybe getting dropped.
Review the SAN zoning configuration. SAN Best Practices should always be followed when configuring SAN zoning. MaxRep Engines zones should always be configured as either single initiator -> single target or single initiator -> multiple targets mentioned in the Oracle MaxRep for SAN User's Guide section "FC Initiator and Target Ports" on page 63. DO NOT configure a zone containing multiple initiators as that can cause RSCN storms.

References

<BUG:24844723> - SAN_EVENT_INM_MIRROR_FAILED

Attachments

This solution has no attachment