FRIENDLY-TECH-ACS-MIB OID Mapping

Version 1.6.9-option-3 | Updated: August 07, 2026

FRIENDLY-TECH-ACS-MIB OID Mapping

Enterprise OID: 1.3.6.1.4.1.65666 (registered PEN: 65666, Friendly Technologies LTD.)

OID Structure

1.3.6.1.4.1.65666           - friendlyTechAcsMIB (enterprise root)
1.3.6.1.4.1.65666.1         - ftAcsObjects
1.3.6.1.4.1.65666.1.1       - ftAcsNotifyObjects (variable bindings)
1.3.6.1.4.1.65666.2         - ftAcsNotifications
1.3.6.1.4.1.65666.2.0       - ftAcsTraps (trap definitions)

Variable Bindings (ftAcsNotifyObjects)

OID Name Type Description

.1.1

ftAlarmSeverity

INTEGER

1=critical, 2=warning, 3=info, 4=clear

.1.2

ftAlarmName

STRING

Alarm identifier (e.g., “DbUnreachable”)

.1.3

ftAlarmSummary

STRING

Brief summary

.1.4

ftAlarmDescription

STRING

Detailed description

.1.5

ftAlarmInstance

STRING

Instance (server, host)

.1.6

ftAlarmTimestamp

STRING

ISO 8601 timestamp

.1.7

ftAlarmProtocol

STRING

Protocol (TR069, LWM2M, etc.)

.1.8

ftAlarmThreshold

INTEGER

Threshold value

.1.9

ftAlarmCurrentValue

INTEGER

Current value

Trap Definitions (ftAcsTraps)

Infrastructure Alarms (OID .2.0.1 - .2.0.10)

Trap OID Name Alertmanager alertname Severity

.2.0.1

ftAcsCommProblem

AcsCommProblem

critical

.2.0.2

ftAcsCommRestored

AcsCommProblem (resolved)

clear

.2.0.3

ftDbUnreachable

DbUnreachable

critical

.2.0.4

ftDbRestored

DbUnreachable (resolved)

clear

.2.0.5

ftTimeDrift

TimeDrift

warning

.2.0.6

ftTimeSynced

TimeDrift (resolved)

clear

Licensing Alarms (OID .2.0.11 - .2.0.20)

Trap OID Name Alertmanager alertname Severity

.2.0.11

ftLicenseExpiring

LicenseExpiring

warning

.2.0.12

ftLicenseExpired

LicenseExpired

critical

.2.0.13

ftLicenseRenewed

LicenseExpired (resolved)

clear

Device Limit Alarms (OID .2.0.21 - .2.0.40)

Trap OID Name Alertmanager alertname Severity

.2.0.21

ftDeviceAccessDenied

DeviceAccessDenied

critical

.2.0.22

ftDeviceLimitWarning

DeviceLimitWarning

warning

.2.0.23

ftDeviceLimitExceeded

DeviceLimitExceeded

critical

.2.0.24

ftDeviceLimitCleared

DeviceLimit* (resolved)

clear

.2.0.25

ftTR069LimitWarning

TR069LimitWarning

warning

.2.0.26

ftTR069LimitExceeded

TR069LimitExceeded

critical

.2.0.27

ftLWM2MLimitWarning

LWM2MLimitWarning

warning

.2.0.28

ftLWM2MLimitExceeded

LWM2MLimitExceeded

critical

.2.0.29

ftMQTTLimitWarning

MQTTLimitWarning

warning

.2.0.30

ftMQTTLimitExceeded

MQTTLimitExceeded

critical

.2.0.31

ftUSPLimitWarning

USPLimitWarning

warning

.2.0.32

ftUSPLimitExceeded

USPLimitExceeded

critical

.2.0.33

ftProtocolLimitCleared

*LimitWarning (resolved)

clear

Infrastructure Resource Alarms (OID .2.0.41 - .2.0.70)

Trap OID Name Alertmanager alertname Severity

.2.0.41

ftServerDown

ServiceDown

critical

.2.0.42

ftServerRestored

ServiceDown (resolved)

clear

.2.0.43

ftAPIDown

APIDown

critical

.2.0.44

ftAPIRestored

APIDown (resolved)

