Sun V880 Fibre channel drive giving Loop OFFLINE message

Hi
I have a v880 with two drives and drive at slot 0 is giving below message every few minutes and drive operation (read and write) halts.
Jul 12 12:36:11 suntest1 qlc: [ID 686697 kern.info] NOTICE: Qlogic qlc(0): Loop ONLINE
Jul 12 12:36:28 suntest1 qlc: [ID 686697 kern.info] NOTICE: Qlogic qlc(0): Loop OFFLINE
Below is message i am seeing in /var/adm/messages.
# tail -f /var/adm/messages
Jul 12 12:34:59 suntest1 scsi: [ID 107833 kern.warning] WARNING: /pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w2100000c50eb2098,0 (ssd1):
Jul 12 12:34:59 suntest1 SCSI transport failed: reason 'tran_err': giving up
Jul 12 12:36:00 suntest1 qlc: [ID 686697 kern.info] NOTICE: Qlogic qlc(0): Loop OFFLINE
Jul 12 12:36:01 suntest1 qlc: [ID 686697 kern.info] NOTICE: Qlogic qlc(0): Loop ONLINE
Jul 12 12:36:05 suntest1 qlc: [ID 686697 kern.info] NOTICE: Qlogic qlc(0): Loop OFFLINE
Jul 12 12:36:06 suntest1 scsi: [ID 243001 kern.warning] WARNING: /pci@8,600000/SUNW,qlc@2/fp@0,0 (fcp0):
Jul 12 12:36:06 suntest1 PLOGI to D_ID=0xef failed: State:Operation Success, Reason:Undefined. Giving up
Jul 12 12:36:11 suntest1 qlc: [ID 686697 kern.info] NOTICE: Qlogic qlc(0): Loop ONLINE
Jul 12 12:36:28 suntest1 qlc: [ID 686697 kern.info] NOTICE: Qlogic qlc(0): Loop OFFLINE
Jul 12 12:36:34 suntest1 qlc: [ID 686697 kern.info] NOTICE: Qlogic qlc(0): Loop ONLINE
System is running solaris 9 and I have following qlogic driver installed.
# modinfo|grep qlc
26 1215a7d 26c61 153 1 qlc (Qlogic FCA Driver v0.40.5)
Any help will be appreciated.
Thanks
Anoop

What is the status of the HDD of this particular path ?
WARNING: /pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w2100000c50eb2098,0 (ssd1):
You can verify with format or iostat -En
Regards
Ravi

Similar Messages

FreeNAS 9.3 with HP M6412-A Fibre Channel Drive Enclosures

Hi,I have acquired two HP M6412-A Fibre Channel Drive Enclosures with 14 dual-port SAS15K disk drives (7 per enclosure) in a recent company takeover.I do not have any HP software licenses for the HP EVA4400 Dual Controller Array that came with the disk enclosures. HP wants more than $15k to re-license the EVA, so that is not an option.I took an older HP DL380 G5 server with 48GB RAM and added a HP StorageWorks 82Q 8GB PCI-e Dual Fibre Channel HBA (AJ764A) and connected the twodisk enclosures with the server. The server also have 4 x 1GB and 4 x 10GB ethernet ports.On the server HP Server I have loaded FreeNas 9.3 and I use the server and disk enclosures as a very capable SAN.The HP M6412-A Fibre Channel Drive Enclosures have two Fibre channel ports (red and green), but I have only connected the enclosures with one Fibre Channel loop to...
This topic first appeared in the Spiceworks Community

Hi,I have acquired two HP M6412-A Fibre Channel Drive Enclosures with 14 dual-port SAS15K disk drives (7 per enclosure) in a recent company takeover.I do not have any HP software licenses for the HP EVA4400 Dual Controller Array that came with the disk enclosures. HP wants more than $15k to re-license the EVA, so that is not an option.I took an older HP DL380 G5 server with 48GB RAM and added a HP StorageWorks 82Q 8GB PCI-e Dual Fibre Channel HBA (AJ764A) and connected the twodisk enclosures with the server. The server also have 4 x 1GB and 4 x 10GB ethernet ports.On the server HP Server I have loaded FreeNas 9.3 and I use the server and disk enclosures as a very capable SAN.The HP M6412-A Fibre Channel Drive Enclosures have two Fibre channel ports (red and green), but I have only connected the enclosures with one Fibre Channel loop to...
This topic first appeared in the Spiceworks Community

Does fibre channel use both ports on the same drive bay

I would like to know if Fibre Channel uses both of the fibre ports when they are connected to the same fibre channel drive bay. (dual port communication)

I would like to know if Fibre Channel uses both of the fibre ports when they are connected to the same fibre channel drive bay. (dual port communication)

Fibre Channel is OFFLINE Errors and A1000

