I'm currently struggling with the automatically created and joined ports into default broadcast domains. How can I disable the auto creation and join of new ports into def. broadcast domains?
#disable automatic broadcast domain creation
latent fox
sudden aurora
you can disable placing new vlans or ifgrps into broadcast domains. Note that you cannot force every port to move to the "Default" broadcast domain by default. Rather they will not be member of any broadcast domain.
The reason is that once a port is in a broadcast domain, ONTAP can move LIFs to that port and if you have not made sure that the layer 2 reachability is correct on those ports, this has the potential to disrupt client traffic
latent fox
so "-skip-broadcast-domain-placement" will be my friend
is -skip-broadcast-domain-placement also available into the powershell module?
sudden aurora
that I don't know from the top of my head, sorry
desert skiff
One thing I've found that helps is placing ports/ifgrps into the broadcast domains you want before plugging in the network cables. If I plug the cables in first, I get the mess of Default-1,2,3,4 broadcast domains.
latent fox
The cluster is already in use 🙄
desert skiff
broadcast-domain split/merge are your friend then
latent fox
yes, that's the way how to fix it... but I'm looking for a way without that struggle - i've up to 500 vlan's per node
pure coral
Why? If your networking is not setup "correctly" ONTAP will let you know.
What I do when I find that a tagged VLAN shares the same BD as e0M, I first verify with the customer. THen I just go ahead and "fix" it cleanly
failover-group create -vserver clus_admin -failover-group mgmt -targets node-01:e0M,node-02:e0M
failover-group create -vserver clus_admin -failover-group mgmt-vlan -targets node-01:a0a-123,node-02:a0a-123
Then modify the interfaces
net int modify -vserver clus_admin -lif * -failover-group mgmt
net int modify -vserver clus_admin -lif !cluster* -failover-policy disabled
But if you want the node-mgmt to failover, then:
net int modify -vserver clus_admin -lif * -failover-policy local
sudden aurora
yeah, I also started to like the automatic BD placement in ONTAP. No more guessing which port is in which access VLAN, ONTAP finds that out for you
pure coral
Not perfect. Some switches do odd things with the native VLANs for ifgrps in that it doesnt detect properly. After verifing the port-configs on the switch, I typically do
broadcast-domain merge Default-2 Default-1
(which are usually the a0a ifgrp ports)
Then I rename:
broadcast-domain rename Default-1 DoNotUse
I am a big fan of vlan tags and try not use the "base" ifgrp (a0a) for anything except sizing it for MTU (9000) so that tagged VLANs can do standard or Jumbo frames
sudden aurora
I usually remove the native VLANs (i.e. a0a etc) from all broadcast domains, since normally you don't want to place LIFs on those anyway, and if you remove them ONTAP won't let you accidentally place LIFs on them
pure coral
LOL...thats why I call the Broadcast domain DoNotUse