2.6.4 Map cooperation (action cooperation)

The map cooperation (action cooperation) function allows users to manipulate SSO without logging in to the SSO console, simply by selecting an SSO-provided action from the Action menu in the NNMi console window. For example, the monitoring status can be viewed from that menu.

The following two actions can be performed:

Viewing the monitoring status

This action displays the monitoring status display window. This window can be opened from only the NNMi console, and cannot be opened from the SSO console menu.
Opening a window

This action starts a window provided by the SSO console.

Note that the above windows can be opened when only one monitoring manager node symbol or monitoring server node symbol is selected. Multiple monitoring status display windows or other windows cannot be opened in a single action by selecting multiple node symbols.

For details on how to add the above listed actions to the Action menu of the NNMi console window, see 3.1 Installation and setup flowcharts.

Organization of this subsection

(1) Viewing the monitoring status
(2) Opening a window
(3) Action menu access rights
(4) Executing actions
(5) Notes on map cooperation (action cooperation)

(1) Viewing the monitoring status

This subsection assumes that Monitoring Browser or Monitoring Browser (HTTPS) has been added under SNMP System Observer in the Action menu of the NNMi console window. By selecting Monitoring Browser or Monitoring Browser (HTTPS), you can open the monitoring status display window that displays both the resource statuses during resource collection (threshold monitoring) and the application statuses (process and service monitoring).

If the map cooperation (symbol cooperation) function is being used, the node symbol color is updated every time the status associated with a status managed in SSO is registered. If you select a node and then select Monitoring Browser or Monitoring Browser (HTTPS), you can check the status of that node without logging in to the SSO console. In this way, if the color of a node changes, you can easily find out the cause.

For details on the settings for opening the monitoring status display window, see (4) Executing actions.

The following figure shows examples of the NNMi console window and the monitoring status display window.

Figure 2‒70: NNMi console window and the monitoring status display window

The following describes the monitoring status display window.

(a) Monitoring status display window

The monitoring status display window displays the resource statuses and application statuses, as well as the process statuses or service statuses.

The following figure shows the monitoring status display window.

Figure 2‒71: Monitoring status display window

The items displayed in the above window are described below.

Monitoring Manager

Displays the host name and IP address of the monitoring manager.

Monitoring Server

Displays the host name and IP address of the monitoring server.

Update Status

Displays the latest monitoring status of SSO.

Resource Status tab

Select this tab to display the resource status. For details on the items displayed when the Resource Status tab is selected, see (b) Viewing the resource status.

Application Status tab

Select this tab to display the application status. For details on the items displayed when the Application Status tab is selected, see (c) Viewing the application status.

Important

The monitoring status display window appears with the Resource Status tab selected when you select Monitoring Browser from the Action menu of the NNMi console window or click the Update Status button in the monitoring status display window.

However, when only process monitoring or service monitoring is being performed, the monitoring status display window appears with the Application Status tab selected.

(b) Viewing the resource status

The Resource Status tab displays the resource status items (Category, Resource Group, Resource, Subresource, Instance, and Status).

The following figure shows an example of the selected Resource Status tab.

Figure 2‒72: Example of the Resource Status tab

The items displayed in the above tab are described below.

Category

Displays categories.

Group

Displays resource groups.

Resource

Displays resources.

Subresource^#1

Displays subresources.

