ONTAP Discussions

Move e0M to default broadcast-domain

Sebastian_Antunez
4,611 Views

Hello Guys

 

I have the following problem

A two-node cluster was created, which is operational but in Network - Overview shows the e0M interface of controller-1 in broadcast domain Default and of controller-2 in broadcast domain Default-1

I need to know if it is possible to move the e0M of the controller located in Default-1 to Default and if they will have the cli command to do it.

 

 

Thanks for your help

1 ACCEPTED SOLUTION
9 REPLIES 9

Ontapforrum
4,576 Views

Yes, please follow the kb for the commands.

 

Note: You cannot directly modify the IPspace on the given port; instead remove it from the current broadcast domain and then add it to the appropriate broadcast domain in the desired IPspace.


How to change the IP space or broadcast domain on a port:
https://kb.netapp.com/onprem/ontap/da/NAS/How_to_change_the_IP_space_or_broadcast_domain_on_a_port

 

TMACMD
4,490 Views

That KB is seriously flawed.

Start with ... I am pretty sure the remove-port fails if there is a port that call the port trying to be removed "home". All that is being suggested is to migrate the port. I suspect the migrate needs to be done followed by a modify. Then the port can be removed from the BD. 

 

Next, If I actually to ad a port to the Cluster BD, the port will take on the MTU of that BD (which would be 9000 and the example is showing 1500) 

 

Finally, there should be some reference to removing the extra port...if e0c is no longer needed, it should be removed from the BD.

 

Sebastian_Antunez
4,572 Views

Hello

 

I have done this process before, but it is the e0M management port and it won't let me move it from broadcast domain.

 

Thanks

Ontapforrum
4,571 Views

What is the error you see when you say it won't let me move ?

 

Check this kb:

Unable to  add a port to broadcast domain - NetApp Knowledge Base

TMACMD
4,484 Views

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 LIF on a0a-99 (VLAN port 99).

 

In my cases, when the new node joins the cluster a few things happen:

  1. The node joins
  2. the node-xx_mgmt LIF maintains the UUID (it does not get renamed)
  3. the node e0M port cannot determine where to go since there are two broadcast domains that it can go into

 

Here is the fix, This usually is happening on a pair of new nodes:

  1. Get a cable and link two unused ports together. This is the trick, the port MUST have a link. the port does NOT need to be connected to any real network, just a LINK. You cannot migrate a LIF to another port unless that port has a LINK. ANY port with a link works. Remember, this is temporary!
  2. I will use e3a as an example. I connected a twinax between node-03:e3a and node-04:e3a
  3. Add node-03:e3a and node-04:e3a to the same Broadcast-domain as node-01:e0M and node-02:e0M:
  4. broadcast-domain add-ports -broadcast-domain Default -port node-03:e3a
  5. broadcast-domain add-ports -broadcast-domain Default -port node-04:e3a
  6. Modify the LIFs to use the temporary link (remember, the LIFs have a UUID at this point!)
  7. net int modify -vserver myclus -lif f6d01922-0075-11ee-90ab-d039ea9b02dd_mgmt1 | 74af8691-0075-11ee-a1b7-d039ea9b3e72_mgmt1 -home-port e3a
  8. Send the LIF home if needed: net int revert -vserver myclus -lif f6d01922-0075-11ee-90ab-d039ea9b02dd_mgmt1 | 74af8691-0075-11ee-a1b7-d039ea9b3e72_mgmt1 (the LIF may have AUTO-REVERT enabled and may go as soon as the port is changed)
  9. Now you can add e0M to the broadcast-domain
  10. Note: if the broadcast-domain containing the e0M ports is NOT called Default, you must rename the current Broadcast-domain to default to relocate e0M!
  11. broadcast-domain add-ports -broadcast-domain Default -ports myclus-03:e0M,myclus-04:e0M
  12. Modify/revert the LIF back to e0M
  13. net int modify -vserver myclus -lif f6d01922-0075-11ee-90ab-d039ea9b02dd_mgmt1 | 74af8691-0075-11ee-a1b7-d039ea9b3e72_mgmt1 -home-port e0M
  14. Send the lif home if needed: net int revert -vserver myclus -lif f6d01922-0075-11ee-90ab-d039ea9b02dd_mgmt1 | 74af8691-0075-11ee-a1b7-d039ea9b3e72_mgmt1
  15. Rename the LIF if desired:
  16. net int rename -vserver myclus -lif f6d01922-0075-11ee-90ab-d039ea9b02dd_mgmt1 myclus-03_mgmt
  17. net int rename -vserver myclus -lif 74af8691-0075-11ee-a1b7-d039ea9b3e72_mgmt1 myclus-04_mgmt
  18. Remove the e3a ports from the Broadcast Domain as they are no longer needed
  19. broadcast-domain remove-ports -broadcast-domain Default -port node-03:e3a
  20. broadcast-domain remove-ports -broadcast-domain Default -port node-04:e3a

Sebastian_Antunez
4,562 Views

1.jpg2.jpg3.jpg4.jpg

Ontapforrum
4,548 Views

Ok. Kb I mentioned deals with the error you have shared.

TMACMD
4,494 Views

Have you tried to merge them?

 

 Broadcast-domain merge -broadcast-domain Default-1 -into Default

 

??

Public