OID reference

netflowMIB

1.3.6.1.4.1.52642.9.226

Description

The Netflow MIB provides a simple and easy method to get NetFlow cache information, current NetFlow configuration and statistics. It will enable medium to small size enterprises to take advantage of NetFlow technology over SNMP at a reduced infrastructure cost. The MIB is created to provide Netflow information in thes…

Full description and source information

Identification

Identifier and names

Parent
1.3.6.1.4.1.52642.9 (nmsMgmt, vtssSwitchMgmt, fsSurveillanceMIB)
Node code
226
Node name
netflowMIB
Numeric OID
1.3.6.1.4.1.52642.9.226
URN notation
urn:oid:1.3.6.1.4.1.52642.9.226
ASN.1, OID-IRI and named path variants
ASN.1 notation

{1 3 6 1 4 1 52642 9 226}

  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) fs(52642) nmsMgmt(9) netflowMIB(226)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) fs(52642) vtssSwitchMgmt(9) netflowMIB(226)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) fs(52642) fsSurveillanceMIB(9) netflowMIB(226)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) nms(52642) nmsMgmt(9) netflowMIB(226)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) nms(52642) vtssSwitchMgmt(9) netflowMIB(226)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) nms(52642) fsSurveillanceMIB(9) netflowMIB(226)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) fiberstore(52642) nmsMgmt(9) netflowMIB(226)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) fiberstore(52642) vtssSwitchMgmt(9) netflowMIB(226)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) fiberstore(52642) fsSurveillanceMIB(9) netflowMIB(226)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) vtss(52642) nmsMgmt(9) netflowMIB(226)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) vtss(52642) vtssSwitchMgmt(9) netflowMIB(226)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) vtss(52642) fsSurveillanceMIB(9) netflowMIB(226)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) userNet(52642) nmsMgmt(9) netflowMIB(226)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) userNet(52642) vtssSwitchMgmt(9) netflowMIB(226)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) userNet(52642) fsSurveillanceMIB(9) netflowMIB(226)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) fs(52642) nmsMgmt(9) netflowMIB(226)}
  • Additional combinations skipped.
OID-IRI notation
  • /1/3/6/1/4/1/52642/9/226
  • /ISO/Identified-Organization/6/1/4/1/52642/9/226
  • /ISO/3/6/1/4/1/52642/9/226
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/fs/nmsMgmt/netflowMIB
  • /iso/identified-organization/dod/internet/private/enterprise/fs/vtssSwitchMgmt/netflowMIB
  • /iso/identified-organization/dod/internet/private/enterprise/fs/fsSurveillanceMIB/netflowMIB
  • /iso/identified-organization/dod/internet/private/enterprise/nms/nmsMgmt/netflowMIB
  • /iso/identified-organization/dod/internet/private/enterprise/nms/vtssSwitchMgmt/netflowMIB
  • /iso/identified-organization/dod/internet/private/enterprise/nms/fsSurveillanceMIB/netflowMIB
  • /iso/identified-organization/dod/internet/private/enterprise/fiberstore/nmsMgmt/netflowMIB
  • /iso/identified-organization/dod/internet/private/enterprise/fiberstore/vtssSwitchMgmt/netflowMIB
  • /iso/identified-organization/dod/internet/private/enterprise/fiberstore/fsSurveillanceMIB/netflowMIB
  • /iso/identified-organization/dod/internet/private/enterprise/FS/nmsMgmt/netflowMIB
  • /iso/identified-organization/dod/internet/private/enterprise/FS/vtssSwitchMgmt/netflowMIB
  • /iso/identified-organization/dod/internet/private/enterprise/FS/fsSurveillanceMIB/netflowMIB
  • /iso/identified-organization/dod/internet/private/enterprise/vtss/nmsMgmt/netflowMIB
  • /iso/identified-organization/dod/internet/private/enterprise/vtss/vtssSwitchMgmt/netflowMIB
  • /iso/identified-organization/dod/internet/private/enterprise/vtss/fsSurveillanceMIB/netflowMIB
  • /iso/identified-organization/dod/internet/private/enterprise/S3200/nmsMgmt/netflowMIB
  • Additional combinations skipped.

Product context

Documented MIB packages

The FS.COM catalogue lists MIB packages containing this definition for these models:

IES3100-16TM, IES3100-8T4F-P, IES3100-8TF, IES3100-8TF-P, S3150-8T2FP, S3400-24T4FP, S3400-24T4SP, S3400-48T4SP, S3400-48T6SP, S5500-48T6SP-R.

