1. Entity MIB – IETF 55 Entity MIB State Extensions Sharon Chisholm schishol@nortelnetworks.com schishol@nortelnetworks.com November 2002

2. Entity State - 1 Entity MIB IETF 55 Entity MIB State Extensions Overview Why Entity State Extensions? –Motivation –Requirements Proposed State Extensions Moving Forward

3. Entity State - 2 Entity MIB IETF 55 Motivation State/Status Information is Useful –Display to user –System Debug –Administrative related state is useful in determining the severity of an alarm. –State information such as standby can provide standard way to query or monitor primary & backup hardware Currently no Consistency in State/Status information –Currently there are too many different and inconsistent ways to get object state Recent analyses of 122 notifications in standard MIBs found over 35 state/status objects. There are likely many more.

4. Entity State - 3 Entity MIB IETF 55 Requirements Ability to query state information for a given entity –Must haves Administrative state Operational state –Nice to haves Alarm Status Standby Status Re-use existing state models if possible

5. Entity State - 4 Entity MIB IETF 55 Proposed State Extensions - Admin Administrative State –This object denotes permission to use or prohibition against using this NE, imposed through the management system. Locked Shutting down Unlocked

6. Entity State - 5 Entity MIB IETF 55 Proposed State Extensions - Oper Operational State –This object denotes whether the NE is physically installed and working. Disabled Enabled Usage State – This object denotes whether or not the NE is actively in use at the specific instance, if so, whether or not it has spare capacity for additional users at that instant idle active busy

7. Entity State - 6 Entity MIB IETF 55 Proposed State Extensions - Alarm Alarm Status –This field gives more information on operational state. Under repair Critical Major Minor Alarm outstanding

8. Entity State - 7 Entity MIB IETF 55 Proposed State Extensions – Standby Standby –This object is meaningful when the back-up relationship role exists. It indicates the current role of the network element hot-standby cold-standby providing-service

9. Entity State - 8 Entity MIB IETF 55 Proposed State Extensions - Example Port Container Module Fan Power Supply Power Supply Admin: shutting Down Oper: Enabled Usage: Active Standby: Providing Service Admin: Unlocked Oper: Enabled Usage: Active Standby: Providing Service Admin: Unlocked Oper: Enabled Usage: Active Standby: Providing Service Admin: Unlocked Oper: Enabled Usage: Active Standby: Providing Service Admin: Unlocked Oper: Enabled Usage: Busy Standby: Providing Service Admin: Unlocked Oper: Enabled Usage: Busy Standby: Providing Service Admin: locked Oper: Enabled Usage: Idle Standby: Hot Standby Admin: Unlocked Oper: Enabled Usage: Idle Standby: Providing Service

10. Entity State - 9 Entity MIB IETF 55 Moving Forward Option 1 –Merge into Entity MIB Version 3 –Rough consensus from Yokohama meeting Option 2 –Make separate working group ID