[Contents] [Prev] [Next] [Index] [Report an Error]

protocol

See the following sections:

protocol (Rewrite Rules)

Syntax

protocol protocol-types;

Hierarchy Level

[edit class-of-service interfaces interface-name unit logical-unit-number rewrite-rules exp rewrite-name],
[edit class-of-service interfaces interface-name unit logical-unit-number rewrite-rules dscp rewrite-name],
[edit class-of-service interfaces interface-name unit logical-unit-number rewrite-rules inet-prec rewrite-name]

Release Information

Statement introduced before JUNOS Release 7.4.

Option for dscp and inet-prec introduced in JUNOS Release 8.4.

Description

Apply a rewrite rule to MPLS packets only, and write the CoS value to MPLS headers only; or apply a rewrite rule to MPLS and IPv4 packets, and write the CoS value to MPLS and IPv4 headers.

Options

protocol-types can be one of the following:

mpls—Apply a rewrite rule to MPLS packets and write the CoS value to MPLS headers.

mpls-inet-both—Apply a rewrite rule to VPN MPLS packets with IPv4 payloads. On T-series, MX-series, and M320 or M120 platforms, write the CoS value to the MPLS and IPv4 headers. On M-series routing platforms, initialize all ingress MPLS LSP packets with IPv4 payloads with 000 code points for the MPLS EXP value, and the configured rewrite code point for IP precedence.

mpls-inet-both-non-vpn—Apply a rewrite rule to non-VPN MPLS packets with IPv4 payloads. On T-series, MX-series, and M320 or M120 platforms, write the CoS value to the MPLS and IPv4 headers. On M-series routing platforms, initialize all ingress MPLS LSP packets with IPv4 payloads with 000 code points for the MPLS EXP value, and the configured rewrite code point for IP precedence.

Usage Guidelines

See Rewriting MPLS and IPv4 Packet Headers.

Required Privilege Level

interface—To view this statement in the configuration.

interface-control—To add this statement to the configuration.

protocol (Schedulers)

Syntax

protocol (any | non-tcp | tcp);

Hierarchy Level

[edit class-of-service schedulers scheduler-name drop-profile-map]

Release Information

Statement introduced before JUNOS Release 7.4.

Description

Specify the protocol type for the specified scheduler.

Options

any—Accept any protocol type.

non-tcp—Accept any protocol type other than TCP/IP.

tcp—Accept only TCP/IP protocol.

Usage Guidelines

See Configuring a Scheduler.

Required Privilege Level

interface—To view this statement in the configuration.

interface-control—To add this statement to the configuration.


[Contents] [Prev] [Next] [Index] [Report an Error]