|
Size: 316
Comment:
|
Size: 2467
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 2: | Line 2: |
| <<TableOfContents()>> | |
| Line 13: | Line 14: |
== Troubshooting Process == === Defining the problems === i. Identifying symptoms i. Gathering information i. Identify recent Changes === Identifying the cause of the problem === i. Identify possible causes i. Determining the root cause i. Test possible causes of the problem === Implementing the resolution === i. Identify possible solutions i. Implementing the best solution i. Verify the resolution i. Document the resolution === Separation Of Transport and Services === i. Test physical connectivity between the hosts 'Virtual Tunneling EndPoints(VTEPs)' i. Ensure that is an adequately MTU end-to-end. (MTU minimum size is 1550 in NSX environment) i. Ensure that the proper VXLAN port is configured for use. i. Ensure that no Firewall is disallowing VXLAN communications Service Separation Routing, Firmwalling, SLB, NAT, DNS, DHCP, VPNs, Deep Packet Inspection... Page 12 Twelve === Determining NSX Services Involved === i. NSX Manager Configuration missing on an NSX endpoint or device may indicate a management communication failure. Or use of NSX Manager for Identify Firewall and failure to properly log in or disallow a login may indicate.( Misconfiguration in Security Policy, Communication failure in accessing LDAP services from AD) i. Control Plane Dependencies Control Plane Method (Unicast, Hybrid, Multicast) i. Security Services employed DFW i. Advanced Services Of Edge Services Gateway. {{{ Load Balancing settings of failures VPN(IPSec, L2VPN tunnels)communications links ESG routing or firewall services ETC.. }}} === Troubshoot the NSX Logical Switching === i. Ensure proper functioning of NSX Managerment and Control Plane communication. i. For Logical Switching Communication, begin checking the following == Troubshoot NSX Logical Routing Overview == If VXLAN communication involves logical routing and logical switching elements and the infrastructure services have been checked. i. For VXLAN to VXLAN endpoint communication i. For VXLAN to VLAN endpoint communication involving Edge Service Gateway |
Contents
NSX Training Day 1
infrastructure
Defining a System Problem
- Problems can arise from numerous sources, which include:
- Configuration issues
- Resource contention
- Network attacks
- Software bugs
- Hardware failures
- Poor or untested designs
Troubshooting Process
Defining the problems
- Identifying symptoms
- Gathering information
- Identify recent Changes
Identifying the cause of the problem
- Identify possible causes
- Determining the root cause
- Test possible causes of the problem
Implementing the resolution
- Identify possible solutions
- Implementing the best solution
- Verify the resolution
- Document the resolution
Separation Of Transport and Services
Test physical connectivity between the hosts 'Virtual Tunneling EndPoints(VTEPs)'
- Ensure that is an adequately MTU end-to-end. (MTU minimum size is 1550 in NSX environment)
- Ensure that the proper VXLAN port is configured for use.
- Ensure that no Firewall is disallowing VXLAN communications Service Separation Routing, Firmwalling, SLB, NAT, DNS, DHCP, VPNs, Deep Packet Inspection... Page 12 Twelve
Determining NSX Services Involved
- NSX Manager
- Configuration missing on an NSX endpoint or device may indicate a management communication failure. Or use of NSX Manager for Identify Firewall and failure to properly log in or disallow a login may indicate.( Misconfiguration in Security Policy, Communication failure in accessing LDAP services from AD)
- Control Plane Dependencies Control Plane Method (Unicast, Hybrid, Multicast)
- Security Services employed DFW
- Advanced Services Of Edge Services Gateway.
Load Balancing settings of failures VPN(IPSec, L2VPN tunnels)communications links ESG routing or firewall services ETC..
Troubshoot the NSX Logical Switching
- Ensure proper functioning of NSX Managerment and Control Plane communication.
- For Logical Switching Communication, begin checking the following
Troubshoot NSX Logical Routing Overview
If VXLAN communication involves logical routing and logical switching elements and the infrastructure services have been checked.
- For VXLAN to VXLAN endpoint communication
- For VXLAN to VLAN endpoint communication involving Edge Service Gateway