Back to bug 1033260
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Brent Holden | 2013-11-21 19:18:17 UTC | Summary | Asymmetric instance bandwidth using tunnelling (GRE/VXLAN) through Neutron | Asymmetric instance bandwidth using tunneling (GRE/VXLAN) through Neutron |
| Joe Talerico | 2013-11-21 19:20:29 UTC | CC | jtaleric | |
| Summary | Asymmetric instance bandwidth using tunneling (GRE/VXLAN) through Neutron | Asymmetric instance bandwidth using Floating IP w/ tunneling (GRE/VXLAN) through Neutron | ||
| Bill Burns | 2013-11-21 19:24:55 UTC | CC | perfbz | |
| RHEL Program Management | 2013-11-21 19:31:21 UTC | Target Release | --- | 4.0 |
| Terry Wilson | 2013-11-25 20:17:55 UTC | Status | NEW | ASSIGNED |
| CC | twilson | |||
| Assignee | rhos-maint | rkukura | ||
| Bob Kukura | 2013-12-03 22:28:10 UTC | Flags | needinfo?(jtaleric) | |
| Link ID | Launchpad 1252900 | |||
| Bob Kukura | 2013-12-05 03:15:28 UTC | CC | bholden | |
| Flags | needinfo?(jtaleric) | needinfo?(bholden) | ||
| Joe Talerico | 2013-12-05 13:35:39 UTC | Flags | needinfo?(bholden) | |
| lpeer | 2013-12-08 20:39:48 UTC | Priority | unspecified | high |
| Status | ASSIGNED | CLOSED | ||
| CC | lpeer, rkukura | |||
| Resolution | --- | CANTFIX | ||
| Doc Text | Cause: Having GRO offloading enabled while using floating IP with GRE/VXLAN tunnelling Consequence: The instance gets asymmetric bandwidth Workaround (if any): disabling GRO offloading on the network node Result: Almost symmetric bandwidth | |||
| Doc Type | Bug Fix | Known Issue | ||
| Flags | needinfo?(rkukura) | |||
| Last Closed | 2013-12-08 15:39:48 UTC | |||
| Bruce Reeler | 2013-12-12 06:05:22 UTC | CC | breeler | |
| Doc Text | Cause: Having GRO offloading enabled while using floating IP with GRE/VXLAN tunnelling Consequence: The instance gets asymmetric bandwidth Workaround (if any): disabling GRO offloading on the network node Result: Almost symmetric bandwidth | When “generic receive offload” (GRO) is enabled while using floating IP with GRE/VXLAN tunneling, inbound bandwidth available to instances using an external gateway from a provider network is extremely low. This is a due to the instance having asymmetric bandwidth. Workaround: Disable GRO offloading on the network node. This will provide more symmetric bandwidth and faster inbound data flow. | ||
| Flags | needinfo?(rkukura) | |||
| Bob Kukura | 2013-12-12 23:05:58 UTC | Blocks | 1042507 | |
| Bob Kukura | 2013-12-12 23:16:00 UTC | Blocks | 1042507 | |
| Doc Text | When “generic receive offload” (GRO) is enabled while using floating IP with GRE/VXLAN tunneling, inbound bandwidth available to instances using an external gateway from a provider network is extremely low. This is a due to the instance having asymmetric bandwidth. Workaround: Disable GRO offloading on the network node. This will provide more symmetric bandwidth and faster inbound data flow. | When “generic receive offload” (GRO) is enabled while using GRE/VXLAN tunneling, inbound bandwidth available to instances using a neutron router with an external gateway from a provider network is extremely low. Workaround: Disable GRO offloading on the network node using the command "ethtool -K <network interface> gro off". This will provide more symmetric bandwidth and faster inbound data flow. | ||
| Flags | needinfo?(rkukura) needinfo?(rkukura) | needinfo?(lpeer) | ||
| Bob Kukura | 2013-12-13 14:40:27 UTC | Doc Text | When “generic receive offload” (GRO) is enabled while using GRE/VXLAN tunneling, inbound bandwidth available to instances using a neutron router with an external gateway from a provider network is extremely low. Workaround: Disable GRO offloading on the network node using the command "ethtool -K <network interface> gro off". This will provide more symmetric bandwidth and faster inbound data flow. | When “generic receive offload” (GRO) is enabled while using GRE or VXLAN tunneling, inbound bandwidth available to instances from an external network using a neutron router is extremely low. Workaround: Disable GRO offloading on the network node whre the l3-agent runs using the command "ethtool -K <network interface> gro off". This will provide more symmetric bandwidth and faster inbound data flow. |
| Bob Kukura | 2013-12-13 16:02:06 UTC | Doc Text | When “generic receive offload” (GRO) is enabled while using GRE or VXLAN tunneling, inbound bandwidth available to instances from an external network using a neutron router is extremely low. Workaround: Disable GRO offloading on the network node whre the l3-agent runs using the command "ethtool -K <network interface> gro off". This will provide more symmetric bandwidth and faster inbound data flow. | When “generic receive offload” (GRO) is enabled while using GRE or VXLAN tunneling, inbound bandwidth available to instances from an external network using a neutron router is extremely low. Workaround: Disable GRO offloading on the network node where the l3-agent runs by adding the following line to /etc/sysconfig/network-scripts/ifcfg-ethX: ETHTOOL_OPTS="-K ethX gro off" where ethX is the network interface device used for the external network. Either reboot or run "ifdown ethX; ifup ethX" for the setting to take effect. This will provide more symmetric bandwidth and faster inbound data flow. |
| lpeer | 2013-12-15 07:35:01 UTC | Flags | needinfo?(lpeer) | |
| Bruce Reeler | 2013-12-16 06:52:39 UTC | Doc Text | When “generic receive offload” (GRO) is enabled while using GRE or VXLAN tunneling, inbound bandwidth available to instances from an external network using a neutron router is extremely low. Workaround: Disable GRO offloading on the network node where the l3-agent runs by adding the following line to /etc/sysconfig/network-scripts/ifcfg-ethX: ETHTOOL_OPTS="-K ethX gro off" where ethX is the network interface device used for the external network. Either reboot or run "ifdown ethX; ifup ethX" for the setting to take effect. This will provide more symmetric bandwidth and faster inbound data flow. | When “generic receive offload” (GRO) is enabled while using GRE or VXLAN tunneling, inbound bandwidth available to instances from an external network using a OpenStack Networking router is extremely low. Workaround: Disable GRO offloading on the network node where the l3-agent runs by adding the following line to /etc/sysconfig/network-scripts/ifcfg-ethX: ETHTOOL_OPTS="-K ethX gro off" where ethX is the network interface device used for the external network. Either reboot or run "ifdown ethX; ifup ethX" for the setting to take effect. This will provide more symmetric bandwidth and faster inbound data flow. |
| Perry Myers | 2016-04-26 13:57:35 UTC | CC | pmyers |
Back to bug 1033260