User Manual

639
Product Manual Troubleshooting
Note that the virtual and maintenance ports can accept IP address assignments from a DHCP server.
If you manually assigned an IP address to the Vess R2000 but there is a DHCP server on your network, there is
a chance that the server might assign the IP address to another node. You might see a warning to this effect on
your PC’s monitor. If this happens, WebPAM PROe may not be able to connect. See your network administrator
to work out a suitable arrangement.
fibre chAnnel cOnnectiOns
When there is a connection failure, use WebPAM PROe to verify that Vess sees the initiators. See “Viewing a
List of FC Initiators on the Fabric” on page 229.
If Vess sees some initiators but not the one you want, the problem is most likely elsewhere in the loop or fabric.
If Vess does not see any initiators:
• CheckalloftheFibreChannelconnections
• Verifythatallnodesareproperlyconnectedandpowered
• Verifythatthefabricrouterorswitchisproperlyconnectedpowered
For more information, see “Managing Fibre Channel Connections” on page 226.
sAs cOnnectiOns
Faulty SAS expansion connections are suspected when the link port counter reports a large number of bad link
errors.
Link errors can be caused by:
• DebrisblockingtheSAScableconnector
• AfaultySAScable
• AfaultycontrollerorI/OmoduleSASconnector
Blocked Cable Connectors
To check for debris blocking the SAS cable connector:
1. Power down the RAID subsystem and JBOD units.
2. Remove the SAS cable and check all SAS connectors for debris.
3. Clean the connectors as required and reconnect the SAS cable.
4. Power up the subsystems and monitor the link port counter for changes in the rate of link error
accumulation.