09-14-2011
Identify Boot from SAN
Hi, I have many servers all of these are boot from SAN. Can anybody let me know that how to identify the server is Boot fron SAN and from which device?
Thanks
Rahul
10 More Discussions You Might Find Interesting
1. HP-UX
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)
Discussion started by: barun agarwal
0 Replies
2. Red Hat
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)
Discussion started by: navadeep
0 Replies
3. Solaris
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)
Discussion started by: q8devilish
3 Replies
4. UNIX for Advanced & Expert Users
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)
Discussion started by: fazzasx
0 Replies
5. UNIX for Dummies Questions & Answers
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)
Discussion started by: asanchez
4 Replies
6. Red Hat
Hello,
How can I identify SAN disks not in use by the OS?
Thank you. (8 Replies)
Discussion started by: asanchez
8 Replies
7. Solaris
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)
Discussion started by: fugitive
0 Replies
8. Solaris
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)
Discussion started by: rahul.kurumkar
0 Replies
9. UNIX for Dummies Questions & Answers
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)
Discussion started by: vamshigvk475
3 Replies
10. Solaris
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
pdc(1M) pdc(1M)
NAME
pdc - processor-dependent code (firmware)
DESCRIPTION
is the firmware that implements all processor-dependent functionality, including initialization and self-test of the processor. Upon com-
pletion, it loads and transfers control to the initial system loader (isl(1M)). Firmware behavior varies somewhat, depending on the hard-
ware as described below.
To load from an external medium, must know the particular device on which resides. Typically the device is identified by the Primary Boot
Path that is maintained by in Stable Storage. A path specification is an I/O subsystem mnemonic that varies according to hardware model.
When the processor is reset after initialization and self-test complete, reads the Console Path from Stable Storage, and attempts to ini-
tialize the console device. If the initialization fails, attempts to find and initialize a console device. Algorithms used to find a con-
sole device are model-dependent. then announces the Primary Boot, Alternate Boot, and Console Paths.
If (see isl(1M)) is enabled, provides a 10-second delay, during which time the operator can override the sequence by typing any character
on the console. If the operator does not interrupt this process, initializes and reads from the Primary Boot Path. On models that support
autosearch, if this path is not valid and (see isl(1M)) is enabled, then searches to find a bootable medium.
If allowed to complete, a list of potentially bootable devices is displayed, labeled with abbreviated path identifiers (P0, P1, etc). A
simple menu is then displayed where the user can:
o Boot a specific device, using the abbreviated path identifier, or the full mnemonic.
o Start a device search where the contents are searched for IPL images (note the first search only identified devices and did not
check the contents).
o Enter the boot administration level.
o Exit the menu and return to autobooting
o Get help on choices
If the sequence is unsuccessful, overridden by the operator, or not enabled in the first place, interactively prompts the operator for the
Boot Path to use. Any required path components that are not supplied default to zero.
The Primary Boot, Alternate Boot, and Console Paths as well as and enable can be modified via
SEE ALSO
boot(1M), isl(1M).
PA-RISC Systems Only pdc(1M)