Skip to main content

Create a transit router

A transit router is a router exclusively dedicated to moving traffic between other routers to build the secure backbone of your network fabric.

It's important to note that all routers in the network are transit routers by default, which is why they include the Allow traversal flag. This guide walks you through creating a new router entry and configuring it to perform this function.

Steps​

  1. From the console, select your network from the dropdown in the left-hand menu.

  2. Click Routers from the same menu.

  3. Click the Transit Routers tab.

  4. Click the plus icon (+) to open the Create New Transit Router form.

  5. Enter a Edge Router Name (e.g., us-central-fabric-node).

  6. Configure the transit router details:

    • Cost: Enter a numeric value that influences the network's smart routing decisions. A lower cost makes this router more preferred for transit traffic. The default is 0.
    • Enabled: Ensure this toggle is set to YES to activate the transit router on the network fabric.
    • Allow traversal: Ensure this toggle is set to YES. This allows the transit router to use network address translation (NAT) to communicate with other components in the fabric, even if it's behind a firewall or network boundary.

  7. Toggle the Show more options switch to ON to configure advanced and optional settings.

  8. Click Save to create the transit router.

API calls panel​

When you create a resource, the console automatically builds the API request that the platform sends in the background. The API calls panel shows that request in JSON. The panel is read-only.

This panel lets you see the exact payload the controller receives when you create the resource. It's the same JSON you'd send if you were automating resource creation through the API.

The URL at the top of the panel is the API endpoint that receives the request.

Advanced options​

The advanced options control the transit router's specific behavior within the data plane fabric.

Custom tags​

Use Name and Value fields to attach any custom key–value tags to the transit router. Tags let you store metadata that's meaningful to your organization or automation tooling. They're optional and don't affect routing or access unless you build logic around them.

App data​

App data lets you attach arbitrary JSON that your applications or automation might use. This isn't used by the platform itself; it's simply a freeform JSON object that travels with the transit router identity.

If you don't have a specific use case, you can leave this as {}.