RE: RE: Dot3OamEntry in EFM-COMMON-MIB

"Romascanu, Dan (Dan)" <[email protected]>
Newsgroups gmane.ietf.hubmib
Message-ID <AAB4B3D3CF0F454F98272CBE187FDE2F056B2696@is0004avexu1.global.avaya.com>
Raj,
 
There is no need to keep a strict relationship between the Clause 30 definitions and the SNMP MIB. From a Hubmib Charter point of view, we are looking at the IEEE 802.3 standard as a source and reference for the IETF MIBs, but we are allowed to take different approaches when needed. From a technical point of view Clause 30 describes the MAC level management model, while the SNMP MIB, may take a different approach, dictated by the operational requirements of management in an Internet environment. 
 
On a different note, I would recommend to use the correct SNMP terminology - i.e. Notifications, rather than Traps (which are a sub-set of SNMPv3 Notifications).
 
Regards,
Dan
-----Original Message-----
From: [email protected] [mailto:[email protected]]On Behalf Of Rajagopalan Subramanian
Sent: 20 February, 2004 7:58 AM
To: '[email protected]'
Cc: '[email protected]'
Subject: [Hubmib] RE: Dot3OamEntry in EFM-COMMON-MIB


Hi Matt,
Its good to have Traps to report whenever there is an OAM event. 
 
But according to the 802.3ah Standard, in the section 30A.19, aOAMLocalErrSymPeriodEvent and aOAMRemoteErrSymPeriodEvent are listed as 'GET' attributes of am OAM object class.
The definition for these in the sections 30.11.1.1.30 and 30.11.1.1.37 also implies that they should be updated as and when we receive or send an Event Notification.
This made me believe that these events should also be maintained as SNMP (statistics) table attributes.
 
Your thoughts please.
 
Thanks
Raj Subramanian
 
 
-----Original Message-----
From: Matt Squire [mailto:[email protected]] 
Sent: Friday, February 06, 2004 9:14 AM


 
Thats a good question.  I'm still a little unsure of how to best map the event tables into MIB stuff.  But we will almost definitly include the running totals into the event information, along with all of the other fields in the event TLVs.  
 
One possibility is to simply map each OAM event to a notification (SNMP trap), where we take all fields (including the running totals) into the trap.  Thats the way I'm leaning presently, where we don't maintain any SNMP tables for the events, and instead just map them to SNMP traps.  If you think thats good/bad, let me know.  
 
- Matt
-----Original Message-----
From: [email protected] [mailto:[email protected]]
Sent: Tuesday, January 20, 2004 6:24 AM
To: Matt Squire
Subject: Dot3OamEntry in EFM-COMMON-MIB
Hi Matt
 
Got one more doubt while going through the draft-squire-hubmib-efm-mib-00.txt
 
Are you planning to provide the following running-total counters in the Dot3OamEntry along with the dot3OamThreshold and Config objects?
 
dot3OamErrSymRunningTotal
dot3OamErrFrameSecsSummaryRunningTotal
dot3OamErrFrameRunningTotal
dot3OamErrFramePeriodRunningTotal
 
regards
Jayaprakash
 

Confidentiality Notice
 
 
The information contained in this electronic message and any attachments to this message are intended
for the exclusive use of the addressee(s) and may contain confidential or privileged information. If
you are not the intended recipient, please notify the sender at Wipro or [email protected] immediately
and destroy all copies of this message and any attachments.
 

Confidentiality Notice





The information contained in this electronic message and any attachments to this message are intended

for the exclusive use of the addressee(s) and may contain confidential or privileged information. If

you are not the intended recipient, please notify the sender at Wipro or [email protected] immediately

and destroy all copies of this message and any attachments.
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.