| Asset ID: |
1-72-1361416.1 |
| Update Date: | 2012-04-17 |
| Keywords: | |
Solution Type
Problem Resolution Sure
Solution
1361416.1
:
Sun Storage Common Array Manager (CAM) reports events for profiles inserted or removed
| Related Items |
- Sun Storage Flexline 380 Array
- Sun Storage 6580 Array
- Sun Storage 2540-M2 Array
- Sun Storage 6180 Array
- Sun Storage 6130 Array
- Sun Storage 2540 Array
- Sun Storage 2510 Array
- Sun Storage 6540 Array
- Sun Storage 6780 Array
- Sun Storage 2530-M2 Array
- Sun Storage 2530 Array
- Sun Storage Common Array Manager (CAM)
- Sun Storage 6140 Array
|
| Related Categories |
- PLA-Support>Sun Systems>DISK>Disk Device Software>SN-DK: CAM
- .Old GCS Categories>Sun Microsystems>Storage Software>Modular Disk Device Software
|
In this Document
Applies to:
Sun Storage 6180 Array - Version Not Applicable to Not Applicable [Release N/A]
Sun Storage 2530-M2 Array - Version Not Applicable to Not Applicable [Release N/A]
Sun Storage 2540-M2 Array - Version Not Applicable to Not Applicable [Release N/A]
Sun Storage 6130 Array - Version Not Applicable to Not Applicable [Release N/A]
Sun Storage 2540 Array - Version Not Applicable to Not Applicable [Release N/A]
Information in this document applies to any platform.
Symptoms
Sun Storage Common Array Manager (CAM) raises one (or both) of the following events:
- Component <profile name> in system <arrayname> has been removed.
Event Code : xx.41.626
Event Type : <array model>.ComponentRemoveEvent.profile
Severity : 0
Probable Cause : The array has reported that a profile has been deleted.
This is usually caused by Administrative or Service Action.
Recommended Action : 1. Verify that this is the result of Administrative or Service Action.
2. Check for other Alarms that may be related.
- Component <profile name> added to <arrayname>.
Event Code : xx.40.626
Event Type : <array model>.ComponentInsertEvent.profile
Severity : 0
Probable Cause : A storage profile has been created.
Recommended Action : No action required.
Cause
These events indicate that a CAM profile was removed and/or added, they can have two different causes:
Cause 1
They are usually triggered in the environments that have more than one CAM server managing the same array that reports the event. If you are managing your array from only one CAM server, then you should move to the Cause 2 below.
The CAM profile data is saved in the private region in the array drives (also known as DACstore) and every version of CAM bundles a set of factory default profiles, for example CAM 6.5 has a number of factory default profiles which have been deprecated in CAM 6.8, hence those profiles no longer exist in CAM 6.8.
When an operation is performed that causes the DACstore to get updated, CAM will report component remove/insert events depending on the profiles associated with the installed version. So if two CAM servers at different levels (ie: 6.5 and 6.8) manages the same array, actions undertaken on the CAM 6.5 server will trigger the insert events, whereas actions undertaken on the CAM 6.8 server will trigger the remove events.
This is an expected behavior. See the solution 1 under the "Solution" section.
This behavior is also described in the <Bug:6998355> CAM6.8.0.6: Observing periodic Component Insert/Delete events of three Deprecated profiles.
Cause 2
These events can be triggered when CAM temporarily loses the connection with the array while retrieving the pool and profile information from the DACstore. You can look at the FMS logs below:
Solaris: /var/opt/SUNWsefms/log/fms.[0-9]
Windows: c:\program files\sun\common array manager\component\fms\var\log\fms.[0-9]
Linux: /var/opt/cam/log/fms.[0-9]
and if you have errors like the example below, for the time when the CAM profile was removed and/or inserted:
Sep 24, 2011 11:53:15 PM com.sun.netstorage.fm.storade.device.storage.treefrog.TreefrogReport createPoolsAndProfiles
WARNING: Error retrieving pool and profile information: devmgr.versioned.jrpc.RPCError: CONNECTION_LOST
this means that you are likely suffering from the <Bug:7068836> Spurious events of pools or profiles components removed and then added.
This bug is due to CAM not retrying the pool and profile collection from the array when sometimes we get a null connection to the array.
See the solution 2 under the "Solution" section.
Solution
Solution 1
The best practice and solution is to manage an array only from one CAM server. It is not recommended to manage the array from multiple CAM servers.
Solution 2
You can ignore these remove/insert events. A solution has been integrated in Sun Storage Common Array Manager 6.9 and later. Please refer <Document 1296274.1> How to Download Common Array Manager (CAM) Software and Patches.
Attachments
This solution has no attachment
