> 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-9-2-sv/connect-the-hardware.md).

# Connect the Hardware

## Connect devices using standard Ethernet cables

IEC 61850‑8‑1 GOOSE communication **operates directly over Layer‑2 Ethernet**. Devices exchange GOOSE messages using multicast Ethernet frames, and the simulator uses its built‑in Ethernet interfaces to publish and subscribe to these messages. To establish communication between IEDs and the simulator, simply interconnect them using **standard Ethernet cables**, ensuring they share the same physical network or switch.

## **Configure VLANs, priorities, and network domains**

Because GOOSE is **not based on IP** and does **not require IP addressing**, network reliability depends on proper Ethernet‑level configuration:

### **VLAN and Priority Settings**

* GOOSE messages should be assigned to a **dedicated VLAN** to ensure isolation and predictability.
* IEEE 802.1Q **VLAN tagging** and **802.1p priority tagging** must be configured according to the SCL file.
* Typical priority values follow UCA recommendations (e.g., **priority ≥ 4** for protection‑class traffic).

### **GOOSE Multicast MAC Address**

Each GOOSE Control Block transmits using a standardized multicast MAC address range:

```
01‑0C‑CD‑01‑00‑XX
```

## **Select the correct network interface**

To publish or subscribe to GOOSE messages:

* Choose the simulator’s Ethernet interface connected to the **GOOSE VLAN**.
* This interface will send and receive the multicast frames defined in the SCL/SCD/ICD file.
* Multiple devices can receive the same GOOSE stream simultaneously, as multicast allows **one‑to‑many** communication.

## **Example of valid GOOSE network configuration**

A typical setup may look like this:

```
Switch VLAN 100 (GOOSE)
 ├── Simulator Ethernet Port (VLAN 100)
 ├── IED 1 – Publishing Trips (VLAN 100)
 ├── IED 2 – Subscribing to Trips (VLAN 100)
 └── IED 3 – Interlocking Logic (VLAN 100)
```

Key points:

* All devices are connected to the **same VLAN**.
* No IP addressing is required for GOOSE messaging.
* Each IED publishes or subscribes to the multicast MAC address defined in the GOOSE Control Block.

Multiple GOOSE publishers can operate on the same VLAN without conflict, as each dataset uses its own multicast MAC address and APPID.


---

# 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-9-2-sv/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.
