RMC (Rack Management Controller) in ORv3

Posted on by lechuck park

RMC (Rack Management Controller) Features in ORv3

This image is an infographic that intuitively explains the five key functions of the RMC (Rack Management Controller) defined in the Open Compute Project (OCP) Open Rack v3 (ORv3) specification. Each function is categorized into a color-coded row, featuring a representative icon and title on the left, paired with a detailed description on the right.

1. Integrated Power Resource Management & Control

  • Icon: A gear with a power plug and a lightning bolt.
  • Detailed Description: This function controls multiple PSUs (Power Supply Units) and BBUs (Battery Backup Units) housed within the Power Shelf. It manages Active Current Sharing in N+1 or N+N redundancy configurations to ensure the load is balanced evenly across operational power supplies. This optimizes power efficiency and reliability.

2. Dynamic Load Balancing & Peak Shaving

  • Icon: A gear with a wave graph.
  • Detailed Description: When transient power spikes (pulse loads) occur—a common characteristic of AI workloads—the RMC can instantly engage the BBUs to suppress peak power demand, preventing AC grid overload. Note that ORv3 BBUs typically discharge within milliseconds if the Vbus voltage drops below a specific threshold, such as 48.5V.

3. Out-of-Band (OOB) Network Communication

  • Icon: A metering device with multiple cable connections.
  • Detailed Description: It connects directly to the Top-of-Rack (ToR) or management switch via a 10/100/1000Base-T Ethernet port to communicate with unified management platforms (AIOps). Utilizing PoE (Power over Ethernet), the RMC remains active and continues to report telemetry even if the main 48V/50V busbar power drops entirely, ensuring high availability of management functions.

4. Standardized Protocol Support

  • Icon: A clipboard with a checklist and a gear.
  • Detailed Description: The RMC natively supports DMTF Redfish APIs and Modbus. This enables consistent telemetry collection, automation, and remote control across heterogeneous hardware environments, facilitating interoperability in multi-vendor data centers.

5. Liquid Cooling Integration (Optional)

  • Icon: A gear shaped like a cooling system with piping and a fan.
  • Detailed Description: This optional feature interfaces with sensors from a CDU (Coolant Distribution Unit) or rack manifolds to monitor heat dissipation. This facilitates synchronized control logic between the cooling and power delivery infrastructures for holistic rack management.

Summary

This image illustrates the five core values of the RMC, a critical component of the OCP ORv3 standard rack. The RMC provides essential capabilities for advanced data center infrastructure management, including maximizing power efficiency, handling sudden power spikes typical of AI workloads, and maintaining management operations via PoE even during main power failures. Additionally, it addresses the complex demands of modern data centers through standardized protocol support and optional integration with liquid cooling systems.

#OCP #OpenComputeProject #ORv3 #RMC #RackManagementController #DataCenter #PowerManagement #PeakShaving #LiquidCooling #AIOps #Redfish

With Gemini

Network : Road to the peer

Posted on by lechuck park

The provided image is a diagram that visually explains the roles and addressing schemes used by the lower four layers (L1 to L4) of a network model during data communication. Here is a detailed breakdown of each layer shown in the image:

  • L4 (Transport Layer):
    • A purple line illustrates the logical end-to-end connection between Applications on the source and destination servers.
    • It uses TCP/UDP Port numbers to identify the specific application receiving the data, handling “Application Data Transferring.”
  • L3 (Network Layer):
    • A blue line represents the logical connection from the source host to the destination host across the network.
    • It utilizes the IP Address, where intermediate routers perform routing to find the best path to the destination (“Route By Dest IP Address”).
  • L2 (Data Link Layer):
    • A light blue line demonstrates node-to-node communication between directly connected devices (e.g., a server and a switch).
    • It uses the MAC Address for local delivery, ensuring the destination MAC address matches the device’s own hardware address (“MAC Address Matching with my one”).
  • L1 (Physical Layer):
    • This layer depicts the conversion between digital information and physical transmission mediums.
    • It shows how binary data (“01 00 data”) is translated into electrical, light, or radio waveforms (“signal”) and vice versa (“Binary <-> Signal”) over cables or wireless antennas.

đź“ť Summary

This image is an excellent educational visualization that breaks down how data travels across network devices (servers, switches, routers). It intuitively maps out the specific protocols and addressing systems applied at each level: L1 (Physical Signals) -> L2 (MAC Addresses) -> L3 (IP Addresses) -> L4 (Port Numbers).This image is an excellent educational visualization that breaks down how data travels across network devices (servers, switches, routers). It intuitively maps out the specific protocols and addressing systems applied at each level: L1 (Physical Signals) -> L2 (MAC Addresses) -> L3 (IP Addresses) -> L4 (Port Numbers).

#NetworkLayer #OSIModel #NetworkingBasics #L1toL4 #DataCommunication #TCPIP #ITInfrastructure

With Gemini

Data Center Protocols(3)

Posted on by lechuck park

