VMware NSX Advanced Load Balancer: Global Server Load Balancing Design and Deploy — Lesson 3: Load-balancing algorithms, geo databases, topology policies, persistence, TTL, fallback, application health, maintenance, site weighting, and traffic steering

Learning Objectives

• Identify the architecture and operational choices that shape Load-balancing algorithms, geo databases, topology policies, persistence, TTL, fallback, application health, maintenance, site weighting, and traffic steering.
• Run normal and boundary tests and record the outcome in traffic-steering test matrix and DNS-response capture.
• Separate root cause from symptom when investigating a long TTL delaying client movement away from an unavailable site.

Detailed Topics

• Load-balancing algorithms
• Geo databases
• Topology policies
• Persistence
• TTL
• Fallback
• Application health
• Maintenance
• Site weighting
• And traffic steering
• Decision ownership, prerequisites, and acceptance evidence for Load-balancing algorithms, geo databases, topology policies, persistence, TTL, fallback, application health, maintenance, site weighting, and traffic steering
• Relevant access, security, capacity, dependency, performance, recovery, and support considerations

Instructor Demonstration

The demonstration traces Load-balancing algorithms, geo databases, topology policies, persistence, TTL, fallback, application health, maintenance, site weighting, and traffic steering from requirement through execution and review. Learners see where evidence should be collected, how traffic-steering test matrix and DNS-response capture supports validation, and which warning signs require investigation.

Hands-On Exercise

Build or execute Load-balancing algorithms, geo databases, topology policies, persistence, TTL, fallback, application health, maintenance, site weighting, and traffic steering for a defined scenario. Introduce the condition “a long TTL delaying client movement away from an unavailable site,” inspect the evidence, correct the cause without discarding the audit trail, and document the accepted state in traffic-steering test matrix and DNS-response capture.

1. Confirm scope, access, sample workloads, and acceptance criteria.
2. Perform the configuration or operation using a controlled sequence.
3. Inspect outputs and downstream effects rather than relying on task status alone.
4. Close with a support note, preventive action, and reproducible validation step.

Scenario Analysis

• Clarify the service trigger, affected components and roles, prerequisites, and acceptable result for Load-balancing algorithms, geo databases, topology policies, persistence, TTL, fallback, application health, maintenance, site weighting, and traffic steering.
• Compare at least two implementation or correction choices and identify which evidence would distinguish them.
• Decide how traffic-steering test matrix and DNS-response capture should be reviewed, approved, retained, and handed to the next owner.

Troubleshooting Guidance

Diagnose Load-balancing algorithms, geo databases, topology policies, persistence, TTL, fallback, application health, maintenance, site weighting, and traffic steering by checking effective state, ownership, dependencies, health, logs, and recent changes. Use traffic-steering test matrix and DNS-response capture to locate the earliest divergence. Treat “a long TTL delaying client movement away from an unavailable site” as a hypothesis until the same test passes after correction and under a boundary condition.

Validation Checklist

• The requirement for Load-balancing algorithms, geo databases, topology policies, persistence, TTL, fallback, application health, maintenance, site weighting, and traffic steering is linked to an owner and observable acceptance condition.
• Traffic-steering test matrix and dns-response capture contains enough detail for another practitioner to repeat the check.
• Normal operation, one boundary condition, and the identified failure path have been tested.
• Access, security, downstream impact, rollback, monitoring, and support ownership are recorded.

Lesson Outcome

Learners can apply Load-balancing algorithms, geo databases, topology policies, persistence, TTL, fallback, application health, maintenance, site weighting, and traffic steering, explain the decisions made, and defend the result with traffic-steering test matrix and DNS-response capture.