diff options
author | Gwenael Lambrouin <gwenael.lambrouin@orange.com> | 2021-12-06 09:23:21 +0100 |
---|---|---|
committer | Gwenael Lambrouin <gwenael.lambrouin@orange.com> | 2022-03-10 09:20:53 +0100 |
commit | a055c1555e0a8c0cfb8c6308990a23eb8db59d13 (patch) | |
tree | b6895702cc437747fd55256e43efb33c220443b2 /docs/testing/user/userguide/images/nfvbench-npvp.png | |
parent | ae318cc8930dd19a3051fee4a0fc26d1a37c64d8 (diff) |
nfvbenchvm: set mgmt interface MTU=1500 by default
By default, configure the MTU of the management interface to the
conservative value of 1500: this will reduce the risk to get an
unmanageable VM. Else the MTU we will get will depend on the IaaS setup
and it could be high. And this will lead to troubles when we try to
manage the VM from a machine configured with a high MTU and when the
network path contains a link with a low MTU. This can typically happen
when we try to manage the VM from another VM in the same IaaS and when
the management traffic has to go outside the IaaS.
To set the MTU to a different value, configure the INTF_MGMT_MTU
variable in /etc/nfvbenchvm.conf. If INTF_MGMT_MTU is set to the
special value "auto", the MTU will not be configured and it will keep
the value set by the hypervisor ("legacy" nfvbenchvm behavior). If
INTF_MGMT_MTU is unset, the MTU will be set to 1500. In other cases,
the MTU will be set to the value of INTF_MGMT_MTU.
Change-Id: I5816113bbacec5fcdcc9672e20d8a4e2ac0c599a
Signed-off-by: Gwenael Lambrouin <gwenael.lambrouin@orange.com>
Diffstat (limited to 'docs/testing/user/userguide/images/nfvbench-npvp.png')
0 files changed, 0 insertions, 0 deletions