Article 10 – IEC 61850 GOOSE and MMS Communication in MiCOM Relays: Network Architecture, VLAN Configuration, Multicast Communication and Troubleshooting

Table Of Contents
  1. Introduction
  2. 1. IEC 61850 Communication Architecture in MiCOM Substations
  3. 2. Differences Between GOOSE and MMS Communication
  4. 3. Understanding Ethernet Frames in IEC 61850
  5. 4. VLAN Configuration for IEC 61850 Networks
  6. 5. Ethernet Multicast Communication
  7. 6. Ethernet Switch Configuration for MiCOM GOOSE Communication
  8. 7. Network Redundancy for IEC 61850 Substations
  9. 8. GOOSE Communication Performance and Network Delay
  10. 9. Practical Example: Two MiCOM Relays Exchanging a GOOSE Signal
  11. 10. Wireshark Analysis of MiCOM IEC 61850 Communication
  12. 11. Common Network-Related Problems and Troubleshooting
  13. 12. Cybersecurity Considerations
  14. 13. Commissioning Checklist for MiCOM IEC 61850 Networks
  15. 14. Conclusion
  16. Practical MiCOM Protection and IEC 61850 Training by Dr Saeed Roostaee – Elec-Engg

Introduction

IEC 61850 communication in MiCOM protection relays depends not only on correct relay configuration but also on a properly engineered Ethernet network. Even when protection functions, datasets, GOOSE control blocks and MMS reporting are configured correctly, network problems can prevent reliable communication between Intelligent Electronic Devices (IEDs).

Two important IEC 61850 communication mechanisms are:

  • GOOSE (Generic Object-Oriented Substation Event): Used for fast peer-to-peer communication between IEDs, including protection, interlocking and breaker-related signals.
  • MMS (Manufacturing Message Specification): Used for client-server communication, including monitoring, measurements, reporting and supported control services.

Both operate over Ethernet networks but have different communication mechanisms and performance requirements.

This article explains how GOOSE and MMS communication work together in a MiCOM-based substation, how Ethernet switches and VLANs affect communication, how multicast traffic is managed, and how engineers can troubleshoot network-related problems.

Technical note: The availability and implementation of IEC 61850 communication features vary between MiCOM models, communication modules and firmware versions. Always check the relevant product documentation and supported IEC 61850 services.

1. IEC 61850 Communication Architecture in MiCOM Substations

A typical IEC 61850 substation network connects protection relays, bay control devices, station controllers, SCADA servers and engineering workstations through managed Ethernet switches.

A simplified architecture is:

                  SCADA / SAS
                       |
                 MMS Communication
                       |
                Station Ethernet
                       |
               Managed Switch
                       |
          -------------------------
          |           |           |
       MiCOM 1     MiCOM 2     MiCOM 3
       Feeder      Transformer   Busbar
       Relay       Relay         Relay
          |           |           |
          -------- GOOSE ----------
              Peer-to-peer
             Communication

The diagram illustrates the logical communication concept. The physical network may use different switch arrangements, redundant paths or separate station and process networks.

Main network components

ComponentFunction
MiCOM protection relayIEC 61850 server and, where supported, GOOSE publisher/subscriber
Managed Ethernet switchForwards Ethernet frames between network devices
SCADA serverMMS client for monitoring and supported control
Engineering workstationRelay and system configuration
Network time serverProvides time synchronization where supported
Network monitoring systemMonitors communication and network performance

The network design must consider traffic type, bandwidth, latency, availability, redundancy and cybersecurity.

2. Differences Between GOOSE and MMS Communication

GOOSE and MMS are both part of IEC 61850 communication, but they serve different purposes.

CharacteristicGOOSEMMS
Communication typePublisher/subscriberClient/server
Main applicationFast event exchangeMonitoring, reporting and control
TransportEthernet multicastTCP/IP
Typical Ethernet protocolEtherType 0x88B8MMS over TCP
TCP portNot applicable102
IP-based communicationNot required for GOOSE frame deliveryYes
Typical informationTrip, interlocking, statusMeasurements, indications, reports
Communication behaviorEvent-driven with retransmissionsClient requests and server responses, plus reporting
Network requirementPredictable low-delay deliveryReliable client-server connectivity

2.1 GOOSE communication

GOOSE messages are transmitted directly over Ethernet using multicast addressing.

A GOOSE publisher sends messages to the configured multicast destination. Subscribers connected to the relevant network receive the frames and process the required data.

GOOSE does not use TCP or UDP. Therefore, engineers should not troubleshoot it as an ordinary IP-based application.