A definition in a model's MIB package does not establish that the device implements it or permits access.

The displayed source records contain one distinct definition. Compare its source records.

netflowMIB MODULE-IDENTITY
        LAST-UPDATED    "201203190000Z"
        ORGANIZATION    "BDCOM Systems, Inc."
        CONTACT-INFO
                "        BDCOM Systems
                         Customer Service
                "
        DESCRIPTION
                "The Netflow MIB provides a simple and easy method
                 to get NetFlow cache information, current NetFlow
                 configuration and statistics. It will enable medium to
                 small size enterprises to take advantage of NetFlow
                 technology over SNMP at a reduced infrastructure cost.
                 The MIB is created to provide Netflow information in
                 these areas:

                        1. Cache information and configuration.
                        2. Collector information and configuration.
                        3. Export Statistics.
                        4. Version 9 Export Template information.

                 Terminology used

                 Flow
                 A flow is defined as a unidirectional sequence of 
				 packets with some common properties that pass 
				 through a network device.  These collected flows 
				 are exported to an external device, the NetFlow
				 collector.  Network flows are highly granular;
                 for example, flow records include details such 
				 as IP addresses, packet and byte counts,timestamps, 
				 Type of Service (ToS), application ports, 
				 input and output interfaces, etc.

                 Exporter
                 A device (for example, a router) with NetFlow
                 services enabled. The exporter monitors packets
                 entering an observation point and creates flows out
                 of these packets. The information from these flows
                 are exported in the form of Flow Records to
                 the collector.

                 Flow Record
                 A Flow Record provides information about an IP Flow
                 that exists on the Exporter. The Flow Records are
                 commonly referred to as NetFlow Services data or
                 NetFlow data.

                 Collector
                 The NetFlow Collector receives Flow Records from
                 one or more Exporters. It processes the received
                 export packet, i.e. parses, stores, display the 
				 Flow Record information. The flow records may be optionally
                 aggregated before being stored into the hard disk.
                                      
                 Template
                 NetFlow Version 9 Export format is template based.
                 Version 9 record format consists of a packet header
                 followed by at least one or more template or data
                 FlowSets. A template FlowSet (collection of one or more
                 template) provides a description of the fields that
                 will be present in future data FlowSets. Templates
                 provide an extensible design to the record format,
                 a feature that should allow future enhancements to
                 NetFlow services without requiring concurrent changes
                 to the basic flow-record format.

                 One additional record type is also a part of
                 Version 9 specification: an options template. Rather
                 than supplying information about IP flows, options are
                 used to supply information about the NetFlow process
                 configuration or NetFlow process specific data."

        REVISION "201203190000Z"
        DESCRIPTION
                 "Initial version of this MIB module."

        ::= { nmsMgmt 226 }

Meaning

Descriptions

1 unique

Identical descriptions are grouped. Different wording and device-specific notes are retained.

The Netflow MIB provides a simple and easy method to get NetFlow cache information, current NetFlow configuration and statistics. It will enable medium to small size enterprises to take advantage of NetFlow technology over SNMP at a reduced infrastructure cost. The MIB is created to provide Netflow information in these areas: 1. Cache information and configuration. 2. Collector information and configuration. 3. Export Statistics. 4. Version 9 Export Template information. Terminology used Flow A flow is defined as a unidirectional sequence of packets with some common properties that pass through a network device. These collected flows are exported to an external device, the NetFlow collector. Network flows are highly granular; for example, flow records include details such as IP addresses, packet and byte counts,timestamps, Type of Service (ToS), application ports, input and output interfaces, etc. Exporter A device (for example, a router) with NetFlow services enabled. The exporter monitors packets entering an observation point and creates flows out of these packets. The information from these flows are exported in the form of Flow Records to the collector. Flow Record A Flow Record provides information about an IP Flow that exists on the Exporter. The Flow Records are commonly referred to as NetFlow Services data or NetFlow data. Collector The NetFlow Collector receives Flow Records from one or more Exporters. It processes the received export packet, i.e. parses, stores, display the Flow Record information. The flow records may be optionally aggregated before being stored into the hard disk. Template NetFlow Version 9 Export format is template based. Version 9 record format consists of a packet header followed by at least one or more template or data FlowSets. A template FlowSet (collection of one or more template) provides a description of the fields that will be present in future data FlowSets. Templates provide an extensible design to the record format, a feature that should allow future enhancements to NetFlow services without requiring concurrent changes to the basic flow-record format. One additional record type is also a part of Version 9 specification: an options template. Rather than supplying information about IP flows, options are used to supply information about the NetFlow process configuration or NetFlow process specific data.

