docs/doc/source/system_configuration/kubernetes/changing-the-mtu-of-an-oam-interface-using-the-cli.rst
Rafael Jardim 01ba8ebfd6 Update system configuration
There are minor changes here, that update the content of some files
here is the link to the commit on downstream
http://bitbucket.wrs.com/projects/DOCS/repos/
starlingx_upstreaming/commits/3b193cc3aa566b2040c7226a9ed32d08bd91b82f


Signed-off-by: Rafael Jardim <rafaeljordao.jardim@windriver.com>
Change-Id: I461fce0c81f4605c200572ff71ae52cc889a856b
2021-03-08 10:52:00 -03:00

62 lines
1.6 KiB
ReStructuredText

.. nnm1552672805879
.. _changing-the-mtu-of-an-oam-interface-using-the-cli:
================================================
Change the MTU of an OAM Interface Using the CLI
================================================
You can change the |MTU| value of an |OAM| interface using the CLI.
If you prefer, you can use the Horizon Web interface; see
:ref:`Change the MTU of an OAM Interface Using Horizon
<changing-the-mtu-of-an-oam-interface-using-horizon>`.
Controller configuration changes require each controller to be locked. This
requires a swact.
.. rubric:: |proc|
#. Lock the standby controller.
.. code-block:: none
~(keystone_admin)]$ system host-lock controller-1
#. Use the :command:`system host-if-modify` command to specify the interface
and the new MTU value on the standby controller. This example assumes the
|OAM| interface name as **oam0**.
.. code-block:: none
~(keystone_admin)]$ system host-if-modify controller-1 oam0 --imtu 1600
#. Unlock the standby controller.
.. code-block:: none
~(keystone_admin)]$ system host-unlock controller-1
#. Swact the controllers.
.. code-block:: none
~(keystone_admin)]$ system host-swact controller-1
#. Lock the new standby controller.
.. code-block:: none
~(keystone_admin)]$ system host-lock controller-0
#. Modify the |MTU| of the corresponding interface on the standby controller.
.. code-block:: none
~(keystone_admin)]$ system host-if-modify controller-0 oam0 --imtu 1600
#. Unlock the standby controller.
.. code-block:: none
~(keystone_admin)]$ system host-unlock controller-0