ActiveXperts Network Monitor 2019##AdminFavorites

RFC1298-MIB by vendor Novell

RFC1298-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 2019 to import vendor-specific MIB files, inclusing RFC1298-MIB.

Vendor: Novell
Mib: RFC1298-MIB  [download]  [view objects]
Tool: ActiveXperts Network Monitor 2019 [download]    (ships with advanced SNMP/MIB tools)
-- WinAgents MIB Extraction Wizard
-- Extracted from rfc1298.txt 16.03.2005 20:20:15


     enterprises         FROM RFC1155-SMI;

     novell              OBJECT IDENTIFIER ::= { enterprises 23 }
     transportDomains    OBJECT IDENTIFIER ::= { novell 7 }

     ipxTransportDomain  OBJECT IDENTIFIER ::= { transportDomains 1 }

   -- Authoritatively names the IPX Transport Domain

   IpxTransportAddress ::= OCTET STRING (SIZE (12))

   -- A textual convention denoting a transport service address in
   -- the ipxTransportDomain.  An IpxTransportAddress is 12 octets
   -- long and comprises 3 fields, each in network-byte (high-low)
   -- order.

   -- The first field is 4 octets long and contains the network
   -- number.

   -- The next field is 6 octets long and contains the physical
   -- address of the node.  Since IPX can run over a variety of
   -- subnet architectures, the physical node address may not
   -- require all 6 octets.  As specified in [2], the physical
   -- node address will occupy the least significant portion of
   -- the field and the most significant octets should be set
   -- to zero.

   -- The last field is 2 octets long and contains the socket
   -- number.