nerdexam
Cisco

500-920 · Question #17

What three options should be verified, when you are able to connect to Cisco UCS Manager, but unable to open a KVM session to a blade? (Choose three)

The correct answer is A. Verify TCP port 2068 is not blocked by an ACL or Firewall D. Confirm the KVM IP Address is added to the route table in Cisco UCS Manager E. Confirm the IP Address assigned to the KVM is not a duplicate IP. When KVM sessions fail while UCS Manager remains accessible, the problem lies in the KVM's dedicated network path, not the management plane. Option A is correct because Cisco UCS KVM traffic uses TCP port 2068, and a firewall or ACL blocking this port will prevent KVM sessions wh

Troubleshoot Cisco UCS B-Series

Question

What three options should be verified, when you are able to connect to Cisco UCS Manager, but unable to open a KVM session to a blade? (Choose three)

Options

  • AVerify TCP port 2068 is not blocked by an ACL or Firewall
  • BConfirm the IP Address assigned to UCS Manager is the same as the KVM address
  • CVerify the KVM IP Address is on the same ip subnet as the virtual machines
  • DConfirm the KVM IP Address is added to the route table in Cisco UCS Manager
  • EConfirm the IP Address assigned to the KVM is not a duplicate IP
  • FVerify the KVM IP Address is on the same subnet as the Fabric Interconnect management address

How the community answered

(58 responses)
  • A
    81% (47)
  • B
    5% (3)
  • C
    10% (6)
  • F
    3% (2)

Explanation

When KVM sessions fail while UCS Manager remains accessible, the problem lies in the KVM's dedicated network path, not the management plane. Option A is correct because Cisco UCS KVM traffic uses TCP port 2068, and a firewall or ACL blocking this port will prevent KVM sessions while leaving UCS Manager (HTTPS/443) fully reachable. Option D is correct because the KVM IP must have a valid route in UCS Manager's routing table - without it, return traffic from the blade's KVM IP has no path back to your client. Option E is correct because a duplicate IP causes ARP conflicts, making the KVM IP unreachable or intermittently unreachable, a classic silent failure.

Why the distractors are wrong: B is wrong because UCS Manager and KVM deliberately use different IPs by design - they should never be the same. C is irrelevant because KVM console access has no dependency on VM subnet placement. F is wrong because the KVM IP can reside on a different subnet than the Fabric Interconnect management interface, provided routing exists (which is what D covers).

Memory tip: Think "Port, Route, Duplicate" - P-R-D. These are the three network fundamentals that are specific to the KVM path but invisible to the UCS Manager path, which is exactly why they'd break KVM without breaking UCS Manager access.

Topics

#KVM connectivity#Network troubleshooting#Port configuration#IP routing

Community Discussion

No community discussion yet for this question.

Full 500-920 Practice