initial commit; version 22.5.12042

mibs/paradyne/PDN-TRAPMGR-MIB

@@ -0,0 +1,246 @@
+PDN-TRAPMGR-MIB DEFINITIONS ::= BEGIN
+
+
+
+IMPORTS
+
+	IpAddress
+
+		FROM RFC1155-SMI
+
+	OBJECT-TYPE
+
+		FROM RFC-1212
+
+	SwitchState
+
+		FROM PDN-TC
+
+        DisplayString, RowStatus
+
+                FROM SNMPv2-TC
+
+     	pdn-traps
+
+		FROM PDN-HEADER-MIB;
+
+
+
+-- ===============================================================
+
+--
+
+-- Device Traps Manager,  01/30/97 
+
+--
+
+-- This MIB will allow an SNMP Manager the ability to edit the Trap Manager
+
+-- table on a Paradyne device. It provides a mechanism to add, delete or edit
+
+-- trap manager entries.
+
+--
+
+-- ===============================================================
+
+--
+
+-- 09/03/2002   Jesus Pinto pinto@paradyne.com
+
+-- Added pdnDevTrapMgrTable
+
+--
+
+-- ===============================================================
+
+--
+
+-- 09/11/2002   Jesus Pinto pinto@paradyne.com
+
+-- Implement changes as per MIBWG review meeting:
+
+--    o Move sysDevConfigTrapsEnable to this mib
+
+--      (renamed as pdnDevConfigTrapsEnable).
+
+--    o Remove devTrapMgrLevel from this mib
+
+--      (not being used, never approved)
+
+--
+
+-- ===============================================================
+
+
+
+devTrapMgrMaxNumber OBJECT-TYPE
+
+    SYNTAX  INTEGER
+
+    ACCESS  read-only
+
+    STATUS  mandatory
+
+    DESCRIPTION
+
+        "Maximum number of managers allowed in the devTrapMgrTable. This 
+
+        may vary per device."
+
+    ::= { pdn-traps 1 }
+
+
+
+devTrapMgrCurrentNumber OBJECT-TYPE
+
+    SYNTAX  INTEGER
+
+    ACCESS  read-only
+
+    STATUS  mandatory
+
+    DESCRIPTION
+
+        "Current number of managers in devTrapMgrTable."
+
+    ::= { pdn-traps 2 }
+
+
+
+devTrapMgrTable OBJECT-TYPE
+
+    SYNTAX  SEQUENCE OF DevTrapMgrEntry
+
+    ACCESS  not-accessible
+
+    STATUS  mandatory
+
+    DESCRIPTION
+
+        "The trap manager table."
+
+    ::= { pdn-traps 3 }
+
+
+
+devTrapMgrEntry OBJECT-TYPE
+
+    SYNTAX  DevTrapMgrEntry
+
+    ACCESS  not-accessible
+
+    STATUS  mandatory
+
+    DESCRIPTION
+
+        "An entry in the trap manager table."
+
+    INDEX { devTrapMgrIpAddress }
+
+    ::= { devTrapMgrTable 1 }
+
+
+
+--
+
+-- Layout of one entry in the devTrapManagerTable
+
+--
+
+
+
+DevTrapMgrEntry ::=
+
+    SEQUENCE {
+
+        devTrapMgrIpAddress
+
+            IpAddress,
+
+        devTrapMgrDestination
+
+            INTEGER,
+
+        devTrapMgrCircuit
+
+            INTEGER,
+
+	devTrapMgrSubCircuit
+
+	    INTEGER
+
+    } 
+
+
+
+devTrapMgrIpAddress OBJECT-TYPE
+
+    SYNTAX  IpAddress
+
+    ACCESS  read-write
+
+    STATUS  mandatory
+
+    DESCRIPTION
+
+        "Unique IP address identifying a Trap Manager. An
+
+	 existing Trap Manager may be deleted by setting
+
+	 the devTrapMgrIpAddress object to 0.0.0.0 or by
+
+	 setting the devTrapMgrIpAddress object to a new
+
+	 address.  A new Trap Manager may be added by setting
+
+	 the devTrapMgrIpAddress object of 0.0.0.0 to the new
+
+	 address as long as there is still room for another
+
+	 Trap Manager."
+
+    ::= { devTrapMgrEntry 1 }
+
+
+
+devTrapMgrDestination OBJECT-TYPE
+
+    SYNTAX INTEGER 
+
+    ACCESS  read-write
+
+    STATUS  mandatory
+
+    DESCRIPTION
+
+        "The ifIndex to be used with the associated IpAddress
+
+	 when sending traps."
+
+    ::= { devTrapMgrEntry 2 }
+
+
+
+devTrapMgrCircuit OBJECT-TYPE
+
+    SYNTAX INTEGER 
+
+    ACCESS  read-write
+
+    STATUS  mandatory
+
+    DESCRIPTION
+
+        "The circuit used for management when multiple circuits
+
+	 are allowed over the specified interface (ifIndex). If
+
+	 the interface allows only one circuit, devTrapMgrCircuit
+
+	 is set to 0."
+
+    ::= { devTrapMgrEntry 3 }
+
+
+