Connect the Pilot to Your Management LAN
Prerequisites:
● Two 100 BaseT ports for the public connection to the management network.
For added redundancy, the two connections should be to separate
switches. The Pillar Axiom system provides a standard Cat 5 RJ-45 jack on
each Pilot control unit (CU) for this connection.
● The external switch ports must be configured for auto-negation, if the Pillar
Axiom system is also configured for auto-negation. If the external switch
ports are manually set to a certain speed or a duplex setting, the Pilot must
be set to match those settings.
● Three IP addresses on the same subnet: one IP for each physical interface
and one shared IP.
● If Pillar Axiom Path Manager (APM) is installed on a SAN host, that host will
require an Ethernet interface for communication with the Pillar Axiom
Storage Services Manager. Because APM communicates with the Pilot
over secure, encrypted XML, the network configuration must permit the
SAN host to reach the Pilot management IP Ethernet interfaces on port 26004.
Note: VLAN tagging is not supported on the management interfaces.
The Pillar Axiom system is shipped with the following default IP addresses and
settings, with the Dynamic Host Configuration Protocol (DHCP) disabled:
● 10.0.0.1 (Default gateway)
● 10.0.0.2 (Shared IP)
● 10.0.0.3 (Pilot CU 0)
● 10.0.0.4 (Pilot CU 1)
● 255.255.255.0 (Netmask)
● Auto-negation: Enabled
Caution
Do not connect the Pillar Axiom Pilot management
interfaces to any network unless you are sure that the
default IP addresses of the Pillar Axiom system are not
currently in use on that network. Using the default Pillar
Axiom IP addresses in your network can interfere with other
workstations on the network as well as cause problems
when you configure the Pillar Axiom system.
Chapter 4 Connect Data Cables
Connect the Pilot to Your Management LAN
100
