I'm trying to see if anyone has any suggestions or best practice recommendations for EPG names of "kitchen sink" networks.
One of our APs collects several EPGs that are Static Path bound to VMware (we don't do VMM integration, separate topic). These are aligned in vCenter to indivudual portgroup profiles, and internally to vCenter given a portgroup profile name of just the Vlan# and subnet. When a new request for a VM comes in, they pick off an unused IP on that subnet and give it to the new VM, regardless who is requesting it or what application it's being used for, and aside from sometimes updating DNS the network team is otherwise never aware of the subnet's management or allocation.
The AP has several of these EPGs. I don't really want to call them "Network1" or "Net1_Vlan100_EPG", with the next one as "Network2" or "Net2_Vlan327_EPG". At that point, all I'm doing is refering to the VLAN# and basically nothing else. I mean, I "can" do that but there's no intelligence to it, nor is it self-documenting.
I can't influence the VMware folks on this point, all I can do roll is with it.
Does anyone have experience in this realm? Minimally in EPG naming but anyone with experience here would be welcome.
