Top
Systemwalker Operation Manager Troubleshooting Guide
FUJITSU Software

2.10.1 Systemwalker Operation Manager Provisioning Fails When Using ServerView Resource Coordinator (*1) Provisioning

*1: Systemwalker Resource Coordinator is the former product name of ServerView Resource Coordinator.

Error message

FJSVrcx:ERROR:61501:the provisioning handler terminated abnormally. product=SWOMGR(Systemwalker Operation Manager), xxxxx(*1)

*1: The detail varies according to the execution environment.

Applicable versions and levels

Action 1

Points to check

Check if Systemwalker Operation Manager is started on the site management server of ServerView Resource Coordinator.

You can check this based on whether an error is displayed when the mppviewo command is executed.

Cause

Systemwalker Operation Manager may have stopped on the site management server of ServerView Resource Coordinator.

Action method

If Systemwalker Operation Manager is not started on the site management server of ServerView Resource Coordinator, execute the soperationmgr command on the site management server to start it before performing ServerView Resource Coordinator provisioning.

Action 2

Points to check

Execute the ServerView Resource Coordinator command (rcxatevt) to check if the provisioning operation definitions have been set for Systemwalker Operation Manager and Systemwalker Centric Manager.

Cause

If ServerView Resource Coordinator provisioning is used to build an environment that combines Systemwalker Operation Manager and Systemwalker Centric Manager, the provisioning operation definitions may have been set for only one of the products.

Action method

If ServerView Resource Coordinator provisioning is used to build an environment that combines Systemwalker Operation Manager and Systemwalker Centric Manager, set the provisioning operation definitions for both products before performing provisioning for ServerView Resource Coordinator.

Action 3

Points to check

Check if the server group to which the management target server for the image collection source of ServerView Resource Coordinator belongs has the same configuration as the host group of Systemwalker Operation Manager.

[How to check]

  1. Execute the distributed execution status display command (mjdjstat) to check if the configuration matches that of the ServerView Resource Coordinator server group.

  2. If the management target server of the image collection source is monitored by Systemwalker Centric Manager, perform the following procedure to check if Systemwalker Operation Manager is installed:

    1. Start the monitoring window as described in "Using console" in the Systemwalker Centric Manager User's Guide - Monitoring Functions.

    2. Check if the image collection source nodes in each server group of ServerView Resource Coordinator are registered in the tree of the monitoring window.

    3. Display the properties window of the image collection source node checked in step 2, and check the following:

      • Systemwalker Operation Manager tab >> Systemwalker Operation Manager has been installed is checked.

      • The Systemwalker Operation Manager operation type is set to Job Server.

Cause

The Systemwalker Operation Manager host group configuration may be different from that of the ServerView Resource Coordinator server group. Alternatively, Systemwalker Operation Manager may have been installed as the management target server of the image collection source.

Action method

Set the same configuration for the ServerView Resource Coordinator server group and Systemwalker Operation Manager host group before image collection by ServerView Resource Coordinator.

[Setup method]

Set up the Systemwalker Operation Manager host group as described in "Definition of Job Execution Control" in the Installation Guide.

After performing setup, collect images, and then check if ServerView Resource Coordinator collected them successfully.

[How to check]

  1. Refer to the ServerView Resource Coordinator manual for information on how to check if images were collected successfully.

  2. Refer to the system log, and check if the following messages have been output.

    • "WARNING: 00401: The node (<management target server>) may not be added completely. Please make a node addition manually."

    • "WARNING: 00402: The node (<management target server>) may not be deleted completely. Please make a node deletion manually."

  3. Execute the mppviewo command to check if the Systemwalker Operation Manager daemon of the management target server has started.

  4. If none of steps 1 to 3 can be confirmed, recheck the steps of the setting method above.

Action 4

Points to check

Check if the "Mpcmtoolo: WARNING: 00401" and "Mpcmtoolo: WARNING: 00402" messages are output to the system log.

Cause

Changing the configuration of the distributed execution server may have failed.

Action method

Perform the procedure described in the "System Administrator Response" subsection in the "Mpcmtoolo: WARNING: 00401" and "Mpcmtoolo: WARNING: 00402" messages in the Message Guide.