From 380f1fee285f9ef0f7af20f5af67c0d456a744d0 Mon Sep 17 00:00:00 2001 From: Adam Amstrong Date: Thu, 8 Mar 2012 09:36:44 +0000 Subject: [PATCH] and fuck you, snmp git-svn-id: http://www.observium.org/svn/observer/trunk@2885 61d68cd4-352d-0410-923a-c4978735b2b8 --- mibs/MTA-MIB | 1226 --------------------------------- mibs/NETWORK-SERVICES-MIB | 626 ----------------- mibs/SCTP-MIB | 1342 ------------------------------------- 3 files changed, 3194 deletions(-) delete mode 100644 mibs/MTA-MIB delete mode 100644 mibs/NETWORK-SERVICES-MIB delete mode 100644 mibs/SCTP-MIB diff --git a/mibs/MTA-MIB b/mibs/MTA-MIB deleted file mode 100644 index 29618adc8..000000000 --- a/mibs/MTA-MIB +++ /dev/null @@ -1,1226 +0,0 @@ -MTA-MIB DEFINITIONS ::= BEGIN - -IMPORTS - OBJECT-TYPE, Counter32, Gauge32, MODULE-IDENTITY, mib-2 - FROM SNMPv2-SMI - TimeInterval - FROM SNMPv2-TC - MODULE-COMPLIANCE, OBJECT-GROUP - FROM SNMPv2-CONF - SnmpAdminString - FROM SNMP-FRAMEWORK-MIB - applIndex, URLString - FROM NETWORK-SERVICES-MIB; - -mta MODULE-IDENTITY - LAST-UPDATED "200003030000Z" - ORGANIZATION "IETF Mail and Directory Management Working Group" - CONTACT-INFO - " Ned Freed - - Postal: Innosoft International, Inc. - 1050 Lakes Drive - West Covina, CA 91790 - US - - Tel: +1 626 919 3600 - Fax: +1 626 919 3614 - - E-Mail: ned.freed@innosoft.com" - DESCRIPTION - "The MIB module describing Message Transfer Agents (MTAs)" - REVISION "200003030000Z" - DESCRIPTION - "This revision, published in RFC 2789, changes a number of - DisplayStrings to SnmpAdminStrings. Note that this change - - is not strictly supported by SMIv2. However, the alternative - of deprecating the old objects and defining new objects - would have a more adverse impact on backward compatibility - and interoperability, given the particular semantics of - these objects. The defining reference for distinguished - names has also been updated from RFC 1779 to RFC 2253." - REVISION "199905120000Z" - DESCRIPTION - "This revision fixes a number of technical problems found in - previous versions: The conformance groups for different - versions of this MIB have been corrected, the recommendation - that an empty string be returned if the last operation was - successful has been removed from - mtaGroupInboundRejectionReason and - mtaGroupOutboundConnectFailureReason as it conflicts - with the stated purpose of these variables, and the - required mtaStatusCode entry has been added to - MtaGroupErrorEntry. It should be noted that this last - change in no way affects the bits on the wire." - REVISION "199708170000Z" - DESCRIPTION - "This revision, published in RFC 2249, adds the - mtaGroupDescription and mtaGroupURL fields, conversion - operation counters, a group hierarchy description mechanism, - counters for specific errors, oldest message IDs, per-MTA - and per-group loop counters, and a new table for tracking - any errors an MTA encounters." - REVISION "199311280000Z" - DESCRIPTION - "The original version of this MIB was published in RFC 1566" - ::= {mib-2 28} - -mtaTable OBJECT-TYPE - SYNTAX SEQUENCE OF MtaEntry - MAX-ACCESS not-accessible - STATUS current - DESCRIPTION - "The table holding information specific to an MTA." - ::= {mta 1} - -mtaEntry OBJECT-TYPE - SYNTAX MtaEntry - MAX-ACCESS not-accessible - STATUS current - DESCRIPTION - "The entry associated with each MTA." - INDEX {applIndex} - ::= {mtaTable 1} - -MtaEntry ::= SEQUENCE { - mtaReceivedMessages - Counter32, - mtaStoredMessages - Gauge32, - mtaTransmittedMessages - Counter32, - mtaReceivedVolume - Counter32, - mtaStoredVolume - Gauge32, - mtaTransmittedVolume - Counter32, - mtaReceivedRecipients - Counter32, - mtaStoredRecipients - Gauge32, - mtaTransmittedRecipients - Counter32, - mtaSuccessfulConvertedMessages - Counter32, - mtaFailedConvertedMessages - Counter32, - mtaLoopsDetected - Counter32 -} - -mtaReceivedMessages OBJECT-TYPE - SYNTAX Counter32 - MAX-ACCESS read-only - STATUS current - DESCRIPTION - "The number of messages received since MTA initialization. - This includes messages transmitted to this MTA from other - MTAs as well as messages that have been submitted to the - MTA directly by end-users or applications." - ::= {mtaEntry 1} - -mtaStoredMessages OBJECT-TYPE - SYNTAX Gauge32 - MAX-ACCESS read-only - STATUS current - DESCRIPTION - "The total number of messages currently stored in the MTA. - This includes messages that are awaiting transmission to - some other MTA or are waiting for delivery to an end-user - or application." - ::= {mtaEntry 2} - -mtaTransmittedMessages OBJECT-TYPE - SYNTAX Counter32 - MAX-ACCESS read-only - STATUS current - DESCRIPTION - "The number of messages transmitted since MTA initialization. - This includes messages that were transmitted to some other - MTA or are waiting for delivery to an end-user or - application." - ::= {mtaEntry 3} - -mtaReceivedVolume OBJECT-TYPE - SYNTAX Counter32 - UNITS "K-octets" - MAX-ACCESS read-only - STATUS current - DESCRIPTION - "The total volume of messages received since MTA - initialization, measured in kilo-octets. This volume should - include all transferred data that is logically above the mail - transport protocol level. For example, an SMTP-based MTA - should use the number of kilo-octets in the message header - and body, while an X.400-based MTA should use the number of - kilo-octets of P2 data. This includes messages transmitted - to this MTA from other MTAs as well as messages that have - been submitted to the MTA directly by end-users or - applications." - ::= {mtaEntry 4} - -mtaStoredVolume OBJECT-TYPE - SYNTAX Gauge32 - UNITS "K-octets" - MAX-ACCESS read-only - STATUS current - DESCRIPTION - "The total volume of messages currently stored in the MTA, - measured in kilo-octets. This volume should include all - stored data that is logically above the mail transport - protocol level. For example, an SMTP-based MTA should - use the number of kilo-octets in the message header and - body, while an X.400-based MTA would use the number of - kilo-octets of P2 data. This includes messages that are - awaiting transmission to some other MTA or are waiting - for delivery to an end-user or application." - ::= {mtaEntry 5} - -mtaTransmittedVolume OBJECT-TYPE - SYNTAX Counter32 - UNITS "K-octets" - MAX-ACCESS read-only - STATUS current - DESCRIPTION - "The total volume of messages transmitted since MTA - initialization, measured in kilo-octets. This volume should - include all transferred data that is logically above the mail - transport protocol level. For example, an SMTP-based MTA - should use the number of kilo-octets in the message header - and body, while an X.400-based MTA should use the number of - kilo-octets of P2 data. This includes messages that were - transmitted to some other MTA or are waiting for delivery - to an end-user or application." - ::= {mtaEntry 6} - -mtaReceivedRecipients OBJECT-TYPE - SYNTAX Counter32 - MAX-ACCESS read-only - STATUS current - DESCRIPTION - "The total number of recipients specified in all messages - received since MTA initialization. Recipients this MTA - has no responsibility for, i.e. inactive envelope - recipients or ones referred to in message headers, - should not be counted even if information about such - recipients is available. This includes messages - transmitted to this MTA from other MTAs as well as - messages that have been submitted to the MTA directly - by end-users or applications." - ::= {mtaEntry 7} - -mtaStoredRecipients OBJECT-TYPE - SYNTAX Gauge32 - MAX-ACCESS read-only - STATUS current - DESCRIPTION - "The total number of recipients specified in all messages - currently stored in the MTA. Recipients this MTA has no - responsibility for, i.e. inactive envelope recipients or - ones referred to in message headers, should not be - counted. This includes messages that are awaiting - transmission to some other MTA or are waiting for - delivery to an end-user or application." - ::= {mtaEntry 8} - -mtaTransmittedRecipients OBJECT-TYPE - SYNTAX Counter32 - MAX-ACCESS read-only - STATUS current - DESCRIPTION - "The total number of recipients specified in all messages - transmitted since MTA initialization. Recipients this - MTA had no responsibility for, i.e. inactive envelope - recipients or ones referred to in message headers, - should not be counted. This includes messages that were - transmitted to some other MTA or are waiting for - delivery to an end-user or application." - ::= {mtaEntry 9} - -mtaSuccessfulConvertedMessages OBJECT-TYPE - SYNTAX Counter32 - MAX-ACCESS read-only - STATUS current - DESCRIPTION - "The number of messages that have been successfully - converted from one form to another since MTA - initialization." - ::= {mtaEntry 10} - -mtaFailedConvertedMessages OBJECT-TYPE - SYNTAX Counter32 - MAX-ACCESS read-only - STATUS current - DESCRIPTION - "The number of messages for which an unsuccessful - attempt was made to convert them from one form to - another since MTA initialization." - ::= {mtaEntry 11} - -mtaLoopsDetected OBJECT-TYPE - SYNTAX Counter32 - MAX-ACCESS read-only - STATUS current - DESCRIPTION - "A message loop is defined as a situation where the MTA - decides that a given message will never be delivered to - one or more recipients and instead will continue to - loop endlessly through one or more MTAs. This variable - counts the number of times the MTA has detected such a - situation since MTA initialization. Note that the - mechanism MTAs use to detect loops (e.g., trace field - counting, count of references to this MTA in a trace - field, examination of DNS or other directory information, - etc.), the level at which loops are detected (e.g., per - message, per recipient, per directory entry, etc.), and - the handling of a loop once it is detected (e.g., looping - - messages are held, looping messages are bounced or sent - to the postmaster, messages that the MTA knows will loop - won't be accepted, etc.) vary widely from one MTA to the - next and cannot be inferred from this variable." - ::= {mtaEntry 12} - --- MTAs typically group inbound reception, queue storage, and --- outbound transmission in some way, rather than accounting for --- such operations only across the MTA as a whole. In the most --- extreme case separate information will be maintained for each --- different entity that receives messages and for each entity --- the MTA stores messages for and delivers messages to. Other --- MTAs may elect to treat all reception equally, all queue --- storage equally, all deliveries equally, or some combination --- of this. Overlapped groupings are also possible, where an MTA --- decomposes its traffic in different ways for different --- purposes. - --- In any case, a grouping abstraction is an extremely useful for --- breaking down the activities of an MTA. For purposes of --- labelling this will be called a "group" in this MIB. - --- Each group contains all the variables needed to monitor all --- aspects of an MTA's operation. However, the fact that all --- groups contain all possible variables does not imply that all --- groups must use all possible variables. For example, a single --- group might be used to monitor only one kind of event (inbound --- processing, outbound processing, or storage). In this sort of --- configuration any counters that are unused as a result of a --- given MTA's use of the group construct must be inaccessible; --- e.g., returning either a noSuchName error (for an SNMPv1 get), --- or a noSuchInstance exception (for an SNMPv2 get). - --- Groups can be created at any time after MTA initialization. Once --- a group is created it should not be deleted or its mtaGroupIndex --- changed unless the MTA is reinitialized. - --- Groups are not necessarily mutually exclusive. A given event may --- be recorded by more than one group, a message may be seen as --- stored by more than one group, and so on. Groups should be all --- inclusive, however: if groups are implemented all aspects of an --- MTA's operation should be registered in at least one group. --- This freedom lets implementors use different sets of groups to --- provide different "views" of an MTA. - --- The possibility of overlap between groups means that summing --- variables across groups may not produce values equal to those in --- the mtaTable. mtaTable should always provide accurate information - --- about the MTA as a whole. - --- The term "channel" is often used in MTA implementations; channels --- are usually, but not always, equivalent to a group. However, --- this MIB does not use the term "channel" because there is no --- requirement that an MTA supporting this MIB has to map its --- "channel" abstraction one-to-one onto the MIB's group abstraction. - --- An MTA may create a group or group of groups at any time. Once --- created, however, an MTA cannot delete an entry for a group from --- the group table. Deletion is only allowed when the MTA is --- reinitialized, and is not required even then. This restriction --- is imposed so that monitoring agents can rely on group --- assignments being consistent across multiple query operations. - --- Groups may be laid out so as to form a hierarchical arrangement, --- with some groups acting as subgroups for other groups. --- Alternately, disjoint groups of groups may be used to provide --- different sorts of "snapshots" of MTA operation. The --- mtaGroupHierarchy variable provides an indication of how each --- group fits into the overall arrangement being used. - --- Note that SNMP also defines and uses term "group". MTA groups are --- NOT the same as SNMP groups. - -mtaGroupTable OBJECT-TYPE - SYNTAX SEQUENCE OF MtaGroupEntry - MAX-ACCESS not-accessible - STATUS current - DESCRIPTION - "The table holding information specific to each MTA group." - ::= {mta 2} - -mtaGroupEntry OBJECT-TYPE - SYNTAX MtaGroupEntry - MAX-ACCESS not-accessible - STATUS current - DESCRIPTION - "The entry associated with each MTA group." - INDEX {applIndex, mtaGroupIndex} - ::= {mtaGroupTable 1} - -MtaGroupEntry ::= SEQUENCE { - mtaGroupIndex - INTEGER, - mtaGroupReceivedMessages - Counter32, - mtaGroupRejectedMessages - - Counter32, - mtaGroupStoredMessages - Gauge32, - mtaGroupTransmittedMessages - Counter32, - mtaGroupReceivedVolume - Counter32, - mtaGroupStoredVolume - Gauge32, - mtaGroupTransmittedVolume - Counter32, - mtaGroupReceivedRecipients - Counter32, - mtaGroupStoredRecipients - Gauge32, - mtaGroupTransmittedRecipients - Counter32, - mtaGroupOldestMessageStored - TimeInterval, - mtaGroupInboundAssociations - Gauge32, - mtaGroupOutboundAssociations - Gauge32, - mtaGroupAccumulatedInboundAssociations - Counter32, - mtaGroupAccumulatedOutboundAssociations - Counter32, - mtaGroupLastInboundActivity - TimeInterval, - mtaGroupLastOutboundActivity - TimeInterval, - mtaGroupLastOutboundAssociationAttempt - TimeInterval, - mtaGroupRejectedInboundAssociations - Counter32, - mtaGroupFailedOutboundAssociations - Counter32, - mtaGroupInboundRejectionReason - SnmpAdminString, - mtaGroupOutboundConnectFailureReason - SnmpAdminString, - mtaGroupScheduledRetry - TimeInterval, - mtaGroupMailProtocol - OBJECT IDENTIFIER, - mtaGroupName - SnmpAdminString, - mtaGroupSuccessfulConvertedMessages - - Counter32, - mtaGroupFailedConvertedMessages - Counter32, - mtaGroupDescription - SnmpAdminString, - mtaGroupURL - URLString, - mtaGroupCreationTime - TimeInterval, - mtaGroupHierarchy - INTEGER, - mtaGroupOldestMessageId - SnmpAdminString, - mtaGroupLoopsDetected - Counter32 -} - -mtaGroupIndex OBJECT-TYPE - SYNTAX INTEGER (1..2147483647) - MAX-ACCESS not-accessible - STATUS current - DESCRIPTION - "The index associated with a group for a given MTA." - ::= {mtaGroupEntry 1} - -mtaGroupReceivedMessages OBJECT-TYPE - SYNTAX Counter32 - MAX-ACCESS read-only - STATUS current - DESCRIPTION - "The number of messages received to this group since - group creation." - ::= {mtaGroupEntry 2} - -mtaGroupRejectedMessages OBJECT-TYPE - SYNTAX Counter32 - MAX-ACCESS read-only - STATUS current - DESCRIPTION - "The number of messages rejected by this group since - group creation." - ::= {mtaGroupEntry 3} - -mtaGroupStoredMessages OBJECT-TYPE - SYNTAX Gauge32 - MAX-ACCESS read-only - STATUS current - DESCRIPTION - "The total number of messages currently stored in this - group's queue." - ::= {mtaGroupEntry 4} - -mtaGroupTransmittedMessages OBJECT-TYPE - SYNTAX Counter32 - MAX-ACCESS read-only - STATUS current - DESCRIPTION - "The number of messages transmitted by this group since - group creation." - ::= {mtaGroupEntry 5} - -mtaGroupReceivedVolume OBJECT-TYPE - SYNTAX Counter32 - UNITS "K-octets" - MAX-ACCESS read-only - STATUS current - DESCRIPTION - "The total volume of messages received to this group since - group creation, measured in kilo-octets. This volume - should include all transferred data that is logically above - the mail transport protocol level. For example, an - SMTP-based MTA should use the number of kilo-octets in the - message header and body, while an X.400-based MTA should use - the number of kilo-octets of P2 data." - ::= {mtaGroupEntry 6} - -mtaGroupStoredVolume OBJECT-TYPE - SYNTAX Gauge32 - UNITS "K-octets" - MAX-ACCESS read-only - STATUS current - DESCRIPTION - "The total volume of messages currently stored in this - group's queue, measured in kilo-octets. This volume should - include all stored data that is logically above the mail - transport protocol level. For example, an SMTP-based - MTA should use the number of kilo-octets in the message - header and body, while an X.400-based MTA would use the - number of kilo-octets of P2 data." - ::= {mtaGroupEntry 7} - -mtaGroupTransmittedVolume OBJECT-TYPE - SYNTAX Counter32 - UNITS "K-octets" - MAX-ACCESS read-only - STATUS current - DESCRIPTION - "The total volume of messages transmitted by this group - since group creation, measured in kilo-octets. This - volume should include all transferred data that is logically - above the mail transport protocol level. For example, an - SMTP-based MTA should use the number of kilo-octets in the - message header and body, while an X.400-based MTA should use - the number of kilo-octets of P2 data." - ::= {mtaGroupEntry 8} - -mtaGroupReceivedRecipients OBJECT-TYPE - SYNTAX Counter32 - MAX-ACCESS read-only - STATUS current - DESCRIPTION - "The total number of recipients specified in all messages - received to this group since group creation. - Recipients this MTA has no responsibility for should not - be counted." - ::= {mtaGroupEntry 9} - -mtaGroupStoredRecipients OBJECT-TYPE - SYNTAX Gauge32 - MAX-ACCESS read-only - STATUS current - DESCRIPTION - "The total number of recipients specified in all messages - currently stored in this group's queue. Recipients this - MTA has no responsibility for should not be counted." - ::= {mtaGroupEntry 10} - -mtaGroupTransmittedRecipients OBJECT-TYPE - SYNTAX Counter32 - MAX-ACCESS read-only - STATUS current - DESCRIPTION - "The total number of recipients specified in all messages - transmitted by this group since group creation. - Recipients this MTA had no responsibility for should not - be counted." - ::= {mtaGroupEntry 11} - -mtaGroupOldestMessageStored OBJECT-TYPE - SYNTAX TimeInterval - MAX-ACCESS read-only - STATUS current - DESCRIPTION - "Time since the oldest message in this group's queue was - - placed in the queue." - ::= {mtaGroupEntry 12} - -mtaGroupInboundAssociations OBJECT-TYPE - SYNTAX Gauge32 - MAX-ACCESS read-only - STATUS current - DESCRIPTION - "The number of current associations to the group, where the - group is the responder." - ::= {mtaGroupEntry 13} - -mtaGroupOutboundAssociations OBJECT-TYPE - SYNTAX Gauge32 - MAX-ACCESS read-only - STATUS current - DESCRIPTION - "The number of current associations to the group, where the - group is the initiator." - ::= {mtaGroupEntry 14} - -mtaGroupAccumulatedInboundAssociations OBJECT-TYPE - SYNTAX Counter32 - MAX-ACCESS read-only - STATUS current - DESCRIPTION - "The total number of associations to the group since - group creation, where the MTA was the responder." - ::= {mtaGroupEntry 15} - -mtaGroupAccumulatedOutboundAssociations OBJECT-TYPE - SYNTAX Counter32 - MAX-ACCESS read-only - STATUS current - DESCRIPTION - "The total number of associations from the group since - group creation, where the MTA was the initiator." - ::= {mtaGroupEntry 16} - -mtaGroupLastInboundActivity OBJECT-TYPE - SYNTAX TimeInterval - MAX-ACCESS read-only - STATUS current - DESCRIPTION - "Time since the last time that this group had an active - inbound association for purposes of message reception." - ::= {mtaGroupEntry 17} - -mtaGroupLastOutboundActivity OBJECT-TYPE - SYNTAX TimeInterval - MAX-ACCESS read-only - STATUS current - DESCRIPTION - "Time since the last time that this group had a - successful outbound association for purposes of - message delivery." - ::= {mtaGroupEntry 18} - -mtaGroupLastOutboundAssociationAttempt OBJECT-TYPE - SYNTAX TimeInterval - MAX-ACCESS read-only - STATUS current - DESCRIPTION - "Time since the last time that this group attempted - to make an outbound association for purposes of - message delivery." - ::= {mtaGroupEntry 34} - -mtaGroupRejectedInboundAssociations OBJECT-TYPE - SYNTAX Counter32 - MAX-ACCESS read-only - STATUS current - DESCRIPTION - "The total number of inbound associations the group has - rejected, since group creation. Rejected associations - are not counted in the accumulated association totals." - ::= {mtaGroupEntry 19} - -mtaGroupFailedOutboundAssociations OBJECT-TYPE - SYNTAX Counter32 - MAX-ACCESS read-only - STATUS current - DESCRIPTION - "The total number associations where the group was the - initiator and association establishment has failed, - since group creation. Failed associations are - not counted in the accumulated association totals." - ::= {mtaGroupEntry 20} - -mtaGroupInboundRejectionReason OBJECT-TYPE - SYNTAX SnmpAdminString - MAX-ACCESS read-only - STATUS current - DESCRIPTION - "The failure reason, if any, for the last association this - group refused to respond to. If no association attempt - - has been made since the MTA was initialized the value - should be 'never'." - ::= {mtaGroupEntry 21} - -mtaGroupOutboundConnectFailureReason OBJECT-TYPE - SYNTAX SnmpAdminString - MAX-ACCESS read-only - STATUS current - DESCRIPTION - "The failure reason, if any, for the last association attempt - this group initiated. If no association attempt has been - made since the MTA was initialized the value should be - 'never'." - ::= {mtaGroupEntry 22} - -mtaGroupScheduledRetry OBJECT-TYPE - SYNTAX TimeInterval - MAX-ACCESS read-only - STATUS current - DESCRIPTION - "The amount of time until this group is next scheduled to - attempt to make an association." - ::= {mtaGroupEntry 23} - -mtaGroupMailProtocol OBJECT-TYPE - SYNTAX OBJECT IDENTIFIER - MAX-ACCESS read-only - STATUS current - DESCRIPTION - "An identification of the protocol being used by this group. - For an group employing OSI protocols, this will be the - Application Context. For Internet applications, OID - values of the form {applTCPProtoID port} or {applUDPProtoID - port} are used for TCP-based and UDP-based protocols, - respectively. In either case 'port' corresponds to the - primary port number being used by the protocol. The - usual IANA procedures may be used to register ports for - new protocols. applTCPProtoID and applUDPProtoID are - defined in the NETWORK-SERVICES-MIB, RFC 2788." - ::= {mtaGroupEntry 24} - -mtaGroupName OBJECT-TYPE - SYNTAX SnmpAdminString - MAX-ACCESS read-only - STATUS current - DESCRIPTION - "A descriptive name for the group. If this group connects to - a single remote MTA this should be the name of that MTA. If - - this in turn is an Internet MTA this should be the domain - name. For an OSI MTA it should be the string encoded - distinguished name of the managed object using the format - defined in RFC 2253. For X.400(1984) MTAs which do not - have a Distinguished Name, the RFC 2156 syntax - 'mta in globalid' used in X400-Received: fields can be - used." - ::= {mtaGroupEntry 25} - -mtaGroupSuccessfulConvertedMessages OBJECT-TYPE - SYNTAX Counter32 - MAX-ACCESS read-only - STATUS current - DESCRIPTION - "The number of messages that have been successfully - converted from one form to another in this group - since group creation." - ::= {mtaGroupEntry 26} - -mtaGroupFailedConvertedMessages OBJECT-TYPE - SYNTAX Counter32 - MAX-ACCESS read-only - STATUS current - DESCRIPTION - "The number of messages for which an unsuccessful - attempt was made to convert them from one form to - another in this group since group creation." - ::= {mtaGroupEntry 27} - -mtaGroupDescription OBJECT-TYPE - SYNTAX SnmpAdminString - MAX-ACCESS read-only - STATUS current - DESCRIPTION - "A description of the group's purpose. This information is - intended to identify the group in a status display." - ::= {mtaGroupEntry 28} - -mtaGroupURL OBJECT-TYPE - SYNTAX URLString - MAX-ACCESS read-only - STATUS current - DESCRIPTION - "A URL pointing to a description of the group. This - information is intended to identify and briefly describe - the group in a status display." - ::= {mtaGroupEntry 29} - -mtaGroupCreationTime OBJECT-TYPE - SYNTAX TimeInterval - MAX-ACCESS read-only - STATUS current - DESCRIPTION - "Time since this group was first created." - ::= {mtaGroupEntry 30} - -mtaGroupHierarchy OBJECT-TYPE - SYNTAX INTEGER (-2147483648..2147483647) - MAX-ACCESS read-only - STATUS current - DESCRIPTION - "Describes how this group fits into the hierarchy. A - positive value is interpreted as an mtaGroupIndex - value for some other group whose variables include - those of this group (and usually others). A negative - value is interpreted as a group collection code: Groups - with common negative hierarchy values comprise one - particular breakdown of MTA activity as a whole. A - zero value means that this MIB implementation doesn't - implement hierarchy indicators and thus the overall - group hierarchy cannot be determined." - ::= {mtaGroupEntry 31} - -mtaGroupOldestMessageId OBJECT-TYPE - SYNTAX SnmpAdminString - MAX-ACCESS read-only - STATUS current - DESCRIPTION - "Message ID of the oldest message in the group's queue. - Whenever possible this should be in the form of an - RFC 822 msg-id; X.400 may convert X.400 message - identifiers to this form by following the rules laid - out in RFC2156." - ::= {mtaGroupEntry 32} - -mtaGroupLoopsDetected OBJECT-TYPE - SYNTAX Counter32 - MAX-ACCESS read-only - STATUS current - DESCRIPTION - "A message loop is defined as a situation where the MTA - decides that a given message will never be delivered to - one or more recipients and instead will continue to - loop endlessly through one or more MTAs. This variable - counts the number of times the MTA has detected such a - situation in conjunction with something associated with - - this group since group creation. Note that the - mechanism MTAs use to detect loops (e.g., trace field - counting, count of references to this MTA in a trace - field, examination of DNS or other directory information, - etc.), the level at which loops are detected (e.g., per - message, per recipient, per directory entry, etc.), and - the handling of a loop once it is detected (e.g., looping - messages are held, looping messages are bounced or sent - to the postmaster, messages that the MTA knows will loop - won't be accepted, etc.) vary widely from one MTA to the - next and cannot be inferred from this variable." - ::= {mtaGroupEntry 33} - --- The mtaGroupAssociationTable provides a means of correlating --- entries in the network services association table with the --- MTA group responsible for the association. - -mtaGroupAssociationTable OBJECT-TYPE - SYNTAX SEQUENCE OF MtaGroupAssociationEntry - MAX-ACCESS not-accessible - STATUS current - DESCRIPTION - "The table holding information regarding the associations - for each MTA group." - ::= {mta 3} - -mtaGroupAssociationEntry OBJECT-TYPE - SYNTAX MtaGroupAssociationEntry - MAX-ACCESS not-accessible - STATUS current - DESCRIPTION - "The entry holding information regarding the associations - for each MTA group." - INDEX {applIndex, mtaGroupIndex, mtaGroupAssociationIndex} - ::= {mtaGroupAssociationTable 1} - -MtaGroupAssociationEntry ::= SEQUENCE { - mtaGroupAssociationIndex - INTEGER -} - -mtaGroupAssociationIndex OBJECT-TYPE - SYNTAX INTEGER (1..2147483647) - MAX-ACCESS read-only - STATUS current - DESCRIPTION - "Reference into association table to allow correlation of - this group's active associations with the association table." - ::= {mtaGroupAssociationEntry 1} - --- The mtaGroupErrorTable gives each group a way of tallying --- the specific errors it has encountered. The mechanism --- defined here uses RFC 1893 status codes to identify --- various specific errors. There are also classes for generic --- errors of various sorts, and the entire mechanism is also --- extensible, in that new error codes can be defined at any --- time. - -mtaGroupErrorTable OBJECT-TYPE - SYNTAX SEQUENCE OF MtaGroupErrorEntry - MAX-ACCESS not-accessible - STATUS current - DESCRIPTION - "The table holding information regarding accumulated errors - for each MTA group." - ::= {mta 5} - -mtaGroupErrorEntry OBJECT-TYPE - SYNTAX MtaGroupErrorEntry - MAX-ACCESS not-accessible - STATUS current - DESCRIPTION - "The entry holding information regarding accumulated - errors for each MTA group." - INDEX {applIndex, mtaGroupIndex, mtaStatusCode} - ::= {mtaGroupErrorTable 1} - -MtaGroupErrorEntry ::= SEQUENCE { - mtaStatusCode - INTEGER (4000000..5999999), - mtaGroupInboundErrorCount - Counter32, - mtaGroupInternalErrorCount - Counter32, - mtaGroupOutboundErrorCount - Counter32 -} - -mtaGroupInboundErrorCount OBJECT-TYPE - SYNTAX Counter32 - MAX-ACCESS read-only - STATUS current - DESCRIPTION - "Count of the number of errors of a given type that have - been accumulated in association with a particular group - while processing incoming messages. In the case of SMTP - - these will typically be errors reporting by an SMTP - server to the remote client; in the case of X.400 - these will typically be errors encountered while - processing an incoming message." - ::= {mtaGroupErrorEntry 1} - -mtaGroupInternalErrorCount OBJECT-TYPE - SYNTAX Counter32 - MAX-ACCESS read-only - STATUS current - DESCRIPTION - "Count of the number of errors of a given type that have - been accumulated in association with a particular group - during internal MTA processing." - ::= {mtaGroupErrorEntry 2} - -mtaGroupOutboundErrorCount OBJECT-TYPE - SYNTAX Counter32 - MAX-ACCESS read-only - STATUS current - DESCRIPTION - "Count of the number of errors of a given type that have - been accumulated in association with a particular group's - outbound connection activities. In the case of an SMTP - client these will typically be errors reported while - attempting to contact or while communicating with the - remote SMTP server. In the case of X.400 these will - typically be errors encountered while constructing - or attempting to deliver an outgoing message." - ::= {mtaGroupErrorEntry 3} - -mtaStatusCode OBJECT-TYPE - SYNTAX INTEGER (4000000..5999999) - MAX-ACCESS not-accessible - STATUS current - DESCRIPTION - "An index capable of representing an Enhanced Mail System - Status Code. Enhanced Mail System Status Codes are - defined in RFC 1893. These codes have the form - - class.subject.detail - - Here 'class' is either 2, 4, or 5 and both 'subject' and - 'detail' are integers in the range 0..999. Given a status - code the corresponding index value is defined to be - ((class * 1000) + subject) * 1000 + detail. Both SMTP - error response codes and X.400 reason and diagnostic codes - can be mapped into these codes, resulting in a namespace - - capable of describing most error conditions a mail system - encounters in a generic yet detailed way." - ::= {mtaGroupErrorEntry 4} - --- Conformance information - -mtaConformance OBJECT IDENTIFIER ::= {mta 4} - -mtaGroups OBJECT IDENTIFIER ::= {mtaConformance 1} -mtaCompliances OBJECT IDENTIFIER ::= {mtaConformance 2} - --- Compliance statements - -mtaCompliance MODULE-COMPLIANCE - STATUS current - DESCRIPTION - "The compliance statement for RFC 1566 implementations - which support the Mail Monitoring MIB for basic - monitoring of MTAs." - MODULE -- this module - MANDATORY-GROUPS {mtaRFC1566Group} - ::= {mtaCompliances 1} - -mtaAssocCompliance MODULE-COMPLIANCE - STATUS current - DESCRIPTION - "The compliance statement for RFC 1566 implementations - which support the Mail Monitoring MIB for monitoring - of MTAs and their associations." - MODULE -- this module - MANDATORY-GROUPS {mtaRFC1566Group, mtaRFC1566AssocGroup} - ::= {mtaCompliances 2} - -mtaRFC2249Compliance MODULE-COMPLIANCE - STATUS current - DESCRIPTION - "The compliance statement for RFC 2249 implementations - which support the Mail Monitoring MIB for basic - monitoring of MTAs." - MODULE -- this module - MANDATORY-GROUPS {mtaRFC2249Group} - ::= {mtaCompliances 5} - -mtaRFC2249AssocCompliance MODULE-COMPLIANCE - STATUS current - DESCRIPTION - "The compliance statement for RFC 2249 implementations - - which support the Mail Monitoring MIB for monitoring of - MTAs and their associations." - MODULE -- this module - MANDATORY-GROUPS {mtaRFC2249Group, mtaRFC2249AssocGroup} - ::= {mtaCompliances 6} - -mtaRFC2249ErrorCompliance MODULE-COMPLIANCE - STATUS current - DESCRIPTION - "The compliance statement for RFC 2249 implementations - which support the Mail Monitoring MIB for monitoring of - MTAs and detailed errors." - MODULE -- this module - MANDATORY-GROUPS {mtaRFC2249Group, mtaRFC2249ErrorGroup} - ::= {mtaCompliances 7} - -mtaRFC2249FullCompliance MODULE-COMPLIANCE - STATUS current - DESCRIPTION - "The compliance statement for RFC 2249 implementations - which support the full Mail Monitoring MIB for - monitoring of MTAs, associations, and detailed errors." - MODULE -- this module - MANDATORY-GROUPS {mtaRFC2249Group, mtaRFC2249AssocGroup, - mtaRFC2249ErrorGroup} - ::= {mtaCompliances 8} - -mtaRFC2789Compliance MODULE-COMPLIANCE - STATUS current - DESCRIPTION - "The compliance statement for RFC 2789 implementations - which support the Mail Monitoring MIB for basic - monitoring of MTAs." - MODULE -- this module - MANDATORY-GROUPS {mtaRFC2789Group} - ::= {mtaCompliances 9} - -mtaRFC2789AssocCompliance MODULE-COMPLIANCE - STATUS current - DESCRIPTION - "The compliance statement for RFC 2789 implementations - which support the Mail Monitoring MIB for monitoring of - MTAs and their associations." - MODULE -- this module - MANDATORY-GROUPS {mtaRFC2789Group, mtaRFC2789AssocGroup} - ::= {mtaCompliances 10} - -mtaRFC2789ErrorCompliance MODULE-COMPLIANCE - STATUS current - DESCRIPTION - "The compliance statement for RFC 2789 implementations - which support the Mail Monitoring MIB for monitoring of - MTAs and detailed errors." - MODULE -- this module - MANDATORY-GROUPS {mtaRFC2789Group, mtaRFC2789ErrorGroup} - ::= {mtaCompliances 11} - -mtaRFC2789FullCompliance MODULE-COMPLIANCE - STATUS current - DESCRIPTION - "The compliance statement for RFC 2789 implementations - which support the full Mail Monitoring MIB for - monitoring of MTAs, associations, and detailed errors." - MODULE -- this module - MANDATORY-GROUPS {mtaRFC2789Group, mtaRFC2789AssocGroup, - mtaRFC2789ErrorGroup} - ::= {mtaCompliances 12} - --- Units of conformance - -mtaRFC1566Group OBJECT-GROUP - OBJECTS { - mtaReceivedMessages, mtaStoredMessages, - mtaTransmittedMessages, mtaReceivedVolume, mtaStoredVolume, - mtaTransmittedVolume, mtaReceivedRecipients, - mtaStoredRecipients, mtaTransmittedRecipients, - mtaGroupReceivedMessages, mtaGroupRejectedMessages, - mtaGroupStoredMessages, mtaGroupTransmittedMessages, - mtaGroupReceivedVolume, mtaGroupStoredVolume, - mtaGroupTransmittedVolume, mtaGroupReceivedRecipients, - mtaGroupStoredRecipients, mtaGroupTransmittedRecipients, - mtaGroupOldestMessageStored, mtaGroupInboundAssociations, - mtaGroupOutboundAssociations, - mtaGroupAccumulatedInboundAssociations, - mtaGroupAccumulatedOutboundAssociations, - mtaGroupLastInboundActivity, mtaGroupLastOutboundActivity, - mtaGroupRejectedInboundAssociations, - mtaGroupFailedOutboundAssociations, - mtaGroupInboundRejectionReason, - mtaGroupOutboundConnectFailureReason, - mtaGroupScheduledRetry, mtaGroupMailProtocol, mtaGroupName} - STATUS current - DESCRIPTION - "A collection of objects providing basic monitoring of MTAs. - This is the original set of such objects defined in RFC - 1566." - ::= {mtaGroups 10} - -mtaRFC1566AssocGroup OBJECT-GROUP - OBJECTS { - mtaGroupAssociationIndex} - STATUS current - DESCRIPTION - "A collection of objects providing monitoring of MTA - associations. This is the original set of such objects - defined in RFC 1566." - ::= {mtaGroups 11} - -mtaRFC2249Group OBJECT-GROUP - OBJECTS { - mtaReceivedMessages, mtaStoredMessages, - mtaTransmittedMessages, mtaReceivedVolume, mtaStoredVolume, - mtaTransmittedVolume, mtaReceivedRecipients, - mtaStoredRecipients, mtaTransmittedRecipients, - mtaSuccessfulConvertedMessages, mtaFailedConvertedMessages, - mtaGroupReceivedMessages, mtaGroupRejectedMessages, - mtaGroupStoredMessages, mtaGroupTransmittedMessages, - mtaGroupReceivedVolume, mtaGroupStoredVolume, - mtaGroupTransmittedVolume, mtaGroupReceivedRecipients, - mtaGroupStoredRecipients, mtaGroupTransmittedRecipients, - mtaGroupOldestMessageStored, mtaGroupInboundAssociations, - mtaGroupOutboundAssociations, mtaLoopsDetected, - mtaGroupAccumulatedInboundAssociations, - mtaGroupAccumulatedOutboundAssociations, - mtaGroupLastInboundActivity, mtaGroupLastOutboundActivity, - mtaGroupLastOutboundAssociationAttempt, - mtaGroupRejectedInboundAssociations, - mtaGroupFailedOutboundAssociations, - mtaGroupInboundRejectionReason, - mtaGroupOutboundConnectFailureReason, - mtaGroupScheduledRetry, mtaGroupMailProtocol, mtaGroupName, - mtaGroupSuccessfulConvertedMessages, - mtaGroupFailedConvertedMessages, mtaGroupDescription, - mtaGroupURL, mtaGroupCreationTime, mtaGroupHierarchy, - mtaGroupOldestMessageId, mtaGroupLoopsDetected} - STATUS current - DESCRIPTION - "A collection of objects providing basic monitoring of MTAs. - This group was originally defined in RFC 2249." - ::= {mtaGroups 4} - -mtaRFC2249AssocGroup OBJECT-GROUP - OBJECTS { - mtaGroupAssociationIndex} - STATUS current - DESCRIPTION - "A collection of objects providing monitoring of MTA - associations. This group was originally defined in RFC - 2249." - ::= {mtaGroups 5} - -mtaRFC2249ErrorGroup OBJECT-GROUP - OBJECTS { - mtaGroupInboundErrorCount, mtaGroupInternalErrorCount, - mtaGroupOutboundErrorCount} - STATUS current - DESCRIPTION - "A collection of objects providing monitoring of - detailed MTA errors. This group was originally defined - in RFC 2249." - ::= {mtaGroups 6} - -mtaRFC2789Group OBJECT-GROUP - OBJECTS { - mtaReceivedMessages, mtaStoredMessages, - mtaTransmittedMessages, mtaReceivedVolume, mtaStoredVolume, - mtaTransmittedVolume, mtaReceivedRecipients, - mtaStoredRecipients, mtaTransmittedRecipients, - mtaSuccessfulConvertedMessages, mtaFailedConvertedMessages, - mtaGroupReceivedMessages, mtaGroupRejectedMessages, - mtaGroupStoredMessages, mtaGroupTransmittedMessages, - mtaGroupReceivedVolume, mtaGroupStoredVolume, - mtaGroupTransmittedVolume, mtaGroupReceivedRecipients, - mtaGroupStoredRecipients, mtaGroupTransmittedRecipients, - mtaGroupOldestMessageStored, mtaGroupInboundAssociations, - mtaGroupOutboundAssociations, mtaLoopsDetected, - mtaGroupAccumulatedInboundAssociations, - mtaGroupAccumulatedOutboundAssociations, - mtaGroupLastInboundActivity, mtaGroupLastOutboundActivity, - mtaGroupLastOutboundAssociationAttempt, - mtaGroupRejectedInboundAssociations, - mtaGroupFailedOutboundAssociations, - mtaGroupInboundRejectionReason, - mtaGroupOutboundConnectFailureReason, - mtaGroupScheduledRetry, mtaGroupMailProtocol, mtaGroupName, - mtaGroupSuccessfulConvertedMessages, - mtaGroupFailedConvertedMessages, mtaGroupDescription, - mtaGroupURL, mtaGroupCreationTime, mtaGroupHierarchy, - mtaGroupOldestMessageId, mtaGroupLoopsDetected} - STATUS current - DESCRIPTION - "A collection of objects providing basic monitoring of MTAs. - - This is the appropriate group for RFC 2789." - ::= {mtaGroups 7} - -mtaRFC2789AssocGroup OBJECT-GROUP - OBJECTS { - mtaGroupAssociationIndex} - STATUS current - DESCRIPTION - "A collection of objects providing monitoring of MTA - associations. This is the appropriate group for RFC - 2789 association monitoring." - ::= {mtaGroups 8} - -mtaRFC2789ErrorGroup OBJECT-GROUP - OBJECTS { - mtaGroupInboundErrorCount, mtaGroupInternalErrorCount, - mtaGroupOutboundErrorCount} - STATUS current - DESCRIPTION - "A collection of objects providing monitoring of - detailed MTA errors. This is the appropriate group - for RFC 2789 error monitoring." - ::= {mtaGroups 9} - -END diff --git a/mibs/NETWORK-SERVICES-MIB b/mibs/NETWORK-SERVICES-MIB deleted file mode 100644 index 0f2cabecb..000000000 --- a/mibs/NETWORK-SERVICES-MIB +++ /dev/null @@ -1,626 +0,0 @@ -NETWORK-SERVICES-MIB DEFINITIONS ::= BEGIN - -IMPORTS - OBJECT-TYPE, Counter32, Gauge32, MODULE-IDENTITY, mib-2 - FROM SNMPv2-SMI - TimeStamp, TEXTUAL-CONVENTION - FROM SNMPv2-TC - MODULE-COMPLIANCE, OBJECT-GROUP - FROM SNMPv2-CONF - SnmpAdminString - FROM SNMP-FRAMEWORK-MIB; - -application MODULE-IDENTITY - LAST-UPDATED "200003030000Z" - ORGANIZATION "IETF Mail and Directory Management Working Group" - - CONTACT-INFO - " Ned Freed - - Postal: Innosoft International, Inc. - 1050 Lakes Drive - West Covina, CA 91790 - US - - Tel: +1 626 919 3600 - Fax: +1 626 919 3614 - - E-Mail: ned.freed@innosoft.com" - DESCRIPTION - "The MIB module describing network service applications" - REVISION "200003030000Z" - DESCRIPTION - "This revision, published in RFC 2788, changes a number of - DisplayStrings to SnmpAdminStrings. Note that this change - is not strictly supported by SMIv2. However, the alternative - of deprecating the old objects and defining new objects - would have a more adverse impact on backward compatibility - and interoperability, given the particular semantics of - these objects. The defining reference for distinguished - names has also been updated from RFC 1779 to RFC 2253." - REVISION "199905120000Z" - DESCRIPTION - "This revision fixes a few small technical problems found - in previous versions, mostly in regards to the conformance - groups for different versions of this MIB. No changes have - been made to the objects this MIB defines since RFC 2248." - REVISION "199708170000Z" - DESCRIPTION - "This revision, published in RFC 2248, adds the - applDescription and applURL objects, adds the quiescing - state to the applOperStatus object and renames the MIB - from the APPLICATION-MIB to the NETWORK-SERVICE-MIB." - REVISION "199311280000Z" - DESCRIPTION - "The original version of this MIB was published in RFC 1565" - ::= {mib-2 27} - --- Textual conventions - --- DistinguishedName is used to refer to objects in the --- directory. - -DistinguishedName ::= TEXTUAL-CONVENTION - DISPLAY-HINT "255a" - STATUS current - DESCRIPTION - "A Distinguished Name represented in accordance with - RFC 2253, presented in the UTF-8 charset defined in - RFC 2279." - SYNTAX OCTET STRING (SIZE (0..255)) - --- Uniform Resource Locators are stored in URLStrings. - -URLString ::= TEXTUAL-CONVENTION - DISPLAY-HINT "255a" - STATUS current - DESCRIPTION - "A Uniform Resource Locator represented in accordance - with RFCs 1738 and 2368, presented in the NVT ASCII - charset defined in RFC 854." - SYNTAX OCTET STRING (SIZE (0..255)) - --- The basic applTable contains a list of the application --- entities. - -applTable OBJECT-TYPE - SYNTAX SEQUENCE OF ApplEntry - MAX-ACCESS not-accessible - STATUS current - DESCRIPTION - "The table holding objects which apply to all different - kinds of applications providing network services. - Each network service application capable of being - monitored should have a single entry in this table." - ::= {application 1} - -applEntry OBJECT-TYPE - SYNTAX ApplEntry - MAX-ACCESS not-accessible - STATUS current - DESCRIPTION - "An entry associated with a single network service - application." - INDEX {applIndex} - ::= {applTable 1} - -ApplEntry ::= SEQUENCE { - applIndex - INTEGER, - applName - SnmpAdminString, - applDirectoryName - - DistinguishedName, - applVersion - SnmpAdminString, - applUptime - TimeStamp, - applOperStatus - INTEGER, - applLastChange - TimeStamp, - applInboundAssociations - Gauge32, - applOutboundAssociations - Gauge32, - applAccumulatedInboundAssociations - Counter32, - applAccumulatedOutboundAssociations - Counter32, - applLastInboundActivity - TimeStamp, - applLastOutboundActivity - TimeStamp, - applRejectedInboundAssociations - Counter32, - applFailedOutboundAssociations - Counter32, - applDescription - SnmpAdminString, - applURL - URLString -} - -applIndex OBJECT-TYPE - SYNTAX INTEGER (1..2147483647) - MAX-ACCESS not-accessible - STATUS current - DESCRIPTION - "An index to uniquely identify the network service - application. This attribute is the index used for - lexicographic ordering of the table." - ::= {applEntry 1} - -applName OBJECT-TYPE - SYNTAX SnmpAdminString - MAX-ACCESS read-only - STATUS current - DESCRIPTION - "The name the network service application chooses to be - known by." - ::= {applEntry 2} - -applDirectoryName OBJECT-TYPE - SYNTAX DistinguishedName - MAX-ACCESS read-only - STATUS current - DESCRIPTION - "The Distinguished Name of the directory entry where - static information about this application is stored. - An empty string indicates that no information about - the application is available in the directory." - ::= {applEntry 3} - -applVersion OBJECT-TYPE - SYNTAX SnmpAdminString - MAX-ACCESS read-only - STATUS current - DESCRIPTION - "The version of network service application software. - This field is usually defined by the vendor of the - network service application software." - ::= {applEntry 4} -applUptime OBJECT-TYPE - SYNTAX TimeStamp - MAX-ACCESS read-only - STATUS current - DESCRIPTION - "The value of sysUpTime at the time the network service - application was last initialized. If the application was - last initialized prior to the last initialization of the - network management subsystem, then this object contains - a zero value." - ::= {applEntry 5} - -applOperStatus OBJECT-TYPE - SYNTAX INTEGER { - up(1), - down(2), - halted(3), - congested(4), - restarting(5), - quiescing(6) - } - MAX-ACCESS read-only - STATUS current - DESCRIPTION - "Indicates the operational status of the network service - application. 'down' indicates that the network service is - - not available. 'up' indicates that the network service - is operational and available. 'halted' indicates that the - service is operational but not available. 'congested' - indicates that the service is operational but no additional - inbound associations can be accommodated. 'restarting' - indicates that the service is currently unavailable but is - in the process of restarting and will be available soon. - 'quiescing' indicates that service is currently operational - but is in the process of shutting down. Additional inbound - associations may be rejected by applications in the - 'quiescing' state." - ::= {applEntry 6} - -applLastChange OBJECT-TYPE - SYNTAX TimeStamp - MAX-ACCESS read-only - STATUS current - DESCRIPTION - "The value of sysUpTime at the time the network service - application entered its current operational state. If - the current state was entered prior to the last - initialization of the local network management subsystem, - then this object contains a zero value." - ::= {applEntry 7} - -applInboundAssociations OBJECT-TYPE - SYNTAX Gauge32 - MAX-ACCESS read-only - STATUS current - DESCRIPTION - "The number of current associations to the network service - application, where it is the responder. An inbound - association occurs when another application successfully - connects to this one." - ::= {applEntry 8} - -applOutboundAssociations OBJECT-TYPE - SYNTAX Gauge32 - MAX-ACCESS read-only - STATUS current - DESCRIPTION - "The number of current associations to the network service - application, where it is the initiator. An outbound - association occurs when this application successfully - connects to another one." - ::= {applEntry 9} - -applAccumulatedInboundAssociations OBJECT-TYPE - SYNTAX Counter32 - MAX-ACCESS read-only - STATUS current - DESCRIPTION - "The total number of associations to the application entity - since application initialization, where it was the responder." - ::= {applEntry 10} - -applAccumulatedOutboundAssociations OBJECT-TYPE - SYNTAX Counter32 - MAX-ACCESS read-only - STATUS current - DESCRIPTION - "The total number of associations to the application entity - since application initialization, where it was the initiator." - ::= {applEntry 11} - -applLastInboundActivity OBJECT-TYPE - SYNTAX TimeStamp - MAX-ACCESS read-only - STATUS current - DESCRIPTION - "The value of sysUpTime at the time this application last - had an inbound association. If the last association - occurred prior to the last initialization of the network - subsystem, then this object contains a zero value." - ::= {applEntry 12} - -applLastOutboundActivity OBJECT-TYPE - SYNTAX TimeStamp - MAX-ACCESS read-only - STATUS current - DESCRIPTION - "The value of sysUpTime at the time this application last - had an outbound association. If the last association - occurred prior to the last initialization of the network - subsystem, then this object contains a zero value." - ::= {applEntry 13} - -applRejectedInboundAssociations OBJECT-TYPE - SYNTAX Counter32 - MAX-ACCESS read-only - STATUS current - DESCRIPTION - "The total number of inbound associations the application - entity has rejected, since application initialization. - Rejected associations are not counted in the accumulated - association totals. Note that this only counts - - associations the application entity has rejected itself; - it does not count rejections that occur at lower layers - of the network. Thus, this counter may not reflect the - true number of failed inbound associations." - ::= {applEntry 14} - -applFailedOutboundAssociations OBJECT-TYPE - SYNTAX Counter32 - MAX-ACCESS read-only - STATUS current - DESCRIPTION - "The total number associations where the application entity - is initiator and association establishment has failed, - since application initialization. Failed associations are - not counted in the accumulated association totals." - ::= {applEntry 15} - -applDescription OBJECT-TYPE - SYNTAX SnmpAdminString - MAX-ACCESS read-only - STATUS current - DESCRIPTION - "A text description of the application. This information - is intended to identify and briefly describe the - application in a status display." - ::= {applEntry 16} - -applURL OBJECT-TYPE - SYNTAX URLString - MAX-ACCESS read-only - STATUS current - DESCRIPTION - "A URL pointing to a description of the application. - This information is intended to identify and describe - the application in a status display." - ::= {applEntry 17} - --- The assocTable augments the information in the applTable --- with information about associations. Note that two levels --- of compliance are specified below, depending on whether --- association monitoring is mandated. - -assocTable OBJECT-TYPE - SYNTAX SEQUENCE OF AssocEntry - MAX-ACCESS not-accessible - STATUS current - DESCRIPTION - "The table holding a set of all active application - - associations." - ::= {application 2} - -assocEntry OBJECT-TYPE - SYNTAX AssocEntry - MAX-ACCESS not-accessible - STATUS current - DESCRIPTION - "An entry associated with an association for a network - service application." - INDEX {applIndex, assocIndex} - ::= {assocTable 1} - -AssocEntry ::= SEQUENCE { - assocIndex - INTEGER, - assocRemoteApplication - SnmpAdminString, - assocApplicationProtocol - OBJECT IDENTIFIER, - assocApplicationType - INTEGER, - assocDuration - TimeStamp -} - -assocIndex OBJECT-TYPE - SYNTAX INTEGER (1..2147483647) - MAX-ACCESS not-accessible - STATUS current - DESCRIPTION - "An index to uniquely identify each association for a network - service application. This attribute is the index that is - used for lexicographic ordering of the table. Note that the - table is also indexed by the applIndex." - ::= {assocEntry 1} - -assocRemoteApplication OBJECT-TYPE - SYNTAX SnmpAdminString - MAX-ACCESS read-only - STATUS current - DESCRIPTION - "The name of the system running remote network service - application. For an IP-based application this should be - either a domain name or IP address. For an OSI application - it should be the string encoded distinguished name of the - managed object. For X.400(1984) MTAs which do not have a - Distinguished Name, the RFC 2156 syntax 'mta in - - globalid' used in X400-Received: fields can be used. Note, - however, that not all connections an MTA makes are - necessarily to another MTA." - ::= {assocEntry 2} - -assocApplicationProtocol OBJECT-TYPE - SYNTAX OBJECT IDENTIFIER - MAX-ACCESS read-only - STATUS current - DESCRIPTION - "An identification of the protocol being used for the - application. For an OSI Application, this will be the - Application Context. For Internet applications, OID - values of the form {applTCPProtoID port} or {applUDPProtoID - port} are used for TCP-based and UDP-based protocols, - respectively. In either case 'port' corresponds to the - primary port number being used by the protocol. The - usual IANA procedures may be used to register ports for - new protocols." - ::= {assocEntry 3} - -assocApplicationType OBJECT-TYPE - SYNTAX INTEGER { - uainitiator(1), - uaresponder(2), - peerinitiator(3), - peerresponder(4)} - MAX-ACCESS read-only - STATUS current - DESCRIPTION - "This indicates whether the remote application is some type of - client making use of this network service (e.g., a Mail User - Agent) or a server acting as a peer. Also indicated is whether - the remote end initiated an incoming connection to the network - service or responded to an outgoing connection made by the - local application. MTAs and messaging gateways are - considered to be peers for the purposes of this variable." - ::= {assocEntry 4} - -assocDuration OBJECT-TYPE - SYNTAX TimeStamp - MAX-ACCESS read-only - STATUS current - DESCRIPTION - "The value of sysUpTime at the time this association was - started. If this association started prior to the last - initialization of the network subsystem, then this - object contains a zero value." - ::= {assocEntry 5} - --- Conformance information - -applConformance OBJECT IDENTIFIER ::= {application 3} - -applGroups OBJECT IDENTIFIER ::= {applConformance 1} -applCompliances OBJECT IDENTIFIER ::= {applConformance 2} - --- Compliance statements - -applCompliance MODULE-COMPLIANCE - STATUS obsolete - DESCRIPTION - "The compliance statement for RFC 1565 implementations - which support the Network Services Monitoring MIB - for basic monitoring of network service applications. - This is the basic compliance statement for RFC 1565." - MODULE - MANDATORY-GROUPS {applRFC1565Group} - ::= {applCompliances 1} - -assocCompliance MODULE-COMPLIANCE - STATUS obsolete - DESCRIPTION - "The compliance statement for RFC 1565 implementations - which support the Network Services Monitoring MIB - for basic monitoring of network service applications - and their associations." - MODULE - MANDATORY-GROUPS {applRFC1565Group, assocRFC1565Group} - ::= {applCompliances 2} - -applRFC2248Compliance MODULE-COMPLIANCE - STATUS deprecated - DESCRIPTION - "The compliance statement for RFC 2248 implementations - which support the Network Services Monitoring MIB - for basic monitoring of network service applications." - MODULE - MANDATORY-GROUPS {applRFC2248Group} - ::= {applCompliances 3} - -assocRFC2248Compliance MODULE-COMPLIANCE - STATUS deprecated - DESCRIPTION - "The compliance statement for RFC 2248 implementations - - which support the Network Services Monitoring MIB for - basic monitoring of network service applications and - their associations." - MODULE - MANDATORY-GROUPS {applRFC2248Group, assocRFC2248Group} - ::= {applCompliances 4} - -applRFC2788Compliance MODULE-COMPLIANCE - STATUS current - DESCRIPTION - "The compliance statement for RFC 2788 implementations - which support the Network Services Monitoring MIB - for basic monitoring of network service applications." - MODULE - MANDATORY-GROUPS {applRFC2788Group} - ::= {applCompliances 5} - -assocRFC2788Compliance MODULE-COMPLIANCE - STATUS current - DESCRIPTION - "The compliance statement for RFC 2788 implementations - which support the Network Services Monitoring MIB for - basic monitoring of network service applications and - their associations." - MODULE - MANDATORY-GROUPS {applRFC2788Group, assocRFC2788Group} - ::= {applCompliances 6} - --- Units of conformance - -applRFC1565Group OBJECT-GROUP - OBJECTS { - applName, applVersion, applUptime, applOperStatus, - applLastChange, applInboundAssociations, - applOutboundAssociations, applAccumulatedInboundAssociations, - applAccumulatedOutboundAssociations, applLastInboundActivity, - applLastOutboundActivity, applRejectedInboundAssociations, - applFailedOutboundAssociations} - STATUS obsolete - DESCRIPTION - "A collection of objects providing basic monitoring of - network service applications. This is the original set - of such objects defined in RFC 1565." - ::= {applGroups 7} - -assocRFC1565Group OBJECT-GROUP - OBJECTS { - - assocRemoteApplication, assocApplicationProtocol, - assocApplicationType, assocDuration} - STATUS obsolete - DESCRIPTION - "A collection of objects providing basic monitoring of - network service applications' associations. This is the - original set of such objects defined in RFC 1565." - ::= {applGroups 2} - -applRFC2248Group OBJECT-GROUP - OBJECTS { - applName, applVersion, applUptime, applOperStatus, - applLastChange, applInboundAssociations, - applOutboundAssociations, applAccumulatedInboundAssociations, - applAccumulatedOutboundAssociations, applLastInboundActivity, - applLastOutboundActivity, applRejectedInboundAssociations, - applFailedOutboundAssociations, applDescription, applURL} - STATUS deprecated - DESCRIPTION - "A collection of objects providing basic monitoring of - network service applications. This group was originally - defined in RFC 2248; note that applDirectoryName is - missing." - ::= {applGroups 3} - -assocRFC2248Group OBJECT-GROUP - OBJECTS { - assocRemoteApplication, assocApplicationProtocol, - assocApplicationType, assocDuration} - STATUS deprecated - DESCRIPTION - "A collection of objects providing basic monitoring of - network service applications' associations. This group - was originally defined by RFC 2248." - ::= {applGroups 4} - -applRFC2788Group OBJECT-GROUP - OBJECTS { - applName, applDirectoryName, applVersion, applUptime, - applOperStatus, applLastChange, applInboundAssociations, - applOutboundAssociations, applAccumulatedInboundAssociations, - applAccumulatedOutboundAssociations, applLastInboundActivity, - applLastOutboundActivity, applRejectedInboundAssociations, - applFailedOutboundAssociations, applDescription, applURL} - STATUS current - DESCRIPTION - "A collection of objects providing basic monitoring of - network service applications. This is the appropriate - - group for RFC 2788 -- it adds the applDirectoryName object - missing in RFC 2248." - ::= {applGroups 5} - -assocRFC2788Group OBJECT-GROUP - OBJECTS { - assocRemoteApplication, assocApplicationProtocol, - assocApplicationType, assocDuration} - STATUS current - DESCRIPTION - "A collection of objects providing basic monitoring of - network service applications' associations. This is - the appropriate group for RFC 2788." - ::= {applGroups 6} - --- OIDs of the form {applTCPProtoID port} are intended to be used --- for TCP-based protocols that don't have OIDs assigned by other --- means. {applUDPProtoID port} serves the same purpose for --- UDP-based protocols. In either case 'port' corresponds to --- the primary port number being used by the protocol. For example, --- assuming no other OID is assigned for SMTP, an OID of --- {applTCPProtoID 25} could be used, since SMTP is a TCP-based --- protocol that uses port 25 as its primary port. - -applTCPProtoID OBJECT IDENTIFIER ::= {application 4} -applUDPProtoID OBJECT IDENTIFIER ::= {application 5} - -END diff --git a/mibs/SCTP-MIB b/mibs/SCTP-MIB deleted file mode 100644 index 9d809d282..000000000 --- a/mibs/SCTP-MIB +++ /dev/null @@ -1,1342 +0,0 @@ -SCTP-MIB DEFINITIONS ::= BEGIN - -IMPORTS - MODULE-IDENTITY, OBJECT-TYPE, Integer32, Unsigned32, Gauge32, - Counter32, Counter64, mib-2 - FROM SNMPv2-SMI -- [RFC2578] - TimeStamp, TruthValue - FROM SNMPv2-TC -- [RFC2579] - MODULE-COMPLIANCE, OBJECT-GROUP - FROM SNMPv2-CONF -- [RFC2580] - InetAddressType, InetAddress, InetPortNumber - FROM INET-ADDRESS-MIB; -- [RFC3291] - -sctpMIB MODULE-IDENTITY - LAST-UPDATED "200409020000Z" -- 2nd September 2004 - ORGANIZATION "IETF SIGTRAN Working Group" - CONTACT-INFO - " - WG EMail: sigtran@ietf.org - - Web Page: - http://www.ietf.org/html.charters/sigtran-charter.html - - Chair: Lyndon Ong - Ciena Corporation - 0480 Ridgeview Drive - Cupertino, CA 95014 - USA - Tel: - Email: lyong@ciena.com - - Editors: Maria-Carmen Belinchon - R&D Department - Ericsson Espana S. A. - Via de los Poblados, 13 - 28033 Madrid - Spain - Tel: +34 91 339 3535 - Email: Maria.C.Belinchon@ericsson.com - - Jose-Javier Pastor-Balbas - R&D Department - Ericsson Espana S. A. - Via de los Poblados, 13 - 28033 Madrid - Spain - Tel: +34 91 339 1397 - Email: J.Javier.Pastor@ericsson.com - " - DESCRIPTION - "The MIB module for managing SCTP implementations. - - Copyright (C) The Internet Society (2004). This version of - this MIB module is part of RFC 3873; see the RFC itself for - full legal notices. " - - REVISION "200409020000Z" -- 2nd September 2004 - DESCRIPTION " Initial version, published as RFC 3873" - ::= { mib-2 104 } - --- the SCTP base variables group - -sctpObjects OBJECT IDENTIFIER ::= { sctpMIB 1 } - -sctpStats OBJECT IDENTIFIER ::= { sctpObjects 1 } -sctpParams OBJECT IDENTIFIER ::= { sctpObjects 2 } - --- STATISTICS --- ********** - --- STATE-RELATED STATISTICS - -sctpCurrEstab OBJECT-TYPE - SYNTAX Gauge32 - MAX-ACCESS read-only - STATUS current - DESCRIPTION - "The number of associations for which the current state is - either ESTABLISHED, SHUTDOWN-RECEIVED or SHUTDOWN-PENDING." - REFERENCE - "Section 4 in RFC2960 covers the SCTP Association state - diagram." - ::= { sctpStats 1 } - -sctpActiveEstabs OBJECT-TYPE - SYNTAX Counter32 - MAX-ACCESS read-only - STATUS current - DESCRIPTION - "The number of times that associations have made a direct - transition to the ESTABLISHED state from the COOKIE-ECHOED - state: COOKIE-ECHOED -> ESTABLISHED. The upper layer initiated - the association attempt." - REFERENCE - "Section 4 in RFC2960 covers the SCTP Association state - diagram." - ::= { sctpStats 2 } - -sctpPassiveEstabs OBJECT-TYPE - SYNTAX Counter32 - MAX-ACCESS read-only - STATUS current - DESCRIPTION - "The number of times that associations have made a direct - transition to the ESTABLISHED state from the CLOSED state: - CLOSED -> ESTABLISHED. The remote endpoint initiated the - association attempt." - REFERENCE - "Section 4 in RFC2960 covers the SCTP Association state - diagram." - ::= { sctpStats 3 } - -sctpAborteds OBJECT-TYPE - SYNTAX Counter32 - MAX-ACCESS read-only - STATUS current - DESCRIPTION - "The number of times that associations have made a direct - transition to the CLOSED state from any state using the - primitive 'ABORT': AnyState --Abort--> CLOSED. Ungraceful - termination of the association." - REFERENCE - "Section 4 in RFC2960 covers the SCTP Association state - diagram." - ::= { sctpStats 4 } - -sctpShutdowns OBJECT-TYPE - SYNTAX Counter32 - MAX-ACCESS read-only - STATUS current - DESCRIPTION - "The number of times that associations have made a direct - transition to the CLOSED state from either the SHUTDOWN-SENT - state or the SHUTDOWN-ACK-SENT state. Graceful termination of - the association." - REFERENCE - "Section 4 in RFC2960 covers the SCTP Association state - diagram." - ::= { sctpStats 5 } - --- OTHER LAYER STATISTICS - -sctpOutOfBlues OBJECT-TYPE - SYNTAX Counter32 - MAX-ACCESS read-only - STATUS current - DESCRIPTION - "The number of out of the blue packets received by the host. - An out of the blue packet is an SCTP packet correctly formed, - including the proper checksum, but for which the receiver was - unable to identify an appropriate association." - REFERENCE - "Section 8.4 in RFC2960 deals with the Out-Of-The-Blue - (OOTB) packet definition and procedures." - ::= { sctpStats 6 } - -sctpChecksumErrors OBJECT-TYPE - SYNTAX Counter32 - MAX-ACCESS read-only - STATUS current - DESCRIPTION - "The number of SCTP packets received with an invalid - checksum." - REFERENCE - "The checksum is located at the end of the SCTP packet as per - Section 3.1 in RFC2960. RFC3309 updates SCTP to use a 32 bit - CRC checksum." -::= { sctpStats 7 } - -sctpOutCtrlChunks OBJECT-TYPE - SYNTAX Counter64 - MAX-ACCESS read-only - STATUS current - DESCRIPTION - "The number of SCTP control chunks sent (retransmissions are - not included). Control chunks are those chunks different from - DATA." - REFERENCE - "Sections 1.3.5 and 1.4 in RFC2960 refer to control chunk as - those chunks different from those that contain user - information, i.e., DATA chunks." - ::= { sctpStats 8 } - -sctpOutOrderChunks OBJECT-TYPE - SYNTAX Counter64 - MAX-ACCESS read-only - STATUS current - DESCRIPTION - "The number of SCTP ordered data chunks sent (retransmissions - are not included)." - REFERENCE - "Section 3.3.1 in RFC2960 defines the ordered data chunk." - ::= { sctpStats 9 } - -sctpOutUnorderChunks OBJECT-TYPE - SYNTAX Counter64 - MAX-ACCESS read-only - STATUS current - DESCRIPTION - "The number of SCTP unordered chunks (data chunks in which the - U bit is set to 1) sent (retransmissions are not included)." - REFERENCE - "Section 3.3.1 in RFC2960 defines the unordered data chunk." - ::= { sctpStats 10 } - -sctpInCtrlChunks OBJECT-TYPE - SYNTAX Counter64 - MAX-ACCESS read-only - STATUS current - DESCRIPTION - "The number of SCTP control chunks received (no duplicate - chunks included)." - REFERENCE - "Sections 1.3.5 and 1.4 in RFC2960 refer to control chunk as - those chunks different from those that contain user - information, i.e., DATA chunks." - ::= { sctpStats 11 } - -sctpInOrderChunks OBJECT-TYPE - SYNTAX Counter64 - MAX-ACCESS read-only - STATUS current - DESCRIPTION - "The number of SCTP ordered data chunks received (no duplicate - chunks included)." - REFERENCE - "Section 3.3.1 in RFC2960 defines the ordered data chunk." - ::= { sctpStats 12 } - -sctpInUnorderChunks OBJECT-TYPE - SYNTAX Counter64 - MAX-ACCESS read-only - STATUS current - DESCRIPTION - "The number of SCTP unordered chunks (data chunks in which the - U bit is set to 1) received (no duplicate chunks included)." - REFERENCE - "Section 3.3.1 in RFC2960 defines the unordered data chunk." - ::= { sctpStats 13 } - -sctpFragUsrMsgs OBJECT-TYPE - SYNTAX Counter64 - MAX-ACCESS read-only - STATUS current - DESCRIPTION - "The number of user messages that have to be fragmented - because of the MTU." - ::= { sctpStats 14 } - -sctpReasmUsrMsgs OBJECT-TYPE - SYNTAX Counter64 - MAX-ACCESS read-only - STATUS current - DESCRIPTION - "The number of user messages reassembled, after conversion - into DATA chunks." - REFERENCE - "Section 6.9 in RFC2960 includes a description of the - reassembly process." - ::= { sctpStats 15 } - -sctpOutSCTPPacks OBJECT-TYPE - SYNTAX Counter64 - MAX-ACCESS read-only - STATUS current - DESCRIPTION - "The number of SCTP packets sent. Retransmitted DATA chunks - are included." - ::= { sctpStats 16 } - -sctpInSCTPPacks OBJECT-TYPE - SYNTAX Counter64 - MAX-ACCESS read-only - STATUS current - DESCRIPTION - "The number of SCTP packets received. Duplicates are - included." - ::= { sctpStats 17 } - -sctpDiscontinuityTime OBJECT-TYPE - SYNTAX TimeStamp - MAX-ACCESS read-only - STATUS current - DESCRIPTION - "The value of sysUpTime on the most recent occasion at which - any one or more of this general statistics counters suffered a - discontinuity. The relevant counters are the specific - instances associated with this interface of any Counter32 or - Counter64 object contained in the SCTP layer statistics - (defined below sctpStats branch). If no such discontinuities - have occurred since the last re-initialization of the local - management subsystem, then this object contains a zero value." - REFERENCE - "The inclusion of this object is recommended by RFC2578." - ::= { sctpStats 18 } - --- PROTOCOL GENERAL VARIABLES --- ************************** - -sctpRtoAlgorithm OBJECT-TYPE - SYNTAX INTEGER { - other(1), -- Other new one. Future use - vanj(2) -- Van Jacobson's algorithm - } - MAX-ACCESS read-only - STATUS current - DESCRIPTION - "The algorithm used to determine the timeout value (T3-rtx) - used for re-transmitting unacknowledged chunks." - REFERENCE - "Section 6.3.1 and 6.3.2 in RFC2960 cover the RTO calculation - and retransmission timer rules." - DEFVAL {vanj} -- vanj(2) - ::= { sctpParams 1 } - -sctpRtoMin OBJECT-TYPE - SYNTAX Unsigned32 - UNITS "milliseconds" - MAX-ACCESS read-only - STATUS current - DESCRIPTION - "The minimum value permitted by a SCTP implementation for the - retransmission timeout value, measured in milliseconds. More - refined semantics for objects of this type depend upon the - algorithm used to determine the retransmission timeout value. - - A retransmission time value of zero means immediate - retransmission. - - The value of this object has to be lower than or equal to - stcpRtoMax's value." - DEFVAL {1000} -- milliseconds - ::= { sctpParams 2 } - -sctpRtoMax OBJECT-TYPE - SYNTAX Unsigned32 - UNITS "milliseconds" - MAX-ACCESS read-only - STATUS current - DESCRIPTION - "The maximum value permitted by a SCTP implementation for the - retransmission timeout value, measured in milliseconds. More - refined semantics for objects of this type depend upon the - algorithm used to determine the retransmission timeout value. - - A retransmission time value of zero means immediate re- - transmission. - - The value of this object has to be greater than or equal to - stcpRtoMin's value." - DEFVAL {60000} -- milliseconds - ::= { sctpParams 3 } - -sctpRtoInitial OBJECT-TYPE - SYNTAX Unsigned32 - UNITS "milliseconds" - MAX-ACCESS read-only - STATUS current - DESCRIPTION - "The initial value for the retransmission timer. - - A retransmission time value of zero means immediate re- - transmission." - DEFVAL {3000} -- milliseconds - ::= { sctpParams 4 } - -sctpMaxAssocs OBJECT-TYPE - SYNTAX Integer32 (-1 | 0..2147483647) - MAX-ACCESS read-only - STATUS current - DESCRIPTION - "The limit on the total number of associations the entity can - support. In entities where the maximum number of associations - is dynamic, this object should contain the value -1." - ::= { sctpParams 5 } - -sctpValCookieLife OBJECT-TYPE - SYNTAX Unsigned32 - UNITS "milliseconds" - MAX-ACCESS read-only - STATUS current - DESCRIPTION - "Valid cookie life in the 4-way start-up handshake procedure." - REFERENCE - "Section 5.1.3 in RFC2960 explains the cookie generation - process. Recommended value is per section 14 in RFC2960." - DEFVAL {60000} -- milliseconds - ::= { sctpParams 6 } - -sctpMaxInitRetr OBJECT-TYPE - SYNTAX Unsigned32 - MAX-ACCESS read-only - STATUS current - DESCRIPTION - "The maximum number of retransmissions at the start-up phase - (INIT and COOKIE ECHO chunks). " - REFERENCE - "Section 5.1.4, 5.1.6 in RFC2960 refers to Max.Init.Retransmit - parameter. Recommended value is per section 14 in RFC2960." - DEFVAL {8} -- number of attempts - ::= { sctpParams 7 } - --- TABLES --- ****** - --- the SCTP Association TABLE - --- The SCTP association table contains information about each --- association in which the local endpoint is involved. - -sctpAssocTable OBJECT-TYPE - SYNTAX SEQUENCE OF SctpAssocEntry - MAX-ACCESS not-accessible - STATUS current - DESCRIPTION - "A table containing SCTP association-specific information." - ::= { sctpObjects 3 } - -sctpAssocEntry OBJECT-TYPE - SYNTAX SctpAssocEntry - MAX-ACCESS not-accessible - STATUS current - DESCRIPTION - "General common variables and statistics for the whole - association." - INDEX { sctpAssocId } - ::= { sctpAssocTable 1 } - -SctpAssocEntry ::= SEQUENCE { - sctpAssocId Unsigned32, - sctpAssocRemHostName OCTET STRING, - sctpAssocLocalPort InetPortNumber, - sctpAssocRemPort InetPortNumber, - sctpAssocRemPrimAddrType InetAddressType, - sctpAssocRemPrimAddr InetAddress, - sctpAssocHeartBeatInterval Unsigned32, - sctpAssocState INTEGER, - sctpAssocInStreams Unsigned32, - sctpAssocOutStreams Unsigned32, - sctpAssocMaxRetr Unsigned32, - sctpAssocPrimProcess Unsigned32, - sctpAssocT1expireds Counter32, -- Statistic - sctpAssocT2expireds Counter32, -- Statistic - sctpAssocRtxChunks Counter32, -- Statistic - sctpAssocStartTime TimeStamp, - sctpAssocDiscontinuityTime TimeStamp - } - -sctpAssocId OBJECT-TYPE - SYNTAX Unsigned32 (1..4294967295) - MAX-ACCESS not-accessible - STATUS current - DESCRIPTION - "Association Identification. Value identifying the - association. " - ::= { sctpAssocEntry 1 } - -sctpAssocRemHostName OBJECT-TYPE - SYNTAX OCTET STRING (SIZE(0..255)) - MAX-ACCESS read-only - STATUS current - DESCRIPTION - "The peer's DNS name. This object needs to have the same - format as the encoding in the DNS protocol. This implies that - the domain name can be up to 255 octets long, each octet being - 0<=x<=255 as value with US-ASCII A-Z having a case insensitive - matching. - - If no DNS domain name was received from the peer at init time - (embedded in the INIT or INIT-ACK chunk), this object is - meaningless. In such cases the object MUST contain a zero- - length string value. Otherwise, it contains the remote host - name received at init time." - ::= { sctpAssocEntry 2 } - -sctpAssocLocalPort OBJECT-TYPE - SYNTAX InetPortNumber (1..65535) - MAX-ACCESS read-only - STATUS current - DESCRIPTION - "The local SCTP port number used for this association." - ::= { sctpAssocEntry 3 } - -sctpAssocRemPort OBJECT-TYPE - SYNTAX InetPortNumber (1..65535) - MAX-ACCESS read-only - STATUS current - DESCRIPTION - "The remote SCTP port number used for this association." - ::= { sctpAssocEntry 4 } - -sctpAssocRemPrimAddrType OBJECT-TYPE - SYNTAX InetAddressType - MAX-ACCESS read-only - STATUS current - DESCRIPTION - "The internet type of primary remote IP address. " - ::= { sctpAssocEntry 5 } - -sctpAssocRemPrimAddr OBJECT-TYPE - SYNTAX InetAddress - MAX-ACCESS read-only - STATUS current - DESCRIPTION - "The primary remote IP address. The type of this address is - determined by the value of sctpAssocRemPrimAddrType. - - The client side will know this value after INIT_ACK message - reception, the server side will know this value when sending - INIT_ACK message. However, values will be filled in at - established(4) state." - ::= { sctpAssocEntry 6 } - -sctpAssocHeartBeatInterval OBJECT-TYPE - SYNTAX Unsigned32 - UNITS "milliseconds" - MAX-ACCESS read-only - STATUS current - DESCRIPTION - "The current heartbeat interval.. - - Zero value means no HeartBeat, even when the concerned - sctpAssocRemAddrHBFlag object is true." - DEFVAL {30000} -- milliseconds - ::= { sctpAssocEntry 7 } - -sctpAssocState OBJECT-TYPE - SYNTAX INTEGER { - closed(1), - cookieWait(2), - cookieEchoed(3), - established(4), - shutdownPending(5), - shutdownSent(6), - shutdownReceived(7), - shutdownAckSent(8), - deleteTCB(9) - } - MAX-ACCESS read-write - STATUS current - DESCRIPTION - "The state of this SCTP association. - - As in TCP, deleteTCB(9) is the only value that may be set by a - management station. If any other value is received, then the - agent must return a wrongValue error. - - If a management station sets this object to the value - deleteTCB(9), then this has the effect of deleting the TCB (as - defined in SCTP) of the corresponding association on the - managed node, resulting in immediate termination of the - association. - - As an implementation-specific option, an ABORT chunk may be - sent from the managed node to the other SCTP endpoint as a - result of setting the deleteTCB(9) value. The ABORT chunk - implies an ungraceful association shutdown." - REFERENCE - "Section 4 in RFC2960 covers the SCTP Association state - diagram." - ::= { sctpAssocEntry 8 } - -sctpAssocInStreams OBJECT-TYPE - SYNTAX Unsigned32 (1..65535) - MAX-ACCESS read-only - STATUS current - DESCRIPTION - "Inbound Streams according to the negotiation at association - start up." - REFERENCE - "Section 1.3 in RFC2960 includes a definition of stream. - Section 5.1.1 in RFC2960 covers the streams negotiation - process." - ::= { sctpAssocEntry 9 } - -sctpAssocOutStreams OBJECT-TYPE - SYNTAX Unsigned32 (1..65535) - MAX-ACCESS read-only - STATUS current - DESCRIPTION - "Outbound Streams according to the negotiation at association - start up. " - REFERENCE - "Section 1.3 in RFC2960 includes a definition of stream. - Section 5.1.1 in RFC2960 covers the streams negotiation - process." - ::= { sctpAssocEntry 10 } - -sctpAssocMaxRetr OBJECT-TYPE - SYNTAX Unsigned32 - MAX-ACCESS read-only - STATUS current - DESCRIPTION - "The maximum number of data retransmissions in the association - context. This value is specific for each association and the - upper layer can change it by calling the appropriate - primitives. This value has to be smaller than the addition of - all the maximum number for all the paths - (sctpAssocRemAddrMaxPathRtx). - - A value of zero value means no retransmissions." - DEFVAL {10} -- number of attempts - ::= { sctpAssocEntry 11 } - -sctpAssocPrimProcess OBJECT-TYPE - SYNTAX Unsigned32 - MAX-ACCESS read-only - STATUS current - DESCRIPTION - "This object identifies the system level process which holds - primary responsibility for the SCTP association. - Wherever possible, this should be the system's native unique - identification number. The special value 0 can be used to - indicate that no primary process is known. - - Note that the value of this object can be used as a pointer - into the swRunTable of the HOST-RESOURCES-MIB(if the value is - smaller than 2147483647) or into the sysApplElmtRunTable of - the SYSAPPL-MIB." - ::= { sctpAssocEntry 12 } - --- Association Statistics - -sctpAssocT1expireds OBJECT-TYPE - SYNTAX Counter32 - MAX-ACCESS read-only - STATUS current - DESCRIPTION - "The T1 timer determines how long to wait for an - acknowledgement after sending an INIT or COOKIE-ECHO chunk. - This object reflects the number of times the T1 timer expires - without having received the acknowledgement. - - Discontinuities in the value of this counter can occur at re- - initialization of the management system, and at other times as - indicated by the value of sctpAssocDiscontinuityTime." - REFERENCE - "Section 5 in RFC2960." - ::= { sctpAssocEntry 13 } - -sctpAssocT2expireds OBJECT-TYPE - SYNTAX Counter32 - MAX-ACCESS read-only - STATUS current - DESCRIPTION - "The T2 timer determines how long to wait for an - acknowledgement after sending a SHUTDOWN or SHUTDOWN-ACK - chunk. This object reflects the number of times that T2- timer - expired. - - Discontinuities in the value of this counter can occur at re- - initialization of the management system, and at other times as - indicated by the value of sctpAssocDiscontinuityTime." -REFERENCE - "Section 9.2 in RFC2960." - ::= { sctpAssocEntry 14 } - -sctpAssocRtxChunks OBJECT-TYPE - SYNTAX Counter32 - MAX-ACCESS read-only - STATUS current - DESCRIPTION - "When T3-rtx expires, the DATA chunks that triggered the T3 - timer will be re-sent according with the retransmissions - rules. Every DATA chunk that was included in the SCTP packet - that triggered the T3-rtx timer must be added to the value of - this counter. - - Discontinuities in the value of this counter can occur at re- - initialization of the management system, and at other times as - indicated by the value of sctpAssocDiscontinuityTime." - REFERENCE - "Section 6 in RFC2960 covers the retransmission process and - rules." - ::= { sctpAssocEntry 15 } - -sctpAssocStartTime OBJECT-TYPE - SYNTAX TimeStamp - MAX-ACCESS read-only - STATUS current - DESCRIPTION - "The value of sysUpTime at the time that the association - represented by this row enters the ESTABLISHED state, i.e., - the sctpAssocState object is set to established(4). The - value of this object will be zero: - - before the association enters the established(4) - state, or - - - if the established(4) state was entered prior to - the last re-initialization of the local network management - subsystem." - ::= { sctpAssocEntry 16 } - -sctpAssocDiscontinuityTime OBJECT-TYPE - SYNTAX TimeStamp - MAX-ACCESS read-only - STATUS current - DESCRIPTION - "The value of sysUpTime on the most recent occasion at which - any one or more of this SCTP association counters suffered a - discontinuity. The relevant counters are the specific - instances associated with this interface of any Counter32 or - Counter64 object contained in the sctpAssocTable or - sctpLocalAddrTable or sctpRemAddrTable. If no such - discontinuities have occurred since the last re-initialization - of the local management subsystem, then this object contains a - zero value. " - REFERENCE - "The inclusion of this object is recommended by RFC2578." - ::= { sctpAssocEntry 17 } - --- Expanded tables: Including Multi-home feature - --- Local Address TABLE --- ******************* - -sctpAssocLocalAddrTable OBJECT-TYPE - SYNTAX SEQUENCE OF SctpAssocLocalAddrEntry - MAX-ACCESS not-accessible - STATUS current - DESCRIPTION - "Expanded table of sctpAssocTable based on the AssocId index. - This table shows data related to each local IP address which - is used by this association." - ::= { sctpObjects 4 } - -sctpAssocLocalAddrEntry OBJECT-TYPE - SYNTAX SctpAssocLocalAddrEntry - MAX-ACCESS not-accessible - STATUS current - DESCRIPTION - "Local information about the available addresses. There will - be an entry for every local IP address defined for this - - association. - Implementors need to be aware that if the size of - sctpAssocLocalAddr exceeds 114 octets then OIDs of column - instances in this table will have more than 128 sub- - identifiers and cannot be accessed using SNMPv1, SNMPv2c, or - SNMPv3." - INDEX { sctpAssocId, -- shared index - sctpAssocLocalAddrType, - sctpAssocLocalAddr } - ::= { sctpAssocLocalAddrTable 1 } - -SctpAssocLocalAddrEntry ::= SEQUENCE { - sctpAssocLocalAddrType InetAddressType, - sctpAssocLocalAddr InetAddress, - sctpAssocLocalAddrStartTime TimeStamp - } - -sctpAssocLocalAddrType OBJECT-TYPE - SYNTAX InetAddressType - MAX-ACCESS not-accessible - STATUS current - DESCRIPTION - "Internet type of local IP address used for this association." - ::= { sctpAssocLocalAddrEntry 1 } - -sctpAssocLocalAddr OBJECT-TYPE - SYNTAX InetAddress - MAX-ACCESS not-accessible - STATUS current - DESCRIPTION - "The value of a local IP address available for this - association. The type of this address is determined by the - value of sctpAssocLocalAddrType." - ::= { sctpAssocLocalAddrEntry 2 } - -sctpAssocLocalAddrStartTime OBJECT-TYPE - SYNTAX TimeStamp - MAX-ACCESS read-only - STATUS current - DESCRIPTION - "The value of sysUpTime at the time that this row was - created." - ::= { sctpAssocLocalAddrEntry 3 } - --- Remote Addresses TABLE --- ********************** - -sctpAssocRemAddrTable OBJECT-TYPE - SYNTAX SEQUENCE OF SctpAssocRemAddrEntry - MAX-ACCESS not-accessible - STATUS current - DESCRIPTION - "Expanded table of sctpAssocTable based on the AssocId index. - This table shows data related to each remote peer IP address - which is used by this association." - ::= { sctpObjects 5 } - -sctpAssocRemAddrEntry OBJECT-TYPE - SYNTAX SctpAssocRemAddrEntry - MAX-ACCESS not-accessible - STATUS current - DESCRIPTION - "Information about the most important variables for every - remote IP address. There will be an entry for every remote IP - address defined for this association. - - Implementors need to be aware that if the size of - sctpAssocRemAddr exceeds 114 octets then OIDs of column - instances in this table will have more than 128 sub- - identifiers and cannot be accessed using SNMPv1, SNMPv2c, or - SNMPv3." - INDEX { sctpAssocId, -- shared index - sctpAssocRemAddrType, - sctpAssocRemAddr } - ::= { sctpAssocRemAddrTable 1 } - -SctpAssocRemAddrEntry ::= SEQUENCE { - sctpAssocRemAddrType InetAddressType, - sctpAssocRemAddr InetAddress, - sctpAssocRemAddrActive TruthValue, - sctpAssocRemAddrHBActive TruthValue, - sctpAssocRemAddrRTO Unsigned32, - sctpAssocRemAddrMaxPathRtx Unsigned32, - sctpAssocRemAddrRtx Counter32, -- Statistic - sctpAssocRemAddrStartTime TimeStamp - } - -sctpAssocRemAddrType OBJECT-TYPE - SYNTAX InetAddressType - MAX-ACCESS not-accessible - STATUS current - DESCRIPTION - "Internet type of a remote IP address available for this - association." - ::= { sctpAssocRemAddrEntry 1 } - -sctpAssocRemAddr OBJECT-TYPE - SYNTAX InetAddress - MAX-ACCESS not-accessible - STATUS current - DESCRIPTION - "The value of a remote IP address available for this - association. The type of this address is determined by the - value of sctpAssocLocalAddrType." - ::= { sctpAssocRemAddrEntry 2 } - -sctpAssocRemAddrActive OBJECT-TYPE - SYNTAX TruthValue - MAX-ACCESS read-only - STATUS current - DESCRIPTION - "This object gives information about the reachability of this - specific remote IP address. - - When the object is set to 'true' (1), the remote IP address is - understood as Active. Active means that the threshold of no - answers received from this IP address has not been reached. - - When the object is set to 'false' (2), the remote IP address - is understood as Inactive. Inactive means that either no - heartbeat or any other message was received from this address, - reaching the threshold defined by the protocol." - REFERENCE - "The remote transport states are defined as Active and - Inactive in the SCTP, RFC2960." - ::= { sctpAssocRemAddrEntry 3 } - -sctpAssocRemAddrHBActive OBJECT-TYPE - SYNTAX TruthValue - MAX-ACCESS read-only - STATUS current - DESCRIPTION - "This object indicates whether the optional Heartbeat check - associated to one destination transport address is activated - or not (value equal to true or false, respectively). " - ::= { sctpAssocRemAddrEntry 4 } - -sctpAssocRemAddrRTO OBJECT-TYPE -- T3-rtx- Timer - SYNTAX Unsigned32 - UNITS "milliseconds" - MAX-ACCESS read-only - STATUS current - DESCRIPTION - "The current Retransmission Timeout. T3-rtx timer as defined - in the protocol SCTP." - REFERENCE - "Section 6.3 in RFC2960 deals with the Retransmission Timer - Management." - ::= { sctpAssocRemAddrEntry 5 } - -sctpAssocRemAddrMaxPathRtx OBJECT-TYPE - SYNTAX Unsigned32 - MAX-ACCESS read-only - STATUS current - DESCRIPTION - "Maximum number of DATA chunks retransmissions allowed to a - remote IP address before it is considered inactive, as defined - in RFC2960." - REFERENCE - "Section 8.2, 8.3 and 14 in RFC2960." - DEFVAL {5} -- number of attempts - ::= { sctpAssocRemAddrEntry 6 } - --- Remote Address Statistic - -sctpAssocRemAddrRtx OBJECT-TYPE - SYNTAX Counter32 - MAX-ACCESS read-only - STATUS current - DESCRIPTION - "Number of DATA chunks retransmissions to this specific IP - address. When T3-rtx expires, the DATA chunk that triggered - the T3 timer will be re-sent according to the retransmissions - rules. Every DATA chunk that is included in a SCTP packet and - was transmitted to this specific IP address before, will be - included in this counter. - - Discontinuities in the value of this counter can occur at re- - initialization of the management system, and at other times as - indicated by the value of sctpAssocDiscontinuityTime." - ::= { sctpAssocRemAddrEntry 7 } - -sctpAssocRemAddrStartTime OBJECT-TYPE - SYNTAX TimeStamp - MAX-ACCESS read-only - STATUS current - DESCRIPTION - "The value of sysUpTime at the time that this row was - created." - ::= { sctpAssocRemAddrEntry 8 } - --- ASSOCIATION INVERSE TABLE --- ************************* - --- BY LOCAL PORT - -sctpLookupLocalPortTable OBJECT-TYPE - SYNTAX SEQUENCE OF SctpLookupLocalPortEntry - MAX-ACCESS not-accessible - STATUS current - DESCRIPTION - "With the use of this table, a list of associations which are - - using the specified local port can be retrieved." - ::= { sctpObjects 6 } - -sctpLookupLocalPortEntry OBJECT-TYPE - SYNTAX SctpLookupLocalPortEntry - MAX-ACCESS not-accessible - STATUS current - DESCRIPTION - "This table is indexed by local port and association ID. - Specifying a local port, we would get a list of the - associations whose local port is the one specified." - INDEX { sctpAssocLocalPort, - sctpAssocId } - ::= { sctpLookupLocalPortTable 1 } - -SctpLookupLocalPortEntry::= SEQUENCE { - sctpLookupLocalPortStartTime TimeStamp - } - -sctpLookupLocalPortStartTime OBJECT-TYPE - SYNTAX TimeStamp - MAX-ACCESS read-only - STATUS current - DESCRIPTION - "The value of sysUpTime at the time that this row was created. - - As the table will be created after the sctpAssocTable - creation, this value could be equal to the sctpAssocStartTime - object from the main table." - ::= { sctpLookupLocalPortEntry 1 } - --- BY REMOTE PORT - -sctpLookupRemPortTable OBJECT-TYPE - SYNTAX SEQUENCE OF SctpLookupRemPortEntry - MAX-ACCESS not-accessible - STATUS current - DESCRIPTION - "With the use of this table, a list of associations which are - using the specified remote port can be got" - ::= { sctpObjects 7 } - -sctpLookupRemPortEntry OBJECT-TYPE - SYNTAX SctpLookupRemPortEntry - MAX-ACCESS not-accessible - STATUS current - DESCRIPTION - "This table is indexed by remote port and association ID. - Specifying a remote port we would get a list of the - associations whose local port is the one specified " - INDEX { sctpAssocRemPort, - sctpAssocId } - ::= { sctpLookupRemPortTable 1 } - -SctpLookupRemPortEntry::= SEQUENCE { - sctpLookupRemPortStartTime TimeStamp - } - -sctpLookupRemPortStartTime OBJECT-TYPE - SYNTAX TimeStamp - MAX-ACCESS read-only - STATUS current - DESCRIPTION - "The value of sysUpTime at the time that this row was created. - - As the table will be created after the sctpAssocTable - creation, this value could be equal to the sctpAssocStartTime - object from the main table." - ::= { sctpLookupRemPortEntry 1 } - --- BY REMOTE HOST NAME - -sctpLookupRemHostNameTable OBJECT-TYPE - SYNTAX SEQUENCE OF SctpLookupRemHostNameEntry - MAX-ACCESS not-accessible - STATUS current - DESCRIPTION - "With the use of this table, a list of associations with that - particular host can be retrieved." - ::= { sctpObjects 8 } - -sctpLookupRemHostNameEntry OBJECT-TYPE - SYNTAX SctpLookupRemHostNameEntry - MAX-ACCESS not-accessible - STATUS current - DESCRIPTION - "This table is indexed by remote host name and association ID. - Specifying a host name we would get a list of the associations - specifying that host name as the remote one. - - Implementors need to be aware that if the size of - sctpAssocRemHostName exceeds 115 octets then OIDs of column - instances in this table will have more than 128 sub- - identifiers and cannot be accessed using SNMPv1, SNMPv2c, or - SNMPv3." - INDEX { sctpAssocRemHostName, - sctpAssocId } - ::= { sctpLookupRemHostNameTable 1 } - -SctpLookupRemHostNameEntry::= SEQUENCE { - sctpLookupRemHostNameStartTime TimeStamp - } - -sctpLookupRemHostNameStartTime OBJECT-TYPE - SYNTAX TimeStamp - MAX-ACCESS read-only - STATUS current - DESCRIPTION - "The value of sysUpTime at the time that this row was created. - - As the table will be created after the sctpAssocTable - creation, this value could be equal to the sctpAssocStartTime - object from the main table." - ::= { sctpLookupRemHostNameEntry 1 } - --- BY REMOTE PRIMARY IP ADDRESS - -sctpLookupRemPrimIPAddrTable OBJECT-TYPE - SYNTAX SEQUENCE OF SctpLookupRemPrimIPAddrEntry - MAX-ACCESS not-accessible - STATUS current - DESCRIPTION - "With the use of this table, a list of associations that have - the specified IP address as primary within the remote set of - active addresses can be retrieved." - ::= { sctpObjects 9 } - -sctpLookupRemPrimIPAddrEntry OBJECT-TYPE - SYNTAX SctpLookupRemPrimIPAddrEntry - MAX-ACCESS not-accessible - STATUS current - DESCRIPTION - "This table is indexed by primary address and association ID. - Specifying a primary address, we would get a list of the - associations that have the specified remote IP address marked - as primary. - Implementors need to be aware that if the size of - sctpAssocRemPrimAddr exceeds 114 octets then OIDs of column - instances in this table will have more than 128 sub- - identifiers and cannot be accessed using SNMPv1, SNMPv2c, or - SNMPv3." - INDEX { sctpAssocRemPrimAddrType, - sctpAssocRemPrimAddr, - sctpAssocId } - ::= { sctpLookupRemPrimIPAddrTable 1 } - -SctpLookupRemPrimIPAddrEntry::= SEQUENCE { - sctpLookupRemPrimIPAddrStartTime TimeStamp - } - -sctpLookupRemPrimIPAddrStartTime OBJECT-TYPE - SYNTAX TimeStamp - MAX-ACCESS read-only - STATUS current - DESCRIPTION - "The value of SysUpTime at the time that this row was created. - - As the table will be created after the sctpAssocTable - creation, this value could be equal to the sctpAssocStartTime - object from the main table." - ::= { sctpLookupRemPrimIPAddrEntry 1 } - --- BY REMOTE IP ADDRESS - -sctpLookupRemIPAddrTable OBJECT-TYPE - SYNTAX SEQUENCE OF SctpLookupRemIPAddrEntry - MAX-ACCESS not-accessible - STATUS current - DESCRIPTION - "With the use of this table, a list of associations that have - the specified IP address as one of the remote ones can be - retrieved. " - ::= { sctpObjects 10 } - -sctpLookupRemIPAddrEntry OBJECT-TYPE - SYNTAX SctpLookupRemIPAddrEntry - MAX-ACCESS not-accessible - STATUS current - DESCRIPTION - "This table is indexed by a remote IP address and association - ID. Specifying an IP address we would get a list of the - associations that have the specified IP address included - within the set of remote IP addresses." - INDEX { sctpAssocRemAddrType, - sctpAssocRemAddr, - sctpAssocId } - ::= { sctpLookupRemIPAddrTable 1 } - -SctpLookupRemIPAddrEntry::= SEQUENCE { - - sctpLookupRemIPAddrStartTime TimeStamp - } - -sctpLookupRemIPAddrStartTime OBJECT-TYPE - SYNTAX TimeStamp - MAX-ACCESS read-only - STATUS current - DESCRIPTION - "The value of SysUpTime at the time that this row was created. - - As the table will be created after the sctpAssocTable - creation, this value could be equal to the sctpAssocStartTime - object from the main table." - ::= { sctpLookupRemIPAddrEntry 1 } - --- 4.1 Conformance Information - -sctpMibConformance OBJECT IDENTIFIER ::= { sctpMIB 2 } -sctpMibCompliances OBJECT IDENTIFIER ::= { sctpMibConformance 1 } -sctpMibGroups OBJECT IDENTIFIER ::= { sctpMibConformance 2 } - --- 4.1.1 Units of conformance - --- --- MODULE GROUPS --- - -sctpLayerParamsGroup OBJECT-GROUP - OBJECTS { sctpRtoAlgorithm, - sctpRtoMin, - sctpRtoMax, - sctpRtoInitial, - sctpMaxAssocs, - sctpValCookieLife, - sctpMaxInitRetr - } - STATUS current - DESCRIPTION - "Common parameters for the SCTP layer, i.e., for all the - associations. They can usually be referred to as configuration - parameters." - ::= { sctpMibGroups 1 } - -sctpStatsGroup OBJECT-GROUP - OBJECTS { sctpCurrEstab, - sctpActiveEstabs, - sctpPassiveEstabs, - sctpAborteds, - sctpShutdowns, - sctpOutOfBlues, - sctpChecksumErrors, - sctpOutCtrlChunks, - sctpOutOrderChunks, - sctpOutUnorderChunks, - sctpInCtrlChunks, - sctpInOrderChunks, - sctpInUnorderChunks, - sctpFragUsrMsgs, - sctpReasmUsrMsgs, - sctpOutSCTPPacks, - sctpInSCTPPacks, - sctpDiscontinuityTime, - sctpAssocT1expireds, - sctpAssocT2expireds, - sctpAssocRtxChunks, - sctpAssocRemAddrRtx - } - STATUS current - DESCRIPTION - "Statistics group. It includes the objects to collect state - changes in the SCTP protocol local layer and flow control - statistics." - ::= { sctpMibGroups 2 } - -sctpPerAssocParamsGroup OBJECT-GROUP - OBJECTS { sctpAssocRemHostName, - sctpAssocLocalPort, - sctpAssocRemPort, - sctpAssocRemPrimAddrType, - sctpAssocRemPrimAddr, - sctpAssocHeartBeatInterval, - sctpAssocState, - sctpAssocInStreams, - sctpAssocOutStreams, - sctpAssocMaxRetr, - sctpAssocPrimProcess, - sctpAssocStartTime, - sctpAssocDiscontinuityTime, - sctpAssocLocalAddrStartTime, - sctpAssocRemAddrActive, - sctpAssocRemAddrHBActive, - sctpAssocRemAddrRTO, - sctpAssocRemAddrMaxPathRtx, - sctpAssocRemAddrStartTime - } - STATUS current - DESCRIPTION - "The SCTP group of objects to manage per-association - parameters. These variables include all the SCTP basic - features." - ::= { sctpMibGroups 3 } - -sctpPerAssocStatsGroup OBJECT-GROUP - OBJECTS - { sctpAssocT1expireds, - sctpAssocT2expireds, - sctpAssocRtxChunks, - sctpAssocRemAddrRtx - } - STATUS current - DESCRIPTION - "Per Association Statistics group. It includes the objects to - collect flow control statistics per association." - ::= { sctpMibGroups 4 } - -sctpInverseGroup OBJECT-GROUP - OBJECTS { sctpLookupLocalPortStartTime, - sctpLookupRemPortStartTime, - sctpLookupRemHostNameStartTime, - sctpLookupRemPrimIPAddrStartTime, - sctpLookupRemIPAddrStartTime - } - STATUS current - DESCRIPTION - "Objects used in the inverse lookup tables." - ::= { sctpMibGroups 5 } - --- 4.1.2 Compliance Statements - --- --- MODULE COMPLIANCES --- - -sctpMibCompliance MODULE-COMPLIANCE - STATUS current - DESCRIPTION - "The compliance statement for SNMP entities which implement - this SCTP MIB Module. - - There are a number of INDEX objects that cannot be represented - in the form of OBJECT clauses in SMIv2, but for which we have - the following compliance requirements, expressed in OBJECT - clause form in this description clause: - --- OBJECT sctpAssocLocalAddrType --- SYNTAX InetAddressType {ipv4(1), ipv6(2)} --- DESCRIPTION --- It is only required to have IPv4 and IPv6 addresses without --- zone indices. --- The address with zone indices is required if an --- implementation can connect multiple zones. --- --- OBJECT sctpAssocLocalAddr --- SYNTAX InetAddress (SIZE(4|16)) --- DESCRIPTION --- An implementation is only required to support globally --- unique IPv4 and IPv6 addresses. --- --- OBJECT sctpAssocRemAddrType --- SYNTAX InetAddressType {ipv4(1), ipv6(2)} --- DESCRIPTION --- It is only required to have IPv4 and IPv6 addresses without --- zone indices. --- The address with zone indices is required if an --- implementation can connect multiple zones. --- --- OBJECT sctpAssocRemAddr --- SYNTAX InetAddress (SIZE(4|16)) --- DESCRIPTION --- An implementation is only required to support globally --- unique IPv4 and IPv6 addresses. --- - " -- closes DESCRIPTION clause of MODULE-COMPLIANCE - - MODULE -- this module - - MANDATORY-GROUPS { sctpLayerParamsGroup, - sctpPerAssocParamsGroup, - sctpStatsGroup, - sctpPerAssocStatsGroup - } - - OBJECT sctpAssocRemPrimAddrType - SYNTAX InetAddressType { ipv4(1), - ipv6(2) - } - DESCRIPTION - "It is only required to have IPv4 and IPv6 addresses - without zone indices. - - The address with zone indices is required if an - implementation can connect multiple zones." - - OBJECT sctpAssocRemPrimAddr - SYNTAX InetAddress (SIZE(4|16)) - DESCRIPTION - "An implementation is only required to support globally - unique IPv4 and globally unique IPv6 addresses." - - OBJECT sctpAssocState - WRITE-SYNTAX INTEGER { deleteTCB(9) } - MIN-ACCESS read-only - DESCRIPTION - "Only the deleteTCB(9) value MAY be set by a management - station at most. A read-only option is also considered to - be compliant with this MIB module description." - - GROUP sctpInverseGroup - DESCRIPTION - "Objects used in inverse lookup tables. This should be - implemented, at the discretion of the implementers, for - easier lookups in the association tables" - ::= { sctpMibCompliances 1 } - -END