PRIMEQUEST Integration

C122-E062-01EN PRIMEQUEST Integration for Microsoft Operations Manager FUJITSU LIMITED

Preface Purpose This manual explains the MOM management pack (PRIMEQUEST Server Agent MOM Connector), a function for allowing PRIMEQUEST to link with Microsoft Operations Manager2005 (hereafter, MOM). For information on installation, environment setup, and operation of MOM, see the MOM-related manuals released by Microsoft. Intended Readers This manual is intended for system administrators who have knowledge of MOM and manage the operation of PRIMEQUEST using MOM. Structure and Contents of This Manual Related Manuals The structure and contents of this manual are as follows: 1 Function Overview 2 Operating Environment 3 Installation Procedure 4 Function Explanation 5 Notes When using this manual, see also the following manuals as required: PRIMEQUEST 500/400 Series Installation Manual (C122-E001EN) PRIMEQUEST 500/400 Series Reference Manual (C122-E003EN) PRIMEQUEST 500/400 Series Reference Manual: Messages and Logs (C122-E004EN) Trademark Acknowledgements - Microsoft, Windows, Windows NT, and Windows Server, Internet Explorer are trademarks or registered trademarks of Microsoft Corporation in the United States and/or other countries. - All other product names mentioned herein are the trademarks or registered trademarks of their respective owners. All Rights Reserved, Copyright FUJITSU LIMITED 2007 1

Contents Preface... 1 1. Function Overview... 4 2. Operating Environment... 6 3. Installation Procedure... 7 3.1 Installing the MOM Management Pack (PRIMEQUEST Server Agent MOM Connector)... 7 3.2 SEL Monitoring Configuration of PSA (PRIMEQUEST Server Agent)... 15 3.3 Configuring PRIMEQUEST Monitoring by MOM Management Server... 17 3.3.1 Creating subgroups... 17 3.3.2 Display settings... 26 3.3.3 Installing MOM Agent... 28 3.4 Uninstalling the Management Pack... 33 4. Function Description... 37 4.1 MOM Management Pack (PRIMEQUEST Server Agent MOM Connector)... 37 4.1.1 Setting a computer group... 37 4.1.2 Events/alerts... 38 4.1.3 Action notification... 39 4.1.4 Task registration... 40 4.2 PRIMEQUEST Server Agent (PSA)... 41 5. Notes... 42 5.1 MOM Agent... 42 5.2 Partition in Which PSA-1.6.x-x or an Earlier Version is Installed... 43 5.3 Connected Partition... 43 5.4 Event Monitoring when Management Pack is Installed... 44 5.5 Differences with MMB-detected Event View (SystemEventLog) of MMB Web UI... 44 5.6 MMB-detected Events Read by PSA... 44 2

Appendix A Settings of Computer Group... 45 Appendix B Alert Generation Conditions... 46 Appendix C Settings of Rule Groups (Event Rules)... 47 Appendix D Settings of Tasks... 52 3

1. Function Overview Microsoft Operations Manager (MOM) centrally manages the network computers running on the Windows Server System. By installing MOM Agent in individual servers to be managed, the MOM management server can centrally manage the following functions (*1): Event management Performance management Application and service monitoring System diagnosis Management automation System operating status reporting function *1 Although operation without MOM Agent installed is also possible, these functions are subjected to some restrictions. To allow MOM to easily manage PRIMEQUEST, do the following: Install the management pack (PRIMEQUEST Server Agent MOM Connector) in the MOM management server. Set the operation of PRIMEQUEST Server Agent (hereafter, PSA) of each partition. Make settings to allow the MOM server to monitor PRIMEQUEST. Doing so enables the following functions: Batch management of multiple PRIMEQUEST devices as a group Add a "PRIMEQUEST" server group to the MOM management server's server group. When a Windows partition in which PSA is installed is recognized, it is managed in the PRIMEQUEST group. Event monitoring on the management server PSA in the Windows partition reads events (errors in power supplies, fans, CPUs, and memory) detected by MMB and logs them to the event log. Based on this operation, the MOM management server can monitor events. PSA detects events (errors in PCI cards and disks) and logs the events to the event log. Based on this operation, the MOM management server can monitor events. 4