Hi All,
I have an A1000 Sun StorEdge disk array that is attached to an Ultra II server running solaris 9. Soon as I attached the A1000 disk array and powered the box up, the following errors started to show up in /var/adm/messages on the Ultra2:
Jun 25 13:26:12 sec46 soc: [ID 854183 kern.info] ID[SUNWssa.soc.link.5010] soc0: port 0 WWN 90165e: Fibre Channel is OFFLINE
Jun 25 13:26:39 sec46 soc: [ID 854183 kern.info] ID[SUNWssa.soc.link.6010] soc0: port 0 WWN 90165e: Fibre Channel is ONLINE
Jun 25 13:26:39 sec46 soc: [ID 854183 kern.info] ID[SUNWssa.soc.login.6010] soc0: port 0 WWN 90165e: Fibre Channel login succeeded
Jun 25 13:26:39 sec46 soc: [ID 854183 kern.info] ID[SUNWssa.soc.link.1010] soc0: port 0 WWN 90165e: message: SSA110 V3.11 (122096) Fri Dec 20 19:09:18 1996
I have applied all of the recommened patches on the system powered down both, the A1000 and the system and brought them back up. No joy
Does any one know why the heck these errors are showing up?
Any pointers will be much appreciated
SamSB.

They are coming from your SSA112(114) array. Check the fibre cable and FCOM to / from SSA. It has nothing to do with A1000 because A1000 is not fibre

Receiving fibre channel activity log email when unplugging usb flash drive

I found this to be very interesting.... I get the email from the log of the machine I am on.... this happens EVERY time I unplug my SanDisk CRUZER GATOR 8GB Flash Drive. I have a couple other non-sandisk drives and it doesnt seem to cause the same thing.
this really doesnt effect our xsan or anything, but its annoying and it worries me that it could screw something up potentially.....so I am just wondering if anyone else is experiencing this?? or would know why this happens with just the sandisk...
This is on a MacPro 2 x 3ghz dual core xeons, 4gb memory. xsan 1.4.2
contents of the email:
Fibre channel activity and failures:
16:03:53: LUN 00:00:00:00:00:00:00:001 is no longer available
16:03:53: LUN 00:00:00:00:00:00:00:000 is no longer avail...
Message was edited by: RoyMan

We received this alert also:
Fibre channel activity and failures:
14:27:05: LUN 00:00:00:00:00:00:00:001 is no longer available
14:27:05: LUN 00:00:00:00:00:00:00:000 is no longer avail...
And we were using a SanDisk 8GB Cruzer USB flash drive as well.
Client is Mac Pro / Two 2.66GHz Dual-Core Intel Xeon / 2BG RAM / Xsan 1.4.2.

Can Time Machine back up Fibre Channel connected drives?

Hello All,
     I am running Mac OS X 10.7.5. I am trying to back up drives connected to my tower via fibre channel using Time Machine and am getting the exclusion error that others have been reporting on Lion and Mountain Lion. In Time Machine > Options, I select a fibre channel connected drive to include it in the next backup. It disappears from the exclusion list as it should AND the properly "estimated size of full backup" is created. I select "Save." However, when I select "Options" again, the fibre channel connected drive has been RE-EXCLUDED. This happens with all of the drives connected via fibre channel.
     All of the drives have unique UUIDs and display Connection Bus: Fibre Channel Interface and Connection Type: External in Disk Utility. All of the drives are formatted as "Mac OS Extended." The drives are all inside of a Facilis Terrablock 24D and are RAID5.
      Before updating to Lion, we were able to back up these drives via Time Machine successfully for many months.
      Does anyone know if it is possible to back up drives connected via fibre channel with Time Machine on Lion and Mountain Lion? To be perfectly clear, I am trying to simply back up these fibre channel connected drives to a Firewire connected external HD via Time Machine...NOT use a fibre channel connected drive as my Time Machine backup disk.
       Your time and help is greatly appreciated!
Best,
LALB

Others have reported the same issue. Apparently it doesn't work.

Need docs that explain Fibre Channel setup, getting I/O error on 2540 SAN

Sun T5220 Host running Solaris 10 5/09 as management host.
Qlogic 5602 FC Switch
Sun Storagetek 2540 - one controller tray with 9 300G SAS Hitachi drives. Firmware 7.35.x.
Sun branded Qlogic QLE2462 HBAs - PCI express, dual port. 3 in the T5220. qlcxxxx drivers for the HBAs.
Sun Common Array Manager software version 6.5.
I am a long-time Oracle DBA who has the task of setting up a Fibre Channel SAN. I am not a Solaris sysadmin, but have installed and maintained large databases on Solaris boxes where I had access to a competent sysadmin. I am at a classified site and cannot bring out electronic files with logs, configuration info, etc. to upload. Connecting the T5220 is the 1st box of many. This is my first exposure to HBA's, Fibre Channel, and SAN, so everything I know about it I have read in a manual or from a post somewhere. I understand the big picture and I have the SAN configured with 2 storage pools each with 1 volume in them on RAID5 virtual disks. I can see the LUN 0 on the T5220 server when I do a luxadm probe and when I do a format. I formatted one of the volumes successfully. Now I attempt to issue:
newfs /dev/rdsk/device_name_from_output_of_luxadm_probe
I get an immediate I/O error. I could be doing something totally naive or have a larger problem - this is where I get lost and the documentation becomes less detailed.
What would be great is if anyone knows of a detailed writeup that would match what I'm doing or a good off-the-shelf textbook that covers all of this or anything close. I continue to search for something to bridge my lack of knowledge in this area. I am unclear about the initiators and targets beyond the fundamental definitions. I have used the CAM 6.5 software to define the initiators that it discovered. I have mapped the Sun host into a host group also. I do not know what role the Qlogic 5602 Fibre Channel switch plays with respect to initiators and targets or if it has any role at all. Is it just a "pass through" and the ports on the 5602 do not have to be included? Maybe I don't have the SAN volume available in read/write. I find bits and pieces in blogs and forums, but nothing that puts it all together. I also find that many of the notes on the web are not accurate.
This all may appear simplistic to someone who works with it a lot and if you know of an obvious reference I should be using, a link or reply would be greatly appreciated as I continue to Google for information.

