Fas2720 re-init, e0M not a member of a broadcast domain and no way to get it to join. | NetApp | Page 1

eager radish Oct 18, 2024, 9:20 PM

#

Running broadcast-domain add-ports -broadcast-domain Default -ports <node 2:e0M>

Command failed: Port "node2:e0M" cannot be used because it is currently the home port or current port of a LIF

Then it lists some commands to run to see who is using e0M as a home port, etc. the thing is, I am setting up 2 identical systems, and one is exactly like the other in every way, except for this. Running these 'home' commands shows the exact same thing on both, and the only real difference is one of the e0Ms just isn't in a broadcast domain on one of the systems. Thus, I can't use it for failover, it's showing as down, etc. anyone have any ideas? I saw one person set up a temporary BD with some spare ports, then did some migrating, but since there's only one rj45 on each of these, that's out

Please help. Thanks!

little shard Oct 18, 2024, 9:48 PM

#

Ah. I have hit this issue SO MANY times. THe culprit, I will bet is that you have an e0M AND a tagged vlan using the same L2 space (same network subnet)

#

First the patch:
I typically find two ports on the new nodes that are unused. All you need is a LINK at this point, does not need to be viable., just a link. Temporarily add that particular link to the Default broadcast domain. Modify the mgmt LIF to now use the port you just added to the broadcast domain. Next, add the nodes e0M to the broadcast domain. Modify the MGMT LIF to now use the node e0M which it should allow you to do now. Then remove the temporary port from the broadcast domain.

#

Now the FIX (I know because it just worked last week)

Merge the VLAN into the Default broadcast domain.

create a failover-group containing JUST the e0M ports

failover-group create -vserver cluster -failover-group e0M -port node-01:e0M,node-02:e0M,node-03:e0M,node-04:e0M

create a failover-group containing JUST the tagged vlan ports

failover-group create -vserver cluster -failover-group VLAN -port node-01:a0a-x,node-02:a0a-x,node-03:a0a-x,node-04:a0a-x

modify the Node-MGMT to use the new failover groups

net int modify -vserver cluster -lif !cluster_mgmt -failover-policy disabled -failover-group e0M
net int modify -vserver cluster -lif cluster_mgmt -failover-policy broadcast-domain-wide -failover-group e0M -auto-revert true

Modify the tagged vlan ports
net int modify {-home-port a0a-x} -failover-group VLAN

Now when you add nodes, the e0M will join in the fun at Default.

The other option is to remove the tagged VLAN for MGMT if it is not in use

eager radish Oct 21, 2024, 4:25 PM

#

little shard Ah. I have hit this issue SO MANY times. THe culprit, I will bet is that you hav...

Ooh ok so I can use the fc/cna ports on these as members of a temporary BD then? Will be trying this afternoon. Thanks!

little shard Oct 21, 2024, 5:05 PM

#

They will need to be in CNA/Ethernet mode

#

And not a temporary bd. You need to add them to the bd with your other mgmt ports. Then remove when done. Please read and understand first then do

eager radish Oct 21, 2024, 5:10 PM

#

@little shard sorry, didn't word that properly. Meant to say "as temporary members of a BD"

#

Oh hey and it's your guide that I can across the other day from June 2023 lol. Cheers 🙂

eager radish Oct 21, 2024, 6:33 PM

#

@little shard or anyone, trying my best to follow along with the above guide and the one you posted last summer - https://community.netapp.com/t5/ONTAP-Discussions/Move-e0M-to-default-broadcast-domain/m-p/444830/highlight/true#M42334

Getting an error that isn't mentioned anywhere I can find.

Specifically, after getting my temporary ports into the Default BD, trying to migrate the management LIF back to e0M yelds this:

Re: Move e0M to default broadcast-domain

And this KB is also flawed. I run into this problem all the time. usually due to "properly" setting up broadcast domains (place all e0M in one BD and then have a BD with a tagged VLAN that happens to be the as the access ports that e0M is using...like a LIF on e0M (Access port VLAN 99) and another L...

#

googling ' "currently has no carrier" netapp ' yields 0 results

#

📎 fas2720_troubleshooting.txt

#

maybe some progress? this port is not "home", so trying to revert it now, but getting this:

eager radish Oct 21, 2024, 6:48 PM

#

eager radish googling ' "currently has no carrier" netapp ' yields 0 results

fixed this, turns out I had a mashed up end on the network cable that was in this port. So, at least some of the pins weren't connected properly.

#

annnnd that fixed everything. sorry for the stream of thought. Thanks for your help!

eager radish Oct 21, 2024, 6:57 PM

#

eager radish <@894285831248957440> or anyone, trying my best to follow along with the above g...

I do wish this was just a simple "hey the link is down, double check your link" instead of the cryptic "has no carrier" which even to a 14 year IT vet, doesn't scream "check layer 1"

#

or, just let me change the port to whatever I want. Warn me that it's down, that's fine, but let me do it at least.

Ok i'm signing off now, thanks again all

little shard Oct 22, 2024, 1:15 AM

#

@eager radish so you are good then? the directions I supplied worked until the "mashed end" got in the way?

eager radish Oct 22, 2024, 1:53 PM

#

that's correct, thank you again!

#Fas2720 re-init, e0M not a member of a broadcast domain and no way to get it to join.