System information

Index
 173
The observed behavior is consistent with the way Clariion works. On Clariion, it is
possible to see the primordial pool with RemainingManagedSpace having a non-
zero value even though all disk drives are in use. In this situation, the value in the
RemainingManagedSpace represents a collection of "left-over", unusable, disk
capacities after the raid groups are created (i.e. concrete pools). For example,
let's assume there are two disk drives available in a Clariion, with the capacities
of 10 and 15 gigabytes. The client wishes to create a raid 1, raid group from
these two disk drives. Because both disk drives should have the same size, the
array uses the first disk drive with the capacity of 10 gigabytes and the first 10
gigabytes of the second disk drive. The remaining 5 gigabytes of the second disk
drive will remain unused and is reported as a part of the
RemainingManagedSpace capacity of the primordial pool.
One way to determine if all disk drives are in use is to examine the primordial
pool's " EMCRemainingRawCapacity " property. If this property contains 0, it
means all disk drives are in use by various concrete pools.
Q: EMC posted and End of Service Life for the Solutions Enabler and SMI-S
provider, what are the versions affected and the end of life dates?
A:
Product Version EOSL Date
SMI-S Provider 3.0 10/2008
SMI-S Provider 3.1 10/2009
SMI-S Provider 3.2 10/2010
Solutions Enabler 5.5.1 9/30/2008
Solutions Enabler 5.4 9/30/2008
Solutions Enabler 5.5 9/30/2008
Q: Not getting storage data and ‘tms’ command shows error ‘invalid pool
id’. Is this a known issue?
A: This happens when one or more pools use a really long name( longer than 32
chars). It is a known issue in provider versions upto 4.0.1.The work around is to
change the pool name to a shorter one.
Q: Why is Symmetrix not showing correct number hosts masked into
array?
A: Look at the symapi log file and look for following message: