Entity MIB State Extensions

1
Entity MIB State Extensions

• Sharon Chisholm schishol_at_nortelnetworks.com
• Dave Perkins
• dperkins_at_snmpinfo.com
• July 2003

2
Entity MIB State ExtensionsOverview

• Problem Tracking
• Changes since San Francisco
• Open Issues
• Moving Forward

3
Problem Tracking

• Experimenting with using Problem Tracking System
• https//rt.psg.com/
• entity-state queue
• Ran into some technical issues
• Often timed out
• People might be able to enter issues directly
  into system

4
Changes in -01

• Boilerplate updates
• Description Cleanup Reorganization
• Clarified two types of state in hierarchies
• Raw
• The state of the entity independent of the states
  of its parents and children in its containment
  hierarchy.
• Computed
• The state of the entity, as it may be influenced
  by the state of its parents and children.
• All states within the draft are raw state

5
Changes in -01

• Added notApplicable value to all Textual
  Conventions
• Usage State
• Reworded most discussion of user to discuss
  physical entities

6
Issues to date from WG Last Call

• 71 entStateAdmin usage clarification required
• 72 Usage State distinction between 'active' and
  'busy'
• 73 AlarmStatusTC - notSupported versus
  indeterminate", a summary of which appears below
• 74 StandbyStatus TC - a new value for
  'load-sharing'

7
Issues to date from Last Call

• 75 Notifications
• first the names are very confusing - they are
  called OperEnabled and OperDisabled,
• they carry only entStateAdmin, and entStateAlarm
  objects. I think that at least entStateOper
  should be added.
• It also is not defined when these notifications
  are supposed to be sent.
• 76 Security Considerations
• The Security Considerations section should
  clearly articulate the operational risks of
  writing on entStateAdmin.
• explain that access to the objects defined in
  this MIB allows to figure out what the active and
  standby resources in a network are and that this
  information can be used to optimize attacks on
  networks. So even read-only access to this MIB
  should be properly protected

8
Issues to date from Last Call

• 77
• Section 2.2.1 - A corrective action is not
  necessary in all cases to make an entity
  available for use. In some cases setting the
  admin state to unlock should be enough.
• 78 Collection of Editorial Comments
• 79 Missing State values for some physical
  components
• 80 Relationship with Other MIBs

9
Moving Forward

• Finish last call July 29, 2003
• Issue new draft with updates

10
(No Transcript)