two cards on same subnet

[H_16]

I have two btlan cards on the same subnet

and carried out the following:

#ifconfig lan1 ip_addr netmask_addr up
#ifconfig lan5 ip_addr netmaks_addr up
#lanadmin -x 1
Current Config = 100 Full-Duplex AUTONEG

# lanadmin -x 100FD 5
btlan: ERROR: Setting 100FD is unsupported
Current Config = NO LINK AUTONEG

I am having problems with modifying the second card to 100 Full duplex

Is this due to both cards on the same subnet is there are work around?

[Matti_Kurkela]

Having two or more cards on the same subnet should not cause any problems with duplex/speed settings, but it *will* cause problems with IP routing, unless you use APA and/or ServiceGuard.

(With "ndd -set /dev/ip ip_strong_es_model 1" you can make it work somewhat, but having two NICs simultaneously active on the same network segment without APA is an unsupported configuration and is not recommended.)

With APA you can get both cards active together. ServiceGuard can use APA if both are installed on the same server.

With just ServiceGuard only one of the cards can be active at a time. If it fails, SG will switch the traffic (and the IP addresses) to another card.

Without knowing the hardware type of your NICs and your HP-UX version & Quality Pack level, it's hard to guess what might be wrong.

The output of commands "ioscan -fnkClan" and "lanscan -v" would be very informative. If one of the cards is built-in to the system board of your server, the output of "model" command might be useful too.

MK

[F Verschuren]

You have to use the capital X to set the speet..
lanadmin -X 100FD 5
if it does not work please check the cable (linkloop.)

[F Verschuren]

explanation for linkloop
use lanscan to find out the mac adress
to check the cable in lan 5
linkloop -i [mac of lan5] 5
to check the cable in lan 1
linkloop -i [mac of lan1] 1
to check if lan 1 and 5 are in the same vlan.
linkloop -i [mac of lan1] 5

[Ganesan R]

Hi,

Could you provide the lan5 card details?
Is this card supports Full duplex?

Look at the errors.
>>btlan: ERROR: Setting 100FD is unsupported
Current Config = NO LINK AUTONEG<<

[F Verschuren · Accepted solution]

Just tested the ERROR it is the capital X verses the low letter x that is causing the error...
strange error code for this typo...

:nl11588> lanadmin -x 3
Current Config = 100 Full-Duplex MANUAL

nlxsms01:nl11588> lanadmin -x 100DF 3
btlan: ERROR: Setting 100DF is unsupported
Current Config = NO LINK

:nl11588> lanadmin -X 100DF 3
Must be super-user
:nl11588>

[UVK]

As said did you try
#lanadmin -X 100DF 5
You should be set with that, If not check for a couple of things
1) Cabling
2) Duplex setting on your switch
3) You NIC card spec's

[Jeroen Peereboom]

Did you both really type 100DF? Should be 100FD.

JP

[rick jones]

Frankly, in this day and age, unless one is playing with ancient networking kit, there should be no need to hardcode duplex settings. Your own output already shows that you were getting 100FD, which says the other side was doing autoneg, so unless you change the other side too, all setting a hardcode of FD will do is (not so subtly) break the link.

[Steven E. Protter]

Shalom,

In early versions of 11.11 this plan was strictly forbidden. I tried it once and both NIC cards dropped of the network instantly.

Later releases of 11.11 supposedly supported it.

I think you need APA, Auto Port Aggregation to get any real benefit of increased band width out of this configuration. That is the tool designed to do the job.

SEP