Change IP Management HP Alletra 5010

[Group-IT-MTT]

Hi Support, 

I need to change Subnet and Gateway for IP Management HP Alletra 5010, can you give me procedure guidance. 

Regards, 

[support_s]

System recommended content:

1. Using Data Ops Manager | Creating a subnet for HPE Alletra 5000 and HPE Alletra 6000 systems

2. HPE Alletra dHCI Deployment Guide for New Installations

Please click on "Thumbs Up/Kudo" icon to give a "Kudo".

Thank you for being a HPE valuable community member.

[shiva_jr]

Hi @Group-IT-MTT ,
    I hope, these HPE documents help in editing subnet mask and Gateway (route). 
    Command formats : 

route --edit network --netconfig draft [--network new_network] [--gateway gateway]

     subnet --edit label [--new_label name] [--subnet_addr network_ipaddr/netmask] [--discovery_ipaddr ipaddr] [--type {mgmt | data | mgmt,data}] [--subtype {iscsi|group}] [--netzone_type {evenodd | bisect | single}] [--netconfig name] [--vlanid id] [--mtu mtu] [--failover {enable|disable}]

    Please let me know if the issue still persists.

Regards,
Shiva_jr

[giladzzz]

Hi

Before you change management parameters it is a good thing to have serial console on the array 

because if you make a mistake you will have a problem.

Regards

Giver a KUDO if this helps

[buzzsubash]

Below are the detailed steps to do from CLI

netconfig --create_draft_from active (creates a new draft)

netconfig --info draft (We will need to reference IP addresses)

array --list     (we will need that array name on the far left)

ip --edit x.x.x.x --netconfig draft --array <array name> --type support --newaddr <new IP controller A> --ctrlr A

ip --edit y.y.y.y --netconfig draft --array <array name> --type support --newaddr <new IP controller B> --ctrlr B

ip --edit z.z.z.z --netconfig draft --type management --newaddr <new IP for managment>

ip --edit w.w.w.w --netconfig draft --type secondary --newaddr <new IP for secondary management>

subnet --edit Management --subnet_addr <network with / subnet example 10.163.18.0/24> --discovery_ipaddr <discovery IP same as new IP for management> --netconfig draft

route --edit 0.0.0.0/0 --netconfig draft --gateway <gateway IP>

netconfig --info draft   (lets you confirm all changes)

netconfig --validate draft (will let you know that you can activate)

netconfig --activate draft (this will activate the draft making it the new running config)

Legend -

x.x.x.x = old ip for Controller A

y.y.y.y = old ip for Controller B

z.z.z.z = old ip for Management IP

w.w.w.w = old ip for Secondary Management IP

NOTE: vVOLS will be affected when you change the management IPs

- Additional resource to reference. https://infosight.hpe.com/InfoSight/media/kb/active/sup_KB-000002_Re-IPing_an_Array.whz/index.html#vot1494617448446.html. or search InfoSight Docs for "KB-000002 Re-IPing an Array"

- The certificate gets regenerated.
- VASA will be disconnected from vCenter
- vvols become unmanageable until VASA connectivity is re-established
- running VMs should be fine as long as you dont snapshot them/power them on or off/vmotion them, so fix with some expedience if you want to do those actions
(this includes DRS of course too)

- Also HA will fail if a VM crashes

[support_s]

Hello,

Let us know if you were able to resolve the issue.

If you are satisfied with the answers then kindly click the "Accept As Solution" button for the most helpful response so that it is beneficial to all community members.

Please click on "Thumbs Up/Kudo" icon to give a "Kudo".