Static Mac address question: Static mac addresses don't have aging time and they will take place of mac address that learned via arp right? Also, can we config static mac address for multiple int in the same vlan?-Yes. If you put the 'show mac address-table', you can see the static assignation and also can configure another mac-address in.
Vnic Mac Addresses Manual Cisco Download
I've run into an interesting issue and for the life of me I cannot figure out why it happened. Not only did it happen, but it happened in 2 different environments (UCS environments), on 6 different blades.
I have about 30 UCS B200 blades all running ESXi. There are various revisions so I have different Service Profile Templates and corresponding Service Profiles, but the networking policy is the same for pretty much everything. The vNICs in UCS have specific VLANs associated with them and the vNICs get these settings from vNIC templates. Furthermore, the Service Profile Templates specify the vNIC template binding order. vNIC0 through vNICx applies in that order.
So on to the problem: For 24 current blades and for a number of blades that have been replaced in the past, due to the specified binding order on the Service Profile Template, the Service Profile's vNICs 0 through x would perfectly and ALWAYS, WITHOUT EXCEPTION, bind to the ESXi hosts' vmnic0 through x. So:
UCS vNIC0 = ESXi Host vmnic0
UCS vNIC1 = ESXi Host vmnic1
UCS vNIC2 = ESXi Host vmnic2
... and so on.
Now on these six brand new UCS blades, the mapping is all over the place and I cannot figure out for the life of me why this is. I am pretty sure VMware assigns vmnicx based on some sort of mac address logic (lowest mac address gets vmnic0?). I am about to dive into that a bit. I just wanted to ping the community and see if anyone has any thoughts on this. Was I just extremely lucky for 24+ other Blades/ESXi hosts that this behavior worked?
Thanks,
Vnic Mac Addresses Manual Cisco Router
Edit Update: Cisco bug. Has to do with how they are delivering information to the OS level. NICs are in the appropriate order from the UCS side, but when the OS solicits or receives the info for the NIC order, it screws them up. TAC specifically recognized that they see this MORE with m5s then they have in previous builds. Cisco linked this BugID to me:
Vnic Mac Addresses Manual Cisco Server
There's ways around it but they all involve me burning more of my time than I am willing to spend since I've already brought these devices online and fully conditioned them and got them past security scans. This is annoying and I want to punch a baby. For now I am just going to reorder the adapters linked to my virtual distributed switches.