Hi andy and all,
   I'm implementing ietf-hardware.yang, and I have a question about 
/hardware/last-change.

   module: ietf-hardware
     +--rw hardware
        +--ro last-change?   yang:date-and-time
        +--rw component* [name]
           +--rw name              string
           +--rw class             identityref
           +--ro physical-index?   int32 {entity-mib}?
           +--ro description?      string
           +--rw parent?           -> ../../component/name
           +--rw parent-rel-pos?   int32
           +--ro contains-child*   -> ../../component/name
           +--ro hardware-rev?     string
           +--ro firmware-rev?     string
           +--ro software-rev?     string
           +--ro serial-num?       string
           +--ro mfg-name?         string
           +--ro model-name?       string
           +--rw alias?            string
           +--rw asset-id?         string
           +--ro is-fru?           boolean
           +--ro mfg-date?         yang:date-and-time

           +--rw uri*              inet:uri

           +--ro uuid?             yang:uuid

           +--rw state {hardware-state}?

           |  +--ro state-last-changed?   yang:date-and-time

           |  +--rw admin-state?          admin-state

           |  +--ro oper-state?           oper-state

           |  +--ro usage-state?          usage-state

           |  +--ro alarm-state?          alarm-state

           |  +--ro standby-state?        standby-state

           +--ro sensor-data {hardware-sensor}?

              +--ro value?               sensor-value

              +--ro value-type?          sensor-value-type

              +--ro value-scale?         sensor-value-scale

              +--ro value-precision?     sensor-value-precision

              +--ro oper-status?         sensor-status

              +--ro units-display?       string

              +--ro value-timestamp?     yang:date-and-time

              +--ro value-update-rate?   uint32


Last-change's description: "The time the '/hardware/component' list changed in 
the

           operational state.";
It seems this description means any change (configuration change or state 
change) of list /hardware/component/ will cause the update of 
/hardware/last-change.


But in description of  notification:hardware-state-change

    notification hardware-state-change {

      description

        "A hardware-state-change notification is generated when the

         value of /hardware/last-change changes in the operational

         state.";

      reference

        "RFC 6933<https://tools.ietf.org/html/rfc6933>: Entity MIB (Version 4) 
- entConfigChange";

    }



This notification means if any change occurs in /hardware/last-change, a 
notification will be reported.

This notification also refers to Entity MIB's entConfigChange.



My question is whether only configuration change of hardware component will 
cause the update of /hardware/last-change?

_______________________________________________
netmod mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/netmod

Reply via email to