Skip to content

What are Cisco UCS vNIC Redundancy Template Pairs?

A “Redundancy Pair” duplicates the vNIC on one FI to the other FI on failure.

The following configurations are shared when using template pairs:
• Network Control Policy
• QoS Policy
• Template Type
• Connection Policies
• VLANs
• MTU
• Statistics Threshold Policy

The following configurations are not shared when using template pairs:
• Fabric ID
• CDN Source
• MAC Pool
• Description
• Pin Group Policy

Source:
https://www.cisco.com/c/en/us/td/docs/unified_computing/ucs/ucs-central/GUI-User-Guides/Network-Mgmt/1-5/b_CiscoUCSCentral_NetworkManagementGuide_1-5/b_CiscoUCSCentral_NetworkManagementGuide_1-5_chapter_0100.pdf

Creating vNIC Template Pairs

Procedure


Step 1

In the Navigation pane, click the LAN tab. On the LAN tab, expand LAN > Policies.

Step 2

Expand the node for the organization where you want to create the policy. If the system does not include multi-tenancy, expand the root node.

Step 3

Right-click the vNIC Templates node and choose Create vNIC Template. In the Create vNIC Template dialog box, assign a Name, Description, and select the Fabric ID for the template.

Step 4

Select the Redundancy Type as Primary or Secondary or No Redundancy. See the redundancy type descriptions below.

Step 5

Select the Peer Redundancy Template—to choose the name of the corresponding Primary or Secondary redundancy template to perform the template pairing from the Primary or Secondary redundancy template.

  • Primary—Creates configurations that can be shared with the Secondary template. Any other shared changes on the Primary template are automatically synchronized to the Secondary template.

    • VLANS

    • Template Type

    • MTU

    • Network Control Policies

    • Connection Policies

    • QoS Policy

    • Stats Threshold Policy

    Following is a list of non-shared configurations:

    • Fabric ID

      Note

      The Fabric ID must be mutually exclusive. If you assign the Primary template to Fabric A, then Fabric B is automatically assigned to the Secondary template as part of the synchronization from the Primary template.

    • CDN Source

    • MAC Pool

    • Description

    • Pin Group Policy

  • Secondary

    All shared configurations are inherited from the Primary template.

  • No Redundancy

    Legacy vNIC template behavior.

Step 6

Click OK.

Source:
https://www.cisco.com/c/en/us/td/docs/unified_computing/ucs/ucs-manager/GUI-User-Guides/Network-Mgmt/3-1/b_UCSM_Network_Mgmt_Guide_3_1/b_UCSM_Network_Mgmt_Guide_3_1_chapter_0111.html

Published inCisco UCS

Be First to Comment

Leave a Reply

Your email address will not be published. Required fields are marked *