topic Re: Issue with Simplivity Host deployment - MTU Values in HPE SimpliVity

Issue with Simplivity Host deployment - MTU Values

jdheltne — Tue, 15 Jun 2021 21:28:20 GMT

We are building a new, 3 node Simplivity environment, and 2 of the 3 hosts have been deployed, along with their virtual controllers and management appliance. When we deployed them we used all MTU of 1500. Since they their MTU settings were updated by updated the interfaces file (ie /etc/network/interfaces) where eth1 and eth2 were updated to an MTU of 9000 for the storage and federation network. Now when I use the Simplivity deployment tool, it fails on New MTU Values Match Existing MTU Values and shows the old values. How do I fix the Simplivity deployment tool to reflect the current setting so I can deploy the new 3rd host?

Re: Issue with Simplivity Host deployment - MTU Values

US_SimpliVity — Wed, 16 Jun 2021 19:08:56 GMT

jdheltne,

The MTU change on the virtual controllers must be made by command line.

You can open a support case for assistance from the SimpliVity Support team if desired.

To complete the MTU change, the virtual controller services must be stopped, the MTU modified by command line, then the virtual controller services can be started again. This will require elevated command line privileges.

Perform this operation on ONE virtual controller.
Log into the virtual controller with administrator user account.
Execute the following commands where xx.xx.xx.xx is the Virtual Controller Storage IP address and yy.yy.yy.yy is the Virtual Controller Federation IP address.

sudo su source /var/tmp/build/bin/appsetup systemctl stop svtfs@0 dsv-address-change --interface Storage --address xx.xx.xx.xx --mtu 9000 dsv-address-change --interface Federation --address yy.yy.yy.yy --mtu 9000 systemctl start svtfs@0 svt-vm-show --violations

Wait for all VMs to obtain HA (no VMs should be reported in the violations output)

Perform the steps on the OTHER virtual controller.

Please open a support case if you do not feel comfortable with the command line changes.

I am an HPE Employee.

Re: Issue with Simplivity Host deployment - MTU Values

jdheltne — Wed, 16 Jun 2021 15:07:49 GMT

and Im guessing the management interface would be

dsv-address-change --interface Management --address xx.xx.xx.xx --mtu 9000

Re: Issue with Simplivity Host deployment - MTU Values

jdheltne — Wed, 16 Jun 2021 15:11:26 GMT

This is what we had done previously

sudo nano /etc/network/interfaces
modify eth1 to mtu 9000
save and close file
sudo service networking restart
sudo ifup eth1

Re: Issue with Simplivity Host deployment - MTU Values

jdheltne — Wed, 16 Jun 2021 15:18:06 GMT

When I tried this I get

Welcome to SimpliVity OmniCube 4.1.0.266

Last login: Tue Jun 15 23:09:25 2021 from 16.118.104.234
administrator-dasvm@omnicube-ip184-16:~$ sudo sudo
usage: sudo -h | -K | -k | -V
usage: sudo -v [-AknS] [-g group] [-h host] [-p prompt] [-u user]
usage: sudo -l [-AknS] [-g group] [-h host] [-p prompt] [-U user] [-u user]
[command]
usage: sudo [-AbEHknPS] [-r role] [-t type] [-C num] [-g group] [-h host] [-p
prompt] [-T timeout] [-u user] [VAR=value] [-i|-s] [<command>]
usage: sudo -e [-AknS] [-r role] [-t type] [-C num] [-g group] [-h host] [-p
prompt] [-T timeout] [-u user] file ...
administrator-dasvm@omnicube-ip184-16:~$ source /var/tmp/build/bin/appsetup
administrator-dasvm@omnicube-ip184-16:~$ systemctl stop svtfs@0
Failed to stop svtfs@0.service: The name org.freedesktop.PolicyKit1 was not provided by any .service files
See system logs and 'systemctl status svtfs@0.service' for details.
administrator-dasvm@omnicube-ip184-16:~$ dsv-address-change --interface Storage --address 192.168.0.16 --mtu 9000
dsv-address-change: command not found

Re: Issue with Simplivity Host deployment - MTU Values

US_SimpliVity — Wed, 16 Jun 2021 19:07:19 GMT

Sorry for the typographical error.

This first command is:
sudo su

I am an HPE Employee

Re: Issue with Simplivity Host deployment - MTU Values

jdheltne — Wed, 16 Jun 2021 21:08:09 GMT

This didnt fix my deployment manager issue I still get MTU errors on deployment. It is like deployment manager is keeping a record of how systems were deployed rather than how they are currently configured, because it still shows the system with MTU of 1500 when on the system it is 9000.