towerops/priv/mibs/fs/LLDPPRIVATE-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

54 lines
1.4 KiB
Text

LLDPPRIVATE-MIB DEFINITIONS ::= BEGIN
IMPORTS
MODULE-IDENTITY, Counter32, TimeTicks, OBJECT-TYPE, Integer32
FROM SNMPv2-SMI
MODULE-COMPLIANCE, OBJECT-GROUP
FROM SNMPv2-CONF
gbnL2 FROM ADMIN-MASTER-MIB;
lldpPrivateMIB MODULE-IDENTITY
LAST-UPDATED "200607270000Z" -- July 27, 2006
ORGANIZATION "admin Inc."
CONTACT-INFO
"admin
E-mail: "
DESCRIPTION "LLDP private module management."
REVISION "200607270000Z" -- July 27, 2006
DESCRIPTION "Initial Version"
::= { gbnL2 5 }
lldpPrivateObjects OBJECT IDENTIFIER ::= { lldpPrivateMIB 0 }
--
-- ***********************************************************
--
-- L L D P PRIVATE C O N F I G
--
-- ***********************************************************
--
lldpAdminStatus OBJECT-TYPE
SYNTAX INTEGER {
enable(1),
disable(2)
}
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"If lldpAdminStatus object has a value of 'enable(1)',then LLDP
module configuration will be active. If lldpAdminStatus object has a
value of 'disable(2)',then LLDP module configuration will be
inactive."
REFERENCE
"LLDP system admin status"
DEFVAL { disable }
::= { lldpPrivateObjects 1 }
END