Nexus 56128P Fibre Channel Interface

Hi everybody,
I'm installing a Nexus 56128P and I try to configure Fibre Channel native interface on GEM N56-M24UP2Q.
I have configured the ports to be fc interface
slot 2
port 1-24 type fc
Then i have reloaded the module, but no fc interface appeared (and no more ethernet interface 2/x).
I checked the license, i have the FC_FEATURES_PKG installed but "unused".
I guess i missed something, but can't figure out what.
Any idea ?
Julien

see https://supportforums.cisco.com/discussion/12254396/fc-ports-nexus-5548up
After the port type has been changed from Ethernet to FC, the FC port will not be enabled on the switch until FCOE feature is enabled:
N5K(config)#feature FCOE
C license checked out successfully
fc_plugin extracted successfully
FC plugin loaded successfully
FCoE manager enabled successfully
FC enabled on all modules successfully
Enabled FCoE QoS policies successfully
After that, we verify that the port type is changed successfully and the FC ports appear on the switch:
N5K# show interface brief

Similar Messages

HP E2749A VXI fibre channel interface

Currently we are using three HP E2749A fibre channel interface cards. Unfortunately, this product is no longer supported by Agilent.
We record 24 channels of 16bit digitized data (160k samples/sec/channel) to a Ciprico RAID via a fibre controlled arbitrated loop.
I am presently investigating options to refurbish this system. The Controller used in the VXI chassis is a HP E1498A/V743
If you have a product which may fit this use or need information before responding please replay as soon as possible.

National Instruments does not have a fibre channel interface card or a product for that type of application. Good luck in your search!

Looking for a Fibre-Channel interface

Does there exist a Fiber Optic communications interface, specifically "Fibre-Channel" for which LabVIEW drivers exist?
Perhaps one of the select integrators may have one or know of one.
Paul Conaway
Lockheed Martin, Syracuse

[Warning: A little self promotion follows. Read at your own risk!]
I am working a project now that includes a "Fibre-Channel" phase in a future phase. We have done a lot of research into this area and are developing benchmarking systems that will let us quantify the determinism of various transport mediums. The current implementation is building on a SCRAMnet gt fiber network to do the measurements.
If you think we may be able to help you out, you can e-mail me at
[email protected]
and I'll put in in contact with management types.
[End of shameless self promotion]
Ben
PS: If you are at the same facility as "Rick Lucas", tell him that "Ben says 'Hi!'"
Message Edited by Ben on 09-24-2008 07:57 AM
Ben Rayner
I am currently active on.. MainStream Preppers
Rayner's Ridge is under construction

Nexus 5548 and vfc Interfaces - WHY?

What is a vfc and why do we need to configure it? I find this extremely tedious.
I have a Dell blade CNA connected to a Dell M8024-k FCoE transit module, which is then connected to a Cisco Nexus 5K. The Cisco 5K's FC port is in NPIV mode and is connected to a Brocade 300 switch. An FC target is connected to the B300.
So, in configuring this set up, I see that, in the Cisco 5K, one has to map the CNA's Ethernet MAC-address to a vfc!
Why do I have to do this mapping? You dont have to do this with Brocade. For example, in another lab setup, I have a Dell M8428-k FCF (FCoE) switch, which is a Brocade ODM, and there is no such mapping necessary. You bring up a CNA at will, the CNA executees a FIP FLOGI, gets an FPMA from the FC fabric switch, and a construct is seamlessly built between that CNA (or perhaps more correctly stated, the N-Port component of that CNA) and a LUN. NO MANUAL MAPPING is necessary.
Can someone explain this Cisco vfc construct and why one has to engage in this laborious task of mapping every CNA to a vfc? Just trying to understand....perhaps I am missing something.
Thank you

Hello,
Virtual Fiber Channel ( vfc ) interfaces are used to apply FC features in FCoE link.
Check out the section " Cisco Nexus 5000 Series Virtual Fibre Channel Interfaces " in following link
http://www.cisco.com/en/US/prod/collateral/switches/ps9441/ps9670/white_paper_c11-560403.html
Additional guidelines on vfc configuration are documented here
http://www.cisco.com/en/US/partner/docs/switches/datacenter/nexus5000/sw/fcoe/513_n1_1/b_Cisco_n5k_fcoe_config_gd_re_513_n1_1_chapter_0100.html#con_1288652
Padma

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.

