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

Troubleshooting Issues with Cisco DCNM Discovery

Troubleshooting Issues with Cisco DCNM Discovery

This chapter contains the following sections:

Default Logging Level Required for Cisco DCNM

This section describes the various logging levels required by the Cisco Nexus Series switches.


Note


To override the default Cisco DCNM behavior, see the custom logging-level configuration in Cisco DCNM.


Table 1 Default Logging Levels for Cisco Nexus 7000 Series Switches
Feature Supported in Cisco DCNM Default Log Level Cisoc DCNM Required Log Level
Ethpm Yes 5 5
Interface-VLAN Yes 2 5
Udld Yes 5 5
Port-channel Yes 5 6
Monitor Yes 3 6
CDP Yes 2 6
VpC Yes 2 6
STP Yes 3 6
Port Security Yes 2 5
DHCP Yes 2 6
GLDB Yes 3 6
HSRP Yes 3 6
AAA Yes 3 5
RADIUS Yes 3 5
Track Yes 3 6
TACACS+ Yes 3 5
Platform Yes 5 5
Sysmgr Yes 3 3
Module Yes 5 5
FEX No - -
DOT1X Yes 2 5
VDCmgr Yes 6 6
LstSVC No - -
Link Status Enable Yes T T
Link Status Default Yes F T
VIM No - -
VMS No - -
LLDP Yes 2 5
Table 2 Default Logging Levels for Cisco Nexus 5000 Series Switches
Feature Supported in Cisco DCNM Default Log Level DCNM Required Log Level
Ethpm Yes 5 5
Interface-VLAN Yes 2 5
Udld Yes 5 5
Port-channel Yes 5 6
Monitor Yes 3 6
CDP Yes 2 6
VpC Yes 2 6
STP Yes 3 6
Port Security No - -
DHCP No - -
GLDB No - -
HSRP No - -
AAA Yes 3 5
RADIUS Yes 3 5
Track No - -
TACACS+ Yes 3 5
Platform Yes 5 5
Sysmgr Yes 3 3
Module No - -
FEX Yes 2 5
DOT1X No - -
VDCmgr No - -
LstSVC No - -
Link Status Enable Yes T T
Link Status Default Yes F T
VIM No - -
VMS No - -
LLDP No - -
Table 3 Default Logging Levels for Cisco Nexus 3000 Series Switches
Feature Supported in Cisco DCNM Default Log Level DCNM Required Log Level
Ethpm Yes 5 5
Interface-VLAN Yes 2 5
Udld Yes 5 5
Port-channel Yes 5 6
Monitor Yes 3 6
CDP Yes 2 6
VpC No - -
STP Yes 3 6
Port Security No - -
DHCP Yes 2 6
GLDB No - -
HSRP No - -
AAA Yes 3 5
RADIUS Yes 3 5
Track No - -
TACACS+ Yes 3 5
Platform Yes 5 5
Sysmgr Yes 3 3
Module No - -
FEX No - -
DOT1X No - -
VDCmgr No - -
LstSVC No - -
Link Status Enable No - -
Link Status Default No - -
VIM No - -
VMS No - -
LLDP Yes 2 5
L2ISIS No - -
FP Topology No - -
FP Resource No - -
Nohms Yes 1 2
Port Profile No - -
MSP No - -
Switchprofile Yes 2 6
FLOGI No - -
Table 4 Default Logging Levels for Cisco Nexus 4000 Series Switches
Feature Supported in Cisco DCNM Default Log Level Cisco DCNM Required Log Level
Ethpm Yes 5 5
Interface-VLAN Yes 2 5
Udld Yes 5 5
Port channel Yes 5 6
Monitor Yes 3 6
CDP Yes 2 6
VpC No - -
STP Yes 3 6
Port Security No - -
DHCP No - -
GLDB No - -
HSRP No - -
AAA Yes 3 5
RADIUS Yes 3 5
Track No - -
TACACS+ Yes 3 5
Platform No - -
Sysmgr Yes 3 3
Module No - -
FEX No - -
DOT1X No - -
VDCmgr Yes 6 6
LstSVC Yes 2 4
Link Status Enable Yes T T
Link Status Default Yes F T
VIM No - -
VMS No - -
LLDP No - -
Table 5 Default Logging Levels for Cisco Nexus 1000 Series Switches
Feature Supported in Cisco DCNM Default Log Level Cisco DCNM Required Log Level
Ethpm Yes 5 5
Interface-VLAN No - -
Udld No - -
Port-channel Yes 5 6
Monitor Yes 3 6
CDP Yes 2 6
VpC No - -
STP No - -
Port Security No - -
DHCP No - -
GLDB No - -
HSRP No - -
AAA Yes 3 5
RADIUS Yes 3 5
Track No - -
TACACS+ Yes 3 5
Platform Yes 5 5
Sysmgr Yes 3 3
Module Yes 5 5
FEX No - -
DOT1X No - -
VDCmgr No - -
LstSVC No - -
Link Status Enable No T T
Link Status Default Yes F T
VIM Yes 5 5
VMS Yes 5 5
LLDP No - -

Default Keywords

