Sun System Handbook - ISO 3.4 June 2011 Internal/Partner Edition | |||
|
|
Solution Type Problem Resolution Sure Solution 1009430.1 : Sun StorEdge[TM] 3310/3510/3120/3511 Array: Monitoring from more than one host using Sun StorEdge[TM] Configuration Service can cause the controller to not respond
PreviouslyPublishedAs 213031 Symptoms When a Sun StorEdge[TM] 3310/3510/3511/3120 is monitored simultaneously by two hosts using Sun StorEdge[TM] Configuration Service, the servers can lose access to the storage array. Typical error seen in this case is: SUNWscsdMonitor[8072]: [ID 180924 daemon.error] [SUNWscsd 0x1060801: Critical] <rctrl4000> Unable to inquire Raid Controller. Chassis FRU Item: 370-5524-01 Serial No: 0046E9 HW Revision: 01 Description: Minnow BOX, RAID, LVD, Chassis+Bkpln Vendor JEDEC ID: 0x7F7F7F01 Date: Wed Sep 24 00:31:15 2003 {SN#0046e9} Resolution Array monitoring from multiple hosts is not supported. Make sure that the array is monitored from only one host. If it is monitored from both the hosts, you will typically see the SUNWscsdMonitoring messages logged in both the hosts. This can be achieved by stopping the agent using the following command: # /etc/init.d/ssagent stop Or by simply disabling the array monitoring in ssconsole which is the configuration GUI provided by the sscs package. If monitoring is required from both the hosts, monitor the array from one host using Sun StorEdge Configuration Service and the other host can monitor using the Sun StorEdge[TM] Diagnostic Reporter. Product Sun StorageTek 3511 SATA Array Sun StorageTek 3510 FC Array Sun StorageTek 3310 SCSI Array Sun StorageTek 3120 SCSI Array Internal Comments The following is strictly for the use of Sun employees: Service Request ID: 37339565 SSCS, 3310, 3510, 3511, 3120, monitoring Previously Published As 81284 Change History Date: 2006-01-19 User Name: 7058 Action: Update Canceled Comment: *** Restored Published Content *** SSH AUDIT Version: 0 Date: 2006-01-19 Attachments This solution has no attachment |
||||||||||||
|