Manually Set IP, Subnet And Gateway Addresses On VNX Control Station

Quite a long time ago I asked about how to change the Gateway and Subnet mask addresses on a unified system. I know this is a global settings so it has to be done on the control station. I once receive a link how to do it by CLI but this articel took care of changing IP adreses not gateway and subnet.

# /nas/sbin/getreason11 - slot_0 secondary control station10 - slot_1 primary control station 5 - slot_2 contacted 5 - slot_3 contactedc) Change the IP address on CS1:# nas_cs -set -ip4address 10.240.200.51 -ip4netmask 255.255.255.0 -ip4gateway 10.240.200.1OK# nas_cel -list# grep /etc/hosts10.240.200.51 cs1_250.localdomain cs1_250d) Verify that CS1's IP address has been updated to the domain before continuing# /nas/sbin/navicli -h 10.240.200.52 domain -list# /nas/sbin/navicli -h 10.240.200.53 domain -list

Manually Set IP, Subnet And Gateway Addresses On VNX Control Station

Download File: https://jinyurl.com/2vBI1y

Got an odd issue. New installation of a VNX5400. Everything is working fine EXCEPT I can't communicate with the storage processor management ip's on any remote subnets. Local subnet works fine. Remote subnets I can talk with both control stations fine (can ping everything but the SP mgmt ip address on A or B). I have verified that address/subnet masks/default gateways are configured correctly on both SPA and SPB as well as on both control stations. I have tried restarting the management agents and restarting the storage processors. There are no firewalls between anything. Any ideas? I know the storage management ip addresses are proxied through the control stations in some way when they communicate with the public LAN but I am not sure what to check other than the /etc/hosts file and the ip routing table on the control stations which both look correct.

Modifying the Control Station hostname, IP address, subnet mask, or gateway may disrupt the Unisphere software connection and any other client access to the Control Station. It may be necessary to reconnect to continue administrative activities. If you make a mistake changing the network, the Control Station may no longer be reachable remotely.

In the meantine I found you a working work-a-round.Go to you VMkernel and change the subnet mask to 255.255.0.0.Then go to your TCP/IP stack and change the gateway to the correct IP in your home subnet.Then go back to your vmkernel and change the IP to an IP in the same subnet range as you home subnet and put the subnet mask back to 255.255.255.0

Last week I had to change the default gateway for an EMC VNX5300 storage system. The SPs network properties, its IP address, subnet mask, and default gateway cannot be changed in Unisphere but must be changed through the control station using the steps below. It is important to note that the following steps apply only to FILE OE versions at 7.0.35 and later. I performed the steps below on FILE OE version 7.1.55.3 and would recommend calling into EMC support to verify the steps on your storage system before attempting.

Change SP_A IP:naviseccli -h 192.168.101.40 -user sysadmin -password sysadmin -scope 0 networkadmin -set -ipv4 -address 10.236.66.71 -subnetmask 255.255.255.0 -gateway 10.236.66.1

Change SP_B IP:naviseccli -h 192.168.101.41 -user sysadmin -password sysadmin -scope 0 networkadmin -set -ipv4 -address 10.236.66.72 -subnetmask 255.255.255.0 -gateway 10.236.66.1

2ff7e9595c