Skip to content
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

Wrong DOM values for xe-* interfaces #178

Closed
fstolba opened this issue Mar 25, 2022 · 0 comments · Fixed by #180
Closed

Wrong DOM values for xe-* interfaces #178

fstolba opened this issue Mar 25, 2022 · 0 comments · Fixed by #180

Comments

@fstolba
Copy link
Contributor

fstolba commented Mar 25, 2022

Running latest master targetting multiple platforms (QFX, EX, MX) on multiple Junos versions.

DOM data from xe-* interfaces is wrong (e.g. junos_interface_diagnostics_laser_rx_dbm shows -inf even though the transceiver is inserted and signal is received, verifiable using show int diagnostics optics). 1G optics act the same.

et-* interfaces look fine, no difference 40/100G or 4 lane/2 lane optics for example.

These lines from the log might be relevant:

junos_exporter[85716]: time="2022-03-24T23:54:25Z" level=error msg="Power: expected element type <rpc-reply> but have <command>" source="junos_collector.go:129"
czerwonk added a commit that referenced this issue Aug 8, 2022
…es-#178

Wrong DOM values for xe-* interfaces #178
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant