RE: FW: EPON MIB comments

[LK] Why is it referred only to debug mode? It can be needed during
operation also. Anyway management can affect device condition and
malfunctioning can be a result of any write operation even if it is
resetting of some database log/or table. I think that the security
section in the document should point to the proper place and point out
the hazards.
Why is it different in a concept from resetting an alarm table action or
from changing an operational mode? 
 

-----Original Message-----
From: Glen Kramer [mailto:[email protected]] 
Sent: Wednesday, January 05, 2005 2:18 AM
To: 'Lior khermosh'; 'Romascanu, Dan (Dan)'; [email protected]
Subject: RE: [Hubmib] FW: EPON MIB comments


[GK] eponDeviceObjectDeviceReadyMode object should be read-only.
Modifying device mode through the management may have unpredictable
results (like taking down entire EPON).

[LK] Changing this variable might indeed cause very major changes in the
system. Yet in my opinion it is needed for management. Unfortunately in
true life engineered systems there is a possibility that a system is not
operating well and it is needed to make it inactive immediately. The
purpose of such an attribute is like this.

[GK] We should not confuse MIB with debug functions. I would agree to
have an object that would allow disabling a device. I am against
allowing management changing device mode from notReady to ready or from
inProcess to ready. This would take down the device and very likely
would take down the entire EPON. Device mode should only change
according to state machines defined in IEEE 802.3ah.

Regards,
Glen