Fibre Optic Backbone for Multi-Building KNX Networks

When fibre is required for KNX buildings

Multi-building campuses — hotels with separate guest wings and service buildings, university complexes with faculty buildings 150 to 400 metres apart, industrial estates with production buildings and an administration block — exceed the 100-metre Cat6A channel length limit in every practical scenario. Fibre optic cabling has no distance limitation within campus ranges and is the correct solution from the outset.

Beyond distance, electrical isolation is a safety-critical reason to choose fibre between buildings. Different buildings on a campus have separate electrical supplies and earth electrodes. Ground potential differences between buildings — which can be several volts under normal conditions and tens of volts during a fault — appear across any copper conductor connecting the two. A copper Ethernet cable between buildings without dedicated equipotential bonding between earth systems exposes network equipment at both ends to this ground potential difference, causing data corruption, equipment damage, and in extreme cases, electric shock risk to persons who touch network equipment during a fault.

Fibre optic cable is a dielectric — it carries no electrical current. It is completely immune to ground potential differences and provides inherent galvanic isolation between buildings. This makes fibre the standard choice for all inter-building network connections, regardless of distance.

Fibre types for campus KNX networks

Three fibre types are relevant to KNX campus installations, each with different core diameter, bandwidth, and achievable distance at 10 Gbps.

For most hotel and university campus KNX networks, where buildings are typically 50 to 200 metres apart, OM4 multimode is the cost-effective choice. OM4 SFP+ transceivers (10GBase-SR) are significantly less expensive than OS2 single-mode transceivers (10GBase-LR), and OM4 cable and termination hardware costs are lower. Where any inter-building run exceeds 400 metres, or where the campus spans a road crossing or separate site, OS2 single-mode is mandatory.

KNX IP router placement per building

The correct architecture for a multi-building KNX campus places one KNX IP router (or KNX IP interface, depending on telegram volume) in each building. Each building has its own KNX TP (twisted pair) bus serving all devices within that building. The KNX IP router in each building connects to the local building switch via a standard Cat6A patch cord, and the building switches connect to the campus core switch via OM4 fibre links.

The SFP+ transceiver modules used in building switches and the core switch must match the fibre type. For OM4: use 10GBase-SR SFP+ modules (e.g. Cisco SFP-10G-SR, Ubiquiti UF-MM-10G). For OS2: use 10GBase-LR SFP+ modules (Cisco SFP-10G-LR). Never mix OM3 transceivers on OM4 fibre — the performance parameters differ and channel tests may fail even though the link appears to be active.

Outdoor fibre cable types and installation

Inter-building outdoor fibre cables must be specified for outdoor exposure: UV resistance, moisture protection, and mechanical protection against rodents and physical damage during ground works. Two categories cover the majority of campus KNX installations.

Outdoor conduit or duct is mandatory for all inter-building routes. Direct burial without a duct is only acceptable for cables with armoured direct-burial rating and even then is inadvisable — future excavation work will damage unprotected cables. Use HDPE microduct bundles for multi-route campus infrastructures where additional fibre paths may be needed in future. Pull fibre using the Kevlar strength members — never the outer jacket or individual fibre tubes — and never exceed the rated pull force.

Termination — fusion splicing and pre-terminated cassettes

Fibre cable runs are terminated at each end by one of two methods: field termination using fusion splicing with pre-fabricated pigtails, or pre-terminated MPO trunk cassettes installed in a fibre enclosure. Each has appropriate use cases.

Field fusion splicing involves cleaving the fibre end to a flat perpendicular face, aligning it with a pre-terminated pigtail end in a fusion splicer, and melting the two ends together with an electric arc. When done correctly, fusion splice attenuation is below 0.1 dB per splice — lower than any connector interface. Fusion splicing is appropriate for long cable runs where the splice point is at a fixed building entry location (telecoms room, optical distribution frame). The splice is protected in a heat-shrink splice sleeve and stored in a splice tray inside the fibre enclosure.

Pre-terminated MPO trunk cassettes (Panduit FiberRunner, CommScope SYSTIMAX) are faster to install and more consistent in quality — no splicer is needed, and each connector is factory-tested. For KNX building telecoms rooms where time is critical and the run length is known at design stage, pre-terminated cassettes are the preferred approach. Each MPO trunk carries 12 or 24 fibres in a single pull, and the cassette converts to LC duplex ports for connection to SFP+ transceivers.

Fibre patch panel in KNX panel enclosures

Where the KNX building switch and IP router are housed in a standard electrical panel enclosure (common in residential and light commercial buildings), a DIN-rail fibre enclosure provides termination for the building's incoming fibre link. Manufacturers including Metz Connect, Telegärtner, and R&M produce DIN-rail fibre enclosures mounting on 35 mm DIN rail, housing 6 or 12 LC duplex adapters with integral splice tray or cassette bay.

The incoming outdoor fibre enters the panel through a conduit connector with IP protection — the transition from outdoor to indoor environment must be weather-sealed at the panel entry. The fibre cable's strength members are clamped at the cable entry point so that tension on the outdoor cable is not transmitted to the fibre terminations inside the enclosure.

Minimum bend radius for OM4 fibre is 40 mm under loaded conditions (during installation with tension) and 30 mm for long-term storage bends. Excess fibre inside the enclosure must be stored in loops of at least 60 mm radius in the fibre storage compartment. Never allow fibre to be kinked or bent below the minimum radius — unlike Cat6A, fibre damage from overbending is permanent and the degraded attenuation may not cause an immediate link failure but will reduce the power margin to zero, making the link unreliable at temperature extremes.

Testing — OLTS and OTDR per IEC 14763-3

Fibre testing for installed cabling follows IEC 14763-3 (testing of optical fibre cabling). Two types of test are required: optical loss test set (OLTS) measurement of total insertion loss, and OTDR (optical time domain reflectometer) trace for event location.

Test both directions for each link (end A to end B, and end B to end A) — connectors and splices have slightly different loss in each direction due to fibre geometry at the joint. Record the worst result for each link as the acceptance value. IEC 14763-3 Class B1 permanent link limits must be met. Retain all test reports in the building documentation folder alongside Cat6A channel test reports.

KNXnet/IP multicast routing across buildings

KNX IP routers in each building communicate by sending KNXnet/IP routing telegrams as IP multicast to group address 224.0.23.12 on UDP port 3671. For this to work across the campus fibre backbone, the core switch must correctly handle multicast forwarding between buildings.

The simplest approach for most KNX campus installations is to place all buildings in the same KNX VLAN (VLAN 10) as a single Layer 2 domain. In this configuration, IGMP snooping on the core switch learns which building switch ports have KNX IP routers (multicast group members) and forwards KNXnet/IP multicast only to those ports. The IGMP querier on the core switch sends periodic membership queries; KNX IP routers respond with IGMP join reports to maintain group membership. No routing protocol is needed — all buildings are in the same broadcast domain.

For larger campuses where each building has its own IP subnet (different VLAN per building), KNXnet/IP multicast must be routed between VLANs at Layer 3. Protocol Independent Multicast — Sparse Mode (PIM-SM) configured on the core switch (which must be a Layer 3 switch with multicast routing capability) forwards KNXnet/IP group 224.0.23.12 between VLANs. A Rendezvous Point (RP) must be designated for this multicast group. In most KNX campus scenarios, this complexity is unnecessary — a single KNX VLAN spanning all buildings via the fibre backbone simplifies commissioning significantly.