Saw you post for Solaris as well.. but for contemporary Red Hat.. ones with reasonable /sys (sysfs)... you can parse through the mess and get some helpful data. But I'm assuming that things are fairly "regular".. I mean, you can always boot from strange device in the BIOS of the HBA from the host and everything else magically comes from somewhere else... in which case what you glean from the server OS isn't all that useful. But, if you know the device your're booting from is fairly uniform, that is, perhaps it's the same device that owns the root (/) filesystem or /boot even.. then you can explore /sys and likely get some data about the STORAGE device disk... and you can even get HBA data.
For example... because /sys contains SOOO much... here's a snippet to glean some interesting data about fibre transports (e.g. a fibre channel based SAN network):
If you can successfully run that, you will see the "sda" "sdb", etc... block stuff and likely be able to better tie such to the actual SAN data you are looking for... but again, almost anything is possible... just saying what is typical.... it's possible that you won't be able to get what you are looking for through the OS at all and will have to get the data from the HBA somehow (it's there, just not necessarily easily viewable from the OS).
Hi all,
I am trying to configure my HPUX host 11.31 IA64 to boot from a LUN for EMC clariion CX3-80 (Flaire PNR 26).
I am following the below mentioned steps..
vi /tmp/idf
3
EFI 500MB
HPUX 100%
HPSP 400MB
idisk -f /tmp/idf -w /dev/rdisk/diskxxx
insf -e
pvcreate -B... (0 Replies)
hi all,
i have qle 2460 hba card in my server. and i have a lun from promise array from raid 0. I want to boot my OS (rhel5.2-64 bit) lun on a dell t300 server. can some one help me on this please asap.. (0 Replies)
My current situation is like this, I have a v440 connected to a netapp central storage 3140 via fiber channel, my OS and oracle is installed in the internal drive of the v440.
What I would like to do is to advertise another LUN in netapp to the v440 and let my v440 boot from it so I can start... (3 Replies)
Hi There,
Has anyone had any luck with or know how to get AIX 5+ to boot from a HP EVA 6000 SAN?
The servers used here will be P Class Blades
My initial searches on this so far did not bring results so I am guessing this may not be possible on HP SAN's but please let me know if I am... (0 Replies)
Hello everybody,
I'm using the binary inqraid (Linux RHEL) in order to retrieve information about SAN disks. The questions are:
Given an LDEV, how do I know if the SAN disk related to this LDEV is being used by the OS? I mean, how can I demonstrate to "Storage department" that all disks of... (4 Replies)
I have a solaris 10 box which does not have internal disks it has just a single dual port HBA card. Storage team has assigned 2 LUNs to the system and i can see it from the probe-scsi-all
/pci@3,700000/SUNW,emlxs@0,1
Device PortID 10100 WWPN 5006016941e0a08d
LUN 0 Disk DGC ... (0 Replies)
How to identify the server is BOOT FROM SAN.
Also how one can find from which device it is booted?
Thanks
Rahul
Double post, continued here (0 Replies)
We can Know the storage devices in fdisk -l. But Please tell me how can i identify the SAN devices :wall:
How SAN devices are represented in the fdisk -l output :wall::wall:
Thanks in Advance........:D (3 Replies)
I am working on VM host and collecting data to identify the type of storage attached to the server which will be migrated to VNX.
it has one ldom created on it
luxadm probe output ---
No Network Array enclosures found in /dev/es
Found Fibre Channel device(s):
Node... (7 Replies)
Discussion started by: kpatel786
7 Replies
LEARN ABOUT SUSE
tran_tgt_init
tran_tgt_init(9E) Driver Entry Points tran_tgt_init(9E)NAME
tran_tgt_init - request to initialize HBA resources on behalf of a particular target
SYNOPSIS
#include <sys/scsi/scsi.h>
void prefixtran_tgt_init(dev_info_t *hba_dip, dev_info_t *tgt_dip, scsi_hba_tran_t *hba_tran, struct scsi_device *sd);
INTERFACE LEVEL
Solaris architecture specific (Solaris DDI).
PARAMETERS
hba_dip Pointer to a dev_info_t structure, referring to the HBA device instance.
tgt_dip Pointer to a dev_info_t structure, referring to the target device instance.
hba_tran Pointer to a scsi_hba_tran(9S) structure, consisting of the HBA's transport vectors.
sd Pointer to a scsi_device(9S) structure, describing the target.
DESCRIPTION
The tran_tgt_init() vector in the scsi_hba_tran(9S) structure may be initialized during the HBA driver's attach(9E) to point to an HBA
driver function to be called by the system when an instance of a target device is being created. The tran_tgt_init() vector, if not
NULL,is called after the dev_info node structure is created for this target device instance, but before probe(9E) for this instance is
called. Before receiving transport requests from the target driver instance, the HBA may perform any initialization required for this par-
ticular target during the call of the tran_tgt_init() vector.
Note that hba_tran will point to a cloned copy of the scsi_hba_tran_t structure allocated by the HBA driver if the SCSI_HBA_TRAN_CLONE flag
was specified in the call to scsi_hba_attach(9F). In this case, the HBA driver may choose to initialize the tran_tgt_private field in the
structure pointed to by hba_tran, to point to the data specific to the particular target device instance.
RETURN VALUES
tran_tgt_init() must return:
DDI_SUCCESS the HBA driver can support the addressed target, and was able to initialize per-target resources.
DDI_FAILURE the HBA driver cannot support the addressed target, or was unable to initialize per-target resources. In this event, the
initialization of this instance of the target device will not be continued, the target driver's probe(9E) will not be
called, and the tgt_dip structure destroyed.
SEE ALSO attach(9E), probe(9E), tran_tgt_free(9E), tran_tgt_probe(9E), scsi_hba_attach_setup(9F), scsi_device(9S), scsi_hba_tran(9S)
Writing Device Drivers
SunOS 5.10 1 Nov 1993 tran_tgt_init(9E)