ONTAP Discussions
ONTAP Discussions
Can i have more than one cluster IP and Node IP ??
Solved! See The Solution
Hello @luciferHK
I just tested this on my lab and this is what i got bellow; It should be possible as well as for Node
In case you dont see the screenshot, here us the output text. Might be distorted.
The cluster_mgmt_2 is the new cluster LIF(IP) i just created
login as: admin
Using keyboard-interactive authentication.
Password:
Last login time: 7/25/2019 18:45:15
cluster1::> net int show
(network interface show)
Logical Status Network Current Current Is
Vserver Interface Admin/Oper Address/Mask Node Port Home
----------- ---------- ---------- ------------------ ------------- ------- ----
cluster1
cluster1-01_mgmt1
up/up 192.168.0.111/24 cluster1-01 e0c true
cluster1-02_mgmt1
up/up 192.168.0.112/24 cluster1-02 e0c true
cluster_mgmt up/up 192.168.0.101/24 cluster1-01 e0c true
cluster1::> net int create -vserver cluster1 -lif cluster_mgmt_2 -role cluster-mgmt -address 192.168.0.105 -netmask 255.255.255.0 -home-node cluster1-02 -status-admin up -failover-policy broadcast-domain-wide -firewall-policy mgmt -auto-revert false -home-port e0c -failover-group Default
(network interface create)
cluster1::> net int show (network interface show)
Logical Status Network Current Current Is
Vserver Interface Admin/Oper Address/Mask Node Port Home
----------- ---------- ---------- ------------------ ------------- ------- ----
cluster1
cluster1-01_mgmt1
up/up 192.168.0.111/24 cluster1-01 e0c true
cluster1-02_mgmt1
up/up 192.168.0.112/24 cluster1-02 e0c true
cluster_mgmt up/up 192.168.0.101/24 cluster1-01 e0c true
cluster_mgmt_2
up/up 192.168.0.105/24 cluster1-02 e0c true
Please if this post resolved your issue, please help others by selecting ACCEPT AS SOLUTION or adding a KUDO or both!
Hello @luciferHK
I just tested this on my lab and this is what i got bellow; It should be possible as well as for Node
In case you dont see the screenshot, here us the output text. Might be distorted.
The cluster_mgmt_2 is the new cluster LIF(IP) i just created
login as: admin
Using keyboard-interactive authentication.
Password:
Last login time: 7/25/2019 18:45:15
cluster1::> net int show
(network interface show)
Logical Status Network Current Current Is
Vserver Interface Admin/Oper Address/Mask Node Port Home
----------- ---------- ---------- ------------------ ------------- ------- ----
cluster1
cluster1-01_mgmt1
up/up 192.168.0.111/24 cluster1-01 e0c true
cluster1-02_mgmt1
up/up 192.168.0.112/24 cluster1-02 e0c true
cluster_mgmt up/up 192.168.0.101/24 cluster1-01 e0c true
cluster1::> net int create -vserver cluster1 -lif cluster_mgmt_2 -role cluster-mgmt -address 192.168.0.105 -netmask 255.255.255.0 -home-node cluster1-02 -status-admin up -failover-policy broadcast-domain-wide -firewall-policy mgmt -auto-revert false -home-port e0c -failover-group Default
(network interface create)
cluster1::> net int show (network interface show)
Logical Status Network Current Current Is
Vserver Interface Admin/Oper Address/Mask Node Port Home
----------- ---------- ---------- ------------------ ------------- ------- ----
cluster1
cluster1-01_mgmt1
up/up 192.168.0.111/24 cluster1-01 e0c true
cluster1-02_mgmt1
up/up 192.168.0.112/24 cluster1-02 e0c true
cluster_mgmt up/up 192.168.0.101/24 cluster1-01 e0c true
cluster_mgmt_2
up/up 192.168.0.105/24 cluster1-02 e0c true
Please if this post resolved your issue, please help others by selecting ACCEPT AS SOLUTION or adding a KUDO or both!
I have done more than one cluster ip. Useful during migrations. Have a cluster split between two buildings. The mgmt networks are different so we have two cluster ip addresses. The nodes on either side continue with one ip. They really do not more than one. Will be removing nodes and then deleting the cluster ip in the older building
Yes, not common, but some customers have a private storage VLAN/subnet, but want access for management from the corporate network. I've seen it. I remember specifically because we had to do a perfstat with all the corporate node management LIF IPs instead of specifying cluster management IP. The perfstat was trying to connect to the storage network node-managment LIFs and taking twice as long!