#trying to create a cluster

1 messages · Page 1 of 1 (latest)

cedar agate
#

Hi guys, I’m trying to create a cluster on our AFF C250s via the CLI and I get the following error when creating the cluster:

Trying to create cluster again as previous attempt failed. Error: unused cluster ports exist in the cluster. One or more ports may not be in the “healthy” state or may be incorrectly assigned to the “cluster” Ipspace.

I run a - “network port show -ipspace cluster” and no ports are showing. We have Broadcom cluster interconnect switching which is not showing any link lights or anything.

Any help would be appreciated 🙂

midnight verge
#

Are you creating a 2 node cluster or 4 node cluster? With a 2 node cluster you have a direct connection between the nodes

south basin
#

If no ports are showing up you first need to create them. You need two ports per node in the Cluster ipspace

midnight verge
#

And did you reboot the nodes? I think there was a bug with the c250 on a specific level

south basin
#

Or rather: you need to move the two ports to the Cluster ipspace and then creat a cluster LIF on each of them

midnight verge
#

And what also can be during the setup, you will be asked if you want to use the configuration of the ports, select no and then they should be created

#

@south basin I had the same issue with an A150 where only one port was configured during the setup. After saying no the other port was correct initialized

south basin
#

In those cases I usually do it manually. Faster than rebooting and trying again 😅

midnight verge
#

🙈

cedar agate
#

This is a 2 node HA pair and we have 2 of them so 4 node in total

#

Haven’t done any ipspace configs

#

I’m following this article if it helps

#

Got to the point of entering a name for the cluster smashed enter then the CLI threw the error

south basin
cedar agate
#

Sorry wrong article!

south basin
cedar agate
#

This one

south basin
feral nest
#

Bottom line is this:

verify the entire cluster is properly cabled before you do anything. Reboot the nodes and it will work. If you use the wrong ports, there will be issues including supportability after the fact

cedar agate
#

We currently have e0c/e0d going to Broadcom cluster interconnect switching, which provides the 169 ranges as expected.

I did notice that when going through the cluster config, we're using the E0M (Which I assume is the spanner RJ45) rather than e0a. Would this be the cause of this?

#

Everything has been cabled correctly (i've traced the cables)

#

I'll give it a reboot and try again however

feral nest
#

I corrected my post. It is e0c/e0d.

#

The e0M is used for management and should be connected for service processor access

When setting the ip for the node and the service processor which share the e0M port make sure they are in the same ip network range/subnet

#

e0M is for management only and will not pass data

feral nest
#

Then you’ve messed with the service-policy/firewall policy for the node management

#

Guess I’ll have to try. On 7-mode it could. Never really tried in ONTAP. I’ll run a few scenarios

#

But, best practices do not want data on e0M

cedar agate
#

Just as an update - Turns out that the Fiber cables I used were at fault here. I used some SFP modules which were not compatible with the broadcom switch which caused it to force the Interfaces offline. Swapped it into some pre-made Fiber cables and worked a treat 😄

forest basalt
# feral nest But, best practices do not want data on e0M

@feral nest I stand corrected. You can't host a simple NAS LIF on the e0M port; I just tried in a lab. Interesting. I'd never tried it and wasn't expecting this error:

Info: create_imp: Failed to create logical interface.
Error: command failed: Port e0M on node <node_name> is not capable of hosting LIF cjtest.

Wow, I was not expecting that. I'll happily take the "L" on that one.

https://kb.netapp.com/on-prem%2Fontap%2Fda%2FNAS%2FNAS-KBs%2FPort_e0M_on_node_is_not_capable_of_hosting_LIF