This subclause defines remote management for UAFX Stations for networking features, including those defined in Clause 6, as well as the services and capabilities defined in Clause 7. For interoperable remote management, UAFX uses the Network Configuration Protocol (NETCONF) as a remote management protocol (see 7.2.2).


Figure 15 – Network commissioning using NETCONF and YANG

Figure 15 shows an example network consisting of two UAFX Stations and one IA-station. The Network Provisioning Entity uses NETCONF as the common remote management protocol for network configuration during commissioning (see OPC 10000-80, Figure 6) as required for the site. This configuration may contain, amongst others, VLAN configuration, IP subnet configuration, time synchronisation configuration, and QoS configuration. In addition, remote management enables network monitoring and communication fault diagnostics.

A UAFX Station supporting remote management shall support a Network Configuration Protocol (NETCONF) server as defined in IETF RFC 7589 (NETCONF over TLS).

NOTE 1 This document does not make use of SSH as a secure transport for NETCONF.

NOTE 2 A future release of this document will define NETCONF capabilities (for both client and server) and YANG modules to be supported by a UAFX Station.

A single management entity controls all components of a UAFX Station. Figure 16 shows a UAFX Station comprised of two End Station Components and one Bridge Component, all controlled by a single management entity.


Figure 16 – Example of a UAFX Station supporting NETCONF

NETCONF messages are recommended to be transmitted using priority information defined for Remote Management in Table 1.