If you are having problems attaching to the Ethernet hosts, your problem might be related
to the network, the
system,
or the host. If you face a ping issue with the host after changing the MTU of ethernet ports, you
need to run rmip command to remove the IP address from the port and then
consecutively execute a mkip command to add the IP address in order to resolve
the issue.
Note: For
more information on the requirements, see Concepts
section.
For network problems, you can attempt any of the following
actions:
- Test your connectivity between the host and
system ports.
- Try to ping the system from the host.
- Ask the Ethernet network administrator to check the firewall and router settings.
- Check that the subnet mask and gateway are correct for the
system host configuration.
Using the management GUI for system
problems, you can attempt any of the following actions:
- View the configured node port IP addresses.
- View the list of volumes that are mapped to a host to ensure that the volume host mappings are
correct.
- Verify that the volume is online.
For problems with iSCSI-attached hosts, you can attempt any of the following actions:
- Verify that the host qualified name (IQN) is correctly configured.
- Use operating system utilities (such as Windows device
manager) to verify that the device driver is installed, loaded, and operating correctly.
- If you configured the VLAN, check that its settings are correct. Ensure that Host Ethernet port,
system Ethernet ports IP address, and Switch port are on the same
VLAN ID. Ensure
that on each VLAN, a different subnet is used. Configuring the same subnet on different VLAN
IDs can cause network connectivity problems.
- For iSCSI discovery or login failure, verify that the target IP and
host object are part of the same portset.
- For missing target IP in the discovery records, verify that the
target IP and the host object are part of the same portset.