RE: IETF-Event-MIB-Draft pktcDevEvProgrammableEntry and pktcDevEv FixedEntry
"Woundy, Richard" <[email protected]>
| Newsgroups | gmane.ietf.ipcdn |
|---|---|
| Message-ID | <C693FAC65F082B4190F29728D454734128C1DD@PACDCEXCMB01.cable.comcast.com> |
I agree that the MIB descriptions are only minimally helpful. Section 3.1.2
of the draft is also minimally helpful.
Looking at these two objects:
pktcDevEvProgrammableId OBJECT-TYPE
SYNTAX Integer32 (1..2147483647)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"ID for a specific programmable event to which the priority and
display string are matched. These Event Ids are vendor specific
or in
the case of PacketCable events defined in
PacketCable Management Event Identifier Technical Report."
::= { pktcDevEvProgrammableEntry 1 }
pktcDevEvFixedId OBJECT-TYPE
SYNTAX Integer32 (1..2147483647)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"ID for a specific fixed event to which the priority and display
string are matched. These Event Ids are vendor specific or in
the
case of PacketCable events defined in
pkt-tr-memevent-id-v01-001128."
::= { pktcDevEvFixedEntry 1 }
These two descriptions are not terribly helpful, since it is the case that
"PacketCable Management Event Identifier Technical Report" is equivalent to
"pkt-tr-memevent-id-v01-001128".
Looking at that particular report
<http://www.packetcable.com/downloads/specs/pkt-tr-memevent-id-v01-001128.pd
f>, it appears that only PacketCable-Specific Programmable Event IDs have
been defined. Are we ever going to define any Pre-Defined aka Fixed Event
IDs? And if not, should the concept of a Pre-Defined/Fixed Event ID be
dropped altogether???
-- Rich
-----Original Message-----
From: Kumar, Satish [mailto:[email protected]]
Sent: Monday, August 09, 2004 1:04 PM
To: [email protected]
Cc: Jean-Francois Mule; Woundy, Richard
Subject: IETF-Event-MIB-Draft pktcDevEvProgrammableEntry and
pktcDevEvFixedEntry
Hi,
We have common description for TWO MIBs. Need to undersand the difference
between the two.
pktcDevEvProgrammableEntry OBJECT-TYPE
SYNTAX PktcDevEvProgrammableEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Allows configuration of the reporting mechanisms for a
programmable event, including level, report type, and text."
INDEX { pktcDevEvProgrammableId, pktcDevEvProgrammableEnterprise }
::= { pktcDevEvProgrammableTable 1 }
pktcDevEvFixedEntry OBJECT-TYPE
SYNTAX PktcDevEvFixedEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Allows configuration of the reporting mechanisms for a
fixed event, including level, and report type."
INDEX { pktcDevEvFixedId, pktcDevEvFixedEnterprise }
::= { pktcDevEvFixedTable 1 }
Which events should be reported through pktcDevEvFixedTable and which
events should be reported through pktcDevEvProgrammableTable or can all
events be reported through either?
Comments please..
Thanks,
Satish