Displaying MMB Web UI on the MOM management server The MMB WEB UI of the selected computer (a Windows partition of PRIMEQUEST) can be displayed on the console of the MOM management server. MOM management server Management pack PRIMEQUEST#1 MMB SEL Partition#n Partition#1 Partition#0 OS: Windows MOM Agent Fan error PSA Event log PRIMEQUEST#2 Partition#n Partition#1 Partition#0 OS: Windows MOM Agent MMB SEL Event log PSA PCI card error 5

2. Operating Environment The operating environments of the MOM management server and the server that is managed by MOM are as follows: Classification MOM management server Managed server Hardware Software Hardware Software Support range CPU: 550 MHz or higher Pentium-compatible processor Memory: 512 MB or more Hard disk: 5 GB or more Microsoft Windows Server 2003, Standard Edition Microsoft Windows Server 2003, Enterprise Edition Microsoft Windows Server 2003, Datacenter Edition PRIMEQUEST Microsoft Windows Server 2003, Enterprise Edition Microsoft Windows Server 2003, Datacenter Edition PSA (PRIMEQUEST Server Agent) 1.7.x or later 6

3. Installation Procedure This section explains the installation procedure for allowing the MOM management server to manage PRIMEQUEST. The workflow is shown below: Install the MOM management pack in the MOM management server. Configure PSA SEL monitoring in the Windows partition of PRIMEQUEST. Configure PRIMEQUEST monitoring on the MOM management server (installation of MOM Agent). 3.1 Installing the MOM Management Pack (PRIMEQUEST Server Agent MOM Connector) The MOM management pack is provided as a single installation package in exe format (psamom1000.exe). This section explains the procedure for installing the MOM management pack on the MOM management server. 1) Store the MOM management pack (pasmom1000.exe) in any directory on the MOM management server. 7

2) Start the stored MOM management pack. When installation preparation is complete with the following screen displayed, click [Next]. 3) If you want to change the installation folder, click [Change]. After deciding on the installation folder, click [Next]. 8

4) Click [Install] to install the MOM management pack. 5) When installation is complete, click [Finish]. 9

6) After the installation is complete, a folder has been created in the management pack installation destination. C:\Program Files\Fujitsu\MOM Management Packs\FJSVpsa (This assumes that the management pack installation destination is "C:\Program Files\Fujitsu.") A file (PrimequestMgmtPack.akm) used to import the management pack has been created in the folder. 10

7) Import the MOM management pack into the MOM management server. To do so, start the MOM administrator console and select [Console Root] -> [Microsoft Operations Manager] -> [Management Packs]. When the contents window of the management pack is displayed, click [Import/Export Management Packs]. 8) [Management Pack Import/Export Wizard] is displayed. Click [Next]. 11

9) Select [Import Management Packs and/or reports] and then click [Next]. 10) Click [Browse] and select the folder containing "PrimequestMgmtPack.akm" that was generated when the management pack was installed in step 6. Click [Next]. For instance, when the MOM management pack is installed at "C:\Program Files\Fujitsu," enter "C:\Program Files\Fujitsu\MOM Management Packs\FJSVpsa". 12

11) Select individual items as shown below and then click [Next]. Please select one or more Management Packs to import: PrimequestMgmtPack.akm Import Options: Update existing Management Pack. Back up existing Management Pack: Check as required. Management Pack backup directory: Specify any location. 12) After the management pack import wizard is complete, click [Finish]. 13

13) The import status is displayed. After confirming the completion of import, click [Close]. 14

3.2 SEL Monitoring Configuration of PSA (PRIMEQUEST Server Agent) PSA is a standard software product supplied with PRIMEQUEST. By configuring SEL monitoring by PSA, PSA reads events that are not recognized by the MOM management server but are detected by MMB, and logs them to the OS event log file. This section explains the procedure for configuring SEL monitoring. 1) Open the PSA configuration file (selwrite.conf) with a text editor. The configuration file is stored in the following folder: C:\Program Files\Fujitsu\FJSVpsa\etc\opt\FJSVpsa\usr (This assumes that PSA is installed at C:\Program Files.) 15

2) Change "SELWRITE=0" to "SELWRITE=1" and then save the file. 3) Restart the OS. 16

