VOL-4782: Changes for Transceiver Threshold events
Change-Id: Iee89d9a362932d06eda1541ed88f2b82ba80d33e
diff --git a/protos/dmi/hw_events_mgmt_service.proto b/protos/dmi/hw_events_mgmt_service.proto
index b4fceb9..1a7e0b0 100644
--- a/protos/dmi/hw_events_mgmt_service.proto
+++ b/protos/dmi/hw_events_mgmt_service.proto
@@ -16,6 +16,12 @@
// Events from the Transceivers
EVENT_TRANSCEIVER_PLUG_OUT = 100;
EVENT_TRANSCEIVER_PLUG_IN = 101;
+ // The threshold based events on the transceivers should be configured on
+ // the port components of that transceiver and not on the transceiver
+ // component itself. This is because there could be different thresholds
+ // on the different ports of a transceiver (for example for a transceiver of
+ // type COMBO_GPON_XGSPON the power thresholds could be different for the
+ // GPON and XGSPON ports)
EVENT_TRANSCEIVER_VOLTAGE_ABOVE_THRESHOLD = 102;
EVENT_TRANSCEIVER_VOLTAGE_BELOW_THRESHOLD = 103;
EVENT_TRANSCEIVER_TEMPERATURE_ABOVE_THRESHOLD = 104;
@@ -75,11 +81,16 @@
}
message ValueType {
+ // For val no multiples of units shall be used.
+ // For example, for memory val should be in bytes and not in kilobytes or any
+ // other multiple of the unit byte.
oneof val{
int64 int_val = 1;
uint64 uint_val = 2;
float float_val = 3;
}
+
+ DataValueType typeOfVal = 4;
}
message WaterMarks {