Appendix B. Troubleshooting

Table Of Contents

Troubleshooting

Killing Processes during Uninstallation and Start-up

Oracle Database Connectivity

CNS Access Registrar

CNS Network Registrar

Troubleshooting

This appendix provides information that is designed to help you if you encounter Cisco BACBA (BACBA) installation related problems.

This appendix includes the following sections:

• "Killing Processes during Uninstallation and Start-up" section

• "Oracle Database Connectivity" section

• "CNS Access Registrar" section

• "CNS Network Registrar" section.

Killing Processes during Uninstallation and Start-up

When pressing Start during the uninstallation process (see "Uninstalling the BACBA Software" section on page 5-7), you may get an error message saying that some applications are still running.

In this case, follow these steps:

Step 1 At the command prompt, enter:

% ps -ef | grep <user>

where <user> is the user who installed the software.

Step 2 Search for the process the uninstallation script is complaining about.

Step 3 Kill the process manually.

This type of error message might also be generated by the bacStartUp script. In this case, follow the same procedure as above.

Oracle Database Connectivity

This section describes the tasks you should perform if you encounter problems while communicating with the Oracle database.

Step 1 Check to ensure that the listener is running:

% ps -ef | grep tnslsnr

Step 2 Ensure you connect to the Oracle database through sqlplus and that the tables have been created:

prompt> $ORA_HOME/sqlplus <username>/<passwd>@<sid>
SQL> select table_name from user_tables;

where <username> is the default oracle BACBA username, <passwd> is the default oracle BACBA password, and <sid> is the default BACBA Oracle SID.

CNS Access Registrar

This section describes the tasks you should perform if you encounter problems with the Cisco CNS Access Registrar (CNS AR) product.

Step 1 Telnet to the Cisco CNS Access Registrar server.

Step 2 Check the status of the Cisco CNS Access Registrar server:

/opt/CSCOar
arstatus

The status you receive should contain information similar to:

RADIUS server running (pid: <xxxx>)
MCD server running (pid: <xxxx>)
Server Agent running (pid: <xxxx>)
MCD lock manager running (pid: <xxxx>)

where <xxxx> is the process ID number.

Note CNS AR requires a symbolic link, cisco-ar---> /opt/CSCOar, (directory where your CNS AR is installed). Check to see if this symbolic link is present. If this link does not exist, then you must manually add it. Use, ln -s /opt/CSCOar cisco-ar.

Step 3 If BAC and CNS AR are installed on the same machine, the symbolic link may link to BAC's SAM server. Link to either CNS AR's home directory or BAC's SAM directory.
For example, use cisco-ar----> /opt/CSCObacss/sam.

CNS Network Registrar

This section describes the tasks you should perform if you encounter problems with the Cisco CNS Network Registrar (CNS NR) product.

Note The $BAC_HOME/resourceMgr/common/ipservice.cfg and $BAC_HOME/resourceMgr/common/resourceMgr.cfg files contain important Cisco CNS Network Registrar related configuration information.

Step 1 Ensure the DNS_HOST value specified in the $BAC_HOME/resourceMgr/common/ipservice.cfg file can be resolved using /etc/resolv.conf.

Step 2 Connect to Cisco CNS Network Registrar:

% $BAC_HOME/resourceMgr/bin/nrcmd
Step 3 Check the dhcp and dns log files in the /var/nwreg2/logs directory.

Step 4 Use the nslookup command to ping for DNS troubleshooting.

Step 5 Use the nrcmd command or the Cisco Network Registrar CLI Reference to troubleshoot DHCP problems.