Sponsored Content
Operating Systems Linux EMC, PowerPath and issue on using LUN Post 302582322 by mark54g on Thursday 15th of December 2011 01:48:22 PM
Old 12-15-2011
locate a script online (open source) called rescan-scsi-bus.sh

run it with -l -w -c

See if that helps

Failing that, crack open the manual on powerpath.
 

10 More Discussions You Might Find Interesting

1. Filesystems, Disks and Memory

Can Veritas DMP & EMC PowerPath coexist?

We currently have a Solaris box connected to a Clariion storage system that is utilising DMP for path failover. I would prefer to use EMC's Powerpath and was wondering if the two can coexist? Basically, I am struggling to find any documentation on the subject and was wonder if anyone can give me... (2 Replies)
Discussion started by: aaron2k
2 Replies

2. Solaris

I have LUN ID, how to find disk relate to that LUN ID?

I have a list of LUN ID, my task is to find if disk has been added or not. How do I do that? I have been searching the forum and not able to find answer. thanks (4 Replies)
Discussion started by: uuontario
4 Replies

3. Red Hat

Configure EMC Powerpath?

Hi , I have a redhat 5.3 server which has 2 vg.. one is rootvg in local harddisk and another one is applicationvg in SAN.. When I reboot the server , EMC powerpath driver is not starting up automatically. Hence applicationvg is not mounting properly. Therefore I need to unmount it manually and... (4 Replies)
Discussion started by: Makri
4 Replies

4. UNIX for Advanced & Expert Users

Removing EMC LUN from Solaris 10 host without a reboot

I have seen a few threads / posts on the forum's but nothing specific to what Iam after. So Iam hoping you can help. Issue : Iam hoping to remove unused emc luns from my solaris servers , T2000 (5.10 Generic_142900-02). I have a list of the process I have followed for the removal of the luns.... (3 Replies)
Discussion started by: furby
3 Replies

5. Solaris

Solaris/vxvm/EMC Lun configuration

Hello all, i try to allocate the same LUN to two server (or more in the future) i use solaris 10, vxvm (vxfs) for data and solaris zones and EMC DMX-4, i try to migrate solaris zones between servers in case of problem. and this is what i want to do - affect LUN to srv00124 and srv10155 -... (5 Replies)
Discussion started by: mat_solaris
5 Replies

6. Solaris

One emc powerpath failed

It seems like I lost one path on my Solaris-11 box. But I want to make sure before going to Storage team, if issue is from OS side or Storage side. Storage team is able to see that only one wwwn is looged in their switch. I am not at server's physical location. What does below output says ? I... (0 Replies)
Discussion started by: solaris_1977
0 Replies

7. Solaris

Emc powerpath device & zfs query

Hi, We're trying out a SAN migration from HP EVA to EMC VMAX, and run into a bit of an issue with powerpath and zfs. The method we're currently using to migrate is to export the HP EVA luns from our sun server, replicate using SAN based method, and then present the new luns to our Sun server... (7 Replies)
Discussion started by: badoshi
7 Replies

8. Solaris

Solaris OS having issue accessing LUN from Qlogic swich

Hi Community, I am facing one issue related storage accessing from solaris 10 machine(M5000). it was working fine then we shifted to another site. the only change on that site is FC switch. The issue i am facing is from solaris machine i can able to see the LUN, it;s only a test lun of 30... (17 Replies)
Discussion started by: bentech4u
17 Replies

9. AIX

AIX Migration issue with EMC ODM sets

Hi Experts , I want to start migrating our AIX 6.1 to AIX 7.1 . I am planning to use alt_disk_migration . Chris gibson has awesome documentation in the internet. However I am running into an issue with EMC odm filesets . So my current OS is AIX 6.1. and I have this : lslpp -l | grep EMC ... (7 Replies)
Discussion started by: JME2015
7 Replies

10. AIX

AIX help -reconnect EMC lun

we have an old AIX system with important data on an EMC LUN. the AIX server crashed and we had to rebuild it with the old AIX os 5.8. how do we reconnect the EMC LUN without losing the data? (15 Replies)
Discussion started by: jhudson12
15 Replies
fcinfo(1M)																fcinfo(1M)

