/usr/sadm/bin/smtnrhdb subcommand [auth_args] -- subcommand_args]

The smtnrhdb command adds, modifies, deletes, and lists entries in the tnrhdb database.

The tnrhdb database specifies which remote-host template to use for each host, including the local host, in the distributed system. If a host's IP address cannot be matched to some entry in the tnrhdb database, communication with the host is not permitted.

The smtnrhdb command requires the Solaris Management Console to be initialized for the command to succeed (see smc(1M)). After rebooting the Solaris Management Console server, the first smc connection can time out, so you might need to retry the command.

The trusted network software uses a network "longest prefix of matching bits" mechanism when looking for a host. The software looks first for the IP address of the host. If the software does not find this address, then the software falls back to searching for an IP address with the longest prefix of a matching bit pattern, and so on.

Note -

Using the "longest prefix of matching bits" mechanism, an IPv4 address of 0.0.0.0 is a wildcard address with a prefix length of 0 and hence matches any IPv4 address. For more information about prefi x lengths in IPv4 and IPv6 addresses, see System Administration Guide: IP Services.

The smtnrhdb command accepts a hostname, IP address, and wildcard address with as optional prefix as valid addresses. See subcommand_args, below, for the format of valid addresses.

smtnrhdb subcommands are:

add

delete

list

modify

The smtnrhdb authentication arguments, auth_args, are derived from the smc arg set. These arguments are the same regardless of which subcommand you use.

The subcommand-specific options, subcommand_args, must be preceded by the -- option.

The valid auth_args are -D, -H, -l, -p, -r, and -u; they are all optional. If no auth_args are specified, certain defaults will be assumed and the user might be prompted for additional information, such as a password for authentication purposes. These letter options can also be specified by their equivalent option words preceded by a double dash. For example, you can use either -D or --domain.

-D | --domain domain

-H | --hostname host_name:port

-l | --rolepassword role_password

-p | --password password

-r | --rolename role_name

-u | --username user_name

--

Note: Descriptions and other arg options that contain white spaces must be enclosed in double quotes.

-h

-H hostname

-i ipaddress

-n templatename

-p prefixlen

-w ipaddress-wildcard

-H hostname -n templatename |
-i ipaddress -n templatename |
-w ipaddress-wildcard -n templatename [ -p prefixlen ] |
-h

-H hostname -n templatename |
-i ipaddress -n templatename |
-w ipaddress-wildcard -n templatename [ -p prefixlen ] |
-h

-H hostname |
-i ipaddress |
-w ipaddress-wildcard [ -p prefixlen ] |
-h

-h

Example 1 Specifying the Template Name for a Wildcard IP Address

The admin role specifies the template name, cipso_lan, for a series of hosts that use the IP address wildcard 192.168.113.0 on the local file system. Since no authorization arguments were specified, the administrator connects to port 898 of the local host on the local server with the file domain type, which are the defaults. The administrator is prompted for the admin password.

$ usr/sadm/bin/smtnrhdb add -- -w 192.168.113.0 -n cipso_lan

Example 2 Deleting an Entry in the tnrhdb Database

The admin role connects to port 898 (which happens to be the default) of the LDAP server and deletes a host entry from the database by specifying its IP address, 192.168.113.8. Since the domain was not specified, the file domain type and local server are used by default. The administrator is prompted for the admin password.

# /usr/sadm/bin/smtnrhdb delete \
-D ldap:/example.domain -i 192.168.113.8

Example 3 Adding a Subnet to the tnrhdb Database

The following command adds all the addresses on the 192.168.55.0 subnet, from 192.168.55.1 to 192.168.55.255, to the tnrhdb database:

# /usr/sadm/bin/smtnrhdb add \e
-D file:/machine1.ExampleCo.COM/machine1.ExampleCo.COM \e
 -- -w 192.168.55.0 -n cipso
Authenticating as user: root
Type /? for help, pressing <enter> accepts the default denoted by [ ]
Please enter a string value for: password ::
Loading Tool: com.exampleco.admin.hostmgr.cli.smtnrhdb.HostMgrTnrhdbCli
from machine1.ExampleCo.COM
Login to machine1.ExampleCo.COM as user root was successful.
Download of com.exampleco.admin.hostmgr.cli.smtnrhdb.HostMgrTnrhdbCli
from machine1.ExampleCo.COM
was successful.

Example 4 Adding Subnet 192.168.0 to the tnrhdb Database

The following command adds all the addresses on the 192.168.0 subnet, from 192.168.0.1 to 192.168.0.255 to the tnrhdb database. The prefix, 24, indicates that the first 24 bits (192.168.0) are fixed. Only the final zero is a wildcard.

# /usr/sadm/bin/smtnrhdb add \e
-D file:/machine1.ExampleCo.COM/machine1.ExampleCo.COM \e
 -- -w 192.168.0.0 -p 24 -n cipso

Login to machine1.ExampleCo.COM as user root was successful.
Download of com.exampleco.admin.hostmgr.cli.smtnrhdb.HostMgrTnrhdbCli 
from machine1.ExampleCo.COM was successful.

The following exit values are returned:

0

1

2

The following files are used by the smtnrhdb command:

/etc/security/tsol/tnrhdb

See attributes(5) for descriptions of the following attributes:

smc(1M), netmasks(4), attributes(5)

System Administration Guide: Security Services

The functionality described on this manual page is available only if the system is configured with Trusted Extensions.