Differences between revisions 9 and 21 (spanning 12 versions)
⇤ ← Revision 9 as of 2016-11-14 02:58:40 →
Size: 1897
Editor: localhost
Comment:
← Revision 21 as of 2016-11-29 03:03:45 → ⇥
Size: 3648
Editor: merlyn
Comment:
Deletions are marked like this. Additions are marked like this.
Line 4: Line 4:
== Class Files ==
 http://tinyurl.com/z8eg7uu

 http://tinyurl.com/hzb5bmp

= lab information =
 i. vCenter 172.20.10.94
Line 34: Line 42:
 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 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.
Line 45: Line 53:
 Control Plane Method (Unicast, Hybrid, Multicast)
Line 46: Line 55:
 DFW
Line 53: Line 63:

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

== NSX for vSphere Infrastructure Preparation Steps ==
  I. Deploy NSX Manager
  Deplay the NSX Manager Open Virtualization Appliance(OVA) file
  I. Register with vCenter Server
  One-to-one relationship NSX MGR - vCenter
  I. Deploy Controllers
  Deploy controller appliances
  Configure IP pool settings
  I. Prepare Hosts
{{{
    Install VIBs for VXLAN, DFW, DLR on all hosts in cluster
    Configures RMQ based messaging infrastructure
    Enable firewall
}}}


== NSX-v Preparation Steps - Connect NSX Manager to vCenter ==
 i. show running config
 i. show arp/ip route
 i. show manager log follow
 i. mgr# debug packet display interface mgmt port 443
 i. ESXi_host# esxcli network ip connnection list | grep 5471
 i. ESXi_host# esxcfg-advcfg -g /UserVars/RmqIpAddress
 i. ESXi_host# esxcli network ip connnection list | grep 1234

== NSX-v Preparation Steps - Deploy NSX Controllers ==

== Important Port Numbers ==
 i. VXLAN UDP port number used is 8372.
 i. Port 80 to be open from NSX Manager to the hosts.

Contents

  1. NSX Training Day 1
    1. Class Files
  2. lab information
    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
    5. NSX for vSphere Infrastructure Preparation Steps
    6. NSX-v Preparation Steps - Connect NSX Manager to vCenter
    7. NSX-v Preparation Steps - Deploy NSX Controllers
    8. Important Port Numbers

NSX Training Day 1

Class Files

lab information

  1. vCenter 172.20.10.94

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 that is an adequately MTU end-to-end. (MTU minimum size is 1550 in NSX environment)
  3. Ensure that 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

NSX for vSphere Infrastructure Preparation Steps

  1. Deploy NSX Manager Deplay the NSX Manager Open Virtualization Appliance(OVA) file
  2. Register with vCenter Server One-to-one relationship NSX MGR - vCenter
  3. Deploy Controllers Deploy controller appliances Configure IP pool settings
  4. Prepare Hosts 

    Install VIBs for VXLAN, DFW, DLR on all hosts in cluster
    Configures RMQ based messaging infrastructure
    Enable firewall

NSX-v Preparation Steps - Connect NSX Manager to vCenter

  1. show running config
  2. show arp/ip route
  3. show manager log follow
  4. mgr# debug packet display interface mgmt port 443
  5. ESXi_host# esxcli network ip connnection list | grep 5471

  6. ESXi_host# esxcfg-advcfg -g /UserVars/RmqIpAddress

  7. ESXi_host# esxcli network ip connnection list | grep 1234

NSX-v Preparation Steps - Deploy NSX Controllers

Important Port Numbers

  1. VXLAN UDP port number used is 8372.
  2. Port 80 to be open from NSX Manager to the hosts.

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