Installation guide

40 Book Title without trademarks, or an abbreviated book title • March 2008
Example –When you create a volume with 17.352GB under the standard “en” locale,
you can enter the size as 17.352 and select GB as unit. However, under the “de”
locale, the dot is interpreted as 1000-separator. A 17.352 size with a 1GB unit would
try to create a ~17 TB volume and likely fail with this error message: “The size
entered for the new volume exceeds the maximum space available on the selected
pool.”
Workaround –For GB and TB values you can multiply by 1024 and enter as MB or
GB.
Write Consistency Group Members Not All Consistent
Bug 6598844 –Members of a replication write consistency group should all have
matching attributes and roles.
Documentation Issues
CLI Command Changes for sscs map initiator and sscs map
snapshot
Bug 6599146 –Although the CLI command sscs map initiator is listed in the
CLI manpage, it is not implemented. And, although the CLI manpage lists the -i
option for use with the CLI commands sscs map volume and sscs map
initiator, this option is not yet implemented.
CLI - sscs modify firmware Command -p Option Requires the
File Path of the Firmware Image
The CLI Quick Reference Guide and the CLI manpage docs do not specify that when
using the -p option with the sscs modify firmware command, you must
supply the file path of the firmware image file.
CLI - sscs modify volume Command Correction
Bug 6592776 – The manpage for the CLI command sscs modify volume should
define the usage for the -c option, which enables you to select a controller, as
follows:
[ -c,--controller A | B ]