Top
ETERNUS SF Storage Cruiser 14.0 User's Guide

10.2.4 Setup procedure

Follow the procedure below on the Systemwalker Centric Manager operation management client.
Log in to the administrative client with a user name belonging to the Administrator group of the local group.


10.2.4.1 Setup from Systemwalker Centric Manager administrative client

  1. On the Systemwalker Centric Manager administration client, follow the procedure to detect a node in a subnet that contains storage devices.

  2. Register the window start method in the pop-up menu of the node.

    Register the start method of this software in the pop-up menu of the node of the storage device, using the Systemwalker Centric Manager mpaplreg command. (Client must be installed on the same PC.)

    For use of the mpaplreg command, see "12.4.1 Systemwalker Centric Manager window linkage command (mpaplreg)". (The example below uses "ESC" as the menu name and "tama" as the server node name. Change these names according to the environment if necessary.

    mpaplreg -a -m ESC -p tama -c "\"C:\Program Files\ETERNUS-SSC\Client\bin\rcxclient.exe\""

    Enclose the entire start command (-c option value) specified with the mpaplreg command within double quotation marks ("), and enclose the start command (C:\Program Files\...\rcxclient.exe) with [\"] and [\"].

Note

  • The operating environment must be set up in such a way that the administrative server recognizes the association between "Name" and "IP" in case that Systemwalker Centric Manager detects the server node by "Name", but not "IP". Please confirm that the name is registered in /etc/hosts or on the DNS server. Software linkage from this software to Systemwalker Centric Manager will fail if the administrative server does not recognize the association between an IP number and a node name.

  • Perform this operation each time a storage device is added.

  • When the event that is displayed as Info in the status item of the event log window is reported to Systemwalker Centric Manager, it is regarded as "Display Mode: general" and is not displayed on the monitoring window. If you want to display it, execute [Display Mode in the Monitored Viewer] from [Action] - [Action Setting] - [Message] from the Systemwalker Centric Manager menu. For the detail about [Display Mode in the Monitored Viewer], refer to the Systemwalker Centric Manager manual.

  • If the starting method of this software administrative server is changed, execute the following command to delete the registered menu, and register it again. (In the example below, the menu name is "ESC.")

    mpaplreg -d -m ESC
  • Confirm the content of registration by the following commands when the icon of this software is not displayed in the pop-up menu of the node though the menu addition by the mpaplreg command has normally. (In the example below, the menu name is "ESC.")

    mpaplreg -v -m ESC
  • After completing the procedure, restart the Systemwalker Centric Manager server of an administrative client, and execute "node detection" in the monitoring area. Updating of registered icons is enabled in the display.

  • A parameter error (swsag5101) occurs if the mpaplreg command contains an invalid parameter when starts from the batch file.


10.2.4.2 Action to be taken if Systemwalker Centric Manager administrative server and this software adminitrative server are the same server

If the Systemwalker Centric Manager administrative server and administrative server of this software are the same server, both Systemwalker Centric Manager and this software receive and display SNMP Traps from devices. Perform the following task to prevent Systemwalker Centric Manager from directly receiving and displaying SNMP Traps from devices:


Suppressing Systemwalker Centric Manager reception of SNMP Traps from devices managed by this software

If the same server node has the Systemwalker Centric Manager administrative server and administrative server of this software, following the steps given below to prevent Systemwalker Centric Manager from direct reception of SNMP Traps of devices managed by this software. As a result, SNMP Traps would be received and decoded by this software and only SNMP Traps necessary for fault monitoring would be posted to Systemwalker Centric Manager. Consequently, when the SNMP Trap display function supported by Systemwalker Centric Manager is used, multiple traps appear for a single event or unnecessary SNMP Traps are displayed.

Information

These settings are not required if the Systemwalker Centric Manager-supported SNMP Trap display function is enabled.

  1. From a Systemwalker Centric Manager administrative client, select [Event] - [Action Definition] in "System Monitoring."

    The Monitored Event Table appears.

  2. Select [Event] - [Event Addition] in the Monitored Event Table dialog.

    The Event Definition dialog appears.

    Define the following items:

    Host Name

    Check "Not specified".

    Monitored Event Type

    Check "Not specified".

    Error Type

    Check "Not specified".

    Message Number

    Check "Not specified".

    Display Mode (only for Systemwalker Centric Manager 5.1 or later)

    Check "Not specified".

    Label

    Check "Not specified".

    Text

    Specify one of the values shown below for an event definition.
    Be sure to define this item only when individual devices are being managed. Otherwise, the item need not be defined.

    Table 10.1 Lists of text

    Device

    Value

    ETERNUS DX60/DX80
    ETERNUS2000 series
    ETERNUS3000 series
    ETERNUS4000 series
    ETERNUS6000 series
    ETERNUS8000 series
    ETERNUS GR series

    enterprise:aplNetStorage\.1

    ETERNUS SX300
    ETERNUS SX300S

    enterprise:enterprises\.1123\.1\.205
    enterprise:enterprises\.1123\.4\.300

    Hitachi SANRISE

    enterprise:enterprises\.116\.3\.11

    EMC Symmetrix (ECC Agent)

    enterprise:enterprises\.1139\.1

    ETERNUS LT120
    HP Surestore

    enterprise:enterprises\.11\.2\.3\.9\.7\.1
    enterprise:enterprises\.11\.2\.3\.9\.7\.2

    ETERNUS LT130

    enterprise:enterprises\.3351\.1\.3\.2\.6

    ETERNUS LT160

    enterprise:aplNetStorage\.3\.1

    ETERNUS LT200

    enterprise:enterprises\.119\.1\.83\.1\.21

    ETERNUS LT210, LT220, LT230

    enterprise:enterprises\.119\.1\.83\.1\.1
    enterprise:enterprises\.119\.1\.83\.1\.2

    ETERNUS LT250

    enterprise:aplNetStorage\.3\.5

    ETERNUS LT270

    enterprise:aplNetStorage\.3\.2

    ETERNUS NR1000

    enterprise:enterprises\.789

    BrocadeFC-Switch
    ETERNUS SN200 series Fibre Channel switch
    PRIMERGY BX600 fiber channel switch blade

    enterprise:enterprises\.1588\.2\.1\.1

    GadzooxFC-Hub

    enterprise:enterprises\.1754\.1\.2\.2

    Performance
    Agent trap

    enterprise:aplSANMgr

    Cisco MDS
    ETERNUS SN200 MDS

    enterprise:enterprises\.9\.9\.117\.2
    enterprise:enterprises\.9\.9\.289\.1\.3
    enterprise:enterprises\.9\.9\.302\.1\.3
    enterprise:enterprises\.9\.9\.91\.2

    McDATA FC-Switch

    enterprise:enterprises\.289

    LT130, BrocadeFC-Switch, SN200, BX600 fiber channel switch blade, Cisco MDS, SN200 MDS, McDATA FC-Swtich, GadzooxFC-Hub common

    enterprise:experimental\.94 (*)

    *: The device not supported with Storage Cruiser includes the device which reports on SNMP Trap of this experimental\.94 and the event of those devices is controlled.

  3. Select [Action] - [Action Setting] for the event set in step 2.

    The Action Definition dialog appears.

    Select the [Message] tab, and define the following items:

    Forward to Monitoring Server

    Check "No"

    Log Spool

    Check "No"

  4. Repeat Steps 1 to 3 for each of the text messages in the "Table 10.1 Lists of text".
    If the SNMP standard trap is reported as an event from a storage device, refer to the above description, and suppress transmission of the SNMP standard trap according to your operation mode.


10.2.4.3 Setting confirmation test

In case that the target device is a device of theETERNUS DX60/DX80, ETERNUS2000 series, ETERNUS3000, ETERNUS4000 series, ETERNUS6000 series, ETERNUS8000 series, GR series, or a Fibre Channel switch, a suitable procedure and command are provided to confirm whether software linkage to Systemwalker Centric Manager is set up correctly. Run the test described in "5.3 Checking Management Status" to check whether operation is correct.

The figure below shows an example of the Systemwalker Centric Manager window displayed during event linkage with Systemwalker Centric Manager.