JPS Performance Traps
Table 1 lists the
performance traps for the Juniper Policy Server (JPS).
Table 1: Performance
Traps–JPS
|
|
|
Alarm Threshold Levels
(default values)
|
|
Trap Event
|
Trap ID
|
Text Displayed
|
Critical
|
Major
|
Minor
|
Interval(sec)
|
R/AV
|
jpsHeapUsed
|
250
|
$S:JPS:$D% of Java VM heap is in use. This $L the threshold
of $T%.:$A
|
95%
|
90%
|
80%
|
60
|
AV
|
jpsCmtsAvgSyncTime
|
251
|
$S:JPS:During the last $Ps, the average time this JPS
spent on CMTS synchronizations is $Dms. This $L the threshold of $Tms.:$A
|
900s
|
600s
|
200s
|
60
|
R
|
jpsCmtsAvgDecTime
|
252
|
$S:JPS:During the last $Ps, the average time the CMTS
connection spent on successfully completed DEC/RPT transactions is
$Dms. This $L the threshold of $Tms.:$A
|
3s
|
2s
|
1s
|
60
|
R
|
jpsMsgHdlrProcTime
|
253
|
$S:JPS:During the last $Ps, the average time the JPS
message handler spent on message handling is $Dms. This $L the threshold
of $Tms.:$A
|
10s
|
5s
|
2s
|
60
|
R
|
jpsMsgFlowProcTime
|
254
|
$S:JPS:During the last $Ps, the average time the JPS
message flow spent on message handling is $Dms. This $L the threshold
of $Tms.:$A
|
30s
|
15s
|
6s
|
60
|
R
|
jpsMsgFlowDroppedMsgs
|
255
|
$S:JPS:During the last $Ps, the number of messages dropped
by a JPS message flow is $D. This $L the threshold of $T.:$A
|
1000
|
100
|
1
|
60
|
R
|
Published: 2009-09-10
