NSX Training Day 1

Class Files

• http://tinyurl.com/z8eg7uu

  http://tinyurl.com/hzb5bmp

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.