Technical References

For example, DHCP Scope objects contain lists of address ranges
from which leases may be offered. To manipulate this list of
ranges, the scope command provides the commands: addRange,
removeRange, and listRanges.
Another example is the forceAvailable command provided by the
lease command to tell the DHCP server that a given lease should
be forced into the available state.
Filters
The results of the list commands can be restricted by applying
filters to the results. The filter specification is similar to
the LDAP query filter specification, but uses infix rather than
prefix relational operators. See the filter man page for a more
complete description of the filter specification grammar.
Format specifiers
The output format of the list and show commands can be specified
with the format arguments. See the format man page for a complete
description of the format specifiers.
Licensing
nrcmd requires the current cluster to have a valid license.
If the license is invalid or has expired, only the 'license'
command will be operational; it may be used to establish a new
license key. A warning will be issued upon login if the
license will be expiring within 7 days.
Locking
nrcmd versions prior to CNR 6.2 are limited to a single
session and use a locking mechanism to control access.
In interactive mode, the program attempts at startup to get an
exclusive lock for the cluster to which it connects. If this
fails, nrcmd will issue a warning, and will allow only the
following commands to be executed: "client", "lease",
"zone create", "help", and "force-lock". The force-lock
command obtains the exclusive lock indiscriminately, and
should be used with caution. In particular, it should not be
used unless you're sure that no one else is updating the cluster.
The warning issued for interactive mode, when the lock cannot
be obtained, is
408 Already locked: '<user>@<host>.<pid>'.
Warning: unable to lock the cluster.
You might want to use the force-lock command if
you're sure that no one else is updating the cluster
where
<user> is the name of the administrator
<host> is the name of the Unix or Windows host on which the
other user is running
<pid> is the process ID of the nrcmd or
Network Registrar process. (You can use system
tools such as Unix "ps" or NT "Task Manager" to
determine if the process is still running.)