NCSI Protocol Support

Computers & Servers

Network Controller Sideband Interface over MCTP/RMII

What is NCSI?

NC-SI (Network Controller Sideband Interface) is a DMTF standard that enables a baseboard management controller (BMC) to configure and manage network controllers (NICs) through a dedicated sideband channel. NC-SI can be transported over MCTP or directly over an RMII interface. The protocol handles NIC configuration commands such as enabling management traffic passthrough, setting MAC address filters, and querying link status — all without using the main network data path. Engineers debugging server network connectivity, BMC-to-NIC communication failures, and management network configuration need NC-SI decode to verify command-response exchanges and diagnose configuration errors.

NCSI Quick Reference

type Packet-based
signals MCTP or RMII
features BMC to NIC sideband management

Acute Instruments Supporting NCSI

Ready to analyze this protocol?

See how Acute instruments capture and decode this protocol in real time. Request a demo or contact our team.

How to Analyze NCSI with Acute Instruments

1

Connect your Acute logic analyzer to the NC-SI transport interface (RMII signals between BMC and NIC, or MCTP transport signals).

2

Attach a ground lead to the target board's ground reference.

3

In the Acute software, select the NCSI protocol decoder and assign the interface signals to the correct input channels.

4

Configure the decoder for the transport type (RMII or MCTP).

5

Capture and view decoded NC-SI commands and responses showing command types, channel/package IDs, and payload data.

Frequently Asked Questions

What sample rate do I need for NCSI analysis?
For NCSI over RMII, the REF_CLK is 50 MHz, requiring a sample rate of at least 200 MHz. For NCSI over MCTP, the sample rate depends on the underlying MCTP transport (SMBus or Ethernet). NC-SI commands are relatively infrequent, but the transport interface must be sampled fast enough for reliable physical-layer decoding.
Why is my BMC failing to configure the NIC over NC-SI?
NC-SI configuration failures often stem from incorrect package or channel selection, unsupported command codes for the NIC firmware version, or physical-layer connectivity issues on the sideband interface. Capture the NC-SI traffic during BMC initialization to see the command sequence and identify which command receives an error response. Verify that the NIC supports the NC-SI commands being sent and that the package/channel IDs match the hardware configuration.
How many channels are needed for NCSI analysis?
For NCSI over RMII: 6-7 channels (TXD[1:0], RXD[1:0], REF_CLK, TX_EN, CRS_DV). For NCSI over MCTP using SMBus: 2 channels (SDA, SCL). The required channel count is determined by the physical transport, not the NC-SI protocol layer itself.

Related Protocols

Need help choosing the right instrument for your protocol? Contact our engineering team.