Differences between revisions 10 and 11
⇤ ← Revision 10 as of 2016-11-14 02:59:15 →
Size: 1899
Editor: localhost
Comment:
← Revision 11 as of 2016-11-14 03:05:30 → ⇥
Size: 2465
Editor: localhost
Comment:
Deletions are marked like this. Additions are marked like this.
Line 43: Line 43:
Line 46: Line 45:
 Control Plane Method (Unicast, Hybrid, Multicast)
Line 47: Line 47:
 DFW
Line 54: Line 55:

=== 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

  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
      6. Troubshoot the NSX Logical Switching
    4. Troubshoot NSX Logical Routing Overview

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 Control Plane Method (Unicast, Hybrid, Multicast)
  3. Security Services employed DFW
  4. 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

  1. Ensure proper functioning of NSX Managerment and Control Plane communication.
  2. 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.

  1. For VXLAN to VXLAN endpoint communication
  2. For VXLAN to VLAN endpoint communication involving Edge Service Gateway

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