When a new node is added or when a new cluster is installed and configured, the GUI may not start on the console node after a failover

Welcome to Cohesity Documentation.

Ask me anything. From setup and configuration to troubleshooting, architecture, features, and release updates, I'm here to help.

AI may make mistakes. Always verify critical information.

COHESITY Documentation

Explore our documentation to get started, discover products & new features, access troubleshooting guides, register sources, platforms support.

Products

Data Security Alliance

COHESITY Documentation

Explore our documentation to get started, discover products & new features, access troubleshooting guides, register sources, platforms support.

Products

Data Security Alliance

When a new node is added or when a new cluster is installed and configured, the GUI may not start on the console node after a failover — Access Appliances 7.4.3 | Cohesity Documentation

Home

Veritas Access Appliance Release Notes

Known issues

Access Appliance known issues

GUI issues

When a new node is added or when a new cluster is installed and configured, the GUI may not start on the console node after a failover

Veritas Access Appliance Release Notes · PDF

Download PDF

When node failover occurs for a console node, the GUI services are expected to auto-start on the failed-over console node. But it fails to start as the GUI is not properly configured on all the nodes. You cannot use the GUI to manage the storage on the cluster.

Workaround:

Run the system guienable command to enable the GUI.

Feedback

Was this page helpful?

GUI issues

When an earlier version of the Access Appliance cluster is upgraded, the GUI shows stale and incomplete data

Feedback

Was this page helpful?