- 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.
30 lines
864 B
Text
30 lines
864 B
Text
CISCOSMB-MIB DEFINITIONS ::= BEGIN
|
|
IMPORTS
|
|
enterprises FROM RFC1155-SMI;
|
|
|
|
cisco MODULE-IDENTITY
|
|
LAST-UPDATED "201010310000Z"
|
|
ORGANIZATION "Cisco Systems, Inc."
|
|
|
|
CONTACT-INFO
|
|
"Postal: 170 West Tasman Drive
|
|
San Jose , CA 95134-1706
|
|
USA
|
|
|
|
|
|
Website: Cisco Small Business Support Community <http://www.cisco.com/go/smallbizsupport>"
|
|
|
|
DESCRIPTION
|
|
"The private MIB module definition for CISCOSB private MIB tree."
|
|
REVISION "201010310000Z"
|
|
DESCRIPTION
|
|
"Initial revision."
|
|
::= { enterprises 9 }
|
|
|
|
--cisco OBJECT IDENTIFIER ::= { enterprises 9 }
|
|
otherEnterprises OBJECT IDENTIFIER ::= { cisco 6 }
|
|
ciscosb OBJECT IDENTIFIER ::= {otherEnterprises 1}
|
|
switch001 OBJECT IDENTIFIER ::= { ciscosb 101 }
|
|
rndMib OBJECT IDENTIFIER ::= { ciscosb 101 }
|
|
|
|
END
|