05-18-2017 02:00 PM
Can some one give me an advantage of using a vNIC redundancy pair template versus just have two vNIC template. I've not been able to find much info.
Thanks.
Solved! Go to Solution.
05-22-2017 10:34 AM
Hello,
On a high level, it eases out managing vNICs or VHBA pair which needs to have same set of configuration
For example, consider blades with two vNICs where each vNIC traffic needs to go through different FI path.
With vNIC template redundancy pair feature, secondary vNIC template synchronize the shared properties from primary templates and reduces error ( MTU, vLAN , etc ) between two vNICs.
Let me know if you need more information.
Thanks
Padma
05-22-2017 10:34 AM
Hello,
On a high level, it eases out managing vNICs or VHBA pair which needs to have same set of configuration
For example, consider blades with two vNICs where each vNIC traffic needs to go through different FI path.
With vNIC template redundancy pair feature, secondary vNIC template synchronize the shared properties from primary templates and reduces error ( MTU, vLAN , etc ) between two vNICs.
Let me know if you need more information.
Thanks
Padma
05-30-2023 09:27 PM - edited 05-30-2023 09:36 PM
deleted
05-30-2023 09:29 PM - edited 05-30-2023 09:34 PM
After a new search found this, and it's helpful:
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
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide