IBM System Storage SAN Volume Controller Console
Readme for Windows 2003 & 2008
----------------------------------------------------------------
Contents
1.0 ABOUT THIS README FILE
1.1 Who should read this readme file
1.2 How to get help
1.3 Code Levels
1.4 Problems Resolved and New Features
2.0 CONTENTS OF THE SAN Volume Controller CONSOLE PACKAGE
3.0 LAST-MINUTE TECHNICAL UPDATES
4.0 PREREQUISITE FOR INSTALLING THE SAN Volume Controller CONSOLE
5.0 FREQUENTLY ASKED QUESTIIONS
6.0 NOTICES
---------------------------------------------------------------
1.0 ABOUT THIS README FILE
This readme file tells you where to obtain information
about the IBM(R) System Storage(TM) SAN Volume Controller
Console and how to get help. It also lists the contents of
the installation package for the Windows(R) host system.
This readme file particularly calls your attention to
the prerequisite for installing the SAN Volume Controller
Console. It also describes the last-minute technical updates,
if any.
1.1 Who should read this readme file
This readme file is intended for system administrators
who are familiar with the Windows environment
and will install and configure the SAN Volume Controller Console.
1.2 How to get help
* Administrative or nontechnical support:
1-877-426-6006 (Listen to voice prompts)
You can call this number if you have questions
about hardware or software orders, hardware
maintenance, services contracts of entitlement,
invoices, or commercial, state, or local support
operations.
* Business Partner Support Operations:
1-800-426-9990
* Federal Government Support Operations:
1-800-333-6705
1.3 Code Levels
Release Level 5.1.0.703
1.4 Problems Resolved and New Features
New features in this release (5.1.0.703):
* upgrade WAS to 6.1.0.31
APARs resolved in this release (5.1.0.703):
NONE
defects resolved in this release (5.1.0.703):
39688 User password display in plane txt in the trace log
---------------------------------------------------------------
2.0 CONTENTS OF THE SAN VOLUME CONTROLLER CONSOLE PACKAGE
temp - Temporary use, has synchronization file
console - Contains the web server, web pages related
executables
logs - Contains installation logs
_uninst - Contains uninstallation program
_jvm - Contains uninstaller Java virtual machine
---------------------------------------------------------------
3.0 LAST-MINUTE TECHNICAL UPDATES
1) IPv6 and IPv4 cluster management - customers should not run the
management console with the a single cluster added under both IPv4 and
IPv6 ip's. By default we do not allow this, but if the cluster is added
while it is unreachable or if the customer performs a forced create for
migration purposes this will be allowed
2) To migrate from pre-4.3.1 version, please uninstall the previous version
and install the 5.1.0 version directly.
3) Installer only supports windows 2003 and windows 2008
4) In order to install on Turkish version of Windows, the Launchpad can
not be used. setup.exe must be manually executed from the command line
with the -G checkPrerequisite=no parameter.
5) Install directory path must not contain characters that are not supported
by Websphere.
6) When migrating the installer will uninstall the current version. It may
be necessary to wait for three minutes after the uninstall to allow the
Websphere SOAP port to become free. Shutting down the Websphere application
prior to starting the upgrade is a proactive way to eliminate this concern.
7) Internet Explorer 7.0 users will need to add the SVC Console to the trusted
sites category of the security profile or warnings will occur.
8) Windows 2003 or 2008 and Internet Exporer 7.0 are required for IPv6.
9) This release supports Embedded CIMOM that comes installed and enabled as
part of the Cluster upgrade. The SVC Console is configured to use a HTTPS
connection to the cluster IP address, on the 5989 port, using the account
superuser and the password of the cluster admin user.
10) The user management of SAN Volume Controller Console is provided by single sign-on.
It enables single sign-on among different storage devices, including TPC.
Among that, Remote authentication is provided by Tivoli Embedded Security Services (ESS).
It integrate SVC with services like LDAP to provide central remote user management.
SVC console also has a local user management in parallel.
A remote user can have multiple roles in ESS. Those roles can be granted at the same time
to one user in the Command Line Interface mode. However, SVC Console defines user
roles in the different way as Command Line Interface. Roles are treated in the rank as follows:
"SecurityAdmin", "Administrator", "CopyOperator", "Service", "Monitor".
In SVC Console, a remote user can only own the highest role among those already defined in ESS.
For example, a remote user can have both "CopyOperator" and "Service" in ESS. He can own both
"CopyOperator" and "Service" roles when visiting Command Line Interface. But he can only
have "CopyOperator" role in SVC Console. In this case, he may lose the right as "Service"
in some operations when visiting SVC Console.
11) Putty installer is packaged here for your convenience.
12) The current SAN Volume Controller Console suppports IE 7.0 and firefox 3.0.x
and their earlier versions.
13) Using the SVC Console, you can add as many clusters as you wish. However each open cluster
and open panel, such as "Viewing Managed Disks" or "Viewing Virtual Disks", consumes memory
on the SVCC server in proportion to the number of mdisks or vdisks.
SVC Console uses a default Java heap size of 400 MB. This is enough memory to manage six clusters
simultaneously, each with 2048 vdisks and 1024 mdisks - 18K total objects.By increasing the heap
size to 800 MB, you can manage clusters with up to 36K total objects - six clusters with 4K vdisks
and 2K mdisks, or four clusters with 8K vdisks and 1K mdisks.
To increase the Java heap size, run setHeapSize.bat in
%ProgramFiles%\IBM\svcconsole\console\embeddedWAS\profiles\SVCProfile\bin, and restart the WebSphere
service "IBM WebSphere Application Server V6 - SVC".
On 32-bit Windows systems, the largest possible heap size is approximately 1600 MB. This is based
on the amount of contiguous memory address space that the operating system can allocate to a process.
If you set the heap size larger than 1600 MB, WebSphere may fail to start.
Note that setHeapSize.bat will only increase the size of the Java heap. If you need to reduce it,
use wsadmin. The following commands will return it to the default size.
Restart the WebSphere service to complete the configuration change.
wsadmin.bat -lang jython
jvm = AdminConfig.list("JavaVirtualMachine").split("\r\n")[0]
AdminConfig.modify(jvm, '[[maximumHeapSize 400]]')
AdminConfig.save()
---------------------------------------------------------------
4.0 PREREQUISITE FOR INSTALLING THE SAN VOLUME CONTROLLER CONSOLE
See the chapter 9 of the "IBM System Storage SAN Volume Controller
Software Installation and Configuration Guide" for detailed
instructions. You can find this Guide in the doc directory at
the root of the SAN Volume Controller Console installation CD-ROM.
---------------------------------------------------------------
5.0 FREQUENTLY ASKED QUESTIONS
1) How do I collect trace logs?
Collect the logs with the following command:
svcutil collectlogs
This will gather up all of the required trace logs and put them into a ZIP file in the current directory..
--------------------------------------------------------------
6.0 NOTICES & TRADMARKS
See notices.txt
--------------------------------------------------------------
(c) Copyright 2009 International Business Machines Corporation.
All rights reserved.
Note to U.S. Government Users Restricted Rights--Use duplication or
disclosure restricted by GSA ADP Schedule Contract with IBM Corp.