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 » Wellfleet » Wellfleet-TNC-MIB

Wellfleet-TNC-MIB device MIB details by Wellfleet

Wellfleet-TNC-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 Wellfleet-TNC-MIB.


Vendor: Wellfleet
Mib: Wellfleet-TNC-MIB  [download]  [view objects]
Tool: ActiveXperts Network Monitor 2024 [download]    (ships with advanced SNMP/MIB tools)
Wellfleet-TNC-MIB DEFINITIONS ::= BEGIN

-- Created by mdl2asn version 3.1
-- Creation date: Wed Aug 30 16:49:36 EDT 1995


    IMPORTS

      Counter, Gauge
        FROM RFC1155-SMI
      OBJECT-TYPE
        FROM RFC-1212
      DisplayString
        FROM RFC1213-MIB
      wfTelnetGroup
        FROM Wellfleet-COMMON-MIB;


    wfTelnetClient	OBJECT IDENTIFIER ::= { wfTelnetGroup 2 }

    wfTelnetClientDelete OBJECT-TYPE
        SYNTAX	INTEGER {
    		    created(1),
    		    deleted(2)
    		}
        ACCESS	read-write
        STATUS	mandatory
        DESCRIPTION
                "Create or Delete the Object Base Record"
        DEFVAL	{ created }
        ::= { wfTelnetClient 1 }

    wfTelnetClientDisable OBJECT-TYPE
        SYNTAX	INTEGER {
    		    enabled(1),
    		    disabled(2)
    		}
        ACCESS	read-write
        STATUS	mandatory
        DESCRIPTION
                "Enable or Disable Telnet Client"
        DEFVAL	{ enabled }
        ::= { wfTelnetClient 2 }

    wfTelnetClientDebug OBJECT-TYPE
        SYNTAX	INTEGER {
    		    on(1),
    		    off(2)
    		}
        ACCESS	read-write
        STATUS	mandatory
        DESCRIPTION
                "The Initial Value of the Debug Toggle"
        DEFVAL	{ off }
        ::= { wfTelnetClient 3 }

    wfTelnetClientRemotePort OBJECT-TYPE
        SYNTAX	INTEGER
        ACCESS	read-write
        STATUS	mandatory
        DESCRIPTION
                "The Default Remote Telnet Server TCP Port"
        DEFVAL	{ 23 }
        ::= { wfTelnetClient 4 }

    wfTelnetClientPrompt OBJECT-TYPE
        SYNTAX	DisplayString
        ACCESS	read-write
        STATUS	mandatory
        DESCRIPTION
                "The Default Telnet Client Command Prompt"
        ::= { wfTelnetClient 5 }

    wfTelnetClientActiveSessions OBJECT-TYPE
        SYNTAX	Gauge
        ACCESS	read-only
        STATUS	mandatory
        DESCRIPTION
                "The number of active outbound telnet sessions"
        ::= { wfTelnetClient 6 }

    wfTelnetClientTotalSessions OBJECT-TYPE
        SYNTAX	Counter
        ACCESS	read-only
        STATUS	mandatory
        DESCRIPTION
                "Total number of outbound telnet sessions"
        ::= { wfTelnetClient 7 }

    END  -- Wellfleet-TNC-MIB