An extension of an existing departmental network to another building is described by the University as an annexe. This allows staff and systems in both locations to operate as if they are connected to the same local network.
An annexe is delivered using a Layer 2 Virtual Private Network (L2VPN), sometimes referred to as a pseudowire. In practical terms, this provides a virtual network link between buildings.
What this means for users
The network switch in the annexe building is connected back to the department’s main network switch so that:
- Devices in the annexe are part of the same network as those in the main building
- Existing network access controls and services apply in both locations
- No changes are required to how users connect to the network
For staff and end users, the network operates in the same way regardless of which building they are working in.
How the connection works
At a high level:
- The University core network carries traffic securely between buildings
- A dedicated virtual connection links the two network switches
- Network traffic is passed between locations without modification, maintaining the existing network structure
This approach avoids the need for separate physical cabling between buildings while maintaining a consistent network environment.
Why this approach is used
Annexe connections are used to:
- Provide a consistent network experience across multiple locations
- Avoid duplication or redesign of existing departmental services
- Enable efficient deployment using established University network standards
- Allow central management and support by the Network Team
Scope and limitations
This connection provides:
- An extension of an existing departmental network
- A managed and supported service delivered by the University
- A standard solution used across the University estate
This connection does not provide:
- A separate or standalone network
- An internet-only or guest network service
- An extension of LIN networks
Reliability and support
Annexe connections are monitored as part of the wider University network. Any faults or issues are managed by the Network Operations Team in line with standard operational processes.
Where required, resilience and capacity requirements are considered during the design stage.
When an annexe is appropriate
An annexe connection may be suitable where:
- A department operates across more than one building
- The same systems and services must be accessible in all locations
- A seamless and consistent network experience is required
