⭐ 欢迎来到虫虫下载站! | 📦 资源下载 📁 资源专辑 ℹ️ 关于我们
⭐ 虫虫下载站

📄 rfc2720.mib

📁 wm PNE 3.3 source code, running at more than vxworks6.x version.
💻 MIB
📖 第 1 页 / 共 5 页
字号:
FLOW-METER-MIB DEFINITIONS ::= BEGINIMPORTS    MODULE-IDENTITY, OBJECT-TYPE,    Counter32, Counter64, Integer32, mib-2        FROM SNMPv2-SMI    TEXTUAL-CONVENTION, RowStatus, TimeStamp, TruthValue        FROM SNMPv2-TC    OBJECT-GROUP, MODULE-COMPLIANCE        FROM SNMPv2-CONF    ifIndex        FROM IF-MIB    TimeFilter        FROM RMON2-MIB;flowMIB MODULE-IDENTITY    LAST-UPDATED "9910250000Z" -- October 25, 1999    ORGANIZATION "IETF Realtime Traffic Flow Measurement Working Group"    CONTACT-INFO        "Nevil Brownlee, The University of Auckland        Postal: Information Technology Sytems & Services                The University of Auckland                Private Bag 92-019                Auckland, New Zealand        Phone:  +64 9 373 7599 x8941        E-mail: n.brownlee@auckland.ac.nz"    DESCRIPTION        "MIB for the RTFM Traffic Flow Meter."    REVISION "9910250000Z"    DESCRIPTION        "Initial Version, published as RFC 2720."     REVISION "9908301250Z"     DESCRIPTION         "UTF8OwnerString Textual Convention added, and used to         replace OwnerString.  Conceptually the same as OwnerString,         but facilitating internationalisation by using UTF-8         encoding for its characters rather than US-ASCII."    REVISION "9908191010Z"    DESCRIPTION        "Changes to SIZE specification for two variables:          - flowRuleInfoName SIZE specified as (0..127)          - flowRuleIndex SIZE increased to (1..2147483647)"    REVISION "9712230937Z"    DESCRIPTION        "Two further variables deprecated:          - flowRuleInfoRulesReady (use flowRuleInfoStatus intead)          - flowDataStatus (contains no useful information)"    REVISION "9707071715Z"    DESCRIPTION        "Significant changes since RFC 2064 include:          - flowDataPackageTable added          - flowColumnActivityTable deprecated          - flowManagerCounterWrap deprecated"    REVISION "9603080208Z"    DESCRIPTION        "Initial version of this MIB (RFC 2064)"    ::= { mib-2 40 }flowControl         OBJECT IDENTIFIER ::= { flowMIB 1 }flowData            OBJECT IDENTIFIER ::= { flowMIB 2 }flowRules           OBJECT IDENTIFIER ::= { flowMIB 3 }flowMIBConformance  OBJECT IDENTIFIER ::= { flowMIB 4 }-- Textual ConventionsUTF8OwnerString ::= TEXTUAL-CONVENTION    DISPLAY-HINT "127t"    STATUS  current    DESCRIPTION        "An administratively assigned name for the owner of a        resource, conceptually the same as OwnerString in the RMON        MIB [RMON-MIB].        To facilitate internationalisation, this name information        is represented using the ISO/IEC IS 10646-1 character set,        encoded as an octet string using the UTF-8 transformation        format described in the UTF-8 standard [UTF-8]."    SYNTAX  OCTET STRING (SIZE (0..127))PeerType ::= TEXTUAL-CONVENTION    STATUS  current    DESCRIPTION        "Indicates the type of a PeerAddress (see below).  The values        used are from the 'Address Family Numbers' section of the        Assigned Numbers RFC [ASG-NBR].  Peer types from other address        families may also be used, provided only that they are        identified by their assigned Address Family numbers."    SYNTAX  INTEGER {        ipv4(1),        ipv6(2),        nsap(3),        ipx(11),        appletalk(12),        decnet(13) }PeerAddress ::= TEXTUAL-CONVENTION    STATUS  current    DESCRIPTION        "Specifies the value of a peer address for various network        protocols.  Address format depends on the actual protocol,        as indicated below:        IPv4:        ipv4(1)            4-octet IpAddress  (defined in the SNMPv2 SMI [RFC2578])        IPv6:        ipv6(2)            16-octet IpAddress  (defined in the                                    IPv6 Addressing RFC [V6-ADDR])        CLNS:        nsap(3)            NsapAddress  (defined in the SNMPv2 SMI [RFC2578])        Novell:      ipx(11)            4-octet Network number,            6-octet Host number (MAC address)        AppleTalk:   appletalk(12)            2-octet Network number (sixteen bits),            1-octet Host number (eight bits)        DECnet:      decnet(13)            1-octet Area number (in low-order six bits),            2-octet Host number (in low-order ten bits)        "    SYNTAX OCTET STRING (SIZE (3..20))AdjacentType ::= TEXTUAL-CONVENTION    STATUS  current    DESCRIPTION        "Indicates the type of an adjacent address.  May be a medium        type or (if metering is taking place inside a tunnel) a        PeerType (see above).        The values used for IEEE 802 medium types are from the 'Network        Management Parameters (ifType definitions)' section of the        Assigned Numbers RFC [ASG-NBR].  Other medium types may also        be used, provided only that they are identified by their        assigned ifType numbers."    SYNTAX  INTEGER {        ip(1),        nsap(3),        ethernet(7),  -- ethernet-like [ENET-OBJ],                      --    includes ethernet-csmacd(6)        tokenring(9),        ipx(11),        appletalk(12),        decnet(13),        fddi(15) }AdjacentAddress ::= TEXTUAL-CONVENTION    STATUS  current    DESCRIPTION        "Specifies the value of an adjacent address.  May be a Medium        Access Control (MAC) address or (if metering is taking place        inside a tunnel) a PeerAddress (see above).        MAC Address format depends on the actual medium, as follows:        Ethernet:     ethernet(7)            6-octet 802.3 MAC address in 'canonical' order        Token Ring:   tokenring(9)            6-octet 802.5 MAC address in 'canonical' order        FDDI:         fddi(15)            FddiMACLongAddress, i.e. a 6-octet MAC address            in 'canonical' order  (defined in [FDDI-MIB])        "    SYNTAX OCTET STRING (SIZE (3..20))TransportType ::= TEXTUAL-CONVENTION    STATUS  current    DESCRIPTION        "Indicates the type of a TransportAddress (see below).  Values        will depend on the actual protocol; for IP they will be those        given in the 'Protocol Numbers' section of the  Assigned Numbers        RFC [ASG-NBR], including icmp(1), tcp(6) and udp(17)."    SYNTAX  Integer32 (1..255)TransportAddress ::= TEXTUAL-CONVENTION    STATUS  current    DESCRIPTION        "Specifies the value of a transport address for various        network protocols.  Format as follows:        IP:            2-octet UDP or TCP port number        Other protocols:            2-octet port number        "    SYNTAX OCTET STRING (SIZE (2))RuleAddress ::= TEXTUAL-CONVENTION    STATUS  current    DESCRIPTION        "Specifies the value of an address.  Is a superset of        MediumAddress, PeerAddress and TransportAddress."    SYNTAX OCTET STRING (SIZE (2..20))FlowAttributeNumber ::= TEXTUAL-CONVENTION    STATUS  current    DESCRIPTION        "Uniquely identifies an attribute within a flow data record."    SYNTAX  INTEGER {        flowIndex(1),        flowStatus(2),        flowTimeMark(3),        sourceInterface(4),        sourceAdjacentType(5),        sourceAdjacentAddress(6),        sourceAdjacentMask(7),        sourcePeerType(8),        sourcePeerAddress(9),        sourcePeerMask(10),        sourceTransType(11),        sourceTransAddress(12),        sourceTransMask(13),        destInterface(14),        destAdjacentType(15),        destAdjacentAddress(16),        destAdjacentMask(17),        destPeerType(18),        destPeerAddress(19),        destPeerMask(20),        destTransType(21),        destTransAddress(22),        destTransMask(23),        pduScale(24),        octetScale(25),        ruleSet(26),        toOctets(27),             -- Source-to-Dest        toPDUs(28),        fromOctets(29),           -- Dest-to-Source        fromPDUs(30),        firstTime(31),            -- Activity times        lastActiveTime(32),        sourceSubscriberID(33),   -- Subscriber ID        destSubscriberID(34),        sessionID(35),        sourceClass(36),          -- Computed attributes        destClass(37),        flowClass(38),        sourceKind(39),        destKind(40),        flowKind(41) }RuleAttributeNumber ::= TEXTUAL-CONVENTION    STATUS  current    DESCRIPTION        "Uniquely identifies an attribute which may be tested in        a rule.  These include attributes whose values come directly        from (or are computed from) the flow's packets, and the five        'meter' variables used to hold an Attribute Number."    SYNTAX  INTEGER {        null(0),        sourceInterface(4),       -- Source Address        sourceAdjacentType(5),        sourceAdjacentAddress(6),        sourcePeerType(8),        sourcePeerAddress(9),        sourceTransType(11),        sourceTransAddress(12),        destInterface(14),        -- Dest Address        destAdjacentType(15),        destAdjacentAddress(16),        destPeerType(18),        destPeerAddress(19),        destTransType(21),        destTransAddress(22),        sourceSubscriberID(33),   -- Subscriber ID        destSubscriberID(34),        sessionID(35),        sourceClass(36),          -- Computed attributes        destClass(37),        flowClass(38),        sourceKind(39),        destKind(40),        flowKind(41),        matchingStoD(50),         -- Packet matching        v1(51),                   -- Meter variables        v2(52),        v3(53),        v4(54),        v5(55) }ActionNumber ::= TEXTUAL-CONVENTION    STATUS  current    DESCRIPTION        "Uniquely identifies the action of a rule, i.e. the Pattern        Matching Engine's opcode number.  Details of the opcodes        are given in the 'Traffic Flow Measurement: Architecture'        document [RTFM-ARC]."    SYNTAX  INTEGER {        ignore(1),        noMatch(2),        count(3),        countPkt(4),        return(5),        gosub(6),        gosubAct(7),        assign(8),        assignAct(9),        goto(10),        gotoAct(11),        pushRuleTo(12),        pushRuleToAct(13),        pushPktTo(14),        pushPktToAct(15),        popTo(16),        popToAct(17) }---- Control Group:  RuleSet Info Table--flowRuleSetInfoTable OBJECT-TYPE    SYNTAX  SEQUENCE OF FlowRuleSetInfoEntry    MAX-ACCESS  not-accessible    STATUS  current    DESCRIPTION        "An array of information about the RuleSets held in the        meter.        Any manager may configure a new RuleSet for the meter by        creating a row in this table with status active(1), and setting        values for all the objects in its rules.  At this stage the new        RuleSet is available but not 'running', i.e. it is not being        used by the meter to produce entries in the flow table.        To actually 'run' a RuleSet a manager must create a row in        the flowManagerInfoTable, set it's flowManagerStatus to        active(1), and set either its CurrentRuleSet or StandbyRuleSet        to point to the RuleSet to be run.        Once a RuleSet is running a manager may not change any of the        objects within the RuleSet itself.  Any attempt to do so should        result in a notWritable(17) SNMP error-status for such objects.        A manager may stop a RuleSet running by removing all        references to it in the flowManagerInfoTable (i.e. by setting        CurrentRuleSet and StandbyRuleSet values to 0).  This provides        a way to stop RuleSets left running if a manager fails.        For example, when a manager is started, it could search the        meter's flowManager table and stop all RuleSets having a        specified value of flowRuleInfoOwner.        To prevent a manager from interfering with variables belonging        to another manager, the meter should use MIB views [RFC2575] so        as to limit each manager's access to the meter's variables,        effectively dividing the single meter into several virtual        meters, one for each independent manager."    ::= { flowControl 1 }flowRuleSetInfoEntry OBJECT-TYPE

⌨️ 快捷键说明

复制代码 Ctrl + C
搜索代码 Ctrl + F
全屏模式 F11
切换主题 Ctrl + Shift + D
显示快捷键 ?
增大字号 Ctrl + =
减小字号 Ctrl + -