The provided image is a table categorizing the dominant interfaces and protocols used by various infrastructure equipment within a data center to transmit and receive data. The data sources can be explained by dividing them into four main functional tiers:

  • IT & AI Core Infrastructure (GPU / server):
    • This is the core source for AI racks, generating the largest point count of data.
    • It predominantly uses Ethernet (dedicated BMC network). The legacy IPMI protocol is actively being retired, making way for the modern Redfish protocol.
  • Cooling Systems (CDU, Rear-door HX, Chiller, etc.):
    • CDUs (Cooling Distribution Units) managing Direct Liquid Cooling (DLC) loops handle high-frequency flow, pressure differentials ($\Delta$P), and supply temperatures. They primarily use Ethernet-based Modbus TCP or BACnet/IP.
    • Chillers and cooling towers are currently undergoing a migration to the more secure BACnet/SC (TLS).
  • Power Infrastructure (UPS, Smart PDU, Switchgear, BESS, etc.):
    • While UPS and PDUs rely on Ethernet, they internally or optionally retain serial buses like RS-485. They utilize a mix of protocols including SNMPv3, Modbus TCP, and Redfish.
    • High-voltage switchgear and gensets require highly synchronized timing (SNTP/PTP) and utilize utility-grade protocols like IEC 61850 and DNP3.
  • Environment & Safety (Rack environmental, Safety chain):
    • Environmental retrofit sensors often utilize RS-485 or LoRaWAN to maintain IP economics.
    • Critical safety chains (EPO, leak detection, fire) deliberately use out-of-band, hardwired DI/DO (dry contacts) to ensure foolproof operation independent of network status.

đź’ˇ Direction for Data Collection Improvement in AI Data Centers (AI DC)

While traditional data center protocols are tuned for standard monitoring intervals, the AI DC environment—characterized by high-density GPU servers and liquid cooling architectures—mandates a shift toward ultra-precise and ultra-high-frequency data collection.

AI workloads create massive and sudden spikes in power draw and thermal output. Even a brief delay (Time Constant) in data collection can lead to thermal runaway. Therefore, to ensure practical and stable operations, edge gateways must be upgraded and polling mechanisms for Redfish and Modbus TCP must be optimized to collect telemetry (flow rates, temperatures, power data) between CDUs and GPU servers at millisecond-level frequencies.

đź“ť Summary

This table illustrates that while Ethernet has become the dominant physical interface across data center infrastructure, the application-layer protocols (Redfish, Modbus, BACnet, hardwired connections) remain highly fragmented depending on the equipment’s specific function (power, cooling, safety). As facilities evolve into AI Data Centers, driving standardization and securing the capability for real-time, ultra-precise data collection—especially around GPUs and liquid cooling systems—has emerged as an urgent operational necessity.This table illustrates that while Ethernet has become the dominant physical interface across data center infrastructure, the application-layer protocols (Redfish, Modbus, BACnet, hardwired connections) remain highly fragmented depending on the equipment’s specific function (power, cooling, safety). As facilities evolve into AI Data Centers, driving standardization and securing the capability for real-time, ultra-precise data collection—especially around GPUs and liquid cooling systems—has emerged as an urgent operational necessity.

#DataCenter #AIDC #Protocols #HighFrequencyTelemetry #LiquidCooling #Redfish #Modbus #InfrastructureOptimization

With Gemini

Data Center Protocols (2, Application Layer )

Posted on by lechuck park

The image is a structured chart titled “Data Center Protocols (2, Application Layer)”. It categorizes various communication protocols used within a data center into three main operational paradigms based on their purpose and characteristics. The chart outlines the protocol name, communication method, data format/security, and typical use cases for each category.

Key Categories and Descriptions

1. Device-Centric This section covers traditional, hardware-specific protocols used for direct communication with physical infrastructure equipment. The primary communication paradigm here is ‘Polling’ (master/slave or with events).

  • Modbus RTU/TCP: Used for UPS, PDU, and power meters. It uses raw registers with no typing and lacks built-in security.
  • BACnet IP-MS-TP-SC: An object-oriented protocol used for Chillers, CRAH, cooling towers, and BMS (Building Management Systems).
  • SNMP v2c/v3: Utilized for Smart PDUs, environmental sensors, and network gear, relying on a MIB (OID tree) structure.
  • Redfish (replaces IPMI): Designed for Server BMC, power, and thermal management using REST polling and JSON schemas.
  • DNP3 / IEC 61850: Used for switchgear, HV substations, and gensets, featuring time-stamped event reporting.

2. Data-Centric This area focuses on protocols designed to collect, route, and distribute large volumes of sensor and telemetry data. These protocols primarily utilize the ‘Publish/Subscribe (Pub/Sub)’ mechanism.

  • MQTT (+Sparkplug B): Ideal for high-volume telemetry and monitoring liquid-cooling flow & temperature, featuring free payloads (with models added by Sparkplug).
  • OPC UA: Used for heterogeneous normalization and gateway-to-DCIM communication, offering a semantic info model and built-in security.
  • Kafka (optional): Acts as a central ingestion bus for stream logs, providing partitioning, retention, and SASL-TLS security.

3. Integration-Centric This tier deals with protocols meant for linking high-level application systems, web services, and user interfaces.

  • REST API (JSON): The standard request/response method used for DCIM integration and generating tenant power reports over HTTPs.
  • gRPC: Based on HTTP/2 and Protobuf, it enforces schemas and is used for internal Microservices Architecture (MSA), AI, and RAG pipelines.
  • WebSocket / Webhook: Provides persistent duplex communication and event callbacks, perfect for live dashboards and real-time fault alerting.

đź’ˇ Summary

The chart illustrates that modern data center communication is strategically divided into three architectural layers: hardware control (Device-Centric), massive data ingestion and routing (Data-Centric), and high-level system connectivity (Integration-Centric). Each layer employs specifically optimized protocols to meet its distinct requirements for speed, payload structure, and security.The chart illustrates that modern data center communication is strategically divided into three architectural layers: hardware control (Device-Centric), massive data ingestion and routing (Data-Centric), and high-level system connectivity (Integration-Centric). Each layer employs specifically optimized protocols to meet its distinct requirements for speed, payload structure, and security.

#DataCenter #NetworkProtocols #InfrastructureManagement #DCIM #ServerEngineering #IoT #SystemsIntegration

With Gemini