Juniper SRX routing engine load event

Hi,

we're trying to monitor the load of the routing engine on our Juniper SRX. With the UnDP we are measuring the load, 9.1.0.0 being the RE.

We created a new alert to test this row for a value greater then 4.

 

But when we try to test it, it's complaining that this is not a numeric value:

Any idea what might be wrong here.

Regards,

John

  • That it says "Juniper" instead of "Cisco"???????????   

     

    Sorry could not help it   :P

  • looks like the problem is with the generated sql query in dbo.AlertDefinitions:

    SELECT     CustomPollerAssignment.CustomPollerAssignmentID AS NetObjectID, CustomPollerAssignment.AssignmentName AS Name
    FROM         CustomPollerStatus INNER JOIN
                          CustomPollerAssignment ON CustomPollerStatus.CustomPollerAssignmentID = CustomPollerAssignment.CustomPollerAssignmentID LEFT OUTER JOIN
                          CustomPollers ON CustomPollerAssignment.CustomPollerID = CustomPollers.CustomPollerID
    WHERE     (CustomPollers.UniqueName = 'jnxOperatingCPU') AND (CustomPollerStatus.RowID = '9.1.0.0') AND (CustomPollerStatus.Status >= '5')

    Which will give following result:

    3a62088e-8fb8-4f1b-862a-83c5db98278ejnxOperatingCPU on go-tst1-fw01

    I think this should be the query:

    SELECT     Nodes.NodeID AS NetObjectID, Nodes.Caption AS Name
    FROM         Nodes INNER JOIN
                          CustomPollerAssignment ON Nodes.NodeID = CustomPollerAssignment.NodeID INNER JOIN
                          CustomPollerStatus ON CustomPollerAssignment.CustomPollerAssignmentID = CustomPollerStatus.CustomPollerAssignmentID INNER JOIN
                          CustomPollers ON CustomPollerAssignment.CustomPollerID = CustomPollers.CustomPollerID
    WHERE     (CustomPollers.UniqueName = 'jnxOperatingCPU') AND (CustomPollerStatus.RowID = '9.1.0.0') AND (CustomPollerStatus.Status >= '5')

    Will give the following result:

    15go-tst1-fw01

    Is there a way to modify this table by hand and fill it with the correct SQL statement.

    Regards,

    John Grinwis

  • Thanks for letting the community know what you found.

    M

  • it's still not working, when adding the SQL statement by hand in the table we get an error.