search for: wwnn

...type Could you please help? virsh # nodedev-dumpxml scsi_host6 <device> <name>scsi_host6</name> <parent>pci_0000_08_00_0</parent> <capability type='scsi_host'> <host>6</host> <capability type='fc_host'> <wwnn>20000024ff57d848</wwnn> <wwpn>21000024ff57d848</wwpn> <fabric_wwn>20018c604f101321</fabric_wwn> </capability> <capability type='vport_ops' /> </capability> </device> virsh # nodedev-dumpxml scsi_host15 <devi...

...h # nodedev-dumpxml scsi_host6 > <device> > <name>scsi_host6</name> > <parent>pci_0000_08_00_0</parent> > <capability type='scsi_host'> > <host>6</host> > <capability type='fc_host'> > <wwnn>20000024ff57d848</wwnn> > <wwpn>21000024ff57d848</wwpn> > <fabric_wwn>20018c604f101321</fabric_wwn> > </capability> > <capability type='vport_ops' /> > </capability> > </device> > > >...

...ent, and then its this storage pool creation I've seen. Though some things are not clear to me. This is what the xml file looks like in the documentation: <pool type='scsi'> <name>poolvhba0</name> <source> <adapter type='fc_host' wwnn='20000000c9831b4b' wwpn='10000000c9831b4b'/> </source> <target> <path>/dev/disk/by-path</path> <permissions> <mode>0700</mode> <owner>0</owner> <group>0</group...

...h # nodedev-dumpxml scsi_host6 > <device> > <name>scsi_host6</name> > <parent>pci_0000_08_00_0</parent> > <capability type='scsi_host'> > <host>6</host> > <capability type='fc_host'> > <wwnn>20000024ff57d848</wwnn> > <wwpn>21000024ff57d848</wwpn> > <fabric_wwn>20018c604f101321</fabric_wwn> > </capability> > <capability type='vport_ops' /> > </capability> > </device> > > >...

...;> <device> >> <name>scsi_host6</name> >> <parent>pci_0000_08_00_0</parent> >> <capability type='scsi_host'> >> <host>6</host> >> <capability type='fc_host'> >> <wwnn>20000024ff57d848</wwnn> >> <wwpn>21000024ff57d848</wwpn> >> <fabric_wwn>20018c604f101321</fabric_wwn> >> </capability> >> <capability type='vport_ops' /> >> </capability> >> &lt...

...(N_Port ID Virtualization) is a Fibre Channel technology to share a single physical Fibre Channel HBA with multiple virtual ports. Henceforth known as a "virtual port" or "virtual Host Bus Adapter" (vHBA), each virtual port is identified by its own WWPN (Word Wide Port Name) and WWNN (Word Wide Node Name). In the virtualization world the vHBA controls the LUNs for virtual machines. The libvirt implementation provides flexibility to configure the LUN's either directly to the virtual machine or as part of a storage pool which then can be configured for use on a virtual machi...

...rsh nodedev-dumpxml scsi_host5 <device> <name>scsi_host5</name> <parent>pci_0000_04_00_1</parent> <capability type='scsi_host'> <host>5</host> <capability type='fc_host'> <wwnn>2001001b32a9da4e</wwnn> <wwpn>2101001b32a9da4e</wwpn> <fabric_wwn>2001000dec9877c1</fabric_wwn> </capability> <capability type='vport_ops'> <max_vports>164</max_vports> &lt...

Hi, When I want to use NPIV for a FC HBA in my Linux machine, I got the below error msg in virsh: virsh # nodedev-create /home/kvm/vHBA.xml error: Failed to create node device from /home/kvm/vHBA.xml error: internal error Parent device scsi_host20 is not capable of vport operations I checked the /sys/class folder for my HBA device that I want to use its NPIV feature, it's there:

...picious messages in dmesg. Also, ctladm dumpooa does not show anything. Here is dumpscructs output : CTL IID to WWPN map start: CTL IID to WWPN map end CTL Persistent Reservation information start: CTL Persistent Reservation information end CTL Frontends: Frontend CTL ioctl Type 4 pport 0 vport 0 WWNN 0 WWPN 0 Frontend ctl2cam Type 8 pport 0 vport 0 WWNN 0x5000000995680700 WWPN 0x5000000995680702 Frontend CTL internal Type 8 pport 0 vport 0 WWNN 0 WWPN 0 Frontend isp0 Type 1 pport 0 vport 0 WWNN 0x20000024ff376b98 WWPN 0x21000024ff376b98 isp0: max tagged openings: 4096, max dev openings: 4096 is...

...n particular is the FC capable fc_host Then creation of the node device : #virsh nodedev-create vhba.xml Node device scsi_hostM created from vhba.xml where 'M' is whatever the next available scsi_host# is on your host. If you 'virsh nodedev-dumpxml scsi_hostM' you'll see the wwnn/wwpn details. You can then create a vHBA scsi pool from that in order to ensure the persistence of the vHBA.  Although it's not required - the vHBA scsi pool just allows you to provide a source pool and volume by unit # for your guest rather than having to edit guests between host reboots or o...

