IBM PowerHA SystemMirror User Interface
This chapter covers the following areas of the IBM PowerHA SystemMirror User Interface (SMUI):
– Planning
– General
– Network
9.1 Introduction
New in PowerHA SystemMirror Version 7.2.1 is a browser-based GUI to monitor your cluster environment, which is called the SMUI.
Highlights
The SMUI provides the following advantages over the PowerHA SystemMirror command line:
•Monitors the status for all clusters, sites, nodes, and resource groups (RGs) in your environment.
•Scans event summaries and read a detailed description for each event. If the event occurred because of an error or issue in your environment, you can read suggested solutions to fix the problem.
•Searches and compares log files. There are predefined search terms along with the ability to enter your own:
– Error
– Fail
– Could not
Also, the format of the log file is easy to read and identify important information. While viewing any log that has multiple versions, such as hacmp.out and hacmp.out.1, they are merged together into a single log.
The logs include:
– hacmp.out
– cluster.log
– clutils.log
– clstrmgr.debug
– syslog.caa
– clverify.log
– autoverify.log
•View properties for a cluster, such as the PowerHA SystemMirror version, name of sites and nodes, and repository disk information.
Filesets
The SMUI consists of the following filesets:
cluster.es.smui.agent This fileset installs the agent files. Installing this fileset does not start the agent. This fileset is automatically installed when you use the smit install_all command to install PowerHA SystemMirror Version 7.2.1 or later. This fileset is automatically installed when you add clusters to the PowerHA SystemMirror GUI.
cluster.es.smui.common This fileset installs common files that are required by both the agent and the PowerHA SystemMirror GUI server. The Node.js files are an example of common files. This fileset is automatically installed when you use the smit install_all command to install PowerHA SystemMirror Version 7.2.1 or later.
cluster.es.smui.server This fileset installs the PowerHA SystemMirror GUI server files. The node on which you install the cluster.es.smui.server fileset is known as the PowerHA SystemMirror GUI server. Installing this fileset does not start the server. You do not need to install this fileset on every node in the cluster. You can install this fileset on a single node to manage multiple clusters. Also, you do not have to install it on any cluster node as you can also install it on a stand-alone AIX system.
9.2 Installation
Before installing the SMUI, your environment must meet certain requirements, as explained in 9.2.1, “Planning” on page 301.
|
Tip: A demonstration of installing the PowerHA SystemMirror User Interface by using a server that has no internet access is demonstrated in this YouTube video.
|
9.2.1 Planning
To use the SMUI, proper planning is necessary. The cluster nodes and SMUI server must be at one of the following levels of AIX:
•IBM AIX 6.1 with Technology Level 9 with Service Pack 15 or later
•IBM AIX 7.1 with Technology Level 3 or later
•IBM AIX Version 7.2 or later
Also, these additional cluster filesets must be installed on all nodes in the cluster:
•cluster.es.smui.agent
•cluster.es.smui.common
For the SMUI server, these filesets must be installed:
•cluster.es.smui.common
•cluster.es.smui.server
All of these filesets are available in the PowerHA SystemMirror 7.2.1 installation media.
Although the SMUI server can be a cluster node, it is expected to be on a separate stand-alone AIX system. Also, ideally, the SMUI server should have internet access to download additional open source packages as required. However, this section describes how to work around this requirement.
The SMUI is supported only on the following web browsers:
•Google Chrome Version 50 or later
•Firefox Version 45 or later
9.2.2 SMUI Client: Cluster nodes
For all client cluster nodes, the only thing that must be done is install the two additional filesets cluster.es.smui.agent and cluster.es.smui.common. To install them, complete the following steps:
1. From the command line, run the smit install_all command.
2. Specify the input device or directory that contains the filesets.
3. Select the filesets from the list.
4. Press Enter to install the fileset.
9.2.3 SMUI server
For the SMUI server, two additional filesets, cluster.es.smui.common and cluster.es.smui.server, must be installed, followed by the execution of smuiinst.ksh script. The smuiinst.ksh command automatically downloads and installs the remaining files that are required to complete the PowerHA SystemMirror GUI installation process. These downloaded files are not shipped in the filesets because the files are licensed under the General Public License (GPL).
To install, complete the following steps:
1. From the command line, run the smit install_all command.
2. Specify the input device or directory that contains the filesets.
3. Select the filesets from the list.
4. Press Enter to install the fileset.
The PowerHA SystemMirror GUI server should have internet access to run the smuiinst.ksh command. However, if the server does not have internet access, complete the following steps:
1. Copy the smuiinst.ksh file from the node to a system that is running the AIX operating system that has internet access. In our case, we copy it to our NIM server.
2. Run the smuiinst.ksh -d /directory command, where /directory is the location where you want to the download the files. We saved it a directory that was also NFS exported to our SMUI server.
The following additional packages were downloaded:
– bash-4.2-5.aix5.3.ppc.rpm
– cpio-2.11-2.aix6.1.ppc.rpm
– gettext-0.17-6.aix5.3.ppc.rpm
– info-4.13-3.aix5.3.ppc.rpm
– libgcc-4.9.2-1.aix6.1.ppc.rpm
– libgcc-4.9.2-1.aix7.1.ppc.rpm
– libiconv-1.13.1-2.aix5.3.ppc.rpm
– libstdc++-4.9.2-1.aix6.1.ppc.rpm
– libstdc++-4.9.2-1.aix7.1.ppc.rpm
– readline-6.2-2.aix5.3.ppc.rpm
3. Copy the downloaded files to a directory on the PowerHA SystemMirror GUI server. In our case, we use an NFS-mounted directory, so we skip this step.
4. From the PowerHA SystemMirror GUI server, run the smuiinst.ksh -i /directory command, where /directory is the location where you copied the downloaded files.
During the smuiinst.ksh execution, the rpms are installed, the SMUI server service and uiserver are started, and a message displays a URL for the PowerHA SystemMirror GUI server similar to what is shown in Figure 9-1. Enter the specified URL into a web browser and the SMUI login window is displayed, as shown in Figure 9-2.
|
# /usr/es/sbin/cluster/ui/server/bin/smuiinst.ksh -i ./
Attempting to install any needed prerequisites.
Configuring the database in "/usr/es/sbin/cluster/ui/data/sqlite/smui.db" using
"/usr/es/sbin/cluster/ui/server/node_modules/smui-server/resources/0.13.0-ddl.sq l"...
The database is now configured.
Attempting to start the server...
The server was successfully started.
The installation completed successfully. To use the PowerHA SystemMirror GUI,
open a web browser and enter the following URL:
https://shawnssmui.cleartechnologies.net:8080/#/login
After you log in, you can add existing clusters in your environment to the
PowerHA SystemMirror GUI.
|
Figure 9-1 SMUI server installation script output
Figure 9-2 SMUI login window
9.2.4 Adding and removing clusters
After logging in, you can see text on the left frame to add a cluster. You can choose it or follow these steps:
1. Click the keypad icon in the top center of the window.
2. Click Add clusters.
3. Enter either host name or IP address of one of the cluster nodes, and the user and password as required.
4. Click Discover clusters.
These steps are shown within the SMUI in Figure 9-3.
|
Attention: During our testing, we had mixed results when using the host name to gather all the cluster data. However, the IP address seemed to be reliable. At the time of writing, this was a known issue by development. If you experience the same issue, then contact IBM PowerHA support.
|
Upon successful discovery, the cluster information is shown, and you can close the window, as shown in Figure 9-4 on page 305.
Figure 9-3 Add clusters
Figure 9-4 Discovered cluster
To remove a cluster:
1. Click the keypad icon in the top center of the window.
2. Click Remove clusters.
3. Check the box next to the correct cluster.
4. Click Remove.
These steps are shown within the SMUI in Figure 9-5.
Figure 9-5 Remove clusters
9.3 Navigating
The SMUI provides a web browser interface that can monitor your PowerHA SystemMirror environment. The following sections explain and show examples of the SMUI.
9.3.1 Event summaries
In the PowerHA SystemMirror GUI, you can quickly view all events for a cluster in your environment. Figure 9-6 on page 307 identifies the different areas of the PowerHA SystemMirror GUI that are used to view events:
1. Navigation pane
This area displays all the clusters, sites, nodes, and RGs in a hierarchy that is discovered by the PowerHA SystemMirror GUI. You can click to view resources for each cluster.
Notice that the clusters are displayed in alphabetical order. However, any clusters that are in a Critical or Warning state are listed at the top of the list.
2. Scoreboard
This area displays the number of clusters, nodes, and RGs that are in a Critical, Warning, or Maintenance state. You can click Critical, Warning, or Maintenance to view all the messages for a specified resource. For example, in Figure 9-6 on page 307, there are six RGs that are identified. If the warning icon is highlighted and you click the warning icon, all messages (critical, warning, and normal) for the RGs are displayed.
3. Event filter
In this area, you can click the icons to display all events in your environment that correspond to a specific state. You can also search for specific event names.
4. Event timeline
This area displays events across a timeline of when the event occurred. This area allows you to view the progression of events that lead to a problem. You can zoom in and out of the time range by using the + or – keys or by using the mouse scroll wheel.
5. Event list
This area displays the name of the event, the time when each event occurred, and a description of the event. The information that is displayed in this area corresponds to the events that you selected from the event timeline area. The most recent event that occurred is displayed first. You can click this area to display more detailed information about the event, such as possible causes and suggested actions.
Figure 9-6 Event summaries
You can customize the view that is shown in Figure 9-7 by hiding either the score board, as shown in Figure 9-8, or hiding the timeline, as shown in Figure 9-9 on page 309.
Figure 9-7 Customize to no scoreboard
Figure 9-8 No scoreboard view
Figure 9-9 No timeline view
9.3.2 Log files
To easily compare and identify the log files that are displayed in the PowerHA SystemMirror GUI, the log files correspond to a particular color. For example, in Figure 9-10, all the log files for the hacmp.out file are displayed in a blue color, and all the log files for the cluster.log file are displayed in a yellow color.
Figure 9-10 Log viewing
1. You click the following predefined search terms to locate the specified term in the log file:
– Error
– Fail
– Could not
You can click the < and > arrows to move to the previous and next instance of the search term in the selected log file. You can also enter your own search term and create a user-defined search term. A user-defined search term functions similar to the predefined search terms. For example, in Figure 9-10 on page 309, preamble is a user-defined search term.
2. Log file selection
You can view the following log files:
– hacmp.out
– cluster.log
– clutils.log
– clstrmgr.debug
– syslog.caa
– clverify.log
– autoverify.log
3. Log file viewer
In this area, you can view the log file information. To easily locate important information in the log files, the scripts are within collapsed sections in the log files. You can expand sections within the log file to view more detailed scripts. You can also open the log file in a separate browser window by clicking the right up diagonal arrow.
9.3.3 General
This window gives an overall view of the cluster configuration. A small portion of it is shown in Figure 9-11. You can expand or condense any or all sections as wanted. Currently, it can only be viewed and not saved in a report. IBM intends to deliver it as a possible enhancement.
Figure 9-11 General cluster configuration
9.3.4 Network
This window displays the cluster networking topology, as shown in Figure 9-12.
Figure 9-12 Network information
9.3.5 Terminal session
The terminal session can be accessed from any of the three previous windows: Logs, General, and Network. You can open a terminal session directly to any known cluster node. A system name, identification, and password are all required, as shown in Figure 9-13.
Figure 9-13 Terminal session
9.4 Troubleshooting
This section provides details about how to troubleshoot issues with your cluster.
9.4.1 Log files
As is the case with most PowerHA components, there is a set of log files specifically for the SMUI. These log files are as follows:
smui-server.log This log file is in the /usr/es/sbin/cluster/ui/server/logs/ directory. The smui-server.log file contains information about the PowerHA SystemMirror GUI server.
smui-agent.log This log file is in the /usr/es/sbin/cluster/ui/agent/logs/ directory. The smui-agent.log file contains information about the agent that is installed on each PowerHA SystemMirror node.
notify-event.log This log file is in the /usr/es/sbin/cluster/ui/agent/logs/ directory. The notify-event.log file contains information about all PowerHA SystemMirror events that are sent from the agent to the PowerHA SystemMirror server.
9.4.2 Login problems
If you are experiencing problems logging in to the PowerHA SystemMirror GUI, complete the following steps:
1. Check for issues in the /usr/es/sbin/cluster/ui/server/logs/smui-server.log file.
2. Verify that the smuiauth command is installed correctly. Also, verify that the smuiauth command has the correct permissions by running the ls -l command from the /usr/es/sbin/cluster/ui/server/node_modules/smui-server/lib/auth/smuiauth directory. An output similar to the following example is displayed:
-r-x------ 1 root system 21183 Oct 18 22:56
3. Verify that you can run the smuiauth command by running the smuiauth -h command.
4. Verify that the pluggable authentication module (PAM) framework is configured correctly by locating the following lines in the /etc/pam.conf file:
smuiauth auth required pam_aix
smuiauth account required pam_aix
The PAM configuration occurs when you install the cluster.es.smui.server fileset.
9.4.3 Adding clusters
If you are not able to add clusters to the PowerHA SystemMirror GUI, complete the following steps:
1. Check for issues in the /usr/es/sbin/cluster/ui/server/logs/smui-server.log file:
a. If SFTP-related signatures exist in the log file, such as Received exit code 127 during the time of establishing an SFTP session, a problem exists with the SSH communication between the PowerHA SystemMirror GUI server and the cluster you are trying to add.
b. From the command line, verify that you can connect to the target system by using SSH File Transfer Protocol (SFTP). If you cannot connect, verify that the daemon is running on the PowerHA SystemMirror GUI server and the target node by running the ps –ef | grep –w sshd |grep –v grep command. You can also check the SFTP subsystem configuration in the /etc/ssh/sshd_config file and verify that following path is correct:
Subsystem sftp /usr/sbin/sftp-server
If the path is not correct, you must enter the correct path in the /etc/ssh/sshd_config file, and then restart the sshd subsystem.
2. Check for issues in the /usr/es/sbin/cluster/ui/agent/logs/agent_deploy.log file on the target cluster.
3. Check for issues in the /usr/es/sbin/cluster/ui/agent/logs/agent_distribution.log file on the target cluster.
9.4.4 Status not updating
If the SMUI is not updating the cluster status or displaying new events, complete the following steps:
1. Check for issues in the /usr/es/sbin/cluster/ui/server/logs/smui-server.log file.
2. Check for issues in the /usr/es/sbin/cluster/ui/agent/logs/smui-agent.log file. If certificate-related problems exist in the log file, the certificate on the target cluster and the certificate on the server do not match. An example of a certificate error follows:
WebSocket server - Agent authentication failed, remoteAddress:::ffff:10.40.20.186, Reason:SELF_SIGNED_CERT_IN_CHAIN
..................Content has been hidden....................
You can't read the all page of ebook, please click here login for view all page.