towerops/priv/mibs/nortel/RAPID-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

29 lines
1 KiB
Text

RAPID-MIB DEFINITIONS ::= BEGIN
IMPORTS
enterprises FROM SNMPv2-SMI;
rapidstream OBJECT IDENTIFIER ::= { enterprises 4355 }
rsProducts OBJECT IDENTIFIER ::= { rapidstream 1 }
fbXSeries OBJECT IDENTIFIER ::= { rsProducts 4 }
-- fbX series
fbX500 OBJECT IDENTIFIER ::= { fbXSeries 1 }
fbX550e OBJECT IDENTIFIER ::= { fbXSeries 2 }
fbX700 OBJECT IDENTIFIER ::= { fbXSeries 3 }
fbX750e OBJECT IDENTIFIER ::= { fbXSeries 4 }
fbX1000 OBJECT IDENTIFIER ::= { fbXSeries 5 }
fbX1250e OBJECT IDENTIFIER ::= { fbXSeries 6 }
fbX2500 OBJECT IDENTIFIER ::= { fbXSeries 7 }
fbX5000 OBJECT IDENTIFIER ::= { fbXSeries 8 }
fbX5500e OBJECT IDENTIFIER ::= { fbXSeries 9 }
fbX6000 OBJECT IDENTIFIER ::= { fbXSeries 10 }
fbX6500e OBJECT IDENTIFIER ::= { fbXSeries 11 }
fbX8000 OBJECT IDENTIFIER ::= { fbXSeries 12 }
fbX8500e OBJECT IDENTIFIER ::= { fbXSeries 13 }
fbX8500e-F OBJECT IDENTIFIER ::= { fbXSeries 14 }
END