Chapter 4: Testing and Configuration
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.
5.
[Optional] Add a domain name server to the network configuration for the appliance. The name server is
added to the appliance DNS table. There is one DNS table that applies to all network devices (ports) on the
appliance.
psesh:>
network dns add nameserver
<IP_address>
-device
<net_device>
NOTE
The domain name settings apply to static network configurations only. If you are using
DHCP, the DNS name servers configured on the DHCP server are used.
When you add a DNS server to a specific network device, it is added to the DNS table for the appliance and
becomes available to both devices, provided the device you added it to is connected to the network. For
example, if you add a DNS server to eth0, eth1 will be able to access the DNS server if eth0 is connected to
the network. If eth0 is disconnected from the network, eth1 also loses DNS server access. To ensure that
any DNS server you add is available in the event of a network or port failure, it is recommended that you add
it to both network-connected devices.
6.
[Optional] Add a search domain to the network configuration. These are automatically appended to an
internet address you specify in PSESH. For example, if you add the search domain
mycompany.com
,
entering the command
network ping hsm1
would search for the domain
hsm1.mycompany.com
. If the
domain resolves, it pings the device with that hostname.
lunash:>
network dns add searchdomain
<domain>
-device
<net_device>
The search domain is added to the appliance DNS table.
NOTE
The search domain settings apply to static network configurations only. If you are
using DHCP, the DNS search domains configured on the DHCP server are used.
When you add a DNS search domain to a specific network device, it is added to the DNS table for the
appliance and becomes available to both devices, provided the device you added it to is connected to the
network. For example, if you add a DNS server to eth0, eth1 will be able to access the DNS server if eth0 is
SafeNet ProtectToolkit 5.9 Installation and Configuration Guide
007-013682-007 Rev. A 08 January 2020 Copyright 2009-2020 Thales
25