starlingx/docs
Code Issues Proposed changes
Files
a370b29a9c182e64cbb7ecbc15dd3a63b6b24427
docs/doc/source/system_configuration/changing-the-mtu-of-an-oam-interface-using-the-cli.rst
Drake Finlay 54ec38e256 Adding System Config Guide 
Incorporated patchset 8 review comments from Mary C.

Conditionalized vendor-specific terms and converted code-block to
parsed-literal as required
Reformatted bulleted lists to definition lists
Implemented abbreviation substitutions
Deleted duplicate content
Some minor edits for clarity
Merged new abbreviation definitions in strings.txt

Responding to Patch 5 comments.

Change-Id: If6dd7c4cb802036445cb65853d8de7652df351c0
Signed-off-by: Stone <ronald.stone@windriver.com>
2020-12-21 13:28:54 -05:00

1.6 KiB
Raw Blame History

Change the MTU of an OAM Interface Using the CLI

You can change the value of an interface using the CLI.

If you prefer, you can use the Horizon Web interface; see 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.

  1. Lock the standby controller.

    ~(keystone_admin)$ system host-lock controller-1

  2. Use the system host-if-modify command to specify the interface and the new MTU value on the standby controller. This example assumes the interface name as oam0.

    ~(keystone_admin)$ system host-if-modify controller-1 oam0 --imtu 1600

  3. Unlock the standby controller.

    ~(keystone_admin)$ system host-unlock controller-1

  4. Swact the controllers.

    ~(keystone_admin)$ system host-swact controller-1

  5. Lock the new standby controller.

    ~(keystone_admin)$ system host-lock controller-0

  6. Modify the of the corresponding interface on the standby controller.

    ~(keystone_admin)$ system host-if-modify controller-0 oam0 --imtu 1600

  7. Unlock the standby controller.

    ~(keystone_admin)$ system host-unlock controller-0