Table 6 Default Keywords for Platform Types
Keyword Platform
dc3 Nexus 7000
n5k Nexus 5000, Nexus 5010, and Nexus 5020
n5500 Nexus 5500, Nexus 5548, and Nexus 5596
n4ki Nexus 4000 IBM Blade Server
n1kv Nexus 1000
n1010 Nexus 1010
m9500 MDS 9500
m9200 MDS 9200
m9100 MDS 9100
Table 7 Default Keywords for Feature Names
Keyword Feature
module Module
interface-vlan Interface VLAN
tacacs TACACS+
monitor Monitor
stp Spanning-tree
eth_port_channel Port channel
udld UDLD
ethpm ETHPM
sysmgr System Manager
platform Platform
cdp CDP
radius Radius
aaa AAA
dhcp DHCP
vdc_mgr VDC
gldp GLDP
port-security Port Security
dot1x DOT1x
track Object tracing
vpc VPC
hsrp_engine HSRP
tunnel Tunnel
fprsrc Fabricpath resource
fptopo Fabricpath topology
l2isis Fabricpath ISIS
fex Fabric Extender
nohms NOHMS
lldp LLDP
flogi FLOGI
fip-snooping FIP-Snooping
lstsvc LSTSVC
port-profile Port profile
vim VIM
vms VMS
msp MSP

DCNM Discovery Required Commands

Command Nexus 7000 Nexus 5000 Nexus 4000 Nexus 3000 Nexus 1000v Nexus 1010 Catalyst 6500 FWSM UCS
show clock Yes Yes Yes Yes Yes Yes Yes Yes Yes
show version Yes Yes Yes Yes Yes Yes Yes Yes Yes
show inventory Yes Yes Yes Yes Yes Yes Yes   Yes
show cdp neighbors detail   Yes Yes Yes Yes   Yes   Yes
show lldp neighbors detail Yes Yes              
show spanning-tree internal info global | i mac   Yes Yes            
show feature-set | include fabricpath   Yes              
show context                  
show running-config                  
show logging level platform Yes       Yes Yes      
show logging level module Yes       Yes Yes      
show logging level sysmgr Yes   Yes   Yes Yes      
logging level platform 5 Yes Yes     Yes Yes      
logging level module 5 Yes       Yes Yes      
logging level sysmgr 3 Yes Yes Yes   Yes Yes      
show log level | egrep 'platform|sysmgr'                  
sh run | include admin-vdc Yes                
show virtual-service-blade           Yes      
sh run | include combined-hostname Yes                
show logging logfile last-index Yes                
show accounting log last-index Yes                
show wwn switch   Yes              
show npv flogi-table   Yes              
show topology   Yes              
show fcs database   Yes              
show fcns database local detail   Yes              
sh feature | include \fcoe\   Yes              
show interface portname | grep ignore-case bound command   Yes              
logging enable             Yes    
logging size 1000             Yes    
record rc             Yes    
show archive log config all             Yes    
show running-config | include record rc|service sequence-numbers|service timestamps log datetime localtime year|service timestamps log datetime localtime show-timezone year             Yes    
show logging | include buffer logging:             Yes    
service timestamps log datetime localtime year             Yes    
service sequence-numbers             Yes    
logging buffered             Yes    
show archive log config *             Yes    
show logging             Yes    
show context               Yes  
show hostname Yes             Yes  
show running-config expand-port-profile Yes       Yes Yes      
logging level Yes Yes Yes Yes Yes Yes      
show running-config   Yes Yes Yes     Yes Yes Yes
show mode               Yes  
show interface               Yes  
show failover               Yes  
show ip interface brief             Yes    
show interfaces | include line | Hardware             Yes    
show interfaces capabilities             Yes    
show interfaces status             Yes    
show interfaces flowcontrol             Yes    
show udld             Yes    
show interfaces status err-disabled             Yes    
show vtp status             Yes    
show vlan             Yes    
show spanning-tree             Yes    
show spanning-tree mst configuration digest             Yes    
show etherchannel summary             Yes    
show resource   Yes Yes Yes Yes Yes      
show vsan   Yes   Yes          
show interface brief   Yes   Yes          
show port-security address | begin Vlan Yes Yes     Yes Yes      
show san-port-channel database   Yes   Yes          
show clock utc Yes                
show vdc fcoe-vlan-range Yes                

Recommended Solutions for Issues During DCNM Discovery

The following table displays a list of issues and recommended solutions that can assist you with troubleshooting a discovery issue. If an attempt to discover devices fails, you should implement these solutions.


Note


Cisco DCNM uses SSH to discover Nexus switches and Telnet for non-Nexus switches.


Issue Recommended Solution
Authentication Failure You have not entered the valid user credentials while logging into the device.

The following solution is recommended:

  1. Log into the device through an external SSH or Telnet client.
  2. Enter the username and password provided during discovery and verify if the login is successful.
Database exception Discovery failed due to an error or exception while querying the database. Rediscover the device.
Device sync-up failure The device is not managed due to an auto-synchronization failure. Rediscover the device.
Manually stopped the device sync-up You have manually disabled auto-synchronization and the device is not managed. To manage the device, enable auto-synchronization for the device.
Internal server error There is an exception raised during the discovery within the server. Rediscover the device.
Connection Failure Application protocol's connection (Telnet, SSH, or HTTP) is not available or the connection is timed out.

