OSPF Version 2 Multiple Instance Management Information Base
draft-shao-ospf-mi-mib-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Xiaofan Shao , fangwei hu | ||
| Last updated | 2010-10-14 | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
The OSPF MIB defined by the IETF (RFC 1850) was designed to work with only one OSPF process/instance on a given router. It currently doesn't offer a mechanism to access ospf mib obejects of different instances. For example, there is only a single ospfRouterId object, not a table of them. In order to handle multiple instances, RFC 4750 suggests that you use SNMPv3 contexts to provide per-instance views. This document introduces a way for OSPF MIB to support multiple instance, no mater in SNMPv2 or SNMPv3 contexts, by adding the object ospfProcId into every OSPF MIB group. According to the specified ospfProcId, other obejects in this OSPF instance can be accessed.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)