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

Collect Digital Optical Monitoring (DOM) data #1232

Closed
jmbredal opened this issue Jan 17, 2017 · 3 comments
Closed

Collect Digital Optical Monitoring (DOM) data #1232

jmbredal opened this issue Jan 17, 2017 · 3 comments
Labels
enhancement nav-ref Fronted by the NAV user reference committee optical
Milestone

Comments

@jmbredal
Copy link
Collaborator

jmbredal commented Jan 17, 2017

NAV should collect DOM-data from switchports (especially HP).

The DOM-data statistics should be displayed in the port details page.


Imported from Launchpad using lp2gh.

@jmbredal
Copy link
Collaborator Author

jmbredal commented Jan 17, 2017

(by knut-helge-vindheim)
To collect DOM data from HP Procurve switches examples HP2920, 3500, 5400 you first has to update the data using the oid "hpicfXcvrDiagnosticsUpdate"

# Update the snmp DOM-data:
--------------------------

$ snmptranslate -m all -Ln -TdB hpicfXcvrDiagnosticsUpdate
HP-ICF-TRANSCEIVER-MIB::hpicfXcvrDiagnosticsUpdate
hpicfXcvrDiagnosticsUpdate OBJECT-TYPE
  -- FROM       HP-ICF-TRANSCEIVER-MIB
  -- TEXTUAL CONVENTION TruthValue
  SYNTAX        INTEGER {true(1), false(2)}
  MAX-ACCESS    read-write
  STATUS        current
  DESCRIPTION   "This object will cause specific actions
                  depending on the diagnostic support of the
                  transceiver.

                  Transceiver Diagnostic support:

                  None  : No action taken.
                  DOM   : Will update diagnostic information
                          for the transceiver.
                  VCT   : Will update diagnostic information
                          for the transceiver.
                  Other : Vendor specific.

                  The value of the object will be reset after
                  the completion of the update.

                  Please note: VCT and other (cable-diagnostics)
                  may cause a loss of link and take a few second
                  to run for each interface."
::= { iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) hp(11) nm(2) icf(14) hpicfObjects(11) hpicfSwitch(5) hpSwitch(1) hpicfTransceiverMIB(82) hpicfXcvrObjects(1) hpicfXcvrInfo(1) hpicfXcvrInfoTable(1) hpicfXcvrInfoEntry(1) 10 }
snmpset -c<write-password> -v2c rfb-413-sw .1.3.6.1.4.1.11.2.14.11.5.1.82.1.1.1.1.10.46 i 1

or

snmpset -c<write-password> -v2c rfb-413-sw HP-ICF-TRANSCEIVER-MIB::hpicfXcvrDiagnosticsUpdate.46 i 1

When the data are updatet you can collect the data.

An example of collecting the DOM data from the sfp in port B22 on the switch rfb-413-sw

$  snmpwalk -c<read-password> -v2c -m all -Ln rfb-413-sw hpicfTransceiverMIB

or

