Sponsored Content
Full Discussion: Mpxio
Operating Systems Solaris Mpxio Post 302265743 by incredible on Monday 8th of December 2008 11:10:32 AM
Old 12-08-2008
#fcinfo hba-port
#fcinfo remote-port -slp 10000000c955c39a
#luxadm display /dev/rdsk/c4t600A0B80000C595B00000007459A7396d0s2
#sar -d
Also check your /var/adm/messages after boot, usually MPXio will give you
the info of which path the get used together.
 

10 More Discussions You Might Find Interesting

1. Solaris

Mpxio

Hi All, I have one question. I found out that my system setting for mpxio-disable=yes. Sun recommend to change it to mpxio-disable=no and run stmsboot -e command. But no one can tell will it affect the system or not and the system is sol-10 and using veritas volume manager and attached... (3 Replies)
Discussion started by: mailbox80
3 Replies

2. Filesystems, Disks and Memory

VxVM and MPxIO

:confused: Last week I read that VxVM won't work with MPxIO (i don't recall the link) and that it should be unconfigured when installing VxVM. Today I read that VxVM works in "pass-thru" mode with MPxIO and DMP uses the devices presented by MPxIO. If I create disks with MPxIO and use VxVM to... (1 Reply)
Discussion started by: bluescreen
1 Replies

3. Filesystems, Disks and Memory

MPxIO question

Greetings Forumers!! I was given a T2000 with one, dual port, HBA card. The card had one fiber connection to the SAN and the former admin enabled MPxIO. Yesterday, I learned that the other port was connected to the same SAN. This system is in another city so I don't have physical access to... (1 Reply)
Discussion started by: bluescreen
1 Replies

4. UNIX for Advanced & Expert Users

mpxio in Solaris10 with NetApp FAS3140 problem

we have a v440 SUN machine with a NetApp FAS3140 SAN storage, the v440 got 2 HBA qlogic cards both connected to the switch side in NetApp 3140, zoning in netapp configured proberly and luns are adversitesed to the SUN machine, the problem i am facing is that when i try to configure the mpxio i am... (7 Replies)
Discussion started by: q8devilish
7 Replies

5. Solaris

MPXIO

Hi Kudo, I wanna to know that how can I do mpxio device name to os native name mapping without using stmsboot -L I tried everything still not able to got the solution till I able to get these o/p here is native disk info as well physical wat is the logical OS name of the disk ... (1 Reply)
Discussion started by: tarunn.dubeyy
1 Replies

6. Solaris

Curious MPxIO problem

Hello folks, I have a newly installed Solaris 10 system running on a T6320 blade. I have set up LDM with the intent to move an ldom from another blade to this one. So far, so good. I had the SAN folks make the LUNs belonging to the ldom visible to my new blade and I can see them, all 4 paths.... (4 Replies)
Discussion started by: Ranck
4 Replies

7. Solaris

Migrate from MPXIO to Powerpath

Here is the issue: I am building a database server using Solaris 10x86 U8. The system is jumpstarted with mpxio enabled and booting from the san. We need to have powerpath 5.3 installed and would like to have powerpath take control of the the boot san as well or have mpxio control the san... (2 Replies)
Discussion started by: nabru72
2 Replies

8. Solaris

solaris turn off multipath mpxio

Im not able to turn the multipath off on the solaris s10 X86...since im on FC boot.. if i disable multipath , from /kernel/drv/iscsi.conf then im not able to boot the machine.:wall: Is there any other go or any suggestions . (2 Replies)
Discussion started by: gowtham.varma
2 Replies

9. Solaris

Solaris 10 + mpxio Path

Hi, I have an Oracle/Sun T3-2 Server with a duel SAS controller Fujitsu DX60 array attached. I have 2 x SAS HBA's in the T3-2. One HBA cabled to CM0 and one HBA cabled to CM1 of the array. The array is setup with one RAID GROUP and one VOLUME and one LUN In Solaris I can see one device... (4 Replies)
Discussion started by: general_lee
4 Replies

10. Solaris

MPxIO Multipathing Problem

