View Issue Details

IDProjectCategoryView StatusLast Update
000310510000-005: Information ModelSpecpublic2023-05-09 15:15
ReporterNathan PocockAssigned ToJeff Harding  
PrioritynormalSeverityminorReproducibilityhave not tried
Status closedResolutionfixed 
Product Version1.03 
Target Version1.05.03 RC1Fixed in Version1.05.03 RC1 
Summary0003105: NonTransparent Hot+PM: Increase information about redundant servers
Description

CMPWG/UAWG Jun-30-2015:

6.3.9 NonTransparentRedundancyType
The call today described adding an OPTIONAL parameter to contain the serviceLevel of the redundant servers. This will allow a client to connect to one Hot+PM Server to conduct normal OPC activities as well as monitoring the status of the redundant servers.

With this fix in place, it will eliminate the need for the Client to establish a connection to the redundant servers to poll (read on a timer) the service level.

Additional Information

Jun-30-2015 Phone Discussion Notes:

  • UA Part 4 will likely need some modifications in section 6.4.2.4.5.5 (HotPlusMirrored).

  • UA Part 7 will need new Conformance Units added for redundancy

  • Possibly release this update in an errata to expedite the release, and to NOT wait for inclusion in UA 1.04.

TagsNo tags attached.
Commit Version
Fix Due Date

Relationships

related to 0008733 closedJeff Harding 10000-005: Information Model Current non-transparent redundancy specifications do not work for a primary/standby set of Servers 
related to 0008951 closedRandy Armstrong NodeSets, XSDs and Generated Code NonTransparent Hot+PM: Increase information about redundant servers 

Activities

Jim Luth

2022-09-27 17:02

administrator   ~0017864

Last edited: 2022-09-27 17:04

Add this for mirrored servers in the list where each mirror is listed. Needs to be optional.

Jeff Harding

2023-04-11 16:57

developer   ~0019164

Added RedudantServerArray as optional to NonTransparentRedundancyType

Jim Luth

2023-05-09 15:15

administrator   ~0019293

Agreed to changes edited in Web meeting. Cloned to Nodeset.

Issue History

Date Modified Username Field Change
2015-06-30 15:36 Nathan Pocock New Issue
2015-07-09 19:32 Jim Luth Target Version => 1.04
2015-07-09 19:33 Jim Luth Status new => acknowledged
2017-01-26 18:02 Jim Luth Target Version 1.04 => ?.??
2022-09-27 17:02 Jim Luth Note Added: 0017864
2022-09-27 17:02 Jim Luth Target Version => 1.05.03 RC1
2022-09-27 17:04 Jim Luth Note Edited: 0017864
2022-09-27 17:04 Jim Luth Assigned To => Jeff Harding
2022-09-27 17:04 Jim Luth Status acknowledged => assigned
2023-03-16 15:51 Jeff Harding Relationship added related to 0008733
2023-04-11 16:57 Jeff Harding Status assigned => resolved
2023-04-11 16:57 Jeff Harding Resolution open => fixed
2023-04-11 16:57 Jeff Harding Fixed in Version => 1.05.03
2023-04-11 16:57 Jeff Harding Note Added: 0019164
2023-05-09 15:13 Jim Luth Issue cloned: 0008951
2023-05-09 15:13 Jim Luth Relationship added related to 0008951
2023-05-09 15:15 Jim Luth Status resolved => closed
2023-05-09 15:15 Jim Luth Fixed in Version 1.05.03 => 1.05.03 RC1
2023-05-09 15:15 Jim Luth Note Added: 0019293