Chapter 3: ProtectServer External 2 Plus Installation and Configuration
CAUTION!
Executing
sysconf appliance factory
over an SSH connection may cause you
to lose connection with the appliance when the IP address is reset. To avoid this, use a serial
connection instead when using this command.
Run System Test
Before field testing and deployment, run the diagnostic utility. While logged in as the
admin
or
pseoperator
enter the command
hsm state
to display the current status:
psesh:>hsm state
HSM device 0:
HSM in NORMAL MODE. RESPONDING to requests. Usage Level=0%
State = (0x8000, 0xffffffff)
Host Interface
= PSIe2
Command Result : 0 (Success)
You can also use the PSESH command
status
to check each of the HSM's processes. See the
PSESH
Command Reference Guide
for command syntax.
Network Configuration
The ProtectServer External 2 Plus is intended to be installed in a data center and accessed remotely over a
network. Network access is provided by two Ethernet LAN ports.
The network device interfaces (eth0 and eth1) are located on the back of the appliance, as illustrated below:
Appliance configuration
The following network parameters are configured at the appliance level:
>
Appliance hostname. A hostname is optional, unless you are using DNS.
Ethernet LAN device configuration
The ProtectServer External 2 Plus is equipped with two individually-configurable Ethernet LAN network
devices. You can configure the following network settings for each device:
>
IPv4 or IPv6 address. You can configure IPv4 addresses using static or DHCP addressing. IPv6 addresses
must be configured as static addresses.
>
Network gateway. Devices must use a gateway appropriate for the network (IPv4 or IPv6).
>
Network mask. IPv4 devices must use dotted-quad format (for example, 255.255.255.0). IPv6 devices can
use full or shorthand syntax.
>
Static network route.
Thales ProtectServer HSM 5.9.1 ProtectServer HSM and ProtectToolkit Installation and Configuration Guide
2021-11-02 08:51:40-04:00 Copyright 2009-2021 Thales Group
53
