Differences between revisions 1 and 10 (spanning 9 versions)
⇤ ← Revision 1 as of 2016-11-14 01:54:25 →
Size: 316
Editor: localhost
Comment:
← Revision 10 as of 2016-11-14 02:59:15 → ⇥
Size: 1899
Editor: localhost
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 the is an adequately MTU end-to-end. (MTU minimum size is 1550 in NSX environment)
 i. Ensure the 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
 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

  1. NSX Training Day 1
    1. infrastructure
    2. Defining a System Problem
    3. Troubshooting Process
      1. Defining the problems
      2. Identifying the cause of the problem
      3. Implementing the resolution
      4. Separation Of Transport and Services
      5. Determining NSX Services Involved

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

  1. Identifying symptoms
  2. Gathering information
  3. Identify recent Changes

Identifying the cause of the problem

  1. Identify possible causes
  2. Determining the root cause
  3. Test possible causes of the problem

Implementing the resolution

  1. Identify possible solutions
  2. Implementing the best solution
  3. Verify the resolution
  4. Document the resolution

Separation Of Transport and Services

  1. Test physical connectivity between the hosts 'Virtual Tunneling EndPoints(VTEPs)'

  2. Ensure the is an adequately MTU end-to-end. (MTU minimum size is 1550 in NSX environment)
  3. Ensure the the proper VXLAN port is configured for use.
  4. 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

  1. 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)
  2. Control Plane Dependencies
  3. Security Services employed
  4. Advanced Services Of Edge Services Gateway. 

  Load Balancing settings of failures
  VPN(IPSec, L2VPN tunnels)communications links
  ESG routing or firewall services
  ETC..

首頁/2016-11-14 (last edited 2016-11-29 03:03:45 by merlyn)