All MIBs › Baytech-MIB-403-1 › communicationEstablished
communicationEstablished
Module: Baytech-MIB-403-1
OID (symbolic): Baytech-MIB-403-1::communicationEstablished
OID (numeric): 1.3.6.1.4.1.4779.0.2
Node type: NOTIFICATION-TYPE
Description: INFORMATION: Communication with the unit has been established. Argument is timeTicks when communication was established.
Examples
Send this trap to an SNMP manager — replace <manager> with the IP or hostname of your monitoring server (SNMPv2c):
snmptrap -v2c -c public <manager> '' Baytech-MIB-403-1::communicationEstablished snmptrap -v2c -c public <manager> '' 1.3.6.1.4.1.4779.0.2
Listen for incoming traps on the manager host (-f keeps it in the foreground, -Lo prints to stdout — useful for testing):
snmptrapd -f -Lo -c /dev/null authCommunity log public
Example snmptrapd log entry:
zoo11-linux.zoo [UDP: [192.168.30.111]:63295->[192.168.30.10]:162]: DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (486231359) 56 days, 6:38:33.59 SNMPv2-MIB::snmpTrapOID.0 = OID: Baytech-MIB-403-1::communicationEstablished
Start monitoring Baytech 403-series power controller/PDU (legacy) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the Baytech-MIB-403-1::communicationEstablished OID value, configure state conditions and alerts, and monitor any Baytech 403-series power controller/PDU (legacy) from a single console.
OID Breakdown
Upper-level ancestors (7 from the standard OID tree / other modules)
| Numeric OID | Name | Module |
|---|---|---|
| 1 | iso | LANART-AGENT |
| 1.3 | org | AirPair-MIB |
| 1.3.6 | dod | AirPair-MIB |
| 1.3.6.1 | internet | AirPair-MIB |
| 1.3.6.1.4 | private | AirPair-MIB |
| 1.3.6.1.4.1 | enterprises | AirPair-MIB |
| 1.3.6.1.4.1.4779 | baytech | Baytech-MIB-401-4 |
| Numeric OID | Name | Module |
|---|---|---|
| 1.3.6.1.4.1.4779.0.2 | communicationEstablished | Baytech-MIB-403-1 |