Sun Microsystems, Inc.  Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition
   Home | Current Systems | Former STK Products | EOL Systems | Components | General Info | Search | Feedback

Asset ID: 1-71-1925610.1
Update Date:2016-07-28
Keywords:

Solution Type  Technical Instruction Sure

Solution  1925610.1 :   Sun Storage 2500, 2500-M2 and 6000 Arrays: How to Identify Host Initiating Failover  


Related Items
  • Sun Storage 2540-M2 Array
  •  
  • Sun Storage 6780 Array
  •  
  • Sun Storage 6180 Array
  •  
  • Sun Storage 2530-M2 Array
  •  
  • Sun Storage 6540 Array
  •  
  • Sun Storage 6580 Array
  •  
  • Sun Storage 6140 Array
  •  
Related Categories
  • PLA-Support>Sun Systems>DISK>Arrays>SN-DK: FLX300_65xx_6780
  •  




In this Document
Goal
Solution
References


Applies to:

Sun Storage 2530-M2 Array - Version Not Applicable and later
Sun Storage 2540-M2 Array - Version Not Applicable and later
Sun Storage 6780 Array - Version All Versions and later
Sun Storage 6540 Array - Version All Versions and later
Sun Storage 6180 Array - Version All Versions and later
Information in this document applies to any platform.

Goal

 How to determine which host attached to the disk array initiated/requested the volume failover.

Solution

Additional information is collected in the Major Event Log (MEL) starting with controller firmware 07.60.xx.xx and higher.  Beginning with firmware 07.60.xx.xx it is very simple to determine the specific host that caused/requested the Automatic Volume Transfer (AVT) (failover from one controller to the alternate controller on the disk array) by looking at the raw data in the MEL of the AVT MEL event.  To perform this:

  1. Collect a support data bundle from the disk array.  (<Document 1002514.1> Collecting Sun Storage Common Array Manager Support Data for Arrays)
  2. After extracting the "zipped" support data bundle open the "majorEventLog.txt" file in a text editor.
  3. In the text editor you will need to search the MEL for event type 400E - Automatic volume transfer started. 
    Example below:
    Date/Time: Tue Apr 22 14:20:32 HST 2014
    Sequence number: 5002366
    Event type: 400E
    Event category: Notification
    Priority: Informational
    Description: Automatic volume transfer started
    Event specific codes: 0/0/0
    Component type: Controller
    Component location: Tray.85.Controller.B
    Logged by: Controller in slot B

    Raw data:

    4d 45 4c 48 03 00 00 00 7e 54 4c 00 00 00 00 00
    0e 40 48 00 50 07 57 53 00 00 00 00 00 00 00 00
    62 00 00 00 04 00 00 00 22 00 00 00 22 00 00 00
    08 00 00 00 55 00 00 00 02 00 00 00 01 00 00 00
    0a 00 00 00 01 00 00 00 00 00 00 00 00 00 00 00
    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
    01 00 00 00 00 00 01 01 0c 00 00 00 08 00 80 01
    10 00 00 00 c9 72 40 13 -> WWPN of HBA initiating failover

     
  4. Using the above 16 alpha-numeric digit World Wide Port Number (WWPN); you can find which host requested the failover by looking in the "Mappings" section of the storageArrayProfile.txt file of the support data bundle.
  5. Open the "storageArrayProfile.txt" file in a text editor.
  6. In the text editor you will need to search for the appropriate WWPN. 
    For this example search for "10000000c9724013":
Host Group: test-public-frontend
      Host: t5k70   -> the Host requesting failover
         Host Port WWN: 10000000C9724013
             Alias: t5k70a
             Type: SOLAVT
         Host Port WWN: 10000000C9723F86
             Alias: t5k70b
             Type: SOLAVT

 

 

References

<NOTE:1002514.1> - Collecting Sun Storage Common Array Manager Support Data for Arrays

Attachments
This solution has no attachment
  Copyright © 2018 Oracle, Inc.  All rights reserved.
 Feedback