After migrating a server that is configured with dynamic vNICs, Cisco UCS Manager assigns new dynamic vNICs to the server. If you had been monitoring traffic on an original dynamic vNIC, what must you

Question

Options

• AReassign the dynamic vNIC back to the old configuration.
• BNothing; Cisco UCS Manager will take over.
• CReassign the service profile back to the master one.
• DRemove and reconfigure the dynamic vNIC.
• EReassign the monitoring source.

• A
  4% (2)
• B
  5% (3)
• C
  14% (8)
• D
  2% (1)
• E
  75% (43)

Explanation

When a server migrates, Cisco UCS Manager assigns new dynamic vNICs with new identifiers, rendering the original vNIC you were monitoring effectively gone - your monitoring session is now pointing at a vNIC that no longer exists. E is correct because you must update the monitoring source to reference the newly assigned dynamic vNIC so traffic capture resumes on the correct interface.

Why the distractors are wrong:

• A - You cannot "reassign" the old vNIC back; dynamic vNIC assignment is controlled by UCS Manager automatically post-migration, not manually reversed.
• B - UCS Manager handles vNIC provisioning, but it has no awareness of your external monitoring session; it will not update that for you.
• C - Reassigning a service profile to a master profile addresses configuration inheritance, not a broken monitoring source.
• D - The new dynamic vNIC is already configured correctly by UCS Manager; there is nothing wrong with the vNIC itself that requires removal.

Memory tip: Think of dynamic vNICs like temp phone numbers - when the server migrates, it gets a new number. Your monitoring tool still has the old number on speed dial, so you have to update the contact manually. UCS Manager is the phone company; it doesn't update your address book.

No community discussion yet for this question.