Thanks for the reply. I had previously read the CAM 6.5 manual and have all the SAN configuration and mappings. Yesterday I was back at the site and was able to place a UFS filesystem on the exposed SAN LUN which was 0. I've not seen any reference to LUN 0 being a placeholder for the 2540 setup and when I assigned it, I allowed the CAM 6.5 software to choose "Next Available" LUN and it chose 0. LUN 31 on the 2540 is the "Access" LUN that is assigned automatically - perhaps it is taking the place of what you describe as the LUN 0 placeholder.
I was able to put a new UFS filesystem on LUN 0 (newfs), mount it, and copy data to it. The disk naming convention that Solaris shows for the SAN disks is pretty wild and I usually have to reference a Solaris book on the standard scsi disk name formats. My question/confusion at the moment is that I have 3 Sun branded Qlogic HBA's in the Sun T5220 server - QLE2462 (dual port) with one port on two of the HBAs cabled to the Qlogic 5602 FC switch which is cabled to the A and B controller of the SAN 2540 - there are only 2 cables coming out of the 5220; the 3rd HBA (for future use) has no cables to it. Both ports show up as active and connected on the server down to the SAN and the CAM 6.5 software automatically identified both initiators (ports) on the Sun 5220 when I mapped them. I had previously mapped them to the Sun host, mapped the host to a host_group, virtual disks to volumes, volumes to....etc.; and was able to put data on the exposed volume named dev_vol1 which is a RAID5 virtual disk on the SAN.
When I use the format command on Solaris, it shows two disks and I assumed this represented the two ports from the same host 5220. I was able to put a label on one of these disks (dev_vol1), format it, and put data on it as noted above. When I select the other disk in the format menu, it is not formatted, won't allow me to put a label on it (I/O error) and I can go no further from there. The CAM 6.5 docs stop after they get you through the mapping and getting a LUN exposed. I continue on the in a Solaris-centric mindset and try to do the normal label, format, newfs, mount routine and it works for the one "disk" that format finds but not for the other. The information from the format info on both the disks shows them as 1.09 TB and that is the only volume mapped right now from the SAN so I know it is the same SAN volume. It does not make sense that I would label it and format it again anyway, but is this what I am supposed to see - two disks (because of 2 ports?) and the ability to access it through one. I found out by trial an error that I could label, format, and access the one. I did not do it from knowledge or looking at the information presented....I just guessed through it.
I have not "bound" the 2 or HBAs in any way and that is on my list as next because I want to do multipathing and failover - just starting to read that so I may be using the wrong language. But I am wondering before I go on to that, if I am leaving something undone in the configuration that is going to hamper my success in the multipathing - since I cannot do anything with the 2nd "disk" that has been exposed to Solaris from the SAN. I thought, after I labeled, formatted and put a filesystem on the one "disk" I can write to that the other "disk" that shows up would just be another path to the same data via a 2nd initiator. Just writing that does not sound right, but I am trying to convey my thoughts as to what I logically expected to see. Maybe the question should be why am I seeing that 2nd "disk" in a Solaris format listing at all? I have not rebooted any time during this process also and can easily do that and will today.

Error -36 + Fibre Channel Error Log

K, so I ran into a very strange occurance.
While attempting to copy a 250GB folder of media from one pool to another on an xsan volume, I ended up hitting a single 500 MB file that kept giving me "error -36" in the finder.
After the third try, I ended up copying the file to my desktop, deleting it from the xsan volume, recopying it back over and then attempting the copy again from pool to pool, and voila!
Now the odd thing, when I tried to copy that file and got that error, all 3 times, I got a notification email that looked something like this:
Fibre channel activity and failures:
03:18:02: Path 50:00:39:30:00:01:17:A6 is no longer available
03:18:02: Path 50:00:39:30:00:00:9E:99 is no longer available
03:18:02: Path 50:00:39:30:00:00:9D:DD is no longer available
03:18:02: Path 50:00:39:30:00:00:6E:13 is no longer available
03:18:02: Path 50:00:39:30:00:00:62:8E is no longer available
03:18:02: Path 50:00:39:30:00:00:41:26 is no longer available

That's odd. /.journal is a hidden file, and not a standard one on an OSX drive.
Do you have any idea what it is?
You could look at it via #A3 in the Time Machine - Troubleshooting *User Tip,* also at the top of this forum.
As you say, it's not causing the backup to fail, but you can exclude it, per the green box in #C3 of the Troubleshooting Tip.

OSX 10.5.6 doesn't see Fibre Channel Disk array, neither does Disk Utility