3.3 Configuring PRIMEQUEST Monitoring by MOM Management Server This section explains various settings for the MOM management server to monitor PRIMEQUEST 3.3.1 Creating subgroups 1) If you want to display PRIMEQUEST units individually on the MOM management server, you need to create a subgroup for each unit under the PRIMEQUEST group. If there is no need to create subgroups, proceed to Section 3.3.2, "Display settings." 2) Start the MOM administrator console. Select [Console Root] -> [Microsoft Operations Manager] -> [Management Packs], right-click [Computer Attribute], and then select [Create Computer Attribute]. 17

3) Select [Registry value] and then click [Next]. 4) Enter the following path and then click [Next]: SOFTWARE\Fujitsu\FJSVpsa\SERIALNO 18

5) Select [Retrieve registry value and convert to] and [string], and then click [Next]. 6) Enter "PRIMEQUEST SERIAL NO" in the [Name] and [Description] fields, check [Enabled], and then click [Finish]. 19

7) Select [Console Root] -> [Microsoft Operations Manager] -> [Management Packs] -> [Computer Groups], right-click [PRIMEQUEST], and then select [Create Computer Group]. 8) When Create Computer Group Wizard appears, click [Next]. 20

9) Enter a name and description that can identify a PRIMEQUEST unit in the [Name] and [Description] fields, and then click [Next]. 10) Confirm that the name entered in step 9 is displayed as a subgroup included in this computer group, and then click [Next]. 21

11) Click [Next]. 12) Click [Next]. 22

13) Select [Do not search for computers] and then click [Next]. 14) Select [Specify a formula for the computer group], enter the following value in the [Formula for computer group] field, and then click [Next]. AttributeValue(PRIMEQUEST)ANDAttributeValue(PRIMEQUEST SERIAL NO)="xxxx" * xxxx is the serial number of the unit. The serial number of the unit can be checked with the [System Status] window of the MMB Web UI. 23

15) Select [The worst state of any member computer or subgroup] and then click [Next]. 16) Confirm the settings you have made, and then click [Next]. 24

17) When the Create Computer Group Wizard completion window appears, click [Finish]. 25

3.3.2 Display settings After a subgroup is set, the relevant detected PRIMEQUEST computer is displayed both as a member of a subgroup and as a member of the PRIMEQUEST group. To prevent this problem and display this computer as a member of the subgroup only, display setting must be performed. 1) After creating a subgroup, select [Console Root] -> [Microsoft Operations Manager] -> [Management Packs] -> [Computer Groups], right-click [PRIMEQUEST], and then select [Properties]. 26

2) On the [Search for Computers] tab, select [Do not search for computers]. When a confirmation popup window appears, click [OK]. 3) On the [Formula] tab, select [Do not use a formula to determine membership for this computer group] and then click [OK]. 27

3.3.3 Installing MOM Agent Make settings so that the MOM management server detects a PRIMEQUEST computer and automatically adds it to a PRIMEQUEST group or subgroup. 1) Start the MOM administrator console. Select [Console Root] -> [Microsoft Operations Manager] -> [Administration] -> [Computers], right-click [Computer Discovery Rule], and then select [Create Computer Discovery Rule]. 2) The [Computer Discovery Rule] dialog box appears. Enter data in individual fields under [Computer discovery rule], and then click [OK]. Note: Select both check boxes. 28

Item Management Server Rule type Domain name Computer name Computer type Initial Management Mode Setting Select the management server. Select "Include." Enter the domain name to be searched for. Select "equals" and enter a computer name. (The computer name can include a wildcard.) Select "Servers and Clients." Select any item. Remarks: For details on the settings of individual items, see the MOM manuals. 3) Next, select [Console Root] -> [Microsoft Operations Manager] -> [Administration] -> [Computers], right-click [Computer Discovery Rule], and then select [Run Computer Discovery Now]. 29

4) When the MOM management server detects a PRIMEQUEST partition, the partition is displayed at [Console Root] -> [Microsoft Operations Manager] -> [Administration] -> [Computers] -> [Unmanaged Computers]. Select the detected partition and right-click it, and then select [Install Agent] or [Begin Agentless Monitoring]. Note: MOM functions are subjected to some restrictions in Agentless mode. (See Section 5.1, "MOM Agent.") 5) If PSA is installed in the partition, the detected computer is added to a PRIMEQUEST group. If a subgroup has been set, the detected computer is added to the subgroup. 30

