ITOUCHHUB

MIB Reference — IPNetwork Monitor · Updated October 06, 2026

All MIBs › ITOUCHHUB

Description: ITOUCHHUB module

Start monitoring vendor-neutral, standards-based MIB, any SNMPv3-capable network device (SNMP engine identity/boot/clock status) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

What Is ITOUCHHUB?

ITOUCHHUB is a legacy iTouch Communications, Inc. enterprise MIB (enterprises.33) built on RFC1155-SMI/RFC-1212/TRAP-TYPE constructs, indicating an SNMPv1-era design; despite its 'hub' name, the module actually defines a broad product-identification scheme spanning iTouch's whole legacy device catalog rather than hub-specific management tables. Under the agent OID branch it registers terminal servers, bridges, repeaters (a common physical form for Ethernet hubs), bridge/routers, bridge/router/repeaters, switches, and OEM/NBase devices, each further subdivided by hardware variant (MAXserver, Network 9000, InReach, NetVantage, and dozens of named io-card and chassis types enumerated in the HardwareType, ChassisType, and IOType textual conventions). Companion conventions DateTime, TypedAddress, and SoftwareType provide common encodings for timestamps, typed network addresses, and the functional role (terminal server, bridge, repeater, router, switch) of a given agent. Because it is primarily an OID/identification registry rather than a live-counter MIB, its main monitoring value is confirming exactly which iTouch hardware and software variant a polled agent identifies as, which then determines which companion MIB modules apply. It is deployed on legacy iTouch Communications terminal server, hub/repeater, bridge, router, and switch products, and the ITOUCHHUB MIB is the reference for decoding those product identifiers.

IPNetwork Monitor allows you to monitor SNMP objects defined in ITOUCHHUB. Use the built-in SNMP Monitoring Browser to explore available variables, view their current values and descriptions, and select the objects you want to monitor. You can then create SNMP monitors, configure thresholds, and receive alerts when monitored values change.

Supported Devices

  • Legacy iTouch Communications terminal server, hub/repeater, bridge, router, and switch products

Monitoring Examples

An operator reads the sysObjectID of a legacy iTouch device and cross-references it against the HardwareType/ChassisType enumerations in this MIB to determine exactly which repeater or terminal-server model is deployed; an unrecognized or mismatched hardware-type value would indicate stale inventory records or an unsupported device variant.

What Can Be Monitored

  • device hardware type identification
  • device software/functional type (bridge, repeater, router, switch)
  • chassis and I/O card type identification
  • agent OID product variant registration
Imported Objects

From RFC-1215

TRAP-TYPE

From RFC1155-SMI

Counter
Gauge
IpAddress
NetworkAddress
OBJECT-TYPE
TimeTicks
enterprises
mgmt

From SNMPv2-TC

TEXTUAL-CONVENTION

How to Use in IPNetwork Monitor

Example using ifInOctets OID:

Select an iTouch Communications hub/terminal-server product as the target host to create a monitor — the SNMP service should be up and running on it. Click New Monitor, then check SNMP Custom on the Favorites tab, click Next, and confirm the host. On the next page, click Select... to open the built-in SNMP MIB Browser and type ifInOctets into the Find box to locate it in the OID tree, selecting the specific row/instance you want to monitor since this is a table column, then select it and click OK. The total number of octets received on the interface, including framing characters. On the monitor's Main parameters page you can set the target's SNMP port (default 161), credentials, polling interval, and other settings — see the SNMP Monitor help for details. On the State conditions and Alerting tabs, configure when the monitor should change state and trigger an alert; since this is a Counter32-type OID, Value bounds is the most useful condition here — trigger an alert if the counter increases sharply between polls relative to its normal baseline, since an unexpected spike often reflects a real change in traffic or activity. Click Finish to create the monitor; you can adjust any parameter later.
OIDs

RFC description

Legacy MIB for iTouch hub network device management using SNMPv1 protocol.

Start monitoring iTouch Communications hub/terminal-server products with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

Download ITOUCHHUB