ZyXEL P-660HN-T1A Support Guide - Page 73

Source-Based Routing, Quality of Service QoS, Cost Savings, Load Sharing

Page 73 highlights

P-660HN Series Support Notes Use IPPR to distribute traffic among multiple paths  Benefits Source-Based Routing - Network administrators can use policy-based routing to direct traffic from different users through different connections. Quality of Service (QoS)- Organizations can differentiate traffic by setting the precedence or TOS (Type of Service) values in the IP header at the periphery of the network to enable the backbone to prioritize traffic. Cost Savings- IPPR allows organizations to distribute interactive traffic on high-bandwidth, high-cost path while using low-path for batch traffic. Load Sharing- Network administrators can use IPPR to distribute traffic among multiple paths.  How does the IPPR work? A policy defines the matching criteria and the action to take when a packet meets the criteria. The action is taken only when all the criteria are met. The criteria include the source address and port, IP protocol (ICMP, UDP, TCP,etc), destination address and port, TOS and precedence (fields in the IP header) and length. The inclusion of length criterion is to differentiate between interactive and bulk traffic. Interactive applications, e.g., Telnet, tend to have short packets, while bulk traffic, e.g., file transfer, tends to have large packets. The actions that can be taken include routing the packet to a different gateway (and hence the outgoing interface) and the TOS and precedence fields in the IP header. IPPR follows the existing packet filtering facility in style and in implementation. The policies are divided into sets, where related policies are grouped together. A use defines the policies before applying them to an 73 All contents copyright © 2010 ZyXEL Communications Corporation.

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118

P-660HN Series Support Notes
73
All contents copyright © 2010 ZyXEL Communications Corporation.
Use IPPR to distribute traffic among multiple paths
Benefits
Source-Based Routing
-
Network administrators can use policy-based
routing to direct traffic from different users through different connections.
Quality of Service (QoS)-
Organizations can differentiate traffic by setting the
precedence or TOS (Type of Service) values in the IP header at the periphery
of the network to enable the backbone to prioritize traffic.
Cost Savings
- IPPR allows organizations to distribute interactive traffic on
high-bandwidth, high-cost path while using low-path for batch traffic.
Load Sharing
- Network administrators can use IPPR to distribute traffic
among multiple paths.
How does the IPPR work?
A policy defines the matching criteria and the action to take when a packet
meets the criteria. The action is taken only when all the criteria are met. The
criteria include the source address and port, IP protocol (ICMP, UDP, TCP,etc),
destination address and port, TOS and precedence (fields in the IP header)
and length. The inclusion of length criterion is to differentiate between
interactive and bulk traffic. Interactive applications, e.g., Telnet, tend to have
short packets, while bulk traffic, e.g., file transfer, tends to have large packets.
The actions that can be taken include routing the packet to a different gateway
(and hence the outgoing interface) and the TOS and precedence fields in the
IP header. IPPR follows the existing packet filtering facility in style and in
implementation. The policies are divided into sets, where related policies are
grouped together. A use defines the policies before applying them to an