2.2 MMS communication

MMS provides client-server communication between an IEC 61850 client and an IED server.

For example, a SCADA server may establish an MMS association with a MiCOM relay to:

  • Read data objects.
  • Discover supported information.
  • Receive reports.
  • Read measurements.
  • Receive status changes.
  • Execute supported control services.

MMS normally uses TCP port 102.

3. Understanding Ethernet Frames in IEC 61850

A good understanding of Ethernet frames helps engineers investigate communication problems.

3.1 GOOSE Ethernet frame

A GOOSE message is transmitted directly in an Ethernet frame.

Its structure includes important fields such as:

  • Destination MAC address.
  • Source MAC address.
  • VLAN information, when configured.
  • EtherType.
  • GOOSE application data.

The GOOSE EtherType is:

0x88B8

This value helps packet-analysis tools identify GOOSE traffic.

A typical GOOSE message contains fields such as:

FieldPurpose
gocbRefIdentifies the GOOSE control block
timeAllowedToLiveIndicates the expected validity interval
datSetIdentifies the dataset
goIDGOOSE identifier
tTimestamp
stNumState number
sqNumSequence number
testIndicates test-related status
confRevConfiguration revision
ndsComIndicates commissioning-related status
numDatSetEntriesNumber of dataset entries
allDataTransmitted dataset values

The actual message structure and available fields depend on the IEC 61850 implementation.

3.2 MMS communication frame

MMS communication is carried over TCP/IP.

A simplified protocol stack is:

Ethernet
   |
IP
   |
TCP
   |
RFC 1006 / TPKT
   |
ISO 8073 / COTP
   |
ACSE
   |
MMS
   |
IEC 61850 Client/Server Services

Engineers investigating MMS problems should examine both the TCP connection and the application-level MMS communication.

A successful TCP connection does not necessarily mean that the MMS association or application configuration is correct.

4. VLAN Configuration for IEC 61850 Networks

Virtual LANs (VLANs) are used to logically separate Ethernet traffic within a switched network.

In substations, VLANs can help organize communication between protection relays, SCADA servers, engineering workstations and other equipment.

For example:

VLAN IDExample purpose
VLAN 10Protection IED communication
VLAN 20SCADA and station-level communication
VLAN 30Engineering access
VLAN 40Network management

These VLAN assignments are illustrative. The actual design must follow the project’s network architecture.

4.1 Why use VLANs?

VLANs can provide:

  • Logical separation of traffic.
  • Better network organization.
  • Easier traffic management.
  • Reduced unnecessary traffic within individual VLANs.
  • A foundation for network security policies.

However, VLANs do not automatically guarantee network security or communication reliability.

4.2 VLAN tagging

IEEE 802.1Q defines VLAN tagging for Ethernet frames.

The VLAN tag contains information including:

  • VLAN identifier (VID).
  • Priority Code Point (PCP).
  • Drop Eligible Indicator (DEI).

The VLAN ID identifies the logical network, while PCP provides traffic-priority information.

For GOOSE communication, VLAN tagging and priority can be configured where supported by the relay and network design.

4.3 Practical GOOSE VLAN example

Consider two MiCOM relays exchanging a trip signal through a managed Ethernet switch.

The engineering design specifies:

  • GOOSE VLAN ID: 10.
  • GOOSE priority: 4.
  • Publisher: Feeder relay.
  • Subscriber: Busbar or interconnection relay.

The switch ports connected to the relays must be configured to handle the relevant tagged or untagged frames according to the network design.

The publisher and subscriber configurations must also agree on the communication parameters.

Important: VLAN ID and priority settings must be consistent across the relevant communication path. Incorrect tagging or switch-port configuration can prevent subscribers from receiving GOOSE messages.

5. Ethernet Multicast Communication

GOOSE uses multicast communication.

Unlike unicast communication, where a frame is sent to one destination, multicast allows a publisher to send a frame to a group of receivers.

The destination MAC address identifies the multicast group.

A typical IEC 61850 GOOSE multicast destination address belongs to the range:

01-0C-CD-01-00-00 to 01-0C-CD-01-01-FF

The exact multicast address is configured as part of the GOOSE communication engineering.

5.1 Why multicast is important

Imagine a feeder relay publishes a protection trip signal that must be received by several IEDs.

Instead of sending an individual message to every subscriber, the publisher transmits a multicast frame.

The Ethernet switches forward the frame according to their forwarding and multicast configuration.

5.2 Multicast filtering

Managed switches may use multicast filtering to control where multicast traffic is forwarded.

