Changing network interface parameters

Changing network interface configuration after deploying storage or compute services includes network migration of this interface.

Prerequisites

To change network interface parameter

Admin panel

  1. On the Infrastructure > Nodes screen, click the name of the node, go to the Network interfaces tab, and then click the network interface.
  2. On the interface right pane, click Edit.
  3. In the Edit network interface window, change the required network settings. For example, you can change the IP address.
  4. Click Save to apply your changes.
  5. If you have already deployed storage or compute services, you will see the migration wizard. Wait until the new configuration is created, and then click Apply.

Command-line interface

Use the following command:

vinfra node iface set [--ipv4 <ipv4>] [--ipv6 <ipv6>] [--gw4 <gw4>] [--gw6 <gw6>]
                      [--mtu <mtu>] [--dhcp4 | --no-dhcp4] [--dhcp6 | --no-dhcp6]
                      [--auto-routes-v4 | --ignore-auto-routes-v4]
                      [--auto-routes-v6 | --ignore-auto-routes-v6]
                      [--network <network> | --no-network] [--connected-mode | --datagram-mode]
                      [--ifaces <ifaces>] [--bond-type <bond-type>] [--node <node>] <iface>
--ipv4 <ipv4>
A comma-separated list of IPv4 addresses
--ipv6 <ipv6>
A comma-separated list of IPv6 addresses
--gw4 <gw4>
Gateway IPv4 address
--gw6 <gw6>
Gateway IPv6 address
--mtu <mtu>
MTU interface value
--dhcp4
Enable DHCPv4
--no-dhcp4
Disable DHCPv4
--dhcp6
Enable DHCPv6
--no-dhcp6
Disable DHCPv6
--auto-routes-v4
Enable automatic IPv4 routes
--ignore-auto-routes-v4
Ignore automatic IPv4 routes
--auto-routes-v6
Enable automatic IPv6 routes
--ignore-auto-routes-v6
Ignore automatic IPv6 routes
--network <network>
Network ID or name
--no-network
Remove a network from the interface
--connected-mode
Enable connected mode (InfiniBand interfaces only)
--datagram-mode
Enable datagram mode (InfiniBand interfaces only)
--ifaces <ifaces>
A comma-separated list of network interface names, for example, iface1,iface2,...,ifaceN
--bond-type <bond-type>

Bond type (balance-rr, balance-xor, broadcast, 802.3ad, balance-tlb, balance-alb)

Bond type for an OVS interface (balance-tcp, active-backup)

--node <node>
Node ID or hostname (default: node001.vstoragedomain)
<iface>
Network interface name

For example, to change the IP address of the eth1 network interface located on the node node002 to 192.168.128.91/24, run:

# vinfra node iface set eth1 --node node002 --ipv4 192.168.128.91/24
+----------------------------+-----------------------------------------------------------------------+
| Field                      | Value                                                                 |
+----------------------------+-----------------------------------------------------------------------+
| configuration              | network_id: f50605a3-64f4-4f0c-b50e-9481ec221c72                      |
| link                       | href: /api/v2/network/migration/ba7854ed-167e-4d6b-ab19-7244371a1b27/ |
|                            | method: GET                                                           |
|                            | rel: network-migration-details                                        |
| operation                  | network-migration                                                     |
| progress                   | 0.0                                                                   |
| single_interface_migration | True                                                                  |
| state                      | preparing                                                             |
| task_id                    | ba7854ed-167e-4d6b-ab19-7244371a1b27                                  |
| transitions                | 0                                                                     |
+----------------------------+-----------------------------------------------------------------------+

If you have already deployed storage or compute services, you will see the output above. Wait until the new network configuration is tested, and then apply it:

# vinfra cluster network migration show | state
| state                      | test-passed                                  |
# vinfra cluster network migration apply