Skip to main content

Change EMC Storage Management IP Address without Storage Reboot

Issue : 
- How to Change EMC Storage Management IP Address without Reboot
- Customer needs to change the IP address, subnet mask , default gateway of a CLARiiON or VNX for Block storage processor (SP)without rebooting the Storage Processors (SP)

Scenario : EMC CLARiiON or VNX BLOCK Storage System

Solution :

1) Download and Install Naviseccli utility

 2)Run following command
Add Security Parameters
For SPA
naviseccli -User admin -Password password -Address 172.XX.XX.XX -Scope 0 -AddUserSecurity

For SPB
naviseccli -User admin -Password password -Address 172.XX.XX.XX -Scope 0 -AddUserSecurity

Get the info about existing SPs
For SPA
naviseccli -h 172.XX.XX.XX networkadmin -get
For SPB
naviseccli -h 172.XX.XX.XX networkadmin -get


Change the IP Address
For SPA
naviseccli -h 172.XX.XX.XX networkadmin -set -address 172.XX.XX.XX -subnetmask 255.255.255.0 -gateway 172.XX.XX.XX

naviseccli -h 172.XX.XX.XX networkadmin -set -address 172.XX.XX.XX -subnetmask 255.255.255.0 -gateway 172.XX.XX.XX



Congratulations! IP Address is changed!!!

Detailed Procedure from EMC Support :

 naviseccli commands will not cause SPs to reboot.
Using the CLARiiON/Block setup page in GUI causes a  reboot
Any name change requires SP reboot.

Instructions to update the SPs IP addresses, netmask and gateway IPs is below:

Before you begin:
Check to be sure the array is not part of a storage domain
Check that all hosts have dual-Fibre connectivity and that failover software is working correctly

In Unisphere, Under Domains-> Local - for the array he logged into.
Next, clicked on local, only one array  should show up - the array the IPs are being change on


Connect to the Array via the naviseccli
Verify the current settings and record them.
Command to check the current SP settings:
CMD:
 naviseccli -h <current SPaIP> networkadmin -get
SAMPLE OUTPIT:
Storage Processor:                  SP A
Storage Processor Network Name:     A-IMAGE
Storage Processor IP Address:       10.241.xx.xx
Storage Processor Subnet Mask:      255.255.xx.xx
Storage Processor Gateway Address:  10.241.xx.xx

Repeat for SPB

Verify the new information before hitting <enter>
Once the new ipaddresses are set, if any mistakes were made, it may be necessary to attach directly to the array to correct via the service or serial port
SAMPLE:
 naviseccli -h <current SPaIP> networkadmin -set -address <newSPaIP> -subnetmask <if changing-new IP> -gateway <if changing-newIP>

At this point theCustomer's  network would need to be changed for the new array IP addresses.
Ping the new SP IP and be sure you are able to connect to it before proceeding to SPB.
Once the SPA is updated, contacted, and accessible, Complete changes on SPB




Comments

Post a Comment

Popular posts from this blog

Solved | SendGrid SSL CERTIFICATE_VERIFY_FAILED certificate verify failed | self signed certificate in certificate chain

Error :   PS C:\Ashish> & "C:/Program Files/Python39/python.exe" c:/Folder/SendEmail.py Traceback (most recent call last):   File "C:\Program Files\Python39\lib\urllib\request.py", line 1346, in do_open     h.request(req.get_method(), req.selector, req.data, headers,   File "C:\Program Files\Python39\lib\http\client.py", line 1279, in request     self._send_request(method, url, body, headers, encode_chunked)   File "C:\Program Files\Python39\lib\http\client.py", line 1325, in _send_request     self.endheaders(body, encode_chunked=encode_chunked)   File "C:\Program Files\Python39\lib\http\client.py", line 1274, in endheaders     self._send_output(message_body, encode_chunked=encode_chunked)   File "C:\Program Files\Python39\lib\http\client.py", line 1034, in _send_output     self.send(msg)   File "C:\Program Files\Python39\lib\http\client.py", line 974, in send     self.connect()   File "C:\Program Files\P

Fixed | WSUS 2016 | Error Code 0x8024401c | Windows 10 | Windows Server 2016

Scenario : Server : Windows WSUS Server 2016 Client : Windows 10, Windows Server 2016 Error Code :  0x8024401c on Windows 10 or Windows Server 2016 Solution : 1) Go to IIS Manager on WSUS Server 2) Goto Advance Settings of  WsusPool. 3) Make sure following settings are present/configured on the Pool, if not change it to below: Queue Length: 25000 Limit Interval (minutes): 15 "Service Unavailable" Response: TcpLevel Private Memory Limit (KB): 0 4) Make sure, the WSUS Entry in the Registry is having fully qualified domain name of WSUS Server. 5) Stop the IIS 6) Edit the web.config located at following location on WSUS Server : C:\Program Files\Update Services\WebServices\ClientWebService\web.config Replace <httpRuntime maxRequestLength="4096" /> with <httpRuntime maxRequestLength="204800" executionTimeout="7200"/> 7) Start the IIS 8) Retry updating clients. Done! Let me know if it has helped to y