Goals and objectives (1 slide only)
Project(s): MIB Ad hoc, involves EMS-NMS (MEF 7.1)
Purpose of the contribution: Provide the rationale behind starting a
project to write a NE-EMS SNMP MIB for SOAM PM and extensions to
the IEEE CFM MIBs (for SOAM FM).
Abstract: This contribution provides the background on why an SNMP
MIB is desirable, provides pointers to related material that will be used,
and provides a plan for the execution of the project.
Motion: Yes, this contribution contains a motion to start a project.
1
MIB Ad hoc update
Marina Del Rey, CA USA (1Q 2010)
32054_001
Contact
Scott Mansfield
Ericsson
2
MIB Ad hoc
•
•
•
•
•
•
•
•
•
Scope
Rationale
Background
Timeframe
Impacts on other documents
Liaison Plan
Deliverables
Call for Participation
Motion
3
Scope
• A project in the Management Area
• Guiding principle
– Keep the scope of the project small
• Concentrate on SOAM PM and extensions needed for SOAM
FM
– Ensure the project provides needed functionality and is small enough to
be completed in a reasonable amount of time
• Documents
– A document containing an SNMP MIB for configuring and monitoring
SOAM PM capabilities in a Carrier Ethernet environment.
– A document containing an SNMP MIB that includes the extensions
needed to the IEEE CFM MIBs for the new functionality described in
the SOAM FM document.
– As a stretch goal, produce a document that includes a YANG model for
NETCONF using the same source material used to create the SNMP
MIBs for both PM and the FM extensions.
4
Rationale
• Creating an SNMP MIB would be beneficial
– Help interoperability between vendor
implementations
• Allow network operators the freedom to move
away from NE-EMS single vendor solutions
• One NMS or EMS vendor can interoperate with
multiple vendor NEs
– Implementation of existing protocol neutral models
would help ensure models are complete
– Provide a baseline of functionality for PM and FM
OAM that can be extended
5
Rationale (cont)
• Creating a YANG model for NETCONF would
be beneficial
– Provide a concrete implementation of the abstract
MEF models using an IETF standard modeling
language
– Assist in the evaluation of the protocol neutral models
to ensure they are complete
– Gain experience with YANG and NETCONF for
potential future projects
– As a stretch goal, this work would not hinder the
completion of the SNMP MIBs
6
Background
• Interface terminology acronyms that are used in the
material that follows:
–
–
–
–
–
–
–
–
–
–
–
–
Network Elements (NE)
Element Management System (EMS)
Network Management System (NMS)
Operations Support System/Business Support System
(OSS/BSS)
eXtensible Markup Language (XML)
Simple Network Management Protocol (SNMP)
Management Information Base (MIB)
Command Line Interface (CLI)
Java Enterprise Edition (Java EE)
Common Object Request Broker Architecture (CORBA)
Network Configuration Protocol (NETCONF)
YANG is a data modeling language for NETCONF
7
Background (cont)
• Relationships and Interfaces for NM
Project would
concentrate
here
8
Background (cont)
• Protocol neutral management specifications exist
– MEF 7.1
– G.8052
• It would be useful to create an implementation of the
protocol neutral models to ensure they are complete
• Assumptions
– MEF 7.1 (EMS-NMS) model can be used as a starting point for
the NE-EMS implementation needed
– The PM area is lacking a management standard so an SNMP
MIB would help with interoperability
– The IEEE CFM MIBs do not contain all the functionality that is
needed by the SOAM FM document
9
Background (cont)
• Guiding principle – Do not redo work that
already exists
• Use the existing work as guidelines
–
–
–
–
MEF 7.1
G.8052
CFM MIBs (IEEE 802.1ap + IEEE 802.1ag)
IETF MIBs
• RFC 4181 “Guidelines for Authors and Reviewers
of MIB Documents”
10
Background (cont)
• SNMP MIB Structure approach
11
Timeframe
• 1Q 2010: Project start
• Conference calls between 1Q-2Q produce a
draft document
• 2Q 2010: Move for Straw Ballot
• Conference calls between 2Q-3Q resolve all
straw ballot comments and produces
another draft
• 3Q 2010: Move for Straw Ballot (if needed)
• 4Q 2010: Letter Ballot
12
Impacts on other documents
• There are no other documents directly
affected by the creation of the SNMP MIB
document or the YANG model
13
Liaison Plan
• Liaise with
–
–
–
–
TMF
IEEE (802.1)
ITU-T (Q10/15)
ITU-T (Q14/15)
• Project kickoff liaison
• Project status liaisons (including requests
for comments) each quarter (or whenever
there are documents ready to share)
• Project completion (with results)
14
Deliverables
• Multiple MEF documents
– A MEF document containing an SNMP MIB for
SOAM PM
– A MEF document containing an SNMP MIB for the
extensions needed to support SOAM FM
– Potentially, a MEF document containing the YANG
model for both the PM and FM extensions.
• Liaisons
15
Call for Participation
• Editor
• Participants
16
Motion
• Create a project based on the scope defined
in 32054_001
• Move
• Second
• Yes
• No
• Abstain
17