A sub-interface is a list of additional (secondary, or virtual) addresses that are to be assigned to a network interface. Sub-interfaces are present only in the saved configuration and are stored in suffixed file names derived from the interface configuration script file name. For example, sub-interfaces for eth0 are stored as: /etc/sysconfig/network-scripts/ifcfg-eth0.0 /etc/sysconfig/network-scripts/ifcfg-eth0.1 etc.
Supports the configuration of bonded NICs, i.e. link aggregation. Bond interface configuration is stored as an interface configuration script, for example: /etc/sysconfig/network-scripts/ifcfg-bond0
Represents a list of bond interface elements.
Configuration for the loopback interface. Loopback interface configuration is stored as an interface configuration script, for example: /etc/sysconfig/network-scripts/ifcfg-lo
Configuration for an ethernet interface. Ethernet interface configuration is stored as an interface configuration script, for example: /etc/sysconfig/network-scripts/ifcfg-eth0
Represents a list of ethernet interface elements.
| Name | Type | Description | Attributes |
|---|---|---|---|
| plcmEthernetInterfaceList | List of plcm-ethernet-interface | See Definition of plcm-ethernet-interface |
| Name | Type | Description | Attributes |
|---|---|---|---|
| services | List of PlcmService | ||
| lan-security-config | LanSecurityConfiguration | ||
| search-path-elements | List of SearchPathElement | ||
| ethtool-options | List of PlcmEthtoolOption | ||
| driver-info | driver-info | See Definition of driver-info | |
| rules | List of PlcmNetworkRoutingRule | ||
| routes | List of PlcmNetworkRoute | ||
| sub-interfaces | List of PlcmSubInterface | ||
| addresses | List of PlcmNetworkAddress | ||
| name | xs:string | A descriptive name for the interface | |
| device-name | xs:string | Defines the name for the device to be configured, e.g. eth0 | Mandatory |
| state | PlcmNetworkInterfaceState | For a live network configuration, this value will not be null and will reflect the current operational state of the interface. For a saved network configuration, this value will be null. | |
| dscp | xs:int | The Differentiated Services marker for outgoing traffic originating on the interface. | |
| read-only | xs:boolean | Informs the client whether this interface can have its settings changed via this API | |
| mac-address | PlcmMacAddress | This address overrides the physical MAC address for this interface. The physical MAC address is found on the ethernet-interface container defined later in this module and is referred to as the hardware address. | |
| ipv4-failure-is-fatal | xs:boolean | Whether a failure to initialize ipv4 should be considered fatal with respect to the network service startup, i.e even if ipv6 is enabled and successfully initialized, the link will not be considered UP if ipv4 cannot be initialized. | |
| ipv6-init | xs:boolean | If set to true, initialize this interface for ipv6 addressing. If set to false, do not initialize this interface for ipv6 addressing. False is the default value. This setting is required for ipv6 static and DHCP assignment of ipv6 addresses. It does not affect ipv6 Stateless Address Auto-Configuration (SLAAC) as per RFC 4862. | |
| ipv6-failure-is-fatal | xs:boolean | Whether a failure to initialize ipv6 should be considered fatal with respect to the network service startup, i.e even if ipv4 is enabled and successfully initialized, the link will not be considered UP if ipv6 cannot be initialized. | |
| ipv6-auto-config | xs:boolean | Defines whether this ipv6 interface has auto configuration turned on | |
| mtu | xs:int | Maximum transmission unit for Ipv4 traffic through this interface | |
| ipv6-mtu | xs:int | Maximum transmission unit for ipv6 traffic through this interface | |
| link-delay-time | xs:int | ||
| interface-type | PlcmNetworkInterfaceType | Specifies the type of interface | |
| boot-protocol | PlcmNetworkBootProtocol | Defines the boot protocol setting for this interface | |
| on-boot | xs:boolean | Defines whether interface is enabled on system boot up | |
| hardware-address | PlcmPhysAddress | The hardware address of the physical device or in the case of a bond interface, the hardware address to use for the channel (link aggregator) | |
| bond-master | BondMaster | The name of the interface that is the master interface when bonding multiple interfaces | |
| bond-slave | xs:boolean | true means this device is controlled by the channel bonding interface specified in the bond-master; false means otherwise. | |
| ipv6-privacy | xs:boolean | Defines whether this ipv6 interface has the privacy feature turned on | |
| ipv6-dhcp | xs:boolean | Defines whether this interface has DHCP feature turned on for ipv6 | |
| ipv6-dhcp-options | List of PlcmIpv6DhcpOption | Defines the DHCP options for ipv6 for this interface, if DHCP is turned on | |
| dhcp-host-name | PlcmDomainName | The hostname of the DHCP server | |
| peer-dns | xs:boolean | When set to true, the DNS nameservers assigned by DHCP will be automatically added to the DNS configuration (/etc/resolv.conf) file. The DNS nameservers may be specified as one (or more) addresses for the interface with address-type set to DNS and an order value specified, e.g. 1,2,3. When using DHCP and specifying nameservers in this fashion, this option should be set to false, which will NOT write the DHCP assigned nameservers to the DNS configuration file. | |
| def-route | xs:boolean | Whether this interface represents the default gateway for the server | |
| uuid | Uuid | Universally unique identifier for the network interface. | |
| dns-domain | PlcmDomainName | DNS domain name for the server | |
| hot-plug | xs:boolean | Whether the interface should be activated when it is hot-plugged | |
| app-config | xs:string | Any application specific configuration that might be associated with this interface | |
| nat-address | PlcmInetAddress | IP address on the external firewall behind which the service is hosted. |
| Name | Type | Description | Attributes |
|---|---|---|---|
| rules | List of PlcmNetworkRoutingRule | ||
| routes | List of PlcmNetworkRoute | ||
| sub-interfaces | List of PlcmSubInterface | ||
| addresses | List of PlcmNetworkAddress | ||
| name | xs:string | A descriptive name for the interface. | |
| device-name | xs:string | Defines the name for the device to be configured, e.g. eth0 | Mandatory |
| state | PlcmNetworkInterfaceState | For a live network configuration, this value will not be null and will reflect the current operational state of the interface. For a saved network configuration, this value will be null. | |
| read-only | xs:boolean | Informs the client whether this interface can have its settings changed via this API | |
| mac-address | PlcmMacAddress | This address overrides the physical MAC address for this interface. The physical MAC address is found on the ethernet-interface container defined later in this module and is referred to as the hardware address. | |
| ipv4-failure-is-fatal | xs:boolean | Whether a failure to initialize ipv4 should be considered fatal with respect to the network service startup, i.e even if ipv6 is enabled and successfully initialized, the link will not be considered UP if ipv4 cannot be initialized. | |
| ipv6-init | xs:boolean | If set to true, initialize this interface for ipv6 addressing. If set to false, do not initialize this interface for ipv6 addressing. False is the default value. This setting is required for ipv6 static and DHCP assignment of ipv6 addresses. It does not affect ipv6 Stateless Address Auto-Configuration (SLAAC) as per RFC 4862. | |
| ipv6-failure-is-fatal | xs:boolean | Whether a failure to initialize ipv6 should be considered fatal with respect to the network service startup, i.e even if ipv4 is enabled and successfully initialized, the link will not be considered UP if ipv6 cannot be initialized. | |
| ipv6-auto-config | xs:boolean | Defines whether this ipv6 interface has auto configuration turned on | |
| mtu | xs:int | Maximum transmission unit for Ipv4 traffic through this interface | |
| ipv6-mtu | xs:int | Maximum transmission unit for ipv6 traffic through this interface | |
| link-delay-time | xs:int | ||
| interface-type | PlcmNetworkInterfaceType | Specifies the type of interface | |
| boot-protocol | PlcmNetworkBootProtocol | Defines the boot protocol setting for this interface | |
| on-boot | xs:boolean | Defines whether interface is enabled on system boot up | |
| hardware-address | PlcmPhysAddress | The hardware address of the physical device or in the case of a bond interface, the hardware address to use for the channel (link aggregator) |
| Name | Type | Description | Attributes |
|---|---|---|---|
| plcmBondInterfaceList | List of plcm-bond-interface | See Definition of plcm-bond-interface |
| Name | Type | Description | Attributes |
|---|---|---|---|
| services | List of PlcmService | ||
| options | List of PlcmBondingOption | ||
| rules | List of PlcmNetworkRoutingRule | ||
| routes | List of PlcmNetworkRoute | ||
| sub-interfaces | List of PlcmSubInterface | ||
| search-path-elements | List of SearchPathElement | ||
| addresses | List of PlcmNetworkAddress | ||
| name | xs:string | A descriptive name for the interface. | |
| device-name | xs:string | Defines the name for the device to be configured, e.g. eth0 | Mandatory |
| state | PlcmNetworkInterfaceState | For a live network configuration, this value will not be null and will reflect the current operational state of the interface. For a saved network configuration, this value will be null. | |
| dscp | xs:int | The Differentiated Services marker for outgoing traffic originating on the interface. | |
| read-only | xs:boolean | Informs the client whether this interface can have its settings changed via this API | |
| mac-address | PlcmMacAddress | This address overrides the physical MAC address for this interface. The physical MAC address is found on the ethernet-interface container defined later in this module and is referred to as the hardware address. | |
| ipv4-failure-is-fatal | xs:boolean | Whether a failure to initialize ipv4 should be considered fatal with respect to the network service startup, i.e even if ipv6 is enabled and successfully initialized, the link will not be considered UP if ipv4 cannot be initialized. | |
| ipv6-init | xs:boolean | If set to true, initialize this interface for ipv6 addressing. If set to false, do not initialize this interface for ipv6 addressing. False is the default value. This setting is required for ipv6 static and DHCP assignment of ipv6 addresses. It does not affect ipv6 Stateless Address Auto-Configuration (SLAAC) as per RFC 4862. | |
| ipv6-failure-is-fatal | xs:boolean | Whether a failure to initialize ipv6 should be considered fatal with respect to the network service startup, i.e even if ipv4 is enabled and successfully initialized, the link will not be considered UP if ipv6 cannot be initialized. | |
| ipv6-auto-config | xs:boolean | Defines whether this ipv6 interface has auto configuration turned on | |
| mtu | xs:int | Maximum transmission unit for Ipv4 traffic through this interface | |
| ipv6-mtu | xs:int | Maximum transmission unit for ipv6 traffic through this interface | |
| ipv6-privacy | xs:boolean | Defines whether this ipv6 interface has the privacy feature turned on | |
| ipv6-dhcp | xs:boolean | Defines whether this interface has DHCP feature turned on for ipv6 | |
| ipv6-dhcp-options | List of PlcmIpv6DhcpOption | Defines the DHCP options for ipv6 for this interface, if DHCP is turned on | |
| dhcp-host-name | PlcmDomainName | The hostname of the DHCP server | |
| peer-dns | xs:boolean | When set to true, the DNS nameservers assigned by DHCP will be automatically added to the DNS configuration (/etc/resolv.conf) file. The DNS nameservers may be specified as one (or more) addresses for the interface with address-type set to DNS and an order value specified, e.g. 1,2,3. When using DHCP and specifying nameservers in this fashion, this option should be set to false, which will NOT write the DHCP assigned nameservers to the DNS configuration file. | |
| def-route | xs:boolean | Whether this interface represents the default gateway for the server | |
| dns-domain | PlcmDomainName | DNS domain name for the server | |
| link-delay-time | xs:int | ||
| interface-type | PlcmNetworkInterfaceType | Specifies the type of interface | |
| boot-protocol | PlcmNetworkBootProtocol | Defines the boot protocol setting for this interface | |
| on-boot | xs:boolean | Defines whether interface is enabled on system boot up | |
| hardware-address | PlcmPhysAddress | The hardware address of the physical device or in the case of a bond interface, the hardware address to use for the channel (link aggregator) | |
| app-config | xs:string | Any application specific configuration that might be associated with this interface |
| Name | Type | Description | Attributes |
|---|---|---|---|
| services | List of PlcmService | ||
| rules | List of PlcmNetworkRoutingRule | ||
| routes | List of PlcmNetworkRoute | ||
| search-path-elements | List of SearchPathElement | ||
| addresses | List of PlcmNetworkAddress | ||
| name | xs:string | A descriptive name for the interface. | |
| device-name | xs:string | Defines the device name for the sub-interface to be configured, e.g. eth0.1, eth0.2, etc. NOTE: When configuring VLAN sub-interfaces, the sub-interface suffix number (.1, .2, etc.) MUST match the ID of the virtual network, i.e. the VLAN tag. For example, to configure a sub-interface of eth0 to use VLAN 492, the number suffix for the device name MUST be .492 resulting in the device name: eth0.492 | Mandatory |
| state | PlcmNetworkInterfaceState | For a live network configuration, this value will not be null and will reflect the current operational state of the interface. For a saved network configuration, this value will be null. | |
| dscp | xs:int | The Differentiated Services marker for outgoing traffic originating on the interface. | |
| read-only | xs:boolean | Informs the client whether this interface can have its settings changed via this API | |
| mac-address | PlcmMacAddress | This address overrides the physical MAC address for this interface. The physical MAC address is found on the ethernet-interface container defined later in this module and is referred to as the hardware address. | |
| ipv4-failure-is-fatal | xs:boolean | Whether a failure to initialize ipv4 should be considered fatal with respect to the network service startup, i.e even if ipv6 is enabled and successfully initialized, the link will not be considered UP if ipv4 cannot be initialized. | |
| ipv6-init | xs:boolean | If set to true, initialize this interface for ipv6 addressing. If set to false, do not initialize this interface for ipv6 addressing. False is the default value. This setting is required for ipv6 static and DHCP assignment of ipv6 addresses. It does not affect ipv6 Stateless Address Auto-Configuration (SLAAC) as per RFC 4862. | |
| ipv6-failure-is-fatal | xs:boolean | Whether a failure to initialize ipv6 should be considered fatal with respect to the network service startup, i.e even if ipv4 is enabled and successfully initialized, the link will not be considered UP if ipv6 cannot be initialized. | |
| ipv6-auto-config | xs:boolean | Defines whether this ipv6 interface has auto configuration turned on | |
| mtu | xs:int | Maximum transmission unit for Ipv4 traffic through this interface | |
| ipv6-mtu | xs:int | Maximum transmission unit for ipv6 traffic through this interface | |
| ipv6-privacy | xs:boolean | Defines whether this ipv6 interface has the privacy feature turned on | |
| ipv6-dhcp | xs:boolean | Defines whether this interface has DHCP feature turned on for ipv6 | |
| ipv6-dhcp-options | List of PlcmIpv6DhcpOption | Defines the DHCP options for ipv6 for this interface, if DHCP is turned on | |
| dhcp-host-name | PlcmDomainName | The hostname of the DHCP server | |
| peer-dns | xs:boolean | When set to true, the DNS nameservers assigned by DHCP will be automatically added to the DNS configuration (/etc/resolv.conf) file. The DNS nameservers may be specified as one (or more) addresses for the interface with address-type set to DNS and an order value specified, e.g. 1,2,3. When using DHCP and specifying nameservers in this fashion, this option should be set to false, which will NOT write the DHCP assigned nameservers to the DNS configuration file. | |
| def-route | xs:boolean | Whether this interface represents the default gateway for the server | |
| dns-domain | PlcmDomainName | DNS domain name for the server | |
| link-delay-time | xs:int | ||
| boot-protocol | PlcmNetworkBootProtocol | Defines the boot protocol setting for this interface | |
| on-parent | xs:boolean | If set to true, the sub-interface will be brought up/down when the parent interface is brought up/down. | |
| vlan | xs:boolean | If set to true, the sub-interface is for a VLAN network. The VLAN id is part of the device name. | |
| app-config | xs:string | Any application specific configuration that might be associated with this interface |
| Name | Type | Description | Attributes |
|---|---|---|---|
| driver-name | xs:string | Name of the network interface driver | |
| driver-version | xs:string | Version of the network interface driver | |
| firmware-version | xs:string | Version of the firmware used by the network interface driver |
| Name | Type | Restrictions |
|---|---|---|
| BondMaster | xs:string | Length of value must be >=1 Length of value must be <=32 |