For Nexus platforms, connect the SSH server in the device through a third-party SSH client. Verify if the connection is established.

Through Telnet, log in to the device, and enter following commands:

Conf t;

Feature ssh;

For non-Nexus platforms, connect the device through the Telnet client available on Windows, Linux, or Solaris. Verify that the connection is getting established.

Unreachable The device is unreachable during discovery. Connect to the SSH server in the device through a third party SSH client. A successful connection will asks you for the user credentials.
Not discovered This is an default error when the server does not report an appropriate error. Rediscover the device.
Nodes went down The server was shut down when the device discovery was in progress. Rediscover the device.
Unsupported version The device platform is not supported in DCNM. See the Cisco DCNM Compatibility Matrix for supported versions.
Archive Logging Disabled The device archive logging is disabled. The following solution is recommended:
  1. Log into the device using a SSH or a Telnet client and enter the user credentials.
  2. In the privileged mode , enter the enable command and password.
  3. In the configuration mode, enter the config t command.
  4. In the archive mode, enter the archive command.
  5. In the log configuration mode, enter the log config command.
  6. Enter the logging enable command to enable logging.
  7. Rediscover the device.
Discovering Fabric Interconnect on secondary node UCS Manager is not available on the secondary Fabric Interconnect. Discover UCS through the primary Fabric Interconnect.
VTP Version 3 not supported Cisco DCNM does not support VTP version 3 on the Catalyst 6500 switch. The following solution is recommended:
  1. Log into the device using a SSH or a Telnet client and enter the user credentials.
  2. Configure the VTP version to either 1 or 2 as below: cat6k(config)# vtp version 1 or cat6k(config)# vtp version 2
  3. Rediscover the device.
Authorization Failure Authorization denied for the show commands during discovery. For information on commands that are supported during discovery, see the list of commands sent by discovery.
Discrepancy in System log Discrepancy found in the time order of the system log. The following solution is recommended:
  1. Log into the device using a SSH or a Telnet client and enter the user credentials.
  2. In the configuration mode, enter configuration t clear logging log.
  3. Enter the logging enable command to enable logging.
  4. Rediscover the device.
Discrepancy in accounting log Discrepancy found in the time order of the accounting log. The following solution is recommended:
  1. Log into the device using a SSH or a Telnet client and enter the user credentials.
  2. In the configuration mode, enter configuration t clear accounting log.
  3. Rediscover the device.
Logging level sync-up failure The required Cisco DCNM logging levels are not configured on your device. The following solution is recommended:
  1. Log into the device using a SSH or a Telnet client and enter the user credentials.
  2. In the configuration mode, enter conf t; logging level feature level .
  3. Rediscover the device.
Connection Limit exceeded The number of connections on the device exceeds its limit to accept any new connections. The following solution is recommended:
  1. Log into the device using a SSH or a Telnet client and enter the user credentials.
  2. View the existing active connections. For example, in the Cisco Nexus 7000 Series switches, enter the show users and show xml server status command to see the list of active users. See the device product page for the maximum concurrent active connections both in CLI and xml mode.
  3. Delete the unwanted connections from the CLI or XML mode. For example, in the Cisco Nexus 7000 Series switches, enter the show users, config t and clear unwanted-line-number-seen-in-show-users-o/p commands to clear CLI connections and show xml server status and xml server terminate session session-number-to-terminate
  4. Rediscover the device.
Non-admin FWSM context discovery not supported Discover the admin-supported context device.
SSH Exception SSH not available for the device. The following solution is recommended:
  1. Log into the device using a Telnet client and enter the user credentials.
  2. To enter the configuration mode, enter config t.
  3. To enable, enter feature SSH.
  4. Rediscover the device.
Insufficient User privilege Some commands are denied during discovery. The following solution is recommended:
  1. Log into the device using a SSH or Telnet client and enter the user credentials.
  2. To enter the configuration mode, enter config t.
  3. To enable, enter conf t; logging level feature level.
  4. For more information, see the Default Logging Level.
  5. Rediscover the device.
NTP not configured Configure NTP in the device and try rediscovering the device.
Device time is ahead of Cisco DCNM server time NTP is not configured in the Cisco DCNM server machine or in the device. Configure NTP in both the machine and try rediscovering the device.
Device time is not set Configure the device clock and try rediscovering the device.
Cisco DCNM does not support discovery of UCS server blades
  1. Discover virtualized servers using VMware before discovering Nexus devices to which the virtualized servers are connected.
  2. To discover the servers and devices using the web client, follow this procedure:
    1. Go to Servers– Admin Menu > Data Sources > VMware
    2. Go to Nexus Devices– Admin Menu > Data Sources > LAN
  3. When the Nexus device port server is up and running, Cisco DCNM detects automatically and triggers the server discovery.
  4. Use the show mac address-table command in Cisco DCNM to track the host connected to the switch.
    Note    The switch MAC address table will not have the host MAC addresses if there is no traffic flowing or the port connected to the server is operationally down.