Servers Australia colocation services are provisioned with two physical network switch ports by default.
Each port is configured independently as an access port and is assigned to the public VLAN associated with the customer's service. The two ports are not bonded, aggregated, or configured for automatic failover by default.
The provision of two switch ports should therefore not be interpreted as providing an automatically redundant network connection. Customers must implement an appropriate network design if they intend to use both ports.
Connecting both ports incorrectly can create a Layer 2 loop, MAC address instability, or Spanning Tree Protocol (STP) issues that may affect the customer's service and other services connected to the same network infrastructure.
Default Switch Port Behaviour
Customer-facing colocation switch ports are configured as independent edge access ports.
Key characteristics include:
Each port is configured independently in access mode
Both ports are normally assigned to the same customer public VLAN
The ports are not bonded or aggregated by default
No automatic failover occurs between the two ports
Ports operate as edge ports and do not participate in customer spanning tree domains
Spanning Tree Protocol (STP) control traffic is filtered on customer-facing interfaces
Discovery protocols such as CDP and LLDP are disabled
Broadcast storm control is enabled to protect the wider network
Because both ports provide access to the same Layer 2 network, customers must ensure that their equipment does not create a Layer 2 forwarding path between the two ports unless an approved link aggregation configuration has been provisioned.
Supported Configurations
Customers intending to connect both provided network ports must use an appropriate network design. The following configurations are supported.
Option 1: Connect Each Port to a Separate Device
Each switch port may be connected to a separate customer device, such as separate firewalls, routers, or servers.
In this configuration:
Each Servers Australia switch port terminates on a different customer device
The customer must ensure there is no Layer 2 bridging path between the two external interfaces
Any failover, clustering, routing, or redundancy mechanism is implemented and managed by the customer
Simply connecting the ports to separate devices does not by itself provide automatic network failover. The customer's equipment and network design must provide the required redundancy.
Examples may include appropriately configured firewall clusters, routers using Layer 3 routing, or other designs that prevent a Layer 2 loop between the two connections.
Option 2: Request a Bonded LACP Connection
Customers who require both physical ports to operate as a single logical connection may request a Link Aggregation Group (LAG) using Link Aggregation Control Protocol (LACP).
In this configuration:
Both physical ports operate as a single logical interface
LACP is configured on the customer device
LACP is configured on Servers Australia network equipment
Important notes:
LACP is not enabled by default
Configuration of LACP on Servers Australia network equipment is a billable service and may incur additional costs
Customers must contact Servers Australia Support to request LACP configuration before connecting both ports as an aggregated interface
LACP is the supported method for operating both provided ports concurrently as a single logical connection to one customer device.
Option 3: Use a Routed Layer 3 Design
Customers may use a routed Layer 3 design where public IP addressing is configured directly on routing-capable customer equipment.
In this configuration:
Public IP addressing is configured on the appropriate customer network interface
Traffic is routed rather than bridged between the provided network connections
No Layer 2 forwarding path exists between the two Servers Australia switch ports
Customers using both ports as part of a Layer 3 design must ensure their routing and interface configuration is appropriate for multiple connections to the same public network.
If you are unsure whether your proposed Layer 3 configuration is suitable, contact Servers Australia Support before connecting both ports.
Unsupported Configurations
The following configurations are not supported and may result in service disruption:
Connecting both provided ports to the same device as independent Layer 2 interfaces without LACP
Bridging the two provided ports together on customer equipment
Creating a Layer 2 forwarding path between the two ports through switches, firewalls, virtual switches, hypervisors, or other customer equipment
Assuming that the two default switch ports provide automatic failover or link redundancy
Relying on customer-side STP to prevent a loop between the two Servers Australia switch ports
These configurations can result in Layer 2 loops, MAC address instability, or other network behaviour that may affect both the customer's service and the wider network.
About Spanning Tree Protocol (STP)
Customers may use Spanning Tree Protocol within their own network where appropriate.
However:
Servers Australia colocation switch ports do not participate in customer STP domains
STP control traffic is filtered on customer-facing switch ports
STP must not be relied upon to prevent a loop between the two provided switch ports
STP is therefore not a supported method for providing redundancy between the two default colocation network connections.
Responsibility and Support
Customers are responsible for the configuration and operation of their own network equipment.
Before connecting both provided switch ports, customers should ensure that their network design does not create a Layer 2 loop and that any required redundancy, failover, routing, or link aggregation functionality has been correctly configured.
If you are unsure how the two ports should be connected for your environment, please contact Servers Australia Support before connecting the second port.
Summary
Servers Australia provides two independent network switch ports with colocation services by default.
These ports:
Are active access-mode ports on the customer's public VLAN
Are not bonded or aggregated by default
Do not provide automatic failover or redundancy by themselves
Customers intending to use both ports must use a suitable design, such as:
Connecting the ports to separate devices with appropriate customer-managed redundancy and no Layer 2 bridging between the connections
Requesting an LACP bonded connection from Servers Australia, for which additional charges apply
Implementing an appropriate routed Layer 3 design with no Layer 2 forwarding path between the two connections
Do not connect both default switch ports to the same device as independent Layer 2 interfaces.
If you are unsure of the correct configuration, contact Servers Australia Support before connecting both ports.