Sponsored Content
Full Discussion: Basic SAN LUN query
Top Forums UNIX for Dummies Questions & Answers Basic SAN LUN query Post 302579589 by pinga123 on Tuesday 6th of December 2011 05:31:06 AM
Old 12-06-2011
Basic SAN LUN query

Hi guys,

We have created a LUN on SAN and assigned it to a server.

On top of it we have created 4 LVM shares which are holding the data.

Is it possible to add this LUN to some other server and access the data on LVM shares?(noob here)
 

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

A basic query

In a Bourne shell script, I often come across statements involving `sh -c`. I was not able to make out if any reason is there behind that. example: echo `sh -c 'date'` killing all server processes Instead of the above, I can use echo `date` killing all server processes. Is there any... (1 Reply)
Discussion started by: asutoshch
1 Replies

2. Solaris

Thoughts/experiences of SAN attaching V880 to EMC SAN

Hi everyone, I wonder if I can canvas any opinions or thoughts (good or bad) on SAN attaching a SUN V880/490 to an EMC Clarion SAN? At the moment the 880 is using 12 internal FC-AL disks as a db server and seems to be doing a pretty good job. It is not I/O, CPU or Memory constrained and the... (2 Replies)
Discussion started by: si_linux
2 Replies

3. Filesystems, Disks and Memory

Finding SAN Lun's on Linux.

Am trying to differentiate between the local disks and LUN's presented from SAN onto the server. Have Tried fdisk -l, however I quite cudn't differentiate the local disks from SAN presented LUN's. Can you pls. let me know the procedure and commands to find this. OS - RHEL 4 SAN - EMC... (3 Replies)
Discussion started by: Crazy_murli
3 Replies

4. 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

5. Shell Programming and Scripting

[Basic Query]bsh script in tcsh shell

I am a beginner (Just 2 days old:o ), i will really appreciate if you can solve my silly queries as below: Lets say i write a script like this #!/bin/bsh clear #to read name from keyboard echo "your name please.." read fname echo "you just entered $fname" exit 0 My environment is... (2 Replies)
Discussion started by: animesharma
2 Replies

6. Shell Programming and Scripting

(CSH basic construct) "@" query

While going through a script, i came across few syntax which I am not aware of what they exactly means. @ cnt = 1 @ num_all = `echo $var` What is the significance of "@" here. What is it called? (3 Replies)
Discussion started by: animesharma
3 Replies

7. UNIX for Advanced & Expert Users

Veritas LUN migrate query

Hi, We are migrating existing LUNS in veritas to new SAN. But the LUNS presented at new SAN are of very less size. What would be the ideal way to migrate/move the data ? Using VxVm 5.1 & VCS. Downtime of filesystem/application is fine. Thanks in advance. (1 Reply)
Discussion started by: unahb1
1 Replies

8. AIX

Mount a SAN LUN which contains clone copy - AIX 6.1

Hello Everyone, Can someone help me to mount a SAN hdisk which contains a clone data copy(san) of the remote server to the another machine. Both servers are running in AIX. Thanks in advance ! Regards, Gowtham.G (3 Replies)
Discussion started by: gowthamakanthan
3 Replies

9. Solaris

Can't see Newly created LUN by SAN admin

hello, i am an oracle DBA and trying to scan a newly created LUN of 200 GB on fiber channel by SAN admin.we have solaris 10 and SANtoolkit is installed.i tried following to get the new LUN at my machine. go /opt/Netapp/Santoolkit/bin and then ./sanlun lun show but i see only the existing... (12 Replies)
Discussion started by: janakors
12 Replies

10. Solaris

Solaris 10, adding new LUN from SAN storage

Hello to all, Actually, currently on my Solaris box, I've a LUN (5TB space) from a EMC storage which is working fine, and a partition with ZFS filesystem is created for that LUN. as further you'll see in the logs, the "c4t6006016053802E00E6A9196B6506E211d0s2" is the current configured LUN in the... (4 Replies)
Discussion started by: Anti_Evil
4 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 01:42 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy