is it possible to use lanadmin during ignite

[Todd Bowden]

To all,

Im wondering if it is possible to use the lanadmin command to force our 10/100BT lan card to go 100FD fixed during an ignite restore? We are doing an ignite restore from an ignite server that has a 10/100 lancard and are attempting to do an ignite restore over the network but found it was very slow. My thought is most likely the card on the target system is probably at 100 Half Auto. I say this because when I do a cold install and look to see what the card is configured for its 100 Half Auto.

Thanks for any assistance you can provide.

Todd

[Pete Randall]

Todd,

I believe that Ignite only accepts the 10MB setting.


Pete

[Steven E. Protter]

In general you do it right before the restore starts rolling.

Landadmin style commands are run with the instl_adm command.

The lanadmin command me accepted, but it may stop the transfer mid-transfer.

If you are willing to risk starting over, it is probably worth a try.

SEP

[Todd Bowden]

I tried to drop into a shell, but I had no access to the lanadmin command. It looks like I have to have it as a pre-command before everything starts. Im still trying to figure it out.

[Todd Bowden]

To all,

I guess it is possible. Here is an exerpt from the manual: (When in doubt RTFM) ;)

The default behavior of the kernel at boot up is to auto-negotiate the speed and duplex settings of all LAN interfaces that support this feature. This default behavior is later modified in HP-UX by startup scripts that can set any speed and duplex rather than allow the LAN interface to auto-negotiate these settings.

When you use an installation kernel with Ignite-UX to install or recover a system, there are no startup scripts. If a Fast or Gigabit Ethernet LAN interface fails to auto-negotiate, defaults to 100 Half-Duplex regardless of the speed and duplex settings at the other end. Mismatched speed and duplex settings can cause serious performance and reliability issues when using Ignite-UX.

You can adjust the speed and duplex settings when using Ignite-UX with the _hp_lanadmin_args variable. The LAN interface Ignite-UX uses must be brought up before the Ignite-UX server can be contacted so this keyword serves no purpose if it is located in the normal configuration files used by Ignite-UX. In view of this, _hp_lanadmin_args must be configured in the installation file system on the server that it boots from. If the client boots using a boot helper, _hp_lanadmin_args must be configured on the boot helper system not the Ignite-UX server.




Note: In a default setting, modern switches and hubs will autonegotiate the speed and duplex settings with your PA-RISC or Itanium-based system. However, in some cases you may want to set the speed and duplex settings to certain values for your environment, for example, the switch may always fail to autonegotiate with your system. If you do not use autonegotiation on the switch or hub that your system is connected to, you must provide the correct speed and duplex settings for Ignite-UX using _hp_lanadmin_args. Mismatched speed and duplex settings may cause significant performance issues or failures during recovery.






Almost all Fast and Gigabit Ethernet interfaces support setting the speed and duplex using the _hp_lanadmin_args variable for using the -X option. Some old Fast Ethernet interfaces may not support full-duplex so please consult the product documentation for any network interfaces you encounter problems with to confirm the speed and duplex settings that each supports.

You can still take advantage of the other options available using the lanadmin command. For more information, refer to the examples in instl_adm(4) regarding setting the MTU (-M) and Duplex (-S) options of _hp_lanadmin_args.




Important: Due to a problem in Ignite-UX in versions prior to B.5.2.x, some parts of the recovery may run with the wrong speed and/or duplex on the LAN interface when the system first reboots and until the final reboot. If this proves to be a problem in your environment, you should ensure that you have installed Ignite-UX version B.5.2.x or later.

[Todd Bowden]

See my comments above.