My system is a Power Mac G5 Quad, 6gb Ram, 1Tb internal hard drives, 1Tb external and several portable drives as needed.
The Drive array in question is a Fujitsu GR710 which contains 12 Seagate Cheeta ST336605FC drives which are around 35gb each.
OK, I have been given a Fibre Channel system, that at one time worked with OSX. I had to move it and now it doesn't show up on Disk Utility anymore. I can totally reformat it if possible, but I have to be able to see it first.
System Profiler sees the setup as:
Fibre Channel Domain 0:
Vendor: LSILogic
Product: LSI7202EP
Revision: Firmware 1.2.18.0, Fcode 1.00.37
Bus: PCI
Slot: SLOT-2
Initiator Identifier: 126
Node World Wide Name: 20:00:00:06:2B:12:C4:C4
Port World Wide Name: 10:00:00:06:2B:12:C4:C4
Address Identifier: 00:00:E8
Description: Port 0
Speed: Automatic (1 Gigabit)
Topology: Automatic (Arbitrated Loop)
Status: Link Established
Cable Type: Fiber Optic
SCSI Target Device @ 0:
Node World Wide Name: 20:00:00:E0:00:41:04:6D
Port World Wide Name: 21:00:00:E0:00:41:04:6D
Address Identifier: 00:00:EF
SCSI Target Identifier: 0
SCSI Peripheral Device Type: 0
Manufacturer: FUJITSU
Model: GR710
Revision: 0000
SCSI Logical Unit @ 0:
SCSI Logical Unit Number: 0
Manufacturer: FUJITSU
Model: GR710
Revision: 0000
Fiber Channel Preferences shows that a link is established.
Hardware RAID says that there is no hardware present.
I am using the Apple MA900A/G Fibre Channel Card to hook into the Drive array. It is hooked up with both ethernet and fiber optic cables.
I have used an IP scanner to search for the IP of the array and only find one that I can't identify at 224.0.0.251 another scan reports an IP of 0.0.0.0, neither worked when I tried to use Safari to access it.
I have tried several programs to try and get into this array and nothing sees it. All my experts tell me that I will need to use the Terminal program and use command lines to access the drives, but I can't find any information about what to do there. I've been told I need the driver for the array, naturally there isn't a driver for Mac to be had, but there are drivers for solaris, Unix, and windows. The last expert said to use the Unix driver, but I don't know where to put it in the system.
So I need help, Terminal commands to talk to the drive and revive it hopefully, or a system program that will do something similar. None of my diagnostic programs sees the array. The Card came with no software or instructions. Neither did the array. I haven't been able to find any hardware information about the drive from FuJitsu at all, it's too old for them to bother with anymore.
Any help would be greatly appreciated!
Thanks
Doc

I have to go with William on this one - if it's shows up over fibre then it should be okay. Have you gotten the admin module to see the device over ether? I have a feeling that is you can get the software to see it you might be able to configure the device into something the computer could mount.
The Promise that way - you can configure the device entire from the web interface and you don't need fibre communication working for any of the configuration of what RAID you want and which disks are attached with what set etc. Once the RAIDs are configured into volumes then the Xserve sees they exist and you can use Disk Utility to format them. If you don't need fibre communication I don't see how SCSI drivers would matter over ethernet. But maybe the box is a strange beast - odder things have been made.
Barring that - can you attach the device to an older machine with the drivers and configure the device into raw volumes and then an HFS+ (or whatever you want) system? If you did that and then switched the box back to Xserve it should be able to pick up the configured volumes drivers or no.
My $.02,
=Tod

Fibre Channel Howto Guide?

Hi, I am new to Fibre Channel and I am having problems. I cannot get my v210's to see the fc 3510 array. The disks on the array show up on the switch fabric as Sun and wwpn numbers. The v210 is connected to the FC Switch (cisco 5428) but when I do a luxadm probe no array is seen. Similarly format shows only the local disk on the system.
I can see the qlogic HBA card and its associated driver on the v210 and I am at a loss what to do next. I need to know how to configure the HBA and Im guessing I have to add it to the Zone. So I wondered if some one could explain zones or tell me where I can find documentation to help me. Any help would be greatly appreciated. thanks.

Solaris 8 but we want to upgrade to Solaris 9.
I dont have FC documentation available - Do you know where I can find some? thats why I registered here, otherwise I will have to buy a book or Go on an expensive course. Or there may be somewhere handy online, for free, that tells me what I need to know.? Howto guide?
Are you referring to documentation that may have come with the hba or something on the sun site.
Thanks for responding.

Fibre Channel Storage

Im planning on using three mac pros to capture live footage in prores 422hq 1080i.
Can I put a fibre channel in each mac pro and network them to each other...that way when i edit i can just edit from each drive from one mac pro without having to copy them all to one station?

What you're asking is called arbitrated loop.
You can start from here:
http://en.wikipedia.org/wiki/Arbitrated_loop
My preliminary kinda lame and super-fast answer is that you'll be involved in a messy configuration, which isn't gonna worth the cost and time.
If you're gonna use fibre channel, buy a switch a proper SAN and do that. Otherwise it is possible to use Gigabit Ethernet switches, a mac pro as a host and work with ProRes.
If you're gonna use the MacBook pro, absolutely check if the GigE port supports jumbo frames because most new iMacs do not.

Sun v880 server thrown messages during reboot

