Chassis MIB Proposal

[{3COM/PDD/PeteW}@pdd.3mail.3com.com]

FROM: Wilson, Peter

TO:  {[e-mail]}:ugate:3com                       DATE:  01-04-94
                                                              TIME:  09:39
CC:
SUBJECT:  Chassis MIB Proposal
PRIORITY:
ATTACHMENTS:

------------------------------------------------------------------------------         an entities ifTable. Note that if this value is zero then either
         the information is not available OR is not applicable."
    ::= { chasLinkEntry 5 }

chasLinkToLocType  OBJECT-TYPE
    SYNTAX INTEGER
    ACCESS read-only
    STATUS mandatory
    DESCRIPTION
        "A link is defined to be between one resource and another. This
         object identifies is a partial definition of one end of the link.
         This object in conjuntion with chasLinkToLoc and
         chasLinkToResourceId identfiy the end of the link."
    ::= { chasLinkEntry 6 }

chasLinkToLoc  OBJECT-TYPE
    SYNTAX INTEGER
    ACCESS read-only
    STATUS mandatory
    DESCRIPTION
        "A link is defined to be between one resource and another. This
         object identifies is a partial definition of one end of the link.
         This object in conjuntion with chasLinkToLocType and
         chasLinkToResourceId identfiy the end of the link."
    ::= { chasLinkEntry 7 }

chasLinkToResourceId  OBJECT-TYPE
    SYNTAX INTEGER
    ACCESS read-only
    STATUS mandatory
    DESCRIPTION
        "A link is defined to be between one resource and another. This
         object identifies is a partial definition of one end of the link.
         This object in conjuntion with chasLinkToLocType and
         chasLinkToResourceId identfiy the end of the link."
    ::= { chasLinkEntry 8 }

chasLinkFromIfNumber OBJECT-TYPE
    SYNTAX INTEGER
    ACCESS read-only
    STATUS mandatory
    DESCRIPTION
        "This object can be used to correlate the resource to an entry in
         an ifTable visible through the entity to which this resource belongs.
         Without this object there is no correlation between a resource and
         an entities ifTable. Note that if this value is zero then either
         the information is not available OR is not applicable."
    ::= { chasLinkEntry 9 }

 
-- the Power Supply Output table. Note that this table contains
-- additional information for resources that represent power
-- supplies. As such this table has the same index as the resource
-- table. When the MIB is represented in an SNMPv2 manner the
-- index columns can be removed from this table and the INDEX
-- clause can refer to the resource table. Alternatively since
-- this table requires exactly the same indices as the resource
-- table it is a good candidate for the AUGMENTS clause!
--
-- && Note that identifying PS resouces differently here to the
-- && resource table is confusing.
chasPowerSupplyOutputTable OBJECT-TYPE
    SYNTAX SEQUENCE OF ChasPowerSupplyOutputEntry
    ACCESS not-accessible
    STATUS mandatory
    DESCRIPTION
    "Additional information for resource that represent source
    of power within the chassis."
    ::= { chasPowerSupply 2 }

chasPowerSupplyOutputEntry OBJECT-TYPE
    SYNTAX ChasPowerSupplyEntry
    ACCESS not-accessible
    STATUS mandatory
    DESCRIPTION
  "Values for a power supply output."
    INDEX { chasPSLocationType, chasPSLocationIndex,chasPSResource}
    ::= { chasPowerSupplyOutputTable 1 }

ChasPowerSupplyOutputEntry ::=
    SEQUENCE {
        chasPSLocationType            INTEGER,
        chasPSLocationIndex           INTEGER,
        chasPSResource                INTEGER,
        chasPSOutputStatus            INTEGER,
        chasPSOutputNominalVoltage    INTEGER,
        chasPSOutputOfferedVoltage    INTEGER,
        chasPSOutputOfferedWattage    INTEGER,
        chasPSOutputWarnings          Counter,
        chasPSOutputFailures          Counter
    }

chasPSLocationType  OBJECT-TYPE
    SYNTAX  INTEGER
    ACCESS  read-only
    STATUS  mandatory
    DESCRIPTION
        "A Power Supply resource exists on a particular module.
         This variable identifies the type part of the module on
         which this resource resides. It can be used with
         chasPSULocationIndex to index the module table for information
         about the module.

         The value of this object could be chasPowerSupplyBay, however
         some chassis implementations will not distinguish between
         slots that accept modular function card and those that accept
         power supplies. A slot can accept for example a power supply
         or a repeater line card."
    ::= { chasPowerSupplyOutputEntry 1 }

