Troubleshooting user access to the administrative command-line interface

Use the information in this topic to troubleshoot problems you might have when accessing the administrative command-line interface.

Problem

The following information describes scenarios and steps to take to access the administrative command-line interface (CLI).

Investigation

If you received access denied errors
Use the following steps to resolve the problem:
  1. Using Secure SHell, access the engine that is having failures.
  2. View the tank.passwd file to verify that the user name and password are correct:
    # cat ~/.tank.passwd
  3. Recreate the password file:
    cd ~; /usr/tank/admin/bin/tankpasswd -u ldap_username -p ldap_passwd
    where the ldap_username and ldap_password are for the user having problems.
  4. Run the sfscli>lsserver command to verify that you have access to the metadata server.
  5. Verify that the LDAP server is running and there are no configuration problems between the LDAP server and the administrative agent. Check the administrative log to determine if you are received errors about SAN File System not connecting to the LDAP server.

If you received administrative agent or CIM agent not found errors
Use the following steps to resolve the problem:
  1. Run the ps Secure SHell command to verify that the administrative agent is running:
    ps -efw | grep -i cimom.cimom
    The results should be similar to the following ones:
    root      4070  3822  0 07:26 ?        S      0:08 
    /opt/IBMJava2-131/jre/bin/exe/java -Xms128m -Xmx256m 
    com.ibm.cimom.CIMOM -RootDir
    root      4087  4070  0 07:26 ?        S      0:00 
    /opt/IBMJava2-131/jre/bin/exe/java -Xms128m -Xmx256m 
    com.ibm.cimom.CIMOM -RootDir
    root      4088  4087  0 07:26 ?        S      0:00 
    /opt/IBMJava2-131/jre/bin/exe/java -Xms128m -Xmx256m 
    com.ibm.cimom.CIMOM -RootDir
    root      4089  4087  0 07:26 ?        S      0:00 
    /opt/IBMJava2-131/jre/bin/exe/java -Xms128m -Xmx256m 
    com.ibm.cimom.CIMOM -RootDir
    root      4090  4087  0 07:26 ?        S      0:00 
    /opt/IBMJava2-131/jre/bin/exe/java -Xms128m -Xmx256m 
    com.ibm.cimom.CIMOM -RootDir
    root      4098  4087  0 07:27 ?        S      0:00 
    /opt/IBMJava2-131/jre/bin/exe/java -Xms128m -Xmx256m 
    com.ibm.cimom.CIMOM -RootDir
    ldap      4099   758  0 07:27 ?        S      0:00 
    /usr/sbin/slapd -u ldap
    root      4101  4087  0 07:27 ?        S      2:11 
    /opt/IBMJava2-131/jre/bin/exe/java -Xms128m -Xmx256m 
    com.ibm.cimom.CIMOM -RootDir
    root      4102  4087  0 07:27 ?        S      0:00 
    /opt/IBMJava2-131/jre/bin/exe/java -Xms128m -Xmx256m 
    com.ibm.cimom.CIMOM -RootDir
  2. If the administrative agent is not running, use the startCimom command to start the administrative agent. If you have problems starting the administrative agent, view the administrative log or /usr/tank/admin/log/stderr.log and attempt to resolve the problems.
  3. Verify that the console has been started:
    /opt/was/bin/serverStatus.sh metadata_server
    where metadata_server is the host name of the server you are trying to access.
    Tip: To receive additional help on using the script, run the script with no parameters.
  4. If the console is not running, run the /usr/tank/admin/bin/startConsole command to start the console. If you have problems starting the console, view the log indicated by the error message and attempt to resolve the problems.
  5. If both the administrative agent and console are running, suspect an IP networking problem.

Parent topic: Troubleshooting an administrative server

Related tasks
Accessing an engine through a secure shell

Library | Support | Terms of use | Feedback
(C) Copyright IBM Corporation 2003, 2004. All Rights Reserved.
IBM TotalStorage SAN File System v2.2