Depending on the switch and network configuration, filtering may involve:

  • Static multicast forwarding.
  • IGMP snooping for IP multicast.
  • Ethernet multicast filtering.
  • VLAN-based forwarding rules.

A critical distinction is that ordinary GOOSE is not IP multicast. It is Ethernet multicast.

Therefore, IGMP snooping alone should not be assumed to manage or control GOOSE traffic. Engineers must verify how the selected switch handles non-IP multicast Ethernet frames.

Incorrect multicast filtering can cause a GOOSE publisher’s frames to reach some subscribers but not others.

6. Ethernet Switch Configuration for MiCOM GOOSE Communication

The Ethernet switch is an important part of the protection communication system.

A managed switch should be configured according to the substation network design and the communication requirements of the connected IEDs.

Important settings include:

  • Port speed and duplex.
  • VLAN membership.
  • Tagged and untagged traffic handling.
  • Multicast forwarding.
  • Priority handling.
  • Port security.
  • Network monitoring.
  • Redundancy configuration, where applicable.

6.1 Port speed and duplex

The switch port and relay communication interface must negotiate a compatible Ethernet speed and duplex mode.

A speed or duplex mismatch may result in:

  • Packet loss.
  • Frame errors.
  • Poor communication performance.
  • Intermittent connectivity.

Check the switch port statistics and relay communication diagnostics.

6.2 Quality of Service (QoS)

Quality of Service allows network equipment to prioritize selected traffic.

For example, a network may prioritize GOOSE frames over less time-critical engineering or file-transfer traffic.

VLAN priority information may be used to classify traffic.

A typical design may assign a higher priority to protection-related communication than to routine network management traffic.

However, the priority values must be determined by the project network design. Engineers should not assume that a particular PCP value is universally required for every MiCOM installation.

6.3 Broadcast and multicast traffic

Unnecessary broadcast and multicast traffic can affect network performance.

The switch should be configured to forward required IEC 61850 traffic without creating excessive unnecessary traffic on unrelated ports.

Check:

  • Multicast forwarding tables.
  • Port traffic statistics.
  • Error counters.
  • VLAN configuration.
  • Traffic filtering rules.

7. Network Redundancy for IEC 61850 Substations

Substation automation systems may require high communication availability.

A single Ethernet switch or communication link can become a single point of failure if the network is not designed with redundancy.

IEC 62439-3 defines important industrial network redundancy protocols, including:

  • PRP – Parallel Redundancy Protocol.
  • HSR – High-availability Seamless Redundancy.

Whether these methods are available in a MiCOM relay depends on its hardware, firmware and supported network architecture.

7.1 PRP – Parallel Redundancy Protocol

PRP uses two independent LANs, commonly called LAN A and LAN B.

A PRP-capable device sends duplicate frames through both networks.

The receiving device accepts the first valid copy and discards the duplicate.

Advantages include:

  • Seamless communication recovery after a single network failure.
  • No need to wait for network reconfiguration before receiving the duplicate frame.
  • Increased communication availability when properly engineered.

7.2 HSR – High-availability Seamless Redundancy

HSR uses a ring topology in which nodes forward frames in both directions.

The receiving device accepts the first valid frame and discards the duplicate.

Advantages include:

  • High availability.
  • Seamless recovery from a single network path failure in a correctly engineered ring.
  • No conventional spanning-tree reconvergence delay for the redundant path.

7.3 Important compatibility considerations

Do not assume that every MiCOM relay supports PRP or HSR.

Before selecting a redundancy arrangement, verify:

  • Relay hardware capability.
  • Communication interface compatibility.
  • Firmware support.
  • Network redundancy protocol.
  • Switch or RedBox requirements.
  • Interoperability with other IEDs.

A network design should be validated using the actual installed devices, not only a generic IEC 61850 architecture diagram.

8. GOOSE Communication Performance and Network Delay

GOOSE is often used for time-critical protection and control signals.

For example, a feeder relay may publish a trip-related signal to another IED, which processes the information and performs a configured action.

The total response time depends on several elements:

  1. Protection function processing time.
  2. GOOSE message publication.
  3. Ethernet transmission.
  4. Switch forwarding.
  5. Subscriber processing.
  6. Output logic and contact operation, if applicable.
  7. Circuit breaker operating time, if the complete trip chain is being evaluated.

It is important to distinguish network transmission time from the overall protection-to-breaker operating time.

8.1 GOOSE retransmission behavior

After a dataset state change, GOOSE publishers normally transmit the updated message and then retransmit it using progressively increasing intervals until reaching a steady-state transmission interval.

