You are here: > Administration > MIB > Novell > RFC1298-MIB

ActiveXperts Network Monitor supports SNMP based checks.It ships with free SNMP GET and SNMP TRAP utilities. It also offers many SNMP scripts (PowerShell and VBScript).

Use ActiveXperts Netork Monitor to monitor your virtualization servers, domains, computers and devices. It runs on a single Windows server, without agents required on the monitored systems. It has many built-in checks and also allows administrators to create custom checks using PowerShell, VBScript and SSH.

RFC1298-MIB provided by Novell

RFC1298-MIB file content

Most network devices and programs ship with so-called MIB files to describe the parameters and meanings (i.e.: friendly names) which are available for monitoring via SNMP.
ActiveXperts Network Monitor can import vendor-specific MIB files, so it can be used to monitor specific OID's (Object Identifiers). This way, you can monitor your devices, computers, etc. by selecting your relevant OID's by name.

Vendor: Novell
Mib: RFC1298-MIB  [download]  [view objects]
Tool: ActiveXperts Network Monitor [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.