3-26
T-Series Traffic Director Installation, Configuration and Administration Guide
Chapter 3 Basic T1000/Unison Load-Balancing Configuration
The above sequence of events would effectively cause the cluster to be inoperable. Wireless
clients are unreachable, since the active T1000 cannot communicate to them, and there is no
hard failure that would result in a failover event to T1000-2 and restore said communication.
This issue can be alleviated with the introduction of route monitors and associating them
with the HA node status.
First, introduce one route monitor for each of the next hop routers. In most cases next-hop
routers will disallow or throttle ICMP messages so an ARP monitor is recommended:
>
add route 172.16.112.0 255.255.255.0 172.16.112.65 -msr ENABLED -monitor arp
Done
>
add route 172.16.113.0 255.255.255.0 172.16.113.65 -msr ENABLED -monitor arp
Done
Afterwards, bind these to monitors to the HA node status:
>
bind HA node -routeMonitor 172.16.112.0 255.255.255.0
Done
>
bind HA node -routeMonitor 172.16.113.0 255.255.255.0
Done
These commands will allow the primary T1000 to constantly monitor the next hop routers.
In case of a failure to communicate with any of them a failover event will be initiated to the
secondary unit.
Configuring Source NAT (SNAT)
The T1000 allows for source NAT (SNAT) of traffic in order to change the subscriber's
private IP address/port into a public IP address/port for packets leaving the network,
preventing Internet servers from responding directly to the clients. Specifically, when the
T1000 receives a request from the client, and if the client IP address in the request is defined
for SNAT, the system translates the source IP address of the incoming packet to the SNAT
address, which will be one of the configured egress IP addresses.
Note:
This SNAT configuration supports only L3-L4, and will work with TCP and
UDP protocols. It does not support any application layer features that require L7
NAT intelligence.
SNAT configuration leverages the net profile and vserver features of the T1000. The
following configuration enables SNAT for all client traffic, mapping the 256K private IP
address range (10.200.0.0/15) to sixteen public IP addresses (172.16.113.(1-16)). This
configuration has the following steps:
1.
Create a net profile that maps to the public IPs you want to use.
2.
Bind net profile to the existing egress-side service.
3.
Create bypass ingress-side-vserver.
This steps are described in the sections that follow.
Summary of Contents for ByteMobile T1010
Page 10: ...x T Series Traffic Director Installation Configuration and Administration Guide...
Page 14: ...Contents xiv T Series Traffic Director Installation Configuration and Administration Guide...
Page 172: ...Index Index 4 T Series Traffic Director Installation Configuration and Administration Guide...
