towerops/priv/mibs/dragonwave/HORIZON-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

32 lines
739 B
Text

-- File Name : horizon-MIB.mib
-- Version : 1.02.00
-- Date : July 13, 2011
-- Author : DragonWave Inc.
HORIZON-MIB DEFINITIONS ::= BEGIN
IMPORTS
OBJECT-TYPE
FROM RFC-1212
enterprises
FROM RFC1155-SMI;
dragonwave OBJECT IDENTIFIER
::= { enterprises 7262 }
horizon OBJECT IDENTIFIER
::= { dragonwave 2 }
--
-- Node definitions
--
hzSystemType OBJECT-TYPE
SYNTAX INTEGER { odu( 1 ) , idu( 2 ) , quantum( 3 ), hcp(4)}
ACCESS read-only
STATUS mandatory
DESCRIPTION "The current type of the system. "
::= { horizon 1 }
END