The IetfBaseNetworkInterfaceType is formally defined in Table 43.
Table 43 – IetfBaseNetworkInterfaceType definition
|
Attribute |
Value |
||||
|
BrowseName |
IetfBaseNetworkInterfaceType |
||||
|
IsAbstract |
False |
||||
|
References |
NodeClass |
BrowseName |
DataType |
TypeDefinition |
Other |
|
Subtype of the BaseObjectType |
|||||
|
|
|
|
|
|
|
|
HasInterface |
ObjectType |
IIetfBaseNetworkInterfaceType |
|
|
|
|
Applied from IIetfBaseNetworkInterfaceType (see 5.2.1) |
|||||
|
HasComponent |
Variable |
AdminStatus |
InterfaceAdminStatus |
BaseDataVariableType |
M |
|
HasComponent |
Variable |
OperStatus |
InterfaceOperStatus |
BaseDataVariableType |
M |
|
HasComponent |
Variable |
PhysAddress |
String |
BaseDataVariableType |
O |
|
HasComponent |
Variable |
Speed |
UInt64 |
AnalogUnitType |
M |
|
|
|
|
|
|
|
|
HasLowerLayerInterface |
Object |
<InterfaceName> |
|
BaseObjectType |
OP |
|
Conformance Units |
|||||
|
BNM IETF Interface Base Info |
|||||
The BrowseName of this Object shall be the same as the ifName of the corresponding IETF object (see IETF RFC 2863: The Interfaces Group MIB).
For the formal definition of AdminStatus, OperStatus, PhysAddress and Speed please refer to section 5.2.1.
The HasLowerLayerInterface Reference points to an Object implementing the IIetfBaseNetworkInterfaceType used to indicate a hierarchical connection of network interfaces. This is used to indicate the relation e.g. between a VLAN interface and the actual physical interface. A VLAN interface shall additionally implement IVlanIdType.
Each instance of the IetfBaseNetworkInterfaceType shall point to zero or one instance of PriorityMappingTableType or a subtype using a UsesProrityMappingTable Reference or a subtype. The referenced PriorityMappingTable is used for the prioritisation of network messages injected to the network using this network interface. If an instance of type IetfBaseNetworkInterfaceType has no reference to a PriorityMappingTable, the PriorityMappingTable of the next lower layer interface of type IetfBaseNetworkInterfaceType shall be used. An example for this is shown in Annex A.2 for “eth0.100”.
Note: It is recommended that within one network domain that all interfaces should have consistent MappingTables assigned. This ensures consistent use of Quality of Service features within the network.
A network interface is linked for transmission or reception via the BrowseName of the object of type IetfBaseNetworkInterfaceType.
Note: An example for a simplified PubSub connection is shown in Annex A.2.
The components of the IetfBaseNetworkInterfaceType have the Attribute values defined in Table 44.
Table 44 – IetfBaseNetworkInterfaceType Attribute values for child Nodes
|
Source Path |
Value Attribute |
Description Attribute |
||
|
NamespaceUri: http://www.opcfoundation.org/UA/units/un/cefact UnitId: 4337968DisplayName: bit/sDescription: bit per second |
- |
The components of the IetfBaseNetworkInterfaceType have additional References which are defined in Table 45.
Table 45 – IetfBaseNetworkInterfaceType Additional References
|
SourceBrowsePath |
Reference Type |
Is Forward |
TargetBrowsePath |
|
<InterfaceName> |
HasInterface |
True |
IIetfBaseNetworkInterfaceType |