The building LAN that carries KNXnet/IP routing also supports IP cameras, VoIP phones, PoE access points, and BMS communication. In commercial buildings, planning the network infrastructure alongside the KNX TP bus design is essential — an undersized or poorly segregated network is the most common cause of KNX IP reliability problems in large installations. Cat6A (ISO/IEC 11801 Class EA, TIA-568-C.2-1) is the correct baseline for any installation where 10G backbone switching is planned or where 60W PoE++ devices (high-power IP cameras, Gira G1 touchpanel, access control) are installed.

Why Cat6A over Cat6 for KNX

Cat6 (Class E) supports 10GBase-T at 55m maximum in unshielded form — adequate for short links but marginal for typical 90m horizontal cable runs. Cat6A (Class EA, 500MHz bandwidth, augmented) supports 10GBase-T for the full 100m channel including connectors and patch cables. For KNX projects: 10G is not typically needed for KNX traffic itself (KNXnet/IP multicast uses minimal bandwidth — 100mbit is more than sufficient). However, IP camera streams (4K H.264/H.265 at 8-15Mbit per camera), NVR writing, and BMS data all compete on the same switch uplinks. A 10G switch uplink from the floor switch to the server room aggregation switch prevents congestion that would delay KNXnet/IP routing telegrams. Additionally, Cat6A shielded (S/FTP — foil per pair + overall braid) provides better interference immunity in panel and plant rooms where variable frequency drives and high-current switching create EMI.

PoE budget planning

PoE devices in a KNX/smart building installation: Gira G1 touchpanel (802.3at PoE+, 25W), Axis P3245-V IP camera (802.3af, 12.95W), DoorBird D11x video intercom (802.3af, 7.5W), 2N IP Verso (802.3at PoE+, 30W), Ubiquiti UAP-AC-Pro access point (802.3af, 9W), Cisco IP phone (802.3af, 6.5W). Budget example for a 24-port floor switch (e.g. Ubiquiti USW-Pro-24-POE, 400W PoE budget): 8 cameras × 15W + 2 touchpanels × 25W + 2 intercoms × 30W + 6 access points × 9W = 120 + 50 + 60 + 54 = 284W. Within 400W budget — safe. For PoE++ (802.3bt Type 3, 60W) devices: check switch supports 802.3bt per port, not just 802.3at (30W). KNX IP routers (Weinzierl 770, MDT KNX IP Router): power from panel 24V DC supply — do not rely on PoE for KNX IP router (loss of network switch = loss of KNX backbone routing if PoE-powered).

VLAN design for KNX IP networks

Isolate KNX multicast traffic from general building LAN using VLANs on a managed switch. Recommended VLAN structure: VLAN 10 = KNX Automation (KNX IP routers, Gira X1, WAGO controller, BMS server) — restricted access, only specific IP ranges allowed. VLAN 20 = Security (IP cameras, NVR, access control) — isolated from KNX and building IT. VLAN 30 = Building IT (PCs, printers, ETS6 laptops) — allowed access to VLAN 10 on specific port 3671 for KNXnet/IP tunnelling. VLAN 40 = Guest WiFi — no access to KNX or security VLANs. Managed switch configuration: IGMP snooping enabled on VLAN 10 (required for KNXnet/IP multicast 224.0.23.12 to route only to KNX IP router ports, not flood all ports). QoS: mark KNXnet/IP traffic (UDP 3671) as DSCP AF41 — priority above general data, below VoIP.

Patch panel in electrical panel enclosure

For buildings where network patch panels live in the same enclosure as the KNX distribution panel (common in residential and small commercial): use a DIN-rail patch panel adapter (Belden KeyConnect, Metz Connect artLine) that mounts on standard 35mm DIN rail. Keystone patch panel: 8 or 12 port Cat6A keystones, field-terminated. Termination: T568A or T568B (consistent throughout project — never mix). Minimum bend radius for Cat6A: 4× cable outer diameter (typically 8mm cable OD = 32mm minimum bend radius). Do not crush or kink Cat6A cable when routing through cable ducts in panel — sheaths are more rigid than Cat5e. Shielded Cat6A (S/FTP): shield drain wire connected to patch panel earthing rail at ONE end only — typically at the network equipment room end, not at the field device end. This prevents ground loop currents on the shield.

Structured cabling documentation

ISO 11801 requires panel schedule (patch panel port numbers, horizontal link identifiers, room/outlet locations), test records (channel test per ANSI/TIA-568, reporting parameters: insertion loss, return loss, NEXT, PS-ANEXT for Cat6A, propagation delay), and identification labels on each patch cord and wall outlet. For KNX panels specifically: document which patch panel ports connect to KNX IP routers, which connect to cameras, and which connect to the building LAN. This is essential when troubleshooting KNX multicast routing issues — being able to identify which switch port is the KNX VLAN uplink vs a camera port eliminates guesswork during fault isolation.