Operating System - HP-UX
1838163 Members
3556 Online
110124 Solutions
New Discussion

Re: Ignite across subnets

 
SOLVED
Go to solution
Berd
Trusted Contributor

Ignite across subnets

I have an Ignite server, ip address 10.1.2.208. I have successfully taken an ignite image of client machine 10.2.2.44. As these machines sit on different networks I am concerned that I may not be able to re-apply an amended image to the client. Will the bootsys function without a boot helper.

Regards,
Berd
6 REPLIES 6
Berd
Trusted Contributor

Re: Ignite across subnets

I think I may have found the answer to my on question !

The bootsys functions ok, because it copies the INSTALL and INSTALLFS binaries to the client. But if I had attempted to issue a boot lan install from the client, this would have failed becuase the client would fail see the server as it is on another subnet. This would require a boot helper.

Do I get points for that :-)

Berd
Berd
Trusted Contributor

Re: Ignite across subnets

I have now kicked of the network recovery. The configure disks phase has completed, as has Download Mini System. Both of these have completed without error.

The 'Loding Software' has now been running for over 5 hours and is only 10% complete. Does this sound ok or do I have an issue ???

Berd
DCE
Honored Contributor
Solution

Re: Ignite across subnets



You may have to temporarily set your card speeds to 10 HD. In testing at DR we had to to that in order to get acceptable restore times Ignite is designed to use the lowest common denominator, and in this case it seems to be optimized to the slower speeds. We cut restore time by 80% by making that change.....

Berd
Trusted Contributor

Re: Ignite across subnets

Am I reading that correctly, you down'd your NIC to 10 Half Duplex to improve performance ???
DCE
Honored Contributor

Re: Ignite across subnets



Yep - at the DR site for ignite restores - then bumped them back up after the restores completed.
DCE
Honored Contributor

Re: Ignite across subnets



I should add that I perform ignite restores within the same subnet on a regular basis at 100FD in the actual environment without any issues. The problem seems to come into play when there are mutiple networking components involved that do not negotiate well with each other......