towerops/priv/mibs/zyxel/ZYXEL-ES-ZyxelAPMgmt
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

52 lines
1 KiB
Text

-- **********************************************
-- ZyXEL Communications Corporation
--
-- Enterprise Solution MIB definitions
-- ZyXEL AP Management MIBs
--
-- LiKuang Tsai
--
-- Copyright by ZyXEL Communications Corp.
-- All rights reserved.
-- **********************************************
ZYXEL-ES-ZyxelAPMgmt DEFINITIONS ::= BEGIN
IMPORTS
MODULE-IDENTITY,
OBJECT-IDENTITY,
OBJECT-TYPE FROM SNMPv2-SMI
OBJECT-GROUP,
MODULE-COMPLIANCE FROM SNMPv2-CONF
esMgmt FROM ZYXEL-ES-SMI;
zyxelAPMgmt MODULE-IDENTITY
LAST-UPDATED "201403100000Z"
ORGANIZATION "Enterprise Solution ZyXEL"
CONTACT-INFO
""
DESCRIPTION
"The subtree for zyxelAPMgmt information"
::= { esMgmt 4 }
-- zyxelAPMgmt OIDs
operationMode OBJECT-TYPE
SYNTAX INTEGER {
standalone (1),
controller (2),
managed (3)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Wireless AP operation mode"
::= { zyxelAPMgmt 1 }
END