Adding EML to CentOS5.5

Thread Tools Search this Thread
Operating Systems Linux Red Hat Adding EML to CentOS5.5
# 1  
Old 08-12-2011
Adding EML to CentOS5.5


I've just installed CentOS 5.5 on HP Proliant DL380G5 with two FC HBA and now I'm struggling with adding HP EML103e connected through two Brocade SAN switches. Tape library has two tape drives, each in different fabric. Robotics connected to both fabrics. Zoning is ok - OS sees drives' and robotics' ports, as well as EML sees host ports, but dmesg shows no tape devices defined. /sys/class/fc_remote_port/rport*/port_name shows correct EML WWNs and */port_state shows Online, but OS cannot recognize it as tape drives. I also tried to investigate the problem using QLogic SANsurfer and it shows Offline in front of drive ports. Command View TL shows all drives as Active and Available, FC ports are up

What did I miss? Could anyone please suggest something to find out what went wrong?..

Thanks in advance
Login or Register to Ask a Question

Previous Thread | Next Thread

10 More Discussions You Might Find Interesting

1. UNIX for Beginners Questions & Answers

Adding to an array in an external file, and adding elements to it.

I have an array in an external file, "array.txt", which contains: char *testarray={"Zero", "One", "Two", "Three", "Four", "Five", "Six", "Seven", "Eight", "Nine"};I want to be able to add an element to this array, and have that element display, whenever I call it, without having to recompile... (29 Replies)
Discussion started by: ignatius
29 Replies

2. Hardware

Bumblebee for CentOS5/RHEL5

I have a laptop running CentOS 5.9 with switchable/hybrid graphics (Intel integrated and Nvidia). For now, have managed to successfully install Nvidia driver using file from Nvidia website, but failed to start xserver. To use both adapters I need to install... (0 Replies)
Discussion started by: cooltoad
0 Replies

3. Red Hat

Mounting NFS (CentOS5.6 x64bit) issue on CentOS6.4 x64bit

Hello, We have NFS server setup on CentOS5.6 x64bit with nfs 3 version. Now we have setup a another server CentOS6.4 x64 bit and going to mount nfs location (Which setup on CentOS5.6 x64bit). Now when i am mounting this location on CentOS6.4 x63 bit, below error is displaying. # mount -o... (2 Replies)
Discussion started by: sunnysthakur
2 Replies

4. UNIX for Advanced & Expert Users

NDMP To Backup a Disk Array to HP B6200, EML 103e Tape Library

Hi All, Seeking information on the following and perhaps a bit of insight and opinions: I would like to look into using NDMP to backup a disk array using NetBackup 7.5 to HP B6200 StoreOnce Backup System (i.e. Virtual Tape Library) as well as physical tape library. Does anyone think... (0 Replies)
Discussion started by: zixzix01
0 Replies

5. Solaris

Add new EML 103e Tape Library in SUN Solaris Host to implement HP DP

Hi, Our environment is SUN Solaris. We have purchased HP EML 103e tape library. Can you please let me know do I need to install any Driver of newly added Tape Library to see from the Solaris Host? or how can i see the tape library from my Solaris hosts. Thanks, Hassan (0 Replies)
Discussion started by: M_Hassan
0 Replies

6. Shell Programming and Scripting

Remove lines if some data is the same: Centos5 / bash

