:>
:>
:> Booting an F40 AIX 4.3.2, the following occurs:
:> 1513-059 rpc.mountd sybsystem has been started PID...
:> 1513-059 rpc.statd sybsystem has been started PID
:> 1513-059 rpc.lockd sybsystem has been started PID
:> rpc.statd: 1813-119 unable to register
:> (SM_PROG, SM_VERS, udp)
:> ypbind: 1831-030 cannot register tcp service
:>
:> the last 2 messages reappear randomly every few minutes.
:> i cannot login to the console or do anything else on the console.
:> i can ping the machine.
:> i cannot telnet or rlogin to the system.
:>
:> please help
:> sol
:>
:>
:> Sent via Deja.com http://www.deja.com/
:> Before you buy.
: Hello Sol,
: Not much help I'm afraid. We have recently taken a makesysb from a client
: system and installed it on an identical machine. Both are 43P's running
: AIX 432 and have exactly the same problem. Also in our case NFS will not
: mount and filesystems from the server. I can't help thinking that this may
: be NIS related. I will let you know if I come up with anything. (Unless
: you have solved it already?)
: Best Regards,
: Andy
: --
: Posted via CNET Help.com
: http://www.help.com/
When an AIX 4.3.2 system first reboots after being cloned via a mksysb tape,
the tcp/ip local loop back interface is in a "down" state. You can verify
this by trying (unsuccessfully) to ping localhost or with "lsattr -El lo0".
Use "chdev -l lo0 -a state=up" to correct this situation. You could
probably restart all the processes manually that are affected by a "down"
lo0, but I've always found it easier to just reboot. You can complete the
reconfiguration of tcp/ip, if you need to, before that reboot. You only
have to do the chdev once; you do NOT have to add it to any start-up scripts.
If you have a graphics card in your system, be sure to avoid logging in
to CDE until you fix lo0. Select "Command Line Login" under the "Options"
button on the front CDE login panel, and log in to the lft "green screen"
console.
I don't know whether lo0 is "down" after a mksysb restore due to purposeful
design or due to a bug, but I find it to be annoying. When I searched the
problem database, I could not find any APAR that matched this situation.
I don't use NIM, so I can't tell you whether restoring from a NIM mksysb
image leaves lo0 "down".
This situation seemed to be new in AIX 4.3.2. I have not had the opportunity
to test whether 4.3.3 changes this behavior.