All MIBs › WOLLONGONG-MIB
Category: Legacy and Miscellaneous
Description: Defines Wollongong Group enterprise network management objects for TCP/IP stack and connectivity monitoring.
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 WOLLONGONG-MIB?
WOLLONGONG-MIB is a legacy enterprise MIB from The Wollongong Group, an early TCP/IP stack vendor, covering their networking software (referenced here as VMS4, suggesting a DEC VMS TCP/IP implementation) and associated LAN bridge functionality. It exposes a LAN bridge table tracking bridge entries and neighbor relationships, along with counters for inbound/outbound frames, bad frames, and collisions on bridged interfaces, plus bridge uptime. Its monitoring value lies in early network hardware/link health visibility: twgLBUpTime shows how long the bridge component has been running, while the frame and collision counters (twgLBInFrames1/2, twgLBOutFrames1/2, twgLBBadFrames1/2, twgLBCollisions) reveal link-layer error rates and traffic levels that indicate a degrading or overloaded bridge connection. As an older enterprise MIB it predates and parallels some functionality later standardized in the IETF Bridge MIB (RFC 1493) and MIB-II interface counters. It would have been deployed on Wollongong TCP/IP stack hosts (e.g., VMS systems) acting as LAN bridges in legacy enterprise networks. Engineers can download the WOLLONGONG-MIB file directly to load it into their MIB browser.
IPNetwork Monitor allows you to monitor SNMP objects defined in WOLLONGONG-MIB. 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
- Wollongong Group TCP/IP stack host (e.g., VMS system)
- legacy LAN bridge device
Monitoring Examples
An operator would poll lANbridgeTab/lANbridgeEnt to inspect twgLBNeigh1 and twgLBNeigh2 for the bridge's neighboring segment identifiers, then compare twgLBInFrames1/twgLBInFrames2 against twgLBBadFrames1/twgLBBadFrames2 to compute an error rate for each side of the bridge. A rising twgLBCollisions count alongside falling throughput would indicate a saturated or faulty LAN segment. twgLBUpTime would be checked to confirm the bridge process has not silently restarted.
What Can Be Monitored
- bridge uptime
- neighbor segment identifiers
- inbound/outbound frame counts
- bad frame counts
- collision counts
Imported Objects
From RFC1065-SMI
| Counter | |
| TimeTicks | |
| enterprises |
From SNMPv2-SMI
| OBJECT-TYPE |
OIDs
RFC description
Defines management objects for Wollongong TCP/IP stack across various platforms including DOS, VMS, and UNIX.
Start monitoring Wollongong Group TCP/IP stack host, legacy LAN bridge device (bridge uptime/frame-error/collision 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.