Multi-homed IUX Svr

[Alan Shearer_1]

Hi Folks,

Hope you can help me get to bottom of this issue: We have an Ignite Svr which is connected to two subnets (will be more in the future); 10.50.10.0 and 10.50.11.0.

Some clients it will Ignite/make_net_rec are on .10 subnet, whilst others are on the .11 subnet.

On IUX svr, lan0 and the IP that instl_adm -d reports is on the .10 subnet.

Clients on .10 subnet can be Ignited fine. Clients on the .11 subnet can boot from server (I'm using bootptab) but they hit issue tftp'ing nbp.efi:

Boot file name: /opt/ignite/boot/nbp.efi

Retrieving File Size.
Retrieving File (TFTP)...\
PXE-E18: Timeout. Server did not respond.
Exit status code: Invalid Parameter

Just trying TFTP of this file on the IUX svr from a .11 client does produce the timeout issue. I suspect something is not correct with this second subnet configuration. Any guidelines on how this setup should be configured correctly?

Thanks.

[Steven E. Protter]

Shalom,

Seems like you have a PXE server interfering with the Ignite server.

What version of Ignite are we talking about?

If Ignite has migrated to PXE technology I didn't get the memo. So you need to isolate any networks using Ignite from PXE servers.

SEP

[Alan Shearer_1]

Hi SEP,

Thanks greatly for your response. I think you're heading in the wrong direction though.

There is not a PXE server interfering with the boot request (this I am sure of). Most systems now have cards that PXE boot, including IA64. The Ignite server responds to the DHCPDISCOVER request with a DHCPOFFER - it just ignores the fact that it is PXE capable. It points it straight to the network bootstrap file - which is the point I am stuck at. If a system cannot boot from your Ignite server it will often throw up an error returned by the PXE firmware on the local LAN card, like in the output I've shown.

This is an issue to do with the fact that the server is multi-homed as I can get it to work on either subnet, WHEN only ONE interface and default route is configured.

I'm sure people must have similar configs and have managed to configure this correctly? - so any thoughts/comments/guidelines would be a great help, as I'm stuck.

Thanks.

[Alan Shearer_1]

Ignite Version is c.7.6.98
HP-UX 11.23
All IA64 hardware

[Rasheed Tamton]

Hi,

Do you have any restriction in /var/adm/inetd.sec to block this specific subnet. Is there any messages on the syslog.log

Regards.

[Alan Shearer_1]

Hi Rasheed,

Thanks for your suggestions.

inetd.sec has no restriction on that subnet - in fact its just the default config.

No messages in syslog.

Anyone know what the routing table for this config should look like on the IUX server?

Thanks.

[Rasheed Tamton]

Hi Alan,

Did you try tftp manually using the IP and the hostname. Is there any difference.

# tftp hostname
tftp> get /opt/ignite/boot/fs_cfg.def /tmp/fs_cfg.def
Received 306 bytes in 0.0 seconds
tftp> quit

Regards.

[Alan Shearer_1]

Hi Rasheed,

Yeah I tried exactly that and get the same timeout.

I'm convinced I've not configured it sufficiently to accomodate the multiple NICs. Whether this is a routing issue, I'm only guessing.

Thanks.

[Rasheed Tamton]

Hi Alan,

The below thread might help - using a boot helper you can use diff subnets:

http://piyut.wordpress.com/2007/11/13/recovery-os-using-ignite-backup/

Did you look the ignite docs.

Regards.

[Alan Shearer_1]

Hi Again Rasheed,

Thanks for your suggestions.

I have read the docs - though there could easily be something I could have missed or not understood correctly.

I've seen the link you gave a while back on previous searches for information.

I also know from the docs about the boot helper option. Though the option that is preferred is to have the Ignite server on multiple subnets - so it can communicate directly with the clients, regardless of the subnet they are actually on.

Hopefully, there are folks out there doing this who can provide some guidance?

Thanks.

[noldi]

Hi Alan,

I'm not sure wether I'm on the right track here, but have you tried this.

instl_adm -d # will show you your current IUX network parameters


# If you need to change these, try this:
instl_adm -d > /tmp/file
vi /tmp/file
insl_adm -f /tmp/file

Good luck & best Regards,

Arnold

[wittie]

well instl_adm -d will show you the IP address configured with your Ignite Server. Take a look at the IP and notice that your IUX Server will be able to communicate to clients in the same subnet. If you wish to use this same IUX Server to install clients from your second subnet then you will have to follow the documentation and set up a boot helper. It is always necessary when IUX server & client IPs reside on different subnets.