> For the complete documentation index, see [llms.txt](https://www.opal-rt.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.opal-rt.com/docs/rt-lab/configure-ios/communication-protocol-ios/iec-61850-8-1-mms/connect-the-hardware.md).

# Connect the Hardware

## Connect devices using standard Ethernet cables <a href="#connectdevicesusingstandardethernetcables" id="connectdevicesusingstandardethernetcables"></a>

IEC 61850‑8‑1 MMS communication operates over **TCP/IP**, using client/server sessions between IEDs and the simulator. Devices exchange MMS messages through reliable, connection‑oriented communication, and the simulator uses its built‑in Ethernet interfaces to host multiple MMS servers or connect as an MMS client. To establish communication between IEDs and the simulator, interconnect them using standard Ethernet cables, ensuring they share the same physical network, switch, and IP subnet as defined in the SCL or project configuration.

## Set IP addresses and subnets

Because MMS relies on **TCP/IP**, correct IP configuration is essential for establishing stable client/server sessions. Each IED and each simulator‑hosted IED model must have a properly assigned IP address matching the values defined in the SCL/SCD/ICD file.

* All MMS clients and servers must be on the same IP subnet unless routing is explicitly configured.\
  MMS uses TCP port 102, so communication across subnets is possible only if L3 routing allows it.
* Each physical device must have a unique IP address to avoid conflicts on the Ethernet network.
* Multiple logical MMS servers may share the same IP address only if they are hosted within the same physical device, typically differentiated by:
  * Different MMS associations
  * Different AP‑titles and AE‑qualifiers (Application Process identifiers)
  * Different VMD (Virtual Manufacturing Device) structures\
    This is common in simulators where multiple virtual IEDs are hosted on one NIC using IP aliasing.
* Static IP addresses are strongly recommended for protection, SCADA, and engineering‑access MMS traffic.

Example of valid MMS subnet configuration:

* SCADA / MMS Client: `192.168.20.10 / 255.255.255.0`
* IED 1 – MMS Server: `192.168.20.11 / 255.255.255.0`
* IED 2 – MMS Server: `192.168.20.12 / 255.255.255.0`
* Simulator-hosted IED: `192.168.20.50 / 255.255.255.0`

## Set the TCP port <a href="#tcpportusage" id="tcpportusage"></a>

MMS typically operates over **TCP port 102**, as defined by IEC 61850‑8‑1.\
Ensure that:

* TCP port 102 is not blocked by firewalls or VLAN ACLs.
* No other application on the same interface conflicts with the port.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://www.opal-rt.com/docs/rt-lab/configure-ios/communication-protocol-ios/iec-61850-8-1-mms/connect-the-hardware.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
