Reconfigure DataDomain network interfaces

you are too vague to say that much really.

The thing with network reconfiguration is that you have to consider not locking yourself out by incorrectly configuring the nic(s).

You talk about moving the nics towards a new subnet, is that another vlan or does that also need physical recabling?

Do you you have physical local access, just in case, so that you could still fix things if they go wrong?

Will it be possible to reconfigure the interfaces more or less one by one? While the other interfaces would still be available?

Having another system in the same subnet would be helpful in case you would have configured something incorrectly with the gateway as within the same subnet you might still be able to login to that interface.

Whenever reconfiguring the nics, I assume you would wanna prevent any data ingestion from occurring, so any backup application should be prevented to use the DD until finished. You would not need to stop anything on the DD itself. You can leave the filesystem and anything else up and running. If you have mtree replication going on, from or towards another DD, then that would be interrupted.

I would not know any reason why you would not be able to configure all interfaces. However for the veth interface, veth0, you would be configuring the veth0 and not the underlying physical interfaces eth1a and eth1b.

Are you also going to reconfigure the ipmi interface? If not, then from another DD you could connect to the SOL (serial over lan) connection to connect to the console.

@bbeckers1  you're right, after reading again I feel i write it a bit too fast.. Excuse me.

So let me add more details : 

I'll move the nics on another vlan (new vlan id) AND new subnet. Recabling will stay the same as i'll reconfigure core switch interfaces where DD is connected.
I got physical access to datacenter and remote/physical access to DD and also core network devices.
In order to make the actions secure, i'll plan to first make the change in the "passive" DD (the one not in production, only used for "replica of replicas") then if it goes well i'll go on active.

In my case i got another devices on the subnet so if it goes wrong/incorrectly configured i may still have access.

Will it be possible to reconfigure the interfaces more or less one by one? While the other interfaces would still be available?
- you mean the DD interfaces or the network swtich interfaces ? if it's about the DD, i got no preferences (can be all reconfigured at the same time or one by one, in any case the DD will be considered "in maintenance")

Whenever reconfiguring the nics, I assume you would wanna prevent any data ingestion from occurring, 
so any backup application should be prevented to use the DD until finished. 
You would not need to stop anything on the DD itself. 
You can leave the filesystem and anything else up and running. If you have mtree replication going on, from or towards another DD, then that would be interrupted.
 - thanks for these details. Actually all jobs that are around the DD will be stop for a timeslot.

I would not know any reason why you would not be able to configure all interfaces.
However for the veth interface, veth0, you would be configuring the veth0 and not the underlying physical interfaces eth1a and eth1b.
- right, eth1a and 1b are used but not configured with an IP as they're bonded.

Are you also going to reconfigure the ipmi interface? 
- no, ipmi is already in the correct subnet and vlan.

If not, then from another DD you could connect to the SOL (serial over lan) connection to connect to the console.
- i wasn't aware of that, thanks a lot ! 

Meanwhile, i saw there's 2 menus about network configuration

one in hardware > Ethernet that list every DD interfaces

another in Maintenance > Configurer System (it opens a popup) but it looks like an initial configuration (as it asks only about ethMa eth1c and eth1d)

Is there a specific order when nic will be reconfigured ?

Thanks a lot !

@motorbass​ might have a look at KB https://www.dell.com/support/kbdoc/en-us/000209434/data-domain-configuring-physical-interfaces "Data Domain - Configuring physical interfaces with Graphical User Interface (GUI)" and for vlan's https://www.dell.com/support/kbdoc/en-us/000206148 "Data Domain - Configuring a VLAN and IP Alias with Graphical User Interface (GUI)"

using ipmitool from windows or linux system (but also is possible between two DD's)

https://www.dell.com/support/kbdoc/en-us/000042933?lang=en "Data Domain: Using IPMI on Linux" and https://www.dell.com/support/kbdoc/en-us/000043086?lang=en "Data Domain: Accessing IPMI/SOL from Windows"

https://www.dell.com/support/kbdoc/en-us/000029715?lang=en "Configuring IPMI and SOL on the DD2500" shows some examples how to connect to another DD to give an indication...

Hey Gael! So you want to move these DD6300s to a new subnet, smart move for security. With all those network interfaces though, it can get tricky.

First up, take some precautions - check if any critical services need to be disabled temporarily to avoid issues during the changes. Maybe even reach out to the vendor for their recommendations on reconfiguring these specific models.

Once you've done your prep, you can use that UI to reconfigure ethMa, eth1c, and eth1d nice and easy with the new subnet info. For the bonded interfaces eth1a, eth1b, and veth0, you might need to dig into some commands or procedures based on the vendor guidance.

Take it slow, double check everything before applying changes. If you run into any snags, no worries, just roll back and ask for help. Better safe than ending up with a non-functional system, right?

After reconfiguring all the interfaces, you might want to reboot the appliances to make sure the new settings are locked in properly.

That's the gist of it, my friend! Prep well, follow the right steps, and don't hesitate to get support if needed. We'll get those DD6300s on that new subnet securely. Let me know if you need any other friendly tips!