clear

.2.0.45

ftFrontendDown

FrontendDown

critical

.2.0.46

ftFrontendRestored

FrontendDown (resolved)

clear

.2.0.47

ftCPUUsageWarning

CPUUsageHigh

warning

.2.0.48

ftCPUUsageCritical

CPUUsageCritical

critical

.2.0.49

ftCPUUsageCleared

CPUUsageHigh (resolved)

clear

.2.0.50

ftMemoryUsageWarning

MemoryUsageHigh

warning

.2.0.51

ftMemoryUsageCritical

MemoryUsageCritical

critical

.2.0.52

ftMemoryUsageCleared

MemoryUsageHigh (resolved)

clear

.2.0.53

ftDiskSpaceWarning

DiskSpaceFilling

warning

.2.0.54

ftDiskSpaceCritical

DiskSpaceCritical

critical

.2.0.55

ftDiskSpaceCleared

DiskSpaceFilling (resolved)

clear

.2.0.56

ftTCPSessionsWarning

TCPSessionsWarning

warning

.2.0.57

ftTCPSessionsCritical

TCPSessionsCritical

critical

.2.0.58

ftTCPSessionsCleared

TCPSessionsWarning (resolved)

clear

.2.0.59

ftHTTPSessionsWarning

HTTPSessionsWarning

warning

.2.0.60

ftHTTPSessionsCritical

HTTPSessionsCritical

critical

.2.0.61

ftHTTPSessionsCleared

HTTPSessionsWarning (resolved)

clear

.2.0.62

ftUDPSessionsWarning

UDPSessionsWarning

warning

.2.0.63

ftUDPSessionsCritical

UDPSessionsCritical

critical

.2.0.64

ftUDPSessionsCleared

UDPSessionsWarning (resolved)

clear

.2.0.65

ftHazelcastNodeDown

HazelcastNodeDown

critical

.2.0.66

ftHazelcastRestored

HazelcastNodeDown (resolved)

clear

.2.0.67

ftMySQLDown

MySQLDown

critical

.2.0.68

ftMySQLRestored

MySQLDown (resolved)

clear

Full OID Examples

# DB Unreachable trap
1.3.6.1.4.1.65666.2.0.3

# License Expiring trap
1.3.6.1.4.1.65666.2.0.11

# TR-069 Limit Warning trap
1.3.6.1.4.1.65666.2.0.25

Trigger vs Resolved OIDs

Each alert uses separate OIDs for triggered and resolved states:

  • oid label — OID sent when alert fires (e.g., .2.0.3 for DbUnreachable)

  • oid_resolved label — OID sent when alert resolves (e.g., .2.0.4 for DbRestored)

The snmp-notifier is configured with:

  • --trap.oid-label=oid — reads firing OID from alert label

  • --trap.resolution-oid-label=oid_resolved — reads resolution OID from alert label

Example Prometheus rule:

* alert: DbUnreachable
  expr: alert{name="db_server_down", type="alert"} == 1
  labels:
    oid: "1.3.6.1.4.1.65666.2.0.3"          # trigger trap
    oid_resolved: "1.3.6.1.4.1.65666.2.0.4"  # resolved trap

Notification Channels

AlertManager sends notifications via multiple channels:

  • Email — via SMTP (MailPit for testing), HTML template with alert details

  • Telegram — bot message with alert summary, severity, instance

  • SNMP — trap via snmp-notifier with per-alert OID and resolved OID

  • Slack — webhook integration (requires workspace webhook URL)

  • MS Teams — webhook integration

  • Webhook — generic HTTP POST (used by snmp-notifier)

All channels support send_resolved: true — notifications sent for both firing and resolved states.

Testing

# Verify MIB syntax
snmptranslate -m +./FRIENDLY-TECH-ACS-MIB.txt -IR ftDbUnreachable

# Send test trap
snmptrap -v 2c -c public localhost:162 '' \
  1.3.6.1.4.1.65666.2.0.3 \
  1.3.6.1.4.1.65666.1.1.1 i 1 \
  1.3.6.1.4.1.65666.1.1.2 s "DbUnreachable" \
  1.3.6.1.4.1.65666.1.1.3 s "Database server unreachable"