Sources for this description

FS.COM official Documentation Hub native MIB packages

See 1 matching source record

Evidence

Source records

1 records

Matching descriptions are grouped; open a group to compare definitions and supporting files.

Records for description 1FS.COM official Documentation Hub native MIB packages1 record · 1 source

Description 1

netflowMIB · unspecifiedFS.COM official Documentation Hub native MIB packages1 source

Status in source: unspecified.

Names: netflowMIB

Technical details
{
  "smi_kind": "MODULE-IDENTITY",
  "definition": [
    "netflowMIB",
    "MODULE-IDENTITY",
    "LAST-UPDATED",
    [
      "literal",
      "223230313230333139303030305a22"
    ],
    "ORGANIZATION",
    "\"BDCOM Systems, Inc.\"",
    "CONTACT-INFO",
    "\" BDCOM Systems Customer Service \"",
    "DESCRIPTION",
    "\"The Netflow MIB provides a simple and easy method to get NetFlow cache information, current NetFlow configuration and statistics. It will enable medium to small size enterprises to take advantage of NetFlow technology over SNMP at a reduced infrastructure cost. The MIB is created to provide Netflow information in these areas: 1. Cache information and configuration. 2. Collector information and configuration. 3. Export Statistics. 4. Version 9 Export Template information. Terminology used Flow A flow is defined as a unidirectional sequence of packets with some common properties that pass through a network device. These collected flows are exported to an external device, the NetFlow collector. Network flows are highly granular; for example, flow records include details such as IP addresses, packet and byte counts,timestamps, Type of Service (ToS), application ports, input and output interfaces, etc. Exporter A device (for example, a router) with NetFlow services enabled. The exporter monitors packets entering an observation point and creates flows out of these packets. The information from these flows are exported in the form of Flow Records to the collector. Flow Record A Flow Record provides information about an IP Flow that exists on the Exporter. The Flow Records are commonly referred to as NetFlow Services data or NetFlow data. Collector The NetFlow Collector receives Flow Records from one or more Exporters. It processes the received export packet, i.e. parses, stores, display the Flow Record information. The flow records may be optionally aggregated before being stored into the hard disk. Template NetFlow Version 9 Export format is template based. Version 9 record format consists of a packet header followed by at least one or more template or data FlowSets. A template FlowSet (collection of one or more template) provides a description of the fields that will be present in future data FlowSets. Templates provide an extensible design to the record format, a feature that should allow future enhancements to NetFlow services without requiring concurrent changes to the basic flow-record format. One additional record type is also a part of Version 9 specification: an options template. Rather than supplying information about IP flows, options are used to supply information about the NetFlow process configuration or NetFlow process specific data.\"",
    "REVISION",
    [
      "literal",
      "223230313230333139303030305a22"
    ],
    "DESCRIPTION",
    "\"Initial version of this MIB module.\"",
    "::=",
    "{",
    "nmsMgmt",
    "226",
    "}"
  ],
  "syntax_tree": [
    [
      "LAST-UPDATED",
      "201203190000Z"
    ],
    [
      "ORGANIZATION",
      "BDCOM Systems, Inc."
    ],
    [
      "CONTACT-INFO",
      "BDCOM Systems Customer Service"
    ],
    [
      "DESCRIPTION",
      "The Netflow MIB provides a simple and easy method to get NetFlow cache information, current NetFlow configuration and statistics. It will enable medium to small size enterprises to take advantage of NetFlow technology over SNMP at a reduced infrastructure cost. The MIB is created to provide Netflow information in these areas: 1. Cache information and configuration. 2. Collector information and configuration. 3. Export Statistics. 4. Version 9 Export Template information. Terminology used Flow A flow is defined as a unidirectional sequence of packets with some common properties that pass through a network device. These collected flows are exported to an external device, the NetFlow collector. Network flows are highly granular; for example, flow records include details such as IP addresses, packet and byte counts,timestamps, Type of Service (ToS), application ports, input and output interfaces, etc. Exporter A device (for example, a router) with NetFlow services enabled. The exporter monitors packets entering an observation point and creates flows out of these packets. The information from these flows are exported in the form of Flow Records to the collector. Flow Record A Flow Record provides information about an IP Flow that exists on the Exporter. The Flow Records are commonly referred to as NetFlow Services data or NetFlow data. Collector The NetFlow Collector receives Flow Records from one or more Exporters. It processes the received export packet, i.e. parses, stores, display the Flow Record information. The flow records may be optionally aggregated before being stored into the hard disk. Template NetFlow Version 9 Export format is template based. Version 9 record format consists of a packet header followed by at least one or more template or data FlowSets. A template FlowSet (collection of one or more template) provides a description of the fields that will be present in future data FlowSets. Templates provide an extensible design to the record format, a feature that should allow future enhancements to NetFlow services without requiring concurrent changes to the basic flow-record format. One additional record type is also a part of Version 9 specification: an options template. Rather than supplying information about IP flows, options are used to supply information about the NetFlow process configuration or NetFlow process specific data."
    ],
    [
      "Revisions",
      [
        [
          "201203190000Z",
          [
            "DESCRIPTION",
            "Initial version of this MIB module."
          ]
        ]
      ]
    ]
  ]
}

