-
Notifications
You must be signed in to change notification settings - Fork 575
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
NMS-7553: Add Juniper SRX flow performance monitoring and default thresholds #242
Conversation
Added configuration to collect, graph and threshold on Juniper SRX router's jnxJsSPUMonitoringCurrentFlowSession OID. Background: When the number of tracked sessions reach the router's maximu capacity, the router starts to drop arbitrary sessions (not necessarly inactive ones) when needed to stay below the maximum. This, obviously, creates strange network issues. This can easily happen if you forget to define a timeout for some kind of UDP sessions. Cyrille
<group name="juniper-srx-router" ifType="all"> | ||
<mibObj oid=".1.3.6.1.4.1.2636.3.39.1.12.1.1.1.11" instance="jnxJsSPUMonitoringObjectsTable" alias="jnxJsSPUMonitoringNodeDescr" type="string" /> | ||
<mibObj oid=".1.3.6.1.4.1.2636.3.39.1.12.1.1.1.6" instance="jnxJsSPUMonitoringObjectsTable" alias="jnxJsSPUMonitoringCurrentFlowSession" type="Gauge32" /> | ||
<mibObj oid=".1.3.6.1.4.1.2636.3.39.1.12.1.1.1.7" instance="jnxJsSPUMonitoringObjectsTable" alias="jnxJsSPUMonitoringMaxFlowSession" type="Gauge32" /> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The alias
exceeds 19 character which is the maximum in RRD world.
…haracters aliases
Hi @indigo423 , I fixed the alias length. that should be oK now. |
@StCyr Thanks for this nice enhancement. |
NMS-7553: Add Juniper SRX flow performance monitoring and default thresholds
Added configuration to collect, graph and threshold on Juniper SRX router's jnxJsSPUMonitoringCurrentFlowSession OID.
Background:
When the number of tracked sessions reach the router's maximu capacity, the router starts to drop arbitrary sessions (not necessarly inactive ones) when needed to stay below the maximum. This, obviously, creates strange network issues.
This can easily happen if you forget to define a timeout for some kind of UDP sessions.
JIRA: http://issues.opennms.org/browse/NMS-7553
Todo: