nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Component react.community-search had an error.

ref must be one of: categoryID, siteSectionID, category, category/categoryID, category/name, category/description, category/url, category/allowedDiscussionTypes, locale, siteSection, siteSection/basePath, siteSection/contentLocale, siteSection/sectionGroup, siteSection/sectionID, siteSection/name, siteSection/description, siteSection/apps, siteSection/attributes, layoutViewType, discussionID, commentID, page, latest, sort, sortType, lookupSort, discussion, discussion/name, tags, breadcrumbs, discussionApiParams, serverDraftID, serverDraft.

Error to create peer cluster setup using Ontap simulator 9.12.1.

Shubhangi_Ranvirkar

Hello Team,

We are trying to create peer cluster setup using Ontap simulator 9.12.1.

We have 2 node cluster setup and created logical interface on cluster1 to communicate using command :
Cluster991::> net interface create -vserver Cluster991 -lif Cluster991-01_LIF1 -address 192.168.32.119 -service-policy default-management -netmask 255.255.240.0 -home-node Cluster991-01 -home-port e0d -status-admin up -failover-policy local-only -firewall-policy mgmt -auto-revert true -failover-group Default -is-dns-update-enabled false

After that we tried to create peer cluster setup using command :

Cluster9121::> cluster peer create -address-family ipv4 -peer-addrs 192.168.32.119 -no-authentication true

Error: command failed: The address family IPv4 of the specified peer addresses is not valid in the IPspace "Default":
there are no operational local IPv4 intercluster LIFs available in the "Default" IPspace. Use the "network
interface show" command to verify that required LIFs are present and operational on each cluster node.

IP Address: 192.168.32.119.

Getting above error and configuration is not complete.

Kindly suggest workaround/inputs to make peer cluster setup available.

Thanks in advance.

Regards,
Shubhangi Ranvirkar

Find more posts tagged with

Comments

TMACMD

Instead of this what you did:

net interface create -vserver Cluster991 -lif Cluster991-01_LIF1 -address 192.168.32.119 -service-policy default-management -netmask 255.255.240.0 -home-node Cluster991-01 -home-port e0d -status-admin up -failover-policy local-only -firewall-policy mgmt -auto-revert true -failover-group Default -is-dns-update-enabled false

do this instead:

net interface create -vserver Cluster991 -lif Cluster991-01_LIF1 -address 192.168.32.119 -service-policy default-intercluster -netmask 255.255.240.0 -home-node Cluster991-01 -home-port e0d -status-admin up -failover-policy disabled

the service policy needs to be default intercluster

in most cases the failover policy can be disabled. (Most usually use a vlan on a port channel and most do not have an extra port for it to fail over to)

since it shouldn’t move, you can skip the auto revert and the failover group and the dns option is always false.

tip: if the option tabs out with a value, that is the default value.

TMACMD

And in case you didn’t already know, a cluster peer is full mesh. Every node on both sides must have an intercluster lif.

Ashun

When creating a intercluster lif, select -service-policy default-intercluster as the service-policy

chenguanghui

Please refer to the following article:

创建集群对等关系 (netapp.com)

如何使用 IP 空间使用指定的集群间 LIF 创建和配置集群对等关系 - NetApp

junwang

Hi Shubhangi Ranvirkar,

When creating lif,Select service policy default-intercluster from the options here
Do not choose service policy default-management
Both sides of the lif should choose service policy default-intercluster lif
Afterwards, try pinging the lif IPs on both sides. Once the IPs are pinged, create a cluster peer.