LIGO-W-JET-MIMO-MIB

All MIBs › LIGO-W-JET-MIMO-MIB

Organization: LigoWave

Last Updated: 2010-03-22

Category: Technology: Wireless, Vendor: LigoWave, Wireless and WLAN

Description: LigoWave MIB providing MIMO-specific radio statistics and configuration objects for W-Jet MIMO point-to-point wireless links.

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 LIGO-W-JET-MIMO-MIB?

LIGO-W-JET-MIMO-MIB is a LigoWave vendor MIB providing MIMO-specific radio statistics and configuration for the W-Jet MIMO point-to-point wireless link product. It exposes a per-peer statistics table tracking token-based transmission counters (transmit, receive, duplicate, lost, dropped tokens) and transmit failure/reinjection counts used in the W-Jet protocol's link-quality accounting, plus a notifications group for link events. This MIB is heavily oriented toward monitoring wireless link hardware/software health, since lost, dropped, and duplicate token counts directly indicate radio link quality degradation, interference, or failure conditions on the MIMO link. No explicit dependency on other standard MIBs is evident from the available data, though the notifications group likely follows standard SNMPv2 trap conventions. It is typically deployed by wireless ISPs monitoring outdoor point-to-point MIMO radio links for interference and link-quality issues. Engineers can download the LIGO-W-JET-MIMO-MIB file directly to load it into their MIB browser.

IPNetwork Monitor allows you to monitor SNMP objects defined in LIGO-W-JET-MIMO-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

LigoWave W-Jet MIMO wireless bridge

Monitoring Examples

An administrator would poll wJetMimoStatsTable (via wJetMimoStatsEntry, indexed by wJetMimoPeerIndex) to compare wJetMimoTxTokens against wJetMimoRxTokens, and check wJetMimoLostTokens and wJetMimoDroppedTokens, revealing a degraded or interference-affected MIMO link if lost/dropped counts climb. wJetMimoTxFailures and wJetMimoReinjectedTokens would be watched to detect a peer connection that is repeatedly failing and retrying, while wJetMimoMacAddress identifies which remote peer the statistics belong to.

What Can Be Monitored

transmit/receive token counts
lost token count
dropped token count
duplicate token count
transmit failure count
reinjected token count

Imported Objects

From IF-MIB

ifIndex

OBJECT-TYPE

From LIGOWAVE-MIB

ligoMgmt

OBJECT-IDENTITY

From SNMPv2-SMI

Counter32
Integer32
MODULE-IDENTITY
OBJECT-TYPE

From SNMPv2-TC

MacAddress

How to Use in IPNetwork Monitor

Example using wJetMimoTxTokens OID:

Select a LigoWave W-Jet MIMO wireless bridge 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 wJetMimoTxTokens 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. It reports the number of transmitted tokens. 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

OID symbolic	OID numeric	Type	Access	Description
ligoWJetMimoMIB	1.3.6.1.4.1.32750.3.9			The LigoWave W-Jet MIMO Protocol MIB.
ligoWJetMimoMIBObjects	1.3.6.1.4.1.32750.3.9.1
ligoWJetMimoNotifs	1.3.6.1.4.1.32750.3.9.1.0
ligoWJetMimoInfo	1.3.6.1.4.1.32750.3.9.1.1
ligoWJetMimoConf	1.3.6.1.4.1.32750.3.9.1.2
ligoWJetMimoStats	1.3.6.1.4.1.32750.3.9.1.3
wJetMimoStatsTable	1.3.6.1.4.1.32750.3.9.1.3.1		not-accessible	W-Jet MIMO protocol statistics table.
wJetMimoStatsEntry	1.3.6.1.4.1.32750.3.9.1.3.1.1		not-accessible	W-Jet MIMO protocol statistics table entry.
I32 wJetMimoPeerIndex	1.3.6.1.4.1.32750.3.9.1.3.1.1.1	Integer32	not-accessible	Peer index. Local device has index 0.
MAC wJetMimoMacAddress	1.3.6.1.4.1.32750.3.9.1.3.1.1.2	MacAddress	read-only	Peer MAC address.
C32 wJetMimoTxTokensEx	1.3.6.1.4.1.32750.3.9.1.3.1.1.3	Counter32	read-only	Number of transmitted tokens.
C32 wJetMimoRxTokens	1.3.6.1.4.1.32750.3.9.1.3.1.1.4	Counter32	read-only	Number of received tokens.
C32 wJetMimoDupTokens	1.3.6.1.4.1.32750.3.9.1.3.1.1.5	Counter32	read-only	Number of duplicate tokens.
C32 wJetMimoLostTokens	1.3.6.1.4.1.32750.3.9.1.3.1.1.6	Counter32	read-only	Number of lost tokens.
C32 wJetMimoDroppedTokens	1.3.6.1.4.1.32750.3.9.1.3.1.1.7	Counter32	read-only	Number of dropped tokens.
C32 wJetMimoTxFailures	1.3.6.1.4.1.32750.3.9.1.3.1.1.8	Counter32	read-only	Number of token transmissions failures.
C32 wJetMimoReinjectedTokens	1.3.6.1.4.1.32750.3.9.1.3.1.1.9	Counter32	read-only	Number of reinjected tokens.

RFC description

Vendor-private MIB for LIGO W JET MIMO wireless equipment management.

Start monitoring LigoWave W-Jet MIMO wireless bridge 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 LIGO-W-JET-MIMO-MIB