datalink-management - service managing datalink and flow persistence
The network/datalink-management service and its default instance and its daemon, dlmgmtd are responsible for managing persistent datalink and flow configuration. Administratively created or modified information about datalinks and flows is stored in SMF at the service instance level under FMRI, svc:/network/datalink-management:default.
Within the datalink-management service instance, the property group datalinks of type application contains persistent datalink information, while the flows property group of type application contains persistent flow information.
Each datalink is represented by a property group nested within the datalinks property group. The name of that property group is the datalink name, while the property group type is derived from the class of the link. Specifically, the property group types are:
datalink-aggr datalink-bridge datalink-cap datalink-eoib datalink-etherstub datalink-iptun datalink-part datalink-phys datalink-vlan datalink-vnic datalink-vxlan
The property group type corresponds to the relevant object, and can be administered using the dladm command.
Each flow is represented as a property group nested within the flows property group. The name of that property group is the flow name, while the property group type is flow.
Details about datalink and flow properties are provided in the dladm and flowadm commands. Properties with string representations are stored as the astring type in SMF, while unsigned values are stored as type count, with boolean values stored as type boolean. Properties with multiple values are stored as lists of values of the relevant type. Some examples of XML profile snippets are given below, with full XML profile examples provided in the /usr/share/auto_install/sc_profiles directory.
<service name='network/datalink-management' type='service' version='0'> <instance name='default' enabled='true'> <property_group name='datalinks' type='application'> ... <property_group name='net2' type='datalink-phys'> <propval name='mtu' type='astring' value='9000'/> </property_group> ... </property_group> </instance> </service>Example 2 Create a trunk-mode L4 Aggregation consisting of net2 and net3
<service name='network/datalink-management' type='service' version='0'> <instance name='default' enabled='true'> <property_group name='datalinks' type='application'> ... <property_group name='aggr0' type='datalink-aggr'> <propval name='aggr-mode' type='astring' value='trunk'/> <propval name='force' type='boolean' value='false'/> <propval name='key' type='count' value='0'/> <propval name='lacp-mode' type='astring' value='off'/> <propval name='lacp-timer' type='astring' value='short'/> <propval name='media' type='astring' value='Ethernet'/> <propval name='nports' type='count' value='2'/> <propval name='policy' type='astring' value='L4'/> <property name='ports' type='astring'> <astring_list> <value_node value='net2'/> <value_node value='net3'/> </astring_list> </property> </property_group> ... </property_group> </instance> </service>Example 3 Create a VNIC over net2
<service name='network/datalink-management' type='service' version='0'> <instance name='default' enabled='true'> <property_group name='datalinks' type='application'> ... <property_group name='vnic0' type='datalink-vnic'> <propval name='linkover' type='astring' value='net2'/> <propval name='mac-address' type='astring' value='2:8:20:91:bb:be'/> <propval name='mac-address-type' type='astring' value='random'/> <propval name='media' type='astring' value='Ethernet'/> <propval name='vid' type='astring' value='0'/> </property_group> ... </property_group> </instance> </service>Example 4 Customize Datalink Name Mapping such that ixgbe0 is named mynet0, and ixgbe1 is named mynet1
Any SC-profile-defined device-to-linkname mappings specified, will override system defaults at install time.
<service name='network/datalink-management' type='service' version='0'> <instance name='default' enabled='true'> <property_group name='datalinks' type='application'> ... <property_group name='mynet0' type='datalink-phys'> <propval name='devname' type='astring' value='ixgbe0'/> </property_group> <property_group name='mynet1' type='datalink-phys'> <propval name='devname' type='astring' value='ixgbe1'/> </property_group> ... </property_group> </instance> </service>Example 5 Create a Flow https-1 for Local Port 433 with Priority Medium over Link net1.
<service name='network/datalink-management' type='service' version='0'> <instance name='default' enabled='true'> <property_group name='flows' type='application'> ... <property_group name='https-1' type='flow'> <propval name='dscp' type='count' value='255'/> <propval name='linkover' type='astring' value='net1'/> <propval name='local-port' type='count' value='433'/> <propval name='priority' type='astring' value='medium'/> <propval name='rank' type='count' value='0'/> </property_group> ... </property_group> </instance> </service>
See attributes(7) for descriptions of the following attributes:
|
dladm(8), flowadm(8), installadm(8), service_bundle(5), smf(7), sysconfig(8)