6) Make settings so that the MMB Web UI can be started from the MOM management server. Start the MOM administrator console and then select [All: Diagram Views] -> [PRIMEQUEST] -> [Diagram]. A PRIMEQUEST diagram is displayed. Select the target computer, and then click [PRIMEQUEST Web UI Registration] from the Tasks menu to reregister the MMB Web UI URL. 31

7) Select the target computer from the PRIMEQUEST Diagram, and click [PRIMEQUEST Web UI Exec] from the Tasks menu. When the task runs normally, the browser starts and displays the MMB Web UI window. 32

3.4 Uninstalling the Management Pack This section explains how to uninstall the management pack from the MOM management server. Start the MOM administrator console. Right-click on the items listed in the table below and then click [Remove]. *1 Before removing the rule group, the relevant PRIMEQUEST computer must be set as an unmanaged computer. *2 Before removing the notification group, the relevant rule group must be removed. Item [Console Root] -> [Microsoft Operations Manager] -> [Management Packs] -> [Computer Groups] -> "PRIMEQUEST" [Console Root] -> [Microsoft Operations Manager] -> [Management Packs] -> [Rule Groups] -> "PRIMEQUEST" (*1) [Console Root] -> [Microsoft Operations Manager] -> [Management Packs] -> [Tasks] -> "PRIMEQUEST" [Console Root] -> [Microsoft Operations Manager] -> [Management Packs] -> [Notification] -> [Notification Groups] -> "PRIMEQUEST Help Disk" (*2) [Console Root] -> [Microsoft Operations Manager] -> [Management Packs] -> [Computer Attributes] -> "PRIMEQUEST" displayed in the right-side frame 33

1) Start the MOM operator console. Right-click on the following items and then click [Remove]. [All: Alert Views] -> [PRIMEQUEST] [All: Public Views] -> [PRIMEQUEST] Item 34

35

2) Select [Start] -> [Control Panel] -> [Add or Remove Programs]. Select [PRIMEQUEST Server Agent MOM Connector] from the program list and click [Remove]. 36

4. Function Description 4.1 MOM Management Pack (PRIMEQUEST Server Agent MOM Connector) By installing the MOM management pack (hereafter referred to as the management pack) on the MOM management server, the following functions can be added to facilitate PRIMEQUEST management. 4.1.1 Setting a computer group Installing the management pack creates a [PRIMEQUEST] group. The [PRIMEQUEST] group is illustrated in a diagram as shown in the figure below. To enable automatic allocation to the [PRIMEQUEST] group, the management pack assigns a computer attribute as identification information. Allocation to the computer group is performed according to the detection of a computer attribute. For information on the settings of the management pack, see Appendix A, "Settings of Computer Group." The management pack sets no subgroup. Therefore, to display individual units after installation of the management pack, subgroups need to be set manually. For information on the setting procedure, see Section 3.3, "Configuring PRIMEQUEST Monitoring by MOM Management Server." 37

4.1.2 Events/alerts Events generated in monitored computers are collectively displayed as events of PRIMEQUEST groups. Errors caused on the MMB are also collected from the event log of each partition and displayed in the same manner. With the management pack installed, errors occurring in each partition and on the MMB can be monitored. These errors are displayed after sorted into the following two items. Item (display name) PRIMEQUEST MMB Hardware Event PRIMEQUEST Server Agent Description The event log of source name "pqmmbsel" at the information, warning, and error levels can be referenced. The event log of source name "FJSVpsa" at the warning and error levels can be referenced. Also, set up the management pack so that the management pack generates an alert when an event occurs. For information on the alert generation conditions, see Appendix B, "Alert Generation Conditions." Furthermore, the management pack sets rule groups (event rules). For information on the settings, see Appendix C, "Settings of Rule Groups (Event Rules)." 38

