IEC 11518-6-02: High-Performance Parallel Interface – Physical Switch Control (HIPPI-SC) Standard

The IEC 11518-6-02 standard, formally designated as ISO/IEC 11518-6:2002 (and adopted as CAN/CSA-ISO/IEC 11518-6-02), defines the Physical Switch Control (HIPPI-SC) protocol for High-Performance Parallel Interface (HIPPI) networks. This article provides a technical examination of its scope, key requirements, implementation aspects, and compliance considerations.

Scope and Application

HIPPI-SC specifies the control protocol for managing crosspoint switches within a HIPPI fabric. It is designed to operate with both the HIPPI-800 (800 Mbit/s) and HIPPI-6400 (6.4 Gbit/s) physical layers, enabling connection-oriented communication in high-performance computing environments. The standard covers connection setup, teardown, status reporting, switch configuration, and error recovery. Typical deployments include supercomputer clusters, mass storage systems, and real-time data acquisition networks where deterministic low-latency switching is critical.

The scope explicitly excludes the physical-level signal specifications and instead focuses on the logical control interface between the host adapters (source/destination) and the switch controller, as well as inter-controller communication for multi-stage switch fabrics.

Technical Requirements and Architecture

The HIPPI-SC architecture is built around a connection-oriented model. The switch fabric is composed of crosspoint elements that establish direct data paths between source and destination ports upon command from a switch controller. The controller communicates with host interfaces using a dedicated set of Protocol Data Units (PDUs).

Addressing and Connection Management

Each endpoint is identified by a 12-bit source address and a 12-bit destination address, allowing addressing of up to 4096 ports per switch domain. Connection management is performed through a request–confirm handshake that ensures only one data path is established at a time. The standard defines several mandatory commands:

Control Message Format

All switch control PDUs are encapsulated in standard HIPPI packets. The PDU header includes fields for destination address, source address, command code, sequence number, and length. Payload fields vary by command but typically contain status words, timing parameters, and routing information. A critical requirement is that the packet must be delivered within the specified time window to meet the connection setup latency budget.

Timing and Synchronization

The standard mandates a set of timing constants, such as T_CONNECT (maximal time to establish a connection), T_DISCONNECT (time to tear down), and T_STATUS (status polling interval). These values are derived from the underlying HIPPI electrical characteristics and guarantee that the switch behaves deterministically over high-speed parallel links.

Implementation Highlights

Implementing HIPPI-SC requires careful integration of the control logic with the switch fabric hardware. Key considerations include:

• Physical layer dependency: The control PDUs must be compatible with the data transmission rate and framing of the underlying HIPPI variant (800 Mbit/s or 6.4 Gbit/s).
• Switch controller processing: The controller must be able to process Connect Requests within the T_CONNECT window, which often necessitates dedicated hardware finite state machines rather than purely software implementations.
• Buffer management: Each switch port must maintain pending connection request queues and proper resource allocation to avoid head-of-line blocking.
• Scalability: For fabrics larger than a single switch, inter-controller communication must follow the cascade protocol defined in the standard, which extends the addressing scheme.

Compliance and Conformance Testing

Compliance with IEC 11518-6-02 is established by verifying that a device meets the requirements of the HIPPI-SC protocol. The conformance tests cover:

• Protocol validation: Each command and response sequence is checked against the state machine tables in the standard.
• Timing conformance: Critical path times (T_CONNECT, T_DISCONNECT) are measured under worst-case load conditions.
• Address mapping: Routing tables must correctly map logical addresses to physical ports without errors.
• Negative testing: Devices must gracefully handle invalid commands, unexpected PDUs, and link failures.

The standard itself is identical to ANSI NCITS 304-1998, and most conformance tests used in industry were originally developed by the High-Performance Parallel Interface Working Group (X3T11, later INCITS T11). Formal certification may be obtained through accredited testing laboratories, though many vendors rely on self-certification with documented test results.

© 2026 International Electrotechnical Commission — Reference article for educational purposes. Always refer to the latest version of the standard for official requirements.