The municipal ISP handoff is a VLAN on the Edge uplinks. Where does the operator attach the county Tier-0 to that VLAN toward the ISP?
Select an answer to reveal the explanation.
Short Explanation
The ISP is the city's driveway onto the public road. You bolt the Tier-0 to that VLAN with an external/uplink interface on a VLAN-backed segment—not with a DFW exclusion.
Full Explanation
The municipal ISP handoff as a VLAN on Edge uplinks is attached by adding an external/uplink interface on the county Tier-0 that uses a VLAN-backed segment toward the ISP. Operators configure that under Networking > Tier-0 Gateway so north-south routing has a Layer-3 interface on the ISP VLAN—the civic curb cut to the provider. Distributed Firewall exclusion lists are not how T0 uplinks are built; exclusions remove VMs from DFW enforcement. Inventory > Groups nesting cannot represent an ISP uplink adjacency. Saving a Traceflow drawing is diagnostics, not uplink configuration. Exam caveat: the uplink VLAN segment, Edge uplink teaming, and Tier-0 interface must agree on VLAN ID and MTU or BGP/static routing to the ISP will fail even when the Tier-0 object exists. Operational check: create/confirm the VLAN segment for the ISP handoff, add the Tier-0 external interface on the Edge cluster, verify link/protocol state, and ping or BGP-establish per county WAN runbook; record interface IPs and VLAN in the ISP circuit folder. After the uplink is up, verify routing toward the ISP next hop and that return traffic for county public services uses the intended Tier-0 path; update the ISP handoff diagram with segment name and Edge uplink labels.