Ethernet connectivity from file modules to the control
enclosure
This topic covers troubleshooting Ethernet network connectivity issues between the
file modules and the attached control enclosure. These network paths are used for
all management operations between the file module and the control enclosure.
About this task
This procedure is used to troubleshoot Ethernet network connectivity between the
file modules and the control enclosure. These connections are used for the active
management node on one of the file modules to ssh storage command-line
interface (CLI) commands to the main configuration node canister in a control
enclosure.
There are no direct physical Ethernet connections between the file module
hardware and the control enclosure. All network connections are done through
your network infrastructure. When configuring your network switches, be sure
that there is an available communication path between the file module network
connections and the control enclosure network connections. Ideally the file
modules and control enclosure should be connected to the same 1 Gbps Ethernet
switch
If you want redundant connectivity to the control enclosure from the file modules,
then both 1 Gbps ports from each node canister in the control enclosure are
connected to your network. If you do not want redundancy, connecting port 2 of
the control enclosure node canister to your network is optional.
If you seem to have intermittent management communication problems between
the file module which is the active management node and the control enclosure
CLI, then it is possible that another machine on your network could be using the
IP address used by the control enclosure. Refer to Problem: Another system may be
using the system IP address for how to check for a duplicate IP address on your
network and how to change the control enclosure IP address if necessary.
If the file modules can no longer ssh CLI commands to the storage system CLI
then the first thing to do is make sure that the management IP addresses are
correctly set. You may find the GUI works very slowly in this case, so access the
CLI by using ssh to the log on to the management IP address as admin (default
password admin001).
For example:
ssh admin@<mangementIP>
Use the lsnwmgt CLI command to show you the IP addresses used by the file
modules for management. For example:
[kd52y0g.ibm]$ lsnwmgt
Interface Service IP Node1 Service IP Node2 Management IP Network Gateway VLAN ID
ethX0 9.71.18.160 9.71.18.161 9.71.18.210 255.255.255.0 9.71.18.1
EFSSG1000I The command completed successfully.
Use the lsstoragesystem CLI command to show you the IP address that the active
management node, running on one of the file modules, will use to ssh commands
to the storage system CLI. For example:
68 Storwize V7000 Unified: Problem Determination Guide 2073-720
To Next Page
Loading...
Need help?
General
