Support #527
Regarding the Network infrastructure: Some MU/SAMU cannot configure their SV stream to different VLAN ID , fixed to 0 (but can c
0%
To be discussed in between 8-1 and 9-2 editors
(20180613)
For GOOSE and SV, configurability of VLAN is stated in 8-1 Ed2.1. Standard 61850-9-2 shall also provide mandatory configurability of VLAN for SV (it shall refer to 8-1 Ed2.1). In the product standard for MU (61869-9) it is stated that VID parameter configuration range is from 0-4095 i.e. it is configurable.
Update Testing Procedures. Send to user feedback TF for further discussion. Solution must consider Layer 3 multicast.
19-01-23: (B. Muschlitz) Layer 3 is not considered by UCA TF because it is decided to test according to 61869-9 that is not taking into account R-SV (yet)
For GOOSE and SV, configurability of VLAN is stated into (wait for Vladan notes)... Standard shall provide configurability of VLAN for SV (it shall refer to 8-1 Ed2.1 is not stated in 9-2). For GOOSE it is stated in 8-1 Ed2.1. In the product standard for MU (61869-9) it is stated that VID parameter configuration range is from 0-4095 i.e. it is configurable.
Update Testing Procedures. Send to user feedback TF for further discussion.
Solution must consider Layer 3 multicast.
Description
Regarding the Network infrastructure:
Some MU/SAMU cannot configure their SV stream to different VLAN ID , fixed to 0 (but can configure Priority)
Some MU/SAMU only send SV without VLAN tag
Should we state that each SV publisher have to be configurable in terms of VLAN to fit every project needs (every infrastructure network)?
Should we be able to declare it in the capabilities of the device (send VLAN tag, configure this VLAN tag (ID, priority) )?
Switches in general don’t have the same way (by default) to handle VLAN 0 tagged packets. Two different switches implementation on substation 1 setup has to handle the problem in 2 different ways. Is it suitable?
(Same for GOOSE)
Updated by Carlos Rodriguez del Castillo almost 2 years ago
- Status changed from New to Closed
Confirm to IEC 61850-6 editor that this issue has been accounted for.