-- extracted from draft-ietf-forces-mib-05.txt -- at Sat Mar 3 06:08:23 2007 FORCES-MIB DEFINITIONS ::= BEGIN IMPORTS MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, mib-2, Integer32, Counter32 FROM SNMPv2-SMI TEXTUAL-CONVENTION, TimeStamp FROM SNMPv2-TC MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP FROM SNMPv2-CONF; forcesMib MODULE-IDENTITY LAST-UPDATED "200703011200Z" -- Mar 1, 2007 ORGANIZATION "IETF Forwarding and Control Element Separation (ForCES) Working Group" CONTACT-INFO "WG Charter: http://www.ietf.org/html.charters/forces-charter.html Mailing lists: General Discussion: forces@peach.ease.lsoft.com To Subscribe: listserv@peach.ease.lsoft.com In Body: subscribe forces Chairs: Patrick Droz Email: dro@zurich.ibm.com David Putzolu Email: David.Putzolu@intel.com Editor: Robert Haas IBM Email: rha@zurich.ibm.com" DESCRIPTION "This MIB module contains managed object definitions for the ForCES Protocol. Copyright (C) The Internet Society (2007). This version of this MIB module is part of RFC yyyy; see the RFC itself for full legal notices." -- RFC Ed.: replace yyyy with actual RFC number & remove this note REVISION "200703011200Z" -- Mar 01, 2007 DESCRIPTION "Initial version, published as RFC yyyy." -- RFC Ed.: replace yyyy with actual RFC number & remove this note ::= { mib-2 XXX } -- RFC Ed.: replace XXX with IANA-assigned number & remove this note --**************************************************************** forcesMibNotifications OBJECT IDENTIFIER ::= { forcesMib 0 } forcesMibObjects OBJECT IDENTIFIER ::= { forcesMib 1 } forcesMibConformance OBJECT IDENTIFIER ::= { forcesMib 2 } ForcesID ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "The ForCES identifier is a four octet quantity." SYNTAX OCTET STRING (SIZE (4)) ForcesProtocolVersion ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "ForCES protocol version number. The version numbers used are defined in the specifications of the respective protocol: 1 - ForCESv1 [RFCzzzz]." -- RFC Ed.: replace zzzz with actual RFC number of ForCES protocol -- & remove this note SYNTAX Integer32 (1..255) DISPLAY-HINT "d" -- Notifications forcesAssociationEntryUp NOTIFICATION-TYPE OBJECTS { forcesAssociationRunningProtocolVersion } STATUS current DESCRIPTION "This notification is generated as soon as an association enters the UP state. Note that these notifications are not throttled as the CE itself should throttle the setup of associations." ::= { forcesMibNotifications 1 } forcesAssociationEntryDown NOTIFICATION-TYPE OBJECTS { forcesAssociationRunningProtocolVersion } STATUS current DESCRIPTION "This notification is generated as soon as an association leaves the UP state. Note that these notifications are not throttled as the CE itself should throttle the setup of associations." ::= { forcesMibNotifications 2 } forcesAssociationEntryUpStats NOTIFICATION-TYPE OBJECTS { forcesAssociationRunningProtocolVersion, forcesAssociationTimeUp, forcesAssociationHBMsgSent, forcesAssociationHBMsgReceived, forcesAssociationOtherMsgSent, forcesAssociationOtherMsgReceived } STATUS current DESCRIPTION "This notification is generated as soon as an association enters the UP state. Note that these notifications are not throttled as the CE itself should throttle the setup of associations." ::= { forcesMibNotifications 3 } forcesAssociationEntryDownStats NOTIFICATION-TYPE OBJECTS { forcesAssociationRunningProtocolVersion, forcesAssociationTimeUp, forcesAssociationTimeDown, forcesAssociationHBMsgSent, forcesAssociationHBMsgReceived, forcesAssociationOtherMsgSent, forcesAssociationOtherMsgReceived } STATUS current DESCRIPTION "This notification is generated as soon as an association leaves the UP state. Note that these notifications are not throttled as the CE itself should throttle the setup of associations." ::= { forcesMibNotifications 4 } -- Objects forcesLatestProtocolVersionSupported OBJECT-TYPE SYNTAX ForcesProtocolVersion MAX-ACCESS read-only STATUS current DESCRIPTION "The ForCES protocol version supported by the CE. The current protocol version is 1. Note that the CE must also allow interaction with FEs supporting earlier versions." ::= { forcesMibObjects 1 } forcesAssociations OBJECT IDENTIFIER ::= { forcesMibObjects 2 } forcesAssociationTable OBJECT-TYPE SYNTAX SEQUENCE OF ForcesAssociationEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "The (conceptual) table of associations." ::= { forcesAssociations 1 } forcesAssociationEntry OBJECT-TYPE SYNTAX ForcesAssociationEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "A (conceptual) entry for one association." INDEX { forcesAssociationCEID, forcesAssociationFEID } ::= { forcesAssociationTable 1 } ForcesAssociationEntry ::= SEQUENCE { forcesAssociationCEID ForcesID, forcesAssociationFEID ForcesID, forcesAssociationRunningProtocolVersion ForcesProtocolVersion, forcesAssociationTimeUp TimeStamp, forcesAssociationTimeDown TimeStamp, forcesAssociationHBMsgSent Counter32, forcesAssociationHBMsgReceived Counter32, forcesAssociationOtherMsgSent Counter32, forcesAssociationOtherMsgReceived Counter32 } forcesAssociationCEID OBJECT-TYPE SYNTAX ForcesID MAX-ACCESS not-accessible STATUS current DESCRIPTION "The ForCES ID of the CE." ::= { forcesAssociationEntry 1 } forcesAssociationFEID OBJECT-TYPE SYNTAX ForcesID MAX-ACCESS not-accessible STATUS current DESCRIPTION "The ForCES ID of the FE." ::= { forcesAssociationEntry 2 } forcesAssociationRunningProtocolVersion OBJECT-TYPE SYNTAX ForcesProtocolVersion MAX-ACCESS read-only STATUS current DESCRIPTION "The current ForCES protocol version used in this association. The current protocol version is 1." ::= { forcesAssociationEntry 3 } forcesAssociationTimeUp OBJECT-TYPE SYNTAX TimeStamp MAX-ACCESS read-only STATUS current DESCRIPTION "The value of sysUpTime at the time this association entered the UP state. If this association started prior to the last initialization of the network subsystem, then this object contains a zero value. This object allows to uniquely identify associations with the same CE and FE IDs." ::= { forcesAssociationEntry 4 } forcesAssociationTimeDown OBJECT-TYPE SYNTAX TimeStamp MAX-ACCESS accessible-for-notify STATUS current DESCRIPTION "The value of sysUpTime at the time this association left the UP state." ::= { forcesAssociationEntry 5 } forcesAssociationHBMsgSent OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "A counter of how many heartbeat messages have have been sent by the CE on this association since the association entered the UP state. If this association started prior to the last initialization of the network subsystem, then this object contains the value since the initialization." ::= { forcesAssociationEntry 6 } forcesAssociationHBMsgReceived OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "A counter of how many heartbeat messages have been received by the CE on this association since the association entered the UP state. If this association started prior to the last initialization of the network subsystem, then this object contains the value since the initialization." ::= { forcesAssociationEntry 7 } forcesAssociationOtherMsgSent OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "A counter of how many messages other than heartbeat (i.e., config and query) have been sent by the CE on this association since the association entered the UP state. If this association started prior to the last initialization of the network subsystem, then this object contains the value since the initialization." ::= { forcesAssociationEntry 8 } forcesAssociationOtherMsgReceived OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "A counter of how many messages other than heartbeat (i.e., config response, query response, event notification, and packet redirect) have been received by the CE on this association since the association entered the UP state. If this association started prior to the last initialization of the network subsystem, then this object contains the value since the initialization." ::= { forcesAssociationEntry 9 } -- Conformance forcesMibCompliances OBJECT IDENTIFIER ::= { forcesMibConformance 1 } forcesMibGroups OBJECT IDENTIFIER ::= { forcesMibConformance 2 } -- Compliance statements forcesMibCompliance MODULE-COMPLIANCE STATUS current DESCRIPTION "The compliance statement for routers running ForCES and implementing the ForCES MIB." MODULE -- this module MANDATORY-GROUPS { forcesMibGroup, forcesNotificationGroup } GROUP forcesNotificationStatsGroup DESCRIPTION "Implementation of this group is recommended." GROUP forcesStatsGroup DESCRIPTION "Implementation of this group is recommended." ::= { forcesMibCompliances 1 } -- Units of conformance forcesNotificationGroup NOTIFICATION-GROUP NOTIFICATIONS { forcesAssociationEntryUp, forcesAssociationEntryDown } STATUS current DESCRIPTION "A collection of notifications for signaling important ForCES events." ::= { forcesMibGroups 1 } forcesMibGroup OBJECT-GROUP OBJECTS { forcesLatestProtocolVersionSupported, forcesAssociationRunningProtocolVersion } STATUS current DESCRIPTION "A collection of objects to support management of ForCES routers." ::= { forcesMibGroups 2 } forcesNotificationStatsGroup NOTIFICATION-GROUP NOTIFICATIONS { forcesAssociationEntryUpStats, forcesAssociationEntryDownStats } STATUS current DESCRIPTION "A collection of optional notifications for signaling important ForCES events including statistics." ::= { forcesMibGroups 3 } forcesStatsGroup OBJECT-GROUP OBJECTS { forcesAssociationTimeUp, forcesAssociationTimeDown, forcesAssociationHBMsgSent, forcesAssociationHBMsgReceived, forcesAssociationOtherMsgSent, forcesAssociationOtherMsgReceived } STATUS current DESCRIPTION "A collection of optional objects to provide extra information about the associations. There is no protocol reason to keep such information, but these objects can be very useful in debugging connectivity problems." ::= { forcesMibGroups 4} END -- -- Copyright (C) The IETF Trust (2007). -- -- This document is subject to the rights, licenses and restrictions -- contained in BCP 78, and except as set forth therein, the authors -- retain all their rights. -- -- This document and the information contained herein are provided on an -- "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS -- OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND -- THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS -- OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF -- THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED -- WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. -- -- -- Intellectual Property -- -- The IETF takes no position regarding the validity or scope of any -- Intellectual Property Rights or other rights that might be claimed to -- pertain to the implementation or use of the technology described in -- this document or the extent to which any license under such rights -- might or might not be available; nor does it represent that it has -- made any independent effort to identify any such rights. Information -- on the procedures with respect to rights in RFC documents can be -- found in BCP 78 and BCP 79. -- -- Copies of IPR disclosures made to the IETF Secretariat and any -- assurances of licenses to be made available, or the result of an -- attempt made to obtain a general license or permission for the use of -- such proprietary rights by implementers or users of this -- specification can be obtained from the IETF on-line IPR repository at -- http://www.ietf.org/ipr. -- -- The IETF invites any interested party to bring to its attention any -- copyrights, patents or patent applications, or other proprietary -- rights that may cover technology that may be required to implement -- this standard. Please address the information to the IETF at -- ietf-ipr@ietf.org. -- -- -- Acknowledgment -- -- Funding for the RFC Editor function is provided by the IETF -- Administrative Support Activity (IASA).