towerops/priv/mibs/cisco/IRONPORT-SMI
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.3 KiB
Text

-- *****************************************************************
-- IRONPORT-SMI
--
-- Copyright (c) 2005-2011 by Cisco Systems, Inc.
-- All rights reserved.
-- *****************************************************************
IRONPORT-SMI DEFINITIONS ::= BEGIN
--
-- Top-level infrastructure of the IronPort project enterprise MIB tree
--
IMPORTS
MODULE-IDENTITY,
enterprises
FROM SNMPv2-SMI;
ironPort MODULE-IDENTITY
LAST-UPDATED "201105021600Z"
ORGANIZATION "IronPort Systems"
CONTACT-INFO
" Cisco IronPort Email and Web Security
Customer Service
Postal: 950 Elm Avenue
San Bruno, CA 94066
USA
Tel: +1 (650) 989-6533
E-mail: customercare@ironport.com"
DESCRIPTION
"Top-level infrastructure of the Cisco IronPort project
enterprise MIB tree."
REVISION "201105021600Z"
DESCRIPTION
"Cleaned up SMI definition."
REVISION "200506170000Z"
DESCRIPTION
"Initial revision."
::= { enterprises 15497 }
--
-- IronPort enterprise-specific management objects
--
asyncOSAppliances
OBJECT IDENTIFIER ::= { ironPort 1 }
asyncOSMail
OBJECT IDENTIFIER ::= { asyncOSAppliances 1 }
END