[bagtache]

Hi all,

We have several NIM clients running AIX 5.3 (5300-05-03 & 5300-04-CSP). The NIM server uses nimsh service to communicate with the clients.

With some clients, the NIM server is unable to communicate with the client when doing an mksysb backup (through the nim -o define command) when the client is configured to use nimsh but as soon as the client is reverted to shell, the communication is possible !!!! There are no network problems and the server and the client (for which the cmd fails) are able to communicate through their various network interfaces.
I did a network trace and i saw that a sometimes the NIM server tries a SYN towards the nimsh service which sent back a FIN packet: i think that this means that the nimsh service terminates the connection for some reason.

The question is : has anyone any knowlege about a bug with nimsh containted in lpp package bos.sysmgt.nim.client 5.3.0.50 & 5.3.0.40


Many thanks.

[ajf]

Try running the nim_config_services smitty fastpath and configure the communication protocol as nimsh.

[aixhpux01]

Try checking the configuration..

If a correct DNS entry exists for this client, then you should get the entry screen below, with the name filled in the NIM Machine Name and Host Name fields. If these aren’t filled in, you really need to go and get a good DNS entry created first, then come back and do this later. In a time crunch, you could add the hostname and IP to /etc/hosts on the NIM server, but this would be inconsistent with what you’re doing for the other hosts.

NIM Machine Name [unix0XX]
Machine Type [standalone]
Hardware Platform Type [chrp]
Kernel to use for Network Boot [mp]
Communication Protocol used by client [nimsh]
Primary Network Install Interface
Cable Type [N/A]
NIM Network network1
Host Name unix0XX
Network Adapter Hardware Address [0]
Network Adapter Logical Device Name []
IPL ROM Emulation Device []
CPU Id []
Machine Group []
Comments []