towerops/priv/mibs/barracuda/BARRACUDA-REF-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

22 lines
552 B
Text

BARRACUDA-REF DEFINITIONS ::= BEGIN
IMPORTS
MODULE-IDENTITY, enterprises
FROM SNMPv2-SMI;
barracuda MODULE-IDENTITY
LAST-UPDATED "200906100000Z" -- June 10, 2009
ORGANIZATION "Barracuda Networks, Inc."
CONTACT-INFO
"
Barracuda Networks Inc.
3175 S. Winchester Blvd.
Campbell, CA 95008
"
DESCRIPTION
"
Main Barracuda MIB
"
::= { enterprises 20632 } -- assigned by IANA
END