Cisco DCNM Troubleshooting Guide
Troubleshooting Issues with DCNM-SAN
Downloads: This chapterpdf (PDF - 401.0KB) The complete bookPDF (PDF - 1.02MB) | Feedback

Troubleshooting Issues with DCNM-SAN

Troubleshooting Issues with DCNM-SAN

This chapter describes troubleshooting issues with solutions while installing Cisco Data Center Network Manager SAN.

Troubleshooting Guidelines for Cisco DCNM-SAN

Table 1 Troubleshooting Guidelines for Cisco DCNM-SAN
Issue Recommended Solution
Files to collect for client or server locking issue. Execute the following command to gather information if you have installed JDK 1.6.x on your client machine: $JDK_HOME/bin/jstack process-id
Files to collect for client or server performance issue. Collect the OS level process CPU or Memory utilization.
New switches or devices do not show properly. Cisco DCNM cannot recognize the new Cisco switch or end device based on the unknown OUIs from WWN. To add new OUIs for Cisco switches or add a new device type, edit $Installation\dcm\fm\conf\server.properties:
# Add new OUIs for discovering switch, end device with format: 
# 0xhhhhhh vendor_name devicetypes h(host)|d(disk)|t(tape)|s(switch)|g(gateway)|m(cisco mds)
# for example: newOUIs=0x00E069 JNI h|d; 0x000ded Cisco m;\
# 0x006069 Brocade s;
newOUIs = 0x000ded Cisco m -- is to add switch new OUI
newOUIs = 0x00E069 JNI h|d  -- is to add host or disk device new OUI

After you finish the edits, restart the Cisco DCNM-SAN server.

The status of all the switches is timeout. The SNMP communication layer might be stuck and the SNMP packets cannot process smoothly.

Enter show snmp on the switch to verify that the user credential exists on the switch, and that it matches the SNMP settings.

Enter show snmp internal tcp connections to get details of the switches.

You can also reset the server SNMP through Installation\dcm\fm\conf\server.properties.

# Snmp session reset execute time at the hour of day (0-23), default value is 0
snmp.resetTime = 0
# Snmp session reset period: Never=0, Once=1, Daily=2; Weekly=3, default value is 2
snmp.resetPeriod = 2

Restart the DCNM-SAN server.

“dbinit” failed during postgres or Cisco DCNM installation.

You can install Postgresql only on Windows console mode. If you are using remote desktop, execute mstsc /console.

Changing the window service dependency. Enter the following command to add the window service dependency: C:\Users\xxxxx>sc config fmserver depend= "OracleServiceXE" [SC] ChangeServiceConfig SUCCESS

You can find the Oracle Service name from the control panel.

Initial discovery takes a long time. Ensure that DCNM-SAN has SNMP access to all switches including NPV devices and UCS.
DCNM-SAN Server is running slow with Postgres. Check the database size ($INSTALLDIR/dcm/db/data) and ensure that the database size is less than 3 GB. On Windows, right-click on the data folder and select Properties. A dialog box is displayed with the folder size. On Linux, execute du –k $INSTALLDIR/dcm/db/data. To reduce the database size, execute the following command:
.Stop FMServer.
      cd $POSTGRES_DIR/bin
     	run ./psql.exe –U db_username dcmdb (where dcmdb is the database name)
      .run this command at psql prompt.
            #vacuum full analyze verbose;
                #\q
     You should see database size is reduced. (The above might take a while)
Increase Oracle XE connection pool size. You need to execute the following command when running federation against Oracle XE to adjust the connection pool and cursor size:
C:\Documents and Settings\Administrator>sqlplus /nolog 
SQL*Plus: Release 10.2.0.1.0 - Production on Wed Jan 6 17:19:32 2010 
Copyright (c) 1982, 2005, Oracle.  All rights reserved. 
SQL> connect / as sysdba;
Connected.

SQL> alter system set processes=150 scope=spfile; 
System altered.
SQL> alter system set open_cursors=500 scope=spfile; 
System altered.
SQL> shutdown immediately;
SP2-0717: illegal SHUTDOWN option
SQL> shutdown immediate;
Database closed.
Database dismounted.
ORACLE instance shut down.
SQL> startup;
How to migrate PM historic data.

To migrate PM historic data, follow this procedure:

  1. Install Cisco DCNM-SAN on a new server.
  2. Stop the Cisco DCNM-SAN servers.
  3. Copy all rrd files from the old server ($INSTALLDIR/fm/pm/db) to the new server (($INSTALLDIR/fm/pm/db).
  4. Enter the following command: $INSTALLDIR/bin/pm.bat s
  5. Restart the Cisco DCNM-SAN server on the new server.
  6. Discover fabrics.
  7. Add fabrics into the collection.
  8. Restart fmserver on the new server.
  9. After an hour, check that the historic statistics are on the new server.
How to change the window service dependency

Enter the following command to add service dependency. Use the control panel to find your Oracle service name. After you enter the command, refresh the FMServer in the control panel and to obtain the correct dependency display.

C:\Users\xxxxx>sc config fmserver depend= "OracleServiceXE" [SC] ChangeServiceConfig SUCCESS
How to remove or uninstall Fabric Manager Server (fmserver) manually To uninstall the Fabric Manager server manually, follow this procedure:
  1. Stop the Fabric Manager server.
  2. On the command prompt, enter sc delete fmserver to remove the service.
  3. From the Add and Remove Programs, uninstall postgres.
  4. Delete the $INSTALLDIR/dcm directory.
How to remove or uninstall DCNM 5.2.x Windows server manually To uninstall the DCNM 5.2.x manually, follow this procedure:
  1. Stop the Fabric Manager server.
  2. On the command prompt, enter sc delete fmserver to remove the service.
  3. From the Add and Remove Programs, uninstall postgres.
  4. Delete $ProgramFiles/Zero G Registry/.com.zerog.registry.xml.
  5. Delete the $INSTALLDIR/dcm directory.
How to remove or uninstall DCNM 5.2.x Linux server manually To uninstall the DCNM 5.2.x manually, follow the procedure below:
  1. Stop the fmserver.
  2. Execute $INSTALLDIR/dcm/db/bin/DB to stop postgres DB server.
  3. Delete /var/.com.zerog.registry.xml.
  4. Delete the $INSTALLDIR/dcm directory.