Resolving Global vNIC Redundancy Template Pair Failure

D.

Global vNIC redundancy templates are used to provide redundancy and high availability to virtual network interface cards (vNICs) within Cisco UCS service profiles. These templates are created in pairs, with a primary and a secondary template. When a service profile is created using these templates, the primary vNIC is active, and the secondary vNIC is in a standby state. If the primary vNIC fails or becomes unavailable, the secondary vNIC takes over and becomes active.

When attempting to use a global vNIC redundancy template pair, it is possible to encounter an issue where the service profile fails to apply. To resolve this issue, the correct action is to assign the primary template first, and then set the peer name. This ensures that the primary vNIC is active and properly configured before attempting to configure the standby vNIC.

Option A, creating the peer names before creating the templates, is not a solution to this issue, as the peer name is not the cause of the problem.

Option B, assigning the secondary template first and then setting the peer name, may also result in a failed service profile. This is because the secondary vNIC is in a standby state and should not be configured until after the primary vNIC is properly configured.

Option C, assigning both templates simultaneously, may also result in a failed service profile, as the primary vNIC needs to be active and properly configured before the standby vNIC is configured.

Therefore, the correct answer is D, assign the primary template first, and then set the peer name.