12-27-2007
Yes, I should have mentioned the whole "path" along which failures can happen...
How we do it is:
1. Cables come to network panels from different switches that are housed in different cabinets.
2. Network cables from the patch panels plug in to NICs which are on different cards - housed in different PCI slots (or one onboard and one in a PCI slot).
10 More Discussions You Might Find Interesting
1. IP Networking
I've setup Solaris IP Multipathing under Solaris whenever the hardware to do so was available. I find it amazing though that so few places I've worked at don't use it until I arrive. I wanted to find out if I'm running into all the exceptions, or is it really not being used? ... (3 Replies)
Discussion started by: kduffin
3 Replies
2. Solaris
I have solaris 10 sparc. I installed a Qlogic hba card.
This card is connected on a brocade switch and the brocade is connected on 2 different controllers on a Hitachi disk bay.
I formated 2 luns. On my solaris system, i have 4 disk.
How to configure solaris 10 to fix the dual disk view.
... (4 Replies)
Discussion started by: simquest
4 Replies
3. Solaris
Hi,
I saw your post on the forums about how to setup IP multipathing. I wanted your help on the below situation .
I have 2 servers A and B . Now they should be connected to 2 network switches . S1 and S2.
Now is it possible to have IP Multipathing on each of the servers as follows ?
... (0 Replies)
Discussion started by: maadhuu
0 Replies
4. Solaris
Dear UNIX Gurus
I need to know how to disable MPXIO feature (Inbuilt multipathing software of Solaris 10) as we are going to implemented iSCSI EMC based SAN. I am bit new to this feature so kindly suggest how to disable it
Regards (4 Replies)
Discussion started by: girish.batra
4 Replies
5. Solaris
Hi friends ,
can anyone provide me the complete steps to configure IPMP in solaris 9 or 10 provided i have two NIC card ?
regards
jagan (4 Replies)
Discussion started by: jaganblore
4 Replies
6. Solaris
Hai
we using emc storage which is conneted to M5000 through san switch.
we asign 13 luns but in server it is showing 22 luns.
i enable the solaris multipathing (MPxIO)
#more /kernel/drv/fp.conf in that file
MPxio-disable=no
#mpathadm list lu
it shows ... (2 Replies)
Discussion started by: joshmani
2 Replies
7. Solaris
Can any one please explain me the concept behind IPMP in solaris clustering.Basic explanation would be really appreciated...
Thanks in Advance
vks (2 Replies)
Discussion started by: vks47
2 Replies
8. Solaris
hi,
just installed solaris 11.1 (11.1.9.5.1) on a sun7410 ZFSSA (x4440 + j4400), but when I enable multipathing with "stmsboot -e", only the 1TB SATA drives inside the j4400 are configured as multipathed vhci / mpxio devices, but the logzillas / ZeusIOPS drives are skipped. the server is... (0 Replies)
Discussion started by: pressy
0 Replies
9. Solaris
hi all,
i start with solaris 11 and i am disapointed by the change on ip managing.
i want to set a ipmp over tow aggregate but i dont find any doc and i am lost with the new commande
switch1
net0 aggregate1 |
net1 aggregate1 |-----|
|... (1 Reply)
Discussion started by: sylvain
1 Replies
10. Solaris
Hi all,
Just a few questions ->
Is an "OFFLINE" interface going back to "ONLINE" consider as a failback by IPMP ?
I have "FAILBACK=no" in my /etc/default/mpathd; however when i do the following
(igb0 and igb7 are in the same ipmp link based group)
q1) why does "if_mpadm -r igb7" cause... (0 Replies)
Discussion started by: javanoob
0 Replies
LEARN ABOUT CENTOS
biosdevname
BIOSDEVNAME(1) General Commands Manual BIOSDEVNAME(1)
NAME
biosdevname - give BIOS-given name of a device
SYNOPSIS
biosdevname [options] [args]...
DESCRIPTION
biosdevname takes a kernel device name as an argument, and returns the BIOS-given name it "should" be.
OPTIONS
-i, --interface
Treat [args] as ethernet devs
-d, --debug
Enable debugging
-p, --policy [physical|all_ethN]
-P, --prefix [string]
string use for embedded NICs in the physical policy (default=em)
-x, --nopirq
Do not use $PIR table for mapping PCI device to slot. Some BIOS have incorrect values.
-s, --smbios [x.y]
Require minimum SMBIOS version x.y
POLICIES
The physical policy is the current default. However, when invoking biosdevname in udev rules, one should always specify the policy you
want, as the default has changed over time.
The physical policy uses the following scheme:
em<port>[_<virtual instance>]
for embedded NICs
p<slot>p<port>[_<virtual instance>]
for cards in PCI slots
The all_ethN policy makes a best guess at what the device order should be, with embedded devices first, PCI cards in ascending slot
order, and ports in ascending PCI bus/device/function order breadth-first. However, this policy does not work if your PCI devices
are hot-plugged or hot-pluggable, including the virtual functions on an SR-IOV device. In a hot-plug scenario, each separate udev
instance will be invoked in parallel, while the device tree is still being populated with new devices. Each udev instance will see
a different PCI tree, and thus cannot provide consistent enumeration. Use of this policy should be limited to only scenarios where
all PCI devices are present at boot (cold-plug).
EXIT CODES
Returns 0 on success, with BIOS-suggested name printed to stdout.
Returns 1 on provided device name lookup failure.
Returns 2 if system BIOS does not provide naming information. biosdevname requires system BIOS to provide naming information, either via
SMBIOS or sysfs files.
Returns 3 if not run as root but requires root privileges.
Returns 4 if running in a virtual machine.
SEE ALSO
http://linux.dell.com/wiki/index.php/Oss/libnetdevname
http://linux.dell.com/files/biosdevname/
git://linux.dell.com/biosdevname.git
RELATED PROGRAMS
The dmidecode package contains two tools useful for debugging BIOS features that biosdevname uses, specifically dmidecode to read the
SMBIOS Type 9 and Type 41 tables, and biosdecode to read the PCI IRQ Routing Table. Please include the output of each of these programs in
any bug reports.
AUTHOR
biosdevname was written by Matt Domsch <Matt_Domsch@dell.com>
This manual page was written by Rudy Gevaert <Rudy.Gevaert@UGent.be>, for the Debian project (but may be used by others).
Nov 28, 2010 BIOSDEVNAME(1)