hubmib-2----Page:32
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41
|
Comments - Raj Subramanian 1. Currently, as far as I know, the standard 802.3ah does not suggest a de-asserting mechanism. While standard specify a way to report the Critical link event, link fault and Dying Gasp events in the form of Flags field in the OAMPDU, it does not talk about resetting them. Similar is the case for all the Errored Events though an assertion and de-assertion is possible in this case without deviating from the standard, I think. However all the Global Events, Temperature and Voltage specific events and the Vendor SpecificAlarm Events, are not defined in the standard. Can they be optional then? Editor’s reply: Isn't a deasserting mechanism also useful? For instance if the link is bad the alarm might be received a lot of times. A deassertion option will allow to remove such alarm. |