Juniper JUNOS OS 10.4 - RELEASE NOTES REV 5 Release Note page 22

Hide thumbs Also See for JUNOS OS 10.4 - RELEASE NOTES REV 5:
Table of Contents

Advertisement

JUNOS OS 10.4 Release Notes
22
not available for per Packet Forwarding Engine instances. To configure the sampling
of traffic for billing purposes, include the
statement at the
[edit forwarding-options sampling family (inet | inet6) output
flow-server server-name version version-number]
billing functionality, include the
flow-monitoring version9 template template-name]
template fields, see the Junos OS Services Interfaces Configuration Guide. You can apply
the existing destination class usage (DCU) policy option configuration for use with this
feature.
In addition, the MPLS top label IP address is added as a new field in the existing
MPLS-IPv4 flow template. You can use this field to gather MPLS forwarding equivalence
class (FEC) -based traffic information for MPLS network capacity planning. These
ALGs that use Junos Services Framework (JSF) (M Series) is a PIC-only feature applied
on sampled traffic and collected by the services PIC or DPC. You can define it for either
global or per Packet Forwarding Engine instances for MPLS traffic.
The
show services accounting aggregation template
updated to include new output fields that reflect the additional functionality.
[Services Interfaces, System Basics and Services Command Reference]
Support for the RPM timestamp on the Services SDK (M Series, MX Series, and T
Series)—Real-time performance monitoring (RPM), which has been supported on the
Adaptive Services (AS) interface, is now supported by the Services SDK. RPM is
supported on all platforms and service PICs that support the Services SDK.
RPM timestamping is needed to account for any latency in packet communications.
You can apply timestamps on the client, the server, or both the client and server. RPM
timestamping is supported only with the
and
udp-ping-timestamp
probe types.
To specify the Services SDK interface, include the
the
[edit services rpm probe probe-owner test test-name]
destination-interface ms-fpc/pic/port.logical-unit-number;
To specify the RPM client router and the RPM server router, include the
at the
[edit interfaces interface-name unit logical-unit-number]
rpm (client | server);
To enable RPM on the Services SDK on the AS interface, configure the
, and
policy-db-size
package
pic-number adaptive-services service-package extension-provider]
the Services SDK,
package-name
.
jservices-rpm
user@host# show chassis
fpc 1 {
pic 2 {
adaptive-services {
service-package {
extension-provider {
control-cores 1;
template as-peer-billing-template-name
hierarchy level. To define the peer-AS
peer-as-billing-template
hierarchy level. For a list of the
operational command has been
,
icmp-ping
icmp-ping-timestamp
destination-interface
statements at the
[edit chassis fpc slot-number pic
in the
package package-name
Copyright © 2011, Juniper Networks, Inc.
statement at the
[edit services
,
udp-ping
statement at
hierarchy level:
statement
rpm
hierarchy level:
object-cache-size
hierarchy level. For
statement is
,
,

Advertisement

Table of Contents
loading

This manual is also suitable for:

Junos os 10.4

Table of Contents