ETERNUS SF Storage Cruiser Install Guide 13.2 - Solaris (TM) Operating System / Linux / Microsoft(R) Windows(R) -
Contents PreviousNext

Chapter 4 Manager installation and setup

The installation and setup of ETERNUS SF Storage Cruiser manager is described.


4.1 [Solaris OS] Manager

4.1.1 Operating environment 

4.1.1.1 Hardware requirements

The hardware listed below is required when using this software.

Section number

Operating server

Supported model

1

Admin server

All Sparc/SUN models


4.1.1.2 Software requirements

4.1.1.2.1 Required basic software

The basic software listed below is required when using this software.

Section number

Product name

Remarks

1

Solaris 8 OS

-

2

Solaris 9 OS

-

3

Solaris 10 OS

When using zone, install this software to the global zone.

Installation to the non-global zone is not possible.

4.1.1.2.2 Required software

The software listed below is required when using this software.

Section number

Product name

Version / Level

Remarks

1

PRIMECLUSTER Enterprise Edition

4.1A20 or later

Required when creating a cluster configuration with the admin server one of the software on the left.
The supported configuration is a standby class, in 1:1 standby mode.

2

PRIMECLUSTER HA Server

4.1A20 or later


4.1.1.2.3 Exclusive software

This software cannot be used in combination with the following software.

Section number

Product name

Version / Level

Remarks

1

Systemwalker Resource Coordinator

All

-

2

Softek Storage Cruiser

All

-

3

Server System Manager

V1.2.2 or less

-


4.1.1.2.4 Required patches

The patches listed below are required when using this software.

Section number

Product name

Patch ID

Remarks

1

Solaris 8 OS

Latest patch

-

2

Solaris 9 OS

Latest patch

-

3

Solaris 10 OS

Latest patch

-

4.1.1.2.5 Static disk space

For new installations, the following static disk space is necessary.

Section number

Directory

Required disk space
(Unit : MB)

Remarks

1

/etc

1

-

2

/var

2

-

3

/opt

300

-

4

/usr

1

-

4.1.1.2.6 Dynamic disk space

The required dynamic disk space is as below.

The following disk space is required for each directory, in addition to the static disk resources.

Section number

Directory

Required disk space
(Unit : MB)

Remarks

1

/etc

5 + 1(*A) + 1.2(*B)

*A: Configuration definition file
*B: Database (MW cooperation)

-> Calculated assuming 100 products at a maximum

2

/var

1055 + (*E) + 30(*C) + 20(*D)

*C: Log
*D: Database
*E : Repository for Manager

