Lose IP after TL Update

UNIX AIX
1

Hi,

sometimes when do TL Updates on AIX machines i loose the IP's. For example I lately updated two machines from 6.1 TL4 and 6.1 TL1 to TL8SP2, they both lost their ip's, when I connect to the console and do smit tcpip all information is still there, i just have to confirm with return and everything is fine..

This does not happen on all systems where I do the update, only on some. I have no clue when it happens. Does anybody know this behaviour and knows the why and when this happens?

Regards, FF

2

Hi,

we had a similar problem with our VIO-Server (oslevel 6100-07-03).
Sometimes after a reboot, the server starts without an ip configuration. But within smitty all information was present.

In our case, the supports told us that the etherchannel (LACP) was not ready when the server try to configure the ip adress.

0821-007 cfgif: ifconfig command failed. The status of "enX" Interface in the current running system is uncertain.

We got a efix for that problem.

May this help you.

Regards

3

Hello there,
Check you ssh version compatibility with your TL version , I have my two cents on this.

Upgrade your SSH version and it should eliminate your problem, coz if you jump to a much higher level you need to upgrade ssh too.

4

Hi,
I updated to the TL8SP2 with smit update_all, so ssh should have been updated in the same step as the rest. I am on ssh level 6.0.0.6100 now.
I guess that can't be the problem...

Regards, Marc

5

Can you send me the output of

# lslpp -L | grep ssh

and

# oslevel -rl 6100-08
6

Hi, here is the output:

#lslpp -L|grep ssh
openssh.base.client     6.0.0.6100    C     F    Open Secure Shell Commands
  openssh.base.server     6.0.0.6100    C     F    Open Secure Shell Server
  openssh.license         5.4.0.6101    C     F    Open Secure Shell License
  openssh.man.en_US       6.0.0.6100    C     F    Open Secure Shell
  openssh.msg.CA_ES       6.0.0.6100    C     F    Open Secure Shell Messages -
  openssh.msg.CS_CZ       6.0.0.6100    C     F    Open Secure Shell Messages -
  openssh.msg.DE_DE       6.0.0.6100    C     F    Open Secure Shell Messages -
  openssh.msg.EN_US       6.0.0.6100    C     F    Open Secure Shell Messages -
  openssh.msg.ES_ES       6.0.0.6100    C     F    Open Secure Shell Messages -
  openssh.msg.FR_FR       6.0.0.6100    C     F    Open Secure Shell Messages -
  openssh.msg.HU_HU       6.0.0.6100    C     F    Open Secure Shell Messages -
  openssh.msg.IT_IT       6.0.0.6100    C     F    Open Secure Shell Messages -
  openssh.msg.JA_JP       6.0.0.6100    C     F    Open Secure Shell Messages -
  openssh.msg.Ja_JP       6.0.0.6100    C     F    Open Secure Shell Messages -
  openssh.msg.KO_KR       6.0.0.6100    C     F    Open Secure Shell Messages -
  openssh.msg.PL_PL       6.0.0.6100    C     F    Open Secure Shell Messages -
  openssh.msg.PT_BR       6.0.0.6100    C     F    Open Secure Shell Messages -
  openssh.msg.RU_RU       6.0.0.6100    C     F    Open Secure Shell Messages -
  openssh.msg.SK_SK       6.0.0.6100    C     F    Open Secure Shell Messages -
  openssh.msg.ZH_CN       6.0.0.6100    C     F    Open Secure Shell Messages -
  openssh.msg.ZH_TW       6.0.0.6100    C     F    Open Secure Shell Messages -
  openssh.msg.Zh_CN       6.0.0.6100    C     F    Open Secure Shell Messages -
  openssh.msg.Zh_TW       6.0.0.6100    C     F    Open Secure Shell Messages -
  openssh.msg.ca_ES       6.0.0.6100    C     F    Open Secure Shell Messages -
  openssh.msg.cs_CZ       6.0.0.6100    C     F    Open Secure Shell Messages -
  openssh.msg.de_DE       6.0.0.6100    C     F    Open Secure Shell Messages -
  openssh.msg.en_US       6.0.0.6100    C     F    Open Secure Shell Messages -
  openssh.msg.es_ES       6.0.0.6100    C     F    Open Secure Shell Messages -
  openssh.msg.fr_FR       6.0.0.6100    C     F    Open Secure Shell Messages -
  openssh.msg.hu_HU       6.0.0.6100    C     F    Open Secure Shell Messages -
  openssh.msg.it_IT       6.0.0.6100    C     F    Open Secure Shell Messages -
  openssh.msg.ja_JP       6.0.0.6100    C     F    Open Secure Shell Messages -
  openssh.msg.ko_KR       6.0.0.6100    C     F    Open Secure Shell Messages -
  openssh.msg.pl_PL       6.0.0.6100    C     F    Open Secure Shell Messages -
  openssh.msg.pt_BR       6.0.0.6100    C     F    Open Secure Shell Messages -
  openssh.msg.ru_RU       6.0.0.6100    C     F    Open Secure Shell Messages -
  openssh.msg.sk_SK       6.0.0.6100    C     F    Open Secure Shell Messages -
  openssh.msg.zh_CN       6.0.0.6100    C     F    Open Secure Shell Messages -
  openssh.msg.zh_TW       6.0.0.6100    C     F    Open Secure Shell Messages -
You have mail in /usr/spool/mail/root

#oslevel -rl 6100-08

doesn't give an output.

7

Ok,
Why is openssh.license at a lower level?

openssh.license 5.4.0.6101 C F Open Secure Shell License

Update the license file to 6.0.0.6100, and then let me know if the problem still exist.

The no o/p is good thing.

On the other hand run #lppchk -v

Also, you don't need to have all that international language (msg) crap with you, delete all other msg files except "openssh.msg.en_US"
If you are not in US but other country, then keep the msg of their regional language.

8

I do not believe the activation of the IP stack should be dependent on any application. That said, I did have issues myself, and it came down to things I had done "in innocence", i.e. user error in changes to /etc/inittab and/or /etc/rc.d/* scripts.

In my case I did always get an IP address, just lacked some daemons such as ssh.

Besides rebooting several times to try and observe what was going wrong I also used the output of the command alog -o -t console and alog -o -t boot to read messages from programs to find that missing depenadancy.

Unfortunately, for you, I do not remember the specifics - this was too long ago. But I do recommend checking your alog outputs for hints about what is going on, error messages, etc..

Hint:
mkdev -l en0; mkdev -l inet0 will do what startup should have done (assuming single interface en0. If more interfaces do them all, then inet0.