An alert is generated when the MOM management server detects an event. If the notification destination has been set, the alert is reported to the administrator according to the notification method. When an alert is generated, the computer causes a state transition as specified by the generated alert. When an alert is reported, the computer causes a state transition as specified by the generated alert unless "Already solved" is set at "Set Alert Solution State" for the generated alert. If an alert is generated, corrective action needs to be taken soon. If the same event recurs while alert control is enabled, the "Repetition count" is incremented by 1. 4.1.3 Action notification The MOM management server can generate an action according to the contents of the event. The management pack allows you to make settings so that an action is reported using SNMP-Traps or electronic mail. Register notification destination group "PRIMEQUEST Help Desk." To receive information on events that occur in PRIMEQUEST using e-mail, etc., the information required for notification needs to be set in "PRIMEQUEST Help Desk." If SNMP-Traps need to be sent, a trap send destination needs to be set using the SNMP service on the MOM management server. Notification can be made using the following three functions: E-mail Beeper External command Determine and set the notification function to be used according to the MOM operation mode. A notification function that is not set is disabled. The notification destination group that is set by the management pack is as follows: Item Setting Remarks Name PRIMEQUEST Help Desk Although this group name is set as a notification destination group, the actual notification destination must be set by the administrator. 39

4.1.4 Task registration Installing the management pack adds the following four tasks. Registering the URL of the MMB Web UI in advance for a computer allows you to select the computer to start the MMB Web UI and check detailed information on the unit. Task PRIMEQUEST Web UI Exec PRIMEQUEST Web UI Node List PRIMEQUEST Web UI Registration PRIMEQUEST Web UI Remove Outline of function Starts the MMB Web UI of the selected computer. Lists the correspondence between the registered computers and MMB virtual IP addresses. Registers/updates the URL of the MMB Web UI of the selected computer. Removes the URL of the MMB Web UI of the selected computer. For information on the settings of the tasks provided by the management pack, see Appendix D, "Settings of Tasks." Note: When removing a computer from the monitoring targets, be sure to execute "PRIMEQUEST Web UI Remove" in advance to remove the computer information. If the URL of the MMB Web UI is changed, execute "PRIMEQUEST Web UI Registration" to update the computer information. When a PRIMEQUEST group or subgroup is selected, only the "PRIMEQUEST Web UI Node List" task can be executed. An error results if another task is executed. 40

Execution of the "PRIMEQUEST Web UI Registration" task requires a domain management privilege or the privilege to access the registries of all computers to be managed by the management pack. Only the privilege to access the MOM management server is required for executing the "PRIMEQUEST Web UI Exec" task. 4.2 PRIMEQUEST Server Agent (PSA) PRIMEQUEST Server Agent (PSA) installed in a PRIMEQUEST partition outputs the following events to the event log. This enables the MOM management server to monitor PRIMEQUEST events. Hardware errors of PCI cards and SCSI devices Hardware errors detected by MMB when the SEL monitoring function is enabled (See Section 5.6, "MMB-detected Events Read by PSA.") For information on the events detected by PSA and MMB, see the PRIMEQUEST 500/400 Series Reference Manual:Messages/Logs (C122-E004EN). The PSA SEL monitoring function is supported by PSA-1.7.x-x or later. If PSA- 1.6.x-x or an earlier version is installed, it must be updated. For information on the procedure for updating PSA, see the PRIMEQUEST 500/400 Series Installation Manual (C122-E001EN). 41

5. Notes 5.1 MOM Agent The MOM management server and managed computer transfer data using MOM Server and MOM Agent. Therefore, MOM Agent thus needs to be installed in managed computers. To install MOM Agent, select "Install/Uninstall Agents Wizard" from the "Administrator Console" screen. If the relevant computer is in the same domain, it is automatically detected. If it is not in the same domain or it is not displayed in the MOM Administrator Console even if it is in the same domain, the Agent installation wizard needs to be used to search for the relevant computer. (If the computer is not in the same domain, the Web UI probably cannot be started.) The management pack monitors resources that can be monitored in either Agent monitoring or Agentless monitoring mode. Either monitoring mode can thus be selected. 42

