If you are unable to display the service assistant on your
browser, you have several options.
- Each node canister runs its own service assistant. Each service
assistant can be used to administer the node on which it runs and
also the other node canister, provided there is no connectivity error
preventing the nodes from communicating. This means there are several
paths through which service tasks can be administered to a node.
- The URL to point your browser at to access a service assistant
always looks like IP address/service. The IP address can be a service IP address of
a node, or it can be a system IP address. If you use a system IP address
you will be connected to the service assistant on the configuration
node.
- Service addresses are configured on Ethernet port 1 of each node
canister. Verify that an Ethernet cable is connected to this port
and to an active port on your Ethernet network. See Procedure: Finding the status of Ethernet connections for details.
- A default service address is initially assigned to each node canister
(see Problem: node canister service IP address unknown). It might not be possible to connect to a node canister
service assistant if multiple node canisters on the same network are
using the default IP addresses.
- To find the IPv4 and IPv6 addresses that are configured on the
node, go to Problem: node canister service IP address unknown.
- Ensure that the node is configured with valid service addresses.
- Ping the service IP address to see if the Ethernet network permits
the connection. If the ping fails, check the Ethernet network configuration
to see if there is a routing or a firewall issue.
- You cannot connect to the service assistant if the node canister
is not able to start the machine code.
To verify that the LEDs indicate that the node machine code is running,
see Procedure: Understanding the system status using the LEDs.