Ok what i have is 8 separate files based on how many IP's are associated with the domain. I want to limit duplication of ip's within the individual files (ie. i don't care if the same ip is in 1 IP file and 4 IP file). Can someone help me with how to go through the files and remove lines that have... (3 Replies)
Discussion started by: oly_r
3 Replies

7. Shell Programming and Scripting

Adding new lines to a file + adding suffix to a pattern

I need some help with adding lines to file and substitute a pattern. Ok I have a file: #cat names.txt name: John Doe stationed: 1 name: Michael Sweets stationed: 41 . . . And would like to change it to: name: John Doe employed permanently stationed: 1-office (7 Replies)
Discussion started by: hemo21
7 Replies

8. Virtualization and Cloud Computing

Install Xen vm on centos5.5 crashed "x00\x00\x00\x00\"

Hi, everyone: I'm new to xen. When I install a vm on centos5.5, I got xen crashed: # virt-install -n centos5 -r 512 --vcpus=1 --disk path=/home/mycoy/centos5.img,size=8 --nographics -l when... (1 Reply)
Discussion started by: mycoy
1 Replies

9. Programming

pthread_mutex_trylock() overwrites global variable on CentOS5

Hi all, I am new to linux and got problem with pthread_mutex_trylock(). I have used mutex in my code. When I try to call pthread_mutex_trylock() on RECURSIVE type of mutex it overwrites adjacent memory location (that is global variable of type structure say x, memory allocated using malloc()). ... (5 Replies)
Discussion started by: liveshell
5 Replies

10. UNIX for Dummies Questions & Answers


Hi All i need a add recored like DateOfDU2=245,Time=00326 (in milli secounds ) DateOfDU2=245,Time=00347 DateOfDU2=245,Time=00258 DateOfDU2=246,Time=00325 DateOfDU2=246,Time=00408 DateOfDU2=246,Time=00257 DateOfDU2=247,Time=00037 DateOfDU2=247,Time=00417 DateOfDU2=247,Time=00420... (1 Reply)
Discussion started by: nalakaatslt
1 Replies
Login or Register to Ask a Question
FMS(8)							       AFS Command Reference							    FMS(8)

fms - Determine a tape's capacity and a tape device's filemark size SYNOPSIS
fms -tape <tape special file> [-help] fms -t <tape special file> [-h] DESCRIPTION
The fms command determines the capacity of the tape currently in the tape device identified by the -tape argument, along with the size of the filemark for the device. The filemark is also referred to as the device's end-of-file (EOF) marker, and can differ for each combination of tape and tape device. As the Tape Coordinator writes a dump, it writes a filemark between the data included from each volume and also tracks the amount of space left before the end of the tape (EOT). For some tape devices, the filemark is large enough (multiple megabytes) that failure to consider it leads the Tape Coordinator significantly to overestimate the available space. The intended use of this command is to determine tape capacity and filemark size values that can be specified in a tape device's entry in the /var/lib/openafs/backup/tapeconfig file. For certain types of tape drives, the Tape Coordinator operates more efficiently when the tapeconfig file lists accurate values. For further discussion, see the OpenAFS Administration Guide chapter on configuring the Backup System. Insert a tape in the drive before issuing this command. CAUTIONS
Do not use this command on compressing tape devices in compression mode or with tape devices that handle tapes of multigigabyte (or multiterabyte) capacity. It does not produce accurate results in those cases. For alternate suggestions on the values to record in the tapeconfig file for compressing drives, see the OpenAFS Administration Guide chapter on configuring the Backup System. Running the command completely overwrites the tape, so use a blank one or one that can be recycled. Because it writes filemarks to the complete length of the tape, the command can take from several hours to more than a day to complete. OPTIONS
-tape <tape special file> Specifies the UNIX device name of the tape device for which to determine filemark size and the capacity of the tape it currently contains. The format varies on different system types, but usually begins with /dev; an example is /dev/sd0a. -help Prints the online help for this command. All other valid options are ignored. OUTPUT
The command generates output both on the standard output stream and in the fms.log file that it creates in the current working directory. The output reports the capacity of the tape in the device and the device's filemark size. The first few lines of output include status information about the execution of the command, including such information as the number of blocks and the number of file marks written to the tape by the command. The last two lines of both screen and file output provide the following information: o "Tape capacity is number bytes": specifies the size, in bytes, of the tape in the device. o "File marks are number bytes": specifies the device's filemark size in bytes. The following message indicates that the fms command interpreter cannot access the tape device. The command halts. Can't open tape drive I<device> The following message indicates that the command interpreter cannot create the fms.log log file. Again, the command halts. Can't open log file EXAMPLES
The following command illustrates the output for the device called /dev/rmt1h: % fms /dev/rmt1h wrote block: 130408 Finished data capacity test - rewinding wrote 1109 blocks, 1109 file marks Finished file mark test Tape capacity is 2136604672 bytes File marks are 1910205 bytes The following appears in the fms.log file: fms test started wrote 9230 blocks Finished file mark test Tape capacity is 151224320 bytes File marks are 2375680 bytes PRIVILEGE REQUIRED
The issuer must be able to insert and write to files in the currently working directory, if the fms.log file does not already exist. If it already exists, the issuer need only be able to write to it. SEE ALSO
fms.log(5), tapeconfig(5) COPYRIGHT
IBM Corporation 2000. <> All Rights Reserved. This documentation is covered by the IBM Public License Version 1.0. It was converted from HTML to POD by software written by Chas Williams and Russ Allbery, based on work by Alf Wachsmann and Elizabeth Cassell. OpenAFS 2012-03-26 FMS(8)