Chapter 16: Dynamic Routing Protocols
STANDARD Revision 1.0
C4® CMTS Release 8.3 User Guide
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
546
match ip address
set ip tos
set ip precedence
set ip next-hop
set ip backup-next-hop
set ip interface null 0
Operational Guidelines
The user should be aware of the following:
PBR is also applied to packets destined to IP addresses of the C4/c CMTS. A misconfigured policy could cause the C4/c
CMTS not to receive packets that it should receive.
The C4/c CMTS supports PBR for IPv4 unicast packets only.
The C4/c CMTS does not support PBR for IPv6 packets.
PBR cannot be used on packets coming in from the SCM management 19/0 and 20/0 interfaces.
If a route map matches a packet to an ACL that contains a deny keyword, then the effect of that deny is to cause the
packet to be forwarded using destination-based (not policy-based) routing.
A route map cannot be changed from permit to deny, or from deny to permit. To make such a change you must first
remove the route map, make the change, and add it.
If the same sequence number is used in two route map commands in the same route map, then the first one is
overwritten by the second.
A route map can be created that references an ACL before the ACL is defined. If the route map is used before the ACL is
defined, then the packet will be routed normally.
The only set interface statement supported is set interface null 0, which is used to drop packets.
PBR can work in conjunction with multiple VRFs. PBR is configured on a sub-interface which may be assigned to a VRF
also. If a next-hop is used in the route-map command, the next-hop IP needs to be in the same VRF (or the default VRF)
as the ingress interface. If no next-hop is specified for the route-map (e.g., a set IP ToS is used without a set next-hop),
the packet is routed using the normal VRF routing mechanism.
Counts
The C4/c CMTS keeps packet and byte counts for the following events: