0007930: Parallel redundancy support for non-transparent and transparent server support

ID	Project	Category	View Status	Date Submitted	Last Update

0007930	10000-004: Services	Spec	public	2022-04-12 09:32	2022-04-12 18:39

Reporter	Hock, Christian	Assigned To	Jim Luth
Priority	high	Severity	major	Reproducibility	always
Status	closed	Resolution	no change required
Product Version	1.04
Target Version	?.??

Summary	0007930: Parallel redundancy support for non-transparent and transparent server support
Description	Support of both profiles in parallel: a. https://reference.opcfoundation.org/v104/Core/docs/Part7/6.6.47/ b. https://reference.opcfoundation.org/v104/Core/docs/Part7/6.6.46/ Problem: • There already exists below the "Server" object (ns=0;i=2253) an object "„ServerRedundancy“ (ns=0;i=2296) with the mandatory property „RedundancySupport“ (ns=0;i=3709) from OPC Foundation NodeSet. • If you want to model both possibilities it is not clear which value should be used for this property „RedundancySupport“ (ns=0;i=3709), because when you create instances from „NonTransparentRedundancyType“ (ns=0;i=2039) and/or „TransparentRedundancyType“ (ns=0;i=2036) this property - because it is mandatory - also exists --> which makes sense. See also "Upload Files" below.
Tags	No tags attached.
Attached Files	ParallelSupportOfRedundancy.JPG (29,416 bytes) ParallelSupportOfRedundancy.JPG (29,416 bytes)

Commit Version
Fix Due Date

Date Modified	Username	Field	Change
2022-04-12 09:32	Hock, Christian	New Issue
2022-04-12 09:32	Hock, Christian	File Added: ParallelSupportOfRedundancy.JPG
2022-04-12 18:39	Jim Luth	Assigned To	=> Jim Luth
2022-04-12 18:39	Jim Luth	Status	new => closed
2022-04-12 18:39	Jim Luth	Resolution	open => no change required
2022-04-12 18:39	Jim Luth	Note Added: 0016579

Jim Luth 2022-04-12 18:39 administrator ~0016579	We discussed in UA call today and agreed to close with no-fix: Although a Server may expose multiple endpoints, each endpoint exposed will only use s single redundancy scheme. So what is exposed to a Client from the Server Object would need to be dynamically changed based on which endpoint a Client used to connect.