1 / 11

NEMO-MIB: Managed Objects for Monitoring MIPv6 Node with NEMO Support

The NEMO-MIB defines objects for monitoring and controlling a MIPv6 node with NEMO support, covering operational statistics, registered state, and notifications for critical state changes.

willeford
Download Presentation

NEMO-MIB: Managed Objects for Monitoring MIPv6 Node with NEMO Support

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. NEMO-MIBhttp://www.ietf.org/internet-drafts/draft-ietf-nemo-mib-00.txtNEMO-MIBhttp://www.ietf.org/internet-drafts/draft-ietf-nemo-mib-00.txt Sri Gundavelli Glenn Keeni Ken Nagami Kazuhide Koide

  2. Purpose Defines managed objects for monitoring and controlling a mipv6 node with NEMO basic support. The Key aspects that are modeled in the MIB are: • Operational Statistics • Current Registered State • Notifications for critical state changes

  3. The NEMO MIB Structure The primary groups in the MIB are: • nemoSystem • nemoConfiguration • nemoStats • nemoNotifications • nemoConformance

  4. nemoSystem Group • The nemoSystem group provides the general information about the NEMO entity. The objects in this group cover the current registered state.

  5. nemoConfiguration Group • The nemoConfiguration group contains information relevant to the implementation and operation of the NEMO protocol. These objects are used for controlling the protocol parameters.

  6. nemoStats Group • The nemoStats group defines the statistics related to the NEMO protocol operations.

  7. nemoNotifications Group • The nemoNotifications group defines the notifications generated by the NEMO entity in response to the operationally interesting protocol state changes.

  8. nemoConformance Group • The nemoConformance group identifies the managed objects that needs to be implemented for conforming to this draft.

  9. Issues/TBD • Need to add the objects for the home agents with NEMO support • What other notifications do we need • Can this support accounting • Do we need other objects for diagnostics

  10. What Next ? • Revise the draft based on the WG input. • Get it reviewed by a MIB Doctor

  11. Questions ?

More Related