Configuring Dual TCP/IP
Dual TCP/IP Overview E-3
■ For a single host, no netmask value is required:
SL8500> network ip policy route add host_IP_address dev 2A
SL8500> network ip policy route add host_IP_address via gateway_IP_address
dev 2A
SL8500> network ip policy enable 2A |2B
SL8500> network ip policy status
5. Verify the configuration.
SL8500> network ip address show
SL8500> network ip route show
SL8500> network ip policy route show dev 2A |2B
6. Check the date and time for accuracy.
SL8500> time
time print
time HH: MM
time HH:MM:SS
7. Test the configuration to ensure you can access the library through both ports.
Configuring an ACSLS Host for Dual TCP/IP
For the ACSLS server, you should use the
acsss_config
command or the Dynamic
Configuration
config
utility to configure two network interfaces on two separate
subnets. Use the
route
command to define the two routes on the ACSLS server. A
second physical connection improves reliability.
1. Update the routing tables of the ACSLS server by following the ACSLS
documentation. If there is a single network interface on the ACSLS server, no
special routing is required on the host.
2. Using the UNIX command prompt at the ACSLS server, use the Dynamic Config
command to add a port connection to the SL8500.
a. Ensure the ACS is in online or diagnostic mode to ACSLS.
b. Use
config port
acs_id to add a port.
c. If not already online, bring the ACS online to ACSLS.
3. To remove or replace an existing IP address with a different port:
a. Shut down ACSLS by issuing
kill.acsss
(for 7.3 and below) or
acsss
disable
(for 8.0 and above).
b. Configure the new ports by issuing
acsss_config
.
c. Bring ACSLS back online by issuing
rc.acsss
(for 7.3 and below) or
acsss
enable
(for 8.0 and above)
For more information, see the ACSLS Administrator’s Guide.
Configure an ELS Host for Dual TCP/IP
1. Update the routing tables of the IBM mainframe by following the ELS
documentation. If there is a single network interface on the IBM mainframe, no
special routing is required on the host.
2. At the IBM mainframe console or PARMLIB, use the
LMUPATH
control statement to
define network LMU attachments.