McDATA 3000 manual Basic Troubleshooting Steps for FC/SCSI Tape Pipelining

13

Troubleshooting FC/SCSI Tape Pipelining (Device Extension)

Basic Troubleshooting Steps for FC/SCSI Tape Pipelining

1.Can the UltraNet Edge 3000 communicate with each other?

a.Run the tankio stats 1 command. (See the “TANKIO” section in this chapter.)

b.Run either the amdenet stats command or the gnic3 stats command. (See the “AMDENET 10/100 WAN or Maintenance Interface” or the “GNIC3 Gigabit Ethernet WAN” sections in this chapter).

2.Is the Fibre Channel link up?

a.Run the fcxl2 dump port command.

b.Check the State status. If State is Offline:

—Check to make sure your cables are plugged in appropriately.

—If the UltraNet Edge 3000 is not plugged in to a Switch, but instead plugged directly into a server or device, make sure the server or device is configured for Public or Private Loop.

—If you are directly connecting a server or device into the UltraNet Edge 3000, verify that the HBA, bridge, or device is included in the supported matrix.

3.Can the UltraNet Edge 3000 access the server(s) and device(s)? a. Run the fcxl2 dump fcp_login command.

b. Can you see the server or device PortID and WWN?

—Are the Brocade zones configured correctly?

—Refer to Chapter 9 for Brocade zoning examples, or consult the Brocade Zoning documentation.

4.Are the devices mapped?

a. Run the ttag luns command.

This command outputs a table which displays the UltraNet Edge 3000’s FC/SCSI Tape Pipelining LUN map. This table displays what WWN entries in the LUN map have been statically configured and dynamically discovered.

b. Run the ttag probe command.

13-14 McDATA UltraNet Edge 3000 User Guide