he server is connected with three application server works as v480 also shown the same error, in the last error messsage we are geting ar 5 17:37:50 gtcerp1 scsi: [ID 107833 kern.notice]      Requested Block: 677 Error Block: 677
Mar 5 17:37:50 gtcerp1 scsi: [ID 107833 kern.notice]      Vendor: HP Serial Number: 9 $DR-1
Mar 5 17:37:50 gtcerp1 scsi: [ID 107833 kern.notice]      Sense Key: Media Error
Mar 5 17:37:50 gtcerp1 scsi: [ID 107833 kern.notice]      ASC: 0x11 (unrecovered read error), ASCQ: 0x0, FRU:
presently system is running fne, no console message, but why this throw so many messages during reboot.
Mar 4 07:42:24 gtcerp1 tictimed[1224]: [ID 423602 user.error] [tictimed]: stopping on SIGTERM or SIGPWR.
Mar 4 07:42:24 gtcerp1 tictimed[1224]: [ID 423602 user.error] [tictimed]: stopping on SIGTERM or SIGPWR.
Mar 4 07:42:34 gtcerp1 syslogd: going down on signal 15
Mar 4 07:44:13 gtcerp1 genunix: [ID 540533 kern.notice] ^MSunOS Release 5.9 Version Generic_118558-03 64-bit
Mar 4 07:44:24 gtcerp1 luxadm[64]: [ID 972850 user.error] ID[luxadm.create_fabric_device.2316] configuration failed for line (/devices/pci@9,700000/SUNW,qlc@3/fp@0,0:fc::216000c0ff07a6ca) in file: /etc/cfg/fp/fabric_WWN_map.old. I/O error
Mar 4 07:44:24 gtcerp1 luxadm[64]: [ID 650835 user.error] ID[luxadm.create_fabric_device.2316] configuration failed for line (/devices/pci@9,700000/SUNW,qlc@3/fp@0,0:fc::256000c0ffc7a6ca) in file: /etc/cfg/fp/fabric_WWN_map.old. I/O error
Mar 4 07:44:13 gtcerp1 genunix: [ID 943905 kern.notice] Copyright 1983-2003 Sun Microsystems, Inc. All rights reserved.
Mar 4 07:44:24 gtcerp1 luxadm[64]: [ID 733177 user.error] ID[luxadm.create_fabric_device.2316] configuration failed for line (/devices/pci@9,700000/SUNW,qlc@4/fp@0,0:fc::226000c0ffa7a6ca) in file: /etc/cfg/fp/fabric_WWN_map.old. I/O error
Mar 4 07:44:13 gtcerp1 Use is subject to license terms.
Mar 4 10:37:22 gtcerp1 luxadm[64]: [ID 972850 user.error] ID[luxadm.create_fabric_device.2316] configuration failed for line (/devices/pci@9,700000/SUNW,qlc@3/fp@0,0:fc::216000c0ff07a6ca) in file: /etc/cfg/fp/fabric_WWN_map.old. I/O error
Mar 4 07:44:13 gtcerp1 genunix: [ID 678236 kern.info] Ethernet address = 0:3:ba:4d:d0:98
Mar 4 10:37:22 gtcerp1 luxadm[64]: [ID 650835 user.error] ID[luxadm.create_fabric_device.2316] configuration failed for line (/devices/pci@9,700000/SUNW,qlc@3/fp@0,0:fc::256000c0ffc7a6ca) in file: /etc/cfg/fp/fabric_WWN_map.old. I/O error
Mar 4 07:44:13 gtcerp1 unix: [ID 389951 kern.info] mem = 16777216K (0x400000000)
Mar 4 10:37:22 gtcerp1 luxadm[64]: [ID 733177 user.error] ID[luxadm.create_fabric_device.2316] configuration failed for line (/devices/pci@9,700000/SUNW,qlc@4/fp@0,0:fc::226000c0ffa7a6ca) in file: /etc/cfg/fp/fabric_WWN_map.old. I/O error
Mar 4 07:44:13 gtcerp1 unix: [ID 930857 kern.info] avail mem = 16490520576
Mar 4 07:44:13 gtcerp1 rootnex: [ID 466748 kern.info] root nexus = Sun Fire 880
Mar 4 07:44:13 gtcerp1 mpxio: [ID 181378 kern.info] /scsi_vhci (scsi_vhci0) multipath capabilities enabled.
Mar 4 07:44:13 gtcerp1 rootnex: [ID 349649 kern.info] scsi_vhci0 at root
Mar 4 07:44:13 gtcerp1 genunix: [ID 936769 kern.info] scsi_vhci0 is /scsi_vhci
Mar 4 07:44:13 gtcerp1 rootnex: [ID 349649 kern.info] pcisch0 at root: SAFARI 0x8 0x700000
Mar 4 07:44:13 gtcerp1 genunix: [ID 936769 kern.info] pcisch0 is /pci@8,700000
Mar 4 07:44:13 gtcerp1 rootnex: [ID 349649 kern.info] pcisch1 at root: SAFARI 0x8 0x600000
Mar 4 07:44:13 gtcerp1 genunix: [ID 936769 kern.info] pcisch1 is /pci@8,600000
Mar 4 07:44:13 gtcerp1 rootnex: [ID 349649 kern.info] pcisch2 at root: SAFARI 0x9 0x700000
Mar 4 07:44:13 gtcerp1 genunix: [ID 936769 kern.info] pcisch2 is /pci@9,700000
Mar 4 07:44:13 gtcerp1 rootnex: [ID 349649 kern.info] pcisch3 at root: SAFARI 0x9 0x600000
Mar 4 07:44:13 gtcerp1 genunix: [ID 936769 kern.info] pcisch3 is /pci@9,600000
Mar 4 07:44:13 gtcerp1 qlc: [ID 171021 kern.info] Qlogic FCA Driver v20040825-1.40 (0)
Mar 4 07:44:13 gtcerp1 qlc: [ID 637753 kern.info] NOTICE: qlc(0): Firmware version 2.1.140
Mar 4 07:44:14 gtcerp1 qlc: [ID 686697 kern.info] NOTICE: Qlogic qlc(0): Loop ONLINE
Mar 4 07:44:14 gtcerp1 pcisch: [ID 370704 kern.info] PCI-device: SUNW,qlc@2, qlc0
Mar 4 07:44:14 gtcerp1 genunix: [ID 936769 kern.info] qlc0 is /pci@8,600000/SUNW,qlc@2
Mar 4 07:44:14 gtcerp1 qlc: [ID 171021 kern.info] Qlogic FCA Driver v20040825-1.40 (1)
Mar 4 07:44:14 gtcerp1 qlc: [ID 637753 kern.info] NOTICE: qlc(1): Firmware version 3.2.110
Mar 4 07:44:14 gtcerp1 qlc: [ID 686697 kern.info] NOTICE: Qlogic qlc(1): Loop OFFLINE
Mar 4 07:44:14 gtcerp1 pcisch: [ID 370704 kern.info] PCI-device: SUNW,qlc@3, qlc1
Mar 4 07:44:14 gtcerp1 genunix: [ID 936769 kern.info] qlc1 is /pci@9,700000/SUNW,qlc@3
Mar 4 07:44:14 gtcerp1 qlc: [ID 171021 kern.info] Qlogic FCA Driver v20040825-1.40 (2)
Mar 4 07:44:14 gtcerp1 qlc: [ID 637753 kern.info] NOTICE: qlc(2): Firmware version 3.2.110
Mar 4 07:44:14 gtcerp1 qlc: [ID 686697 kern.info] NOTICE: Qlogic qlc(2): Loop OFFLINE
Mar 4 07:44:14 gtcerp1 pcisch: [ID 370704 kern.info] PCI-device: SUNW,qlc@4, qlc2
Mar 4 07:44:14 gtcerp1 genunix: [ID 936769 kern.info] qlc2 is /pci@9,700000/SUNW,qlc@4
Mar 4 07:44:14 gtcerp1 genunix: [ID 936769 kern.info] fp0 is /pci@8,600000/SUNW,qlc@2/fp@0,0
Mar 4 07:44:14 gtcerp1 genunix: [ID 936769 kern.info] fp1 is /pci@9,700000/SUNW,qlc@3/fp@0,0
Mar 4 07:44:14 gtcerp1 genunix: [ID 936769 kern.info] fp2 is /pci@9,700000/SUNW,qlc@4/fp@0,0
Mar 4 07:44:14 gtcerp1 qlc: [ID 686697 kern.info] NOTICE: Qlogic qlc(2): Loop ONLINE
Mar 4 07:44:15 gtcerp1 scsi: [ID 799468 kern.info] ssd1 at fp0: name w2100000c507a995e,0, bus address e8
Mar 4 07:44:15 gtcerp1 genunix: [ID 936769 kern.info] ssd1 is /pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w2100000c507a995e,0
Mar 4 07:44:15 gtcerp1 scsi: [ID 799468 kern.info] ssd0 at fp0: name w210000008715a66e,0, bus address ef
Mar 4 07:44:15 gtcerp1 genunix: [ID 936769 kern.info] ssd0 is /pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w210000008715a66e,0
Mar 4 07:44:15 gtcerp1 scsi: [ID 799468 kern.info] ssd22 at fp0: name w2100000c5080e94e,0, bus address e4
Mar 4 07:44:15 gtcerp1 genunix: [ID 936769 kern.info] ssd22 is /pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w2100000c5080e94e,0
Mar 4 07:44:15 gtcerp1 scsi: [ID 799468 kern.info] ssd33 at scsi_vhci0: name g600c0ff00000000007a6ca587d8cff00, bus address g600c0ff00000000007a6ca587d8cff00
Mar 4 07:44:15 gtcerp1 genunix: [ID 936769 kern.info] ssd33 is /scsi_vhci/ssd@g600c0ff00000000007a6ca587d8cff00.