...ssfully created a virtual HBA using virsh nodedev-create and an XML config. Here's a sample config: [root at host ~]# cat vm1vhba1.xml <device> <parent>scsi_host3</parent> <capability type='scsi_host'> <capability type='fc_host'> <wwnn>a97a3b9220010002</wwnn> <wwpn>a97a3b9220010001</wwpn> </capability> <capability type='vport_ops' /> </capability> </device> Pretty straightforward. The parent is physical SCSI host 3. The resulting SCSI host is 5. This is one...

...> virtio_scsi: Implement fc_host > > drivers/scsi/virtio_scsi.c | 55 +++++++++++++++++++++++++++++++++++++++- > include/uapi/linux/virtio_scsi.h | 6 +++++ > 2 files changed, 60 insertions(+), 1 deletion(-) > Hmm. How it this supposed to work? You do export the WWPN/WWNN of the associated host to the guest (nb: will get interesting for non NPIV setups ...), but virtio scsi will still do a LUN remapping. IE the LUNs you see on the host will be different from the LUNs presented to the guest. This makes reliable operations very tricky. Plus you don't _actually_ e...

...n particular is the FC capable fc_host Then creation of the node device : #virsh nodedev-create vhba.xml Node device scsi_hostM created from vhba.xml where 'M' is whatever the next available scsi_host# is on your host. If you 'virsh nodedev-dumpxml scsi_hostM' you'll see the wwnn/wwpn details. You can then create a vHBA scsi pool from that in order to ensure the persistence of the vHBA. Although it's not required - the vHBA scsi pool just allows you to provide a source pool and volume by unit # for your guest rather than having to edit guests between host reboots or o...

...n particular is the FC capable fc_host Then creation of the node device : #virsh nodedev-create vhba.xml Node device scsi_hostM created from vhba.xml where 'M' is whatever the next available scsi_host# is on your host. If you 'virsh nodedev-dumpxml scsi_hostM' you'll see the wwnn/wwpn details. You can then create a vHBA scsi pool from that in order to ensure the persistence of the vHBA.  Although it's not required - the vHBA scsi pool just allows you to provide a source pool and volume by unit # for your guest rather than having to edit guests between host reboots or o...

This series implements the proposed fc_host feature of virtio-scsi. The first patch updates the data structure changes according to the spec proposal; the second patch actually implements the operations. Fam Zheng (2): virtio_scsi: Add fc_host definitions virtio_scsi: Implement fc_host drivers/scsi/virtio_scsi.c | 55 +++++++++++++++++++++++++++++++++++++++-

This series implements the proposed fc_host feature of virtio-scsi. The first patch updates the data structure changes according to the spec proposal; the second patch actually implements the operations. Fam Zheng (2): virtio_scsi: Add fc_host definitions virtio_scsi: Implement fc_host drivers/scsi/virtio_scsi.c | 55 +++++++++++++++++++++++++++++++++++++++-

...n particular is the FC capable fc_host Then creation of the node device : #virsh nodedev-create vhba.xml Node device scsi_hostM created from vhba.xml where 'M' is whatever the next available scsi_host# is on your host. If you 'virsh nodedev-dumpxml scsi_hostM' you'll see the wwnn/wwpn details. You can then create a vHBA scsi pool from that in order to ensure the persistence of the vHBA.  Although it's not required - the vHBA scsi pool just allows you to provide a source pool and volume by unit # for your guest rather than having to edit guests between host reboots or o...

...defined in the IBM?? Storage ITE Software Configuration Guide. If available, the correct host type will be "IBM TS SAN VCE". Once the issue has been resolved, click Next to continue. The following additional information may help with correcting the problem: Storage system name: ds3400-01 WWNN (Worldwide Node Name): XX:XX:XX:XX:XX:XX:XX:XX WWPN (Worldwide Port Number): XX:XX:XX:XX:XX:XX:XX:XX Problem type : Unsupported RDAC Mode Set ----%<------- The fix then runs, but reports the same 1624 error. > >> The V3700 is still complaining and I note the "path checker rdac&qu...

...defined in the IBM?? Storage ITE Software Configuration Guide. If available, the correct host type will be "IBM TS SAN VCE". Once the issue has been resolved, click Next to continue. The following additional information may help with correcting the problem: Storage system name: ds3400-01 WWNN (Worldwide Node Name): XX:XX:XX:XX:XX:XX:XX:XX WWPN (Worldwide Port Number): XX:XX:XX:XX:XX:XX:XX:XX Problem type : Unsupported RDAC Mode Set ----%<------- The fix then runs, but reports the same 1624 error. > >> The V3700 is still complaining and I note the "path checker rdac&qu...

...defined in the IBM?? Storage ITE Software Configuration Guide. If available, the correct host type will be "IBM TS SAN VCE". Once the issue has been resolved, click Next to continue. The following additional information may help with correcting the problem: Storage system name: ds3400-01 WWNN (Worldwide Node Name): XX:XX:XX:XX:XX:XX:XX:XX WWPN (Worldwide Port Number): XX:XX:XX:XX:XX:XX:XX:XX Problem type : Unsupported RDAC Mode Set ----%<------- The fix then runs, but reports the same 1624 error. > >> The V3700 is still complaining and I note the "path checker rdac&qu...