![]() This shows 100% packet loss when no fragmentation is allowed. This causes fragmentation because system packets use 8996 as the MTU. Here's an example of an instance (deployed in OSP 16.1.5) configured with jumbo frames (8996), but you can see that the network path does not also have jumbo frames configured. In telco workloads, for example, the most common MTU value for all instances is 9000, so it's easy to inadvertently cause fragmentation after networks and instances have been created. However, the compute node itself is still set to the MTU, so fragmentation may still occur. This allows administrators to create 1500 MTU networks for the instances. Neutron networks are created after OSP is deployed. Normally, the System Integrator expects that the end-to-end path is properly configured before deploying and configuring the network for the stack to avoid constant MTU changes just for testing. Changing the configuration after the cluster is deployed is not recommended. ![]() The Message Transfer Unit (MTU) configuration is also generated at this stage. OpenStack initiates the network interface card (NIC) configuration during the initial setup of the cluster or when new nodes are added.
0 Comments
Leave a Reply. |