1672 Allow connection Server and ServerAt to the same SCL.Subnetwork
Created: 17 Feb 2020
Part: Part 6 (2019; Edition 2.1)
Paragraph: Below Table 50
Issue: it is not allowed to connect multiple Access Point of a Server to the same subnetwork.
The restriction has been identified during the last Interop TEst as being to restrictive and lead to interoperability problems.
Proposal: During the TC57WG10 Meeting in Golden, it was decided to remove the restriction as follow:
- define a new Service Capability to indicate that multiple APs of a server can be connected to the same subnetwork,
- the SCT shall provide the apRef while configuring GOOSE, SMV, and Report subscription.
- the IP address asignement by the SCT shall be careful, as using IP addresses in the same IP network for different ConnectedAP of a server may lead to communication problem with OS like Windows, Linux.
Note: To see attachments you have to log-in first.
Imagine the following configuration:
A server has 2 AccessPont P1, and P2. The following IP configuration is made: the 2 aacess point have IP addresses in the same IP subnetwork:
An IP stack in the server will have problem to answer to IP telegram over the correct access point / ethernet controller.
The problem exists today, even when the 2 ConnectedAP are NOT connected onto the same SCL.SubNetwork.
Therefore, the IP address configuration shall ensure that ConnectedAPs of the same Server does not get IP addresses in the same IP subnetwork.
is a correct IP configuration.
P1 is member of IP subnetwork 192.168.1 while
P2 is member of IP subnetwork 192.168.2
The proposal includes:
the IP address assignment by the SCT shall be careful, and not assign IP addresses in the same IP subnetwork to ConnectedAP of an IED.
(here regardless of Server / Client - restricution applies to ConnectedAP).
|25 Feb 20
Privacy | Contact | Disclaimer
Tissue DB v. 18.104.22.168