Table of Contents
Advertisement
On T Series, M120, and M320 routers, the source class and destination classes are
not carried across the router fabric. The implications of this are as follows:
Once you enable accounting on an interface, the JUNOS Software maintains packet
counters for that interface, with separate counters for
families. You must then configure the source class and destination class attributes
in policy action statements, which must be included in forwarding-table export
policies.
For a complete discussion about source and destination class accounting profiles,
see the JUNOS Network Management Configuration Guide. For more information about
MPLS, see the JUNOS MPLS Applications Configuration Guide.
Examples: Enabling Source Class and Destination Class Usage
Configure DCU and SCU output on one interface:
Chapter 5: Configuring Protocol Family and Interface Address Properties
On T Series, M120, and M320 routers, SCU and DCU accounting is performed
before the packet enters the fabric.
On T Series, M120, and M320 routers, DCU is performed before output filters
are evaluated. On other M Series routers, DCU is performed after output filters
are evaluated.
If an output filter drops traffic on T Series, M120, and M320 routers, the dropped
packets are included in DCU statistics. If an output filter drops traffic on other
M Series routers, the dropped packets are excluded from DCU statistics.
On T-series, M120, and M320 platforms, the
statements are supported at the
term term-name from]
hierarchy level only for the filter applied to the forwarding
table. On other M-series platforms, these statements are supported.
[edit]
interfaces {
so-6/1/0 {
unit 0 {
family inet {
accounting {
destination-class-usage;
source-class-usage {
output;
}
}
}
}
}
}
destination-class
[edit firewall family family-name filter filter-name
inet
Enabling Source Class and Destination Class Usage
and
source-class
,
, and
protocol
inet6
mpls
223
Advertisement
Table of Contents
