Chapter 2: ProtectServer External 2 Installation and Configuration
IPv6
psesh:>
network interface ipv6 -device
<netdevice>
-ip
<IP> [
-gateway
<IP>]
Either of these commands will prompt you to restart the network service.
3.
[Optional] Configure network interface bonding. This allows the two network devices to function as a single
interface, with a single MAC address, improving bandwidth and providing redundancy.
NOTE
Use network interface bonding with static IP addresses only. If DHCP is used, the
bond will be broken if one interface is assigned a different IP.
psesh:>
network interface bonding config -ip
<IP>
-netmask
<IP>
-gateway
<IP>] [
-mode
<mode>]
psesh:>
network interface bonding enable
psesh:>
sysconf appliance reboot
Multiple bonding modes provide different options for load-balancing between the two physical interfaces:
•
0
: Balance Round Robin. Packets are transmitted alternately on each device in the bond, providing load
balancing and fault tolerance.
•
1
: Active-Backup. One bonded device is active and the other serves as a backup. The backup only
becomes active if the active device loses connectivity.
•
2
: Balance XOR. Transmits based on an XOR formula, where the source MAC address is XOR'd with the
destination MAC address. The same bonded device is selected for each destination MAC address,
providing load balancing and fault tolerance.
•
3
: Broadcast. All packets are transmitted on both bonded interfaces, providing fault tolerance.
•
4
: 802.3ad (Dynamic Link Aggregation). Creates aggregated groups that share the same speed and
duplex settings. This mode requires a switch that supports IEEE 802.3ad dynamic links. The dvice used
for an outgoing packet is selected by the transmit hash policy (by default, a simple XOR). This policy can
be changed via the xmit_hash_policy option.
NOTE:
Check the 802.3ad standard to ensure that your
transmit policy is 802.3ad-compliant. In particular, check section 43.2.4 for packet mis-ordering
requirements. Non-compliance tolerance may vary between different peer implementations.
•
5
: Balance TLB (Transmit Load Balancing). Outgoing traffic is distributed according to the current load
and queue on each bonded device. Incoming traffic is received by the current device.
•
6
: Balance ALB (Adaptive Load Balancing). Both outgoing and incoming traffic is load-balanced like
outgoing traffic in mode 5. Incoming load balancing is governed by ARP negotiation. The bonding driver
intercepts the ARP replies sent by the appliance and overwrites the source hardware address with the
unique hardware address of one of the bonded devices. Different clients will therefore use different
hardware addresses for the appliance.
4.
[Optional] Set the appliance hostname and domain name.
psesh:>
network hostname
<hostname>
psesh:>
network domain
<netdomain>
You must configure your DNS server to resolve the hostname to the IP address configured on the Ethernet
port of the appliance. Do this for each Ethernet port connected to a network. See your network administrator
for assistance.
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
33
