09-11-2011
Alot of information missing.. you're using iSCSI san boot or FC san boot? confusing.. if its FC , you need to change fp.conf. was any changes made to scsi_vhci.conf at all? If you want to turn off MPxIO for your SAN boot, you need to boot off cd and manually change the respective configurations including vfstab etc, before you can boot. You cant simply a edit a single file and expect the boot from san.
This User Gave Thanks to incredible For This Post:
10 More Discussions You Might Find Interesting
1. Solaris
Hi,
Anyone know how to turn on Solaris 8 audt trial
Thank (2 Replies)
Discussion started by: civic2005
2 Replies
2. Solaris
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
3. Solaris
Hi,
I have a quick question.
How can I see MPXIO statistics (like errors, how many I/O|throuput per path, ....) on Solaris 10? Does maybe a ready dtrace script exist (I do not have the knowledge to write one myself)?
I would be happy if somebody knows some good documentation/links (with... (1 Reply)
Discussion started by: victorinox
1 Replies
4. Solaris
System: Sun M3000 and M4000
OS: Solaris 10 (fully up to date with latest patches)
iSCSI HBA: 2x QLE4060C (QLogic)
In each system are 2 QLE4060C iSCSI adapters.
I manage to set up both HBA's to connect to the LUNs on the SAN
However I don't manage to enable multi-pathing.
Made the... (4 Replies)
Discussion started by: sb008
4 Replies
5. Solaris
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
I have been running some tests with solaris mpxio, dual-pathed to HDS SAN storage.
When I take a path offline, Solaris recognised this and a path is shown as offline in luxadm display <device>. However, it does not recover on reinstatement of the path until I run cfgadm -al.
Any ideas?
Phil (3 Replies)
Discussion started by: UKPhil
3 Replies
7. Solaris
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
8. Solaris
hi,
i am an oracle DBA and having problems with the starting of enterprise manager on solaris. one of solution is to check whether firewall is on or off
so i am new bie in solaris so kindly tell me how to check the firewall in solaris 10 and how to stop it and what are effects of such... (2 Replies)
Discussion started by: janakors
2 Replies
9. Solaris
Hi all,
I'm wondering if anyone knows whether Solaris IPMP can be configured such that the IPs of the physical NICs are not available to applications when using IP4 or if the group address and the underlying physical address are always present?
Thanks. (3 Replies)
Discussion started by: Skrynesaver
3 Replies
10. Solaris
Hi everybody,
i am working on the new script , its job discover the Storage Env ( especially MultiPATH ) and FC cards for solaris 11 sparc systems for now..
script is seem working ( but may contain any mistakes or bug ) on the oracle Qlogic fc cards on Emc_VMAx systems and Solaris 11 Sparc_64... (0 Replies)
Discussion started by: ygemici
0 Replies
LEARN ABOUT FREEBSD
loader.4th
LOADER.4TH(8) BSD System Manager's Manual LOADER.4TH(8)
NAME
loader.4th -- loader.conf processing tools
DESCRIPTION
The file that goes by the name of loader.4th is a set of commands designed to manipulate loader.conf(5) files. The default /boot/loader.rc
includes loader.4th and uses one of its commands to automatically read and process the standard loader.conf(5) files. Other commands exists
to help the user specify alternate configurations.
The commands of loader.4th by themselves are not enough for most uses. Please refer to the examples below for the most common situations,
and to loader(8) for additional commands.
Before using any of the commands provided in loader.4th, it must be included through the command:
include loader.4th
This line is present in the default /boot/loader.rc file, so it is not needed (and should not be re-issued) in a normal setup.
The commands provided by it are:
boot
boot kernelname [...]
boot directory [...]
boot -flag ... Boot as specified by the loader.conf(5) files read.
Depending on the arguments passed, it can override boot flags and either the kernel name or the search path for
kernel and modules.
boot-conf
boot-conf kernelname [...]
boot-conf directory [...]
boot-conf -flag ... Works like boot described above, but instead of booting immediately, uses autoboot, so it can be stopped.
start Reads /boot/defaults/loader.conf, all other loader.conf(5) files specified in it, then loads the desired kernel
and modules (if not already loaded). After which you can use the boot or autoboot commmands or simply exit
(provided autoboot_delay is not set to NO) to boot the system. start is the command used in the default
/boot/loader.rc file (see loader(8)).
initialize Initialize the support library so commands can be used without executing start first. Like start, it reads
/boot/defaults/loader.conf and all other loader.conf(5) files specified in it (but does not load kernel or
modules). Returns a flag on the stack to indicate if any configuration files were successfully loaded.
read-conf filename Reads and processes a loader.conf(5) file. Does not proceed to boot.
enable-module module Enables the loading of module.
disable-module module Disables the loading of module.
toggle-module module Toggles the loading of module on and off.
show-module module Shows the information gathered in the loader.conf(5) files about the module module.
retry Used inside loader.conf(5) files to specify the action after a module loading fails.
ignore Used inside loader.conf(5) files to specify the action after a module loading fails.
try-include file [file ...]
Process script files if they exist. Each file, in turn, is completely read into memory, and then each of its
lines is passed to the command line interpreter. If any error is returned by the interpreter, the try-include
command aborts immediately, without reading any other files, and silently returns without error.
FILES
/boot/loader The loader(8).
/boot/loader.4th loader.4th itself.
/boot/loader.rc loader(8) bootstrapping script.
/boot/defaults/loader.conf
File loaded by the start command.
EXAMPLES
Standard /boot/loader.rc:
include /boot/loader.4th
start
Load a different kernel with the standard configuration:
set kernel="kernel.old"
unload
boot-conf
Read an additional configuration file and then proceed to boot:
unload
read-conf /boot/special.conf
boot-conf
Disable the loading of the splash screen module and bitmap and then proceed to boot:
unload
disable-module splash_bmp
disable-module bitmap
boot-conf
SEE ALSO
loader.conf(5), loader(8)
HISTORY
The loader.4th set of commands first appeared in FreeBSD 3.2.
AUTHORS
The loader.4th set of commands was written by Daniel C. Sobral <dcs@FreeBSD.org>.
BUGS
A British espionage series.
BSD
November 13, 2013 BSD