Graham McIntire
b4f8b40b7f
- 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.
44 lines
1.4 KiB
Text
44 lines
1.4 KiB
Text
--
|
|
-- Juniper Enterprise Specific MIB: Structure of Management Information
|
|
--
|
|
-- Copyright (c) 2002-2009, Juniper Networks, Inc.
|
|
-- All rights reserved.
|
|
--
|
|
-- The contents of this document are subject to change without notice.
|
|
--
|
|
|
|
JUNIPER-EX-SMI DEFINITIONS ::= BEGIN
|
|
|
|
IMPORTS
|
|
jnxExMibRoot FROM JUNIPER-SMI;
|
|
|
|
|
|
|
|
--
|
|
-- This MIB file added the nodes to create the Juniper Security
|
|
-- tree structure under the object node: jnxExObjects.
|
|
-- In general, the prefix jnxEx is used to name the object identifiers
|
|
-- and to designate them.
|
|
--
|
|
-- The jnxEx node is designed to provide a branch for the Switching
|
|
-- related MIB defintions specific to the EX products.
|
|
--
|
|
|
|
--
|
|
-- Object identifier added as the basis for identifying other EX nodes.
|
|
--
|
|
jnxExSwitching OBJECT IDENTIFIER ::= { jnxExMibRoot 1 }
|
|
|
|
|
|
--
|
|
-- next level object identifiers under jnxExSwitching
|
|
--
|
|
jnxExAnalyzer OBJECT IDENTIFIER ::= { jnxExSwitching 1 }
|
|
jnxExSecureAccessPort OBJECT IDENTIFIER ::= { jnxExSwitching 2 }
|
|
jnxExPaeExtension OBJECT IDENTIFIER ::= { jnxExSwitching 3 }
|
|
jnxExVirtualChassis OBJECT IDENTIFIER ::= { jnxExSwitching 4 }
|
|
jnxExVlan OBJECT IDENTIFIER ::= { jnxExSwitching 5 }
|
|
jnxRPS OBJECT IDENTIFIER ::= { jnxExSwitching 6 }
|
|
jnxMacNotificationRoot OBJECT IDENTIFIER ::= { jnxExSwitching 7 }
|
|
END
|
|
|