VMware NSX: Introduction to Routing and Switching — Lesson 3: Tier-0 and tier-1 gateways, connected routes, static routes, route advertisement, BGP concepts, edge nodes, north-south paths, and service routing

Learning Objectives

• Identify the architecture and operational choices that shape Tier-0 and tier-1 gateways, connected routes, static routes, route advertisement, BGP concepts, edge nodes, north-south paths, and service routing.
• Run normal and boundary tests and record the outcome in logical routing diagram and route-table validation.
• Separate root cause from symptom when investigating a connected segment remaining unreachable because its route is not advertised upstream.

Detailed Topics

• Tier-0 and tier-1 gateways
• Connected routes
• Static routes
• Route advertisement
• BGP concepts
• Edge nodes
• North-south paths
• And service routing
• Decision ownership, prerequisites, and acceptance evidence for Tier-0 and tier-1 gateways, connected routes, static routes, route advertisement, BGP concepts, edge nodes, north-south paths, and service routing
• Relevant access, security, capacity, dependency, performance, recovery, and support considerations

Instructor Demonstration

The demonstration traces Tier-0 and tier-1 gateways, connected routes, static routes, route advertisement, BGP concepts, edge nodes, north-south paths, and service routing from requirement through execution and review. Learners see where evidence should be collected, how logical routing diagram and route-table validation supports validation, and which warning signs require investigation.

Hands-On Exercise

Build or execute Tier-0 and tier-1 gateways, connected routes, static routes, route advertisement, BGP concepts, edge nodes, north-south paths, and service routing for a defined scenario. Introduce the condition “a connected segment remaining unreachable because its route is not advertised upstream,” inspect the evidence, correct the cause without discarding the audit trail, and document the accepted state in logical routing diagram and route-table validation.

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 Tier-0 and tier-1 gateways, connected routes, static routes, route advertisement, BGP concepts, edge nodes, north-south paths, and service routing.
• Compare at least two implementation or correction choices and identify which evidence would distinguish them.
• Decide how logical routing diagram and route-table validation should be reviewed, approved, retained, and handed to the next owner.

Troubleshooting Guidance

Diagnose Tier-0 and tier-1 gateways, connected routes, static routes, route advertisement, BGP concepts, edge nodes, north-south paths, and service routing by checking effective state, ownership, dependencies, health, logs, and recent changes. Use logical routing diagram and route-table validation to locate the earliest divergence. Treat “a connected segment remaining unreachable because its route is not advertised upstream” as a hypothesis until the same test passes after correction and under a boundary condition.

Validation Checklist

• The requirement for Tier-0 and tier-1 gateways, connected routes, static routes, route advertisement, BGP concepts, edge nodes, north-south paths, and service routing is linked to an owner and observable acceptance condition.
• Logical routing diagram and route-table validation 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 Tier-0 and tier-1 gateways, connected routes, static routes, route advertisement, BGP concepts, edge nodes, north-south paths, and service routing, explain the decisions made, and defend the result with logical routing diagram and route-table validation.