It just adds a layer of complexity when working with a small amount of VLANs. If you have a large group of VLANs you are going to be adding or you need to divide up groups of VLANs for tenant purposes, they might be useful. I wouldn't say there is a reason NOT to use them, it is just a lot simpler to use global individual VLANs and prune them via LAN uplinks manager if required. ... View more

If you want to restrict certain VLANs, you can use LAN Uplinks manager instead of VLAN Groups.   https://community.cisco.com/t5/unified-computing-system/vlans-not-in-a-vlan-group/td-p/3839018 ... View more

Okay, so I am seeing some similar behavior when I add a VLAN group to the specified uplink. It is taking away my global VLANs and only adding the VLANs defined in my VLAN group.   You do not have many VLANs on your uplinks, so I think you should just get rid of VLAN groups all together, and just add VLANs as global or as Fabric A or B specific. I think the VLAN groups in your use case are causing more confusion. I have typically only used VLAN groups when adding VLANs to uplinks when you have 50 or more VLANs. ... View more

Creating a new global VLAN should make it appear on all of the FI uplinks by default.   Let me know the results of the tests in my previous posts, and can you also confirm what each uplink physically connects to and what the running configs are for those uplink interfaces are? Similar to the outputs from my lab. ... View more

Should not be related, I just configured a VLAN group and both my VLAN group VLANs and my Fabric B VLANs all show up on the correct uplinks.   If you create a new test VLAN on A only or B only, does it show up correctly on Fabric A/B?   If you create a new test VLAN that is global/common, does it show up correctly on both fabrics?   If you add a VLAN to a VLAN group, does it show up correctly on both fabrics?   Can you send outputs for VLAN 32 and another working VLAN?   B(nxos)#show vlan id 32 ... View more

When you create a VLAN in UCSM it is distributed to all the uplink interfaces by default. You dont specify a VLAN group to go to a specific port or port-channel.   If you have a disjointed layer 2 network with multiple upstream switches, where some switches utilize certain VLANs while others do not, you would use LAN Uplinks manager to pin a specific VLAN to a specific uplink. If you only have a single layer 2 network northbound of the fabric interconnects, you want to create your VLAN under Fabric A or B and then it will only be distributed to only uplinks on the A or B. If you create them as global VLANs, they are distributed to A and B.   In my lab I have multiple global VLANs which you will see configured on my both Br1/25/1 uplinks, but also VLANs specific to Fabric A/B. I have a single uplink on A side and single uplink for B.     ... View more

Screen cap from 3.2.3i....no plans of phasing out LAN uplinks manager I am aware of.   ... View more