Transcript liaison-mef-35073-001-soam-mib-status-update-mood-1110.ppt

Goals and objectives
Project(s): Service OAM MIB
Purpose of the contribution: Status update of the Service OAM MIB
project
Abstract: The SOAM MIB project continued work on the FM/TC and PM
MIBs. Reviewed and incorporated SB comment for the FM/TC MIBs.
Motion: Yes, four motions: two approved drafts, one to initiate a straw
ballot and one to initiate a letter ballot
1
SOAM MIB Status
Beijing, China, October 2010
Steve Mood
Omnitron Sytems
2
History
• Ad Hoc was created during the 2009 4Q
meeting
• Project committee was created during the
2010 Q1 meeting
• FM/TC MIBs were submitted to Straw Ballot
during the 2010 Q2 meeting
• FM/TC MIBs were submitted to a second
Straw Ballot during the 2010 Q3 meeting
• FM/TC MIB to letter ballot meeting and PM
MIB to straw ballot during the 2010 Q4
meeting
3
Original Scope of the Project
• 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
– Provide a baseline of functionality that supports FM &
PM Implementation Agreements (IA)
5
Quarterly Status
• 14 Conference Calls were held during the
last quarter
• Participation was good. Thanks for those
who helped this work along:
Steve Mood (Omnitron)
Brian Hedstrom (CableLabs)
Carl Moberg (Tail-f)
David Ball (Cisco)
Eddie Jones (Frontier)
Jimmy Hu (Ciena)
Johan Bevemyr (Tail-f)
Ken Huang (Omnitron)
Mark Sylor (Exfo)
Mehmet Toy (Comcast)
Michael Bugenhagen (CenturyLink)
Moti Nisim (Telco)
Sri Gangula (Adva)
6
Quarterly Status, cont.
• Large part of quarterly meetings covered the
Performance Monitoring (PM) MIB
– MIB was written
– MIB was reviewed and updated
• Reviewed Straw Ballot Comments for Fault
Management (FM) MIB (SB #2)
– All the SB comments were reviewed and resolved
– Received feedback from the MIB Doctors and their
changes have been incorporated into MIB
• Started work on YANG model for NETCONF
7
SOAM MIB Project Timeline/Schedule
•
•
•
•
•
•
•
•
1Q 2010: Project Launch
2Q 2010: FM/TC MIB went to SB #1
3Q 2010: FM/TC MIB went to SB #2
4Q 2010: Move FM/TC MIB for LB, PM MIB
for SB #1
1Q 2011: Move PM MIB for SB #2 (LB?),
YANG FM model for SB #1
2Q 2011: Move PM MIB to LB, YANG FM
model for SB #2, YANG PM model for SB #1
3Q 2011: Move YANG FM model for LB
4Q 2011: Move YANG PM model for LB
8
FM MIB SB #2 Results
• SB #2 Results
– 16 Yes votes, 5 Yes with comments, 1 No with
comments, 5 Abstains
– 36 comments were received from 5 companies
• SB #1 Results (last quarter)
– 11 Yes, 5 Yes w/comments, 2 No w/comments, 5
abstains
– 104 comments were received from 8 companies
• SB comments incorporated into FM MIB
– Consolidated comments
– Updated FM/TC MIB posted
9
PM MIB Status
• The PM MIB was reviewed and completed
during the quarter
– Global configuration area
– DM (Delay Measurement) configuration, current
statistic table, and historic statistic table
– LM (Loss Measurement) configuration, current
statistic table, and historic statistic table
– Notification section: containing state alarms and
threshold crossing notifications
– Conformance & compliance section
– Compiled successfully with MG-Soft and LIBSMI
• To be submitted to MIB Doctors next quarter
10
PM MIB Open Item – History table index
• Method 1: Most of the standard IETF MIBs have a
fixed indexing structure where index 1 is the most
recently completed measurement interval.
– With 15 minutes intervals in 24 hours would result in
index values 1..96
• Method 2: Index starts at 1 but increases overtime,
so that the youngest completed measurement
interval is the largest index number
– Creates a “sliding window” of valid indexes.
– With 15 minute intervals in 24 hours would result in
index values (x)..(x+95) in a 24 hour period
• Comments? [email protected]
11
History table index - Pros and Cons
• Method 1 (fixed index)
– Pros
• Supported by standard IETF MIBs: DS1
(RFC2495/3895), DS3 (RFC2496/3896), SONET (RFC
3592), ADSL (RFC2662), HDLS2 (RFC4319) MIBs and
RFC 2493/3593/3705 (HC-PerfHist-TC-MIB)
• Common method implemented with history tables
– Cons
• Implementation of OSS very complicated, as a given
index refers to different data at different points in time. It
is very hard to ensure there are no race conditions when
accessing multiple objects.
• Many OSS/NMS do not get this right
12
History table index - Pros and Cons
• Method 2 (sliding index)
– Pros
• Simplifies OSS design
• Reduces data integrity problem of when is the data
valid in a particular row
• Supported by some proprietary MIBs, such as Cisco
IP-SLA (RTTMON) MIB, which is widely used
– Cons
• Not generally supported by IETF MIBs
13
Motion #1
• Approve contribution 35071_001 as
Approved Draft 3 of the Service OAM FM MIB
Technical Specification
• Motion:
• Second:
• Voting:
– Yes
– No
– Abstain
14
Motion #2
• Initiate Letter Ballot on Approved Draft 3 of
Service OAM FM MIB Technical Specification
(based on 35071_001 )
• Motion:
• Second:
• Voting:
– Yes
– No
– Abstain
15
Motion #3
• Approve contribution 35072_000 as
Approved Draft 1 of the Service OAM PM
MIB Technical Specification
• Motion:
• Second:
• Voting:
– Yes
– No
– Abstain
16
Motion #4
• Initiate Straw Ballot on Approved Draft 1 of
Service OAM PM MIB Technical
Specification (based on 35072_000 )
• Motion:
• Second:
• Voting:
– Yes
– No
– Abstain
17