Latest Chassis MIB Draft Mon, 10 August 1992 12:43 UTC

Return-Path: <owner-chassismib>
Received: by CS.UTK.EDU (5.61++/2.8s-UTK) id AA17301; Mon, 10 Aug 92 08:43:52 -0400
Received: from by CS.UTK.EDU with SMTP (5.61++/2.8s-UTK) id AA17297; Mon, 10 Aug 92 08:43:48 -0400
Received: by; id AA24655; Mon, 10 Aug 92 05:43:44 -0700
Received: by; id AA13663; Mon, 10 Aug 92 08:38:55 -0400
Message-Id: <>
Received: from quiver.enet; by us1rmc.enet; Mon, 10 Aug 92 08:41:01 EDT
Date: Mon, 10 Aug 92 08:41:01 EDT
Subject: Latest Chassis MIB Draft

How 'bout one more state for chasEntityAdminStatus:

    restoreToDefaults(5) - setting this object to this state
    restores all of its non-volatile parameters to their
    factory default state and resets the module (see reset(4)).

and for chasEntityOperStatus:

    nonFatalFailure(7) - indicates that the device's self-test
    has detected a non-fatal fault.  The device operates are less than
    a fully functional level in the presence of non-fatal errors.

which is useful if, say, one port of an 8 port terminal server is
broken.  And also for chasEntityOperStatus:

    needProgramLoad(8) - indicates that the device is waiting
    to be loaded.

    loading(9) - indicates that the device is attempting to load.

What is the intended use of chasEntityArgument?  I know it's described
as "implementation specific", but can someone give me an example or two?

The latest draft is a definite improvement.   Good job.