Errors?
I don't see anything that a good call to Oracle Technical Support can't fix.
Go use your service contract and open a Support Request (SR).
Else wipe the system and resinstsall everything fresh.
While you are at it, you should patch your Solaris 9 system with the newest full bundle you can get.
SunOS Release 5.9 Version Generic_118558-03That system is about a decade under-patched.
That suggests a deliberate lack of continual maintenance.

Xserve RAID Fibre Channel Lights pegged until disk activity

We are having some issues with an Xserve RAID connected to a G5 Xserve running 10.4.8 Server. The Fibre Channel lights on the front are constantly maxed out, but whenever the disk are active the lights die down only to peg again when activity stops. Needless to say, we are having SEVERE access speed issues. Any ideas?

This can happen in a protected RAID set (i.e. RAID 5) if a single raid member drive pops offline and back on again, since the RAID set has to re-build itself from the parity data in that case.
It also happens after creating a RAID 5 volume, as the creation usually takes a few days (assuming you used the 'RAID Now' option), and so you'll see the blue lights.
It also makes sense that the blue light 'spiking' would drop when you do a read/write, as the initialization process has to pause to handle the disk activity.
Are either of these the case?
We are having some issues with an Xserve RAID
connected to a G5 Xserve running 10.4.8 Server. The
Fibre Channel lights on the front are constantly
maxed out, but whenever the disk are active the
lights die down only to peg again when activity
stops. Needless to say, we are having SEVERE access
speed issues. Any ideas?
MacBook Pro Mac OS X (10.4.8)

