Citrix ByteMobile T1010, Установка, настройка и администрирование

Страница: 90 / 172

3-16 T-Series Traffic Director Installation, Configuration and Administration Guide
Chapter 3 Basic T1000/Unison Load-Balancing Configuration
> bind vlan 100 -IPAddress 169.254.0.100 255.255.255.0
Done
> bind vlan 200 -IPAddress 169.254.64.100 255.255.255.0
Done
> bind vlan 151 -IPAddress 172.16.112.101 255.255.255.0
Done
> bind vlan 251 -IPAddress 172.16.113.101 255.255.255.0
Done
Adding Routes
The T1000 requires routes to next-hop gateways on the wireless and Internet sides of the
network.
Use the add route command to add routes from the T1000 to the next hop gateways. The
add route command has the following basic syntax:
add route network netmask gateway
Using the example configuration:
> add route 10.200.0.0 255.254.0.0 172.16.112.65
Done
> add route 192.168.40.0 255.255.255.0 172.16.113.65
Done
Configuring Policy Based Routing (PBR)
The T1000 has a policy based routing (PBR) feature that is typically used to simplify
routing decisions. In most Unison deployments routing decisions are keyed against the
incoming VLAN. For example, in the reference outlined in Figure 3-2:
• Incoming traffic on ingress VLAN 151 is routed towards the 172.16.113.65 router on
egress VLAN 251.
• Incoming traffic on egress VLAN 251 is routed towards the 172.16.112.65 router on
ingress VLAN 151.
The benefits of PBR are more obvious in an actual deployment rather than the example
configuration outlined in this guide. Specifically, in case of multiple client subnets
(sometimes a dozen or more), a small set of PBR entries may substitute a number of static
routes (one per client subnet), simplifying both the routing logic and the T1000
configuration.
Using the example configuration:
>
add ns pbr pbr_ingress ALLOW -vlan 151 -nextHop 172.16.113.65 -priority 99
Done
> add ns pbr pbr_egress ALLOW -vlan 251 -nextHop 172.16.112.65 -priority 100
Done
>
apply ns pbrs
Done