AD | Application | AWS | Azure | Cloud | Database | Enterprise | Environmental | Event Log | File System | Infra | IoT | IT Service | Linux | Network/System | Performance | Protocol | SaaS | Security | Service Level | SNMP | Storage | VMware | VoIP | Web | Wireless

Crumbtrail

MonitorTools.com » Technical documentation » SNMP » MIB » Xircom » XIRCOM-MIB

XIRCOM-MIB device MIB details by Xircom

XIRCOM-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 XIRCOM-MIB.


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

	XIRCOM-MIB

	DEFINITIONS ::= BEGIN


	IMPORTS 
		enterprises
			FROM RFC1155-SMI
		OBJECT-TYPE
			FROM RFC-1212
		TRAP-TYPE
			FROM RFC-1215;

	-- Xircom private enterprises MIB extensions
	xircom         OBJECT IDENTIFIER ::= { enterprises 588 }

	-- examples MIB
	printers        OBJECT IDENTIFIER ::= { xircom 1 }

	-- define a couple of objects
	printerStatus   OBJECT-TYPE
		SYNTAX  INTEGER
		ACCESS  read-only
		STATUS  mandatory
		DESCRIPTION     "Bitfield with the following bit
				 positions defined
					bit 0 - other error
					bit 1 - paper out
					bit 2 - io error
					bit 3 - offline"

		::= { printers 1 }

	acceptPrintJobs   OBJECT-TYPE
		SYNTAX  INTEGER
		ACCESS  read-write
		STATUS  mandatory
		DESCRIPTION     "Set to one if the system is accepting
				 new print jobs "
		::= { printers 2 }


	queuedJobs   OBJECT-TYPE
		SYNTAX  INTEGER
		ACCESS  read-only
		STATUS  mandatory
		DESCRIPTION     "the number of queued print jobs "
		::= { printers 3 }

	sendTrap   OBJECT-TYPE
		SYNTAX  INTEGER
		ACCESS  read-write
		STATUS  mandatory
		DESCRIPTION     "Bitfield with the following bit
				 positions defined
					bit 0 - other error
					bit 1 - paper out
					bit 2 - io error
					bit 3 - offline

				 If the bit is set, a trap is sent when the
				 status of that bit position in printerStatus
				 changes"

		::= { printers 4 }

	printerTrap  TRAP-TYPE
		ENTERPRISE      printers
		VARIABLES       { printerStatus }
		DESCRIPTION     "The printer status changed"
		::= 0

	END