How to identify fibre channel HBA working or not

Hi,
I dont know how to identify FC hba card and port. I cant access the box because it is in a remote location.
My customer is saying there is 3 hba cards and one is showing disconnected. I see three types of cards in path_to_inst file and luxadm -e port command.
I cant understand the connection between the controller which showing in the cfgadm command and hba device.
/devices/ssm@0,0/pci@1d,600000/QLGC,qla@1/fp@0,0:devctl showing disconnected what does it mean?
So Please help me to find answers of these questions.
1) how many physical FC HBA cards are in this server.
2) How many FC Ports are in this server
3) Why controller C4 showing un configured.
4) why /devices/ssm@0,0/pci@1d,600000/QLGC,qla@1/fp@0,0:devctl showing disconnected
logs :-
bash-3.00# fcinfo hba
fcinfo: invalid object
Usage: fcinfo [-?] <OBJECT> [-?] [<OPERAND>]
Usage by OBJECT:
fcinfo hba-port [OPTIONS] [<WWN ...>]
fcinfo remote-port <OPTIONS> [<WWN ...>]
For more information, please see fcinfo(1M)
bash-3.00# fcinfo hba-port
HBA Port WWN: 10000000c93aa32d
OS Device Name: /dev/cfg/c2
Manufacturer: Emulex
Model: LP9002L
Firmware Version: 3.90a7 (C2D3.90A7)
FCode/BIOS Version: Boot:3.20 Fcode:1.40a0
Serial Number: BG40340370
Driver Name: emlxs
Driver Version: 2.50o (2010.01.08.09.45)
Type: N-port
State: online
Supported Speeds: 1Gb 2Gb
Current Speed: 2Gb
Node WWN: 20000000c93aa32d
HBA Port WWN: 10000000c93ae1be
OS Device Name: /dev/cfg/c7
Manufacturer: Emulex
Model: LP9002L
Firmware Version: 3.92a3 (C2D3.92A3)
FCode/BIOS Version: Boot:3.20 Fcode:none
Serial Number: BG40855848
Driver Name: emlxs
Driver Version: 2.50o (2010.01.08.09.45)
Type: N-port
State: online
Supported Speeds: 1Gb 2Gb
Current Speed: 2Gb
Node WWN: 20000000c93ae1be
HBA Port WWN: 210000e08b08c5c1
OS Device Name: /dev/cfg/c4
Manufacturer: QLogic Corp.
Model: QLA2200
Firmware Version: 02.01.145
FCode/BIOS Version: fcode: 0.00;
Serial Number: not available
Driver Name: qlc
Driver Version: 20090929-2.32
Type: unknown
State: offline
Supported Speeds: 1Gb
Current Speed: not established
Node WWN: 200000e08b08c5c1
bash-3.00#
bash-3.00# cat /etc/path_to_inst | grep -i fp
"/ssm@0,0/pci@19,600000/lpfc@1/fp@0,0" 3 "fp"
"/ssm@0,0/pci@19,600000/lpfc@1/fp@0,0/ssd@w5001738001900142,1" 0 "ssd"
"/ssm@0,0/pci@19,600000/lpfc@1/fp@0,0/ssd@w5001738001900142,2" 2 "ssd"
"/ssm@0,0/pci@19,600000/lpfc@1/fp@0,0/ssd@w5001738001900160,1" 3 "ssd"
"/ssm@0,0/pci@19,600000/lpfc@1/fp@0,0/ssd@w5001738001900190,1" 4 "ssd"
"/ssm@0,0/pci@19,600000/lpfc@1/fp@1,0" 4 "fp"
"/ssm@0,0/pci@1b,600000/lpfc@1/fp@0,0" 1 "fp"
"/ssm@0,0/pci@1b,600000/lpfc@1/fp@0,0/ssd@w5001738001900170,1" 1 "ssd"
"/ssm@0,0/pci@1b,600000/lpfc@1/fp@1,0" 2 "fp"
"/ssm@0,0/pci@1d,600000/QLGC,qla@1/fp@0,0" 5 "fp"
"/ssm@0,0/pci@1f,600000/QLGC,qla@1/fp@0,0" 0 "fp"
"/ssm@0,0/pci@1f,600000/fibre-channel@1/fp@0,0" 6 "fp"
"/ssm@0,0/pci@1f,600000/fibre-channel@1/fp@1,0" 7 "fp"
bash-3.00# cfgadm -al | grep -i fc
c2 fc-fabric connected configured unknown
c4 fc connected unconfigured unknown
c7 fc-fabric connected configured unknown
bash-3.00# luxadm -e port
/devices/ssm@0,0/pci@19,600000/lpfc@1/fp@0,0:devctl CONNECTED
/devices/ssm@0,0/pci@1f,600000/fibre-channel@1/fp@0,0:devctl CONNECTED
/devices/ssm@0,0/pci@1d,600000/QLGC,qla@1/fp@0,0:devctl NOT CONNECTED
bash-3.00#
bash-3.00#
bash-3.00#
bash-3.00#
bash-3.00# cfgadm -alv | grep -i fc
unavailable fc-fabric n /devices/ssm@0,0/pci@19,600000/lpfc@1/fp@0,0:fc
unavailable array-ctrl n /devices/ssm@0,0/pci@19,600000/lpfc@1/fp@0,0:fc::5001738001900142
unavailable fc n /devices/ssm@0,0/pci@1d,600000/QLGC,qla@1/fp@0,0:fc
unavailable fc-fabric n /devices/ssm@0,0/pci@1f,600000/fibre-channel@1/fp@0,0:fc
unavailable array-ctrl n /devices/ssm@0,0/pci@1f,600000/fibre-channel@1/fp@0,0:fc::5001738001900160
unavailable array-ctrl n /devices/ssm@0,0/pci@1f,600000/fibre-channel@1/fp@0,0:fc::5001738001900190
bash-3.00#