Registration

Registration authorities

Current Registration Authority (inferred from ancestor 1.3.6.1.4.1.52642)

FS.COM INC

Direct children (1)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.52642.9.226.1 netflowMIBObjects444

Siblings (95)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.52642.9.85 vtssVlanTranslationMib229
1.3.6.1.4.1.52642.9.89 vtssGvrpMib219
1.3.6.1.4.1.52642.9.91 vtssLoopProtectionMib229
1.3.6.1.4.1.52642.9.97 vtssDaylightSavingMib226
1.3.6.1.4.1.52642.9.100 nmsNatMIB, vtssPortPowerSavingsMib262
1.3.6.1.4.1.52642.9.101 nmsGbscHostMIB, vtssIcfgMib247
1.3.6.1.4.1.52642.9.102 nmsIpslaMIB, vtssIpMib2396
1.3.6.1.4.1.52642.9.105 vtssSntpMib215
1.3.6.1.4.1.52642.9.109 nmsProcessMIB, vtssDhcpServerMib3188
1.3.6.1.4.1.52642.9.110 vtssRfc2544Mib2132
1.3.6.1.4.1.52642.9.117 vtssPerfMonitorMib2170
1.3.6.1.4.1.52642.9.121 vtssDdmiMib248
1.3.6.1.4.1.52642.9.123 vtssUdldMib230
1.3.6.1.4.1.52642.9.125 vtssHqosMib247
1.3.6.1.4.1.52642.9.126 vtssDhcp6ClientMib260
1.3.6.1.4.1.52642.9.127 vtssMplsMib2465
1.3.6.1.4.1.52642.9.128 vtssTtLoopMib241
1.3.6.1.4.1.52642.9.129 vtssJsonRpcNotificationMib234
1.3.6.1.4.1.52642.9.175 nms1705MIB122
1.3.6.1.4.1.52642.9.181 cardSys523
1.3.6.1.4.1.52642.9.182 nmsvlanExt1162
1.3.6.1.4.1.52642.9.183 opticalPortPower831
1.3.6.1.4.1.52642.9.184 cardOper722
1.3.6.1.4.1.52642.9.185 nmsFileMgmtMIB121
1.3.6.1.4.1.52642.9.186 nmsIfQosPolicy16
1.3.6.1.4.1.52642.9.187 fanTrap537
1.3.6.1.4.1.52642.9.188 nmsAuthenticationTrap67
1.3.6.1.4.1.52642.9.189 power515
1.3.6.1.4.1.52642.9.193 nmsSerial329
1.3.6.1.4.1.52642.9.194 nmsrqos4166
1.3.6.1.4.1.52642.9.218 nmsIfThresholdMIB359
1.3.6.1.4.1.52642.9.225 snmp880
1.3.6.1.4.1.52642.9.231 nmsSntp15
1.3.6.1.4.1.52642.9.251 powerExt411
1.3.6.1.4.1.52642.9.252 nmsLoopbackDetectMIB211
1.3.6.1.4.1.52642.9.253 stp713
1.3.6.1.4.1.52642.9.254 nmsBackupLinkMIB, nmsTftp, NMSBackupLinkMIB328
1.3.6.1.4.1.52642.9.350 routing22
1.3.6.1.4.1.52642.9.351 nmsAccounting311
1.3.6.1.4.1.52642.9.352 wlan29
1.3.6.1.4.1.52642.9.353 ntp33
1.3.6.1.4.1.52642.9.354 nmsSysNotifications77
1.3.6.1.4.1.52642.9.355 dhcp29
1.3.6.1.4.1.52642.9.356 wan19
1.3.6.1.4.1.52642.9.357 nmsL2ProtocolTunnelMIB15