KVM-over-IP

The size depends on the number of end devices, meaning the total of computer and console modules:

• ControlCenter-IP-XS — up to 50 end devices, licences fully included
• ControlCenter-IP — up to 600 end devices
• ControlCenter-IP-Max — up to 2,500 end devices

System capacity is unlocked via licenses, with one license per device. The central modules come with 20 licenses, and add-ons are available in packages ranging from 10 to 500—even retroactively. This means you pay for the installation you’re actually running, not for the maximum possible capacity.

When DirectRedundancyShield is used, the maximum number of end devices is reduced.

At minimum, a layer-2 managed switch with Gigabit Ethernet supporting QoS, VLAN, multicast, IGMP as well as IGMP snooping and snooping querier. Performance matters just as much: forwarding and switching bandwidth and the uplink must suit the installation, particularly where several network switches are involved. Up to 100 m over CAT applies between two active network components.

The full requirements are in the data sheet "Network requirements KVM over IP". Settle this point before selecting modules — it determines how the installation behaves in service.

All communication is permanently encrypted: AES256-GCM for keyboard, mouse and control data, AES128-CTR for video, audio, GenericUSB and serial data. Bootloader, operating system and firmware form a trusted computing platform whose integrity is verified at every system start; an integrated trusted platform module protects access and configuration data.

At user level, rights management, configurable password policies and integration with Active Directory, Radius or LDAP are available. The end devices themselves store no login credentials — if a module is lost, nothing can be read from it.

Two-factor authentication and the SecureCert feature for compliance with FIPS 140-3, DoDIN APL and Common Criteria EAL2+ are available as options.

At the end device: the 2C and 2F variants use link aggregation across two transmission channels.

At the central module: two internal power supplies and two network interfaces.

At system level: DirectRedundancyShield keeps every module connected to an active and a passive matrix at the same time; if the primary connection drops, the passive one takes over seamlessly and with no delay in the picture. MatrixGuard automatically connects the modules to another matrix switch in the event of a fault and restores the switching states. Both functions require an additional matrix switch with the corresponding licences.

And if the central module itself fails: the console and computer modules connect directly in extender mode. The workplace stays operable, even without switching.

Selected computer and console modules can be powered via Power over Ethernet. At the workplace, that removes the power supply — one cable covers transmission and power.

In the IP world, every module transmits compressed, predominantly via bluedec™: pixel-perfect and with no perceptible latency, at efficient bandwidth. Uncompressed variants do not exist here — they would not be compatible with a standard network.

IP modules work with IP central modules. Dedicated end devices cannot be integrated into an IP matrix system, and vice versa. Within the IP world, mix & match applies across all signal types: DisplayPort, DVI, HDMI and USB Type-C operate on the same system.

Virtual machines are integrated via the RemoteAccess-IP-CPU, appearing like physical computers.

High-speed USB 2.0 is brought into the matrix by the U2-LAN. Note that MatrixGuard cannot be combined with U2-LAN devices.

Operating and control functions such as TS-Function with CrossDisplay switching and FreeSeating, Push-Get for control room collaboration, or the IP-Control API for scenario control are listed under KVM features.

• How many licences do I need?
  One per end device, so one per computer and one per console module. The central modules include a base package that can be extended later.
• Is my existing network switch sufficient?
  Layer-2 management, Gigabit Ethernet, QoS and VLAN are required as a minimum. Simple unmanaged switches are not enough.
• Can I keep using existing dedicated modules?
  No, an IP matrix system requires IP end devices. An existing dedicated setup, on the other hand, can be expanded into a matrix system by adding a dedicated central module — without having to replace the end devices.
• Do I need a second central module for redundancy?
  Not for transmission redundancy — modules with link aggregation cover that. DirectRedundancyShield and MatrixGuard, however, require an additional matrix switch with the corresponding licences.
• Can it run on my production network?
  It can, but it needs planning. A dedicated VLAN or a separate network segment for KVM traffic is the usual approach.