Resolving a problem with accessing the management GUI

If you are unable to connect to the management GUI from your web browser and received a Page not found or similar error, this information might help you resolve the issue.

If you are unable to connect to the management GUI from your web browser and received a Certificate expired or similar error, see Resolving a problem with SSL certificates.

If you are unable to connect to the management GUI from your web browser and received a cipher error, SSL error, TLS error, or handshake error or similar error, see Resolving a problem with SSL/TLS clients.

Consider the following possibilities if you are unable to connect to the SAN Volume Controller management GUI:
  • You cannot connect if the system is not operational with at least one node online. If you know the service address of a node, either use the service assistant to verify that the state of at least one node is active, or if the node is not active, use the LEDs to see whether any node state is active.

    If there is not a node with a state of active, resolve the reason why it is not in active state. If the state of all nodes is candidate, then there is not a clustered system to connect to. If the node state is service, see the topic that contains information about fixing node errors.

  • Ensure that you are using the correct system IP address. If you can access the service assistant by using the service address or the technician port of a node, log in to find the node and system addresses on the Access tab of the Node Detail table.
  • Ensure that all nodes have an Ethernet cable that is connected to port 1 and that the port is working. Use the Ethernet LEDs to understand the port status.
  • Ping the management address to see whether the Ethernet network permits the connection. If the ping fails, check the Ethernet network configuration to see whether there is a routing or a firewall issue. Ensure that the Ethernet network configuration is compatible with the gateway and subnet or prefix settings. Ensure that you did not use the Ethernet address of another device as the management address. If necessary, modify your network settings to establish a connection.
  • If the system IP address settings are incorrect for your environment, take these steps:
    1. You can determine this if you can access the service assistant on any node. Access the service assistant by using the technician port on the rear of a node if it cannot be accessed over your network. Alternatively use the summary data returned, when a USB flash drive is plugged into a node.
    2. You can temporarily run the management GUI on the service address of the configuration node. Point your browser to service address/gui. For example, if the service address of the configuration node is 11.22.33.44, point your browser to 11.22.33.44/gui.
    3. In the management GUI, use the options in the Settings > Network to change the management IP settings.
    4. As an alternative to using the management GUI, you can use the chsystemip CLI command to correct the system IP address settings by using ssh to the service IP of the configuration node.