NEXUS 56128P

It is not directly clear from the documentation, but i assume all 48 standard onboard SFP+ ports support FEX connectivity and FCOE possibility ?
regards,
GN

Hi,
Yes you are correct.
Cisco Nexus 56128P Switch: The Cisco Nexus 56128P is a 2RU switch (figure 3) that supports 2.56 Tbps of bandwidth across 48 fixed 1 Gigabit and 10 Gigabit Ethernet SFP+ ports, and four 40-Gbps QSFP+ ports (Figure 3). The Cisco Nexus 56128P offers two expansion slots to support 24 ports of 10 Gigabit Ethernet and FCoE or 8/4/2-Gbps Fibre Channel and two ports of 40 Gigabit Ethernet using QSFP optics.
The Cisco Nexus 56128P (figure 4) also offers two slots for a Generic Expansion Modules (GEM). The GEM for the Cisco Nexus 56128P provides 24 ports 10G Ethernet/FCoE or 2/4/8G Fibre Channel and 2 ports 40 Gigabit QSFP+ Ethernet/FCoE ports. The expansion module supports native 40 Gigabit Ethernet on the QSFP+ ports. The expansion module is supported on the Cisco Nexus 56128P chassis only and can be populated in either of the two expansion slots.
HTH
Inayath.

Can I hook up a NAS via Fibre Channel?

I am building a Linux NAS to be accessed by my Macs. I've purchased fibre cards for all of my macs, an LSI fibre card for my Linux machine, and a McData 4400 fibre switch. I'm trying to configure my fibre network so I can share files from my NAS. I've got the fabric set up, but everything that I read is talking about using SAN software to connect to a SAN, not a NAS. I can't find any information at all on how to do what I want to do, or whether or not it's possible. Can someone please help me figure out how to set up this Fibre Channel network, or at least figure out if it's possible or not? Thank you!
-Ryan