chasPSLocationIndex  OBJECT-TYPE
    SYNTAX  INTEGER
    ACCESS  read-only
    STATUS  mandatory
    DESCRIPTION
        "A power supply resource exists on a particular module. A module
         is identified by its location type and location instance.
         This variable identifies the instance part of the module
         identification on which this resource resides. It can be
         used with chasPSLocationType to index the module table
         for information about the module."
    ::= { chasPowerSupplyOutputEntry 2 }

chasPSResource  OBJECT-TYPE
    SYNTAX  INTEGER
    ACCESS  read-only
    STATUS  mandatory
    DESCRIPTION
         "A unique index for the power supply resource on this
          particular physical module."
    ::= { chasPowerSupplyOutputEntry 3 }

chasPSOutputStatus OBJECT-TYPE
    SYNTAX INTEGER {
        unknown         (1),
        bad             (2),
        warning         (3),
        good            (4)
    }
    ACCESS read-only
    STATUS mandatory
    DESCRIPTION
        "Actual status of the power supply:

            - unknown(1)     status not known
            - bad(2)         unable to supply power due to failure
            - warning(3)     supplying power but marginally
            - good(4)        supplying power

        It is an implementation specific matter whether
        the agent keeps entries with status unknown(1) in
        the table.  If unknown(1), offered values and
        counters are meaningless."
                ::= { chasPowerSupplyOutputEntry 4 }

chasPSOutputNominalVoltage OBJECT-TYPE
    SYNTAX INTEGER
    ACCESS read-only
    STATUS mandatory
    DESCRIPTION
           "In hundredths of a volt, the voltage
            the output is supposed to supply, such
            as -5, +5, +12, -15, etc."
   ::= { chasPowerSupplyOutputEntry 5 }

chasPSOutputOfferedVoltage OBJECT-TYPE
    SYNTAX INTEGER
    ACCESS read-only
    STATUS mandatory
    DESCRIPTION
          "In hundredths of a volt, the voltage
           actually offered by the output.  If
           chasPowerSupplyOutputStatus is good(4),
           the value 0 means offered voltage is
           not available."
  ::= { chasPowerSupplyOutputEntry 6 }

chasPSOutputOfferedWattage OBJECT-TYPE
    SYNTAX INTEGER
    ACCESS read-only
    STATUS mandatory
    DESCRIPTION
          "In hundredths of a watt, the wattage
          actually offered by the output.  If
          chasPowerSupplyOutputStatus is good(4),
          the value 0 means offered wattage is not
          available."
 ::= { chasPowerSupplyOutputEntry 7 }

chasPSOutputWarnings OBJECT-TYPE
    SYNTAX Counter
    ACCESS read-only
    STATUS mandatory
    DESCRIPTION
         "The number of times
         chasPowerSupplyOutputStatus has gone to
         warning(3)."
    ::= { chasPowerSupplyOutputEntry 8 }

chasPSOutputFailures OBJECT-TYPE
    SYNTAX Counter
    ACCESS read-only
    STATUS mandatory
    DESCRIPTION
        "The number of times chasPowerSupplyOutputStatus
         has gone to bad(2)."
    ::= { chasPowerSupplyOutputEntry 9 }

-- the chasEnviron (Environment) group
-- Implementation of this group is optional.

-- && In the same way that each power supply is
-- && a resource, so is each environmental monitor. This
-- && table can also be described as an AUGMENTS or a shared
-- && index with the resource table. In the long run it is
-- && more economical on MIB objects to share the indices
-- && with the resource table. In preparation for this I've
-- && changed this table to use the location type and index
-- && to identify rows in this table.
-- &&
-- && Because a sensor is a resource, its can be identified
-- && by the OID in the resource table so chasEnvironSensor
-- && is no longer required.
chasEnvironTable OBJECT-TYPE
    SYNTAX SEQUENCE OF ChasEnvironEntry
    ACCESS not-accessible
    STATUS mandatory
    DESCRIPTION
        "A list of environmental entries, one for
        each environmental sensor in the chassis. This table
        augments the resources in the resource table for those
        entries which represent sensors."
    ::= { chasEnviron 1 }

chasEnvironEntry OBJECT-TYPE
    SYNTAX ChasEnvironEntry
    ACCESS not-accessible
    STATUS mandatory
    DESCRIPTION "Values for a environmental sensor."
    INDEX { chasEnvironLocationType,
            chasEnvironLocationIndex,
            chasEnvironResource }
    ::= { chasEnvironTable 1 }

ChasEnvironEntry ::= SEQUENCE {
    chasEnvironLocationType                     INTEGER,
    chasEnvironLocationIndex                    INTEGER,
    chasEnvironResource                         INTEGER,
    chasEnvironStatus                           INTEGER,
    chasEnvironWarnings                         Counter,
    chasEnvironFailures                         Counter,
}

chasEnvironLocationType  OBJECT-TYPE
    SYNTAX  INTEGER
    ACCESS  read-only