How to define/specify OUTBOUND/INBOUND Network Interface Card?

[remer]

if i'm using lan0, lan1 and lan2, how can i specify or designate which will be the outbound or inbound network interface card?

Thanks.

[Laurent Menase]

It may not work but try:
1) define the ifconfig with -arp option on lan0
2) define the interface in a different subnet
3) then add a permanent arp publication of lan0 IP adddres with lan2 mac address


This may work, the difficulty is to make that the switch if it is the same one differenciate the 2 routes.

If the switch builds its mac table with arp answers it can work, if it builds it with usual ip messages, it will not work

[Torsten.]

You should only open 1 thread about a specific question, but you have 2.
http://forums11.itrc.hp.com/service/forums/questionanswer.do?threadId=1201652

Consider to close one of them and refer to the other.

Not really sure about the question.

Do you have 2 NICs in the same subnet?
Maybe this is your problem.

[Ramesh S]

Hi

As far as i know, cant designate a NIC for only outbound or inbound traffic.

If you are using APA configuration, you could do load balancing.

Thanks & Regards

Ramesh

[remer]

yes i have three NICs on same subnet.

thanks.

[Torsten.]

In order to use several NICs on the same subnet you should read about APA
(HP Auto Port Aggregation):

http://docs.hp.com/en/J4240-90035/index.html

[remer]

so does this mean even the remote user specify which NIC/IP to use as inbound interface, it still enter to the default lan card?

[Ramesh S]

Hi

so does this mean even the remote user specify which NIC/IP to use as inbound interface, it still enter to the default lan card?

Remote users are suppose to specify the IP to connect. Not to specify NIC.

If you created a aggregated port with 2 3 NIC's by APA, you need to configure IP for the same.

Thanks & Regards

Ramesh

[Matti_Kurkela]

Installing multiple physical NICs to one host and connecting them all to the same subnet is not supported. It may not always fail immediately, but it *will* cause problems eventually. HP-UX's network stack is simply not designed to work that way.

If you need multiple IP addresses, use IP aliases (i.e. lan0, lan0:1 and lan0:2 instead of lan0, lan1, lan2). To create one, just ifconfig it. See "man ifconfig".

If you need more network bandwidth, use APA or get a higher-speed NIC. For redundancy, use APA (or ServiceGuard, if applicable to your situation).

MK

[Laurent Menase]

> Installing multiple physical NICs to one >host and connecting them all to the same >subnet is not supported. It may not always >fail immediately, but it *will* cause >problems eventually. HP-UX's network stack >is simply not designed to work that way.

In fact it is not that simple: it is supported - see 11iv2 release note.
If you specify that all the NIC are in the same subnet, you can't be sure by which NIC the message is outbound or inbound, except if you specify ndd param ip_strong_es_model to 2.

If you want to load balance inbound you need that your switch does load balacing.

[Laurent Menase · Accepted solution]

in fact the difficulty with strong es set to 2 it will be probably difficult to split the inbound and outbound traffic. But it is the only way to have a quasi deterministic behavior when you have multiple interfaces on the same subnet.

[Laurent Menase]

In fact the difficulty with strong es set to 2 it will be probably difficult to split the inbound and outbound traffic. But it is the only way to have a quasi deterministic behavior when you have multiple interfaces on the same subnet.

[rick jones]

You also need to add specific routes pointing at specific local IPs to get stuff spread going outbound, and make sure that you have your applications bind to specific local IP's.

The best thing to do is to go ahead and get APA installed and use it.