Troubleshooting FC/SCSI Tape Pipelining (Device Extension)

 

 

 

 

 

 

 

 

 

 

 

V002

Basic hardware (serial port, PCI, network)

 

initialization

 

 

failed

 

V003

Kernel configuration failed

 

V004

Instruction cache enabling failed

 

V005

Kernel root task creation failed

 

V007

Memory pool initialization failed

 

V008

MMU initialization failed

 

V009

System timer initialization failed

 

V010

Console initialization failed

 

V011

Filesystem initialization failed

 

V012

Real-time clock initialization failed

 

V013

I2C initialization failed

 

V014

Disk initialization failed

 

V015

Network initialization failed

 

V016

Misc. failures

 

V017

System symbol table creation failed

 

V018

Misc library initialization failed

 

V019

Script running failure

 

V020

Shell initialization failure

 

VXOK

Kernel ok

 

V020-V027Network protocol initialization failed

V028-V030 unused

V030 Can't load network config info from NVRAM or

BOOTP failure.

V031-V037Network stack setup failed

V038

unused

Kernel ok

 

VXOK

Troubleshooting FC/SCSI Tape Pipelining (Device Extension)

The following section provides basic troubleshooting steps for your UltraNet Edge 3000’s FC/SCSI Tape Pipelining (Device Extension) network.

This section is not intended to be an exhaustive troubleshooting guide for FC/SCSI Tape Pipelining, also called Device Extension, but provides basic steps to provide visibility from the tape device(s) to the server. This section assumes the user has some SCSI experience.

NOTE: Tuning Veritas NetBackup or Tivoli Storage Manager may result in higher throughput through the UltraNet Edge 3000. If you need assistance with application tuning, contact McDATA Advanced Services.

Troubleshooting and Diagnostics

13-13

 

 

13

Page 325
Image 325
McDATA 3000 manual Troubleshooting FC/SCSI Tape Pipelining Device Extension, Vxok