If you see state other than online, or speed "not established," the HBA is not working, but it may not be connected to anything.
If you think it is connected, get the WWN from the "HBA Port WWN" field, and run
fcinfo remote-port wwn
If you don't get any information back, you're not seeing any other FC devices (might be a switch zoning issue).
If you see other ports (usually their WWN starts with a 5), but not your LUNs, add -s, and you can see which LUNs have been masked (made available) to this WWN.
If you add -l, you can see the error counters for the link, which should be very low (single digit) and not increasing. If not, you might have a bad cable or SFP/GBIC.
Hope this helps!

Clarification on how to use Xserve Raid and Fibre Channel without xsan.

First let me apologize for not responding earlier to your response, I tend to get busy and then forget to check back here.
Tod, the answer to your question is No, only one computer is accessing the xserve raid files at any one time and that is via Fibre Channel. However I do have the xserve raids set up as share points via ethernet.
Maybe I should turn that off and only access the files with the one computer that can connect via fibre channel.
I never thought of that. I will try that while I await for your answer, thanks again.
Todd Buhmiller
I have the following setup:
Xserve: 2x2Ghz Dual Core Intel Xeon, 5Gb of Ram, Running 10.5.8 Leopard Server
Xserve Raid with firmware version 1.5.1/1.51c on both controllers, and
Qlogic Sanbox 5600
Apple Fibre Channel Cards in Xserve, and Mac Pro Tower; Apple 2 Port 4Gbs Fibre Channel Card
Mac Pro Tower-Quad Core Intel Xeon 2.8Ghz, 16Gb of Ram, Running Snow Leopard 10.6.4
Here is the problem.
The directory for the xserve raids keep getting corrup, and I use disc warrior to rebuild them. Is there a way to keep the directories from getting corrupt? I am a few pieces of equipment before I can build an Xsan as that is the ultimate goal, but until then, I just need to be able to have the raids funciton as storage without having to rebuild the directories all of the time.
Anybody have any suggestions?
Thanks
Todd Buhmiller
Widescreen Media
Calgary, Alberta Canada
Tod Kuykendall
Posts: 1,237
From: San Diego
Registered: Oct 11, 2000
Re: Xserve Raid Mounts, Corrupt Directory tired of rebuilding directory
Posted: Jun 27, 2010 1:25 PM in response to: Todd Buhmiller
Are multiple computers accessing the same data on the RAID at the same time?
If so then NO. This is the source of your data corruption and I'm surprised if you were able to get all your data back every time if this is how you've been running your system. Each fibre channel assumes it has full and sole control of every volume it has mounted, no data arbitration is practiced and data corruption will occur if this assumption is wrong.
The only way this set-up will work is to use partitions or LUN masks so the volumes are accessed by one computer at any time. As long as one computer relinquishes control before another mounts it you will dodge arbitration issues but this is a dangerous game. If you screw up and mount an already mounted volume - and there is no easy way to tell if a volume is mounted - corruption will then occur. Sharing data simultaneous at fibre speeds is what XSAN does and to do this you need it.
HTH,
=Tod
Intel Xserve, G5 XServes, XRAID, Promise

+The xserve raids will mount automatically to any computer that I connect the qlogic fc switch to+
This is source of the corruption to your data. Any computer that attaches to a drive/partition via fibre channel assumes that it alone is in control of the drive and data corruption is inevitable.
+Is that the issue, should I disconnect the xserve from the fc switch and leave it connected via ethernet?+
Short answer: YES. The ethernet connections are fine because the server is controlling the file arbitration through the sharing protocol. Fibre channel connections assumes complete control over the partition and no arbitration of the file access is performed. It's like two people independently driving trying to drive the same car to different locations.
Depending on your set-up it is possible for the two machines to see and use different parts of the Xserve RAID storage but they cannot access the same areas without SAN doing the arbitration.
Hope that's clear,
=Tod

Sun V880 Fibre channel drive giving Loop OFFLINE message

Similar Messages

Maybe you are looking for