Say, for example, I am deploying a large amount of VLANs with a vPC toology. So I would have no spanning tree loops. Logically my topology looks like a single Core switch to Access switch link. However, ideally I would like to only allow specific VLANs on each vPC.
I understand the MST recommendation that for an MST region I should allow all VLANs in that region over all trunk links involved in the region to avoid accidental traffic black holes.
However I don't really want to allow VLANs on a link to an edge switch when there are no ports in that VLAN on the edge switch. So since I have no STP loops could I safely allow VLANs 1 to 100 on vPC 100, VLANs 101 to 200 on vPC 200 and so on but still have all VLANs in one MST instance ? MST would still calculate vPC 100 and 200 as forwarding so my traffic still gets to where it needs to. Only if I introduce a loop is there a potential problem.
I don't want to rely on VTP pruning and I can't create many MST instances and easily allocate vlans to each one because any VLAN could be required on any vPC.
So can I create 1 MST instance, map all VLANs to it and still safely remove specific VLANs from vPC's on a vPC by vPC basis ?
My alternative is to have my 1000 VLANs each running a rapid instance on each port they are active on when I really don't need all that overhead with no loops in the network.
Introduction This article will help you understand the steps on how to
download the UCS licenses from the Cisco Systems website and then
installing it on the UCS. The redacted (blue lines) just covers up
certain numbers for privacy please do not take them...
Introduction This article will help you understand and educate the
customer on how to clear their "expired licenses"
(license-graceperiod-expired) from their UCS-M. If a customer just
purchased a license and needs a step by step guide on how to download
==================== VIC FNIC driver does not support Virtual Volumes (
second level LUN ID ) An enhancement request has been created to track
this feature - CSCux64473 UPDATE - 12-14-2016 We made some traction on
the enhancement request - The Fix is in t...