📘

Labels separated into WAN and LAN

Recommend “Starter” labels. (any WAN label can apply to any WAN interface and LAN to any LAN interface; however, symmetry is easier to manage!)

1. Keep names short for readability.
2. Use all CAPS so they stand out.

Label examples

📘

WAN Labels can override MESH BIO and function only as Hub and Spoke by selecting the option when creating the label. This is useful for CG-NAT circuits in a MESH environment. See BIO section for information.

👍

WAN Labels build tunnels between WAN labels according to Business Intent Overlays configuration, covered later.

LAN labels are currently just identify lan side interfaces and subinterfaces.

LAN labels can be use to ID interfaces for use in firewall rules and other areas of Orch.

For example a "Guest" network that has a different VLAN at location. Using a LAN label "GUEST" can quickly reference all these interfaces. Simplifying Rules.

There are a couple way to approach labels

1. Set all labels the same at both HUB/data center and remote/branch locations.
   1. Requires less labels
   2. Requires a few cross connections in the BIO
   3. Looses readability in charts
   4. 2nd and 3rd circuits remote/branch will still require their own label and cross connection
   5. IPSEC and encryption settings are easier
2. Define labels for Each HUB/Data center connection and each Branch interface.
   1. Requires more labels
   2. Requires a lot of BIO cross connections
   3. Helps Chart readability
   4. IPSEC and encryption setting take more time to change
   5. Increases total tunnel count

❗️

Each Edge Connect, Including Edge HA pairs, can only have one of each WAN label. If you put the same label on two interfaces, deployment will not allow save or an alarm is raised and tunnels will not build.

🚧

After creating a new WAN label you must return to Tunnel Settings and configure the label settings.