Use the following suggestions if you encounter problems while connecting to a client, listing domain members, or defining a working collective. A Failed prompt in the Command Status field of the output screen indicates that one or more systems reported a failure.
If the front end of DSMIT/crex/srex abnormally terminates, the following may not have been cleared:
Concurrent DSMIT/crex/srex sessions may have similar side effects and they must be resolved. The following information is intended as a guide for cleaning up processes that abnormally terminated:
Many of the problems associated with Distributed System Management Interface Tool (DSMIT) arise when you cannot connect to one or all of the clients. Consult the following list if you cannot connect to the DSMIT clients:
ping ClientNameIf the client responds, then the network is active. If the client does not respond, follow the problem determination steps defined by TCP/IP.
rsh HostName ps -ef | grep inetd
If the inetd daemon does not exist or the rsh command fails, start it using the following appropriate method:
For AIX systems, check to see if the inetd daemon is active by locally entering lssrc -s inetd . If the inetd daemon is not active, start it by entering startsrc -s inetd . If the inetd daemon is active, refresh it using the following methods:
/usr/bin/refresh -s inetd
rsh HostName /usr/bin/refresh -s inetd
ps -aux | grep inetd kill -1 Process_id_of_inetd
rsh Hostname ps -aux | grep inetd rsh Hostname kill -1 Process_id_of_inetd
/etc/inetd -c
rsh Hostname /etc/inetd -c
netstat -Aan | grep 6125 netstat -Aan | grep 6126Output should look similar to this:
<HexNumber> udp 0 0 *.6125 *.* <HexNumber> tcp 0 0 *.6126 *.* LISTEN
rex dgram udp wait root /usr/dsmit/bin/crexd crexd -t30 rex stream tcp nowait root /usr/dsmit/bin/srexd srexd -iIf these lines are not present in the file, add them to the file and refresh the inetd daemon.
rex 6126/tcp #srexd port rex 6125/udp #crexd portIf these lines are not present in the file, add them to the file and refresh the inetd daemon.
ping Server HostNameIf the system returns the server's TCP/IP address, the network is working correctly. If it does not, add the server host name to the /etc/hosts.equiv or /etc/hosts file. If the system is using a name server, the problem could be the result of name server failure. See "TCP/IP Name Resolution" in AIX Version 4.3 System Management Guide: Communications and Networks for more information on name servers.
If a message such as "establishing secure session failed" is displayed, refer to the following steps:
Note: If the machine you are trying to establish a session with does not appear in the list of managed machines, you should add it. See "Modifying DSMIT Security Configuration" for more information.
Note: See "Modifying DSMIT Security Configuration" for more information.
If the output from the lsdsmitd command does not include all of the hosts that were added to a domain, check the /usr/share/DSMIT/hosts file for spaces between client names. Remove all spaces in the definition of a domain.
If you cannot define a working collective because you get the message:
All the hosts should have one and the same Operating System
Double entries can occur if you completed step 4 in the "Database" section even though DSMIT was installed on the HostWithNewLevel . To correct this situation, remove the NewLevelDirectory and complete all the steps except step 4 in the "Database" section.
If you get messages such as the following:
Cannot acquire exclusive lock
Cannot connect to the file server
Enter the dsmit-unlock and dsmit-dec commands on the file server.
If you cannot run the dsmit-addkey command because you get the message:
dsmit-addkey: Problems with /tmp/new-v5srvtab -- exiting.
If you get the Cannot access/open file /tmp.installp_cmd message when trying to install a software package, the version of installp on the remote machine is different than the SMIT database version on the local machine. To fix this, install the correct version of the database on the local machine. Refer to "Databases".
You may get the following message cause you cannot select the next:
There is a conflict in selecting the next screen - Make other selections in previous screens and/or exclude some hosts from the collective
The next menu to display is not exactly the same on all machines in the working collective. This indicates one of the following:
For example, for the menu Change/Show Characteristics of a Tape Drive, the working collective is defined to be M1 and M2 . On M1 , a 4.0 GB 4mm tape drive exists and on M2 , a 2.3 GB 8mm tape drive exists. When DSMIT attempts to display a menu, you will get the above error message. This is because of the different dialog type options. On the 4.0 GB tape drive, it has the extra option Use data COMPRESSION and on the 8.0 GB, it has the Use EXTENDED file marks option. DSMIT cannot display different dialogs at once. Each dialog must be the same to work.
To correct this problem, you must work with each group of machines that have the same dialogs by temporarily excluding the machines that are different and working with them later.
If you cannot get Solaris 2.3 and Solaris 2.4 machines into the same working collective, check /usr/share/DSMIT/hosts to be sure all machines are listed as Solaris and not Solaris_2.3.
Distributed System Management Interface Tool (DSMIT) Overview.