- Gather Tech-Support Through Web Browser (DCNM 10.2.1 and Newer)
- Gather Tech-Support Through Windows (All Versions DCNM Window Installs)
- Gather Tech-Support Through Linux (All Versions DCNM Linux/OVA Installs)
- Gather Tech-Support Through Linux (OVA Only)
The Cisco Technical Assistance Center (TAC) often asks for Data Center Network Manager (DCNM) Tech-Supports when working to troubleshoot an issue involving DCNM. This document is meant to provide both a visual guide and the Command Line Interface (CLI) steps to gathering a DCNM tech-support.
Requirements
Gathering a Tech-Support Through Web User Interface (UI)
- Credentials to successfully log into DCNM Web UI with a Network Administrator role.
Gathering a Tech-Support Through Linux CLI
- Root user credentials or similar to successfully login to the Linux OS hosting DCNM.
Gathering a Tech-Support Through Microsoft Windows
- Credentials to successfully log into Windows
Components Used
Gather Tech-Support Through Web UI
- Firefox or Chrome
Gather Tech-Support Through Microsoft Windows
- Remote Desktop
Gather Tech-Support Through Linux CLI
- SSH client
Conventions
Refer to Cisco Technical Tips Conventions for more information on document conventions.
Gather Tech-Support Through Web Browser (DCNM 10.2.1 and Newer)
Starting in 10.2.1 there is now the ability to gather a full tech-support through the DCNM Web UI.
This tech-support is the same type of server tech-support gathered in the Windows and Linux/OVA installs.
- Login with an admin level user role through Chrome or Firefox.
- After successfully logging in select Administration > Logs.
- Select Generate Techsupport.
- DCNM Tech-support will download to your default downloads location configured by your browser.
- Upload the file to your case throug the Cisco.com case portal or by using the followng link:
Gather Tech-Support Through Windows (All Versions DCNM Window Installs)
Used when the DCNM Web UI is not available.
- Login to Windows OS hosting DCNM.
- Navigate to $INSTALLDIR/dcm/fm/bin/.
- Right Click techsupport.bat and select Run as administrator
- A Command Prompt window appears and runs the batch file.
- When the batch file completes, it will report the location and name of the generated tech-support.
- The location is always $INSTALLDIR/dcm/fm/logs/
- Upload the file to your case through the Cisco.com case portal or by using the following link:
Gather Tech-Support Through Linux (All Versions DCNM Linux/OVA Installs)
Used when the DCNM Web UI is not available.
- Login to the Linux OS hosting DCNM.
- Run $INSTALLDIR/dcm/fm/bin/techsupport.sh.
- In DCNM OVA installations the direct path is /usr/local/cisco/dcm/fm/bin/techsupport.sh.
- The location and name of the generated tech-support is indicated in the second to last line of the output.
# /usr/local/cisco/dcm/fm/bin/techsupport.sh Server configuration file loaded: /usr/local/cisco/dcm/fm//conf/server.properties Done setting System properties log4j:WARN No appenders could be found for logger (fms.db). log4j:WARN Please initialize the log4j system properly. log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info. Done loading from db Done sending show tech to server 0:Received % from server 1:Received dump written to /usr/local/cisco/dcm/fm/logs/fms_dump.9 from server dumpFName: 'fms_dump.9' adding /usr/local/cisco/dcm/fm/logs/fms_dump.9 Start compressing .... Done with /usr/local/cisco/dcm/fm/logs/pm.log Done with /usr/local/cisco/dcm/fm/logs/fmserver.log.7 Done with /usr/local/cisco/dcm/fm/logs/fmserver.log.2 Done with /usr/local/cisco/dcm/fm/logs/fmserver.log.3 Done with /usr/local/cisco/dcm/fm/logs/fmserver.log.9 Done with /usr/local/cisco/dcm/fm/logs/fmserver.log Done with /usr/local/cisco/dcm/fm/logs/fmserver.log.4 Done with /usr/local/cisco/dcm/fm/logs/fmserver.log.5 Done with /usr/local/cisco/dcm/fm/logs/fmserver.log.1 Done with /usr/local/cisco/dcm/fm/logs/fmserver.log.10 Done with /usr/local/cisco/dcm/fm/logs/fmserver.log.8 Done with /usr/local/cisco/dcm/fm/logs/fmserver.log.6 Done with /usr/local/cisco/dcm/fm/logs/fm_web.log Done with /usr/local/cisco/dcm/fm/logs/fms_snmp.log Done with /usr/local/cisco/dcm/fm/logs/fms_snmp_trap.log Done with /usr/local/cisco/dcm/fm/logs/fm_webusract.log Done with /usr/local/cisco/dcm/fm/logs/fms_ws.log Done with /usr/local/cisco/dcm/fm/logs/sme_accounting_log.2017-08-23-09-17-41.log Done with /usr/local/cisco/dcm/fm/logs/smeAccounting.log Done with /usr/local/cisco/dcm/fm/logs/sme_accounting_log.2017-07-23-12-00-00.log Done with /usr/local/cisco/dcm/fm/logs/sme_accounting_log.2017-10-22-12-00-00.log Done with /usr/local/cisco/dcm/fm/logs/sme_accounting_log.2017-06-18-12-00-00.log Done with /usr/local/cisco/dcm/fm/logs/sme.log Done with /usr/local/cisco/dcm/fm/logs/sme_accounting_log.2017-07-02-12-00-00.log Done with /usr/local/cisco/dcm/fm/logs/sme_accounting_log.2017-10-29-12-00-00.log Done with /usr/local/cisco/dcm/fm/logs/sme_dkr.log Done with /usr/local/cisco/dcm/fm/logs/sme_accounting_log.2017-07-09-12-00-00.log Done with /usr/local/cisco/dcm/fm/logs/sme_accounting_log.2017-08-27-12-00-00.log Done with /usr/local/cisco/dcm/fm/logs/sme_accounting_log.2017-06-25-12-00-00.log Done with /usr/local/cisco/dcm/fm/logs/sme_accounting_log.2017-07-16-12-00-00.log Done with /usr/local/cisco/dcm/fm/logs/sme_accounting_log.2017-11-05-12-00-00.log Done with /usr/local/cisco/dcm/fm/logs/sme_accounting_log.2017-10-17-07-46-48.log Done with /usr/local/cisco/dcm/fm/logs/sme_accounting_log.2017-06-12-11-12-22.log Done with /usr/local/cisco/dcm/fm/logs/fm_webreport.log Done with /usr/local/cisco/dcm/fm/logs/fms_event_manager.log Done with /usr/local/cisco/dcm/fm/logs/fm_zoneserver.log Done with /usr/local/cisco/dcm/fm/logs/jboss7.log.1 Done with /usr/local/cisco/dcm/fm/logs/jboss7.log Done with /usr/local/cisco/dcm/fm/logs/jboss7.log.2 Done with /usr/local/cisco/dcm/fm/logs/epl.log Done with /usr/local/cisco/dcm/fm/conf/server.properties Done with /usr/local/cisco/dcm/fm/logs/fms_dump.9 Done with /root/dcnm_installer.log Done with /usr/local/cisco/dcm/fm/../jboss-as-7.2.0.Final/standalone/log/sanservice.log Done with /usr/local/cisco/dcm/fm/../smis/server/jserver/logs/jserverlog-6.trace Done with /usr/local/cisco/dcm/fm/../smis/server/jserver/logs/jserverlog-2.trace Done with /usr/local/cisco/dcm/fm/../smis/server/jserver/logs/jserverlog-3.trace Done with /usr/local/cisco/dcm/fm/../smis/server/jserver/logs/jserver.log Done with /usr/local/cisco/dcm/fm/../smis/server/jserver/logs/jserverlog-0.trace Done with /usr/local/cisco/dcm/fm/../smis/server/jserver/logs/jserverlog-4.trace Done with /usr/local/cisco/dcm/fm/../smis/server/jserver/logs/jserverlog-1.trace Done with /usr/local/cisco/dcm/fm/../smis/server/jserver/logs/jserverlog-5.trace Done with /usr/local/cisco/dcm/fm/../smis/server/jserver/logs/jserverlog-7.trace /usr/local/cisco/dcm/fm/logs/techsupport2017-11-08-12-11-35.zip is generated. Press Enter to exit
- Gather the logs from $INSTALLDIR/dcm/fm/logs/.
- Upload the file to your case through the Cisco.com case portal or by using the following link:
Gather Tech-Support Through Linux (OVA Only)
On some occasions the TAC will ask for a tech-support that encompases more services that are available in DCNM OVA installs.
- Execute # appmgr tech_support
[root@DCNM ~]# appmgr tech_support /usr/local/cisco/dcm/smis/client/conf/configuration.properties /usr/local/cisco/dcm/smis/client/conf/DCNMConnect.xml /usr/local/cisco/dcm/smis/client/conf/filter.properties /usr/local/cisco/dcm/smis/server/jserver/schema/brand/rebrand.xml /usr/local/cisco/dcm/smis/server/jserver/schema/brand/brand.properties /usr/local/cisco/dcm/smis/server/jserver/bin/hs_err_pid19478.log /usr/local/cisco/dcm/smis/server/jserver/bin/jservertrace.properties /usr/local/cisco/dcm/smis/server/jserver/bin/cimom.properties /usr/local/cisco/dcm/smis/server/jserver/bin/hs_err_pid19470.log /usr/local/cisco/dcm/smis/server/jserver/bin/hs_err_pid19474.log /usr/local/cisco/dcm/smis/server/jserver/bin/hs_err_pid20056.log /usr/local/cisco/dcm/smis/server/jserver/bin/hs_err_pid19486.log /usr/local/cisco/dcm/smis/server/jserver/bin/hs_err_pid20062.log /usr/local/cisco/dcm/smis/server/jserver/bin/hs_err_pid19482.log /usr/local/cisco/dcm/smis/server/jserver/bin/jserver.properties /usr/local/cisco/dcm/smis/server/jserver/bin/hs_err_pid20048.log /usr/local/cisco/dcm/smis/server/jserver/bin/hs_err_pid20044.log /usr/local/cisco/dcm/smis/server/jserver/bin/hs_err_pid20052.log /usr/local/cisco/dcm/smis/server/jserver/logs/jserver.log /usr/local/cisco/dcm/smis/server/jserver/logr/provider.properties /usr/local/cisco/dcm/java/jre1.8/lib/images/cursors/cursors.properties /usr/local/cisco/dcm/java/jre1.8/lib/javafx.properties /usr/local/cisco/dcm/java/jre1.8/lib/flavormap.properties /usr/local/cisco/dcm/java/jre1.8/lib/psfontj2d.properties /usr/local/cisco/dcm/java/jre1.8/lib/desktop/mime/packages/x-java-archive.xml /usr/local/cisco/dcm/java/jre1.8/lib/desktop/mime/packages/x-java-jnlp-file.xml /usr/local/cisco/dcm/java/jre1.8/lib/calendars.properties /usr/local/cisco/dcm/java/jre1.8/lib/hijrah-config-umalqura.properties /usr/local/cisco/dcm/java/jre1.8/lib/management/management.properties /usr/local/cisco/dcm/java/jre1.8/lib/sound.properties /usr/local/cisco/dcm/java/jre1.8/lib/net.properties ... /opt/Python-2.7.3/build/temp.linux-x86_64-2.7/libffi/config.log /opt/Python-2.7.3/Doc/tools/sphinxext/opensearch.xml /opt/Python-2.7.3/Lib/test/xmltestdata/simple-ns.xml /opt/Python-2.7.3/Lib/test/xmltestdata/simple.xml /opt/Python-2.7.3/Lib/test/xmltestdata/test.xml /opt/Python-2.7.3/config.log ===================================================== Logs available at logs_11_08_2017__13_29_28.tar.gz =====================================================
- Gather the logs from the location executed.
- Upload the file to your case through the Cisco.com case portal or by using the following link:
