Ignite push resets to half duplex

[jmb]

I have the Ignite process running just fine when I do pull installs. The lanadmin setting in "instl_adm" works great.

Now when I'm trying to do a push from the same server, with the force to 100FD as the first entry in INSTALLFS, the client appears to be ignoring it. My installation would have normally finished an hour ago, but it's still clunking along.

I can kill the process, and start again, but I need to know how to force the client to full duplex, after the Ignite server has rebooted it. I didn't think I had control over the client at that point. This push is mostly controlled from the server. Is there something I need to do when the client's installation menu when it says I "don't need to do anything more on the client"?

Also, is there any functional difference between the previous lanadmin setting of "-X 100FD" and this new one I'm seeing of "-S 1" ?

[John Payne_2]

This is the order of my instl_adm:

server="xxx.xxx.xxx.xxx"
netmask[]="255.255.255.0"
route_gateway[0]="xxx.xxx.xxx.xxx"
route_destination[0]="default"
init_hp_lanadmin_args="-X 100FD"
# end instl_adm defaults.
is_net_info_temporary=false
run_ui=false
control_from_server=true

The install forces the 100FD setting every time. man 4 instl_adm says the following:

To set the speed for a 100-Base-T interface to full duplex (the default is half duplex) you could use the setting: init _hp_lanadmin_args="-S 1"

I'm not sure why you would just have the '-S 1' flag when you can force the 100FD...

hope it helps
John