Still having issues with CoS, specifically my classifier. If I
explicitly force all traffic on a given logical unit to
forwarding-class ef-high-fc (at [edit class-of-service interface]
heirarchy), it works as expected. All traffic on that interface ends
up in the right forwarding class. However, when using the classifier
below to (try to) do the same thing, no traffic is reclassified. All
of it ends up in my be-low-fc queues. Is there a glaring error in the
config below? I believe I've narrowed it down to the classifier being
the problem.
I'm in the process of locating a sniffer to see if it actually sees
the 802.1p markings that my test sets are sending (sending 5 in one
direction, 2 in the other), in case the Juniper isn't seeing what it
needs to. Any ideas are appreciated.
classifiers {
ieee-802.1 trial {
forwarding-class be-high-fc {
loss-priority low code-points [ be-low-bits be-high-bits ];
}
forwarding-class af-low-fc {
loss-priority low code-points [ af-low-bits af-high-bits
ef-low-bits ];
}
forwarding-class ef-low-fc {
loss-priority low code-points [ ef-high-bits nc-low-bits
nc-high-bits ];
}
}
}
code-point-aliases {
ieee-802.1 {
be-low-bits 000;
be-high-bits 001;
af-low-bits 010;
af-high-bits 011;
ef-low-bits 100;
ef-high-bits 101;
nc-low-bits 110;
nc-high-bits 111;
}
}
interfaces {
ge-7/0/7 {
unit 100 {
scheduler-map env-mpls-core-scheduler;
input-scheduler-map env-mpls-core-scheduler;
classifiers {
ieee-802.1 trial;
}
}
}
ge-7/2/7 {
unit 100 {
scheduler-map env-mpls-core-scheduler;
input-scheduler-map env-mpls-core-scheduler;
classifiers {
ieee-802.1 trial;
}
}
}
}
_______________________________________________
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp
