Chapter 7 Route

7.2.2 Policy Route Command Example

The following commands create two address objects (TW_SUBNET and GW_1) and insert a policy that routes the packets (with the source IP address TW_SUBNET and any destination IP address) through the interface ge1 to the next-hop router GW_1. This route uses the IP address of the outgoing interface as the matched packets’ source IP address.

Router(config)# address-object TW_SUBNET 192.168.2.0 255.255.255.0 Router(config)# address-object GW_1 192.168.2.250 Router(config)# policy insert 1

Router(policy-route)# description example Router(policy-route)# destination any Router(policy-route)# interface ge1 Router(policy-route)# next-hop gateway GW_1 Router(policy-route)# snat outgoing-interface Router(policy-route)# source TW_SUBNET Router(policy-route)# exit Router(config)# show policy-route 1

index: 1 active: yes description: example user: any schedule: none interface: ge1 tunnel: none sslvpn: none source: TW_SUBNET destination: any DSCP code: any service: any nexthop type: Gateway nexthop: GW_1

nexthop state: Not support

auto destination: no

bandwidth: 0

bandwidth priority: 0

maximize bandwidth usage: no

SNAT: outgoing-interface

DSCP marking: preserve

amount of port trigger: 0 Router(config)#

7.3 IP Static Route

The NXC has no knowledge of the networks beyond the network that is directly connected to the NXC. For instance, the NXC knows about network N2 in the following figure through gateway R1. However, the NXC is unable to route a packet to network N3 because it doesn't know that there is a route through the same gateway R1 (via gateway R2). The static routes are for you to tell the NXC about the networks beyond the network connected to the NXC directly.

 

69

NXC CLI Reference Guide