-
Notifications
You must be signed in to change notification settings - Fork 272
Open
Milestone
Description
I'm checking with 4.35.1F and it looks like priority-flow-control block is now rendered right after qos map .*, before any class-map .* or policy-map .*s are rendered:
+qos rewrite dscp
+qos random-detect ecn allow non-ect chip-based
+qos tx-queue shape rate percent adaptive
+qos map cos 1 4 to traffic-class 2
+qos map dscp 8 9 10 11 12 13 14 15 16 17 19 21 23 24 25 27 29 31 32 33 35 37 39 40 41 42 43 44 45 47 49 50 51 52 53 54 55 57 58 59 60 61 62 63 to traffic-class 1
+qos map dscp 18 20 22 26 28 30 34 36 38 to traffic-class 4 drop-precedence 2
+qos map exp 0 to traffic-class 0
+qos map traffic-class 2 4 5 to cos 7
+qos map traffic-class 1 to dscp 56
+qos map traffic-class 6 to uc-tx-queue 2
+priority-flow-control all off
+priority-flow-control pause watchdog default timeout 0.05
+priority-flow-control pause watchdog default recovery-time 1.22
+priority-flow-control pause watchdog default polling-interval 10.001
+priority-flow-control pause watchdog action drop
+!
+class-map type qos match-any CM_IPv6_ACCESS_GROUP
+ match ipv6 access-group ACL_REPLICATION_LD
+!
+class-map type qos match-any CM_REPLICATION_LD
+ match ip access-group ACL_REPLICATION_LD
+!
+class-map type qos match-any CM_REPLICATION_LD2
+ match vlan 200 0xfff
+!
+class-map type qos match-any CM_REPLICATION_LD3
+ match cos 3
+!
+class-map type qos match-any COS_RANGE
+ match vlan 1-3
+!
+class-map type qos match-any DSCP_TEST_1
+ match dscp af11 ecn ect-ce
+!
Originally posted by @alexeygorbunov in #6318 (comment)
Metadata
Metadata
Assignees
Labels
No labels