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

Timestamps on M-series and T-series Routing Platforms

If your router network includes an Adaptive Services (AS) or MultiServices PIC or a MultiServices DPC, you can enable timestamping of RPM probe messages. The timestamp is applied on the RPM client router (the router that originates the RPM probes). The functionality is not supported on the RPM probe server and applies only to IPv4 traffic. It is supported in the Layer 2 service package on all MultiServices PICs and DPCs and in the Layer 3 service package on AS and MultiServices PICs and MultiServices DPCs.

To configure two-way timestamping on M-series and T-series routing platforms, include the destination-interface statement at the [edit services rpm probe probe-owner test test-name] hierarchy level:




destination-interface sp-fpc/pic/port.logical-unit;

Specify the RPM client router on the adaptive services logical interface by including the rpm statement at the [edit interfaces interface-name unit logical-unit-number] hierarchy level:




rpm client;

The logical interface (unit 0) must be dedicated to the RPM task. It requires configuration of the family inet statement and a /32 address, as shown in the example. This configuration is also needed for other services such as NAT and stateful firewall.

Note: If you configure RPM time stamping on an AS PIC, you cannot configure the source-address statement at the [edit services rpm probe probe-name test test-name] hierarchy level.

To configure one-way timestamping, you must also include the one-way-hardware-timestamp statement at the [edit services rpm probe probe-owner test test-name] hierarchy level:




one-way-hardware-timestamp;

Note: If you configure RPM probes for a services interface (sp-), you need to announce local routes in a specific way for the following routing protocols:

For OSPF, you can announce the local route by including the services interface in the OSPF area. To configure this setting, include the interface sp-fpc/pic/port statement at the [edit protocols ospf area area-number] hierarchy level.
For BGP and IS-IS, you must export interface routes and create a policy that accepts the services interface local route. To export interface routes, include the point-to-point and lan statements at the [edit routing-options interface-routes family inet export] hierarchy level. To configure an export policy that accepts the services interface local route, include the protocol local, rib inet.0, and route-filter sp-interface-ip-address/32 exact statements at the [edit policy-options policy-statement policy-name term term-name from] hierarchy level and the accept action at the [edit policy-options policy-statement policy-name term term-name then] hierarchy level. For the export policy to take effect, apply the policy to BGP or IS-IS with the export policy-name statement at the [edit protocols protocol-name] hierarchy level.

For more information about these configurations, see the JUNOS Policy Framework Configuration Guide or the JUNOS Routing Protocols Configuration Guide.

Routing the probe packets through the AS or MultiServices PIC also enables you to filter the probe packets to particular queues. The following example shows the RPM configuration and the filter that specifies queuing:



services rpm {


probe p1 {


test t1 {
probe-type icmp-ping;
target address 10.8.4.1;
probe-count 10;
probe-interval 10;
test-interval 10;
dscp-code-points af11;
data-size 100;
destination-interface sp-1/2/0.0;
}


}


}
firewall {


filter f1 {


term t1 {


from {
dscp af11;
}




then {
forwarding-class assured-forwarding;
}


}


}


}
interfaces sp-1/2/0 {


unit 0 {
rpm client;


family inet {
address 10.8.4.2/32;


filter {
input f1;
}


}


}


}

For more information about firewall filters, see the JUNOS Policy Framework Configuration Guide; for more information about queuing, see the JUNOS Class of Service Configuration Guide.

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