Users Guide
Broadcom DRVLin-LPe-UG124-100
30
Emulex Drivers for Linux User Guide
3.2.4 Monitoring vPorts with fc_vport
The transport creates an fc_vports directory that you can use to monitor vPorts. This directory is populated entirely of
vPorts and has links from each to the fc_host associated with that vPort.
ls /sys/class/fc_vports/
vport-5:0-0
ls -d /sys/bus/pci/drivers/lpfc/*/host*/*/host*
/sys/bus/pci/drivers/lpfc/0000:03:06.1/host5/vport-5:0-0/host6
ls /sys/devices/pci*/*/host5/vport-5*/host6
power rport-6:0-0 rport-6:0-1 rport-6:0-2 uevent
ls /sys/devices/pci*/*/host5/vport-5*/host6/rport-*
/sys/devices/pci00:03/00:03:06.1/host5/vport-5:0-0/host6/rport-6:0-0:
power uevent
/sys/devices/pci00:03/00:03:06.1/host5/vport-5:0-0/host6/rport-6:0-1:
power uevent
/sys/devices/pci00:03/00:03:06.1/host5/vport-5:0-0/host6/rport-6:0-2:
power target6:0:0 uevent
In this example:
A new entry exists in the fc_vports directory for the vPort (vport-5:0-0). The vport-5:0-0 entry indicates that
the vPort was created from host5, and it is the first (0) vPort to be created on that fc_host.
The new host for the vPort is host6, and it appears in the usual directories.
A new directory exists in the bus tree. This new directory indicates that host6 was created under vport-5:0-0
(which was created from host5).
3.2.5 vPort Configuration Limits
vPort configuration limits are designated as enforced or unenforced. Enforced limits are limits that the driver enforces and
prevents you from exceeding. Unenforced limits are limits that the driver cannot enforce, but configurations that exceed them
are unsupported.
The following vPort configuration limits have been tested with and are supported by the Emulex driver. Configurations that
exceed one or more of these limits are unsupported.
Before the vPort is deleted or the driver is unloaded, I/O devices accessed through a vPort must be stopped and file
systems must be unmounted.
The maximum number of vPorts configurable on a physical port is 255.
vport_delete Write- only WWPN; WWNN /sys/class/fc_host/hostX/vport_delete
This entry deletes a vPort on the physical port on
which hostX is located. The vPort matching the
WWPN and WWNN is immediately deleted.
This entry returns a 0 if the vPort deletion was
successful. A nonzero value indicates that the vPort
was not deleted.
If an fc_host does not support NPIV, this sysfs
entry might not exist.
NOTE: This entry deletes the vPort even if there are
mounted file systems being accessed through this
vPort, or if there are open files on it.
Table 4: vPort sysfs Entries (Continued)
vPort sysfs Entries Type Range/Input Location and Description