Refer to the exhibit. A network engineer must add a Cisco Nexus 5000 Series Switch to a Cisco DCNM. However, the device discovery status shows as unreachable. The engineer verifies these parameters…

Question

Exhibits

Options

• ARestart the Advanced Message Queuing Protocol service in the DCNM appliance.
• BIncrease the heap size of the Elasticsearch on the DCNM server.
• CGlobally enable Cisco Discovery Protocol on the switch and on the DCNM interface.
• DRediscover the Nexus switch from the DCNM server.

• A
  8% (3)
• B
  3% (1)
• C
  18% (7)
• D
  71% (27)

Explanation

When a device shows as "unreachable" in DCNM after all connectivity, credential, compatibility, and SSH parameters have been verified and confirmed correct, the fix is to trigger a rediscovery - DCNM needs to re-attempt the discovery process to clear the stale unreachable state and establish the managed relationship with the switch (option D).

Why the distractors are wrong:

• A is wrong because AMQP is a messaging service used for internal DCNM communication, not device discovery reachability - restarting it won't resolve a switch discovery failure.
• B is wrong because Elasticsearch heap size affects search/indexing performance and log capacity, not the device discovery or reachability mechanism.
• C is wrong because CDP enablement helps DCNM auto-discover devices on connected interfaces, but the scenario shows the device is already being added manually and SSH is the relevant protocol for DCNM-to-Nexus management communication - not CDP.

Memory tip: Think of it as a "refresh handshake" - once you've confirmed the four pillars (compatibility, credentials, IP reachability, SSH), DCNM just needs to be told to try again. If everything checks out externally, the answer is almost always to rediscover/re-initiate from the DCNM side rather than change any service or protocol.

No community discussion yet for this question.