towerops/priv/mibs/smartoptics/MSERIES-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

52 lines
No EOL
1.5 KiB
Text

-- SmartOptics Enterprise Specific MIB.
--
-- Copyright (c) 2011, SmartOptics
-- All rights reserved
--
MSERIES-MIB DEFINITIONS ::= BEGIN
IMPORTS
enterprises, MODULE-IDENTITY, OBJECT-IDENTITY
FROM SNMPv2-SMI;
smartoptics MODULE-IDENTITY
LAST-UPDATED "201402121327Z"
ORGANIZATION "SmartOptics"
CONTACT-INFO "http://www.smartoptics.com"
DESCRIPTION
"This is the enterprise specific MIB for SmartOptics M-Series.
The root of the OID sub-tree assigned to SmartOptics."
REVISION "201402121327Z"
DESCRIPTION
"The initial revision."
::= { enterprises 30826 }
mseries OBJECT-IDENTITY
STATUS current
DESCRIPTION
"The M-Series product root."
::= { smartoptics 1}
-- MIB overview
-- MSERIES-SYSTEM smartSystemMIB
-- tbd
-- MSERIES-ALARM smartAlarmMIB
-- Active Alarm List and Log.
-- MSERIES-TC smartTcMIB
-- Textual coneventions
-- MSERIES-PORT smartPortMIB
-- Line and Client Port Description.
-- MSERIES-ENVMON smartEnvMonMIB
-- Temperature sensor reading from the M-Series.
END