Difference between revisions of "Troubleshoot"

From Personal Wiki
Jump to navigation Jump to search
Line 1: Line 1:
== MTU MSS ==
+
== Not working network ==
 +
*Duplex
 +
*Cable
 +
*Firewall - disable it
 +
*DNS filtering - public DNS
 +
*ISP outage - ping its address
 +
*Path outage - MTR tool
 +
*ARP old record
 +
*MAC collision
 +
*STP loop/Broadcast storm
 +
*Route missing
 +
*LACP/PAGP must be on both ends configured
 +
*Zombie process and station or froze
 +
*Local firewall on device, or network type (windows-public)
  
 +
 +
== Slow network ==
 +
*Path drop - MTR tool
 +
*Number of active sessions on device
 +
*Packet/Frame size
 +
*Number of ACL on device
 +
*Wireless is slower + wireless noise
 +
*Duplex
 +
*Cable
 +
*Link type overhead + MTU
 +
*Aggregated interfaces - hashing type (source+destination IP)
 +
 +
 +
== MTU ==
 +
 +
MTU MSS
 
[https://www.michaelfmcnamara.com/files/Contivity%20MTU%20and%20TCP%20MSS%20clamping.pdf Article MSS/MTU]
 
[https://www.michaelfmcnamara.com/files/Contivity%20MTU%20and%20TCP%20MSS%20clamping.pdf Article MSS/MTU]
  
===Testing max MTU===
+
Testing max MTU
  
 
The important thing to remember is that an ICMP header is 8 bits so the ping test from CMD should be whatever number is your max without fragmenting PLUS 8 which gives your value for the router.
 
The important thing to remember is that an ICMP header is 8 bits so the ping test from CMD should be whatever number is your max without fragmenting PLUS 8 which gives your value for the router.
  
 
[https://www.sonicwall.com/support/knowledge-base/set-mtu-in-vpn-environment-in-case-of-throughput-issues/170705131319789/ Testing Max MTU/MSS]
 
[https://www.sonicwall.com/support/knowledge-base/set-mtu-in-vpn-environment-in-case-of-throughput-issues/170705131319789/ Testing Max MTU/MSS]

Revision as of 17:32, 23 May 2021

Not working network

  • Duplex
  • Cable
  • Firewall - disable it
  • DNS filtering - public DNS
  • ISP outage - ping its address
  • Path outage - MTR tool
  • ARP old record
  • MAC collision
  • STP loop/Broadcast storm
  • Route missing
  • LACP/PAGP must be on both ends configured
  • Zombie process and station or froze
  • Local firewall on device, or network type (windows-public)


Slow network

  • Path drop - MTR tool
  • Number of active sessions on device
  • Packet/Frame size
  • Number of ACL on device
  • Wireless is slower + wireless noise
  • Duplex
  • Cable
  • Link type overhead + MTU
  • Aggregated interfaces - hashing type (source+destination IP)


MTU

MTU MSS Article MSS/MTU

Testing max MTU

The important thing to remember is that an ICMP header is 8 bits so the ping test from CMD should be whatever number is your max without fragmenting PLUS 8 which gives your value for the router.

Testing Max MTU/MSS