Method of configuring local policy routing of an AR router

15

The method of configuring local policy routing of an AR router is as follows:
1. Configure IP addresses of different interfaces.
2. Configure a static route.
3. Configure policy-based routing.

For details about the configuration, see the URL: Example for Configuring Local PBR.

Other related questions:
Configure rules of local policy routing on an AR router
Run the system-view command to access the system view. Run the policy-based-routepolicy-name { deny | permit } nodenode-id command to create policy-based routing and policy points. If policy points have been created, access the local policy routing view. By default, no local policy routing or policy point has been created. Note: For packets that matches a rule, permit indicates a policy routing is applied; while deny indicates no policy routing is applied. Repeat the previous command to create multiple policy points for a local policy routing. The policy points are specified based on the node ID. The smaller the node ID, the higher the priority, and corresponding policy is implemented preferentially. Run the if-match aclacl-number command to set ACL rules of IP packets. The command can be implemented once or twice. By default, rules about IP addresses are not configured in local policy routing. Note: If an ACL rule is set to permit, the router implements an action for packets that match the rule. When a policy point is permit, packets that match the rule are routed based on a policy. When a policy point is deny, packets that match the rule are not routed based on a policy, and are forwarded according to the destination IP addresses. If an ACL is configured with rules, packets that do not match any rule are forwarded according to the destination IP addresses. If an ACL rule is set to deny or an ACL is not configured with rules, local policy routing that applies the ACL does not take effect. Therefore, packets are forwarded according to the destination IP addresses. Run the if-match packet-lengthmin-lengthmax-length command to set a length rule of IP packets. By default, length rules of IP packets are not configured in local policy routing.

Method of configuring interface policy routing of an AR router
The roadmap of configuring interface policy routing of an AR router is as follows: 1. Configure a traffic classifier. 2. Configure a traffic behavior (redirection to a next hop or an outbound interface). 3. Configure a traffic policy. 4. Apply the traffic policy to the interface in the inbound direction. Supposed that the intranet is composed of two network segments 1.0 and 2.0, and traffic transmitted over 1.0 is redirected to China Telecom and traffic transmitted over 2.0 is redirected to China Unicom, then the configuration is as follows: # acl number 3001 rule 5 permit ip source 10.1.1.0 0.0.0.255 acl number 3002 rule 5 permit ip source 10.1.2.0 0.0.0.255 # traffic classifier redirect-dx operator or if-match acl 3001 traffic classifier redirect-lt operator or if-match acl 3002 # traffic behavior redirect-dx redirect ip-nexthop 1.1.1.1 traffic behavior redirect-lt redirect ip-nexthop 2.2.2.2 # traffic policy celvluyou classifier redirect-dx behavior redirect-dx classifier redirect-lt behavior redirect-lt # interface GigabitEthernet0/0/1 traffic-policy celvluyou inbound # For details about specific configuration cases, see the URL: Example for Configuring Interface PBR.

Method of configuring smart policy routing of an AR router
The method of configuring smart policy routing of an AR router is as follows: 1. Configure IP addresses of different interfaces. 2. Configure a static route. 3. Configure NQA instances. 4. Configure ACLs that differentiate service flows. 5. Configure routing parameters of smart policy routing on router A. 6. Configure service parameters of smart policy routing. For details about the configuration, see the URL: Example for Configuring SPR.

How to configure local traffic mirroring on AR series routers
By configuring local traffic mirroring, you can replicate specific packets transmitted through an interface to local monitoring devices for analysis and surveillance. Prerequisites Before configuring local traffic mirroring, ensure that the link protocol state of the interface is Up. 1. Configure the local observing interface. Background In local traffic mirroring, monitoring devices are directly connected to the observing interface. It is recommended that other configurations should not be performed on an interface that is configured as the observing interface to prevent its mirroring function from being affected: - If not only the mirroring packets but also the packets of other services are transmitted through the observing interface, the source of the packets cannot be distinguished. - If traffic congests on the observing interface, mirroring packets may be discarded because the priority of the mirroring packets is lower. Procedure Run the system-view command to enter the system view. Run the observe-port interface interface-type interface-number command to configure the local observing interface. 2. Configure traffic mirroring. Background In traffic mirroring, the mirroring interface applies a traffic policy that includes traffic mirroring behavior. Packets that are transmitted through the interface and match the traffic classification rules are replicated to the observing interface. Procedure a. Configure the traffic classifier. Run the system-view command to enter the system view. Run the traffic classifier classifier-name [ operator { and | or } ] command to create a traffic classifier and enter the view of the traffic classifier. Run the if-match command to configure the matching rule of the traffic classifier based on actual requirements. Run the quit command to quit the view of the traffic classifier. b. Configure the traffic behavior. Run the traffic behavior behavior-name command to create traffic behavior and enter the view of the traffic behavior. Run the mirror to observe-port command to mirror traffic that matches the rule to the specified observing interface. Run the quit command to quit the view of the traffic behavior. Run the quit command to quit the system view. c. Configure the traffic policy. Run the system-view command to enter the system view. Run the traffic policy policy-name command to create a traffic policy and enter the view of the traffic policy, or directly enter the view of an existing traffic policy. Run the classifier classifier-name behavior behavior-name command to configure the traffic behavior of specified traffic classifiers in the traffic policy, that is, bind the traffic behavior to the specified traffic classifier. Run the quit command to quit the view of the traffic policy. Run the quit command to quit the system view. d. Apply the traffic policy. Run the system-view command to enter the system view. Run the interface interface-type interface-number [.subinterface-number ] command to enter the interface view. Run the traffic-policy policy-name { inbound | outbound } to apply the traffic policy in the inbound or outbound direction of the interface.

Method used to configure a static route on the AR router
The procedure for configuring static route on the AR router is as follows: - Use command lines. [RouterA] ip route-static 0.0.0.0 0.0.0.0 1.1.4.2 //Configure a default route that is often used at the egress of a small-sized company. The address 1.1.4.2 is the gateway address of the carrier. When the specific route cannot be matched, data flows are forwarded to 1.1.4.2. If the device has only one default route, all the data packets are forwarded to 1.1.4.2 by default. [RouterB] ip route-static 1.1.3.0 255.255.255.0 1.1.4.6 //Configure the route to network segment 1.1.3.0/24. The next hop of the route is 1.1.4.6, which is the specific route but not the default route. Use the web platform. For details, see Example for Configuring IPv4 Static Routes .

If you have more questions, you can seek help from following ways:
To iKnow To Live Chat
Scroll to top