Dell PowerSwitch S4112F-ON OS10 Enterprise Edition User Guide Release 10.4.1.0 - Page 602

Check match routes OS10(config)# route-map test permit 1 0S10(conf-route-map)# match tag 250000 OS10(conf-route-map)# set weight 100 Set conditions There is no limit to the number of set commands per route map, but keep the number of set filters in a route-map low. The set commands do not require a corresponding match command. • Enter the IP address in A.B.C.D format of the next-hop for a BGP route update in ROUTE-MAP mode. set ip next-hop address • Enter an IPv6 address in A::B format of the next-hop for a BGP route update in ROUTE-MAP mode. set ipv6 next-hop address • Enter the range value for the BGP route's LOCAL_PREF attribute in ROUTE-MAP mode, from 0 to 4294967295. set local-preference range-value • Enter a metric value for redistributed routes in ROUTE-MAP mode, from 0 to 4294967295. set metric {+ | - | metric-value} • Enter an OSPF type for redistributed routes in ROUTE-MAP mode. set metric-type {type-1 | type-2 | external | internal} • Enter an ORIGIN attribute in ROUTE-MAP mode. set origin {egp | igp | incomplete} • Enter a tag value for the redistributed routes in ROUTE-MAP mode, from 0 to 4294967295. set tag tag-value • Enter a value as the route's weight in ROUTE-MAP mode, from 0 to 65535. set weight value Check set conditions OS10(config)# route-map ip permit 1 OS10(conf-route-map)# match metric 2567 continue Clause Only BGP route-maps support the continue clause. When a match is found, set clauses run and the packet is forwarded - no routemap processing occurs. If you configure the continue clause without configuring a module, the next sequential module processes. If you configure the continue command at the end of a module, the next module processes even after a match is found. The example shows a continue clause at the end of a route-map module - if a match is found in the route-map test module 10, module 30 processes. Route-map continue clause OS10(config)# route-map test permit 10 OS10(conf-route-map)# continue 30 ACL flow-based monitoring Flow-based monitoring conserves bandwidth by selecting only the required flow to be mirrored instead of mirroring entire packets from an interface. This feature is available for L2 and L3 ingress traffic. Specify flow-based monitoring using ACL rules. Flow-based monitoring copies incoming packets that match the ACL rules applied on the ingress port and forwards (mirrors) them to another port. The source port is the monitored port (MD), and the destination port is the monitoring port (MG). 602 Access Control Lists