Intel-Common-MIB device MIB details by Intel Corporation

Intel-Common-MIB file content

The SNMP protocol is used to for conveying information and commands between agents and managing entities. SNMP uses the User Datagram Protocol (UDP) as the transport protocol for passing data between managers and agents. The reasons for using UDP for SNMP are, firstly it has low overheads in comparison to TCP, which uses a 3-way hand shake for connection. Secondly, in congested networks, SNMP over TCP is a bad idea because TCP in order to maintain reliability will flood the network with retransmissions.

Management information (MIB) is represented as a collection of managed objects. These objects together form a virtual information base called MIB. An agent may implement many MIBs, but all agents must implement a particular MIB called MIB-II [16]. This standard defines variables for things such as interface statistics (interface speeds, MTU, octets sent, octets received, etc.) as well as various other things pertaining to the system itself (system location, system contact, etc.). The main goal of MIB-II is to provide general TCP/IP management information.

Use ActiveXperts Network Monitor 2024 to import vendor-specific MIB files, inclusing Intel-Common-MIB.

Vendor:	Intel Corporation
Mib:	Intel-Common-MIB  [download]
Tool:	ActiveXperts Network Monitor 2024 [download]    (ships with advanced SNMP/MIB tools)

Intel-Common-MIB DEFINITIONS ::= BEGIN

IMPORTS
    enterprises FROM RFC1155-SMI;

-- Categories

intel               OBJECT IDENTIFIER ::=   { enterprises 343 }

-- 
-- Intel Private space divides into 3 branches at the top. They are
-- identifiers, products, and experimental.  
-- 
-- 'identifiers' branch typically contains objects which are used as
-- constants.  For example, if a mib contained an object identifier
-- "appliance-type", somewhere down under identifiers would be a list
-- containing OIDs for "refrigerator", "toaster", etc.  Currently
-- there are 3 groups under identifiers; systems, objects and
-- comm-methods.
-- 'systems' contains objects for system type such as PCs, hubs, etc.
-- 'objects' contains identifiers for component pieces.  
-- 'comm-methods' refers to the transmission medium used in 
-- proxy-to-agent conversation.
-- 
-- 'products' branch contains objects which are specifically Intel
-- products.  Under this branch go all MIBs for Intel products.
-- 
-- 'experimental' is for exactly what the name implies.
--  
-- 'information-technology' encompasses the work of the Information 
-- Technology (IT) group within Intel. 
--  
-- For example, an identifier for a toaster would exist under
-- 'identifiers.systems.toasters' while another identifier for an
-- Intel specific toaster MIB would live under 'products.appliances'.
-- 

identifiers         OBJECT IDENTIFIER ::=   { intel 1 }
products            OBJECT IDENTIFIER ::=   { intel 2 }
experimental        OBJECT IDENTIFIER ::=   { intel 3 }
information-technology  OBJECT IDENTIFIER ::=   { intel 4 }

-- Groups under 'identifiers'

systems             OBJECT IDENTIFIER ::=   { identifiers 1 }
objects             OBJECT IDENTIFIER ::=   { identifiers 2 }
comm-methods        OBJECT IDENTIFIER ::=   { identifiers 3 }

pc-systems          OBJECT IDENTIFIER ::=   { systems 1 }
proxy-systems       OBJECT IDENTIFIER ::=   { systems 2 }
hub-systems         OBJECT IDENTIFIER ::=   { systems 3 }

local-proxy-1       OBJECT IDENTIFIER ::=   { comm-methods 1 }
pc-novell-1         OBJECT IDENTIFIER ::=   { comm-methods 2 }

-- Identifiers for 'hub-systems'
-- Note: These items match the definitions for moduleType
--       in intelhub.mib.

express10-100Stack  OBJECT IDENTIFIER ::=   { hub-systems 1 }
express12TX         OBJECT IDENTIFIER ::=   { hub-systems 2 }
express24TX         OBJECT IDENTIFIER ::=   { hub-systems 3 }
expressReserved     OBJECT IDENTIFIER ::=   { hub-systems 4 }
expressMgmt         OBJECT IDENTIFIER ::=   { hub-systems 5 }
expressBridge       OBJECT IDENTIFIER ::=   { hub-systems 6 }
express210-12       OBJECT IDENTIFIER ::=   { hub-systems 7 }
express210-24       OBJECT IDENTIFIER ::=   { hub-systems 8 }
express220-12       OBJECT IDENTIFIER ::=   { hub-systems 9 }
express220-24       OBJECT IDENTIFIER ::=   { hub-systems 10 }

-- Groups under 'products'

pc-products         OBJECT IDENTIFIER ::=   { products 1 }
hub-products        OBJECT IDENTIFIER ::=   { products 2 }
proxy               OBJECT IDENTIFIER ::=   { products 3 }
print-products      OBJECT IDENTIFIER ::=   { products 4 }
network-products    OBJECT IDENTIFIER ::=   { products 5 }
snmp-agents         OBJECT IDENTIFIER ::=   { products 6 }
nic-products        OBJECT IDENTIFIER ::=   { products 7 }

-- Groups under 'hub-products'

express110          OBJECT IDENTIFIER ::=   { hub-products 1 }

-- Groups under 'print-products'

netport-1           OBJECT IDENTIFIER ::=   { print-products 1 }
netport-2           OBJECT IDENTIFIER ::=   { print-products 2 }
netport-express     OBJECT IDENTIFIER ::=   { print-products 3 }

-- Groups under 'network-products'

lanDesk             OBJECT IDENTIFIER ::=   { network-products 1 }
ld-alarms           OBJECT IDENTIFIER ::=   { lanDesk 1 }
internetServer-2    OBJECT IDENTIFIER ::=   { network-products 2 }
iS-alarms           OBJECT IDENTIFIER ::=   { internetServer-2 1 }

-- Groups under 'experimental'

-- <none>

--

END