Entity MIB State Extensions

1
Entity MIB State Extensions

• Sharon Chisholm schishol_at_nortelnetworks.com
• November 2002

2
Entity MIB State ExtensionsOverview

• Why Entity State Extensions?
• Motivation
• Requirements
• Proposed State Extensions
• Moving Forward

3
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
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
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
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
Proposed State Extensions - Alarm

• Alarm Status
• This field gives more information on operational
  state.
• Under repair
• Critical
• Major
• Minor
• Alarm outstanding

8
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
Proposed State Extensions - Example
Port
Module
Admin shutting Down Oper
Enabled Usage Active Standby Providing
Service
Admin Unlocked Oper Enabled Usage
Idle Standby Providing Service
Container
Container
Admin Unlocked Oper Enabled Usage
Busy Standby Providing Service
Admin Unlocked Oper Enabled Usage
Active Standby Providing Service
Fan
Fan
Admin Unlocked Oper Enabled Usage
Busy Standby Providing Service
Admin Unlocked Oper Enabled Usage
Active Standby Providing Service

Power Supply
Power Supply
Admin Unlocked Oper Enabled Usage
Active Standby Providing Service
Admin locked Oper Enabled Usage Idle Standby
Hot Standby
10
Moving Forward

• Option 1
• Merge into Entity MIB Version 3
• Rough consensus from Yokohama meeting
• Option 2
• Make separate working group ID

11
(No Transcript)