Transceiver Power error in fiber interface
Hi
After upgrading to latest observium i start getting loads of following errors. I don't understand is this a threshold set problem or some IOS bug? Can some one please shed some light?
Observium :: Network Observation and Monitoring
Dbm Alarm: sfsw1 Te2/1 Receive Power Sensor - TenGigabitEthernet2/1 Receive Power Sensor is over threshold: -2.5dBm (> -40dBm)
Observium :: Network Observation and Monitoring
Dbm Alarm: sfsw1 Te2/2 Receive Power Sensor - TenGigabitEthernet2/2 Receive Power Sensor is over threshold: -2.6dBm (> -40dBm)
Observium :: Network Observation and Monitoring
Voltage Alarm: sfsw1 Te2/1 Supply Voltage Sensor - TenGigabitEthernet2/1 Supply Voltage Sensor is over threshold: 0V (> 0V)
Observium :: Network Observation and Monitoring
Dbm Alarm: sfsw2 Te2/1 Receive Power Sensor - TenGigabitEthernet2/1 Receive Power Sensor is over threshold: -2.8dBm (> -40dBm)
Observium :: Network Observation and Monitoring
Dbm Alarm: coresw1.aus.edu Te5/4 Receive Power Sensor - TenGigabitEthernet5/4 Receive Power Sensor is over threshold: 0dBm (> -40dBm)
SFSW1#sh interfaces transceiver detail Transceiver monitoring is disabled for all interfaces.
mA: milliamperes, dBm: decibels (milliwatts), NA or N/A: not applicable. ++ : high alarm, + : high warning, - : low warning, -- : low alarm. A2D readouts (if they differ), are reported in parentheses. The threshold values are calibrated.
High Alarm High Warn Low Warn Low Alarm Temperature Threshold Threshold Threshold Threshold Port (Celsius) (Celsius) (Celsius) (Celsius) (Celsius) ---------- ------------------ ---------- --------- --------- --------- Te2/1 29.5 ++ 0.0 0.0 0.0 0.0 Te2/2 29.1 ++ 0.0 0.0 0.0 0.0
High Alarm High Warn Low Warn Low Alarm Voltage Threshold Threshold Threshold Threshold Port (Volts) (Volts) (Volts) (Volts) (Volts) ---------- --------------- ---------- --------- --------- --------- Te2/1 0.00 0.00 0.00 0.00 0.00 Te2/2 0.00 0.00 0.00 0.00 0.00
High Alarm High Warn Low Warn Low Alarm Current Threshold Threshold Threshold Threshold Port (milliamperes) (mA) (mA) (mA) (mA) ---------- ----------------- ---------- --------- --------- --------- Te2/1 6.1 ++ 0.0 0.0 0.0 0.0 Te2/2 6.7 ++ 0.0 0.0 0.0 0.0
Optical High Alarm High Warn Low Warn Low Alarm Transmit Power Threshold Threshold Threshold Threshold Port (dBm) (dBm) (dBm) (dBm) (dBm) ---------- ----------------- ---------- --------- --------- --------- Te2/1 -2.9 ++ -40.0 -40.0 -40.0 -40.0 Te2/2 -2.6 ++ -40.0 -40.0 -40.0 -40.0
Optical High Alarm High Warn Low Warn Low Alarm Receive Power Threshold Threshold Threshold Threshold Port (dBm) (dBm) (dBm) (dBm) (dBm) ---------- ----------------- ---------- --------- --------- --------- Te2/1 -2.5 ++ -40.0 -40.0 -40.0 -40.0 Te2/2 -2.6 ++ -40.0 -40.0 -40.0 -40.0
Thanks
Disable all of the alerts using the config.inc.php variable. They're not reliable.
adam.
On 18/06/2012 07:31, Zafar Pravaiz wrote:
Hi
After upgrading to latest observium i start getting loads of following errors. I don't understand is this a threshold set problem or some IOS bug? Can some one please shed some light?
Observium :: Network Observation and Monitoring
Dbm Alarm: sfsw1 Te2/1 Receive Power Sensor - TenGigabitEthernet2/1 Receive Power Sensor is over threshold: -2.5dBm (> -40dBm)
Observium :: Network Observation and Monitoring
Dbm Alarm: sfsw1 Te2/2 Receive Power Sensor - TenGigabitEthernet2/2 Receive Power Sensor is over threshold: -2.6dBm (> -40dBm)
Observium :: Network Observation and Monitoring
Voltage Alarm: sfsw1 Te2/1 Supply Voltage Sensor - TenGigabitEthernet2/1 Supply Voltage Sensor is over threshold: 0V (> 0V)
Observium :: Network Observation and Monitoring
Dbm Alarm: sfsw2 Te2/1 Receive Power Sensor - TenGigabitEthernet2/1 Receive Power Sensor is over threshold: -2.8dBm (> -40dBm)
Observium :: Network Observation and Monitoring
Dbm Alarm: coresw1.aus.edu Te5/4 Receive Power Sensor - TenGigabitEthernet5/4 Receive Power Sensor is over threshold: 0dBm (> -40dBm)
SFSW1#sh interfaces transceiver detail Transceiver monitoring is disabled for all interfaces.
mA: milliamperes, dBm: decibels (milliwatts), NA or N/A: not applicable. ++ : high alarm, + : high warning, - : low warning, -- : low alarm. A2D readouts (if they differ), are reported in parentheses. The threshold values are calibrated.
High Alarm High Warn Low Warn Low Alarm Temperature Threshold Threshold Threshold ThresholdPort (Celsius) (Celsius) (Celsius) (Celsius) (Celsius)
Te2/1 29.5 ++ 0.0 0.0 0.0 0.0 Te2/2 29.1 ++ 0.0 0.0 0.0 0.0
High Alarm High Warn Low Warn Low Alarm Voltage Threshold Threshold Threshold ThresholdPort (Volts) (Volts) (Volts) (Volts) (Volts)
Te2/1 0.00 0.00 0.00 0.00 0.00 Te2/2 0.00 0.00 0.00 0.00 0.00
High Alarm High Warn Low Warn Low Alarm Current Threshold Threshold Threshold ThresholdPort (milliamperes) (mA) (mA) (mA) (mA)
Te2/1 6.1 ++ 0.0 0.0 0.0 0.0 Te2/2 6.7 ++ 0.0 0.0 0.0 0.0
Optical High Alarm High Warn Low Warn Low Alarm Transmit Power Threshold Threshold Threshold ThresholdPort (dBm) (dBm) (dBm) (dBm) (dBm)
Te2/1 -2.9 ++ -40.0 -40.0 -40.0 -40.0 Te2/2 -2.6 ++ -40.0 -40.0 -40.0 -40.0
Optical High Alarm High Warn Low Warn Low Alarm Receive Power Threshold Threshold Threshold ThresholdPort (dBm) (dBm) (dBm) (dBm) (dBm)
Te2/1 -2.5 ++ -40.0 -40.0 -40.0 -40.0 Te2/2 -2.6 ++ -40.0 -40.0 -40.0 -40.0
Thanks
--
*Zafar Pravaiz *IT Senior Systems Engineer Information Technology Department
AUS /> </span><span style='font-size:10.0pt;font-family:Times;mso-bidi-font-family:
Tel +971 6 515 2164 Fax +971 6515 2112
American University of Sharjah PO Box 26666, Sharjah United Arab Emirates http://www.aus.edu http://www.aus.edu/ zpravaiz@aus.edu mailto:youremail@aus.edu
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
The point of Observium is certainly not to have alerts.
IPMI thresholds are set incorrectly indeed, this will be fixed in due time; however, the problem in this thread is not incorrectly set thresholds at the Observium side, but at the device side ;)
Tom
On 18/06/2012 10:01, Nikolay Shopik wrote:
Well what's point then of observium if you can't even have alerts? :)
btw same apply to IPMI thresholds, which incorrectly set, thus false alerts.
On 18.06.2012 11:16, Adam Armstrong wrote:
Disable all of the alerts using the config.inc.php variable. They're not reliable.
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
On 18.06.2012 12:06, Tom Laermans wrote:
The point of Observium is certainly not to have alerts.
So you guys gonna get rid of them? I know obserivum is more statistical thingy, less alerting like nagios. But I'd like to have simple alerts
IPMI thresholds are set incorrectly indeed, this will be fixed in due time; however, the problem in this thread is not incorrectly set thresholds at the Observium side, but at the device side ;)
Oh I totally understand that as we talked about that, it just yesterday it become worse, so I though to mention it.
On 18/06/2012 10:10, Nikolay Shopik wrote:
On 18.06.2012 12:06, Tom Laermans wrote:
The point of Observium is certainly not to have alerts.
So you guys gonna get rid of them? I know obserivum is more statistical thingy, less alerting like nagios. But I'd like to have simple alerts
Well, yes, we're going to get rid of the current alerting it does, because it's not well implemented an kind of random and unreliable. But Adam is/was working on a ruleset system to define thresholds for anything we monitor, so we know when to create events (you can see an empty alert tab on your device, which is a beginning for it). Then we're going to write something to handle those events and do alerting (mail, sms?, irc, ...) + an overview of "open issues" on the frontpage. But it's not a small task, so it won't be finished real soon...
IPMI thresholds are set incorrectly indeed, this will be fixed in due time; however, the problem in this thread is not incorrectly set thresholds at the Observium side, but at the device side ;)
Oh I totally understand that as we talked about that, it just yesterday it become worse, so I though to mention it.
I'll try to fix it soon :-)
Tom
On 18/06/2012, at 10.06, Tom Laermans wrote:
The point of Observium is certainly not to have alerts.
IPMI thresholds are set incorrectly indeed, this will be fixed in due time; however, the problem in this thread is not incorrectly set thresholds at the Observium side, but at the device side ;)
and please keep them coming, so we will be forced to update devices with better configuration - to get rid of unnecessary alarms :-)
I have a growing network and the ease with which I can add a new device into Observium, and receive pertinent alarms (BGP etc.) is fantastic! Just a short time ago I added a Juniper MX and this night received email about flapping BGP, and the only configuration was SNMP with Contact email on the device!
Never has Network Management been this easy!
and fiber optics alerts will be very welcome!
Best regards
Henrik
-- Henrik Lund Kramshøj, Follower of the Great Way of Unix hlk@kramse.org hlk@solidonetworks.com +45 2026 6000 cand.scient CISSP http://solidonetworks.com/ Network Security is a business enabler
Adam Armstrong <adama@...> writes:
Disable all of the alerts using the config.inc.php variable. They're not reliable.
adam.
To your comment, I was unable to find the mentioned config.inc.php variables. I am currently running Observium Pro 0.14.5.5452. It is possible that I simply missed them.
Can you please point me to documentation or a list of variables to disable all alerts of a certain type? I have some alerts working beautifully, but other types are reporting unreliable data (as you stated below). Email alerts are being sent out for those, so I would like to disable those alert types.
Some examples: * power supply sensors reporting -100000000C (< 0C) * fanspeed alarms under threshold: 9180RPM (< 9216RPM) * DOM TX bias current 2.2E-5A (> 0.000015A).
I have done some considerable searching but I remain confused. Any help that can be provided is appreciated.
Ryan
On 18/06/2012 07:31, Zafar Pravaiz wrote:
Hi
After upgrading to latest observium i start getting loads of following errors. I don't understand is this a threshold set problem or some IOS bug? Can some one please shed some light?
Observium :: Network Observation and Monitoring
Dbm Alarm: sfsw1 Te2/1 Receive Power Sensor - TenGigabitEthernet2/1 Receive Power Sensor is over threshold: -2.5dBm (> -40dBm)
Observium :: Network Observation and Monitoring
Dbm Alarm: sfsw1 Te2/2 Receive Power Sensor - TenGigabitEthernet2/2 Receive Power Sensor is over threshold: -2.6dBm (> -40dBm)
On 2014-05-23 16:13, Ryan wrote:
Adam Armstrong <adama@...> writes:
Disable all of the alerts using the config.inc.php variable. They're not reliable.
adam.
To your comment, I was unable to find the mentioned config.inc.php variables.
That's because the default config.inc.php only includes the options you need to set to make it work. It doesn't include any of the optional settings.
Can you please point me to documentation or a list of variables to disable all alerts of a certain type? I have some alerts working beautifully, but other types are reporting unreliable data (as you stated below). Email alerts are being sent out for those, so I would like to disable those alert types.
Some examples:
- power supply sensors reporting -100000000C (< 0C)
- fanspeed alarms under threshold: 9180RPM (< 9216RPM)
- DOM TX bias current 2.2E-5A (> 0.000015A).
I have done some considerable searching but I remain confused. Any help that can be provided is appreciated.
These are the /old/ alerts. One you disable them, most of them should go away.
Any remaining sensors with incorrect thresholds should either be disabled in the device's settings, or have their thresholds manually changed in the same settings.
The new alerting is still a WiP, and only basic documentation exists at : http://www.observium.org/wiki/Alerting
Thanks, adam.
In this case, your device is reporting the high and low alert levels as -40dBm, which would cause it to alert every time.
adam.
On 18/06/2012 07:31, Zafar Pravaiz wrote:
Hi
After upgrading to latest observium i start getting loads of following errors. I don't understand is this a threshold set problem or some IOS bug? Can some one please shed some light?
Observium :: Network Observation and Monitoring
Dbm Alarm: sfsw1 Te2/1 Receive Power Sensor - TenGigabitEthernet2/1 Receive Power Sensor is over threshold: -2.5dBm (> -40dBm)
Observium :: Network Observation and Monitoring
Dbm Alarm: sfsw1 Te2/2 Receive Power Sensor - TenGigabitEthernet2/2 Receive Power Sensor is over threshold: -2.6dBm (> -40dBm)
Observium :: Network Observation and Monitoring
Voltage Alarm: sfsw1 Te2/1 Supply Voltage Sensor - TenGigabitEthernet2/1 Supply Voltage Sensor is over threshold: 0V (> 0V)
Observium :: Network Observation and Monitoring
Dbm Alarm: sfsw2 Te2/1 Receive Power Sensor - TenGigabitEthernet2/1 Receive Power Sensor is over threshold: -2.8dBm (> -40dBm)
Observium :: Network Observation and Monitoring
Dbm Alarm: coresw1.aus.edu Te5/4 Receive Power Sensor - TenGigabitEthernet5/4 Receive Power Sensor is over threshold: 0dBm (> -40dBm)
SFSW1#sh interfaces transceiver detail Transceiver monitoring is disabled for all interfaces.
mA: milliamperes, dBm: decibels (milliwatts), NA or N/A: not applicable. ++ : high alarm, + : high warning, - : low warning, -- : low alarm. A2D readouts (if they differ), are reported in parentheses. The threshold values are calibrated.
High Alarm High Warn Low Warn Low Alarm Temperature Threshold Threshold Threshold ThresholdPort (Celsius) (Celsius) (Celsius) (Celsius) (Celsius)
Te2/1 29.5 ++ 0.0 0.0 0.0 0.0 Te2/2 29.1 ++ 0.0 0.0 0.0 0.0
High Alarm High Warn Low Warn Low Alarm Voltage Threshold Threshold Threshold ThresholdPort (Volts) (Volts) (Volts) (Volts) (Volts)
Te2/1 0.00 0.00 0.00 0.00 0.00 Te2/2 0.00 0.00 0.00 0.00 0.00
High Alarm High Warn Low Warn Low Alarm Current Threshold Threshold Threshold ThresholdPort (milliamperes) (mA) (mA) (mA) (mA)
Te2/1 6.1 ++ 0.0 0.0 0.0 0.0 Te2/2 6.7 ++ 0.0 0.0 0.0 0.0
Optical High Alarm High Warn Low Warn Low Alarm Transmit Power Threshold Threshold Threshold ThresholdPort (dBm) (dBm) (dBm) (dBm) (dBm)
Te2/1 -2.9 ++ -40.0 -40.0 -40.0 -40.0 Te2/2 -2.6 ++ -40.0 -40.0 -40.0 -40.0
Optical High Alarm High Warn Low Warn Low Alarm Receive Power Threshold Threshold Threshold ThresholdPort (dBm) (dBm) (dBm) (dBm) (dBm)
Te2/1 -2.5 ++ -40.0 -40.0 -40.0 -40.0 Te2/2 -2.6 ++ -40.0 -40.0 -40.0 -40.0
Thanks
--
*Zafar Pravaiz *IT Senior Systems Engineer Information Technology Department
AUS /> </span><span style='font-size:10.0pt;font-family:Times;mso-bidi-font-family:
Tel +971 6 515 2164 Fax +971 6515 2112
American University of Sharjah PO Box 26666, Sharjah United Arab Emirates http://www.aus.edu http://www.aus.edu/ zpravaiz@aus.edu mailto:youremail@aus.edu
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
participants (6)
-
Adam Armstrong -
Henrik Lund Kramshøj -
Nikolay Shopik -
Ryan -
Tom Laermans -
Zafar Pravaiz