|
Size: 1284
Comment:
|
Size: 1586
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 40: | Line 40: |
| === Involve | === Determining NSX Services Involved === i. NSX Manager i. Control Plane Dependencies i. Security Services employed i. Advanced Services Of Edge Services Gateway. {{{ Load Balancing settings of failures VPN(IPSec, L2VPN tunnels)communications links ESG routing or firewall services ETC.. }}} |
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 the is an adequately MTU end-to-end. (MTU minimum size is 1550 in NSX environment)
- Ensure the 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
- Control Plane Dependencies
- Security Services employed
- Advanced Services Of Edge Services Gateway.
Load Balancing settings of failures VPN(IPSec, L2VPN tunnels)communications links ESG routing or firewall services ETC..