NAME
fcinfo - Fibre Channel HBA Port Command Line Interface SYNOPSIS
fcinfo hba-port [-l] [HBA_port_WWN...] fcinfo remote-port [-ls] [-p HBA_port_WWN] [REMOTE_port_WWN...] fcinfo [-V] fcinfo [-?] fcinfo is a command line interface that collects administrative information on fibre channel host bus adapter (HBA) ports on a host. It also collects data on any fibre channel targets that may be connected to those ports in a Storage Area Network (SAN). SUBCOMMANDS The following subcommands are supported: hba-port Lists information for the HBA port referenced by the specified HBA_port_WWN. If HBA_port_WWN is not specified, all 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. 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. -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. The -p option can only be used with the remote-port subcommand and is a mandatory option. -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. -V, --version Prints the version information. -?, --help Prints the usage information. EXAMPLES
Example 1: Listing all HBA ports The following command lists all fibre channel HBA ports on the host: # fcinfo hba-port HBA Port WWN: 210000e08b074cb5 OS Device Name: /dev/cfg/c1 Manufacturer: QLogic Corp. Model: 375-3108-xx Type: N-port State: online Supported Speeds: 1Gb 2Gb Current Speed: 2Gb Node WWN: 200000e08b074cb5 HBA Port WWN: 210100e08b274cb5 OS Device Name: /dev/cfg/c2 Manufacturer: QLogic Corp. Model: 375-3108-xx Type: N-port State: online Supported Speeds: 1Gb 2Gb Current Speed: 2Gb Node WWN: 200100e08b274cb5 HBA Port WWN: 210000e08b072ab5 OS Device Name: /dev/cfg/c3 Manufacturer: QLogic Corp. Model: 375-3108-xx Type: L-port State: online Supported Speeds: 1Gb 2Gb Current Speed: 2Gb Node WWN: 200000e08b072ab5 HBA Port WWN: 210100e08b272ab5 OS Device Name: /dev/cfg/c4 Manufacturer: QLogic Corp. Model: 375-3108-xx Type: N-port State: online Supported Speeds: 1Gb 2Gb Current Speed: 2Gb Node WWN: 200100e08b272ab5 Example 2: 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 OS Device Name: /dev/cfg/c1 Manufacturer: QLogic Corp. Model: 375-3108-xx 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 OS Device Name: /dev/cfg/c2 Manufacturer: QLogic Corp. Model: 375-3108-xx 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 3: 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 Node WWN: 50020f200000b4af Remote Port WWN: 210000e08b07daa6 Active FC4 Types: SCSI SCSI Target: no Node WWN: 200000e08b07daa6 Remote Port WWN: 20030003ba27c788 Active FC4 Types: SCSI SCSI Target: yes Node WWN: 10000003ba27c788 Remote Port WWN: 210000e08b096a60 Active FC4 Types: SCSI,IP SCSI Target: no Node WWN: 200000e08b096a60 Example 4: 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 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 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 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 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 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 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 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 5: 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 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 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 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 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 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 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 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 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 Node WWN: 200100e08b296a60 Remote Port WWN: 20030003ba27d56d Active FC4 Types: SCSI SCSI Target: yes 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 Node WWN: 200100e08b27f7a6 Remote Port WWN: 50020f230000b897 Active FC4 Types: SCSI SCSI Target: yes 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 Node WWN: 200100e08b27daa6 Remote Port WWN: 210000e08b074cb5 Active FC4 Types: SCSI,IP SCSI Target: no Node WWN: 200000e08b074cb5 Remote Port WWN: 210100e08b296060 Active FC4 Types: SCSI SCSI Target: no Node WWN: 200100e08b296060 See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNW | +-----------------------------+-----------------------------+ |Interface Stability |Evolving | +-----------------------------+-----------------------------+ attributes(5) ERROR MESSAGES
Errors that can occur in addition to the errors normally associated with system administration commands: HBA_port_WWN: not found REMOTE_port_WWN: not found 17 Feb 2005 fcinfo(1M)
All times are GMT -4. The time now is 07:39 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy