RE: FW: EPON MIB comments

"Glen Kramer" <[email protected]>
Newsgroups gmane.ietf.hubmib
Organization Teknovus
Message-ID <[email protected]>
[GK] The following objects represent non-EPON-specific events and should be
moved to OAM MIB.
>    eponDeviceSampleMinimum
>    eponDeviceDyingGaspAlarmState
>    eponDeviceDyingGaspAlarmEnabled
>    eponDeviceCriticalEventState
>    eponDeviceCriticalEventEnabled
>    eponDeviceLocalLinkFaultAlarmState
>    eponDeviceLocalLinkFaultAlarmEnabled
>    eponDeviceTemperatureEventIndicationState
>    eponDeviceTemperatureEventIndicationEnabled
>    eponDevicePowerVoltageEventIndicationState
>    eponDevicePowerVoltageEventIndicationEnabled
>    eponDeviceGlobalEventState
>    eponDeviceGlobalEventEnabled
>    eponDeviceErroredSymbolPeriodEventState
>    eponDeviceErroredSymbolPeriodEventEnabled
>    eponDeviceErroredFrameEventState
>    eponDeviceErroredFrameEventEnabled
>    eponDeviceErroredFramePeriodEventState
>    eponDeviceErroredFramePeriodEventEnabled
>    eponDeviceErroredFrameSecondsSummaryEventState
>    eponDeviceErroredFrameSecondsSummaryEventEnabled
>    eponDeviceOrganizationSpecificEventState
>    eponDeviceOrganizationSpecificEventEnabled
>    eponDeviceEventControl

[LK] As a general concept we tried to create in the EFM MIB objects a
reflection of the IEEE802.3ah management object keeping as much as we can
aligned to clause 30. There is here an additional section which refers to
device MIB objects. In there I tried to put all things which are necessary
for the management of an EPON device (in an access network) and was not
truly covered by the IEEE802.3ah spec as being a spec for L2 MAC mainly. So
although they are OAM they are in device level.

[GK] Lior, any network device is a combination of multiple specs. And
correspondingly, management of a network device comprises many MIBs. EPON
MIB should only cover EPON-specific objects. There exist many other MIBs
that are not EPON-specific, but that must be implemented in EPON devices.
Such objects as eponDeviceDyingGaspAlarmEnabled and
eponDeviceTemperatureEventIndicationState (and all other objects listed
above) are not EPON-specific. They exist in other MIBs.
What I am trying to say is that EPON MIB will not be used as substitution
for other MIBs. It is to be used in EPON devices in addition to other MIBs. 

Regards,
Glen
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.