Multi-homed Ignite Server

[Sebastien Masson]

Hi all,

I install a Ignite server on a host which has multi ip address in same subnet on one nic card. here the output of my netstat -nr

Routing tables
Destination Gateway Flags Refs Interface Pmtu
127.0.0.1 127.0.0.1 UH 0 lo0 4136
2.0.0.1 2.0.0.1 UH 0 lan0 4136
172.25.2.45 172.25.2.45 UH 0 lan1:2 4136
172.25.2.38 172.25.2.38 UH 0 lan1:1 4136
172.25.2.124 172.25.2.124 UH 0 lan1 4136
172.25.2.0 172.25.2.124 U 4 lan1 1500
172.25.2.0 172.25.2.45 U 4 lan1:2 1500
172.25.2.0 172.25.2.38 U 4 lan1:1 1500
2.0.0.0 2.0.0.1 U 2 lan0 1500
127.0.0.0 127.0.0.1 U 0 lo0 0
default 172.25.2.1 UG 0 lan1 0

And the output of my instl_adm config:

server="172.25.2.124"
netmask="255.255.255.0"
route_gateway[0]="172.25.2.1"
route_destination[0]="default"
_hp_keyboard="PS2_DIN_US_English"
_hp_lanadmin_args="-X 100FD"
disable_dhcp=true
run_ui=true
control_from_server=true

=========================

Now on any host, if I do a sea lan install, I always got 172.25.2.38 ip address. Why ? Why not my primary ip address (172.25.2.124), the IP defined in the instl_adm config ?

If I try bo lan.172.25.2.38 install, I got this:

Main Menu: Enter command or menu > bo lan.172.25.2.38 install
Interact with IPL (Y, N, or Cancel)?> n

Booting...
Network Station Address 00306e-27ac68
System IP Address 172.25.2.140
Server IP Address 172.25.2.38

Boot IO Dependent Code (IODC) revision 2

========================

And the boot hang there. I check in the syslog of my server and I got this line:

tftp/udp: Connection from unknown (172.25.2.140) at Thu Apr 24 09:38:36 2003

(172.25.2.140) is the IP of the server client on which I try to boot lan.
========================

If I try with bo lan.172.25.2.124 install the boot hang at booting...

Now, if I remove all the IP alias (lan1:1 and lan1:2) and leave only my primary IP address the bo lan.172.25.2.124 install work fine!

So please, help required. Somebody has the same configuration ?

Thanks

[John Poff]

Hi,

What does 'instl_adm -d' report?

JP

[Jerome Baron]

Hi Sebastien,

Ignite-UX does not support virtual lan interfaces until version B.4.2.

If you have this version, you can check if you have the latest tftp and SD-UX patch install.

Regards,
Jerome

[Sebastien Masson]

Hey!

After many test, I found the problem or the solution to multi-homed server.

Juste change the order of IP address in the /etc/hosts.

In that case I put the 172.25.2.124 after the two other and now sea lan install display 172.25.2.124 and bo lan.172.25.2.124 install work fine!

Ciao