A virtual interfaces configuration may be represented by Objects representing the virtual and the physical network interface instances. HasLowerLayerInterface References point from the Object(s) representing the virtual interface(s) to the Object representing the physical interface. All Objects are of ObjectType IetfBaseNetworkInterfaceType. An example is shown in Figure A-1.

Note: The usage of the References is following the YANG modelling approach which is using reference pointers in the YANG-interface nodes to point to other interface nodes in lower or higher layers (“higher-layer-if”, “lower-layer-if”).

image009.png

Figure A-1 – Modelling Example for virtual network interfaces

A link aggregation configuration may be represented by Objects representing the logical aggregation and the particular physical interface instances. HasLowerLayerInterface References point from the Object(s) representing the aggregation interface to the Objects representing the physical interfaces. All Objects implement the IIetfBaseNetworkInterfaceType. An example is shown in Figure A-2.

image010.png

Figure A-2 – Modelling example for link aggregation

All packets sent via this network interface will use the source address and – in case of VLAN interfaces – VLAN ID as specified by this interface to generate a packet. All packets received via this network interface will use – in case of unicast communication – the destination address and – in case of VLAN interfaces – VLAN ID as specified by the interface to filter incoming packets.

When using PubSub, each PubSubConnection as defined by the PubSubConnectionDataType in Part14 contains the address variable of type NetworkAddressDataType. If the networkInterface String of the NetworkAddressDataType matches the BrowseName of one Object in the NetworkInterfaces folder, it links the transmission or reception and the network interface.

image011.png

Figure A-3 – Modelling Example for PriorityMappingTableType and IetfBaseNetworkInterface

image012.png

Figure A-4 – Possible Integration of BNM into PubSub

image013.png

Figure A-5 – Recommended Integration of BNM into Companion Spec exemplified by PROFINET

___________