That's what my "fixed port classifier" does - any packet entering the
given port is assigned a FC:
class-of-service {
interfaces {
ge-0/0/0 { ### ingress untagged interface for Internet traffic
unit 0 {
forwarding-class be1;
}}
Then this FC is matched on egress port and 802.1p bits are rewritten:
ge-1/0/0 { ### egress tagged interface for Internet traffic
unit 0 {
rewrite-rules {
ieee-802.1 test1; }}}}
On 24/06/2015 07:34, Victor Sudakov wrote:
Yes but there should be a way to say "any packet enering this untagged
port should be processed as if it has such and such CoS value."
Alexander Arseniev wrote:
Not on untagged ports - IEEE 802.1 PCP bits are only present in tagged
frames.
Thanks
Alex
On 23/06/2015 12:47, Victor Sudakov wrote:
Alexander Arseniev wrote:
On 17/06/2015 15:45, Victor Sudakov wrote:
Would you care to give a simple example?
Of course. Please try the below and see if it works for You:
While trying to implement your example, I have come across something
called a classifier:
admin@sw-kedr> show class-of-service classifier type ieee-802.1
Classifier: ieee8021p-default, Code point type: ieee-802.1, Index: 11
Code point Forwarding class Loss priority
000 best-effort low
001 best-effort low
010 best-effort low
admin@sw-kedr> show class-of-service interface ge-0/0/12.0
Logical interface: ge-0/0/12.0, Index: 81
Object Name Type Index
Classifier ieee8021p-untrust untrust 16
Can I possibly define my own ieee-802.1 classifier and apply it on ingress?
_______________________________________________
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp
