UBQS-ENTITY-ALARM-MIB :: ubiAlarmContactTrigger

MIB Reference — IPNetwork Monitor · Updated October 06, 2026

All MIBs › UBQS-ENTITY-ALARM-MIB › ubiAlarmContactTrigger

ubiAlarmContactTrigger

Module: UBQS-ENTITY-ALARM-MIB

OID (symbolic): UBQS-ENTITY-ALARM-MIB::ubiAlarmContactTrigger

OID (numeric): 1.3.6.1.4.1.7800.100.28.1.1.1.4

Node type: OBJECT-TYPE

Type: INTEGER

Access: read-write

Description: This object specifies the trigger state associated with the specific alarm.

What is ubiAlarmContactTrigger?

This writable value specifies which physical contact state, closed(1) or open(2), is defined as the condition that triggers this alarm. Admins set it to match how the external sensor is wired, normally-open or normally-closed, so the device correctly interprets when an alarm condition exists. For example, for a door sensor wired normally-closed, setting the trigger to open(2) means the alarm fires when the door opens and the circuit breaks.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.7800.100.28.1.1.1.4
snmpwalk -v2c -c public <target> UBQS-ENTITY-ALARM-MIB::ubiAlarmContactTrigger

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.7800.100.28.1.1.1.4.1
snmpget -v2c -c public <target> UBQS-ENTITY-ALARM-MIB::ubiAlarmContactTrigger.1

Set instance 1 (SNMPv2c):

snmpset -v2c -c private <target> 1.3.6.1.4.1.7800.100.28.1.1.1.4.1 i <value>

Start monitoring Ubiquoss access/aggregation switch (environmental alarm severity/enable status) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the UBQS-ENTITY-ALARM-MIB::ubiAlarmContactTrigger OID value, configure state conditions and alerts, and monitor any Ubiquoss access/aggregation switch (environmental alarm severity/enable status) from a single console.

How to Use in IPNetwork Monitor

Select an Ubiquoss access/aggregation switch (environmental alarm severity/enable status) 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 ubiAlarmContactTrigger 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. This object specifies the trigger state associated with the specific alarm. 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 an INTEGER-type OID, Value bounds is the most useful condition here — trigger an alert if the value changes unexpectedly, since which state (open or closed) is normal for this contact depends on how it's wired. Click Finish to create the monitor; you can adjust any parameter later.

OID Breakdown

Upper-level ancestors (8 from the standard OID tree / other modules)
Numeric OIDNameModule
1isoLANART-AGENT
1.3orgAirPair-MIB
1.3.6dodAirPair-MIB
1.3.6.1internetAirPair-MIB
1.3.6.1.4privateAirPair-MIB
1.3.6.1.4.1enterprisesAirPair-MIB
1.3.6.1.4.1.7800ubiquossUBIQUOSS-SMI
1.3.6.1.4.1.7800.100ubiMgmtv2UBQS-SMI
Numeric OIDNameModule
1.3.6.1.4.1.7800.100.28ubiEntityAlarmMIBUBQS-ENTITY-ALARM-MIB
1.3.6.1.4.1.7800.100.28.1ubiEntityAlarmMIBObjectsUBQS-ENTITY-ALARM-MIB
1.3.6.1.4.1.7800.100.28.1.1ubiAlarmContactTableUBQS-ENTITY-ALARM-MIB
1.3.6.1.4.1.7800.100.28.1.1.1ubiAlarmContactEntryUBQS-ENTITY-ALARM-MIB
1.3.6.1.4.1.7800.100.28.1.1.1.4ubiAlarmContactTriggerUBQS-ENTITY-ALARM-MIB