towerops/priv/mibs/axis/AXIS-ROOT-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

36 lines
1 KiB
Text
Executable file

AXIS-ROOT-MIB DEFINITIONS ::= BEGIN
IMPORTS
enterprises, MODULE-IDENTITY, OBJECT-IDENTITY
FROM SNMPv2-SMI;
axis MODULE-IDENTITY
LAST-UPDATED "201206081000Z"
ORGANIZATION "Axis Communications AB"
CONTACT-INFO
"Postal: Axis Communications AB
Emdalavagen 14
SE-223 69 Lund
Sweden
Phone: +46 (0)46 272 18 00
Fax: +46 (0)46 13 61 30
E-Mail: info@axis.com
Web: www.axis.com"
DESCRIPTION
"The AXIS root MIB."
REVISION "201206081000Z"
DESCRIPTION
"Initial version of this MIB module."
::= { enterprises 368 } -- assigned by IANA
products OBJECT-IDENTITY
STATUS current
DESCRIPTION
"products is the root OBJECT IDENTIFIER from which
sysObjectID values are assigned. Actual values and
respectively products sub-tree are defined in:
AXIS-PRINTSERVER-MIB
AXIS-VIDEO-MIB"
::= { axis 1 }
END