IBM Support

Console reports system status is "Unconnected" and storage is "UNKNOWN" after node failover

Fix Readme


Abstract

If there is a node failure in the system, HA manager will rebalance the MLNs with left nodes and recover the application. The master node is NOT the first node when this happens. However, due to incorrect LDAP configuration, web console displays the System State as Unconnected and Storage as UNKNOWN.

Content

Screenshot for the state noted in the abstract:


Also, the following pages might not work properly:

  • Home page
  • MONITOR-Dashboard
  • MONITOR-System-Hardware
  • MONITOR-System-Software
  • MONITOR-System-Storage
  • MONITOR-System-Data Slices
  • MONITOR-System-Notifications
  • SETTINGS-Call Home
  • HELP-PMRs
WORKAROUND:
Restarting web console fixes the issue. 



If you can't access the system as root user (root user is locked:
NOTE: These steps restart Db2 and cause an outage.
1. Run the apstop command;
2. Run the apstart command;
3. Check the status of application with ap sw command


If you can access the system as root user (IBM service personnel only):
1. Use ap node command to get the current master node.
2. On the master node, run the following command:
sudo /usr/bin/docker exec -it dashDB su - db2inst1 /opt/ibm/dsserver/bin/stop.sh
3. Wait for the HA manager to recover the web console. You can check the status of the web console with the following command:
sudo /usr/bin/docker exec -it dashDB status
NOTE: the above step generates an alert that should be ignored. It does not cause a Db2 outage.

[{"Product":{"code":"SSHRBY","label":"IBM Integrated Analytics System"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Component":"--","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"Version Independent","Edition":"All Editions","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
17 October 2019

UID

swg22010869

Page Feedback