To Connect to an Existing Network that exists outside of your VergeIO system, an External Network must be created in VergeIO. Typically, at least one External Network is created during VergeIO Installation (setup to be used for UI access.) If the External Network was not created during installation or additional Layer 2 access points (different vlan / vxlan IDs) are needed to the same physical network, you will want to create an External Network from the VergeIO UI. The following instructions walk through creation of an External Network.
With Layer 3 routing enabled
- Navigate to Networks from the Main Dashboard.
- Click New External on the left menu.
- Enter a Name for the new network. (Name should be something helpful for future administration.)
- Optionally, a Description can be added for the new Network, to record additional information.
- Optionally, a HA Group can be defined for the Network. When two or more networks have been configured with the same HA Group (same entry in this field), the system will always attempt to run the different networks on different hosts to provide an extra Layer of high availability.
- Select appropriate Layer 2 Type:
- vLAN - unique ID specified in Layer 2 ID field
- vxLAN - unique ID be specified in Layer 2 ID field.
- Bond* - supports switch port configured for lag group -active / main physical device
- Bond Slave* - supports switch configured for lag group -secondary device
- None -simple direct connect
NOTE: Bond/Bond Slave options are typically configured during initial VergeIO installation. These are highly advanced configurations; please consult VergeIO Support for assistance.
- Enter a Layer 2 ID, if applicable (vLAN / vxLAN)
- Enter appropriate MTU size for the network.
- Optionally, a specific Cluster can be selected to specify the primary VergeIO cluster where the Network will run.
- Optionally, a specific VergeIO Failover Cluster can be selected to specify a VergeIO Cluster on which the Network should run if the primary Cluster is not available.
- Optionally, a Preferred node can be selected to specify a particular Node (physical or Tenant) as a “first-choice” on which to run the network.
- PXE boot is set to none by default. VergeOS can be selected to provide PXE booting from this network.
- Select appropriate Interface Network from the dropdown list of External and Physical Networks.
NOTE: Selecting another External Network (rather than a physical Network) would be for scenarios to use Q-in-Q (vlans inside a vlan transport). Physical Networks are typically created during install (External Switch, External 1 Switch, etc.)
- Select appropriate IP Address Type:
- Static - to specify a particular address for the network
- Dynamic - to configure this network as a DHCP client.
NOTE: this is only used in small, test-type situations as it will be limited to a single IP address.
3. BGP / OSPF
NOTE: These instructions deal with creating an External Layer 3 network. To create the network as Layer 2 only, select “None” for IP Address Type. You will see that selecting “None” takes away all the Layer 3 configuration options, such as DHCP, DNS, vnet IP address, route limiting, etc.
- For BGP networks only: enter appropriate ASN.
- Enter IP Address for the vnet router. (Does not apply if IP Address Type=Dynamic selected above.)
- Enter the CIDR Network Address for the network, ex: 192.168.0.0/24
- Specify a DNS server list.
- Select a DNS setting:
- Disabled - no DNS management.
- Bind - select for networks that will act as authoritative DNS for a name space.
- Simple - DNS provided to the network, but holds no actual DNS records.
- Optionally, the DHCP (checkbox) option can be selected to run a DHCP server. When selected, Network DHCP configuration options become visible:
- Domain name for this network (optional)
- Gateway
- Hostname for this network
- Dynamic DHCP option (checkbox) - if selected, DHCP start / stop Addresses can be entered to specify a scope of addresses for dynamic allocation. Additionally, DHCP Sequential Addresses can be selected to allocate dynamic addresses in a consecutive manner.
- Select a setting for On Power Loss
- Power On - network will be powered on when power is restored (regardless of its state at time of power loss)
- Last State - network will only be powered on if it was on at the time of power loss.
- Leave Off - network will not be powered on when power is restored (regardless of its state at time of power loss)
- Optionally, the following options (checkboxes) can be selected:
- Track Statistics for All Rules to automatically turn on tracking for all Rules applied to this network.
- Track DMZ Statistics to track total packets / bytes from this network through the DMZ network.
- Enable Rate Limiting on Routing to define limits on this overall network. (Example usage: consumption-based billing, etc.)
1. Rate Limit - enter an integer
1. Rate Type - Packets per second, Megabytes per day, Bytes per Hour, etc.
1. Rate Limit Burst - allow this burst rate as long as the rate limit is staying within averages defined.
Need more Help? Email support@verge.io or call us at (855) 855-8300