Is what you want technically possible? Probably.
In an earlier era, you could have a network or an image scanner or other devices connected to a host via SCSI; via a storage bus. There was all manner of odd SCSI-connected gear. (Think of SCSI as expensive multi-host USB with big expensive cables and with expensive peripheral devices, and you'll have the general idea. And FWIW, SCSI is the underpinnings of USB.)
You would end up writing a whole lot of driver code for the devices and hosts you have, too.
Which is where folks end up with commercial SAN solutions, or with NAS solutions, and not with using a SAN as a network.
The various Fibre Channel controller vendors discussed but never seemed to have sorted out the network interface designs for their FC controllers.
If you want to roll your own storage arrays akin to the [Apple Xsan|http://www.apple.com/xsan> or the HP [MSA|http://h18000.www1.hp.com/storage/diskstorage/msa_diskarrays/sanarrays/index.html] or [EVA|http://h18000.www1.hp.com/storage/diskstorage/eva_diskarrays/evaarrays/index.html] SAN arrays, well, have at. You'll likely end up needing to write host disk drivers, as well as the firmware within the SAN controller. Networking drivers might be a bit more tricky; I haven't looked at those device interfaces in a while, and you'd need to tie those drivers into the host network stacks. Once you have some or all of that working, then the hosts can see the block storage out on the SAN. If you need sharing, you'll need to sort out a cluster or SAN file system to run atop the block storage or atop the network connection you've built; a file system that can coordinate distributed access.
Possible? Sure. On a budget? Probably not.

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

Nexus 1000v - port-channel "refresh"

Hi All,
My question is, does anyone have any information on this 1000v command:
Nexus-1000v(config)# port-channel internal device-id table refresh
I am looking for a way for the port-channel interface to be automatically removed from the 1000v once the VEM has been deleted, currently the port-channel interface does not disappear when the VEM has been removed. This seems to be causing problems once the same VEM is re-added later on. Ports are getting sent into quarantine states and ending up in invalid states (eg. NoPortProfile state when there is actually a port-profile attached).
Anyway, if anyone can explain the above command or tell me how to find out more, it would be great, I can't find it documented anywhere and the context-sensitive help in the NXOS is vague at best.

Brendan,
I don't have much information on that command, but I do know it wont remove any unused port channels. They have to be manually deleted if they're no longer needed.
The port Channel ID will remain even after a VEM is removed in case the assigned VEM comes back. When a VEM is decommisioned permanently, I'll do a "no vem x" to also remove the Host entry for that VEM from the VSM. This way the module slot # can be re-assigned to the next new VEM inserted. After adding/removing VEMs just do a "show port-channel summary" to see any unused Port Channel IDs, and delete them. It's a quick & painless task.
I would hope this wouldn't be a common issue - how often are you deleting/removing VEMs?
Regards,
Robert

Fibre Channel Jumbo Frames - UCS

I was wondering if it's actually possible to have Jumbo Fibre Channel Frames running on a UCS?
I've read these two articles which provide some excellent information on implementing Jumbo Frames and Fibre Channel Jumbo Frames:
http://datacenteroverlords.com/2013/04/01/jumbo-fc-frames/
http://www.ccierants.com/2013/10/ccie-dc-definitive-jumbo-frames.html
Everything within the SAN I'm administrating has the ability to set the MTU up to 9036 except for the UCS. For example on the NetApp gear I can set the MTU per interface, on the Cisco MDS I can set the MTU per vsan. However in the UCS manager when I go to QoS System Class, the option to set the MTU for Fibre Channel is greyed out and it doesnt look like there's anyway to override the preset frame size. I can set the MTU of Best Effort however my understanding is Fibre Channel traffic within the UCS will use the Fibre Channel system class.
Furthermore I noticed I can set the Maximum Data Field Size on the vHBA's within the UCS manager however my understanding is the maximum this can go up to is 2048.

Hi
Did you check
http://datacenteroverlords.com/2013/04/01/jumbo-fc-frames/
Erik Smith says:
April 1, 2013 at 5:52 pm
April fools! I wish I saw this earlier, I would have posted corroborating test results!
In Summary: forget Jumbo Frames for FC !

How to using Virtual fibre channel feature in IC 3.5?

Hi ,guys ,i have noticed that microsoft released IC 3.5 to support virtual fibre channel in redhat and centos linux.
the links are:
http://technet.microsoft.com/en-us/library/dn531026.aspx
http://blogs.technet.com/b/virtualization/archive/2014/01/02/linux-integration-services-3-5-announcement.aspx
in these links above ,notes 2 says:
While using virtual fibre channel devices, ensure that logical unit number 0 (LUN 0) has been populated. If LUN 0 has not been populated, a Linux virtual machine might not be able to mount fibre channel devices natively.
but I do not understand how to ensure logical unit number 0 has been populated ,anyone who have tested such new features please share your expirence , thank you very much.
yoke88
IM：[email protected]

The same issues as yours,no HBA card can be seen
I have tried the command here to list hyper-v virutal fiber channel card in oracle linux 6.5 ,but no luck,and EMC powerpath does not support UEK r3 which was installed default on OL 6.5 X64,I will try Oracle linux 6.3 with IC 3.5
http://mikent.wordpress.com/2012/02/07/how-to-find-wwn-of-hba-on-redhat-6-x/
[root@computer01 ~]# uname -a
Linux computer01.localdomain 3.8.13-26.1.1.el6uek.x86_64 #2 SMP Thu Feb 13 19:42:43 PST 2014 x86_64 x86_64 x86_64 GNU/Linux
[root@computer01 ~]# lspci -nn
00:00.0 Host bridge [0600]: Intel Corporation 440BX/ZX/DX - 82443BX/ZX/DX Host bridge (AGP disabled) [8086:7192] (rev 03)
00:07.0 ISA bridge [0601]: Intel Corporation 82371AB/EB/MB PIIX4 ISA [8086:7110] (rev 01)
00:07.1 IDE interface [0101]: Intel Corporation 82371AB/EB/MB PIIX4 IDE [8086:7111] (rev 01)
00:07.3 Bridge [0680]: Intel Corporation 82371AB/EB/MB PIIX4 ACPI [8086:7113] (rev 02)
00:08.0 VGA compatible controller [0300]: Microsoft Corporation Hyper-V virtual VGA [1414:5353]
[root@computer01 ~]# fdisk -l
Disk /dev/sda: 53.7 GB, 53687091200 bytes
255 heads, 63 sectors/track, 6527 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x000896c0
   Device Boot      Start         End      Blocks   Id System
/dev/sda1   *           1          64      512000   83 Linux
Partition 1 does not end on cylinder boundary.
/dev/sda2              64        6528    51915776   8e Linux LVM
Disk /dev/mapper/vg_computer01-lv_root: 49.0 GB, 48964304896 bytes
255 heads, 63 sectors/track, 5952 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000
Disk /dev/mapper/vg_computer01-lv_swap: 4194 MB, 4194304000 bytes
255 heads, 63 sectors/track, 509 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000
[root@computer01 ~]# lsmod |grep hv
hv_netvsc              21641 0
hv_utils                7440 0
hv_balloon              9843 0
hv_storvsc             10236 2
hv_vmbus               92011 5 hid_hyperv,hv_netvsc,hv_utils,hv_balloon,hv_storvsc
[root@computer01 ~]# modinfo hv_vmbus
filename:       /lib/modules/3.8.13-26.1.1.el6uek.x86_64/kernel/drivers/hv/hv_vmbus.ko
version:        3.1
license:        GPL
srcversion:     8BAC864516830DFFF7DC2B1
alias:          acpi*:VMBus:*
alias:          acpi*:VMBUS:*
depends:
intree:         Y
vermagic:       3.8.13-26.1.1.el6uek.x86_64 SMP mod_unload modversions
using microsoft virutal fibre chanel trouble shooting guide ,i see the event logs indicate the VHBA card was successfully added to the vm.
yoke88
IM：[email protected]

Cisco fibre channel domain manager "fast start" feature

Hi there:
I'm trying to understand the
cisco fibre channel domain manager "fast start" feature
but I can't
Manual say:
About Domain Manager Fast Restart
As of Cisco MDS SAN-OS Release 3.0(2), when a principal link fails, the domain manager must select a new principal link. By default, the domain manager starts a build fabric (BF) phase, followed by a principal switch selection phase. Both of these phases involve all the switches in the VSAN and together take at least 15 seconds to complete. To reduce the time required for the domain manager to select a new principal link, you can enable the domain manager fast restart feature.
When fast restart is enabled and a backup link is available, the domain manager needs only a few milliseconds to select a new principal link to replace the one that failed. Also, the reconfiguration required to select the new principal link only affects the two switches that are directly attached to the failed link, not the entire VSAN. When a backup link is not available, the domain manager reverts to the default behavior and starts a BF phase, followed by a principal switch selection phase. The fast restart feature can be used in any interoperability mode.
Questions:
Those links are not a Port channel, aren't they?
If those links would form a port channel then it is not need the fast restart feature?
In case of there are not a backup link, should be another fabric path and host should conmute because multipath?
Then, there are very specific scenarios where Fast Restart feature apply, aren't they?
Thank you in advance for your comments
Al

Please post "debug ccsip messages".
Based on your debug you are getting "Cause No. 38 - network out of order."
You may want to bind SIP to an interface that the IP address is defined which Lync points to.
Chris

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

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.

Problem with fibre channel card and raid system after upgrading to 10.4.7

Hello, I have a problem with our Xserve G4 DP. After the installation of 10.4.7 everything works fine exept our fibre channel card. This card is connected to a Hitachi Raid System which worked fine over a year. But after the update the volume was no longer mounted. I even reinstalled the server to 10.4.4 and no sign of our raid volume. Using the apple fibre channel utiltiy 2.0, I see that there is a connection - but still the raid volume is not mounted. When I restart the server the lights on the back of the card are shortly flickering and sending some packets to the raid system but that´s all. Has anybody an idea?
Greetings from Heidelberg
Klaus
Xserve G4 DP 1 GHz Mac OS X (10.4.6) Mac OSX Server 10.4.7

You could re-update, by downloading the 10.4.7 Combination Updater from Apple.

Nexus 56128P Fibre Channel Interface

Similar Messages

Maybe you are looking for