Important fields include:

  • stNum: State number.
  • sqNum: Sequence number.
  • timeAllowedToLive: Supervision interval.
  • t: Timestamp associated with the state.

When the state changes, stNum increments. Retransmissions of the same state use an advancing sqNum.

This behavior helps subscribers detect state changes and supervise communication.

8.2 Network design considerations

For time-critical GOOSE communication:

  • Avoid unnecessary network congestion.
  • Use suitable switch forwarding capacity.
  • Configure VLAN and priority consistently.
  • Check multicast forwarding.
  • Monitor packet loss and frame errors.
  • Verify subscriber supervision.
  • Perform end-to-end timing tests.

The actual performance requirement must come from the protection scheme design and applicable project specifications.

9. Practical Example: Two MiCOM Relays Exchanging a GOOSE Signal

Consider a substation with two protection relays.

  • MiCOM Relay 1 protects an outgoing feeder.
  • MiCOM Relay 2 receives a GOOSE signal for a configured interlocking or protection application.

The objective is to exchange a binary signal over IEC 61850 GOOSE.

Step 1 – Configure the publisher

In the publisher relay, identify the required internal signal.

Examples could include:

  • Protection start.
  • Protection trip.
  • Breaker status.
  • Interlocking status.

Map the signal to the appropriate GOOSE dataset entry, where supported.

Step 2 – Configure the GOOSE control block

Configure the GOOSE control block using the available relay engineering facilities.

The configuration includes relevant parameters such as:

  • GOOSE control block reference.
  • Dataset reference.
  • GOOSE identifier.
  • Multicast destination MAC address.
  • VLAN ID.
  • VLAN priority.
  • Configuration revision.

The actual parameters and configuration method depend on the MiCOM model and engineering software.

Step 3 – Configure the subscriber

In the receiving relay, configure the external GOOSE reference and map it to the intended internal signal or application logic.

Where supported, the SCL engineering process may use an external reference such as ExtRef to describe the subscribed information.

Step 4 – Configure the Ethernet switch

Check that the relevant ports:

  • Belong to the correct VLAN.
  • Allow the required Ethernet frame type.
  • Forward the GOOSE multicast destination.
  • Apply the intended priority policy.

Step 5 – Test communication

Use a network analyzer to confirm that:

  • The publisher transmits GOOSE frames.
  • The destination MAC address is correct.
  • The VLAN tag is correct, if used.
  • The expected dataset is transmitted.
  • The subscriber receives the messages.
  • The intended internal signal changes state.

Step 6 – Perform end-to-end functional testing

Under an approved commissioning procedure:

  1. Apply the required test condition to the publisher.
  2. Verify the published GOOSE dataset changes.
  3. Confirm that the subscriber receives the new state.
  4. Verify the mapped internal signal.
  5. Confirm the intended output or logic response.
  6. Check communication supervision and recovery.

Never rely only on the presence of GOOSE packets in Wireshark. The receiving relay must also correctly process the required information.

10. Wireshark Analysis of MiCOM IEC 61850 Communication

Wireshark is a valuable tool for investigating IEC 61850 communication.

It can help engineers identify:

  • GOOSE messages.
  • MMS communication.
  • TCP connection problems.
  • Retransmissions.
  • Unexpected communication interruptions.
  • Incorrect destination addresses.
  • VLAN tagging problems.

10.1 GOOSE display filters

To display GOOSE traffic:

goose

To identify GOOSE Ethernet frames:

eth.type == 0x88b8

To inspect VLAN-tagged traffic:

vlan

To filter by a specific source MAC address:

eth.src == aa:bb:cc:dd:ee:ff

Replace the example MAC address with the actual address of the relay.

10.2 MMS display filters

To display MMS-related TCP traffic:

tcp.port == 102

To investigate TCP retransmissions:

tcp.analysis.retransmission

To identify TCP reset packets:

tcp.flags.reset == 1

10.3 What should engineers examine?

When analyzing GOOSE messages, check:

FieldWhat to verify
Source MACCorrect publisher
Destination MACCorrect multicast address
VLAN IDMatches network design
VLAN priorityMatches configured policy
EtherType0x88B8
gocbRefCorrect GOOSE control block
datSetCorrect dataset
stNumChanges when state changes
sqNumAdvances during retransmission
confRevMatches the intended configuration
timeAllowedToLiveAppropriate supervision information
allDataCorrect values and dataset entries

For MMS, investigate the TCP connection, association establishment, client requests, server responses and reporting behavior.

11. Common Network-Related Problems and Troubleshooting

