EMAIL SUPPORT

dclessons@dclessons.com

LOCATION

NZ

LAB NSX EDGE SERVICES GATEWAY

LAB NSX EDGE SERVICES GATEWAY

Posted on Jan 17, 2020 (0)

LAB NSX Edge Service Gateway Configuration

Task:

  • Configure and deploy a new Edge Services Gateway and Configure Load Balancing on the Edge Services Gateway
  • Verify the Load Balancer's configuration and test the load balancing traffic.

Topology:

DEPLOY EDGE SERVICES GATEWAY FOR LOAD BALANCING in ONE ARM MODE

  • Click on Home icon | Click Networking & Security |Click NSX Edges | Click the Green Plus icon.

  • Enter Dclessons-OneArm-LoadBalancer as the Name | Click Next.

  • Enter XXXXXXXX as Password and confirm it again
  • Check Enable SSH access option and then click Next

Click Green Plus icon | Select RegionA01-MGMT01 as Cluster/Resource Pool.

  • Select RegionA01-ISCSI01-COMP01 as Datastore | Select esx-05a.corp.local as Host | Click

Click Next.

PLACING A NEW NETWORK INTERFACE ON THE NSX EDGE

  • Click the Green Plus icon | Dclessons-Web-Network as the Name | Select Uplink as the Type.
  • Click Select | Click Logical Switch | Click the radio button to the left of Web_Tier_Logical_Switch (5006) to select it.
  • Click OK.

CONFIGURING SUBNETS

Click Green Plus icon to configure the IP address of this interface and Click Next.

CONFIGURING THE DEFAULT GATEWAY

  • Use 172.16.10.1 as the Gateway IP | Click Next.

CONFIGURING FIREWALL AND HA OPTIONS

  • Check Configure Firewall default policy | Select Accept as the Default Traffic Policy | Click Next.

Click Finish to begin the deployment.

Configure Edge Services Gateway for Load Balancer

Once the Edge Services Gateway is deployed, we will now start configuring load balancing service on it.

When we will be able to configure the Load Balancer Services on Edge Service gateway, it will be part of existing Web_Tier_Logical_Switch and connection to its gateway will be provided by existing Perimeter-Gateway-01 ESG

Load Balancer will accept the traffic on Virtual server IP 172.16.10.10 and it will further load balance the traffic to pre-defined pool members web-01a.corp.local (172.16.10.11) and web-02a.corp.local (172.16.10.12).

CONFIGURE LOAD BALANCER FEATURE ON ONEARM-LOAD BALANCER

  • Double-click OneArm-LoadBalancer | Manage. | Load Balancer.
  • Click on Global Configuration | Edit to change Load Balancer global configuration.
  • Check Enable Load Balancer | Click OK.

CREATING A NEW APPLICATION PROFILE

  • Click Application Profiles| Click Green Plus icon.

  • Enter OneArmWeb-01 as Name | Select HTTPS as Type.
  • Check the option Enable SSL Passthrough | Click OK.

DEFINE CUSTOM HTTPS SERVICE MONITOR

  • Click Service Monitoring | Click the Green Plus to define a new Monitor.
  • Enter custom_https_monitor for Name | Select HTTPS for Type.
  • Enter /cgi-bin/app.py for URL | Click OK.

CREATE NEW POOL

  • Click Pools | Click Green Plus icon.
  • Enter Web-Tier-Pool-01 | Select default_https_monitor as the Monitors.
  • Click Green Plus icon | Enter web-01a as the Name.
  • Enter 172.16.10.11 as the IP Address / VC Container | Enter 443 for the Port.
  • Enter 443 for the Monitor Port |Click OK.

Repeat the process above to add the second pool member using the following information:

  • Name: web-02a | IP Address: 172.16.10.12 | Port: 443 | Monitor Port: 443

CREATE NEW VIRTUAL SERVER

  • Click Virtual Servers | Click Green Plus icon.
  • Enter Web-Tier-VIP-01 | Enter 172.16.10.10 as the IP Address.
  • Select HTTPS as the Protocol | Select Web-Tier-Pool-01 | Click OK.

TEST ACCESS TO VIRTUAL SERVER


Comment

    You are will be the first.

LEAVE A COMMENT

Please login here to comment.