Sun Storage 2540 Array
 
Sun Storage 2540-M2 Array
 
Sun Storage 2510 Array
 
Sun Storage 6180 Array
 
Sun Storage 6780 Array
 
Sun Storage 2530-M2 Array
 
Sun Storage 2530 Array
 
Sun Storage 6540 Array
 
Sun Storage 6580 Array
 
Sun Storage 6140 Array
 

PLA-Support>Sun Systems>DISK>Arrays>SN-DK: 6140_6180
 

In this Document

Symptoms

Cause

Solution

References

Created from <SR 3-9450125091>

Applies to:

Symptoms

During a firmware upgrade of a Sun Storage 2500, 2500-M2, or 6000 Array, Sun Storage Common Array Manager (CAM) may report the following error:

Cause

Usually, this indicates a communication issue between CAM and one or both of the array controllers. CAM sends commands to the controllers via RPC commands issued through the TCP/IP stack. Two conditions are required for proper communication between CAM and the array controllers:

• The controllers should be reachable. This can be verified using the ping command executed from the CAM server.
  
  
• The SYMbol server process must be running and optimal on each controller, so it can reply to the RPC commands.

There are situations where the SYMbol server might be in a hung state. In these types of cases, the controllers will respond to ping, but any command issued from CAM will fail to execute.

Solution

The following steps will resolve this error:

1. Use ping from your CAM server to validate the communication to both controllers:
   
   
   # ping <controller A IP>
   # ping <controller B IP>
   
   
   • If either controller does not respond, please refer to <Document 1008327.1> How to validate Sun Storage 6000, 2500 and Flexline Array Controller Out of Band Communication.
     
     
   • If both controllers respond to ping, continue to next step.
     
     
2. Collect a supportdata from your array. Refer to <Document 1002514.1> Collecting Sun Storage Common Array Manager Support Data for Arrays.
   
   
3. Extract the file stateCaptureData.dmp from the supportdata.
   
   
4. Execute the following command against the file extracted in step 3:
   
   
   # grep "no debug data is available" stateCaptureData.dmp
   
   
   
   • If you obtain the result "The client connection to Controller X is null, no debug data is available" (where X can either be A or B), please proceed to next step.
   • If you do not obtain the result "The client connection to Controller B is null, no debug data is available", please contact the Oracle support for further assistance.
     
     
5. The controller reported in the error "The client connection to Controller X is null" will need to be rebooted. CAM cannot communicate with this controller. With CAM 6.10 and higher, use the sscs command. This version of CAM has the capability to reboot a controller via its alternate by using sscs. The instructions to reboot the controller which is not responding are:
   
   
   • For CAM 6.9 and below:
     
     
     1. Fail the controller that is not responding by using the following command, which will execute the command via the alternate controller:
        
        
        # service -d <arrayname> -c fail -t <X>
        
        
        
        Where X is replaced by A or B, based on what you obtained in the above step 4.
        
        
        
        Where `service` is under:
        Solaris: /opt/SUNWsefms/bin/
        Linux:  /opt/sun/cam/private/fms/bin/
        Windows: C:\Program Files\Sun\Common Array Manager\Component\fms\bin\
        
        
        
     2. Wait 2 minutes.
        
        
     3. Revive the controller:
        
        
        # service -d <arrayname> -c revive -t <X>
        
          
        Where X is replaced by A or B, based on what you obtained in the above step 4.
          
        
        
     4. Wait 2 minutes.
        
        
        
   • For CAM 6.10 and higher:
     
     
     1. The sscs command can be used:
        
        
        # sscs reset -a <arrayname> controller <X>
        
        
        
        Where X is replaced by A or B, based on what you obtained in the above step 4.
        
        
        
        Where `sscs` is under:
        Solaris: /opt/SUNWstkcam/bin/
        Linux: /opt/sun/cam/bin/
        Windows: C:\Program Files\Sun\Common Array Manager\bin
        
        
        
6. Confirm that CAM is able to communicate with both controllers:
   
   
   # service -d <arrayname> -c contact
    
   
   
   • If either controller is not reachable, refer to <Document 1002514.1> Collecting Sun Storage Common Array Manager Support Data for Arrays to collect a supportdata and contact Oracle support for further assistance.
     
     
   • If both controllers are reachable, you can proceed with the firmware upgrade.
     
     

References

This solution has no attachment