ProblemPossible causeRecommended action
GOOSE messages are not visiblePublisher not transmitting or incorrect capture pointCheck relay configuration and capture location
Publisher messages visible but subscriber does not receive themVLAN or multicast forwarding problemCheck switch configuration and port membership
GOOSE subscriber reports communication failureIncorrect subscription or supervision problemCheck references, configuration revision and message reception
GOOSE works intermittentlyNetwork congestion or unstable linkCheck port statistics, errors and traffic load
GOOSE dataset is received but signal does not changeIncorrect mapping or application logicVerify external reference and subscriber logic
MMS association failsIP, TCP or client/server configuration problemCheck addressing, routing and TCP port 102
MMS communication is slowNetwork congestion, server load or client configurationAnalyze traffic and device diagnostics
Some IEDs receive GOOSE while others do notMulticast filtering or VLAN inconsistencyInspect forwarding tables and switch-port settings
Communication fails after switch replacementConfiguration mismatchCompare VLANs, multicast rules and QoS settings
Network redundancy does not operate as expectedUnsupported or incorrect redundancy configurationVerify device compatibility and redundancy topology

12. Cybersecurity Considerations

IEC 61850 communication networks are critical parts of substation infrastructure.

Network availability and protection communication must be considered together with cybersecurity.

Important engineering practices include:

  • Separate engineering access from operational communication where appropriate.
  • Restrict access to relay configuration interfaces.
  • Use controlled engineering workstations.
  • Apply network access controls.
  • Disable unused switch ports.
  • Monitor unexpected traffic.
  • Maintain approved firmware and configuration records.
  • Control remote access.
  • Use supported security features and protocols.
  • Maintain backups of relay and switch configurations.

IEC 62351 provides security-related standards for power system communications. However, the availability of specific IEC 62351 features depends on the device, protocol profile and firmware.

Do not assume that an IEC 61850-capable MiCOM relay automatically supports every IEC 62351 security mechanism.

13. Commissioning Checklist for MiCOM IEC 61850 Networks

Network configuration

  • Confirm the approved network architecture.
  • Verify relay IP addresses where applicable.
  • Check Ethernet port speed and duplex.
  • Confirm switch-port configuration.
  • Verify VLAN membership and tagging.
  • Check multicast forwarding.
  • Confirm QoS and priority settings.
  • Check network error counters.

GOOSE communication

  • Verify publisher configuration.
  • Verify subscriber configuration.
  • Confirm dataset references.
  • Check multicast MAC addresses.
  • Confirm VLAN ID and priority.
  • Check configuration revision.
  • Verify state-change transmission.
  • Confirm subscriber reception.
  • Test communication failure supervision.
  • Verify recovery after communication restoration.

MMS communication

  • Verify IP connectivity.
  • Check TCP port 102.
  • Establish MMS association.
  • Verify data-model access.
  • Check datasets and report control blocks.
  • Test report reception.
  • Verify measurements and status indications.
  • Confirm quality and timestamp handling.

Redundancy and cybersecurity

  • Verify supported PRP or HSR capability, if used.
  • Test the approved network failure scenarios.
  • Confirm network management access.
  • Check access-control policies.
  • Back up final switch and relay configurations.

14. Conclusion

Reliable IEC 61850 communication in MiCOM protection systems requires coordinated engineering of protection relays, Ethernet switches, VLANs, multicast forwarding, network priority and communication supervision.

GOOSE provides fast peer-to-peer event exchange, while MMS provides client-server communication for monitoring, reporting and supported control functions.

For commissioning engineers, it is important to understand that correct relay configuration alone is not sufficient. The Ethernet network must also forward the required frames correctly, and the receiving IED must process the information as intended.

A complete test should therefore verify the communication path from the publisher through the network to the subscriber, followed by confirmation of the actual protection or control application.

Practical MiCOM Protection and IEC 61850 Training by Dr Saeed Roostaee – Elec-Engg

Elec-Engg provides practical training for protection, commissioning and substation automation engineers.

Training subjects include:

  • MiCOM protection relay configuration.
  • IEC 61850 engineering and communication.
  • GOOSE publisher and subscriber configuration.
  • MMS client-server communication.
  • VLAN and Ethernet network fundamentals.
  • SCL engineering and system integration.
  • Wireshark-based communication analysis.
  • GOOSE and MMS testing and troubleshooting.
  • Practical protection and substation automation applications.

Training is available through video courses, structured self-paced training, face-to-face courses and customized in-house programs.

Visit Elec-Engg for practical power system protection and substation automation training.

Leave a Comment

Your email address will not be published. Required fields are marked *

Scroll to Top