Instance^{#1, #2}

Displays instances.

Status^#1

Displays resource statuses.

The following table lists the correspondence between icons and statuses.

Table 2‒18: Icons and statuses
Icon	Resource status
(Green)	Normal
(Yellow)	Warning
(Red)	Critical
(blue)	Unknown

#1:

For the resources whose values are not calculated, a hyphen (-) is displayed. Resource values are not calculated in the following cases:

Threshold monitoring is not being performed.
Resource values have not yet been collected (for example, immediately after the start of collection).

#2:

If the names of all instances in the same resource are numeric values, the displayed names are sorted by natural ordering. In other cases (if there are instances whose names include character strings), the displayed names are sorted in lexical order.

(c) Viewing the application status

Selecting the Application Status tab displays the application status items (Application Name, Additional Information, and Status).

The following figure shows an example of the Application Status tab.

Figure 2‒73: Example of the Application Status tab

The items displayed in the above tab are described below.

Application Name

Displays applications.

When one of the displayed applications is selected, depending on whether the process or service of the application is being monitored, the process status or service status is displayed.

For details on the process status and service status, see (d) Viewing the process status and service status.

Additional Information

Displays additional information about the application. If additional information has not been set, a hyphen (-) is displayed.

Status

Displays the application statuses.

For the correspondence between icons and statuses, see Table 2-18.

(d) Viewing the process status and service status

For applications whose processes are being monitored, the process statuses are displayed. For applications whose services are being monitored, the service statuses are displayed.

The following figure shows an example of the Application Status tab when process statuses are displayed.

Figure 2‒74: Example of the Application Status tab when process statuses are displayed

The items displayed in the above tab are described below.

Process Name

Displays monitoring processes.

Child Process Name

Displays monitoring child processes.

Status

Displays the monitoring process and monitoring child process statuses.

For the correspondence between icons and statuses, see Table 2-18.

The following figure shows an example of the Application Status tab when service statuses are displayed.

Figure 2‒75: Example of the Application Status tab when service statuses are displayed

The items displayed in the above tab are described below.

Service Name

Displays monitoring services.

Status

Displays the monitoring service status.

For the correspondence between icons and statuses, see Table 2-18.

(e) Notes

The Resource Status tab and Application Status tab cannot display statuses when the ssocolmng daemon process and the ssoapmon daemon process are stopped.

To Page Top

(2) Opening a window

This subsection assumes that window names (such as Resource Configuration) have been added under SNMP System Observer in the Action menu of the NNMi console window. By selecting such a window name, you can remotely open and manipulate an SSO window. The following lists the windows that can be opened:

Resource Browser window
Resource Data Reference window
Resource Configuration window
Resource Reference window
Process Monitor window
Process Configuration window
Process Reference window
Report Configuration window
Report Browser window^#

#:: A list of the created report files is displayed.

The SSO that is remotely operated by opening a window differs depending on the node that is selected when the action is executed. If the selected node is a monitoring manager, the remotely-operated SSO is the SSO on the monitoring manager. If the selected node is a monitoring server, the remotely-operated SSO is the SSO that monitors the monitoring server.

Note

When you open a Java applet window (except a report browser), the window shown below also opens. If you close the window shown below, the parent window, which you want to manipulate, also closes. Therefore, while you are manipulating the window that you opened, do not close the window shown below.

After you finish manipulating the window and close it, make sure that you manually close the following window, which does not close automatically.

[Figure]

To Page Top

(3) Action menu access rights

The action menu access rights are controlled by the NNMi roles. The role required for action execution differs depending on the menu item. The following table lists the roles set by default for the menu items.

Table 2‒19: Default roles of menu items
No	Menu item	Role^#
No	Menu item	Definition 1	Definition 2
1	Monitoring Browser	Operator level 1	Operator level 1
2	Resource Browser	Operator level 1	Operator level 1
3	Resource Data Reference	Operator level 1	Administrator
4	Resource Configuration	Administrator	Administrator
5	Resource Reference	Operator level 1	Administrator
6	Process Monitor	Operator level 1	Administrator
7	Process Configuration	Administrator	Administrator
8	Process Reference	Operator level 1	Administrator
9	Report Configuration	Administrator	Administrator
10	Report Browser	Operator level 1	Administrator
11	Monitoring Browser (HTTPS)	Operator level 1	Operator level 1
12	Resource Browser (HTTPS)	Operator level 1	Operator level 1
13	Resource Data Reference (HTTPS)	Operator level 1	Administrator
14	Resource Configuration (HTTPS)	Administrator	Administrator
15	Resource Reference (HTTPS)	Operator level 1	Administrator
16	Process Monitor (HTTPS)	Operator level 1	Administrator
17	Process Configuration (HTTPS)	Administrator	Administrator
18	Process Reference (HTTPS)	Operator level 1	Administrator
19	Report Configuration (HTTPS)	Administrator	Administrator
20	Report Browser (HTTPS)	Operator level 1	Administrator

#:: The default role is set to either definition 1 or definition 2 according to the definition in the imported URL action definition file. For details on the URL action definition file, see 3.1.1 Flow of SSO installation and setup tasks.

The NNMi role required for execution can be changed according to the operational requirements. To change the role, change the role of the menu item in question from the NNMi console. For details, see the NNMi console's Help.

You can select one of the following roles:

Administrator
Operator level 1
Operator level 2

Note: When the URL action definition file is re-imported to NNMi, the role is reset to the default role.

To Page Top

(4) Executing actions

Before you can open the monitoring status display window and other windows as actions, you must specify the URLs of those windows in URL action definitions of NNMi.

From version 09-10, SSO supports distributed system configurations. To execute an SSO action from the Action menu, you must take into consideration the fact that the monitoring manager of each node might be different. Also, you must keep in mind that the URL of each window includes the IP address and port number of the monitoring manager. If the monitoring manager is different, the IP address and port number also are different. Therefore, the NNMi custom attribute function is used to hold the IP address and port number information of the monitoring manager for each node. By registering monitoring manager information as custom attributes, support for SSO in a distributed configuration is provided.

The following subsections describe NNMi custom attributes.

(a) Overview of custom attributes

When an action is executed on a node, the monitoring manager that manages the resource status and application status of that node must be identified. For the monitoring manager to be identified, you must register the information about the monitoring manager on the Custom Attributes tab in NNMi's node window for the target node. On that tab, specify the names and values of custom attributes.

The following table describes the names and values of the custom attributes to be registered.

Table 2‒20: Information registered on the Custom Attributes tab
No	Name	Description
1	jp.co.hitachi.jp1.sso.address	IP address of the monitoring manager that monitors the target node (The IP address of the physical host or the IP address specified for the `change-my-address:` key. If the `ssonnmactaddr.conf` file exists, this item indicates the monitoring manager's IP address specified in the file.)
2	jp.co.hitachi.jp1.sso.agentaddr	IP address of the monitoring server
3	jp.co.hitachi.jp1.sso.consoleweb	Port number specified for `ssoconsoleweb` in the `ssoport.conf` file
4	jp.co.hitachi.jp1.sso.consoleweb.https	Port number specified for `ssoconsolewebhttps` in the `ssoport.conf` file

The custom attributes that must be registered differ according to the node. The following table lists the custom attributes that must be registered for each node.

Table 2‒21: Custom attributes that must be registered for each node
No	Custom attribute	Monitoring manager	Monitoring server
1	jp.co.hitachi.jp1.sso.address	Y	Y
2	jp.co.hitachi.jp1.sso.agentaddr	N^#	Y
3	jp.co.hitachi.jp1.sso.consoleweb	Y	Y
4	jp.co.hitachi.jp1.sso.consoleweb.https	Y	Y

Legend:

Y: Register this attribute.

N: Do not register this attribute.

#:

This attribute must be registered if the monitoring manager is monitoring the monitoring manager itself.

The custom attributes required for executing actions from the Action menu differ according to the action. The following table lists the required custom attributes for each action.

Table 2‒22: Custom attributes required for executing actions from the Action menu
No	Custom attribute	Monitoring status	Window startup
1	jp.co.hitachi.jp1.sso.address	Y	Y
2	jp.co.hitachi.jp1.sso.agentaddr	Y	--
3	jp.co.hitachi.jp1.sso.consoleweb	Y	Y
4	jp.co.hitachi.jp1.sso.consoleweb.https	Y	Y

Legend:

Y: Required

--: Not required

(b) Triggers for registering custom attributes

The following describes the triggers for registering custom attributes.

Registration on the monitoring server node

When all the following conditions are met, the custom attributes are registered on the monitoring server node:
- NNMi cooperation is enabled.
- In the ssoapmon action definition file (ssoapmon.def) or ssocolmng action definition file (ssocolmng.def), the value of the nnm-urlaction-coop: key is on.
- Resource collection conditions or process monitoring conditions are added.
  
  If NNMi cooperation was disabled when the conditions were added, the custom attributes are registered when NNMi cooperation becomes enabled. However, custom attributes are not registered on the monitoring server on which custom attributes had already been registered when the conditions were added.
- Resource collection conditions and process monitoring conditions were already registered when the ssoapmon and ssocolmng daemon processes were started.
  
  Custom attributes are registered only once after these daemon processes start.
Registration on the monitoring manager node

When all the following conditions are met, the custom attributes are registered on the monitoring manager node:
- NNMi cooperation is enabled.
- In the ssoapmon action definition file (ssoapmon.def) or ssocolmng action definition file (ssocolmng.def), the value of the nnm-urlaction-coop: key is on.
- Either of the following conditions is met:
  
  - The ssoapmon or ssocolmng daemon process started (if NNMi cooperation is disabled at startup, the custom attributes are registered when NNMi cooperation becomes enabled).
  
  - The ssoapcom -n command or the ssocolmng -n command is executed.

For details on the ssoapmon action definition file (ssoapmon.def), see 6.3.7 ssoapmon action definition file (ssoapmon.def). For details on the ssocolmng action definition file (ssocolmng.def), see 6.3.8 ssocolmng action definition file (ssocolmng.def).

(c) Triggers for deleting custom attributes

Custom attributes are deleted when:

The ssocadel command is executed.
SSO is uninstalled.

The custom attributes that will be deleted are those that were registered by the monitoring manager that executed the ssocadel command. For details on this command, see ssocadel in 5. Commands.

(d) Notes

After SSO stops, the monitoring manager's IP address and port number registered on the Custom Attributes tab for a node displayed in the NNMi map view remain.
For HTTP-based access, the value of ssoconsoleweb in the ssoport.conf file is used as the port number. For HTTPS-based access, the value of ssoconsolewebhttps in the ssoport.conf file is used as the port number. After you change this value, if you restart only the ssoconsoled daemon process, the action cooperation function does not work correctly. In such a case, restart both the ssocolmng and ssoapmon daemon processes.
Once custom attributes are registered, they are not deleted unless the ssocadel command is executed. Therefore, even after the nnm-urlaction-coop: key is set to off, SSO actions can be executed from the Action menu for any monitoring servers on which custom attributes have been registered. To prevent SSO action execution from the Action menu, execute the ssocadel command to delete the custom attributes.

To Page Top

(5) Notes on map cooperation (action cooperation)

To use the action link function, you must start the ssoconsoled daemon process of the SSO console by using the monitoring manager.
If the URL action of SSO is not defined in NNMi, the SSO menu is not displayed on the NNMi console screen.

To Page Top