Networker

Re: [Networker] HP-UX multiple Interfaces with same IP subnet

2008-06-26 04:44:20
Subject: Re: [Networker] HP-UX multiple Interfaces with same IP subnet
From: Birk Bohne <birk.bohne AT BATCHWORKS DOT DE>
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Date: Thu, 26 Jun 2008 10:33:23 +0200
Thanks for sharing your experiences. So i must configure both nics as a team. I 
tried to avoid this, because of my bad experiences with teaming under windows 
and linux. All teaming configurations with different hardware at different 
customers 
show no throughput gain on the receive side. The load balancing(also 802.3ad) 
works only for send packets. This is useless for backup servers and storage 
nodes... Maybe the HP-UX IP stack can surprise me this time.

greetings
Birk Bohne

----- "Stein-Are Smoge" <stein.are.smoge AT ROLLS-ROYCE DOT COM> schrieb:

> Hi, 
> 
> We tried this a couple of years ago. All clients who had the second
> NIC' 
> as "server network interface" sent their backup data to broadcast
> which 
> again caused our network to collapse.  The answer from HP was that it
> is 
> not supported. HP-UX does not work correctly when two NIC's are
> configued 
> in the same subnet. The onlky way to do that is either using bundeled
> NIC's 
> or NIC's in different subnets. 
> 
> Our solution was to buy the Auto Port Aggregation (APA. This allowed
> us to 
> bundle three NIC's into one VLAN(server LAN) and another three in a 
> different VLAN(deignated backup LAN) in two different subnets.  As APA
> in 
> combination with Cisco only supports four bundeled NIC's this was the
> only 
> solution to utilize all our six NIC's
> 
> Sorry for the bad news.
> 
> Regards
> Stein-Are Smoge
> ICT Senior Consultant
> Rolls-Royce Marine - ICT Operations - Head Office Ulsteinvik
> Email:stein.are.smoge AT rolls-royce DOT com
> Phone:        +4770014298
> Mobile:       +4795721585
> Fax:             +4770014020

To sign off this list, send email to listserv AT listserv.temple DOT edu and 
type "signoff networker" in the body of the email. Please write to 
networker-request AT listserv.temple DOT edu if you have any problems with this 
list. You can access the archives at 
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER