towerops/priv/mibs/tplink/TPLINK-MIB
Graham McIntire b4f8b40b7f
Include MIB files in Docker image instead of using PVC
- Remove PVC volume mount from k8s/deployment.yaml
- Delete k8s/mib-pvc.yaml (no longer needed)
- Update .gitignore to commit MIB files to git
- Add mix import_mibs task to copy MIBs from LibreNMS
- Add all MIB files from priv/mibs/ to git

This fixes the multi-attach volume error in Kubernetes where new pods
couldn't start because the RWO (ReadWriteOnce) PVC was attached to the
old pod. MIBs are now part of the Docker image and can be used by all
pods simultaneously.
2026-01-19 14:01:03 -06:00

40 lines
1.1 KiB
Text

TPLINK-MIB DEFINITIONS ::= BEGIN
--iso OBJECT IDENTIFIER ::= { 1 }
--org OBJECT IDENTIFIER ::= { iso 3 }
--dod OBJECT IDENTIFIER ::= { org 6 }
--internet OBJECT IDENTIFIER ::= { dod 1 }
--private OBJECT IDENTIFIER ::= { internet 4 }
--enterprises OBJECT IDENTIFIER ::= { private 1 }
IMPORTS
enterprises
FROM RFC1155-SMI
OBJECT-IDENTITY
FROM SNMPv2-SMI;
tplink OBJECT IDENTIFIER ::= { enterprises 11863 }
switch OBJECT IDENTIFIER ::= { tplink 1 }
router OBJECT IDENTIFIER ::= { tplink 2 }
wireless OBJECT IDENTIFIER ::= { tplink 3 }
adsl OBJECT IDENTIFIER ::= { tplink 4 }
tplinkProducts OBJECT-IDENTITY
STATUS current
DESCRIPTION
"tplinkProducts is the root OBJECT IDENTIFIER from
which sysObjectID values are assigned. Actual
values are defined in TPLINK-PRODUCTS-MIB."
::= { tplink 5 }
tplinkMgmt OBJECT-IDENTITY
STATUS current
DESCRIPTION
"tplinkMgmt is the main subtree for new mib development."
::= { tplink 6 }
END