AKCP OID Queries & SNMP Monitoring: Complete Guide for SensorProbe (Temperature, Humidity, Relay)

Overview: What is an OID and why is it important?

An OID (Object Identifier) is a unique identifier within a Management Information Base (MIB). A MIB is a structured database that describes the variables (objects) offered by network devices. For monitoring AKCP sensors (e.g. AKCP SensorProbe8, AKCP sensorProbe8-X20), OID paths are essential because they specify exactly which measurement (temperature, humidity, switch state, etc.) can be read at which port. Executing SNMP queries correctly means accessing sensor values directly via OIDs.

Basic structure of AKCP OIDs

AKCP OIDs start with the common prefix 1.3.6.1.4.1.3854.1.2.2.1 and branch into groups representing different sensor types:

• Group/type identification (e.g. Group A = temperature, Group B = analog sensors like humidity, Group C = switched sensors like water or relays).
• The last segment contains the Port Index (X), running from 0–7 for SensorProbe8 devices or up to 27 for sensorProbe8-X20 units.

Detailed OID examples: Group A (Temperature)

For AKCP temperature sensors (keyword: AKCP Temperature Sensor OID), the common OIDs are:

 sensorProbeTempDegree = 1.3.6.1.4.1.3854.1.2.2.1.16.1.3.X 
 sensorProbeTempStatus = 1.3.6.1.4.1.3854.1.2.2.1.16.1.4.X 

Replace X with the port index: on a SensorProbe8, it is 0–7; on a sensorProbe8-X20, indices can go up to 27. Example: .1.3.6.1.4.1.3854.1.2.2.1.16.1.3.0 represents the temperature sensor at Port 1 (Index 0).

Group B: Analog Sensors (Humidity, Airflow, 4-20mA)

Group B covers humidity sensors or 4-20mA converters. Relevant OIDs:

 sensorProbeHumidityPercent = 1.3.6.1.4.1.3854.1.2.2.1.17.1.3.X 
 sensorProbeHumidityStatus  = 1.3.6.1.4.1.3854.1.2.2.1.17.1.4.X 

For documentation and mapping, use tables aligning port index, physical RJ-45 port, and OID for easier SNMP automation in monitoring systems (keyword: SNMP OID query AKCP).

Group C: Switched Sensors (Switch, Water, Relay, Siren)

 sensorProbeSwitchStatus = 1.3.6.1.4.1.3854.1.2.2.1.18.1.3.X 

This OID reports switch state. For water detectors or motion/security sensors, fast SNMP queries ensure timely alarms in network management systems.

AKCP Dual Sensors (Temperature & Humidity)

AKCP dual sensors combine both functions in one unit. Internally, they are treated as two separate OIDs (temperature in Group A and humidity in Group B).

Practical SNMP queries: snmpget & snmpwalk

 snmpget -v2c -c COMMUNITY IP .1.3.6.1.4.1.3854.1.2.2.1.16.1.3.0 
 snmpwalk -v2c -c COMMUNITY IP 1.3.6.1.4.1.3854.1.2.2 

Use snmpget for a single OID (e.g. Temperature OID AKCP). snmpwalk traverses a subtree. snmpget is often faster and less resource-intensive in automated scripts.

Integration with monitoring systems (Zabbix, Nagios, PRTG)

In Zabbix or Nagios, define items with regular SNMP queries:

• Item name: AKCP_Temp_Port_1
• SNMP OID: 1.3.6.1.4.1.3854.1.2.2.1.16.1.3.0
• Interval: 60s
• Trigger: Temperature > threshold

In PRTG or other NMS tools, import the AKCP MIB (AKCP MIB download). Always document location, rack, and contact info for escalation.

Mapping port → X-index

Port mapping rule:
Port 1 → Index 0
Port 2 → Index 1
... Port 8 → Index 7

Applies to SensorProbe8. For sensorProbe8-X20, higher indices apply. Confirm with device documentation or run snmpwalk.

Example: SNMP Integration Step by Step

1. Note device IP and community string.
2. Download and import AKCP MIB into your NMS if needed.
3. Run snmpwalk: snmpwalk -v2c -c public 192.168.1.100 1.3.6.1.4.1.3854.
4. Create items for each port, define thresholds.
5. Configure alerts (SMS, email, webhook, syslog).

Best practices for robust SNMP monitoring

• Use VLANs for isolating SNMP traffic.
• Understand AKCP MIB data types (INTEGER, OCTET STRING, Gauge).
• Use reasonable polling intervals (60–300s).
• Document mappings in tables.

Alerts and Escalation

1. Trigger initial alert (E-mail + dashboard).
2. Retry alerts if unacknowledged.
3. Create tickets upon critical state confirmation.

Combine polling with SNMP traps for near real-time alarms. Ensure port 162/UDP is allowed in firewalls.

SNMP versions and security

Always prefer SNMPv3 for authentication and encryption. SNMPv1/v2c use weak community strings. Check AKCP model manuals for SNMPv3 support.

Troubleshooting common issues

• No response to snmpget: Check IP, community, firewall.
• Wrong values: Check scaling (integer vs decimals).
• Mapping issues: Use snmpwalk to confirm indices.
• Lost traps: Verify firewall UDP 162.

Scaling: Monitoring many sensors

• Use central pollers with local collectors.
• Batch queries to reduce network load.
• Automate deployment with templates (e.g. via Ansible).

Example OID table

Practical automation: Script example (pseudo)

 for idx in 0 1 2 3 4 5 6 7; do 
 oid=".1.3.6.1.4.1.3854.1.2.2.1.16.1.3.$idx"
 value=$(snmpget -v2c -c COMMUNITY IP $oid)
 echo "Port $((idx+1)): $value" 
 done 

Conclusion

Accurate OID mapping is essential for reliable monitoring of AKCP sensors. Use the provided examples such as sensorProbeTempDegree and sensorProbeSwitchStatus, automate mapping with templates, and always prefer SNMPv3. For advanced integration, refer to the AKCP MIB files and consult support if needed.