Entrust nShield Connect v12.50.4 - Config-Serverstartup

9 Basic nShield Connect, RFS and client configuration
nethsmenroll [Options] --privileged <nShield Connect IP><nShield Connect ESN><nShield
Connect KNETI HASH>
Options :
-m, --module=MODULE
Specifies the local module number that should
be used (default is 0 for dynamic configuration
by hardserver).
-p, --privileged
Makes the hardserver request a privileged
connection to the nShield Connect (default
unprivileged).
-r, --remove
Removes the configuration of the specified
nShield Connect.
-f, --force
Forces reconfiguration of an nShield Connect
already known.
--no-hkneti-confirmation
Does not request confirmation when
automatically determining the nShield Connect's
ESN and HKNETI.
CAUTION! This option is potentially
insecure and should only be used on
secure networks where there is no
possibility of a man-in-the-middle attack.
-V, --verify-nethsm-details
When the ESN and HKNETI have been provided
on the command line, verifies that the selected
HSM is online, reachable and matches those
details.
-P, --port=PORT
Specifies the port to use when connecting to the
given nShield Connect (default 9004).
-n, --ntoken-esn=ESN
Specifies the ESN of the LOCAL nToken that
should be used when connecting to the nShield
Connect (default empty, i.e. no nToken
authentication used)
9.3.1.2 config-serverstartup
The config-serverstartup command-line utility automatically edits the [server_startup] section in the
local hardserver configuration file in order to enable TCP ports for Java and KeySafe. Any fields for
which values are not specified remain unchanged. After making any changes you are prompted to
restart the hardserver.
Run config-serverstartup using the following commands:
config-serverstartup [OPTIONS]
For more information about the options available to use with config-serverstartup, run the command:
Page 57
nShield® Connect - Installation Guide