Sponsored Content
Special Forums IP Networking Quick Poll: Solaris IP Multipathing Post 44393 by kduffin on Friday 5th of December 2003 09:22:40 AM
Old 12-05-2003
I've actually seen network failures enough to always try to implement mulipathing where possible. I also try to have the interfaces set to seperates switches to take in account a switch failure. I've seen the following happen at least once:

1. Cisco switch/NIC card settings mismatch - especially when companies have a distinct sepearation between network and host responsibilities. Most networking devices autonegotiate speed and duplex settings by default. Autonegotiation is fine when connecting links that aren't permanent, but permanent links should have hard-coded speed and duplex settings at both ends. More than once a good intentioned NE has made changes that have caused problems on a NIC.
2. Afore mentioned switch failure.
3. Bad cable
4. Failed NIC

Whenever a single point of failure can be removed, it should be.

Cheers,

Keith
 

7 More Discussions You Might Find Interesting

1. Solaris

Quick question about Solaris =)

:D Just curious, I know that solaris 2.0-2.x_present are System V UNIX... But, I have only used Solaris 10, 9 and 2.5... On a 2.5 Sparc box, after you login you get presented with the usual SunOS 5.5.1 then UNIX(R) System V Release 4.0 I know Solaris 9 and 10 do not include this banner... ... (0 Replies)
Discussion started by: ssorel
0 Replies

2. Solaris

solaris multipathing

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

Solaris IP Multipathing (IPMP) Help

Hello All, I work for a Health care company at a local trauma hospital. I maintain a Picture Archiving and Communication System (PAC's). Basically, any medical images (X-Ray, CT, MRI, Mammo, etc) are stored digitally on the servers for viewing and dictation from diagnostic stations. I took over... (10 Replies)
Discussion started by: mainegeek
10 Replies

4. Solaris

Solaris IP Multipathing

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

5. Solaris

Disable Inbuilt multipathing software of Solaris 10

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

6. Solaris

Solaris multipathing

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

ZeusIOPS multipathing failed Solaris 11

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
AN(4)							   BSD Kernel Interfaces Manual 						     AN(4)

NAME
     an -- Aironet Communications 4500/4800 wireless network adapter driver

SYNOPSIS
     To compile this driver into the kernel, place the following lines in your kernel configuration file:

	   device an
	   device wlan

     Alternatively, to load the driver as a module at boot time, place the following line in loader.conf(5):

	   if_an_load="YES"

DESCRIPTION
     The an driver provides support for Aironet Communications 4500 and 4800 wireless network adapters and variants, including the following:

	   o   Aironet Communications 4500 and 4800 series
	   o   Cisco Aironet 340 and 350 series
	   o   Xircom Wireless Ethernet Adapter

     Support for these devices include the ISA, PCI and PCMCIA varieties.  The Aironet 4500 series adapters operate at 1 and 2Mbps while the
     Aironet 4800 series and Cisco adapters can operate at 1, 2, 5.5 and 11Mbps.  The ISA, PCI and PCMCIA devices are all based on the same core
     PCMCIA modules and all have the same programming interface, however unlike the Lucent WaveLAN/IEEE cards, the ISA and PCI cards appear to the
     host as normal ISA and PCI devices and do not require any PCCARD support.

     The PCMCIA Aironet cards require PC Card support, including the kernel pccard(4) driver.  ISA cards can either be configured to use ISA Plug
     and Play or to use a particular I/O address and IRQ by properly setting the DIP switches on the board.  (The default switch setting is for
     Plug and Play.)  The an driver has Plug and Play support and will work in either configuration, however when using a hard-wired I/O address
     and IRQ, the driver configuration and the NIC's switch settings must agree.  PCI cards require no switch settings of any kind and will be
     automatically probed and attached.

     All host/device interaction with the Aironet cards is via programmed I/O.	The Aironet devices support 802.11 and 802.3 frames, power manage-
     ment, BSS (infrastructure) and IBSS (ad-hoc) operation modes.  The an driver encapsulates all IP and ARP traffic as 802.11 frames, however it
     can receive either 802.11 or 802.3 frames.  Transmit speed is selectable between 1Mbps, 2Mbps, 5.5Mbps, 11Mbps or "auto" (the NIC automati-
     cally chooses the best speed).

     By default, the an driver configures the Aironet card for infrastructure operation.

     For more information on configuring this device, see ifconfig(8).

DIAGNOSTICS
     an%d: init failed	The Aironet card failed to become ready after an initialization command was issued.

     an%d: failed to allocate %d bytes on NIC  The driver was unable to allocate memory for transmit frames in the NIC's on-board RAM.

     an%d: device timeout  The Aironet card failed to generate an interrupt to acknowledge a transmit command.

SEE ALSO
     altq(4), arp(4), miibus(4), netintro(4), wlan(4), ancontrol(8), ifconfig(8)

HISTORY
     The an device driver first appeared in FreeBSD 4.0.

AUTHORS
     The an driver was written by Bill Paul <wpaul@ee.columbia.edu>.

BSD								   July 16, 2005							       BSD
All times are GMT -4. The time now is 01:19 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy