Dell 3-DNS, Administrator'S Manual

Page: 37 / 165

Planning the 3-DNS Configuration
3-DNS
®
Administrator Guide 2 - 9
◆ 3-DNS Controllers communicating with other 3-DNS Controllers
To allow 3-DNS Controllers to communicate with each other, you must
set up
ssh and scp utilities.
◆ 3-DNS Controllers communicating with BIG-IP systems and
EDGE-FX systems
To allow the 3-DNS Controller to communicate with BIG-IP systems
and EDGE-FX systems, you address the same
ssh issues.
◆ 3-DNS Controllers communicating with big3d agents
To allow communications between big3d agents and the 3-DNS
Controller, you need to configure iQuery ports on any 3-DNS
Controllers, BIG-IP systems, and EDGE-FX systems that run the
big3d
agent.
Setting up communication between crypto and non-crypto systems
The 3-DNS Controllers in your network need to communicate with each
other in order to synchronize configuration and performance data. If you use
exclusively crypto 3-DNS Controllers (those that use the SSH protocol) the
communication tools set up by the Setup utility are all you need.
If your network is a mixed environment, that is, composed of both crypto
and non-crypto systems, you need to enable the
rsh and rcp utilities on the
crypto systems. Though the rsh and rcp utilities come pre-installed on the
crypto systems, you must explicitly enable these utilities. You can enable
the utilities using the Setup utility. Table 2.1 shows the ports and protocols
used for SSH and RSH communications between crypto and non-crypto
systems.
Setting up data collection with the big3d agent
The big3d agent collects performance information from other 3-DNS
Controllers, BIG-IP systems, and EDGE-FX systems on behalf of the
3-DNS Controller you are configuring. The 3-DNS Controller then uses this
performance data for load balancing. The
big3d agent uses factories to
manage the data collection. For detailed information on configuring the
From To Protocol
From
Port To
Port
Connection
Crypto Crypto TCP <1024 22 SSH/SCP
Crypto Non-crypto TCP <1024 514 RSH/RCP
Non-crypto Crypto TCP <1024 514 RSH/RCP
Non-crypto Non-crypto TCP <1024 514 RSH/RCP
Table 2.1 SSH and RSH communications ports and protocols