Post VPAR recovery reboots with modifiy /etc/hosts file ??

[Jane Bell]

I had to recovery a VPAR from a recent Ignite archive (image taken by make_net_recovery) which seems to have completed successfully. I did have to go to a shell , and exit 2 for the recovery to complete.... When i reboot the VPAR /etc/hosts is modified, the Backup and User interfaces ( Lan 900 and lan 901 ) are given the same name... The actual intefaces have been assigned the correct addresses...

If i modify /etc/hosts and reboot...they get set back to the same... Trawled the server and logs looking for a script that could be doing this.. ( i.e. inittab, /sbin/init.d /etc/rc.config.d/* cron ) ...

Vpar is using 11.31...

[Steven E. Protter]

Shalom,

Depending on how the Ignite backup was made, /etc/hosts may have been excluded from the image. This can be changed with a golden image when you write it.

If this is the only problem you are having, it is relatively minor, and you can copy a /etc/hosts file in from another system and check your Ignite backup script that this file is included.

It woule appear from the apa configuration that the image being restored was not taken from this vpar, which would explain the differences.

You need to decide if you would rather do the restore again, or correct the problems manually and take another image of this system for future use.

SEP

[Jane Bell]

Thanks , but not my case ...some more detail...

Vpar was recovered from an image collected 2 days ago when I built the VPAR... Issue is doesn't matter what i put in /etc/hosts it's getting over written each time I reboot.... I only came to notice it when Service Guard would not start following a reboot and i looked at /etc/hosts...

at the efi level when i reboot does do anything causing this?

[likid0]

Take a look if you have DHCP enebled in your network configuration.

You can take a look in the /etc/rc.config.d/netconf file for:

DHCP_ENABLE[0]=1


1 is enabled ...