$ snmpwalk -c<read-password> -v2c -m all -Ln rfb-413-sw .1.3.6.1.4.1.11.2.14.11.5.1.82
HP-ICF-TRANSCEIVER-MIB::hpicfXcvrPortIndex.46 = INTEGER: 46
HP-ICF-TRANSCEIVER-MIB::hpicfXcvrPortDesc.46 = STRING: B22
HP-ICF-TRANSCEIVER-MIB::hpicfXcvrModel.46 = STRING: NON-HP
HP-ICF-TRANSCEIVER-MIB::hpicfXcvrSerial.46 = STRING: F121113003
HP-ICF-TRANSCEIVER-MIB::hpicfXcvrType.46 = STRING: SFP+LRM
HP-ICF-TRANSCEIVER-MIB::hpicfXcvrConnectorType.46 = STRING: LC
HP-ICF-TRANSCEIVER-MIB::hpicfXcvrWavelength.46 = STRING: 1310nm
HP-ICF-TRANSCEIVER-MIB::hpicfXcvrTxDist.46 = STRING: 220m (50um), 220m (62.5um), 220m (50um OM3),
HP-ICF-TRANSCEIVER-MIB::hpicfXcvrDiagnostics.46 = INTEGER: dom(1)
HP-ICF-TRANSCEIVER-MIB::hpicfXcvrDiagnosticsUpdate.46 = INTEGER: false(2)
HP-ICF-TRANSCEIVER-MIB::hpicfXcvrTemp.46 = INTEGER: 40113 thousandths of degrees Celsius
HP-ICF-TRANSCEIVER-MIB::hpicfXcvrVoltage.46 = Gauge32: 32452 hundreds of microvolts
HP-ICF-TRANSCEIVER-MIB::hpicfXcvrBias.46 = Gauge32: 30330 microamps
HP-ICF-TRANSCEIVER-MIB::hpicfXcvrTxPower.46 = INTEGER: -1897 thousandths of dBm
HP-ICF-TRANSCEIVER-MIB::hpicfXcvrRxPower.46 = INTEGER: -5818 thousandths of dBm
HP-ICF-TRANSCEIVER-MIB::hpicfXcvrAlarms.46 = BITS: 00 00 00 00
HP-ICF-TRANSCEIVER-MIB::hpicfXcvrErrors.46 = BITS: 00 00 00 00
HP-ICF-TRANSCEIVER-MIB::hpicfXcvrTempHiAlarm.46 = INTEGER: 75000 thousandths of degrees Celsius
HP-ICF-TRANSCEIVER-MIB::hpicfXcvrTempLoAlarm.46 = INTEGER: -5000 thousandths of degrees Celsius
HP-ICF-TRANSCEIVER-MIB::hpicfXcvrTempHiWarn.46 = INTEGER: 70000 thousandths of degrees Celsius
HP-ICF-TRANSCEIVER-MIB::hpicfXcvrTempLoWarn.46 = INTEGER: 0 thousandths of degrees Celsius
HP-ICF-TRANSCEIVER-MIB::hpicfXcvrVccHiAlarm.46 = Gauge32: 35000 hundreds of microvolts
HP-ICF-TRANSCEIVER-MIB::hpicfXcvrVccLoAlarm.46 = Gauge32: 30800 hundreds of microvolts
HP-ICF-TRANSCEIVER-MIB::hpicfXcvrVccHiWarn.46 = Gauge32: 34800 hundreds of microvolts
HP-ICF-TRANSCEIVER-MIB::hpicfXcvrVccLoWarn.46 = Gauge32: 31000 hundreds of microvolts
HP-ICF-TRANSCEIVER-MIB::hpicfXcvrBiasHiAlarm.46 = Gauge32: 90000 microamps
HP-ICF-TRANSCEIVER-MIB::hpicfXcvrBiasLoAlarm.46 = Gauge32: 2000 microamps
HP-ICF-TRANSCEIVER-MIB::hpicfXcvrBiasHiWarn.46 = Gauge32: 80000 microamps
HP-ICF-TRANSCEIVER-MIB::hpicfXcvrBiasLoWarn.46 = Gauge32: 4000 microamps
HP-ICF-TRANSCEIVER-MIB::hpicfXcvrPwrOutHiAlarm.46 = Gauge32: 14125 tenths of microwatts
HP-ICF-TRANSCEIVER-MIB::hpicfXcvrPwrOutLoAlarm.46 = Gauge32: 1995 tenths of microwatts
HP-ICF-TRANSCEIVER-MIB::hpicfXcvrPwrOutHiWarn.46 = Gauge32: 11220 tenths of microwatts
HP-ICF-TRANSCEIVER-MIB::hpicfXcvrPwrOutLoWarn.46 = Gauge32: 2512 tenths of microwatts
HP-ICF-TRANSCEIVER-MIB::hpicfXcvrRcvPwrHiAlarm.46 = Gauge32: 10000 tenths of microwatts
HP-ICF-TRANSCEIVER-MIB::hpicfXcvrRcvPwrLoAlarm.46 = Gauge32: 100 tenths of microwatts
HP-ICF-TRANSCEIVER-MIB::hpicfXcvrRcvPwrHiWarn.46 = Gauge32: 7943 tenths of microwatts
HP-ICF-TRANSCEIVER-MIB::hpicfXcvrRcvPwrLoWarn.46 = Gauge32: 126 tenths of microwatts
HP-ICF-TRANSCEIVER-MIB::hpicfXcvrDiagnosticsTimeStamp.46 = STRING: Fri Mar 20 13:35:05 2015

VCT data:

