FINALY i choose mtu 9 416 ... View more

attached is the topology, the switch is in l3 mode, the core switches are stacked, the sfp cables are 10g they interconnect the switch cores, switch distributions and the fw   ... View more

HELLo for the DNS, should I keep my internal DNS or take Google's? ... View more

When I connect to the firewall, there is no slowness but i connect to the core switch there is a lot of slowness ... View more

yes I see this option is the same one that is on my switch ... View more

WE have a firewall with fai we have 46 MBPS , but when  connect on ms425  we have 20 MBPS OR 30   MS425 is STP Root When you launch a web page, you have to restart it several times before it opens. Plus, there's a lot of Mac address flapping. ... View more

HELLO MS425 is configure L3 ROUTING but the parameter bridge priority is 8192 ... View more

The problem has been going on for seven months. We opened a ticket with Meraki support. Packet captures were taken, and support noted the slowness on the VLANs from the core switches. The following solution was proposed: Our analysis of the captured traffic reveals several network-related issues that are likely contributing to the performance problems. Specifically, we observed the following: TCP Retransmissions: The analysis of the traffic to both destination IPs shows significant TCP retransmissions. Retransmissions occur when a sender doesn't receive an acknowledgment for sent data, indicating packet loss or delays. This is a primary cause of slowdowns, as data needs to be re-sent, consuming more bandwidth and increasing transfer time. Increased Latency/Time Deltas: We noted noticeable time delays between packets. This increased latency slows down communication, as devices must wait longer for responses, impacting the overall transfer rate. TCP Window Size Fluctuations: The TCP window sizes vary, which can be a sign of congestion control mechanisms being triggered. While window size changes are normal, erratic or consistently small windows can further contribute to performance bottlenecks. These observations strongly suggest that network-level issues are impeding the Nutanix update process. To resolve this issue, we recommend the following troubleshooting steps: Investigate Network Congestion:​​​​​​​Uplink Utilization: Monitor the bandwidth usage of the switches' uplink(s) to identify any potential bottlenecks. Network Path Analysis: Use traceroute or similar tools to map the network path between the Nutanix servers/clients and the update servers (Akamai) to pinpoint potential congestion points. Check Physical Layer: Ensure all network cables are properly connected and in good working order. Quality of Service (QoS): Review your QoS configuration on other network devices to ensure that Nutanix update traffic is being prioritized appropriately. Isolate Network Segments: If possible, try to isolate different network segments to determine if the issue is localized to a specific area. Switch Restart (Troubleshooting Step): As a troubleshooting step, consider performing a controlled restart of the core switches (MS425) during a maintenance window. This can sometimes resolve transient software or hardware issues that might be contributing to the problem. ... View more

The problem has been going on for seven months. We opened a ticket with Meraki support. Packet captures were taken, and support noted the slowness on the VLANs from the core switches. The following solution was proposed: Our analysis of the captured traffic reveals several network-related issues that are likely contributing to the performance problems. Specifically, we observed the following: TCP Retransmissions: The analysis of the traffic to both destination IPs shows significant TCP retransmissions. Retransmissions occur when a sender doesn't receive an acknowledgment for sent data, indicating packet loss or delays. This is a primary cause of slowdowns, as data needs to be re-sent, consuming more bandwidth and increasing transfer time. Increased Latency/Time Deltas: We noted noticeable time delays between packets. This increased latency slows down communication, as devices must wait longer for responses, impacting the overall transfer rate. TCP Window Size Fluctuations: The TCP window sizes vary, which can be a sign of congestion control mechanisms being triggered. While window size changes are normal, erratic or consistently small windows can further contribute to performance bottlenecks. These observations strongly suggest that network-level issues are impeding the Nutanix update process. To resolve this issue, we recommend the following troubleshooting steps: Investigate Network Congestion:​​​​​​​ Uplink Utilization: Monitor the bandwidth usage of the switches' uplink(s) to identify any potential bottlenecks. Network Path Analysis: Use traceroute or similar tools to map the network path between the Nutanix servers/clients and the update servers  to pinpoint potential congestion points. Check Physical Layer: Ensure all network cables are properly connected and in good working order. Quality of Service (QoS): Review your QoS configuration on other network devices to ensure that Nutanix update traffic is being prioritized appropriately. Isolate Network Segments: If possible, try to isolate different network segments to determine if the issue is localized to a specific area. Switch Restart (Troubleshooting Step): As a troubleshooting step, consider performing a controlled restart of the core switches (MS425) during a maintenance window. This can sometimes resolve transient software or hardware issues that might be contributing to the problem. ... View more