towerops/priv/mibs/corero/CORERO-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

38 lines
1,010 B
Text

CORERO-MIB DEFINITIONS ::= BEGIN
IMPORTS
MODULE-IDENTITY, OBJECT-IDENTITY, enterprises
FROM SNMPv2-SMI;
corero MODULE-IDENTITY
LAST-UPDATED "201706160000Z"
ORGANIZATION "Corero Network Security"
CONTACT-INFO
" Corero Support
E-mail: support.portal@corero.com"
DESCRIPTION
"Corero Management Server MIB."
REVISION "201706160000Z"
DESCRIPTION
"Updated contact info."
REVISION "201404240000Z"
DESCRIPTION
"Initial version of this MIB module."
::= { enterprises 41036 }
coreroRegistrations OBJECT-IDENTITY
STATUS current
DESCRIPTION
"This module defines the enterprises OID for Corero Network Security."
::= { corero 1 }
coreroProducts OBJECT-IDENTITY
STATUS current
DESCRIPTION
"A registration point under which all Corero AGENT-CAPABILIITES
definitions (and therefore values of sysObjectId) are defined."
::= { corero 2 }
END