The difference between the Agent monitoring mode and Agentless monitoring mode is as follows: Monitoring mode Agent monitoring Agentless monitoring Description Agent periodically reports events that occurred to the management server. The management server periodically polls the managed computer. The following restrictions apply to Agentless monitoring. See the MOM manuals for more information. One management server can monitor up to 10 Agentless-managed servers. Up to 60 Agentless-managed servers can be monitored per management group. The description of the event log output by an Agentless-managed server is not displayed on the management server. No application log provider is permitted. 5.2 Partition in Which PSA-1.6.x-x or an Earlier Version is Installed To monitor PRIMEQUEST on the MOM server, PSA-1.7.x-x or later version must be installed in the PRIMEQUEST Windows partition. Note that the following operations occur for a partition in which PSA-1.6.x-x or an earlier version is installed: Even if a subgroup is created for each unit, the unit isn't included in the subgroup. (Computer attributes cannot be read in units of computers.) Events detected by MMB are not reported to the MOM management server. The "PRIMEQUEST Web UI Registration" task cannot be executed. 5.3 Connected Partition In a partition disconnected by a power failure or network failure, the relevant computer on the MOM management server is in heartbeat down state and cannot be monitored. The log of events that are output during this period can be monitored after network recovery. Also, at the time of recovery, an alert is generated for the event that is output then. 43

5.4 Event Monitoring when Management Pack is Installed Events detected by PSA and MMB before installation of the management pack cannot be monitored. Alerts for them cannot be generated either. However, if the system volume is moved to another unit (partition) or the relevant partition has been stopped for some time, outdated MMB-detected events may be reported mistakenly. After the management pack is installed, events logged to a computer cannot be monitored until computer detection is performed. 5.5 Differences with MMB-detected Event View (SystemEventLog) of MMB Web UI Installing the management pack enables MMB-detected events to be monitored on the MOM management server. Note, however, that differences may occur between the occurrence time for the MMB-detected event information displayed on the MOM server and the occurrence time for the information displayed in SystemEventLog of the MMB Web UI 5.6 MMB-detected Events Read by PSA MMB-detected events read by PSA are limited to hardware errors related to the own partition and common parts. Hardware errors related to other partitions cannot be read. 44

Appendix A Settings of Computer Group The settings of the computer group for the management pack are as follows: Computer group Set the computer group monitored by the management pack as shown below: Item Name Included subgroup Included computer Excluded computer Computer search Formula State Roll-up Policy Setting PRIMEQUEST None None None Server/domain controller AttributeValue(PRIMEQUEST) The worst state of any member computer or subgroup 45

Appendix B Alert Generation Conditions For the management pack, make settings so that an alert is generated when an event occurs. Event that generates an alert Reported event Source name Type Transition state PRIMEQUEST MMB Hardware Event PRIMEQUEST Server Agent pqmmbsel Error Serious error pqmmbsel Warning Warning pqmmbsel Information *1 - *2 FJSVpsa Error Serious error FJSVpsa Warning Warning *1 An alert is generated only when an event related to System Status Sensor occurs. *2 The transition state becomes "serious error" only when it is reported that System Status Sensor has been set to Panic. 46

Appendix C Settings of Rule Groups (Event Rules) For the management pack, set the rule groups (event rules) as shown below: Subrule group: PRIMEQUEST MMB Hardware Item Setting Remarks Name Condition Response Alert Alert control MMB Error The following event log is monitored: Source name=pqmmbsel Type = Error SNMP-Trap and notification Enable / Severity = Serious error Enable (Check items: Computer, domain, and event number) *1 Item Setting Remarks Name Condition Response Alert Alert control MMB Warning The following event log is monitored: Source name=pqmmbsel Type = Warning SNMP-Trap and notification Enable / Severity = Warning Enable (Check items: Computer, domain, and event number) *1 Item Setting Remarks Name Condition Response Alert Alert control MMB Information (Power Off) The following event log is monitored: Source name=pqmmbsel Type = Information Parameter %6 = C06F00FF SNMP-Trap Enable / Severity = Information Enable (Check items: Computer, domain, and event number) *1 47

Item Setting Remarks Name Condition Response Alert Alert control MMB Information (Power On In Progress) The following event log is monitored: Source name=pqmmbsel Type = Information Parameter %6 =C06F01FF SNMP-Trap Enable / Severity = Information Enable (Check items: Computer, domain, and event number) *1 Item Setting Remarks Name Condition Response Alert Alert control MMB Information (Reset) The following event log is monitored: Source name=pqmmbsel Type = Information Parameter %6 =C06F02FF SNMP-Trap Enable / Severity = Information Enable (Check items: Computer, domain, and event number) *1 Item Setting Remarks Name Condition Response Alert Alert control MMB Information (Boot) The following event log is monitored: Source name=pqmmbsel Type = Information Parameter %6 =C06F04FF SNMP-Trap Enable / Severity = Information Enable (Check items: Computer, domain, and event number) *1 48