Hi, I believe this is an OS multipathing issue - Solaris 10 We have x2 Dual port 8GB Qlogic HBA's installed in our SOlaris 10 host. HBA0 (IOU0) Port WWN's - 09f4 (pci@3,700000/SUNW,qlc@0) 09f5 (pci@3,700000/SUNW,qlc@0,1) HBA1 (IOU1) Port WWN's... (2 Replies)
Discussion started by: jamba1
2 Replies
fcinfo(1M)						  System Administration Commands						fcinfo(1M)

NAME
fcinfo, fcadm - Fibre Channel HBA Port Command Line Interface SYNOPSIS
fcinfo hba-port [-lit] [HBA_port_WWN]... fcadm hba-port [-lit] [HBA_port_WWN]... fcinfo remote-port [-ls] [-p HBA_port_WWN] [REMOTE_port_WWN]... fcadm remote-port [-ls] [-p HBA_port_WWN] [REMOTE_port_WWN]... fcinfo logical-unit | lu [-v] [OS device_path] fcadm logical-unit | lu [-v] [OS device_path] fcadm create-npiv-port -p Virtal_Port_WWN [-n Virtual_Node_WWN] PhysicalPort_port_WWN fcadm delete-npiv-port -p Virtal_Port_WWN [-n Virtual_Node_WWN] PhysicalPort_port_WWN fcinfo [-V] fcadm [-V] fcinfo [-?] fcadm [-?] DESCRIPTION
fcinfo and fcadm are command line interfaces that collect administrative information on fibre channel host bus adapter (HBA) ports on a host. They also collect data on any fibre channel targets that might be connected to those ports in a Storage Area Network (SAN). A port can be either in initiator mode or target mode. The same FC attribute information and remote port information are applied to both the initiator and the target modes port except that SCSI-related operations described below do not apply for the target mode port. SUBCOMMANDS The following subcommands are supported by both fcinfo and fcadm: hba-port Lists information for the HBA port referenced by the specified HBA_port_WWN. If HBA_port_WWN is not specified, all initiator mode and target mode fibre channel HBA ports on the host will be listed. remote-port Lists the remote-port information for those remote ports that are specified. If no REMOTE_port_WWN is specified, all remote ports that are visible through HBA_port_WWN are listed. logical-unit | lu Lists the logical unit referenced by the specified device_path. If device_path is not specified, all fibre channel logical units will be listed. This subcommand applies only to the initiator mode. The following subcommands, which administer N_Port ID Virtualization (NPIV) HBA ports, are supported only by fcadm: create-npiv-port Create an NPIV virtual port on the specified adapter. delete-npiv-port Delete an NPIV virtual port. This delete only ports create by fcadm. OPTIONS
The following options are supported: -l, --linkstat Lists the link error statistics information for the port referenced by the specified HBA_port_WWN or REMOTE_port_WWN. -i [HBA_node_WWN], -initiator [HBA_node_WWN] Lists the information for the port with the initiator mode referenced by the specified HBA_node_WWN or all initiator mode ports discov- ered in the host. -n HBA_node_WWN, --node HBA_node_WWN When used with NPIV options, specify a virtual node WWN. If used with create-npiv-port, it can be omitted, and a random based WWN will be used. It is mandatory for delete-npiv-port. -p HBA_port_WWN, --port HBA_port_WWN Retrieve remote port information from the HBA_port_WWN of the local HBA port on the host. When used with the remote-port subcommand, the -p option is mandatory. When used with NPIV options, specify a virtual port WWN. If used with create-npiv-port, it can be omitted, and a random based WWN will be used. It is mandatory for delete-npiv-port. -s, --scsi-target Lists the SCSI target information for all remote ports the user has asked for. The -p, --port option must always be specified and must be a valid HBA port on the host. This HBA port will be used as the initiator for which to retrieve the SCSI level target information. Note that this will only function on remote port fibre channel World-Wide Names that support an FC4 type of SCSI. This option applies only to an initiator mode port. -t [HBA_node_WWN], -target [HBA_node_WWN] Lists the information for the port with the target mode referenced by the specified HBA_node_WWN or all target mode ports discovered in the host. -v, --verbose When used with the logical-unit subcommand, the -v displays additional information for the logical unit, including SCSI vendor and product information and device type as well as the FC World-Wide names for the local and remote fibre channel ports to which this device is attached. -V, --version Displays the version information. -?, --help Displays the usage information. EXAMPLES
Example 1 Listing All HBA Ports The following command lists all initiator mode fibre channel HBA ports on the host: # fcinfo hba-port HBA Port WWN: 210000e08b074cb5 Port Mode: Initiator OS Device Name: /dev/cfg/c1 Manufacturer: QLogic Corp. Model: 375-3108-xx Firmware Version: 3.3.116 FCode/BIOS Version: 1.13.08 Serial Number: not available Driver Name: qlc Driver Version: 20070212-2.19 Type: N-port State: online Supported Speeds: 1Gb 2Gb Current Speed: 2Gb Node WWN: 200000e08b074cb5 NPIV Port List: Virtual Port 1: Port WWN: 200000e08b074cb1 Node WWN: 200000e08b074cb3 HBA Port WWN: 210100e08b274cb5 Port Mode: Initiator OS Device Name: /dev/cfg/c2 Manufacturer: QLogic Corp. Model: 375-3108-xx Firmware Version: 3.3.116 FCode/BIOS Version: 1.13.08 Serial Number: not available Driver Name: qlc Driver Version: 20070212-2.19 Type: N-port State: online Supported Speeds: 1Gb 2Gb Current Speed: 2Gb Node WWN: 200100e08b274cb5 HBA Port WWN: 210000e08b072ab5 Port Mode: Initiator OS Device Name: /dev/cfg/c3 Manufacturer: QLogic Corp. Firmware Version: 3.3.116 FCode/BIOS Version: 1.13.08 Model: 375-3108-xx Serial Number: not available Driver Name: qlc Driver Version: 20070212-2.19 Type: L-port State: online Supported Speeds: 1Gb 2Gb Current Speed: 2Gb Node WWN: 200000e08b072ab5 HBA Port WWN: 210100e08b272ab5 Port Mode: Initiator OS Device Name: /dev/cfg/c4 Manufacturer: QLogic Corp. Model: 375-3108-xx Firmware Version: 3.3.116 FCode/BIOS Version: 1.13.08 Serial Number: 0402F00-0549112808 Driver Name: qlc Driver Version: 20070212-2.19 Type: N-port State: online Supported Speeds: 1Gb 2Gb Current Speed: 2Gb Node WWN: 200100e08b272ab5 Example 2 Listing Target Mode HBA Ports The following command lists all target mode fibre channel HBA ports on the host: # fcinfo hba-port -t HBA Port WWN: 210100e08bb09221 Port Mode: Target Port ID: 10700 OS Device Name: Not Applicable Manufacturer: QLogic Corp. Model: d30ac7e0 Firmware Version: 4.0.109 FCode/BIOS Version: N/A Type: F-port State: online Supported Speeds: not established Current Speed: 2Gb Node WWN: 200100e08bb09221 HBA Port WWN: 210000e08b909221 Port Mode: Target Port ID: 10900 OS Device Name: Not Applicable Manufacturer: QLogic Corp. Model: d37ad1e0 Firmware Version: 4.0.109 FCode/BIOS Version: N/A Type: F-port State: online Supported Speeds: not established Current Speed: 2Gb Node WWN: 200000e08b909221 Example 3 Listing HBA Ports and Link Statistics The following command lists information for the HBA ports and the link statistics for those ports: # fcinfo hba-port -l 210000e08b074cb5 210100e08b274cb5 HBA Port WWN: 210000e08b074cb5 Port Mode: Initiator OS Device Name: /dev/cfg/c1 Manufacturer: QLogic Corp. Model: 375-3108-xx Firmware Version: 3.3.116 FCode/BIOS Version: 1.13.08 Serial Number: 0402F00-0549112808 Driver Name: qlc Driver Version: 20070212-2.19 Type: N-port State: online Supported Speeds: 1Gb 2Gb Current Speed: 2Gb Node WWN: 200000e08b074cb5 Link Error Statistics: Link Failure Count: 0 Loss of Sync Count: 0 Loss of Signal Count: 0 Primitive Seq Protocol Error Count: 0 Invalid Tx Word Count: 0 Invalid CRC Count: 0 HBA Port WWN: 210100e08b274cb5 Port Mode: Initiator OS Device Name: /dev/cfg/c2 Manufacturer: QLogic Corp. Model: 375-3108-xx Firmware Version: 3.3.116 FCode/BIOS Version: 1.13.08 Serial Number: 0402F00-0549112808 Driver Name: qlc Driver Version: 20070212-2.19 Type: N-port State: online Supported Speeds: 1Gb 2Gb Current Speed: 2Gb Node WWN: 200100e08b274cb5 Link Error Statistics: Link Failure Count: 0 Loss of Sync Count: 0 Loss of Signal Count: 0 Primitive Seq Protocol Error Count: 0 Invalid Tx Word Count: 0 Invalid CRC Count: 0 Example 4 Listing All Remote Ports The following command lists all remote ports that are visible through the given HBA port: # fcinfo remote-port -p 210100e08b274cb5 Remote Port WWN: 50020f230000b4af Active FC4 Types: SCSI SCSI Target: yes Port Symbolic Name: unknown Node WWN: 50020f200000b4af Remote Port WWN: 210000e08b07daa6 Active FC4 Types: SCSI SCSI Target: no Port Symbolic Name: unknown Node WWN: 200000e08b07daa6 Remote Port WWN: 20030003ba27c788 Active FC4 Types: SCSI SCSI Target: yes Port Symbolic Name: unknown Node WWN: 10000003ba27c788 Remote Port WWN: 210000e08b096a60 Active FC4 Types: SCSI,IP SCSI Target: no Port Symbolic Name: unknown Node WWN: 200000e08b096a60 Example 5 Listing Remote Ports and Link Statistics The following command lists information for the remote ports and the link statistics for those ports: # fcinfo remote-port -l -p 210100e08b272ab5 Remote Port WWN: 210100e08b296a60 Active FC4 Types: SCSI,IP SCSI Target: no Port Symbolic Name: unknown Node WWN: 200100e08b296a60 Link Error Statistics: Link Failure Count: 0 Loss of Sync Count: 0 Loss of Signal Count: 0 Primitive Seq Protocol Error Count: 0 Invalid Tx Word Count: 0 Invalid CRC Count: 0 Remote Port WWN: 20030003ba27d56d Active FC4 Types: SCSI SCSI Target: yes Port Symbolic Name: unknown Node WWN: 10000003ba27d56d Link Error Statistics: Link Failure Count: 0 Loss of Sync Count: 4765165 Loss of Signal Count: 4765165 Primitive Seq Protocol Error Count: 0 Invalid Tx Word Count: 0 Invalid CRC Count: 0 Remote Port WWN: 210100e08b27f7a6 Active FC4 Types: SCSI SCSI Target: no Port Symbolic Name: unknown Node WWN: 200100e08b27f7a6 Link Error Statistics: Link Failure Count: 0 Loss of Sync Count: 0 Loss of Signal Count: 0 Primitive Seq Protocol Error Count: 0 Invalid Tx Word Count: 0 Invalid CRC Count: 0 Remote Port WWN: 50020f230000b897 Active FC4 Types: SCSI SCSI Target: yes Port Symbolic Name: unknown Node WWN: 50020f200000b897 Link Error Statistics: Link Failure Count: 0 Loss of Sync Count: 7 Loss of Signal Count: 7 Primitive Seq Protocol Error Count: 0 Invalid Tx Word Count: 0 Invalid CRC Count: 0 Remote Port WWN: 210100e08b27daa6 Active FC4 Types: SCSI SCSI Target: no Port Symbolic Name: unknown Node WWN: 200100e08b27daa6 Link Error Statistics: Link Failure Count: 0 Loss of Sync Count: 0 Loss of Signal Count: 0 Primitive Seq Protocol Error Count: 0 Invalid Tx Word Count: 0 Invalid CRC Count: 0 Remote Port WWN: 210000e08b074cb5 Active FC4 Types: SCSI,IP SCSI Target: no Port Symbolic Name: unknown Node WWN: 200000e08b074cb5 Link Error Statistics: Link Failure Count: 0 Loss of Sync Count: 0 Loss of Signal Count: 0 Primitive Seq Protocol Error Count: 0 Invalid Tx Word Count: 0 Invalid CRC Count: 0 Remote Port WWN: 210100e08b296060 Active FC4 Types: SCSI SCSI Target: no Port Symbolic Name: unknown Node WWN: 200100e08b296060 Link Error Statistics: Link Failure Count: 0 Loss of Sync Count: 0 Loss of Signal Count: 0 Primitive Seq Protocol Error Count: 0 Invalid Tx Word Count: 0 Invalid CRC Count: 0 Example 6 Listing All SCSI Targets and Link Statistics The following command lists all remote ports as well as the link statistics and scsi-target information: # fcinfo remote-port -sl -p 210100e08b272ab5 Remote Port WWN: 210100e08b296a60 Active FC4 Types: SCSI,IP SCSI Target: no Port Symbolic Name: unknown Node WWN: 200100e08b296a60 Link Error Statistics: Link Failure Count: 0 Loss of Sync Count: 0 Loss of Signal Count: 0 Primitive Seq Protocol Error Count: 0 Invalid Tx Word Count: 0 Invalid CRC Count: 0 Remote Port WWN: 20030003ba27d56d Active FC4 Types: SCSI SCSI Target: yes Port Symbolic Name: unknown Node WWN: 10000003ba27d56d Link Error Statistics: Link Failure Count: 0 Loss of Sync Count: 4765165 Loss of Signal Count: 4765165 Primitive Seq Protocol Error Count: 0 Invalid Tx Word Count: 0 Invalid CRC Count: 0 LUN: 0 Vendor: SUN Product: T4 OS Device Name: /dev/rdsk/c4t20030003BA27D56Dd0s2 LUN: 1 Vendor: SUN Product: T4 OS Device Name: /dev/rdsk/c4t20030003BA27D56Dd1s2 Remote Port WWN: 210100e08b27f7a6 Active FC4 Types: SCSI SCSI Target: no Port Symbolic Name: unknown Node WWN: 200100e08b27f7a6 Link Error Statistics: Link Failure Count: 0 Loss of Sync Count: 0 Loss of Signal Count: 0 Primitive Seq Protocol Error Count: 0 Invalid Tx Word Count: 0 Invalid CRC Count: 0 Remote Port WWN: 50020f230000b897 Active FC4 Types: SCSI SCSI Target: yes Port Symbolic Name: unknown Node WWN: 50020f200000b897 Link Error Statistics: Link Failure Count: 0 Loss of Sync Count: 7 Loss of Signal Count: 7 Primitive Seq Protocol Error Count: 0 Invalid Tx Word Count: 0 Invalid CRC Count: 0 LUN: 0 Vendor: SUN Product: T300 OS Device Name: Unknown LUN: 1 Vendor: SUN Product: T300 OS Device Name: /dev/rdsk/c4t50020F230000B897d1s2 LUN: 2 Vendor: SUN Product: T300 OS Device Name: /dev/rdsk/c4t50020F230000B897d2s2 LUN: 3 Vendor: SUN Product: T300 OS Device Name: /dev/rdsk/c4t50020F230000B897d3s2 LUN: 4 Vendor: SUN Product: T300 OS Device Name: /dev/rdsk/c4t50020F230000B897d4s2 LUN: 5 Vendor: SUN Product: T300 OS Device Name: /dev/rdsk/c4t50020F230000B897d5s2 LUN: 6 Vendor: SUN Product: T300 OS Device Name: /dev/rdsk/c4t50020F230000B897d6s2 LUN: 7 Vendor: SUN Product: T300 OS Device Name: /dev/rdsk/c4t50020F230000B897d7s2 LUN: 8 Vendor: SUN Product: T300 OS Device Name: /dev/rdsk/c4t50020F230000B897d8s2 LUN: 9 Vendor: SUN Product: T300 OS Device Name: /dev/rdsk/c4t50020F230000B897d9s2 LUN: 10 Vendor: SUN Product: T300 OS Device Name: /dev/rdsk/c4t50020F230000B897d10s2 LUN: 11 Vendor: SUN Product: T300 OS Device Name: /dev/rdsk/c4t50020F230000B897d11s2 LUN: 12 Vendor: SUN Product: T300 OS Device Name: /dev/rdsk/c4t50020F230000B897d12s2 LUN: 13 Vendor: SUN Product: T300 OS Device Name: /dev/rdsk/c4t50020F230000B897d13s2 LUN: 14 Vendor: SUN Product: T300 OS Device Name: /dev/rdsk/c4t50020F230000B897d14s2 LUN: 15 Vendor: SUN Product: T300 OS Device Name: /dev/rdsk/c4t50020F230000B897d15s2 Remote Port WWN: 210100e08b27daa6 Active FC4 Types: SCSI SCSI Target: no Port Symbolic Name: unknown Node WWN: 200100e08b27daa6 Link Error Statistics: Link Failure Count: 0 Loss of Sync Count: 0 Loss of Signal Count: 0 Primitive Seq Protocol Error Count: 0 Invalid Tx Word Count: 0 Invalid CRC Count: 0 Remote Port WWN: 210000e08b074cb5 Active FC4 Types: SCSI,IP SCSI Target: no Port Symbolic Name: unknown Node WWN: 200000e08b074cb5 Link Error Statistics: Link Failure Count: 0 Loss of Sync Count: 0 Loss of Signal Count: 0 Primitive Seq Protocol Error Count: 0 Invalid Tx Word Count: 0 Invalid CRC Count: 0 Remote Port WWN: 210100e08b296060 Active FC4 Types: SCSI SCSI Target: no Port Symbolic Name: unknown Node WWN: 200100e08b296060 Link Error Statistics: Link Failure Count: 0 Loss of Sync Count: 0 Loss of Signal Count: 0 Primitive Seq Protocol Error Count: 0 Invalid Tx Word Count: 0 Invalid CRC Count: 0 Example 7 Listing SCSI Target Information The following command lists all remote ports as well as the scsi-target information: # fcinfo remote-port -s -p 210100e08b272ab5 Remote Port WWN: 210100e08b296a60 Active FC4 Types: SCSI,IP SCSI Target: no Port Symbolic Name: unknown Node WWN: 200100e08b296060 Remote Port WWN: 20030003ba27d56d Active FC4 Types: SCSI SCSI Target: yes Port Symbolic Name: unknown Node WWN: 10000003ba27d56d LUN: 0 Vendor: SUN Product: T4 OS Device Name: /dev/rdsk/c4t20030003BA27D56Dd0s2 LUN: 1 Vendor: SUN Product: T4 OS Device Name: /dev/rdsk/c4t20030003BA27D56Dd1s2 Remote Port WWN: 210100e08b27f7a6 Active FC4 Types: SCSI SCSI Target: no Port Symbolic Name: unknown Node WWN: 200100e08b27f7a6 Remote Port WWN: 50020f230000b897 Active FC4 Types: SCSI SCSI Target: yes Port Symbolic Name: unknown Node WWN: 50020f200000b897 LUN: 0 Vendor: SUN Product: T300 OS Device Name: Unknown LUN: 1 Vendor: SUN Product: T300 OS Device Name: /dev/rdsk/c4t50020F230000B897d1s2 LUN: 2 Vendor: SUN Product: T300 OS Device Name: /dev/rdsk/c4t50020F230000B897d2s2 LUN: 3 Vendor: SUN Product: T300 OS Device Name: /dev/rdsk/c4t50020F230000B897d3s2 LUN: 4 Vendor: SUN Product: T300 OS Device Name: /dev/rdsk/c4t50020F230000B897d4s2 LUN: 5 Vendor: SUN Product: T300 OS Device Name: /dev/rdsk/c4t50020F230000B897d5s2 LUN: 6 Vendor: SUN Product: T300 OS Device Name: /dev/rdsk/c4t50020F230000B897d6s2 LUN: 7 Vendor: SUN Product: T300 OS Device Name: /dev/rdsk/c4t50020F230000B897d7s2 LUN: 8 Vendor: SUN Product: T300 OS Device Name: /dev/rdsk/c4t50020F230000B897d8s2 LUN: 9 Vendor: SUN Product: T300 OS Device Name: /dev/rdsk/c4t50020F230000B897d9s2 LUN: 10 Vendor: SUN Product: T300 OS Device Name: /dev/rdsk/c4t50020F230000B897d10s2 LUN: 11 Vendor: SUN Product: T300 OS Device Name: /dev/rdsk/c4t50020F230000B897d11s2 LUN: 12 Vendor: SUN Product: T300 OS Device Name: /dev/rdsk/c4t50020F230000B897d12s2 LUN: 13 Vendor: SUN Product: T300 OS Device Name: /dev/rdsk/c4t50020F230000B897d13s2 LUN: 14 Vendor: SUN Product: T300 OS Device Name: /dev/rdsk/c4t50020F230000B897d14s2 LUN: 15 Vendor: SUN Product: T300 OS Device Name: /dev/rdsk/c4t50020F230000B897d15s2 Remote Port WWN: 210100e08b27daa6 Active FC4 Types: SCSI SCSI Target: no Port Symbolic Name: unknown Node WWN: 200100e08b27daa6 Remote Port WWN: 210000e08b074cb5 Active FC4 Types: SCSI,IP SCSI Target: no Port Symbolic Name: unknown Node WWN: 200000e08b074cb5 Remote Port WWN: 210100e08b296060 Active FC4 Types: SCSI SCSI Target: no Port Symbolic Name: unknown Node WWN: 200100e08b296060 Example 8 Listing the Logical Unit The following command lists the logical unit: # fcinfo logical-unit /dev/rdsk/c0t600C0FF0000000000036223AE73EB705d0s2 /dev/rdsk/c0t600C0FF00000000000362272539E5B03d0s2 /dev/rmt/0n Example 9 Displaying Additional Information for the Logical Unit The following command displays additional information about the logical unit using the -v option for device /dev/rmt/On: # fcinfo lu -v /dev/rmt/On OS Device Name: /dev/rmt/0n HBA Port WWN: 210000e07c030b91 Remote Port WWN: 21010003b7830a6 LUN: 0 Vendor: STK Product: 9940A Device Type: Tape device The following command displays additional information about the logical unit using the -v option for device /dev/rdsk/c0t600C0FF0000000000036223AE73EB705d0s2 # fcinfo logical-unit -v /dev/rdsk/c0t600C0FF0000000000036223AE73EB705d0s2 OS Device Name: /dev/rdsk/c0t600C0FF0000000000036223AE73EB705d0s2 HBA Port WWN: 210100e08b27a8a1 Remote Port WWN: 256000c0ffc03622 LUN: 0 Remote Port WWN: 216000c0ff803622 LUN: 0 HBA Port WWN: 210000e08b07a8a1 Remote Port WWN: 256000c0ffc03622 LUN: 0 Remote Port WWN: 216000c0ff803622 LUN: 0 Vendor: SUN Product: StorEdge 3510 Device Type: Disk device Example 10 Adding an NIPV Port The following command adds an NPIV port to the HBA with a port name: 210000e08b170f1c The NPIV port has a port name of 2000000000000001 and a node name of 2100000000000001. # fcadm create-npiv-port -p 2000000000000001 -n 2100000000000001 210000e08b170f1c Created NPIV Port: HBA Port WWN: 2000000000000001 Node WWN: 2100000000000001 Physical HBA Port WWN: 210000e08b170f1c Example 11 Adding an NIPV Port with Random WWN The following command adds an NPIV port to the HBA with a randomly assigned port name of 210000e08b170f1c. # fcadm create-npiv-port 210000e08b170f1c Created NPIV Port: HBA Port WWN: 2038295824942801 Node WWN: 2100392849248001 Physical HBA Port WWN: 210000e08b170f1c Example 12 Deleting an NIPV Port The following command deletes an NPIV port. # fcadm delete-npiv-port -p 2000000000000001 -w 2100000000000001 210000e08b170f1c ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNW | +-----------------------------+-----------------------------+ |Interface Stability |Committed | +-----------------------------+-----------------------------+ SEE ALSO
attributes(5) ERROR MESSAGES
Errors that can occur in addition to the errors normally associated with system administration commands: o HBA_port_WWN: not found o Remote_port_WWN: not found o HBA_port_WWN: NPIV not supported on this HBA SunOS 5.11 4 Aug 2008 fcinfo(1M)
All times are GMT -4. The time now is 06:24 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy