In order to create an Inband Profile for Cisco Integrated Management Controller (IMC) connectivity, what do you need to perform first?

Question

Options

• ACreate a Management IP Pool, a MAC Address Pool, and a VLAN Pool
• BCreate an IPMI Policy
• CCreate a Service Profile
• DCreate different VLANs, with different VLAN IDs
• ECreate a Management IP Pool, a VLAN. and a VLAN Group

• A
  4% (1)
• C
  92% (24)
• E
  4% (1)

Explanation

Creating an Inband Profile in Cisco UCS Manager requires a Service Profile to exist first because the Inband Profile is bound directly to a Service Profile - it defines inband IMC management settings for a specific server identity, and that identity is represented by the Service Profile. Without a Service Profile to attach it to, the Inband Profile has no target object to configure.

Why the distractors are wrong:

• A - A Management IP Pool, MAC Pool, and VLAN Pool are useful building blocks in UCS, but this specific combination is not the prerequisite step for an Inband Profile.
• B - An IPMI Policy governs IPMI access settings and is a separate, independent configuration; it is not required before creating an Inband Profile.
• D - VLANs may be involved in inband networking, but simply creating VLANs with different IDs is not the defined prerequisite step.
• E - A Management IP Pool, VLAN, and VLAN Group are closer to what is eventually needed in the inband configuration, but these are configured within or alongside the profile, not strictly before it; and more importantly, the Service Profile must exist first.

Memory tip: Think "Profile before Policy" - in UCS, the Service Profile is the cornerstone object that gives a server its identity. Any management configuration (including inband) must anchor to an existing Service Profile, so always create it first.

No community discussion yet for this question.