Calculated the space required for databases assuming 1000 servers and two devices for each (12KB * Number of registered servers + 4KB * Number of registered devices)

  1. Repository for manager

    For manager, the following amount of memory is required, depending on the numbers of managed storage modes, switches, and storage units.

    Amount of disk space (MB) = 1 + [Number of target units] * 4

    Additionally, when performance management is being performed, based on the fibre channel switch used to collect the performance information, the type of target (the ETERNUS/GR series), the number of logical units involved, the number of DE (Disk Enclosure), and the number of days for which information is to be collected, the required capacity given below becomes necessary.

    The default number of days for collection is seven. The number of secured LUs (Logical Units) is the actual number of LUs the functions of which are secured in order to perform performance management for the ETERNUS/GR series. Performance management is secured in units of 64 LUN for the ETERNUS/GR series. Therefore, when instructed to secure from LUN 15 to 200, the information for the actual LUs 0 to 255 (256 in total) would be secured.

    Units

    Required disk space
    (Unit : MB)

    ETERNUS8000 disk array

    (Number of days to collect+1) * (18000 + ( 90 + 0.4 * number of DE + 0.3 * number of secured LUs) * ( 86400 / Interval between performance monitoring (seconds) ) + ( 120 * number of DE ) + ( 50 * number of secured LUs )) / 1024

    ETERNUS6000 disk array

    (Number of days to collect+1) * (9.85 + (0.06 + 13.43 / performance monitoring interval (seconds)) * number of secured Lus[*] + 1956.45 / performance monitoring interval (seconds))

    * For ETERNUS6000 disk array device, it is counted as a total number of LUs (Logical Unit) targeted for performance monitoring..

    ETERNUS4000 disk array

    (Number of days to collect+1) * (5000 + ( 30 + 0.4 * number of DE + 0.3 * number of secured LUs) * ( 86400 / Interval between performance monitoring (seconds) ) + ( 120 * number of DE ) + ( 50 * number of secured LUs )) / 1024

    ETERNUS3000 disk array (except Model 80 and 100)

    (Number of days to collect+1) * ((0.06 + 11.61 / performance monitoring interval (seconds)) * number of secured LUs + 253.13 / performance monitoring interval (seconds) + 1.29)

    ETERNUS3000 Model 80 disk array

    ETERNUS3000 Model 100 disk array

    (Number of days to collect+1) * ((0.06 + 11.62 / performance monitoring interval (seconds)) * number of secured LUs + (38.73 / performance monitoring interval(seconds)) + 1.29)

    ETERNUS2000 disk array

    (Number of days to collect 1) * (140 + (0.7 + 0.2 * number of installed DE + 0.3 * number of secured LUs ) * (86400 / Interval between performance monitoring (seconds) + (60 * number of DE) + (50 * number of secured LUs ) ) / 1024

    ETERNUS GR740

    ETERNUS GR820

    ETERNUS GR840

    (Number of days to collect+1) * ((0.06 + 11.61 / performance monitoring interval (seconds)) * number of secured LUs + 341.95 / performance monitoring interval (seconds) + 1.67)

    ETERNUS GR720

    ETERNUS GR730

    (Number of days to collect+1) * ((0.06 + 11.62 / performance monitoring interval (seconds)) * number of secured LUs + 138.43 / performance monitoring interval (seconds) + 0.65)

    ETERNUS SN200 series Fibre Channel Switch

    (Maximum number of FC ports = 16 max.)

    PRIMERGY BX600 Fibre Channel Switch Blade

    PRIMERGY BX600 Fibre Channel Switch Blade(4Gbps)

    Brocade Fibre Channel Switch

    (Maximum number of FC ports = 16 max.)

    (Number of days to collect +1) * (30 / Interval between performance monitoring (seconds)) * 1.6

    ETERNUS SN200 series Fibre Channel Switch

    (Maximum number of FC ports = 32 max.)

    Brocade Fibre Channel Switch

    (Maximum number of FC ports = 32 max.)

    (Number of days to collect +1) * (30 / Interval between performance monitoring (seconds)) * 3.2

    ETERNUS SN200 series Fibre Channel Switch

    (Maximum number of FC ports = 128 max.)

    Brocade Fibre Channel Switch

    (Maximum number of FC ports = 128 max.)

    (Number of days to collect +1) * (30 / Interval between performance monitoring (seconds)) * 13

    ETERNUS SN200 series Fibre Channel Switch

    (Maximum number of FC ports = 256 max.)

    Brocade Fibre Channel Switch

    (Maximum number of FC ports = 256 max.)

    (Number of days to collect +1) * (30 / Interval between performance monitoring (seconds)) * 26

    ETERNUS SN200 series Fibre Channel Switch

    (Maximum number of FC ports = 384 max.)

    Brocade Fibre Channel Switch

    (Maximum number of FC ports = 384 max.)

    (Number of days to collect +1) * (30 / Interval between performance monitoring (seconds)) * 39

    ETERNUS SN200 MDS series Fibre Channel Switch

    (Number of days to collect +1) * 0.1 * Maximum number of slots supported by device (*) * 128 * (30 / Interval between performance monitoring (seconds))

    (*) Use 1 as the maximum number of slots for MDS9120


    For example, when securing the performance information of 512LUs on an ETERNUS3000 model 200, at 30 second intervals for 7 days,
    8 * (30 / 30) * 375 * 512 / 1024 = 1500MB is required.

4.1.1.2.7 Memory capacity

The minimum memory necessary for operation of this software is indicated.

Section number

Required memory (Unit : MB)

Remarks

1

200

-

4.1.1.2.8 Swap volume

The amount of swap volume used by this software is indicated.

Section number

Swap volume (Unit : MB)

Remarks

1

300

-

4.1.2 Advisory notes

++When Systemwalker Resource Coordinator, Softek Storage Cruiser or Server System Manager is already installed

++Post-installation advisory notes

After this software is installed, take care about the following.

This software can be used in the mixed environment with the following software. When these software are uninstalled, the SNMP Trap-monitoring daemon may be stopped.

When after above software are uninstalled from the mixed environment, restart the system or execute the following.

  1. Check if nwsnmp-trapd is running with the ps command.

    # /bin/ps -ef | grep nwsnmp-trapd <RETURN>

  2. If nwsnmp-trapd is not running, execute the following commands.

    # /opt/FJSVswstt/bin/mpnm-trapd stop <RETURN>

    # /opt/FJSVswstt/bin/mpnm-trapd start <RETURN>

4.1.3 Installation procedure

The procedure for manager installation is given below.
The ETERNUS SF Storage Cruiser CD-ROM for manager client program is used for manager installation.


4.1.3.1 Pre-installation preparations

  1. Local file system checking (for the single user mode)

    Please install this product in multi-user mode.
    When installation is performed in single-user mode, please check that mounting of the local file system has been performed before installing. If it has not been performed, please perform mounting of the local file system.

    An example is given below.

    <Example>

    # /usr/sbin/mountall -l <RETURN>


    Please refer to the OS manual for details of the mount command.


  2. Software installation checking

    Check that required software has been installed and that exclusive software and this software have not been installed.
    Insert the manager client program CD-ROM into the CD-ROM drive, and execute the following command.

    # cd CD-ROM_mount_point/manager/Solaris <RETURN>
    # ./scinstall.sh -check <RETURN>

    In the event that the message is output as a result of the above operation, take action as follows.

4.1.3.2 Installation time 

Installation time for this software is around ten minutes.


4.1.3.3 Software installation

By executing this software's exclusive installation command (scinstall.sh), multiple packages can be installed simultaneously. The scinstall.sh command invokes the pkgadd(1M) command and installs the component program packages.

  1. Login as the super user (root) by the following command.

    # su <RETURN>

  2. After performing the procedures in "4.1.3.1 Pre-installation preparations", move to the directory storing this software's exclusive installation command "scinstall.sh" (CD-ROM_mount_point/manager/Solaris).

    # cd CD-ROM_mount_point/manager/Solaris <RETURN>


  3. Execute the scinstall.sh command.

    # ./scinstall.sh <RETURN>

    ETERNUS SF Storage Cruiser 13.2
    All Rights Reserved, Copyright(c) FUJITSU LIMITED 2006-2007
    This program will install "ETERNUS SF Storage Cruiser" Manager on your system.


    Do you want to continue the installation of this package? [y, n, ?, q]


  4. To execute installation enter "y", to discontinue the installation enter a different character.

    Do you want to continue the installation of this package? [y, n, ?, q]


  5. Enter "y" and the installation will commence.

    An example of the displayed information is given below.

    <Example>

    INFO : Starting Installation of ETERNUS SF Storage Cruiser ...
    ...
    Installation of <FJSVswstt> was successful.
    INFO : Package FJSVswstt was successfully installed.
    ...

    Installation of <FJSVtrccb> was successful.
    INFO : Package FJSVtrccb was successfully installed.
    ...
    Installation of <FJSVssmgr> was successful.
    INFO : Package FJSVssmgr was successfully installed.
    ...


  6. When installation is completed normally, the following message will be displayed.

    INFO : "ETERNUS SF Storage Cruiser" Manager was installed successfully.

    If there is an error during installation, one of the following messages will be displayed.

    ERROR : Required package_name is not installed.
    or
    ERROR : Exclusive package "software_name" is installed.
    or
    ERROR : Package package_name is already installed.
    or
    ERROR : Installing package_name was failed.


  7. In the event that the installation fails, check the install status using the following command.

    # ./scinstall.sh -check <RETURN>

    In cases where the same versions of packages have been installed, delete all packages that have been identified by the above command using the scinstall.sh command. Then recommence the installation process from Item 3.

    scuninstall.sh is stored in "CD-ROM_mount_point/manager/Solaris".

    # cd CD-ROM_mount_point/manager/Solaris <RETURN>
    # ./scuninstall.sh <RETURN>

    If installation fails even then, please note down the output message and contact Fujitsu technical staff.

  8. Post-installation setup


4.1.4 Post-installation setup

The procedure for manager setup is given below.


When the Operation control server is a cluster system, refer to "A.4 Manager Operation Setup" for the procedure.

4.1.4.1 /etc/services configuration

For operation of manager, the following port numbers are necessary for transmissions with manager, clients, and agents.

Include the following details in the /etc/services file, and declare usage of the port number.

When a port number is already in use, please specify a vacant port number. In this case, with regards to all other ETERNUS SF Storage Cruiser servers with the same port number configuration, perform the same configuration changes.

In situations where there is no description in the /etc/services file, booting will be from the following port numbers.

"/etc/services file configuration details"

# service name  port number/protocol name
sscruisera      4917/tcp
nfport          23456/tcp
ssvscme       7420/tcp
ssvscme       7420/udp


The relationship of service name and port number, protocol name, sender, receiver is given below.

Service name

Port number / Protocol name

Sender

Receiver

sscruisera

4917/tcp

Manager

Agent

nfport

23456/tcp

Manager

Client

ssvscme

7420/tcp
7420/udp

Manager

Virtualization switch


4.1.4.2 Administrator login account creation

  1. Login as the administrator (root) and execute the following command.

    # /opt/FJSVssmgr/bin/scsetup <RETURN>

  2. Administrator login account creation

    Create the administrator's login account and perform creation of a CLI encryption key.

  3. When installation is completed normally, the following message will be displayed.

    FJSVrcx:INFO:27801:rcxcert:The command was successfully completed.

    If there is an error during installation, one of the following messages will be displayed.

    ERROR : Database update failed.
    or
    FJSVrcx:ERROR:67806:rcxcert:rcxcert setup has already been completed.

    FJSVrcx:ERROR:67808:rcxcert:The command was not completed successfully.
    or
    ERROR: "scsetup" command can not be executed except for " ETERNUS SF Storage Cruiser" Manager. Please create administrative login account manually.

     

  4. If administrator login account creation failed, please confirm the following content.

    If installation fails even then, please note down the output message and contact Fujitsu technical staff.

4.1.4.3 Rebooting the system

Reboot the system after finishing configuration. ETERNUS SF Storage Cruiser will boot automatically.

# /usr/sbin/shutdown -y -g0 -i6 <RETURN>

4.1.5 Upgrading from older products 

When a previous version level of the Softek Storage Cruiser administrative server or the ETERNUS SF Storage Cruiser operation control server has been installed, you can save the setting data and have the current version of ETERNUS SF Storage Cruiser administrative server inherit the saved data.

4.1.5.1 Upgrading from Softek Storage Cruiser 

See "Appendix D Procedure for Upgrading from Softek Storage Cruiser".

4.1.5.2 Upgrading from a previous version level 

This section explains how to upgrade from a previous version level of ETERNUS SF Storage Cruiser.

4.1.5.2.1 Upgrading from a previous version level (non-cluster environment)

  1. Back up the setting data of the previous version level of ETERNUS SF Storage Cruiser Manager.

    Refer to "9.1.1.2.1 Backing up Solaris Manager" in the "ETERNUS SF Storage Cruiser User's Guide" for how to perform backup.

  2. Uninstall the previous version level of ETERNUS SF Storage Cruiser Manager.

    To uninstall the Manager, refer to " 9.1 [Solaris] Manager uninstallation" in the "ETERNUS SF Storage Cruiser Install Guide" for the previous version level.

  3. Install the ETERNUS SF Storage Cruiser Manager.

    Refer to " 4.1 [Solaris OS] Manager " in the "ETERNUS SF Storage Cruiser Install Guide" for how to install and set up the Manager.

  4. Restore the setting data of the previous version level of ETERNUS SF Storage Cruiser Manager.

    Refer to "9.1.1.3.1 Restoring Solaris Manager" in the "ETERNUS SF Storage Cruiser User's Guide" for how to restore backup data that was created according to the procedure described in Item 1.

  5. Update the configuration information of the performance management function.

    <When migrating from ETERNUS SF Storage Cruiser13.0>

    When the performance management function is used for devices that meet the following conditions, start the Manager, then update the configuration information of those devices by referring to "7.2.11 Updating configuration information" in the "ETERNUS SF Storage Cruiser User's Guide".

    Device

    Firmware version

    ETERNUS3000 (M80,M100)

    V20L85 orlater, or V30L15 or later

    ETERNUS4000 (M80,M100)

    V30L15 or later

    ETERNUS8000, ETERNUS4000 (excl.M80,M100)

    V10L50 or later


4.1.5.2.2 Upgrading from a previous version level (cluster environment)

  1. Back up the setting data of the previous version level of ETERNUS SF Storage Cruiser Manager.

    Refer to "9.1.1.2.2 Backing up Solaris Manager (Cluster environment)" in the "ETERNUS SF Storage Cruiser User's Guide" for how to perform backup.

  2. Uninstall the previous version level of ETERNUS SF Storage Cruiser Manager.

    To uninstall the Manager, refer to "Appendix A High-availability admin servers " in the "ETERNUS SF Storage Cruiser Install Guide" for the previous version level.

  3. Install the ETERNUS SF Storage Cruiser Manager.

    Refer to "Appendix A High-availability admin servers" in the "ETERNUS SF Storage Cruiser Install Guide" for how to install and set up the Manager.

  4. Restore the setting data of the previous version level of ETERNUS SF Storage Cruiser Manager.

    Refer to "9.1.1.3.2 Restoring the Solaris Manager (Cluster environment)" in the "ETERNUS SF Storage Cruiser User's Guide" for how to restore backup data that was created according to the procedure described in Item 1.

  5. Update the configuration information of the performance management function.

    <When migrating from ETERNUS SF Storage Cruiser13.0>

    When the performance management function is used for devices that meet the following conditions, start the Manager, then update the configuration information of those devices by referring to "7.2.11 Updating configuration information" in the "ETERNUS SF Storage Cruiser User's Guide".

    Devices

    Firmware version/level

    ETERNUS3000 (M80,M100)

    V20L85 orlater, or V30L15 or later

    ETERNUS4000 (M80,M100)

    V30L15 or later

    ETERNUS8000, ETERNUS4000 (excl.M80,M100)

    V10L50 or later

4.2 [Linux] Manager  


4.2.1 Operation environment  


4.2.1.1 Hardware requirements 

The hardware listed below is required when using this software.

Section number

Operation server

Supported model

1

Operation control server

Over 512MB memory and CPU is Pentium(R)III 1.2GHz or better

2

PRIMEQUEST

3

PRIMERGY


4.2.1.2 Software requirements  


4.2.1.2.1 Required basic software

The basic software listed below is required when using this software.

Section number

Product name

Remarks

1

Red Hat Enterprise Linux 5 (for x86)

Modified kernel is required. Obtain a modified kernel and create a modified kernel update CD. Essential software such as driver kit and update kit also need to be prepared, if any. Refer to server instruction manuals or Linux installation guide for essential software information.

In addition, if any virtual machine is being used, install this software to the host operating system. If installed to a guest operating system, it does not work properly.

2

Red Hat Enterprise Linux 5 (for Intel Itanium)

Operation server is only PRIMEQUEST

In addition, if any virtual machine is being used, install

this software to the host operating system. If installed to a guest operating system, it does not work properly.

4.2.1.2.2 Required software

The required software listed below is required when using this product.

Section number

Product name

Version / Level

Remarks

1

PRIMECLUSTER Enterprise Edition

4.2A30 or later

Either one of the two software is required when a cluster is configured by the Admin Server.

Support type is "Standby class1:1 Operation standby type.

2

PRIMECLUSTER HA Server

4.2A30 or later

 

4.2.1.2.3 Exclusive software

There are no Exclusive software.

4.2.1.2.4 Required batches

The required batches listed below are required when using this product.

Section number

Product name

Batch ID

Remarks

1

Red Hat Enterprise Linux 5 (for x86)

None

-

2

Red Hat Enterprise Linux 5 (for Intel Itanium)

None

-

4.2.1.2.5 Static disk space

For new installations, the following static disk space is required.

Section number

Decretory

Required disk space (Unit : MB)

Remarks

1

/etc

1

-

2

/var

2

-

3

/opt

300

-

4

/usr

1

-

 

4.2.1.2.6 Dynamic disk space

The required dynamic disk space is as below.
The following disk space is required for each directory, in addition to the static disk resources.

Section number

Directory

Required disk space (Unit : MB)

Remarks

1

/etc

5 + 1(*A) + 1.2(*B)

*A : Environment definition file
*B : Database (MW link)

Calculated the space required for databases assuming 100 products

2

/var

1055 + (*E) + 30(*C) + 20(*D)

*C : Log
*D : Database
*E : Repository for manager

Calculated the space required for databases assuming 1000 servers and two devices for each (12KB * Number of registered servers + 4KB * Number of registered devices)

  1. Repository for manager

    For manager, the following amount of memory is required, depending on the numbers of managed storage modes, switches, and storage units.

    Amount of disk space (MB) = 1 + [Number of target units] * 4

    Additionally, when performance management is being performed, based on the fibre channel switch used to collect the performance information, the type of target (the ETERNUS/GR series), the number of logical units involved, the number of DE (Disk Enclosure), and the number of days for which information is to be collected, the required capacity given below becomes necessary.

    The default number of days for collection is seven. The number of secured LUs (Logical Units) is the actual number of LUs the functions of which are secured in order to perform performance management for the ETERNUS/GR series. Performance management is secured in units of 64 LUN for the ETERNUS/GR series. Therefore, when instructed to secure from LUN 15 to 200, the information for the actual LUs 0 to 255 (256 in total) would be secured.

    Device

    Required disk space (Unit : MB)

    ETERNUS8000 disk array

    (Number of days to collect +1) * (18000 + (90 + 0.4 * number of installed DE + 0.3 * number of secured LUs) * (86400 / Interval between performance monitoring (seconds)) + (120 * number of installed DE) + (50 * number of secured LUs) ) /1024

    ETERNUS6000 disk array

    (Number of days to collect;+1) * (9.85 + (0.06 + 13.43 / performance monitoring interval (seconds)) * number of secured LUs [*] + 1956.45 / performance monitoring interval (seconds)

    * For ETERNUS6000 disk array, it is counted as a total number of LUs (Logical Unit) targeted for performance monitoring.

    ETERNUS4000 disk array

    (Number of days to collect +1) * (5000 + (30 + 0.4 * number of installed DE + 0.3 * number of secured LUs) * (86400 / Interval between performance monitoring (seconds)) + (120 * number of installed DE) + (50 * number of secured LUs) ) /1024

    ETERNUS3000 disk array (except Models 80 and 100)

    (Number of days to collect+1) * ((0.06 + 11.61 / performance monitoring interval (seconds)) * number of secured LUs + 253.13 / performance monitoring interval (seconds) + 1.29)

    ETERNUS3000 disk array model 80

    ETERNUS3000 disk array model 100

    (Number of days to collect+1) * ((0.06 + 11.62 / performance monitoring interval (seconds)) * number of secured LUs + (38.73 / performance monitoring intervals (seconds)) + 1.29)

    ETERNUS2000 disk array

    (Number of days to collect +1) * (140 + (0.7 + 0.2 * number of installed DE + 0.3 * number of secured LUs) * (86400 / Interval between performance monitoring (seconds)) + (60 * number of installed DE) + (50 * number of secured LUs) ) / 1024

    ETERNUS GR740

    ETERNUS GR820

    ETERNUS GR840

    (Number of days to collect+1) * ((0.06 + 11.61 / performance monitoring interval (seconds)) * number of secured LUs + 341.95 / performance monitoring interval (seconds) + 1.67)

    ETERNUS GR720

    ETERNUS GR730

    (Number of days to collect+1) * ((0.06 + 11.62 / performance monitoring interval (seconds)) * number of secured LUs + 138.43 / performance monitoring interval (seconds) + 0.65)

    ETERNUS SN200 series fiber channel switch

    (Maximum number of FC ports = 16)

    PRIMERGY BX600 fiber channel switch blade

    PRIMERGY BX600 fiber channel switch blade(4Gbps)

    Brocade fiber channel switch

    (Maximum number of FC port = 16)

    		 (Number of days to collect +1) * (30 / Interval between performance monitoring (seconds)) * 1.6

    ETERNUS SN200 series fiber channel switch

    (Maximum number of FC port = 32)

    Brocade fiber channel switch

    (Maximum number of FC port = 32)

    		 (Number of days to collect +1) * (30 / Interval between performance monitoring (seconds)) * 3.2

    ETERNUS SN200 series fiber channel switch

    (Maximum number of FC port = 128)

    Brocade fiber channel switch

    (Maximum number of FC port = 128)

    		 (Number of days to collect +1) * (30 / Interval between performance monitoring (seconds)) * 13

    ETERNUS SN200 series fiber channel switch

    (Maximum number of FC port = 256)

    Brocade fiber channel switch

    (Maximum number of FC port = 256)

    		 (Number of days to collect +1) * (30 / Interval between performance monitoring (seconds)) * 26

    ETERNUS SN200 series fiber channel switch

    (Maximum number of FC port = 384)

    Brocade fiber channel switch

    (Maximum number of FC port = 384)

    		 (Number of days to collect +1) * (30 / Interval between performance monitoring (seconds)) * 39

    ETERNUS SN200 MDS series fiber channel switch

    (Number of days to collect +1) * 0.1 * Maximum number of slots that the devise can support (*1) * 128 * (30 / Interval between performance monitoring (seconds))

    *1 USE 1 AS THE MAXIMUM NUMBER OF SLOTS FOR MDS9120.

    For example, when securing the performance information of 512LUs on an ETERNUS 3000 model 200, at 30 second intervals for 7 days.

    8 * (30 / 30) * 375 * 512 / 1024 = 1500MB will be.


4.2.1.2.7 Memory capacity

The minimum memory required for operation of this software is indicated.

Section number

Required memory (Unit : MB)

Remarks

1

200

-

 

4.2.1.2.8 Swap volume

The minimum swap required for operation of this software is indicated.

Section number

Swap volume (Unit: MB)

Remarks

1

300

-

 

4.2.2 Advisory notes 

+SNMP trap daemon

On servers operating managers, the standard Linux SNMP trap daemon cannot be used.
Also applications that use the SNMP trap daemon cannot be used.

When "PRIMERGY server management software ServerView for Linux" is already installed, caution is necessary regarding AlarmService.
When not using AlarmService, uninstall it following the procedure below.
When using AlarmService, the ServerView trap transfer program (trpsrvd) is required.
For details, refer to "ServerView trap transfer program (trpsrvd)".

Uninstall AlarmService using the following procedure.

  1. Redefinition of ServerView alarm settings

    When alarm configuration has been performed on a ServerView Linux Agent, redefine the setting definitions for each server on the ServerView console.


    For details of the methods for defining alarm settings, refer to the ServerView documentation.

  2. Addition and change of ServerView Linux SNMP trap destinations

    When using ServerView alarm settings, configure the ServerView console as the SNMP trap destination.


    For details of the methods for adding or changing ServerView Linux SNMP trap receivers, refer to the ServerView documentation.

  3. Uninstallation of AlarmService

    Uninstall the "AlarmService" of ServerView on Linux servers.
    On Linux servers on which ServerView is operating, execute the following command.

    # rpm -e AlarmService <RETURN>

Applications other than AlarmService, that use the standard Linux SNMP trap daemon must be uninstalled or have their settings changed to prevent them from operating.

When the standard Linux SNMP trap daemon is configured to start automatically, change the configuration to prevent it from starting automatically.

Prevent the SNMP trap daemon from starting automatically using the following procedure.

  1. Log in as a super user and execute the following command.

    # /usr/sbin/setup <RETURN>

    (The setup command is only for Red Hat)
    A menu window will be displayed.

  2. Select "System service", and press the Enter key.

    The service window will be displayed.

  3. Remove the "*" from the "snmptrapd" parameter.

    To remove the "*", align the cursor with the parameter and press the Space key.

  4. Use the Tab key to align the cursor with "OK", and press the Enter key.

  5. Use the Tab key to align the cursor with "Cancel", and press the Enter key.

    Setup is complete.

     

+ServerView trap transfer program (trpsrvd)

When using ServerView AlarmService on servers that manager has been installed on, the ServerView trap transfer program (trpsrvd) for transferring SNMP Trap is required.
The ServerView trap transfer program (trpsrvd) is used to transfer SNMP Traps received at UDP port number 162 to other UDP port numbers.

To obtain the ServerView trap transfer program (trpsrvd), contact Fujitsu technical staff. For details of installation methods, refer to the attached Readme.

+Post-installation advisory notes

After this software is installed, take care about the following.

This software can be used in the mixed environment with the following software. When these software are uninstalled, the SNMP Trap-monitoring daemon may be stopped.

When after above software are uninstalled from the mixed environment, restart the system or execute the following.

  1. Check if nwsnmp-trapd is running with the ps command.

    # /bin/ps -ef | grep nwsnmp-trapd <RETURN>

  2. If nwsnmp-trapd is not running, execute the following commands.

    In the PRIMEQUEST environment:

    # /etc/init.d/sw-trapd restart <RETURN>

    In other environment:

    # /opt/FJSVswstt/bin/mpnm-trapd stop <RETURN>

    # /opt/FJSVswstt/bin/mpnm-trapd start <RETURN>

4.2.3 To obtain the ServerView trap transfer program (trpsrvd), contact Fujitsu technical staff. For details of installation methods, refer to the attached Readme.Installation procedure  

Procedure to install the Manager is described below.
ETERNUS SF Storage Cruiser manager client program CD-ROM is used for installing the Manager.


4.2.3.1 Pre-installation preparation

  1. Check if a local file system is mounted (in the case of a single user mode)

    This product must be installed on a multiple user mode.
    When this product is installed on a single user mode, check if a local file system is mounted before installation. If not installed, mount a local file system.

    An example is shown below.

    <Example>

    # /usr/sbin/mountall -l <RETURN>


    Refer to Operation System manual for mount command details.

  2. Check if basic software is installed

    Make sure that the basic software is installed and this software is not installed.

    Set up an ETERNUS SF Storage Cruiser CD-ROM and then execute the command below:

    # cd CD-ROM mount point /manager/RHEL <RETURN>
    # /bin/sh ./scinstall.sh -check <RETURN>

    When a message is displayed after executing the above command, take a relevant measure accordingly.

4.2.3.2 Installation time 

Installation time for this software is around ten minutes.

4.2.3.3 Software installation 

By executing this software's exclusive installation command (scinstall.sh), multiple packages can be installed simultaneously. The scinstall.sh command calls the rpm(8) command and installs the configuration program package.

  1. Login with root (superuser)

    # su <RETURN>

     

  2. After performing the procedures in "4.2.3.1 Pre-installation preparation", move to the directory (CD-ROM Mountpoint/manager/RHEL) where this software's exclusive install command is stored.

    # cd CD-ROM Mountpoint/manager/RHEL <RETURN>

     

  3. Execute the scinstall.sh command

    # /bin/sh ./scinstall.sh <RETURN>

    ETERNUS SF Storage Cruiser 13.2
    All Rights Reserved, Copyright(c) FUJITSU LIMITED 2006-2007
    This program will install "ETERNUS SF Storage Cruiser" Manager on your system.


    Do you want to continue the installation of this package? [y, n, ?, q]

     

  4. To continue to install the package, enter "y", to discontinue the installation enter a different character.

    Do you want to continue the installation of this package? [y, n, ?, q]

     

  5. When "y" is entered, the installation will commence.

    Message examples are as follows:

    <Example>

    INFO : Starting Installation of ETERNUS SF Storage Cruiser ...

    INFO : Package FJSVswstt was successfully installed.

    INFO : Package FJSVtrccb was successfully installed.

    INFO : Package FJSVssmgr was successfully installed.

     

  6. When the installation is successful, the following message will be displayed.

    INFO : "ETERNUS SF Storage Cruiser" Manager was installed successfully.

    If the installation fails, the following messages will be displayed.

    ERROR : Required Package name is not installed.
    or
    ERROR : Exclusive package "Software name" is installed.
    or
    ERROR : Package Package name is already installed.
    orERROR : Installing Package name was failed.

     

  7. If the installation fails, check the installation status with the following command.

    # /bin/sh ./scinstall.sh -check <RETURN>

    In cases where the same versions of packages have been installed, delete all packages that have been identified by the above command, using the scinstall.sh command. Then recommence the installation process from Item 3.

    scuninstall.sh is stored in "CD-ROM Mountpoint/manager/RHEL"

    # cd CD-ROM Mountpoint/manager/RHEL <RETURN>
    # /bin/sh ./scuninstall.sh <RETURN>

    When the installation failed even if the above procedure was taken, take note of the message displayed and contact Fujitsu technical engineer.

  8. Post-installation setup

4.2.4 Post-installation setup

Procedure to setup the Manager is described below.

When the operating control server is a cluster system, refer to "A4 Manager operation setup" for the execution of this procedure.

4.2.4.1 /etc/services configuration

Manager operation requires port numbers below to enable it to communicate with a client or an agent.

Write the contents below in the /etc/services file and declare the use of a port number.

When a port number is already occupied by another, select an available port and then change the port. In this case, the settings for another server of ETERNUS SF Storage Cruiser, if using the same port number, should also be changed.

When the /etc/services is not setup, restart will take place with the port numbers below:

[/etc/services file settings contents

#Service name Port number/Protocol name

sscruisera 4917/tcp

nfport 23456/tcp

ssvscme 7420/tcp

ssvscme 7420/udp

The relationship amongst service name, port number, protocol name, and connection source and connection destination is described below:

Service name

Port number/Protocol name

Connection source

Connection destination

sscruisera

4917/tcp

Manager

Agent

nfport

23456/tcp

Manager

Client

ssvscme

7420/tcp
7420/udp

Manager

Virtual switch

4.2.4.2 Administrator login account creation

  1. Login with the operating system administrator (root), and execute the command below:

    # /opt/FJSVssmgr/bin/scsetup <RETURN>

  2. How to create an administrative login account

    This explains how to create an administrative login account for the operation control server and a CLI encryption key.

  3. When a login account is successfully created, the following message will be displayed.

    FJSVrcx:INFO:27801:rcxcert:The command was successfully completed.

    If failed, the following message will be displayed.

    ERROR : Database update failed.
    or
    FJSVrcx:ERROR:67806:rcxcert:rcxcert setup has already been completed.

    FJSVrcx:ERROR:67808:rcxcert:The command was not completed successfully.
    or
    ERROR: "scsetup" command can not be executed except for "ETERNUS SF Storage Cruiser" Manager. Please create administrative login account manually.

     

  4. When the creation of administrative login account failed, check the status as below.

    If the creation of administrative login account still failed, collect the displayed message and contact Fujitsu System Engineer.

4.2.4.3 Rebooting the system

The system should be restarted upon completion of the settings. ETERNUS SF Storage Cruiser will start automatically.

# /sbin/shutdown -r now <RETURN>

4.3 [Windows] Manager

4.3.1 Operating environment 

4.3.1.1 Hardware requirements

The hardware listed below is required when using this software.

Section number

Operating server

Supported model

1

Admin server

Over 512MB memory and CPU is Pentium (R) III 1.2GHz or better


4.3.1.2 Software requirements

4.3.1.2.1 Required basic software

The basic software listed below is required when using this software.

Section number

Product name

Remarks

1

Windows Server 2003 R2, Standard Edition

includes SP2

2

Windows Server 2003 R2, Enterprise Edition

includes SP2

3

Windows Server 2003, Standard Edition

includes SP1, SP2

4

Windows Server 2003, Enterprise Edition

includes SP1, SP2

5

Windows 2000 Server (SP1 or later version)

-

6

Windows 2000 Advanced Server (SP1 or later version)

-

7

Windows 2000 Professional (SP1 or later version)

-


4.3.1.2.2 Required software

None.

4.3.1.2.3 Exclusive software

This software cannot be used in combination with the following software.

Section number

Product name

Version / Level

Remarks

1

Systemwalker Resource Coordinator

All

Excluding Systemwalker Resource Coordinator Virtual server Edition

2

Systemwalker/StorageMGR

All

-

3

Softek Storage Cruiser

All

-

4

Softek SANView

All

-

 

4.3.1.2.4 Static disk space

For new installations, the following static disk space is required.

Section number

Directory

Required disk space (Unit : MB)

Remarks

1

\$DIR1(*1)

300

-

2

\$DIR2(*2)

1

-

3

\$DIR3(*3)

2

-

4.3.1.2.5 Dynamic disk space

The required dynamic disk space is as below.
The following disk space is required for each directory, in addition to the static disk resources.

Section number

Directory

Required disk space (Unit : MB)

Remarks

1

\$DIR2(*2)

5 + 1(*A) + 1.2(*B)

*A: Configuration definition file
*B: Database (MW cooperation)

-> Calculated assuming 100 products at a maximum

2

\$DIR3(*3)

1055 + (*E) + 30(*C) + 20(*D)

*C: Log
*D: Database
*E: Repository for Manager :

Calculated the space required for databases assuming 1000 servers and two devices for each (12KB * Number of registered servers + 4KB * Number of registered devices)

  1. Repository for manager

    For manager, the following amount of memory is required, depending on the numbers of managed storage modes, switches, and storage units.

    Amount of disk space (MB) = 1 + [Number of target units] * 4

    Additionally, when performance management is being performed, based on the fibre channel switch used to collect the performance information, the type of target (the ETERNUS/GR series), the number of logical units involved, the number of DE (Disk Enclosure), and the number of days for which information is to be collected, the required capacity given below becomes necessary.

    The default number of days for collection is seven. The number of secured LUs (Logical Units) is the actual number of LUs the functions of which are secured in order to perform performance management for the ETERNUS/GR series. Performance management is secured in units of 64 LUN for the ETERNUS/GR series. Therefore, when instructed to secure from LUN 15 to 200, the information for the actual LUs 0 to 255 (256 in total) would be secured.

    Units

    Required disk space
    (Unit : MB)

    ETERNUS8000 disk array

    (Number of days to collect+1) * (18000 + ( 90 + 0.4 * number of DE + 0.3 * number of secured LUs) * ( 86400 / Interval between performance monitoring (seconds) ) + ( 120 * number of DE ) + ( 50 * number of secured LUs )) / 1024

    ETERNUS6000 disk array

    (Number of days to collect+1) * (9.85 + (0.06 + 13.43 / performance monitoring interval (seconds)) * number of secured LUs [*] + 1956.45 / performance monitoring interval (seconds))

    * For ETERNUS6000 disk array device, it is counted as a total number of LUs (Logical Unit) targeted for performance monitoring.

    ETERNUS4000 disk array

    (Number of days to collect+1) * (5000 + ( 30 + 0.4 * number of DE + 0.3 * number of secured LUs) * ( 86400 / Interval between performance monitoring (seconds) ) + ( 120 * number of DE ) + ( 50 * number of secured LUs )) / 1024

    ETERNUS3000 disk array (except Models 80 and 100)

    (Number of days to collect+1) * ((0.06 + 11.61 / performance monitoring interval (seconds)) * number of secured LUs + 253.13 / performance monitoring interval (seconds) + 1.29)

    ETERNUS3000 Model 80 disk array

    ETERNUS3000 Model 100 disk array

    (Number of days to collect+1) * ((0.06 + 11.62 / performance monitoring interval (seconds)) * number of secured LUs + (38.73 / performance monitoring interval (seconds)) + 1.29)

    ETERNUS2000 disk array

    (Number of days to collect +1) * (140 + (0.7 + 0.2 * number of installed DE + 0.3 * number of secured LUs) * (86400 / Interval between performance monitoring (seconds)) + (60 * number of installed DE) + (50 * number of secured LUs) ) / 1024

    ETERNUS GR740

    ETERNUS GR820

    ETERNUS GR840

    (Number of days to collect+1) * ((0.06 + 11.61 / performance monitoring interval (seconds)) * number of secured LUs + 341.95 / performance monitoring interval (seconds) + 1.67)

    ETERNUS GR720

    ETERNUS GR730

    (Number of days to collect+1) * ((0.06 + 11.62 / performance monitoring interval (seconds)) * number of secured LUs + 138.43 / performance monitoring interval (seconds) + 0.65)

    ETERNUS SN200 series Fibre Channel Switch

    (Maximum number of FC ports = 16 max.)

    PRIMERGY BX600 Fibre Channel Switch Blade

    PRIMERGY BX600 Fibre Channel Switch Blade(4Gbps)

    Brocade Fibre Channel Switch

    (Maximum number of FC ports = 16 max.)

    (Number of days to collect +1) * (30 / Interval between performance monitoring (seconds)) * 1.6

    ETERNUS SN200 series Fibre Channel Switch

    (Maximum number of FC ports = 32 max.)

    Brocade Fibre Channel Switch

    (Maximum number of FC ports = 32 max.)

    (Number of days to collect +1) * (30 / Interval between performance monitoring (seconds)) * 3.2

    ETERNUS SN200 series Fibre Channel Switch

    (Maximum number of FC ports = 128 max.)

    Brocade Fibre Channel Switch

    (Maximum number of FC ports = 128 max.)

    (Number of days to collect +1) * (30 / Interval between performance monitoring (seconds)) * 13

    ETERNUS SN200 series Fibre Channel Switch

    (Maximum number of FC ports = 256 max.)

    Brocade Fibre Channel Switch

    (Maximum number of FC ports = 256 max.)

    (Number of days to collect +1) * (30 / Interval between performance monitoring (seconds)) * 26

    ETERNUS SN200 series Fibre Channel Switch

    (Maximum number of FC ports = 384 max.)

    Brocade Fibre Channel Switch

    (Maximum number of FC ports = 384 max.)

    (Number of days to collect +1) * (30 / Interval between performance monitoring (seconds)) * 39

    ETERNUS SN200 MDS series Fibre Channel Switch

    (Number of days to collect +1) * 0.1 * Maximum number of slots supported by device (*) * 128 * (30 / Interval between performance monitoring (seconds))

    (*) Use 1 as the maximum number of slots for MDS9120

    For example, when securing the performance information of 512LUs on an ETERNUS3000 model 200, at 30 second intervals for 7 days,
    8 * (30 / 30) * 375 * 512 / 1024 = 1500MB is required.

4.3.1.2.6 Memory capacity

The minimum memory required for operation of this software is indicated.

Section number

Required memory (Unit : MB)

Remarks

1

200

-

 

4.3.2 Advisory notes


4.3.3 Installation procedure

The procedure for domain manager installation is given below.
The ETERNUS SF Storage Cruiser CD-ROM for manager client program is used for manager installation.

4.3.3.1 Pre-installation preparations

  1. Before installing ETERNUS SF Storage Cruiser, please refer to "4.3.1.2.3 Exclusive software", and check whether or not exclusive software is installed.

     

  2. Select [Start]-[Control Panel].

    The menu given above is for when the "[Start] menu" is selected on Windows Server 2003 Standard Edition, or Windows Server 2003 Enterprise Edition.

    In cases where the "Classic [start] menu" has been selected on Windows Server 2003 Standard Edition and Windows Server 2003 Enterprise Edition, and where the "[Start] menu" is selected on Windows 2000 Server and Windows 2000 Advanced Server, the menu is given as [Start]-[Settings]-[Control Panel].

  3. Open the "Add or Remove Programs" window, and check that exclusive software and ETERNUS SF Storage Cruiser Manager are not displayed.

     

  4. In the event that software information is displayed as a result of the above operation, this is because the software is already installed. Please uninstall it as outlined below.


4.3.3.2 Installation time 

Installation time for this software is around ten minutes.


4.3.3.3 Software installation

  1. Log on to the manager installation target system. Please log on as the OS administrator (Administrator) of the terminal.

     

  2. Insert the ETERNUS SF Storage Cruiser CD-ROM into the CD-ROM drive, open the CD-ROM_drive:\manager\Windows\I32 directory using Explorer or another tool, and execute setup.exe. The following window will be displayed.

     

  3. When the InstallShield window appears, confirm the contents and click <Next>.

     

  4. On the license agreement window, accept the agreement.

     

  5. Select the installation directory for ETERNUS SF Storage Cruiser.

    In the event that installation is to be performed to a directory other than the default, click <Browse> and select the directory to install to. When directory specification is completed, click <Next>.

    You can specify installation directory names using any printable ASCII characters other than the following symbols.

    " | : * ? / . < > , % & ^ = ! ;

     

  6. To install in a directory other than the default given in step 5, change the default directory by clicking <Browse> and select another directory. When all directory specifications are completed, if there are no errors in the configuration details, click <Next>. To change the settings, click <Back>.

    You can specify installation directory names using any printable ASCII characters other than the following symbols.

    " | : * ? / . < > , % & ^ = ! ;

     

  7. Input the port numbers which are necessary for transmissions with manager, clients, and agents.

    Please confirm the current service file that the port number described above is vacant. Services file is located as follows:

    If a port number is already being used for other purposes, specify an available port number.If the port number was changed, the port number for the same service name set on the other server side must also be set to the same value.

     

  8. Before copy process starts, confirm all the specified content.

     

  9. Copy process starts

  10. Administrator login account creation

    Create the administrator's login account and perform creation of a CLI encryption key.

    The following message will be displayed if <Skip> is clicked.

    Please refer to "C.3.1.1 Administrator login account creation (rcxcert)" in "ETERNUS SF Storage Cruiser User's Guide" and set the administrator account.

     

  11. After the copy process is complete, Resource Coordinator Agent installation will finish.

    After completing installation, click <Finish>, and restart the computer.

    When you want this software and the ServerView manager on the same system, execute the mpmsts command with the ON option specified in the esc-install-directory\Manager\opt\FJSVswstt\bin directory after installation is complete.

    Example: (When the installation directory is the default)

    In C:\Program Files\ETERNUS-SSC\Manager\opt\FJSVswstt\bin, execute the following:

    mpmsts ON <RETURN>

    When the command has been executed, restart the computer.

    When you execute no use of the ServerView manager and nor this action by mistake, execute the mpmsts command with the OFF option specified in the esc-install-directory\Manager\opt\FJSVswstt\bin directory after installation is complete.

    Example: (When the installation directory is the default)

    In C:\Program Files\ETERNUS-SSC\Manager\opt\FJSVswstt\bin, execute the following:

    mpmsts OFF <RETURN>

    When the command has been executed, restart the computer.

     

  12. Post-installation setup

    Refer to "4.3.4 Post-installation setup", and perform post installation setup.

4.3.4 Post-installation setup

The procedure for manager setup is given below.


4.3.4.1 Services configuration 

For manager operation, the following port number is necessary for transmissions with the agent and client.

"services file configuration details"

# service name  port number/protocol name
sscruisera      4917/tcp
nfport          23456/tcp


The relationship of service name and port number, protocol name, sender, receiver is given below.

Service name

Port number / Protocol name

Sender

Receiver

sscruisera

4917/tcp

Manager

Agent

nfport

23456/tcp

Manager

Client

ssvscme

7420/tcp
7420/udp

Manager

Virtualization switch

This information reflects the port number that was entered at the point of software installation, in "Port number registration" window. Check that there are no errors in the information reflected here. When a port number is already in use, specify a vacant port number.


4.3.5 Upgrading from older products 

When a previous version level of the Softek Storage Cruiser administrative server or the ETERNUS SF Storage Cruiser administrative server has been installed, you can save the setting data and have the current version level of the ETERNUS SF Storage Cruiser administrative server inherit the saved data.

4.3.5.1 Upgrading from Softek Storage Cruiser 

See "Appendix D Procedure for Upgrading from Softek Storage Cruiser".

4.3.5.2 Upgrading from a previous version level 

This section explains how to upgrade from a previous version level of the ETERNUS SF Storage Cruiser.

  1. Back up the setting data of the previous version level of ETERNUS SF Storage Cruiser Manager.

    Refer to "9.1.1.2.5 Backing up Windows Manager" in the "ETERNUS SF Storage Cruiser User's Guide" for how to perform backup.

  2. Uninstall the previous version level of ETERNUS SF Storage Cruiser Manager.

    To uninstall the Manager, refer to "9.2 [Windows] Manager uninstallation" in the "ETERNUS SF Storage Cruiser Install Guide" for the previous version level.

  3. Install the ETERNUS SF Storage Cruiser Manager.

    Refer to "4.3 [Windows] Manager " in the "ETERNUS SF Storage Cruiser Install Guide" for how to install and set up the Manager.

  4. Restore the setting data of the previous version level of ETERNUS SF Storage Cruiser Manager.

    Refer to "9.1.1.3.5 Restoring Windows Manager" in the "ETERNUS SF Storage Cruiser User's Guide" for how to restore backup data that was created according to the procedure described in Item 1.

  5. Update the configuration information of the performance management function.

    <When migrating from ETERNUS SF Storage Cruiser13.0 >

    When the performance management function is used for devices that meet the following conditions, start the Manager, then update the configuration information of those devices by referring to "7.2.11 Updating configuration information" in the "ETERNUS SF Storage Cruiser User's Guide".

    Devices

    Firmware version/level

    ETERNUS3000 (M80,M100)

    V20L85 or later or V30L15 or later

    ETERNUS4000 (M80,M100)

    V30L15 or later

    ETERNUS8000, ETERNUS4000 (Except for M80,M100)

    V10L50 or later

Contents PreviousNext
All Rights Reserved, Copyright(C) FUJITSU LIMITED 2008