Create and Manage Edge Router Policies

This article applies to NetFoundry networks version 7 or higher.  Refer to Finding Your Network Version for detailed information on determining your Network Version. 


This guide goes over the specifics of creating and managing Edge Router Policies in the web console.  An Edge Router Policy configures connections for Endpoints. Endpoints use Edge Routers to connect. 

To use an Edge Router Policy you will need a NetFoundry network, an Endpoint, and an Edge Router. You may go back to create those first if necessary:

Create Your Edge Router Policy

To create an Edge Router Policy, navigate to Edge Routers  Edge Router Policies to get the process started. Click the blue plus sign in the upper right corner to create a new Edge Router Policy. 


On the 'Create a New Edge Router Policy' screen, you'll see options for name and attributes, along with a preview of your Endpoints and Edge Routers. A unique name is needed to create an Edge Router Policy. Next, either select from your list of already created attributes or create a new one. If you have attributes already created, you'll need to click on the field to populate the list of attributes to choose from. When creating a new one, hit 'return' or 'enter' to populate the attribute. 

To the right of those options, you'll see a preview of your Edge Routers and Endpoints that are associated with the attributes you've created or selected.


Manage Your Edge Router Policy 

To manage your existing Edge Router Policy, navigate to Edge Routers and switch over to Edge Router Policies. You can click on an Edge Router Policy row to edit it or use the ellipsis menu at the end of each row to take actions on the individual Edge Router Policy. Use the select bubbles in the first column of the table to select multiple Edge Routers for bulk deletion


When editing an existing Edge Router Policy, the screen will look the same as the 'Create a New Edge Router Policy' screen, except that you'll click 'Update' to finish editing instead of create. 

Was this article helpful?
0 out of 0 found this helpful



Article is closed for comments.