Item Setting Remarks Name Condition Response Alert Alert control MMB Information (OS Running) The following event log is monitored: Source name=pqmmbsel Type = Information Parameter %6 =C06F05FF SNMP-Trap Enable / Severity = Information Enable (Check items: Computer, domain, and event number) *1 Item Setting Remarks Name Condition Response Alert Alert control MMB Information (OS Shutdown) The following event log is monitored: Source name=pqmmbsel Type = Information Parameter %6 =C06F06FF SNMP-Trap Enable / Severity = Information Enable (Check items: Computer, domain, and event number) *1 Item Setting Remarks Name Condition Response Alert Alert control MMB Information (Panic) The following event log is monitored: Source name=pqmmbsel Type = Information Parameter %6 =C06F07FF SNMP-Trap Enable / Severity = Serious error Enable (Check items: Computer, domain, and event number) *1 49

Item Setting Remarks Name Condition Response Alert Alert control MMB Information (Power Off In Progress) The following event log is monitored: Source name=pqmmbsel Type = Information Parameter %6 =C06F08FF SNMP-Trap Enable / Severity = Information Enable (Check items: Computer, domain, and event number) *1 Item Setting Remarks Name Condition Response Alert Alert control MMB Information (Check Stop) The following event log is monitored: Source name=pqmmbsel Type = Information Parameter %6 =C06F09FF SNMP-Trap Enable / Severity = Information (pending) Enable (Check items: Computer, domain, and event number) *1 Subrule group: PRIMEQUEST Server Agent Item Setting Remarks Name Condition Response Alert Alert control PSA Error The following event log is monitored: Source name =FJSVpsa Type = Error SNMP-Trap and notification Enable / Severity = Serious error Enable (Check items: Computer, domain, and event number) *1 50

Item Setting Remarks Name Condition Response Alert Alert control PSA Warning The following event log is monitored: Source name =FJSVpsa Type = Warning SNMP-Trap and notification Enable / Severity = Warning Enable (Check items: Computer, domain, and event number) *1 *1 When "Alert control" is set to Enable, an alert is generated only once for events with the same values for all check items. A notification (e-mail) is also sent only once. However, an SNMP-Trap is not controlled but is generated for each event. A notification (e-mail) can also be generated for each event. 51

Appendix D Settings of Tasks For the management pack, set the tasks that can be used as shown below. Name Task command line Start directory Item Display task output operation Setting PRIMEQUEST Web UI Exec cmd /c pqwebui $FQDN$ %PQMOMPATH% No Function description This task retrieves the MMB virtual IP address information of the specified computer from the registry and starts the relevant MMB Web UI. If the IP address is not found in the registry, the task obtains the MMB virtual IP address and starts the MMB Web UI. If the MMB virtual IP address cannot be obtained because, for example, an access privilege has not been granted, it displays a message. Item Setting Name PRIMEQUEST Web UI Node list Task command line cmd /c pqwebview Start directory %PQMOMPATH% Display task output operation Yes Function description This task lists the nodes and MMB virtual IP addresses defined in the registry. 52

Name Task command line Start directory Item Display task output operation Setting PRIMEQUEST Web UI Registration cmd /c pqwebreg $FQDN$ %PQMOMPATH% Yes Function description This task retrieves the MMB virtual IP address information of the specified computer and enters it in the registry management table. If the specified computer is already registered but the information is different, the information is updated. The task does nothing if no difference is found. If the linkage is disabled or registry information cannot be retrieved, the task displays a message. Name Task command line Start directory Item Display task output operation Setting PRIMEQUEST Web UI Registration cmd /c pqwebreg $FQDN$ %PQMOMPATH% Yes Function description This task removes the MMB virtual IP address information of the specified computer from the registry management table. Before execution of removal, an execution confirmation message box appears. The task does nothing if the specified computer is not registered. 53