-
Notifications
You must be signed in to change notification settings - Fork 650
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Update Juniper module #1351
Update Juniper module #1351
Conversation
Signed-off-by: Jacob Winther <jacob@9.nz>
Signed-off-by: Jacob Winther <jacob@9.nz>
generator/generator.yml
Outdated
- JUNIPER-DOM-MIB::jnxDomCurrentTxLaserOutputPowerHighAlarmThreshold | ||
- JUNIPER-DOM-MIB::jnxDomCurrentTxLaserOutputPowerLowAlarmThreshold | ||
- JUNIPER-DOM-MIB::jnxDomCurrentTxLaserOutputPowerHighWarningThreshold | ||
- JUNIPER-DOM-MIB::jnxDomCurrentTxLaserOutputPowerLowWarningThreshold |
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.
I wonder if some of this should be a separate module, like juniper_optics
.
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.
I used to break that out but found I keep on telling people they needed to add it, so I figure making it default makes it easier. It should only impact devices that have optics that support DOM.
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.
I also used JUNIPER-DOM-MIB::jnxDomCurrentLaneTxLaserBiasCurrent
to alert on "dying" optics when they start drawing more and more current.
We also used separate modules for basic juniper (switches,routers...) and more specific for devices with DOM support.
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.
I used to have jnxDomCurrentLaneTxLaserBiasCurrent but removed it because I didn't use it. I can see add that.
Regarding switches with DOM support, is there much benefit in removing it. Even small switches often have DOM for uplinks.
Happy to break DOM out though if that's the preference. My goal was to make life easier for users.
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.
Since we added multi-module scrapes, I think splitting makes more sense. Users can request scrapes like if_mib,juniper,juniper_optics
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.
Ok I'll make the changes tonight.
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.
I've broken optics out into it's own module, and included jnxDomCurrentLaneTxLaserBiasCurrent.
I also remove the threshold items as you can look at the jnxDomCurrentWarnings and jnxDomCurrentAlarms for threshold breaches, rather than calculating manually.
Signed-off-by: Jacob Winther <jacob@9.nz>
Signed-off-by: Jacob Winther <jacob@9.nz>
Signed-off-by: Jacob Winther <jacob@9.nz>
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.
Fine for me
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.
Thanks
Update Juniper module to include FRU, DOM and basic subscriber count. Also use EnumAsStateSet to support alerting.