Using the NIM dtls_init operation
Use the dtls_init operation to prepare resources for use by a dataless client.
The command line syntax for the dtls_init operation
is as follows:
nim -o dtls_init -a Attribute=Value ... TargetName |TargetNames
The target of a dtls_init operation can be any dataless NIM client or group of dataless NIM clients.
The following are required attributes that
can be specified for the dtls_init operation:
Item | Description |
---|---|
-a dump=Value | Specifies the dump resource that contains client dump files. |
-a spot=Value | Specifies the SPOT resource to be used to provide network boot support and the /usr file system for clients. |
-a root=Value | Specifies the root resource that contains the client root (/) directories. The root resource must be served by the same machine that serves the SPOT. |
The following are optional attributes that
can be specified for the dtls_init operation:
Item | Description |
---|---|
-a paging=Value | Specifies the paging resource containing client paging files. |
-a group=Value | Specifies the name of a resource group to use for the installation. A resource group can be specified as an alternative to specifying multiple resources as separate attributes. |
-a home=Value | Specifies the home resource that contains client /home directories. |
-a resolv_conf=Value | Specifies the resolv_conf resource to configure Domain Name Protocol name server information on the client. |
-a shared_home=Value | Specifies the shared_home resource that contains a common /home directory for multiple clients. |
-a size=Value | Specifies the size in megabytes for client paging files. |
-a tmp=Value | Specifies the tmp resource that contains client /tmp directories. |
-a verbose=Value | Displays information for debugging. Valid values are 1-5. Use verbose=5 to show maximum detail. The default is to show no debugging output. |
The dtls_init operation populates client directories and creates client paging and dump files. A network boot image is also allocated to the client. When the client boots over the network, it obtains the boot image and is configured to mount the remaining resources.