Filter
Top Products
190
Intel
®
NetStructure™ 480T Routing Switch User Guide
Policy-Based Routing and Route Load-Sharing
Policy-based routing is used to alter the normally calculated next-
hop route, which is based on the route table. This same alteration
can also load-share across multiple routers. It implies a set of rules
or policies that take precedence over information in the route table.
These policies can perform a flow-redirection to different next-hop
addresses based on:
• IP source address and mask
• IP destination address and mask
• Layer 4 destination port
In the event that the next-hop address (or addresses) becomes
unavailable, the 480T routing switch will route the traffic normally.
Several rules may be defined; the precedence of rules is determined
by best match of the rule to the packet. If no rule is satisfied, no
redirection occurs.
There are two types of commands you can use to set up policy-
based routing. One configures the redirection rule(s) and the other
configures the next-hop IP address(es):
create flow-redirect <flow_rule_name> [tcp | udp]
destination [<ip_address>/<mask> | any] [ip-port
[<L4_port> | any]] source [<ip_address>/<mask> |
any]
configure flow-redirect <flow_rule_name> [add |
delete] next-hop <ip_address>
If multiple next-hop addresses are defined, traffic satisfying the rule
is load-shared across the next-hop addresses based on destination IP
address.
If next-hop address(es) fail (do not respond to ICMP pings), the
switch will resume normal routing.
Using policy-based routing
has no impact on switch
performance.
To show configuration and status of flow redirection rules, use the
command:
show flow-redirect [<flow_rule_name | <cr>]