HP-ICF-TRANSCEIVER-MIB::hpicfXcvrPhyLinkStatus.46 = INTEGER: down(0)
HP-ICF-TRANSCEIVER-MIB::hpicfXcvrPhySpeed.46 = Gauge32: 10 megabits per second
HP-ICF-TRANSCEIVER-MIB::hpicfXcvrPhyDuplex.46 = INTEGER: half(0)
HP-ICF-TRANSCEIVER-MIB::hpicfXcvrMdiPairACableStatus.46 = INTEGER: unspecified(5)
HP-ICF-TRANSCEIVER-MIB::hpicfXcvrMdiPairACableLength.46 = Gauge32: 0 meters
HP-ICF-TRANSCEIVER-MIB::hpicfXcvrMdiPairADistanceToFault.46 = Gauge32: 0 meters
HP-ICF-TRANSCEIVER-MIB::hpicfXcvrMdiPairAPolaritySwap.46 = INTEGER: unspecified(2)
HP-ICF-TRANSCEIVER-MIB::hpicfXcvrMdiPairASkew.46 = Gauge32: 0 nanoseconds
HP-ICF-TRANSCEIVER-MIB::hpicfXcvrMdiPairBCableStatus.46 = INTEGER: unspecified(5)
HP-ICF-TRANSCEIVER-MIB::hpicfXcvrMdiPairBCableLength.46 = Gauge32: 0 meters
HP-ICF-TRANSCEIVER-MIB::hpicfXcvrMdiPairBDistanceToFault.46 = Gauge32: 0 meters
HP-ICF-TRANSCEIVER-MIB::hpicfXcvrMdiPairBPolaritySwap.46 = INTEGER: unspecified(2)
HP-ICF-TRANSCEIVER-MIB::hpicfXcvrMdiPairBSkew.46 = Gauge32: 0 nanoseconds
HP-ICF-TRANSCEIVER-MIB::hpicfXcvrMdiPairCCableStatus.46 = INTEGER: unspecified(5)
HP-ICF-TRANSCEIVER-MIB::hpicfXcvrMdiPairCCableLength.46 = Gauge32: 0 meters
HP-ICF-TRANSCEIVER-MIB::hpicfXcvrMdiPairCDistanceToFault.46 = Gauge32: 0 meters
HP-ICF-TRANSCEIVER-MIB::hpicfXcvrMdiPairCPolaritySwap.46 = INTEGER: unspecified(2)
HP-ICF-TRANSCEIVER-MIB::hpicfXcvrMdiPairCSkew.46 = Gauge32: 0 nanoseconds
HP-ICF-TRANSCEIVER-MIB::hpicfXcvrMdiPairDCableStatus.46 = INTEGER: unspecified(5)
HP-ICF-TRANSCEIVER-MIB::hpicfXcvrMdiPairDCableLength.46 = Gauge32: 0 meters
HP-ICF-TRANSCEIVER-MIB::hpicfXcvrMdiPairDDistanceToFault.46 = Gauge32: 0 meters
HP-ICF-TRANSCEIVER-MIB::hpicfXcvrMdiPairDPolaritySwap.46 = INTEGER: unspecified(2)
HP-ICF-TRANSCEIVER-MIB::hpicfXcvrMdiPairDSkew.46 = Gauge32: 0 nanoseconds
HP-ICF-TRANSCEIVER-MIB::hpicfXcvrMdiPairABSwap.46 = INTEGER: unspecified(2)
HP-ICF-TRANSCEIVER-MIB::hpicfXcvrMdiPairCDSwap.46 = INTEGER: unspecified(2)
HP-ICF-TRANSCEIVER-MIB::hpicfXcvrDiagnosticsTimeTicks.46 = Timeticks: (10704102) 1 day, 5:44:01.02 centi-seconds
HP-ICF-TRANSCEIVER-MIB::hpicfXcvrManufacDate.46 = STRING: 121122

Regard
Knut-Helge Vindheim

@lunkwill42
Copy link
Member

The relation to #1211 here is an important one: For Cisco equipment, we largely have the DOM values already - we just lack a way to associate the sensor values to the interface objects in our data model.

@lunkwill42 lunkwill42 changed the title collect DOM-data Collect Digital Optical Monitoring (DOM) data Nov 8, 2017
@lunkwill42 lunkwill42 added this to the 4.8.0 milestone Nov 8, 2017
@lunkwill42
Copy link
Member

Support for Juniper and Cisco has been implemented in time for 4.8.0, but HP is still missing.

Closing this issue now, and adding #1609 to track the HP implementation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement nav-ref Fronted by the NAV user reference committee optical
Projects
None yet
Development

No branches or pull requests

2 participants