How to activate the MTU 9000 after installation?
yannick
3 Posts
May 29, 2018, 8:53 pmQuote from yannick on May 29, 2018, 8:53 pmHi,
The cluster is operational, but during the installation, I did not configure the MTU. How can I configure it without having to reinstall everything ?
Congratulations on this amazing project.
Thank you
Yannick
PS : please excuse me for my English, I use a translator.
Hi,
The cluster is operational, but during the installation, I did not configure the MTU. How can I configure it without having to reinstall everything ?
Congratulations on this amazing project.
Thank you
Yannick
PS : please excuse me for my English, I use a translator.
Last edited on May 29, 2018, 8:56 pm by yannick · #1
admin
2,930 Posts
May 29, 2018, 10:49 pmQuote from admin on May 29, 2018, 10:49 pmThis is stored in the json config file /opt/petasan/config/cluster_info.json
An example
{
"backend_1_base_ip": "10.0.4.0",
"backend_1_eth_name": "bond0",
"backend_1_mask": "255.255.255.0",
"backend_2_base_ip": "10.0.5.0",
"backend_2_eth_name": "bond0",
"backend_2_mask": "255.255.255.0",
"bonds": [
{
"interfaces": "eth3,eth4",
"is_jumbo_frames": true,
"mode": "balance-rr",
"name": "bond0",
"primary_interface": ""
}
],
"eth_count": 5,
"iscsi_1_eth_name": "eth1",
"iscsi_2_eth_name": "eth2",
"jumbo_frames": [
"eth2",
"eth3",
"eth4"
],
"management_eth_name": "eth0",
"management_nodes": [],
"name": "demo"
}
of interest are "jumbo_frames" listing the nics and "is_jumbo_frames" for bond definition. You can also create a test config yourself by installing a single vm and select "Create New Cluster" during deployment,,you do not have to deploy other nodes but you can use the json file generated without messing with manual editing.
This file needs to be changed on all nodes, then all need to be rebooted. If you have many nodes you can use the file sync utility rather than copying it one by one:
/opt/petasan/scripts/util/sync_file.py /opt/petasan/config/cluster_info.json
This is stored in the json config file /opt/petasan/config/cluster_info.json
An example
{
"backend_1_base_ip": "10.0.4.0",
"backend_1_eth_name": "bond0",
"backend_1_mask": "255.255.255.0",
"backend_2_base_ip": "10.0.5.0",
"backend_2_eth_name": "bond0",
"backend_2_mask": "255.255.255.0",
"bonds": [
{
"interfaces": "eth3,eth4",
"is_jumbo_frames": true,
"mode": "balance-rr",
"name": "bond0",
"primary_interface": ""
}
],
"eth_count": 5,
"iscsi_1_eth_name": "eth1",
"iscsi_2_eth_name": "eth2",
"jumbo_frames": [
"eth2",
"eth3",
"eth4"
],
"management_eth_name": "eth0",
"management_nodes": [],
"name": "demo"
}
of interest are "jumbo_frames" listing the nics and "is_jumbo_frames" for bond definition. You can also create a test config yourself by installing a single vm and select "Create New Cluster" during deployment,,you do not have to deploy other nodes but you can use the json file generated without messing with manual editing.
This file needs to be changed on all nodes, then all need to be rebooted. If you have many nodes you can use the file sync utility rather than copying it one by one:
/opt/petasan/scripts/util/sync_file.py /opt/petasan/config/cluster_info.json
yannick
3 Posts
May 30, 2018, 1:19 pmQuote from yannick on May 30, 2018, 1:19 pmHello,
What responsiveness ! Thank you
Yannick
Hello,
What responsiveness ! Thank you
Yannick
How to activate the MTU 9000 after installation?
yannick
3 Posts
Quote from yannick on May 29, 2018, 8:53 pmHi,
The cluster is operational, but during the installation, I did not configure the MTU. How can I configure it without having to reinstall everything ? Congratulations on this amazing project. Thank you Yannick PS : please excuse me for my English, I use a translator.
Hi,
The cluster is operational, but during the installation, I did not configure the MTU. How can I configure it without having to reinstall everything ? Congratulations on this amazing project. Thank you Yannick PS : please excuse me for my English, I use a translator.
admin
2,930 Posts
Quote from admin on May 29, 2018, 10:49 pmThis is stored in the json config file /opt/petasan/config/cluster_info.json
An example
{
"backend_1_base_ip": "10.0.4.0",
"backend_1_eth_name": "bond0",
"backend_1_mask": "255.255.255.0",
"backend_2_base_ip": "10.0.5.0",
"backend_2_eth_name": "bond0",
"backend_2_mask": "255.255.255.0",
"bonds": [
{
"interfaces": "eth3,eth4",
"is_jumbo_frames": true,
"mode": "balance-rr",
"name": "bond0",
"primary_interface": ""
}
],
"eth_count": 5,
"iscsi_1_eth_name": "eth1",
"iscsi_2_eth_name": "eth2",
"jumbo_frames": [
"eth2",
"eth3",
"eth4"
],
"management_eth_name": "eth0",
"management_nodes": [],
"name": "demo"
}of interest are "jumbo_frames" listing the nics and "is_jumbo_frames" for bond definition. You can also create a test config yourself by installing a single vm and select "Create New Cluster" during deployment,,you do not have to deploy other nodes but you can use the json file generated without messing with manual editing.
This file needs to be changed on all nodes, then all need to be rebooted. If you have many nodes you can use the file sync utility rather than copying it one by one:
/opt/petasan/scripts/util/sync_file.py /opt/petasan/config/cluster_info.json
This is stored in the json config file /opt/petasan/config/cluster_info.json
An example
{
"backend_1_base_ip": "10.0.4.0",
"backend_1_eth_name": "bond0",
"backend_1_mask": "255.255.255.0",
"backend_2_base_ip": "10.0.5.0",
"backend_2_eth_name": "bond0",
"backend_2_mask": "255.255.255.0",
"bonds": [
{
"interfaces": "eth3,eth4",
"is_jumbo_frames": true,
"mode": "balance-rr",
"name": "bond0",
"primary_interface": ""
}
],
"eth_count": 5,
"iscsi_1_eth_name": "eth1",
"iscsi_2_eth_name": "eth2",
"jumbo_frames": [
"eth2",
"eth3",
"eth4"
],
"management_eth_name": "eth0",
"management_nodes": [],
"name": "demo"
}
of interest are "jumbo_frames" listing the nics and "is_jumbo_frames" for bond definition. You can also create a test config yourself by installing a single vm and select "Create New Cluster" during deployment,,you do not have to deploy other nodes but you can use the json file generated without messing with manual editing.
This file needs to be changed on all nodes, then all need to be rebooted. If you have many nodes you can use the file sync utility rather than copying it one by one:
/opt/petasan/scripts/util/sync_file.py /opt/petasan/config/cluster_info.json
yannick
3 Posts
Quote from yannick on May 30, 2018, 1:19 pmHello,
What responsiveness ! Thank you
Yannick
Hello,
What responsiveness ! Thank you
Yannick