Refer to the exhibit. F16338 [FSM:STAGE:FAILED]: Establish connection Stage: comp/prov-VMware/cdr-[RTPACIlab]-Test vCenter Failed to retrieve ServiceContent from the vCenter server 10.12.2.253:532…

Question

Options

• AThe specified data center does not exist on the vCenter m question.
• BThe Cisco APIC(s) cannot reach the vCenter host/vm.
• CThe Service Content process has crashed.
• DCisco Discovery Protocol is disabled on the vSwitch policy tied to the corresponding AAEP.

• A
  75% (27)
• B
  3% (1)
• C
  6% (2)
• D
  17% (6)

Explanation

Option A is correct because the FSM path in the error (cdr-[RTPACIlab]-Test vCenter) includes the datacenter name configured in the APIC VMM domain - if that datacenter name doesn't exist on the target vCenter server, APIC cannot proceed with provisioning the DVS, producing this "Failed to retrieve ServiceContent" fault. Option B is wrong because a total connectivity failure (unreachable host) would generate a TCP-level error (timeout/connection refused), not a ServiceContent retrieval failure, which implies the TCP session was at least partially established. Option C is wrong because "ServiceContent" is a VMware vSphere API root object, not an OS-level process - it cannot "crash" independently of the vCenter service itself. Option D is wrong because CDP (Cisco Discovery Protocol) governs endpoint/hypervisor discovery and is unrelated to APIC's ability to authenticate and communicate with the vCenter management API.

Memory tip: Picture the FSM path like a postal address - APIC found the right building (IP/port reachable) but the suite number (datacenter name) doesn't exist, so delivery fails. Mismatched datacenter names = no ServiceContent.

No community discussion yet for this question.