graham/towerops
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Include MIB files in Docker image instead of using PVC

Browse source 
- 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.
This commit is contained in:
Graham McIntire 2026-01-19 14:01:03 -06:00
parent f497de4474
commit b4f8b40b7f
No known key found for this signature in database
4780 changed files with 10155248 additions and 27 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

7
.gitignore vendored
View file

@ -58,8 +58,5 @@ profiles.json
/mibs/*
!/mibs/.gitkeep
# Application MIB files (imported from LibreNMS)
# Ignore everything in priv/mibs except README.md and .gitkeep marker files
/priv/mibs/*
!/priv/mibs/README.md
!/priv/mibs/.gitkeep
# Application MIB files (now committed to git and included in Docker image)
# Only ignore the top-level librenms mibs directory (symlink)

10
k8s/deployment.yaml
View file

@ -5,7 +5,7 @@ metadata:
name: towerops
namespace: towerops
spec:
replicas: 1
replicas: 4
strategy:
type: RollingUpdate
rollingUpdate:
@ -124,11 +124,3 @@ spec:
timeoutSeconds: 2
successThreshold: 1
failureThreshold: 2
volumeMounts:
- name: mibs
mountPath: /app/mibs
readOnly: false
volumes:
- name: mibs
persistentVolumeClaim:
claimName: towerops-mibs

13
k8s/mib-pvc.yaml
View file

@ -1,13 +0,0 @@
---
apiVersion: v1
kind: PersistentVolumeClaim
metadata:
name: towerops-mibs
namespace: towerops
spec:
accessModes:
- ReadWriteOnce # Ceph RBD only supports ReadWriteOnce
storageClassName: ceph-rbd # Use the default Ceph RBD storage class
resources:
requests:
storage: 1Gi # MIB files are typically small (few hundred MB)

160
lib/mix/tasks/import_mibs.ex Normal file
View file

@ -0,0 +1,160 @@
defmodule Mix.Tasks.ImportMibs do
@shortdoc "Import MIB files from LibreNMS to priv/mibs"
@moduledoc """
Imports MIB files from a LibreNMS installation to priv/mibs for inclusion in the Docker image.
## Usage
# Import all MIB files
mix import_mibs --source-path ~/dev/librenms/mibs
# Import specific vendors only
mix import_mibs --source-path ~/dev/librenms/mibs --vendors mikrotik,cisco,ubiquiti
## Options
* `--source-path` - Path to the LibreNMS mibs directory (required)
* `--vendors` - Comma-separated list of vendor directories to import (default: all)
* `--clean` - Remove existing MIBs in priv/mibs before importing (default: false)
## Notes
* Copies MIB files to priv/mibs/ which will be included in the Docker image
* Preserves directory structure from LibreNMS
* Standard MIB files are copied to priv/mibs/ root
* Vendor-specific MIBs are copied to priv/mibs/vendor_name/
* After importing, commit the changes to git so MIBs are included in the container
"""
use Mix.Task
require Logger
def run(args) do
{opts, _} =
OptionParser.parse!(args,
strict: [
source_path: :string,
vendors: :string,
clean: :boolean
]
)
source_path = opts[:source_path] || raise "Missing --source-path argument"
vendors = parse_vendors(opts[:vendors])
clean = opts[:clean] || false
if !File.exists?(source_path) do
raise "Source directory not found: #{source_path}"
end
dest_path = Path.join(["priv", "mibs"])
if clean do
Logger.info("Cleaning priv/mibs...")
File.rm_rf!(dest_path)
File.mkdir_p!(dest_path)
else
File.mkdir_p!(dest_path)
end
case vendors do
:all ->
import_all_vendors(source_path, dest_path)
vendor_list ->
import_specific_vendors(source_path, dest_path, vendor_list)
end
end
defp parse_vendors(nil), do: :all
defp parse_vendors(""), do: :all
defp parse_vendors(vendors_string) do
vendors_string
|> String.split(",")
|> Enum.map(&String.trim/1)
|> Enum.reject(&(&1 == ""))
end
defp import_all_vendors(source_path, dest_path) do
Logger.info("Discovering entries in #{source_path}...")
entries =
source_path
|> File.ls!()
|> Enum.reject(fn name ->
name == "lost+found" or String.starts_with?(name, ".")
end)
|> Enum.sort()
Logger.info("Found #{length(entries)} entries to import")
# Separate files and directories
{files, directories} =
Enum.split_with(entries, fn name ->
path = Path.join(source_path, name)
File.regular?(path)
end)
# Copy top-level MIB files (standard MIBs)
Logger.info("Copying #{length(files)} standard MIB files...")
Enum.each(files, fn file ->
copy_file(Path.join(source_path, file), Path.join(dest_path, file))
end)
# Copy vendor directories
Logger.info("Copying #{length(directories)} vendor directories...")
Enum.each(directories, fn vendor ->
copy_vendor_directory(source_path, dest_path, vendor)
end)
Logger.info("Import complete!")
Logger.info("Remember to commit the changes: git add priv/mibs && git commit")
end
defp import_specific_vendors(source_path, dest_path, vendors) do
Logger.info("Importing #{length(vendors)} specified vendors...")
Enum.each(vendors, fn vendor ->
vendor_source = Path.join(source_path, vendor)
if File.exists?(vendor_source) do
copy_vendor_directory(source_path, dest_path, vendor)
else
Logger.warning("Vendor directory not found: #{vendor}")
end
end)
Logger.info("Import complete!")
Logger.info("Remember to commit the changes: git add priv/mibs && git commit")
end
defp copy_vendor_directory(source_path, dest_path, vendor) do
vendor_source = Path.join(source_path, vendor)
vendor_dest = Path.join(dest_path, vendor)
Logger.info("Copying #{vendor}...")
case File.cp_r(vendor_source, vendor_dest) do
{:ok, _files} ->
:ok
{:error, reason, file} ->
Logger.error("Failed to copy #{vendor}: #{inspect(reason)} (file: #{file})")
end
end
defp copy_file(source, dest) do
case File.copy(source, dest) do
{:ok, _bytes} ->
:ok
{:error, reason} ->
Logger.error("Failed to copy #{Path.basename(source)}: #{inspect(reason)}")
end
end
end

142
priv/mibs/2n/TEL2N-MIB Normal file
View file

@ -0,0 +1,142 @@
TEL2N-MIB DEFINITIONS ::= BEGIN
IMPORTS
OBJECT-TYPE, MODULE-IDENTITY, enterprises,
Integer32, TimeTicks, IpAddress
FROM SNMPv2-SMI;
tel2n MODULE-IDENTITY
LAST-UPDATED "201505011057Z"
ORGANIZATION
"2N TELEKOMUNIKACE a.s."
CONTACT-INFO
"Modranska 621, 143 01 Praha 4"
DESCRIPTION
"telecommunication company"
REVISION "201505011057Z"
DESCRIPTION
"Initial version."
::= { enterprises 6530 }
-- Helios IP intercoms
heliosip OBJECT IDENTIFIER ::= { tel2n 11 }
hipProductName OBJECT-TYPE
SYNTAX OCTET STRING
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Name of product"
::= { heliosip 1 }
hipHwVersion OBJECT-TYPE
SYNTAX OCTET STRING
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Hardware version"
::= { heliosip 2 }
hipSerial OBJECT-TYPE
SYNTAX OCTET STRING (SIZE(14))
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Unique serial number"
::= { heliosip 3 }
hipVersion OBJECT-TYPE
SYNTAX OCTET STRING (SIZE(16))
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Firmware version number"
::= { heliosip 4 }
hipBootVersion OBJECT-TYPE
SYNTAX OCTET STRING
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Bootloader version number"
::= { heliosip 5 }
hipSipTable OBJECT-TYPE
SYNTAX SEQUENCE OF HipSipEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"State of SIP accounts"
::= { heliosip 6 }
hipSipEntry OBJECT-TYPE
SYNTAX HipSipEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
""
INDEX { hipIndex }
::= { hipSipTable 1 }
HipSipEntry ::= SEQUENCE {
hipIndex
Integer32,
hipPhoneNumber
OCTET STRING,
hipState
INTEGER,
hipRegistrationAt
IpAddress,
hipRegistrationTime
TimeTicks
}
hipIndex OBJECT-TYPE
SYNTAX Integer32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Identifier of SIP account"
::= { hipSipEntry 1 }
hipPhoneNumber OBJECT-TYPE
SYNTAX OCTET STRING
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Registered phone number"
::= { hipSipEntry 2 }
hipState OBJECT-TYPE
SYNTAX INTEGER {
down (0),
goingup (1),
up (2),
goingdown (3)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Current state of account"
::= { hipSipEntry 3 }
hipRegistrationAt OBJECT-TYPE
SYNTAX IpAddress
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Registrar IP address"
::= { hipSipEntry 4 }
hipRegistrationTime OBJECT-TYPE
SYNTAX TimeTicks
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Registration time"
::= { hipSipEntry 5 }
END

2198
priv/mibs/3com/A3COM-HUAWEI-DEVICE-MIB Normal file
View file

File diff suppressed because it is too large Load diff

608
priv/mibs/3com/A3COM-HUAWEI-LswDEVM-MIB Normal file
View file

@ -0,0 +1,608 @@
-- ==================================================================
-- Copyright (c) 2004-2012 Hangzhou H3C Tech. Co., Ltd. All rights reserved.
--
-- Description£º HUAWEI Lan Switch Platform Device Management MIB
-- Reference:
-- Version: V2.3
-- History:
-- V1.0 (1) Created by Hou Qiang, 2001.06.29
-- (2) Revised by Qi Zhenglin, 2001.12.30 ----r003 revision
-- V1.1 2004/7/20 import hwLswFrameIndex, hwLswSlotIndex
-- FROM A3COM-HUAWEI-DEVICE-MIB
-- V1.2 2004/09/10
-- 1) change all MIB objects' STATUS from mandatory to current.
-- 2) remove statement before hwLswdevMMib
-- 3) adjust file format, change tab to space and some small
-- changes.
-- 4) change STATUS of hwCfmWriteFlash and hwCfmEraseFlash
-- from write-only to read-write.
-- V2.0 2004-10-12 updated by gaolong
-- Import Gauge32, OBJECT-IDENTITY.
-- Relocate hwLswdevMMib MODULE-IDENTITY clause.
-- Change ACCESS to MAX-ACCESS
-- Change Gauge to Gauge32.
-- Change value of hwDevMFanStatus and hwDevMPowerStatus from underscores to hyphens.
-- V2.1 2005-01-12
-- Change the description of hwFlhTotalSize and hwFlhTotalFree by sunqiang
-- V2.2 2005-06-10 updated by Chen Xi
-- Modify the SYNTAX and DESCRIPTION of hwLinkUpDownTrapEnable
-- and adjust file format.
-- V2.3 2011-11-26 updated by duyanbing
-- Add hwDevMFirstTrapTime.
-- ==================================================================
-- ==================================================================
--
-- Varibles and types be imported
--
-- ==================================================================
A3COM-HUAWEI-LswDEVM-MIB DEFINITIONS ::= BEGIN
IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, TimeTicks, Gauge32, OBJECT-IDENTITY
FROM SNMPv2-SMI
lswCommon, huaweiUtility
FROM A3COM-HUAWEI-OID-MIB
hwLswFrameIndex, hwLswSlotIndex
FROM A3COM-HUAWEI-DEVICE-MIB
;
hwLswdevMMib MODULE-IDENTITY
LAST-UPDATED "201111260000Z"
ORGANIZATION ""
CONTACT-INFO
""
DESCRIPTION
""
REVISION "200106290000Z"
DESCRIPTION
""
::= { lswCommon 9 }
hwDevice OBJECT IDENTIFIER ::= { huaweiUtility 1 }
-- ==================================================================
--
-- ======================= definition begin =========================
--
-- ==================================================================
hwCpuTable OBJECT-TYPE
SYNTAX SEQUENCE OF HwCpuEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A table of CPU statistics."
::= { hwDevice 1 }
hwCpuEntry OBJECT-TYPE
SYNTAX HwCpuEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The Entries of hwCpuTable."
INDEX { hwCpuIndex }
::= { hwCpuTable 1 }
HwCpuEntry ::=
SEQUENCE {
hwCpuIndex INTEGER,
hwCpuCostRate Gauge32,
hwCpuCostRatePer1Min Gauge32,
hwCpuCostRatePer5Min Gauge32
}
hwCpuIndex OBJECT-TYPE
SYNTAX INTEGER
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Index of hwCpuTable. This integer is a uniq number to
identify the CPU(s). We recommand two Number Plans in this
paper, Logical Number or Phisical Number. For the first
case, hwCpuIndex is a integer, range from 1 to the Maximum
number, for example 1,2,3,4,5 ..., where 1 represents
the first CPU, 2 represents the second CPU, etc. For the
second case hwCpuIndex represents physical card position
(Shelf Number, Frame Number, Slot Number, SubSlotNumber)
where the CPU residing, for example, 0x01020304 represent
the CPU on the 4th subslot of the 3th slot of the 2nd frame
of the 1st Shelf. In the condition of multiple CPU system
where CPU group coordinately process on one board, we see
the CPUs as one CPU"
::= { hwCpuEntry 1 }
hwCpuCostRate OBJECT-TYPE
SYNTAX Gauge32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The overall CPU busy percentage in the last 5 second period. "
::= { hwCpuEntry 2 }
hwCpuCostRatePer1Min OBJECT-TYPE
SYNTAX Gauge32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The overall CPU cost percentage in the last 1 minute period. "
::= { hwCpuEntry 3 }
hwCpuCostRatePer5Min OBJECT-TYPE
SYNTAX Gauge32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The overall CPU cost percentage in the last 5 minutes period. "
::= { hwCpuEntry 4 }
hwMem OBJECT IDENTIFIER ::= { hwDevice 2 }
hwMemTable OBJECT-TYPE
SYNTAX SEQUENCE OF HwMemEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table contains memory information. "
::= { hwMem 1 }
hwMemEntry OBJECT-TYPE
SYNTAX HwMemEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The Entries of hwMemTable"
INDEX { hwMemModuleIndex }
::= { hwMemTable 1 }
HwMemEntry ::=
SEQUENCE {
hwMemModuleIndex INTEGER,
hwMemSize Gauge32,
hwMemFree Gauge32,
hwMemRawSliceUsed Gauge32,
hwMemLgFree Gauge32,
hwMemFail Gauge32,
hwMemFailNoMem Gauge32
}
hwMemModuleIndex OBJECT-TYPE
SYNTAX INTEGER
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Index of hwMemTable. This integer is a uniq number to
identify the memory module. We recommand two Number Plans
in this paper, Logical Number or Phisical Number. For the
first case, hwMemModuleIndex is a integer, range from 1 to
the Maximum number, for example 1,2,3,4,5 ..., where 1
represents the first memory module, 2 represents the second
memory module, etc. For the second case hwMemModuleIndex
represents physical card position (Shelf Number, Frame Number,
Slot Number, SubSlotNumber) where the memory module residing,
for example, 0x01020304 represent the memory module on the 4th
subslot of the 3th slot of the 2nd frame of the 1st Shelf. "
::= { hwMemEntry 1 }
hwMemSize OBJECT-TYPE
SYNTAX Gauge32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Indicates the total size of the memory module
which is on the managed object."
::= { hwMemEntry 2 }
hwMemFree OBJECT-TYPE
SYNTAX Gauge32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Indicates the free size of the memory"
::= { hwMemEntry 3 }
hwMemRawSliceUsed OBJECT-TYPE
SYNTAX Gauge32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Indicates the used size of the raw slice memory"
::= { hwMemEntry 4 }
hwMemLgFree OBJECT-TYPE
SYNTAX Gauge32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The largest free size of the contiguous area in the memory.
The unit is byte."
::= { hwMemEntry 5 }
hwMemFail OBJECT-TYPE
SYNTAX Gauge32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The times of memory allocation failures"
::= { hwMemEntry 6 }
hwMemFailNoMem OBJECT-TYPE
SYNTAX Gauge32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The times of memory allocation failures due to no free memory."
::= { hwMemEntry 7 }
hwBufTable OBJECT-TYPE
SYNTAX SEQUENCE OF HwBufEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table contains buffer information. "
::= { hwMem 2 }
hwBufEntry OBJECT-TYPE
SYNTAX HwBufEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The Entries of hwBufferTable"
INDEX { hwBufModuleIndex , hwBufSize }
::= { hwBufTable 1 }
HwBufEntry ::=
SEQUENCE {
hwBufModuleIndex INTEGER,
hwBufSize INTEGER,
hwBufCurrentTotal Gauge32,
hwBufCurrentUsed Gauge32
}
hwBufModuleIndex OBJECT-TYPE
SYNTAX INTEGER
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Index of hwBufferTable. This integer is a uniq number to
identify the buffer module. We recommand two Number Plans
in this paper, Logical Number or Phisical Number. For the
first case, hwBufferModuleIndex is a integer, range from 1 to
the Maximum number, for example 1,2,3,4,5 ..., where 1
represents the first buffer module, 2 represents the second
buffer module, etc. For the second case hwBufferModuleIndex
represents physical card position (Shelf Number, Frame Number,
Slot Number, SubSlotNumber) where the buffer module residing,
for example, 0x01020304 represent the buffer module on the 4th
subslot of the 3th slot of the 2nd frame of the 1st Shelf. "
::= { hwBufEntry 1 }
hwBufSize OBJECT-TYPE
SYNTAX INTEGER
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The size of buffer,unit is byte."
::= { hwBufEntry 2 }
hwBufCurrentTotal OBJECT-TYPE
SYNTAX Gauge32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The total number of buffer currently."
::= { hwBufEntry 3 }
hwBufCurrentUsed OBJECT-TYPE
SYNTAX Gauge32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of used buffer currently."
::= { hwBufEntry 4 }
hwFlh OBJECT IDENTIFIER ::= { hwDevice 3 }
-- huawei Local Flash Group
-- This group is present in all products which contain flash"
hwFlhTotalSize OBJECT-TYPE
SYNTAX INTEGER
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The flash memory's total size, in kilobyte"
::= { hwFlh 1 }
hwFlhTotalFree OBJECT-TYPE
SYNTAX INTEGER
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The free space in internal flash memory, in kilobyte"
::= { hwFlh 2 }
hwFlhLastDelTime OBJECT-TYPE
SYNTAX TimeTicks
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The time since system up of the lastest deleting operation of
flash memory.The value of Zero indicates there is no erasing operation
since system up"
DEFVAL { 0 }
::= { hwFlh 3 }
hwFlhDelState OBJECT-TYPE
SYNTAX INTEGER {
executing(1),
ok(2),
error(3),
readOnly(4),
failtoopen(5),
blockMallocFail(6),
noneDelOperationSinceStart(7)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The state indicates the result of current or
lastest flash memory deleting operation"
::= { hwFlh 4 }
hwFlhState OBJECT-TYPE
SYNTAX INTEGER {
busy(1),
free(2)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Busy indicates the flash memory is unavailable due to others may be using it,
and free indicates the flash memory is available now"
::= { hwFlh 5 }
-- ==================================================================
hwLswdevMMibObject OBJECT-IDENTITY
STATUS current
DESCRIPTION
"Description."
::= { hwLswdevMMib 1 }
hwdevMFanStatusTable OBJECT-TYPE
SYNTAX SEQUENCE OF HwDevMFanStatusEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION " Fan status description table "
::= { hwLswdevMMibObject 1 }
hwdevMFanStatusEntry OBJECT-TYPE
SYNTAX HwDevMFanStatusEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION " Fan status description table entry "
INDEX { hwDevMFanNum }
::= { hwdevMFanStatusTable 1}
HwDevMFanStatusEntry ::=
SEQUENCE {
hwDevMFanNum INTEGER,
hwDevMFanStatus INTEGER
}
hwDevMFanNum OBJECT-TYPE
SYNTAX INTEGER
MAX-ACCESS read-only
STATUS current
DESCRIPTION " Fan number "
::= { hwdevMFanStatusEntry 1 }
hwDevMFanStatus OBJECT-TYPE
SYNTAX INTEGER
{
active (1),
deactive (2),
not-install (3),
unsupport (4)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION " Fan status: active (1), deactive (2) not installed (3) and unsupported (4)"
::= { hwdevMFanStatusEntry 2 }
hwdevMPowerStatusTable OBJECT-TYPE
SYNTAX SEQUENCE OF HwDevMPowerStatusEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION " Power status description table "
::= { hwLswdevMMibObject 2 }
hwdevMPowerStatusEntry OBJECT-TYPE
SYNTAX HwDevMPowerStatusEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION " Power status description table entry "
INDEX { hwDevMPowerNum }
::= { hwdevMPowerStatusTable 1}
HwDevMPowerStatusEntry ::=
SEQUENCE {
hwDevMPowerNum INTEGER,
hwDevMPowerStatus INTEGER
}
hwDevMPowerNum OBJECT-TYPE
SYNTAX INTEGER
MAX-ACCESS read-only
STATUS current
DESCRIPTION "Power number "
::= { hwdevMPowerStatusEntry 1 }
hwDevMPowerStatus OBJECT-TYPE
SYNTAX INTEGER
{
active (1),
deactive (2),
not-install (3),
unsupport (4)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION " Power status: active (1), deactive (2) not installed (3) and unsupported "
::= { hwdevMPowerStatusEntry 2 }
hwdevMSlotEnvironmentTable OBJECT-TYPE
SYNTAX SEQUENCE OF HwdevMSlotEnvironmentEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION " environment description table "
::= { hwLswdevMMibObject 3 }
hwdevMSlotEnvironmentEntry OBJECT-TYPE
SYNTAX HwdevMSlotEnvironmentEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION " environment description table entry "
INDEX { hwLswFrameIndex, hwLswSlotIndex, hwdevMSlotEnvironmentType }
::= { hwdevMSlotEnvironmentTable 1 }
HwdevMSlotEnvironmentEntry ::=
SEQUENCE {
hwdevMSlotEnvironmentType INTEGER,
hwDevMSlotEnvironmentStatus INTEGER,
hwDevMSlotEnvironmentValue INTEGER,
hwDevMSlotEnvironmentUpperLimit INTEGER,
hwDevMSlotEnvironmentLowerLimit INTEGER
}
hwdevMSlotEnvironmentType OBJECT-TYPE
SYNTAX INTEGER
{
temperature(1),
humidity(2),
fog(3)
}
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION "Environment type "
::= { hwdevMSlotEnvironmentEntry 1 }
hwDevMSlotEnvironmentStatus OBJECT-TYPE
SYNTAX INTEGER
{
normal(1),
upper(2),
lower(3)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION " Environment status"
::= { hwdevMSlotEnvironmentEntry 2 }
hwDevMSlotEnvironmentValue OBJECT-TYPE
SYNTAX INTEGER
MAX-ACCESS read-only
STATUS current
DESCRIPTION " Environment value"
::= { hwdevMSlotEnvironmentEntry 3 }
hwDevMSlotEnvironmentUpperLimit OBJECT-TYPE
SYNTAX INTEGER
MAX-ACCESS read-write
STATUS current
DESCRIPTION "Environment upper limit "
::= { hwdevMSlotEnvironmentEntry 4 }
hwDevMSlotEnvironmentLowerLimit OBJECT-TYPE
SYNTAX INTEGER
MAX-ACCESS read-write
STATUS current
DESCRIPTION " Environment Lower limit"
::= { hwdevMSlotEnvironmentEntry 5 }
hwLinkUpDownTrapEnable OBJECT-TYPE
SYNTAX INTEGER
{
enableBoth(1) ,
disableBoth(2) ,
enableLinkUpTrapOnly(3) ,
enableLinkDownTrapOnly(4)
}
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Enable/Disable linkUp/linkDown traps of the device, determining whether
to enable linkUp/linkDown traps with that of the interface.
When the value is enableBoth(1), the linkUp/linkDown traps are both
enabled.
When the value is disableBoth(2), the linkUp/linkDown traps are both
disabled.
When the value is enableLinkUpTrapOnly(3), the linkUp traps is enabled
and the linkDown traps is disabled.
When the value is enableLinkDownTrapOnly(4), the linkUp traps is
disabled and the linkDown traps is enabled. "
::= { hwLswdevMMibObject 9 }
hwdot1qTpFdbLearnStatus OBJECT-TYPE
SYNTAX INTEGER
{
enabled(1),
disabled(2)
}
MAX-ACCESS read-write
STATUS current
DESCRIPTION " Enable/Disable the address learning."
::= { hwLswdevMMibObject 10 }
hwCfmWriteFlash OBJECT-TYPE
SYNTAX INTEGER
{
write(1)
}
MAX-ACCESS read-write
STATUS current
DESCRIPTION " Write the current effective configuration into the Flash memory.
This object does not support read operation."
::= { hwLswdevMMibObject 11 }
hwCfmEraseFlash OBJECT-TYPE
SYNTAX INTEGER
{
erase(1)
}
MAX-ACCESS read-write
STATUS current
DESCRIPTION " Delete the configuration from the Flash memory.
This object does not support read operation."
::= { hwLswdevMMibObject 12 }
hwDevMFirstTrapTime OBJECT-TYPE
SYNTAX TimeTicks
MAX-ACCESS accessible-for-notify
STATUS current
DESCRIPTION
"Represents the first trap time."
::= { hwLswdevMMibObject 13 }
END

253
priv/mibs/3com/A3COM-HUAWEI-OID-MIB Normal file
View file

@ -0,0 +1,253 @@
-- =================================================================
-- Copyright (c) 2004-2012 Hangzhou H3C Tech. Co., Ltd. All rights reserved.
--
-- Description:The H3C root mib
-- Reference:
-- Version: V1.70
-- History:
-- V1.0 2004-08-05 Initial version, created by gaolong.
-- V1.22 add MIB identifier
-- 'h3cVoiceVlan'
-- 'h3cL4Redirect'
-- 'h3cUser', 'h3cRadius'
-- 'h3cPowerEthernetExt'
-- 'h3cEntityRelation'
-- 'h3cProtocolVlan'
-- 'h3cQosProfile'
-- V1.23 add MIB identifier
-- 'hwQoS'
-- V1.3 2004-10-12 updated by gaolong
-- add MIB identifier 'rmonExtend'
-- V1.31 2004-10-23 updated by gaolong
-- add 'h3cEntityVendorTypeOID', 'dlsw', 'hwpaeExtMib', 'hwDevice', 'h3cNat',
-- 'h3cPos', subnode 20 under h3cCommon, 'voice', object identifiers.
-- V1.32 2004-11-8 update by xiejianping
-- add 'h3cAAL5' and 'h3cSSH';
-- V1.33 2004-11-10 update by xiejianping
-- add 'h3cRSA';
-- V1.34 2004-12-12 updated by gaolong
-- add h3cVrrpExt, h3cIpa, h3cPortSecurity, h3cVpls, h3cE1,
-- h3cT1, h3cIkeMonitor
-- V1.35 2004-12-25 updated by gaolong
-- add 'h3cIfExt', 'h3cWebSwitch', 'h3cAutoDetect', 'h3cIpBroadcast',
-- and 'h3cIpx'.
-- V1.36 2005-03-10 updated by gaolong
-- modify 'h3cIkeMonitor' to 'h3cIKEMonitor' by gaolong
-- add 'h3cDldp' and 'h3cRrpp'
-- V1.37 2005-03-29 updated by gaolong
-- modify object name for IPSec monitor
-- V1.38 2005-05-03 updated by gaolong
-- add 'h3cVoice', 'h3cRcr', 'h3cAtmDxi', 'h3cDomain', 'h3cUnicast', 'h3cTrap',
-- 'h3cDhcpSnoop', 'h3cIPS', 'h3cProtocolPriority', 'h3cEpon', 'h3cCfCard',
-- and 'h3cIds'
-- V1.39 2005/5/25 add 'h3cMulticast' and 'h3cMpm' by gaolong
-- change name of subnode 20 under h3cCommon to 'h3cNS'
-- V1.40 2005/6/25 updated by gaolong
-- add 'h3cOadp', 'h3cTunnel', 'h3cGre', 'h3cObjectInfo', 'h3cDvpn'
-- and 'h3cDhcpRelay' by gaolong
-- V1.41 2005/7/9 add 'h3cIsis' by gaolong
-- V1.42 2005/8/2 add 'h3cRpr' by gaolong
-- V1.43 2005/9/2 add 'h3cSubnetVlan' by gaolong
-- V1.44 2005/9/20 add 'h3cDlswExt', 'h3cSyslog' by gaolong
-- V1.45 2005/10/29 remove 'voice' for confliction with 3Com MIB by longyin
-- V1.46 2005/12/02 add 'h3cFlowTemplate' and 'h3cQos2' under 'h3cCommon',
-- add 'h3cSNMPAgCpb' under 'h3c',
-- add subidentifier 'h3cQosCapability' of 'h3cSNMPAgCpb',
-- add subidentifier 'h3cIfQos2' and 'h3cCBQos2' of 'h3cQos2',
-- add 'h3cStormConstrain' by longyin
-- V1.47 2006/01/09 add 'h3cIpAddrMIB' by longyin
-- V1.48 2006/01/21 add 'h3cMirrGroup' by longyin
-- V1.49 2006/03/05 add 'h3cQINQ' by longyin
-- V1.50 2006/04/06 add 'h3cTransceiver', 'h3cIpv6AddrMIB' by gaolong
-- V1.51 2006/06/14 add 'h3cBfdMIB' by longyin
-- V1.52 2006/11/25 add 'h3cRCP' by gaolong
-- V1.53 2007/01/11 add 'h3cAcfp' by gaolong
-- V1.54 2007/01/24 add 'h3cDot11' by gaolong
-- V1.55 2007/05/15 add 'h3cE1T1VI' by gaolong
-- V1.56 2007/07/10 add 'h3cwapiMIB', "h3cL2VpnPwe3", "h3cMplsOam"
-- and "h3cMplsOamPs" by gaolong
-- V1.57 2007/08/09 add 'h3cSiemMib' by gaolong
-- V1.58 2007/12/27 add 'h3cAFC' and 'h3cMultCDR' by longyin
-- V1.59 2008/02/27 add 'h3cMACInformation', 'h3cFireWall', 'h3cDSP' by longyin
-- V1.60 2008/04/29 add 'h3cNetMan' by songhao
-- V1.61 2008/06/02 add 'h3cStack', 'h3cPosa' by songhao
-- V1.62 2008/07/29 add 'h3cWebAuthentication' by songhao
-- V1.63 2008/12/03 add 'h3cLpbkdt' by songhao
-- V1.64 2009/02/27 add 'h3cMultiMedia', 'h3cDns', 'h3c3GModem'
-- and 'h3cPortal' by songhao
-- V1.65 2009/05/18 add 'h3clldp','h3cDHCPServer','h3cPPPoEServer','h3cL2Isolate',
-- 'h3cSnmpExt' by duyanbing
-- V1.66 2009/11/04 add 'h3cVsi','h3cEvc','h3cMinm','h3cblg','h3cRS485' by shuaixiaojuan
-- V1.67 2010/03/16 add 'h3cARPRatelimit', 'h3cLI' by songhao
-- V1.68 2011/01/31 add 'h3cDar', 'h3cPBR' by songhao
-- V1.69 2011/04/22 add 'h3cAAANasId' by duyanbing
-- V1.70 2012/04/19 add 'h3cTeTunnel','h3cLB','h3cDldp2','h3cWIPS','h3cFCoE' by duyanbing
-- =================================================================
A3COM-HUAWEI-OID-MIB DEFINITIONS ::= BEGIN
IMPORTS
enterprises
FROM RFC1155-SMI;
-- level 1 under .enterprises
a3Com OBJECT IDENTIFIER ::= { enterprises 43 }
jv-mib OBJECT IDENTIFIER ::= { a3Com 45 }
huawei OBJECT IDENTIFIER ::= { jv-mib 1 }
-- level 2 under .huawei
hwLocal OBJECT IDENTIFIER ::= { huawei 1 }
hwproducts OBJECT IDENTIFIER ::= { huawei 2 }
huaweiMgmt OBJECT IDENTIFIER ::= { huawei 5 }
huaweiUtility OBJECT IDENTIFIER ::= { huawei 6 }
h3c OBJECT IDENTIFIER ::= { huawei 10 }
-- level 3
hwInternetProtocol OBJECT IDENTIFIER ::= { hwLocal 3 }
router OBJECT IDENTIFIER ::= { hwproducts 2 }
lanSw OBJECT IDENTIFIER ::= { hwproducts 23 }
mlsr OBJECT IDENTIFIER ::= { hwproducts 33 }
dlsw OBJECT IDENTIFIER ::= { hwproducts 34 } -- Reference: huawei-dlsw.mib
hwDhcp OBJECT IDENTIFIER ::= { huaweiMgmt 7 }
hwMpls OBJECT IDENTIFIER ::= { huaweiMgmt 12 }
hwpaeExtMib OBJECT IDENTIFIER ::= { huaweiMgmt 22 } -- Reference: huawei-8021x-ext.mib
huaweiDatacomm OBJECT IDENTIFIER ::= { huaweiMgmt 25 }
hwDevice OBJECT IDENTIFIER ::= { huaweiUtility 1 } -- Reference: huawei-splat-devm.mib
-- under h3c
h3cCommon OBJECT IDENTIFIER ::= { h3c 2 } -- 2004/1/12, xiejianping changed
h3cEntityVendorTypeOID OBJECT IDENTIFIER ::= { h3c 3 } -- 2004/5/18, xiejianping added
hwSystem OBJECT IDENTIFIER ::= { h3c 6 } -- 2004/4/24, xiejianping changed
h3cSNMPAgCpb OBJECT IDENTIFIER ::= { h3c 7 } -- 2005/11/27, longyin added, for capability MIBs
vrpProtocol OBJECT IDENTIFIER ::= { hwInternetProtocol 3 }
rmonExtend OBJECT IDENTIFIER ::= { hwInternetProtocol 4 }
-- under lanSw
lswCommon OBJECT IDENTIFIER ::= { lanSw 1 }
-- remove 'voice' for confliction of 3Com
-- voice OBJECT IDENTIFIER ::= { huaweiDatacomm 1 }
hwQoS OBJECT IDENTIFIER ::= { huaweiDatacomm 32 }
h3cFtm OBJECT IDENTIFIER ::= { h3cCommon 1 }
h3cUIMgt OBJECT IDENTIFIER ::= { h3cCommon 2 }
h3cEntityExtend OBJECT IDENTIFIER ::= { h3cCommon 6 }
h3cIPSecMonitor OBJECT IDENTIFIER ::= { h3cCommon 7 }
h3cAcl OBJECT IDENTIFIER ::= { h3cCommon 8 }
h3cVoiceVlan OBJECT IDENTIFIER ::= { h3cCommon 9 }
h3cL4Redirect OBJECT IDENTIFIER ::= { h3cCommon 10 }
h3cUser OBJECT IDENTIFIER ::= { h3cCommon 12 }
h3cRadius OBJECT IDENTIFIER ::= { h3cCommon 13 }
h3cPowerEthernetExt OBJECT IDENTIFIER ::= { h3cCommon 14 }
h3cEntityRelation OBJECT IDENTIFIER ::= { h3cCommon 15 }
h3cProtocolVlan OBJECT IDENTIFIER ::= { h3cCommon 16 }
h3cQosProfile OBJECT IDENTIFIER ::= { h3cCommon 17 }
h3cNat OBJECT IDENTIFIER ::= { h3cCommon 18 }
h3cPos OBJECT IDENTIFIER ::= { h3cCommon 19 }
h3cNS OBJECT IDENTIFIER ::= { h3cCommon 20 }
h3cAAL5 OBJECT IDENTIFIER ::= { h3cCommon 21 }
h3cSSH OBJECT IDENTIFIER ::= { h3cCommon 22 }
h3cRSA OBJECT IDENTIFIER ::= { h3cCommon 23 }
h3cVrrpExt OBJECT IDENTIFIER ::= { h3cCommon 24 }
h3cIpa OBJECT IDENTIFIER ::= { h3cCommon 25 }
h3cPortSecurity OBJECT IDENTIFIER ::= { h3cCommon 26 }
h3cVpls OBJECT IDENTIFIER ::= { h3cCommon 27 }
h3cE1 OBJECT IDENTIFIER ::= { h3cCommon 28 }
h3cT1 OBJECT IDENTIFIER ::= { h3cCommon 29 }
h3cIKEMonitor OBJECT IDENTIFIER ::= { h3cCommon 30 }
h3cWebSwitch OBJECT IDENTIFIER ::= { h3cCommon 31 }
h3cAutoDetect OBJECT IDENTIFIER ::= { h3cCommon 32 }
h3cIpBroadcast OBJECT IDENTIFIER ::= { h3cCommon 33 }
h3cIpx OBJECT IDENTIFIER ::= { h3cCommon 34 }
h3cIPS OBJECT IDENTIFIER ::= { h3cCommon 35 }
h3cDhcpSnoop OBJECT IDENTIFIER ::= { h3cCommon 36 }
h3cProtocolPriority OBJECT IDENTIFIER ::= { h3cCommon 37 }
h3cTrap OBJECT IDENTIFIER ::= { h3cCommon 38 }
h3cVoice OBJECT IDENTIFIER ::= { h3cCommon 39 }
h3cIfExt OBJECT IDENTIFIER ::= { h3cCommon 40 }
h3cCfCard OBJECT IDENTIFIER ::= { h3cCommon 41 }
h3cEpon OBJECT IDENTIFIER ::= { h3cCommon 42 }
h3cDldp OBJECT IDENTIFIER ::= { h3cCommon 43 }
h3cUnicast OBJECT IDENTIFIER ::= { h3cCommon 44 }
h3cRrpp OBJECT IDENTIFIER ::= { h3cCommon 45 }
h3cDomain OBJECT IDENTIFIER ::= { h3cCommon 46 }
h3cIds OBJECT IDENTIFIER ::= { h3cCommon 47 }
h3cRcr OBJECT IDENTIFIER ::= { h3cCommon 48 }
h3cAtmDxi OBJECT IDENTIFIER ::= { h3cCommon 49 }
h3cMulticast OBJECT IDENTIFIER ::= { h3cCommon 50 }
h3cMpm OBJECT IDENTIFIER ::= { h3cCommon 51 }
h3cOadp OBJECT IDENTIFIER ::= { h3cCommon 52 }
h3cTunnel OBJECT IDENTIFIER ::= { h3cCommon 53 }
h3cGre OBJECT IDENTIFIER ::= { h3cCommon 54 }
h3cObjectInfo OBJECT IDENTIFIER ::= { h3cCommon 55 }
h3cDvpn OBJECT IDENTIFIER ::= { h3cCommon 57 }
h3cDhcpRelay OBJECT IDENTIFIER ::= { h3cCommon 58 }
h3cIsis OBJECT IDENTIFIER ::= { h3cCommon 59 }
h3cRpr OBJECT IDENTIFIER ::= { h3cCommon 60 }
h3cSubnetVlan OBJECT IDENTIFIER ::= { h3cCommon 61 }
h3cDlswExt OBJECT IDENTIFIER ::= { h3cCommon 62 }
h3cSyslog OBJECT IDENTIFIER ::= { h3cCommon 63 }
h3cFlowTemplate OBJECT IDENTIFIER ::= { h3cCommon 64 }
h3cQos2 OBJECT IDENTIFIER ::= { h3cCommon 65 }
h3cStormConstrain OBJECT IDENTIFIER ::= { h3cCommon 66 }
h3cIpAddrMIB OBJECT IDENTIFIER ::= { h3cCommon 67 }
h3cMirrGroup OBJECT IDENTIFIER ::= { h3cCommon 68 }
h3cQINQ OBJECT IDENTIFIER ::= { h3cCommon 69 }
h3cTransceiver OBJECT IDENTIFIER ::= { h3cCommon 70 }
h3cIpv6AddrMIB OBJECT IDENTIFIER ::= { h3cCommon 71 }
h3cBfdMIB OBJECT IDENTIFIER ::= { h3cCommon 72 }
h3cRCP OBJECT IDENTIFIER ::= { h3cCommon 73 }
h3cAcfp OBJECT IDENTIFIER ::= { h3cCommon 74 }
h3cDot11 OBJECT IDENTIFIER ::= { h3cCommon 75 }
h3cE1T1VI OBJECT IDENTIFIER ::= { h3cCommon 76 }
h3cwapiMIB OBJECT IDENTIFIER ::= { h3cCommon 77 }
h3cL2VpnPwe3 OBJECT IDENTIFIER ::= { h3cCommon 78 }
h3cMplsOam OBJECT IDENTIFIER ::= { h3cCommon 79 }
h3cMplsOamPs OBJECT IDENTIFIER ::= { h3cCommon 80 }
h3cSiemMib OBJECT IDENTIFIER ::= { h3cCommon 81 }
h3cAFC OBJECT IDENTIFIER ::= { h3cCommon 85 }
h3cMultCDR OBJECT IDENTIFIER ::= { h3cCommon 86 }
h3cMACInformation OBJECT IDENTIFIER ::= { h3cCommon 87 }
h3cFireWall OBJECT IDENTIFIER ::= { h3cCommon 88 }
h3cDSP OBJECT IDENTIFIER ::= { h3cCommon 89 }
h3cNetMan OBJECT IDENTIFIER ::= { h3cCommon 90 }
h3cStack OBJECT IDENTIFIER ::= { h3cCommon 91 }
h3cPosa OBJECT IDENTIFIER ::= { h3cCommon 92 }
h3cWebAuthentication OBJECT IDENTIFIER ::= { h3cCommon 93 }
h3cLpbkdt OBJECT IDENTIFIER ::= { h3cCommon 95 }
h3cMultiMedia OBJECT IDENTIFIER ::= { h3cCommon 96 }
h3cDns OBJECT IDENTIFIER ::= { h3cCommon 97 }
h3c3GModem OBJECT IDENTIFIER ::= { h3cCommon 98 }
h3cPortal OBJECT IDENTIFIER ::= { h3cCommon 99 }
h3clldp OBJECT IDENTIFIER ::= { h3cCommon 100 }
h3cDHCPServer OBJECT IDENTIFIER ::= { h3cCommon 101 }
h3cPPPoEServer OBJECT IDENTIFIER ::= { h3cCommon 102 }
h3cL2Isolate OBJECT IDENTIFIER ::= { h3cCommon 103 }
h3cSnmpExt OBJECT IDENTIFIER ::= { h3cCommon 104 }
h3cVsi OBJECT IDENTIFIER ::= { h3cCommon 105 }
h3cEvc OBJECT IDENTIFIER ::= { h3cCommon 106 }
h3cMinm OBJECT IDENTIFIER ::= { h3cCommon 107 }
h3cBlg OBJECT IDENTIFIER ::= { h3cCommon 108 }
h3cRS485 OBJECT IDENTIFIER ::= { h3cCommon 109 }
h3cARPRatelimit OBJECT IDENTIFIER ::= { h3cCommon 110 }
h3cLI OBJECT IDENTIFIER ::= { h3cCommon 111 }
h3cDar OBJECT IDENTIFIER ::= { h3cCommon 112 }
h3cPBR OBJECT IDENTIFIER ::= { h3cCommon 113 }
h3cAAANasId OBJECT IDENTIFIER ::= { h3cCommon 114 }
h3cTeTunnel OBJECT IDENTIFIER ::= { h3cCommon 115 }
h3cLB OBJECT IDENTIFIER ::= { h3cCommon 116 }
h3cDldp2 OBJECT IDENTIFIER ::= { h3cCommon 117 }
h3cWIPS OBJECT IDENTIFIER ::= { h3cCommon 118 }
h3cFCoE OBJECT IDENTIFIER ::= { h3cCommon 120 }
-- under h3c.h3cSNMPAgCpb
h3cQosCapability OBJECT IDENTIFIER ::= { h3cSNMPAgCpb 1 }
-- under h3c.h3cCommon.h3cQos2
h3cIfQos2 OBJECT IDENTIFIER ::= { h3cQos2 1 }
h3cCBQos2 OBJECT IDENTIFIER ::= { h3cQos2 2 }
END

87
priv/mibs/3com/A3COM0004-GENERIC Normal file
View file

@ -0,0 +1,87 @@
-- **********************************************************************
--
-- Name: 3Com ESD Generic MIB branches
--
-- Description:
-- This is the register for all MIB branches under a3com.generic.
-- These MIB branches are declared in the source file:
-- /vobs/shelf/gma/gmi/bdn.mib
--
-- This document is currently maintained by:
-- Les Bell Les_Bell@3Com.com 4-400-8025
--
-- History Date Reason for Change
--
-- 1.00 1997 Issued as 3Com RFC.
-- some history was lost
-- 1.50 17 March 00 Added branch for qos
-- 1.60 23 Oct 00 Added branch for L4 Re-direction
-- ================================
-- YY/MM/DD Author Comments
-- ================================
-- 01/12/06 EL Bell Added a3ComTrafficStats {41} a3ComRadiusMIB {42}
-- 01/12/11 P Biti Added a3ComBackup-mib { 43}
-- 02/04/30 EL Bell Added a3comLicenseGroup {44}
-- 02/09/30 EL Bell Added a3ComPowerEthernetExt {45}
-- 03/02/06 EL Bell Added a3ComQBridgeMIB {46}
-- 03/02/14 EL Bell Added a3ComFabric {47}
-- 03/06/13 EL Bell Added a3ComLinkAgg {48}
-- 03/12/22 EL Bell Added a3ComPaeMIB {49} + a3ComSntpGroup {50}
-- **********************************************************************
-- Copyright (c) 3Com Corporation. All Rights Reserved.
-- **********************************************************************
A3COM0004-GENERIC DEFINITIONS ::= BEGIN
IMPORTS generic FROM A3Com-products-MIB ;
setup OBJECT IDENTIFIER ::= {generic 2}
sysLoader OBJECT IDENTIFIER ::= {generic 3}
security OBJECT IDENTIFIER ::= {generic 4}
gauges OBJECT IDENTIFIER ::= {generic 5}
asciiAgent OBJECT IDENTIFIER ::= {generic 6}
serialIf OBJECT IDENTIFIER ::= {generic 7}
repeaterMgmt OBJECT IDENTIFIER ::= {generic 8}
endStation OBJECT IDENTIFIER ::= {generic 9}
localSnmp OBJECT IDENTIFIER ::= {generic 10}
manager OBJECT IDENTIFIER ::= {generic 11}
unusedGeneric12 OBJECT IDENTIFIER ::= {generic 12}
chassis OBJECT IDENTIFIER ::= {generic 14}
mrmResilience OBJECT IDENTIFIER ::= {generic 15}
tokenRing OBJECT IDENTIFIER ::= {generic 16}
multiRepeater OBJECT IDENTIFIER ::= {generic 17}
bridgeMgmt OBJECT IDENTIFIER ::= {generic 18}
fault OBJECT IDENTIFIER ::= {generic 19}
poll OBJECT IDENTIFIER ::= {generic 20}
powerSupply OBJECT IDENTIFIER ::= {generic 21}
securePort OBJECT IDENTIFIER ::= {generic 22}
alertLed OBJECT IDENTIFIER ::= {generic 23}
remoteControl OBJECT IDENTIFIER ::= {generic 24}
rmonExtensions OBJECT IDENTIFIER ::= {generic 25}
rfc1516extensions OBJECT IDENTIFIER ::= {generic 26}
superStackIIconfig OBJECT IDENTIFIER ::= {generic 27}
extendedIfInfo OBJECT IDENTIFIER ::= {generic 28}
a3ComVlan OBJECT IDENTIFIER ::= {generic 29}
vlanServerClient OBJECT IDENTIFIER ::= {generic 30}
segmentLoadBalancing OBJECT IDENTIFIER ::= {generic 31}
virtualFileSystem OBJECT IDENTIFIER ::= {generic 32}
smartAutosensing OBJECT IDENTIFIER ::= {generic 33}
brasica2 OBJECT IDENTIFIER ::= {generic 34}
smaVlanSupport OBJECT IDENTIFIER ::= {generic 35}
a3ComBridgeExt OBJECT IDENTIFIER ::= {generic 36}
igmpMIB OBJECT IDENTIFIER ::= {generic 37}
mibSummary OBJECT IDENTIFIER ::= {generic 38}
qosProfiles OBJECT IDENTIFIER ::= {generic 39}
l4Redirect OBJECT IDENTIFIER ::= {generic 40}
a3ComTrafficStats OBJECT IDENTIFIER ::= {generic 41}
a3ComRadiusMIB OBJECT IDENTIFIER ::= {generic 42}
a3ComBackup-mib OBJECT IDENTIFIER ::= {generic 43}
a3comLicenseGroup OBJECT IDENTIFIER ::= {generic 44} -- 3FC-485
a3ComPowerEthernetExt OBJECT IDENTIFIER ::= {generic 45} -- 3FC-484
a3ComQBridgeMIB OBJECT IDENTIFIER ::= {generic 46} -- 3FC-493
a3ComFabric OBJECT IDENTIFIER ::= {generic 47} -- 3FC-491
a3ComLinkAgg OBJECT IDENTIFIER ::= {generic 48} -- 3FC-490
a3ComPaeMIB OBJECT IDENTIFIER ::= {generic 49}
a3ComSntpGroup OBJECT IDENTIFIER ::= {generic 50} -- 3FC-515
END

678
priv/mibs/3com/A3COM0352-STACK-CONFIG Normal file
View file

@ -0,0 +1,678 @@
--
-- Name: 3Com SuperStack II Stack Configuration MIB
--
-- Description:
--
-- This is an updated version of 3Com RFC 0017. Additional
-- functionality added since 3Com RFC 0017 is as follows:
-- (1) A notepad facility which allows the device to store a 512
-- character DisplayString.
-- (2) A column for the unit's product number.
-- (3) A Unit Departure Trap.
--
--
-- This MIB is used to publicise the units in the stack. The information
-- is represented by two tables. Both tables are indexed by a simple
-- location index. The convention is that the lower numbered units are
-- at the bottom of the stack. This index will generally NOT be sparse,
-- but management applications CANNOT rely on this. Different
-- technologies can be used to detect stack position and those
-- technologies may or may not detect units that are not powered. Matrix
-- technologies may allocate a fixed unit number to the cables that
-- connect them to the units in the stack. Depending upon the wiring,
-- the index for matrix inter-connected stacks may be sparse. The agents
-- reporting this information are allowed to implement this index in a
-- sparse fashion.
--
-- Note that the position in the stack, and hence the position in these
-- tables can change as various units in the stack are switched on and
-- off. Because a unit is indexed in this table as row 2, it should NOT
-- be assumed that unit will continue to remain at location 2. If an
-- application wishes to uniquely tag information for a particular unit
-- in the stack, that unit should be identified by its MAC address.
--
-- Note also that not all values will be available for all units. In
-- this case those objects that are not supported may return
-- NO-SUCH-NAME or a default value. Management applications must be
-- aware of this and take appropriate actions. It should be noted that
-- units which support the earlier RFC (0017) will not support the
-- stackUnitNotepad object since it has been added by this MIB.
--
--
-- History Date Reason for Change
--
-- 1.00 Jan 1999 Created from 3Com RFC 0017.
-- The stackUnitNotepad object has been added.
-- The stackAddressTable is read-only.
-- 1.01 May 1999 Added missing import of TimeTicks.
-- Made stackUnitNotepad an OCTET STRING since
-- DisplayStrings are not allowed to be greater
-- than 255 octets in length.
-- 1.02 Dec 1999 Added stackUnitProductNumber column to the
-- stackConfigTable object
-- 1.03 March 2000 Added Unit Departure Trap.
-- 1.04 April 2001 Added latest stackUnitCapability enumerations.
-- 2.01 May 2002 Added stackUnitAutoReboot and
-- stackBankSwapTable.
-- 2.02 Oct 2002 Added unitAwaitReset to stackUnitState.
-- 2.03 Jan 2003 Added latest stackUnitCapability enumerations:
-- PoE (0x31) and OSPF (0x32)
-- 2.04 Mar 2003 Fixed format error
-- 2.05 Apr 03,2003 Added stackUnitCapability enumerations:
-- Trusted IP(0x33),Secure Shell(0x34),
-- Configurable management VLAN(0x35)
-- 2.06 Apr 16,2003 Added stackUnitCapability enumeration:
-- Manual L4 cache configuration
-- 2.07 May 23,2003 Added stpIgnoreCapability
-- 2.08 March 1,2004 Added for Hoover
-- MAC-address Based Network Access (56) This indicates that the device supports MAC-address Based Network Access.
-- Simple Network Time Protocol Client (57) This indicates that the device supports the Simple Network Time Protocol Client.
-- System Logger (58) This indicates that the device supports System Log.
-- IGMP V3 (59) - This indicates that the device supports IGMP V3.
-- *********************************************************************
-- Copyright (c) 3Com Corporation. All Rights Reserved.
-- *********************************************************************
A3COM0352-STACK-CONFIG DEFINITIONS ::= BEGIN
IMPORTS
superStackIIconfig FROM A3COM0004-GENERIC
PhysAddress, DisplayString FROM RFC1213-MIB
OBJECT-TYPE FROM RFC-1212
TRAP-TYPE FROM RFC-1215
TimeTicks FROM SNMPv2-SMI
;
-- *********************************************************************
-- This is the main configuration table. It is indexed on the unit
-- location within the stack. Not all objects in this table will be
-- applicable to every device type and the table rows may be sparse.
-- *********************************************************************
stackConfiguration OBJECT IDENTIFIER ::= {superStackIIconfig 1}
stackConfigTable OBJECT-TYPE
SYNTAX SEQUENCE OF StackConfigEntry
ACCESS not-accessible
STATUS mandatory
DESCRIPTION "The main table of configuration data."
::= {stackConfiguration 1}
stackConfigEntry OBJECT-TYPE
SYNTAX StackConfigEntry
ACCESS not-accessible
STATUS mandatory
DESCRIPTION "The configuration entry for a unit in the stack."
INDEX {stackUnitLocation}
::= {stackConfigTable 1}
StackConfigEntry ::= SEQUENCE {
stackUnitLocation INTEGER,
stackUnitAddress PhysAddress,
stackUnitLastReset TimeTicks,
stackUnitType INTEGER,
stackUnitDesc DisplayString,
stackUnitName DisplayString (SIZE(0..30)),
stackUnitState INTEGER,
stackUnitManagementType INTEGER,
stackUnitCapabilities OCTET STRING ,
stackUnitPromVersion DisplayString,
stackUnitHWVersion DisplayString,
stackUnitSWVersion DisplayString,
stackUnitSerialNumber DisplayString,
stackUnitAttention INTEGER,
stackUnitMgmtInterface INTEGER,
stackUnitSummary OCTET STRING ,
stackUnitSlipMgmtInterface INTEGER,
stackUnitNotepad OCTET STRING (SIZE(0..512)),
stackUnitProductNumber DisplayString
}
stackUnitLocation OBJECT-TYPE
SYNTAX INTEGER
ACCESS not-accessible
STATUS mandatory
DESCRIPTION "Used to identify individual units in the stack. Note
that this value will usually be contiguous, but that gaps may be
present due, for example, to unpowered units."
::= {stackConfigEntry 1}
stackUnitAddress OBJECT-TYPE
SYNTAX PhysAddress
ACCESS read-only
STATUS mandatory
DESCRIPTION "Every conformant unit in the SuperStack II system
will have a unique physical (MAC) address by which it can be
recognised. Note that the location index on this table can
change if a unit is inserted into the stack and so the location
can not be used to uniquely identify a location. Instead an
application should refer to units by their physical address -
see stackUnitAddress below."
::= {stackConfigEntry 2}
stackUnitLastReset OBJECT-TYPE
SYNTAX TimeTicks
ACCESS read-only
STATUS mandatory
DESCRIPTION "This is the time in hundredths of a second, since
this unit last reset (ie the unit's concept of sysUpTime). Note
that if a unit is not operational then this object will report
zero (0)."
::= {stackConfigEntry 3}
stackUnitType OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-only
STATUS mandatory
DESCRIPTION "This is an integer type identifier for this unit. The
values of this integer are administered by allocating a MIB
object identifier for each type of unit from a common branch.
The value of this object is then the last level in that
identifier. The values are defined in 3Com RFC 0025. Note that
the values are unlikely to be contiguous.
Note that if a type value is not available for this unit then
this object will return zero. There are several reasons why this
value may not be available through this view of the MIB. One
reason may be that the device is not currently active (dead) or
that the information is only available through the units own
agent (see stackUnitManagementType)."
::= {stackConfigEntry 4}
stackUnitDesc OBJECT-TYPE
SYNTAX DisplayString
ACCESS read-only
STATUS mandatory
DESCRIPTION "This is a text string which describes this unit. If a
unit cannot provide a name then the value of this object will be
an empty string."
::= {stackConfigEntry 5}
stackUnitName OBJECT-TYPE
SYNTAX DisplayString (SIZE(0..30))
ACCESS read-write
STATUS mandatory
DESCRIPTION "This is a simple text string which can be used by an
application to assign a text name to a unit. By default this
string is empty. If a management application writes a text
string to this object the device will store the string in
non-volatile storage."
::= {stackConfigEntry 6}
stackUnitState OBJECT-TYPE
SYNTAX INTEGER {
unitStateUnknown (1),
unitInactive (2),
unitOperational (3),
unitLoading (4),
unitAwaitReset(5)
}
ACCESS read-only
STATUS mandatory
DESCRIPTION "This object represents the best known state of a unit
in the stack. The unknown state is not expected to be used, but
may exist because of loosely integrated components in the stack.
Management applications MUST EXPECT to see the 'unknown' value.
The other states are as follows:
unitInactive: The device appears to be in the stack but does not
appear to be in an operational state.
unitOperational: The unit is sending out periodic identification
messages and indicates that it is operational, running its
complete image.
unitLoading: The unit is running in a special operational mode
which means that it is unmanaged while it loads a new
operational code image.
unitAwaitReset: The unit has accomplished a successful software
upgrade and is waiting for the remaining units in the stack to
successfully complete their upgrades and enter this state before
resetting the system. If any unit transitions from unitLoading
to any other state than unitAwaitReset, then the units in the
unitAwaitReset state will not reset and will transition to
unitOperational. Implementations of this object that do not
synchronize stack-wide resets after software upgrades will reset
immediately after the unitLoading state is completed and never
transition to unitAwaitReset."
::= {stackConfigEntry 7}
stackUnitManagementType OBJECT-TYPE
SYNTAX INTEGER {
unknown (1),
distributed (2),
intelligent (3)
}
ACCESS read-only
STATUS mandatory
DESCRIPTION "This object can be used to determine the management
method used to access the agent in this unit. The options are:
unknown: The unit has not reported any management
capability. It is either faulty or a
non-conformant device.
distributed: This unit can be managed using the SuperStackII
distributed management architecture and so is
managed through this agent. The unit may or may
not have an active comms stack. If it has then
the addresses for that agent can be determined
from the address table.
intelligent: The unit has its own SNMP agent which is accessed
seperately. The agent is not part of the SSII
distributed management architecture."
::= {stackConfigEntry 8}
-- Aside: The SuperStack II Distributed Management Architecture allows a
-- stack of units to be managed as though they formed a single unit.
-- The MIBs of each unit in the stack are merged and amy be accessed
-- through any unit in the stack that has an active comms stack.
stackUnitCapabilities OBJECT-TYPE
SYNTAX OCTET STRING
ACCESS read-only
STATUS mandatory
DESCRIPTION "This object describes the capabilities of this
particular unit. This is used in conjunction with the upgrade
level of the stack to enable a management application to
correctly enable and disable the various features of the
application depending on the capabilities of the unit.
The object is an octet string, where each octet represents a
capability of the unit. Different capabilities will be added
to the list as required. The current list of values is:
0x01 Full RMON
0x02 3Com Proprietary Resilience MIB
0x03 3Com Repeater Security MIB
0x04 PSHub Port Switching
0x05 PSHub Capability Upgrade Facility
0x06 Dual Speed Hub Capability Upgrade Facility
0x07 TelNet
0x08 Web
0x14 SMA Resource Allocator
0x15 SMA Distributed SNMP
0x16 SMA Global Variables
0x17 SMA Licence Server
0x18 PSHub Cascade Switch
0x19 PSH Load Balancing
0x1a RPC
0x1b Internal SNMP
0x1c Mapper
0x1d Distributed RMON
0x1e Lazy ACK
0x1f Resilience switchback
0x20 Security II
0x21 RMON Email
0x22 Rapid Spanning Tree (RSTP)
0x23 Link Aggregation Control Protocol (LACP)
0x24 L4 Redirection (WEB cache)
0x25 Device IP Configuration (DHCP)
0x26 Revised Global Port Numbering
0x27 Local Trunk Forwarding
0x28 Improved TFTP Upgrade
0x29 802.1x Network Login
0x2a RADIUS Client
0x2b Layer 3 Stacking
0x2c SW Variant
0x2d Jag3 Mode
0x2e Jag6 Mode
0x2f QoS Support of RSTP Applications
0x30 Multiple Agent Images
0x31 Power over Ethernet
0x32 OSPF
0x33 Trusted IP
0x34 Secure Shell (SSH)
0x35 Configurable management VLAN
0x36 Manual L4 cache configuration
0x37 STP Ignore Mode
0x38 MAC-address Based Network Access
0x39 Simple Network Time Protocol Client
0x3a System Logger
0x3b IGMP V3
So, for example, if a unit has a value of '02 03' for this
object then it supports repeater resilience and security, but
no other features such as RMON."
::= {stackConfigEntry 9}
stackUnitPromVersion OBJECT-TYPE
SYNTAX DisplayString
ACCESS read-only
STATUS mandatory
DESCRIPTION "This is the version number of the PROM on the unit.
If the unit has no PROM, does not correctly report the PROM
version or is currently non-operational then this object will
return an empty string."
::= {stackConfigEntry 10}
stackUnitHWVersion OBJECT-TYPE
SYNTAX DisplayString
ACCESS read-only
STATUS mandatory
DESCRIPTION "This is the hardware version of this unit, expressed
as a string. Note that if the hardware version is not available
for this particular unit then the version string will be empty."
::= {stackConfigEntry 11}
stackUnitSWVersion OBJECT-TYPE
SYNTAX DisplayString
ACCESS read-only
STATUS mandatory
DESCRIPTION "This is the software version number of this unit. The
software version number is a string. Note that if a unit does
not make its version number information available, or the unit
has no software, then this object will report an empty string."
::= {stackConfigEntry 12}
stackUnitSerialNumber OBJECT-TYPE
SYNTAX DisplayString
ACCESS read-only
STATUS mandatory
DESCRIPTION "This is the serial number for this unit. The number
is globally unique and expressed as a textual string."
::= {stackConfigEntry 13}
stackUnitAttention OBJECT-TYPE
SYNTAX INTEGER {
noAttention (1),
attention (2)
}
ACCESS read-write
STATUS mandatory
DESCRIPTION "Some of the units in the stack will contain a
mechanism for drawing attention to that unit. This is useful
for directing maintainance personnel. The method often employed
is for a special LED, or by placing some other LED into a
flashing state. This object gives access to the attention
mechanism for a unit.
Note that if a unit does not support this mechanism then reading
the value of this object will return 'no-such-name' error."
::= {stackConfigEntry 14}
stackUnitMgmtInterface OBJECT-TYPE
SYNTAX INTEGER (0..65535)
ACCESS read-only
STATUS mandatory
DESCRIPTION "If a unit in the stack participates in the
distributed SNMP stack (stackUnitManagementType = 'distributed')
then it will have an instance of this object. The object points
to the entry in the interface table which represents the
potential management interface for this unit. That is the index
to use in the ifTable for this device. Note that if the value of
this object is zero, or the result of reading this object is
NO-SUCH-NAME then there is no management interface available on
that unit."
::= {stackConfigEntry 15}
stackUnitSummary OBJECT-TYPE
SYNTAX OCTET STRING
ACCESS read-only
STATUS mandatory
DESCRIPTION "This object provides a summary of this units
configuration in order to improve the performance of the
management applications. The information in this object is
represented as a list of items, each item is a type-length-value
triplet which will have a basic encoding. The information
encoded in this string will be determined by the requirements of
the management applications. The contents of this object is
separately defined for each device.
Note: This object has been replaced by 3Com RFCs 0341, 0342 and
0343 for some devices."
::= {stackConfigEntry 16}
stackUnitSlipMgmtInterface OBJECT-TYPE
SYNTAX INTEGER (0..65535)
ACCESS read-only
STATUS mandatory
DESCRIPTION "If a unit in the stack participates in the
distributed SNMP stack then it will have an instance of this
object(stackUnitManagementType = 'distributed'). The object
points to the entry in the interface table which represents the
potential SLIP (serial port) management interface for this unit.
That is the index to use in the ifTable for this device. Note
that if the value of this object is zero, or the result of
reading this object is NO-SUCH-NAME then there is no SLIP
access port available on that unit."
::= {stackConfigEntry 17}
stackUnitNotepad OBJECT-TYPE
SYNTAX OCTET STRING (SIZE(0..512))
ACCESS read-write
STATUS mandatory
DESCRIPTION "This object is used to store user-specified data
regarding this unit. The user may store any relevant data about
the unit. This may include its floor location, history or other
details. The unit stores the data in non-volatile storage so
that the data is not lost over a normal reset. The data will be
cleared if the unit is returned to factory defaults. A maximum
of 512 characters of data may be stored in this object.
This object can be treated as a displayString. In the MIB it is
defined as an OCTET STRING since displayStrings are not allowed
to be more than 255 characters in length."
::= {stackConfigEntry 18}
stackUnitProductNumber OBJECT-TYPE
SYNTAX DisplayString
ACCESS read-only
STATUS mandatory
DESCRIPTION "This is a textual representation of the unit's
product number. Note that if a unit does not make its product
number information available then this object will report an
empty string."
::= {stackConfigEntry 19}
-- *********************************************************************
-- The following definitions are part of the Bank Swap implementation.
-- Bank Swap allows a user to select the agent that is to be used by the
-- system after a reboot.
-- The stackBankSwapTable shows the agent version string and status for
-- all agents that reside in flash. The status descriptions are shown in
-- the description for stackUnitBankStatus.
-- *********************************************************************
stackBankSwapTable OBJECT-TYPE
SYNTAX SEQUENCE OF StackBankSwapEntry
ACCESS not-accessible
STATUS mandatory
DESCRIPTION "A table of the agent software versions and status for
all agents stored in flash"
::= {stackConfiguration 2}
stackBankSwapEntry OBJECT-TYPE
SYNTAX StackBankSwapEntry
ACCESS not-accessible
STATUS mandatory
DESCRIPTION "A table entry showing the bank identifier, software
version and status for each agent."
INDEX {stackUnitLocation, stackBankSwapId}
::= {stackBankSwapTable 1}
StackBankSwapEntry ::= SEQUENCE {
stackBankSwapId INTEGER,
stackBankSwapSWVersion DisplayString,
stackBankSwapStatus INTEGER,
stackBankSwapNextActive INTEGER
}
stackBankSwapId OBJECT-TYPE
SYNTAX INTEGER
ACCESS not-accessible
STATUS mandatory
DESCRIPTION "Identifier for an agent location in the system."
::= {stackBankSwapEntry 1}
stackBankSwapSWVersion OBJECT-TYPE
SYNTAX DisplayString
ACCESS read-only
STATUS mandatory
DESCRIPTION "Software version for the software in this bank. If a
valid agent is not present in the bank, then an empty
string is returned."
::= {stackBankSwapEntry 2}
stackBankSwapStatus OBJECT-TYPE
SYNTAX INTEGER {
active(1),
activeOnLoad(2),
inactiveOnLoad(3)
}
ACCESS read-write
STATUS mandatory
DESCRIPTION "Status of a bank location. This object should be set
prior to loading new software to indicate when that
new software will become active. This object can only
be written for banks not in the active(1) state as
the software download process will always load into a
bank not in the active(1) state.
active(1) read-only - the agent is currently running.
New software will not be loaded into a bank
in this state. An error will be returned if
an attempt is made to set this value.
activeOnLoad(2) read-write - the agent is currently
inactive. If new software is successfully
loaded into a bank in this state, then the
stackBankSwapNextActive object is
automatically set to nextActive(1) for this
bank and an immediate reboot occurs, thereby
making stackBankSwapStatus active(1) and
stackBankNextActive nextActive(1) after the
reboot. This is the default state for a
bank when it is not active(1).
inactiveOnLoad(3) read-write - the agent is currently
inactive. If an attempt is made to load new
software into this bank, then after the
attempt, the box is not rebooted and the
stackBankNextActive object is left
unaffected."
::= {stackBankSwapEntry 3}
stackBankSwapNextActive OBJECT-TYPE
SYNTAX INTEGER {
nextActive(1),
nextActivePostLoad(2),
notNextActive(3)
}
ACCESS read-write
STATUS mandatory
DESCRIPTION "This object indicates which bank contains the
software that will be running after the next reboot.
The supported values include:
nextActive(1) read-write - If set, then the software
contained in this bank will be running after
the next reboot. Only one bank may have
nextActive(1) set. When using this state,
it is assumed that the software in this bank
may become active at any time since a reboot
may occur unexpectedly for many reasons.
nextActivePostLoad(2) read-write - If set, then the
software in this bank will be marked as
active after the next reboot after the
next successful software upgrade to this
bank. If the upgrade is successful, this
object will be automatically set to
nextActive(1) for this bank. If the upgrade
is unsuccessful, it will be automatically
set to notNextActive(3).
notNextActive(3) read-only - This bank does not
contain the software that will be active
after the next reboot. An error will be
returned if this value is written. When
nextActive(1) is written to a bank, the
other banks are automatically set to
notNextActive(3)."
::= {stackBankSwapEntry 4}
-- *********************************************************************
-- The stack of units may be addressable through more than one unit in
-- the stack. Some units may be manageable through more than one
-- address. This table lists the addresses within the stack through
-- which the stack (or just the unit) may be managed. Devices for which
-- the stackUnitManagementType is 'Intelligent'are not able to manage
-- other devices in the stack.
-- *********************************************************************
stackAddressInformation OBJECT IDENTIFIER ::= {superStackIIconfig 2}
stackAddressTable OBJECT-TYPE
SYNTAX SEQUENCE OF StackAddressEntry
ACCESS not-accessible
STATUS mandatory
DESCRIPTION "This table contains entries for units in the stack
which have active inband communications stacks. The table
comprises of a set of entries for each unit, each entry
representing a single address. Note that the address information
in this table cannot be changed!
This table is required specifically for those units which
execute their own SNMP agents without taking part in the Arnie
co-operative agent. I.e., the only devices for which there will
be an entry in this table are those for which the
stackUnitManagementType is 'Intelligent'."
::= {stackAddressInformation 1}
stackAddressEntry OBJECT-TYPE
SYNTAX StackAddressEntry
ACCESS not-accessible
STATUS mandatory
DESCRIPTION ""
INDEX {stackUnitLocation, stackAddressNumber}
::= {stackAddressTable 1}
StackAddressEntry ::= SEQUENCE {
stackAddressNumber INTEGER,
stackAddressType INTEGER,
stackAddress OCTET STRING
}
stackAddressNumber OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-only
STATUS mandatory
DESCRIPTION "This identifies one of a number of different
addresses for this unit. This is a second index column for this
table, the first being the unit number shared with the
stackConfigTable (stackUnitLocation)."
::= {stackAddressEntry 1}
stackAddressType OBJECT-TYPE
SYNTAX INTEGER {
ipAddress (1),
ipxAddress (2)
}
ACCESS read-only
STATUS mandatory
DESCRIPTION "This identifies the type of address."
::= {stackAddressEntry 2}
stackAddress OBJECT-TYPE
SYNTAX OCTET STRING
ACCESS read-only
STATUS mandatory
DESCRIPTION "The address."
::= {stackAddressEntry 3}
-- Define all possible sysObjIdent values as a branch from this MIB.
-- Note that because of the nature of the distributed SNMP architecture
-- it is not possible to determine the function of the device from its
-- sysObjId and so all distributed stack components will have the same
-- value.
--
-- The OBJECT IDENTIFIERS and unit types are now defined in 3Com0025.
--
stackSysObjIdentities
OBJECT IDENTIFIER ::= {superStackIIconfig 4}
stackUnitTypes OBJECT IDENTIFIER ::= {superStackIIconfig 5}
--
-- Trap Definitions
--
unitDeparture TRAP-TYPE
ENTERPRISE a3Com
VARIABLES {stackUnitDesc, stackUnitSerialNumber}
DESCRIPTION "This trap is raised by the lowest numbered unit in a
stack when a communications loss is detected to another
unit. The raising of this trap is optional."
::= 89
END

2678
priv/mibs/3com/A3Com-products-MIB Normal file
View file

File diff suppressed because it is too large Load diff

770
priv/mibs/4rf/4RF-APRISAXE-EVENTS Normal file
View file

@ -0,0 +1,770 @@
APRISAXE-EVENTS-4RF DEFINITIONS ::= BEGIN
--
-- File: $Id: 4RF-APRISAXE-EVENTS.txt,v 1.40 2007/07/20 02:50:01 ma Exp $
--
-- Copyright: 2004 4RF COMMUNICATIONS LTD
--
-- Description:
-- Event MIB for AprisaXE project, the values in this file are not accessible
-- except as notifications.
--
-- Versions:
--
-- Release 3
-- Added support for 4-wire cards and configurable cross-connections
--
-- Notes:
-- None
--
IMPORTS
-- Standard imports
MODULE-IDENTITY, OBJECT-TYPE, OBJECT-IDENTITY, NOTIFICATION-TYPE,
Integer32, Unsigned32, Counter32, IpAddress
FROM SNMPv2-SMI
TEXTUAL-CONVENTION, DisplayString
FROM SNMPv2-TC
MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP
FROM SNMPv2-CONF
-- 4RF Specific imports
fourRFAprisaXE
FROM PRODUCTS-MIB-4RF
FourRFAlarmStatus, FourRFAlarmSeverity, FourRFAlarmEnabled, FourRFAlarmPresent,
FourRFImageVersion, FourRFHardwareVersion
FROM COMMON-TC-4RF
AprisaXEAlarmType, AprisaXECardType, AprisaXESlotNumber,
AprisaXEDataStatus, AprisaXEPortNumber
FROM APRISAXE-TC-4RF
aprisaXEObjects, aprisaXEEvents
FROM APRISAXE-MIB-4RF
fourRFModules
FROM MIB-4RF;
-- Module Identification
aprisaXE4RFEventModule MODULE-IDENTITY
LAST-UPDATED "200704300000Z"
ORGANIZATION "www.4rf.com"
CONTACT-INFO
"postal: 4RF Communications Ltd
26 Glover Street
Ngauranga
PO Box 13-506
Wellington 6032
New Zealand
phone: +64 4 499 6000
email: support@4rf.com"
DESCRIPTION "Event MIB for the AprisaXE project"
-- Revision history
-- (in reverse chronological order)
REVISION "200704300000Z"
DESCRIPTION "Second draft"
REVISION "200411300334Z"
DESCRIPTION "First draft"
::= { fourRFModules 7 }
-- Trap Values
aprisaXEEventValues OBJECT IDENTIFIER ::= { aprisaXEObjects 1000 }
-- Alarm event values
aprisaXEEventAlarmStatus OBJECT-TYPE
SYNTAX FourRFAlarmPresent
MAX-ACCESS accessible-for-notify
STATUS current
DESCRIPTION "The status of an alarm event."
::= { aprisaXEEventValues 1 }
aprisaXEEventAlarmSeverity OBJECT-TYPE
SYNTAX FourRFAlarmSeverity
MAX-ACCESS accessible-for-notify
STATUS current
DESCRIPTION "The severity of the alarm."
::= { aprisaXEEventValues 2 }
aprisaXEEventAlarmValue OBJECT-TYPE
SYNTAX Integer32
MAX-ACCESS accessible-for-notify
STATUS current
DESCRIPTION "Indicatesthe current value."
::= { aprisaXEEventValues 3 }
aprisaXEEventAlarmThreshold OBJECT-TYPE
SYNTAX Integer32
MAX-ACCESS accessible-for-notify
STATUS current
DESCRIPTION "Indicates the level at which the alarm was set."
::= { aprisaXEEventValues 4 }
aprisaXEEventAlarmType OBJECT-TYPE
SYNTAX AprisaXEAlarmType
MAX-ACCESS accessible-for-notify
STATUS current
DESCRIPTION "The alarm type."
::= { aprisaXEEventValues 5 }
-- Card mismatch event values
aprisaXEEventCardExpected OBJECT-TYPE
SYNTAX AprisaXECardType
MAX-ACCESS accessible-for-notify
STATUS current
DESCRIPTION "The type of MUX card expected in a slot."
::= { aprisaXEEventValues 6 }
aprisaXEEventCardInstalled OBJECT-TYPE
SYNTAX AprisaXECardType
MAX-ACCESS accessible-for-notify
STATUS current
DESCRIPTION "The type of MUX card found in a slot."
::= { aprisaXEEventValues 7 }
aprisaXEEventCardSlot OBJECT-TYPE
SYNTAX AprisaXESlotNumber
MAX-ACCESS accessible-for-notify
STATUS current
DESCRIPTION "The slot containing the unexpected card."
::= { aprisaXEEventValues 8 }
aprisaXEEventCardStatus OBJECT-TYPE
SYNTAX FourRFAlarmPresent
MAX-ACCESS accessible-for-notify
STATUS current
DESCRIPTION "Indicates whether the alarm is present or has been cleared."
::= { aprisaXEEventValues 9 }
aprisaXEEventCardPort OBJECT-TYPE
SYNTAX AprisaXEPortNumber
MAX-ACCESS accessible-for-notify
STATUS current
DESCRIPTION "The port reporting the event."
::= { aprisaXEEventValues 10 }
-- Characterisation Data Status
aprisaXEEventCharacterisationStatus OBJECT-TYPE
SYNTAX AprisaXEDataStatus
MAX-ACCESS accessible-for-notify
STATUS current
DESCRIPTION "Indicates whether the characterisation is valid or invalid."
::= { aprisaXEEventValues 15 }
-- MIB Data Status
aprisaXEEventMibStatus OBJECT-TYPE
SYNTAX AprisaXEDataStatus
MAX-ACCESS accessible-for-notify
STATUS current
DESCRIPTION "Indicates whether the MIB is valid or invalid."
::= { aprisaXEEventValues 16 }
-- ***************************************************************************
-- Traps
-- ***************************************************************************
aprisaXELinkAlarmsEvents OBJECT-IDENTITY
STATUS current
DESCRIPTION "The events for the link alarms."
::= { aprisaXEEvents 1 }
aprisaXELinkAlarmsEventsV2 OBJECT-IDENTITY
STATUS current
DESCRIPTION "The SNMPv2 events for the link alarms."
::= { aprisaXELinkAlarmsEvents 0 }
aprisaXEThresholdAlarmEvent NOTIFICATION-TYPE
OBJECTS { aprisaXEEventAlarmStatus,
aprisaXEEventAlarmSeverity,
aprisaXEEventAlarmValue,
aprisaXEEventAlarmThreshold,
aprisaXEEventAlarmType
}
STATUS current
DESCRIPTION "Event indicating a change in state of a threshold alarm.
It will be sent whenever the status of the alarm changes from
noAlarm to alarmPresent and vice versa."
::= { aprisaXELinkAlarmsEventsV2 1 }
-- ***************************************************************************
-- Receiver Traps
-- ***************************************************************************
aprisaXERxSynthOutOfLockAlarmEvent NOTIFICATION-TYPE
OBJECTS { aprisaXEEventAlarmStatus }
STATUS current
DESCRIPTION "Event indicating a change in state of the Rx synthesizer out of lock alarm.
It will be sent whenever the status of the alarm changes from
noAlarm to alarmPresent and vice versa."
::= { aprisaXELinkAlarmsEventsV2 10 }
aprisaXEAlarmRxCDataEvent NOTIFICATION-TYPE
OBJECTS { aprisaXEEventCharacterisationStatus }
STATUS current
DESCRIPTION "Event indicating a change in state of the receiver
characterisation data alarm."
::= { aprisaXELinkAlarmsEventsV2 11 }
aprisaXEAlarmRx12VStatusEvent NOTIFICATION-TYPE
OBJECTS { aprisaXEEventAlarmStatus }
STATUS current
DESCRIPTION "Event indicating a change in state of the Rx synthesizer out of lock alarm.
It will be sent whenever the status of the alarm changes from
noAlarm to alarmPresent and vice versa."
::= { aprisaXELinkAlarmsEventsV2 12 }
aprisaXEAlarmRxOffEvent NOTIFICATION-TYPE
OBJECTS { aprisaXEEventAlarmStatus }
STATUS current
DESCRIPTION "Event indicating a change in state of receiver, when it is
turned on or off.
It will be sent whenever the status of the alarm changes from
noAlarm to alarmPresent and vice versa."
::= { aprisaXELinkAlarmsEventsV2 13 }
aprisaXEAlarmRxBadMibEvent NOTIFICATION-TYPE
OBJECTS { aprisaXEEventMibStatus }
STATUS current
DESCRIPTION "Event indicating a change in state of the receiver
MIB data alarm."
::= { aprisaXELinkAlarmsEventsV2 14 }
-- ***************************************************************************
-- Transmitter Traps
-- ***************************************************************************
aprisaXEAlarmTxCDataEvent NOTIFICATION-TYPE
OBJECTS { aprisaXEEventCharacterisationStatus }
STATUS current
DESCRIPTION "Event indicating a change in state of the transmitter
characterisation data alarm."
::= { aprisaXELinkAlarmsEventsV2 20 }
aprisaXEAlarmTxSynthOutOfLockEvent NOTIFICATION-TYPE
OBJECTS { aprisaXEEventAlarmStatus }
STATUS current
DESCRIPTION "Event indicating a change in state of the transmitter
synthesiser out of lock alarm."
::= { aprisaXELinkAlarmsEventsV2 21 }
aprisaXEAlarmTx28VStatusEvent NOTIFICATION-TYPE
OBJECTS { aprisaXEEventAlarmStatus }
STATUS current
DESCRIPTION "Event indicating a change in state of the transmitter
28V supply status alarm."
::= { aprisaXELinkAlarmsEventsV2 22 }
aprisaXEAlarmTx11VStatusEvent NOTIFICATION-TYPE
OBJECTS { aprisaXEEventAlarmStatus }
STATUS current
DESCRIPTION "Event indicating a change in state of the transmitter
11V supply status alarm."
::= { aprisaXELinkAlarmsEventsV2 23 }
aprisaXEAlarmTx5VStatusEvent NOTIFICATION-TYPE
OBJECTS { aprisaXEEventAlarmStatus }
STATUS current
DESCRIPTION "Event indicating a change in state of the transmitter
5V digital supply status alarm."
::= { aprisaXELinkAlarmsEventsV2 24 }
aprisaXEAlarmTxAmplifierBalanceEvent NOTIFICATION-TYPE
OBJECTS { aprisaXEEventAlarmStatus }
STATUS current
DESCRIPTION "Event indicating a change in state of the transmitter
amplifier balance status alarm."
::= { aprisaXELinkAlarmsEventsV2 25 }
aprisaXEAlarmTxBadMibEvent NOTIFICATION-TYPE
OBJECTS { aprisaXEEventMibStatus }
STATUS current
DESCRIPTION "Event indicating a change in state of the transmitter
MIB data alarm."
::= { aprisaXELinkAlarmsEventsV2 26 }
aprisaXEAlarmTxNeg5VStatusEvent NOTIFICATION-TYPE
OBJECTS { aprisaXEEventAlarmStatus }
STATUS current
DESCRIPTION "Event indicating a change in state of the transmitter
Negative 5V digital supply status alarm."
::= { aprisaXELinkAlarmsEventsV2 27 }
-- ***************************************************************************
-- Modem Traps
-- ***************************************************************************
aprisaXEModemSyncEvent NOTIFICATION-TYPE
OBJECTS { aprisaXEEventAlarmStatus }
STATUS current
DESCRIPTION "Event indicating a change in state of the modem lock."
::= { aprisaXELinkAlarmsEventsV2 30 }
aprisaXEModemTDMAlignmentEvent NOTIFICATION-TYPE
OBJECTS { aprisaXEEventAlarmStatus }
STATUS current
DESCRIPTION "Event indicating a change in state of the modem TDM alignment."
::= { aprisaXELinkAlarmsEventsV2 31 }
aprisaXEModemDemodAlignmentEvent NOTIFICATION-TYPE
OBJECTS { aprisaXEEventAlarmStatus }
STATUS current
DESCRIPTION "Event indicating a change in state of the modem demodulator alignment."
::= { aprisaXELinkAlarmsEventsV2 32 }
aprisaXEModemRefAStatusEvent NOTIFICATION-TYPE
OBJECTS { aprisaXEEventAlarmStatus }
STATUS current
DESCRIPTION "Event indicating a change in state of the Ref A clock."
::= { aprisaXELinkAlarmsEventsV2 33 }
aprisaXEModemRefBStatusEvent NOTIFICATION-TYPE
OBJECTS { aprisaXEEventAlarmStatus }
STATUS current
DESCRIPTION "Event indicating a change in state of the Ref B clock."
::= { aprisaXELinkAlarmsEventsV2 34 }
aprisaXEModemUCEPresentEvent NOTIFICATION-TYPE
OBJECTS { aprisaXEEventAlarmStatus }
STATUS current
DESCRIPTION "Event indicating the presence of uncorrectable errors."
::= { aprisaXELinkAlarmsEventsV2 35 }
-- ***************************************************************************
-- QuadE1 Traps
-- ***************************************************************************
aprisaXEQuadE1LOSEvent NOTIFICATION-TYPE
OBJECTS { aprisaXEEventCardSlot,
aprisaXEEventCardPort,
aprisaXEEventAlarmStatus
}
STATUS current
DESCRIPTION "Event indicating a change in LOS state for a port."
::= { aprisaXELinkAlarmsEventsV2 40 }
aprisaXEQuadE1AISEvent NOTIFICATION-TYPE
OBJECTS { aprisaXEEventCardSlot,
aprisaXEEventCardPort,
aprisaXEEventAlarmStatus
}
STATUS current
DESCRIPTION "Event indicating a change in AIS state for a port."
::= { aprisaXELinkAlarmsEventsV2 41 }
aprisaXEQuadE1RAIEvent NOTIFICATION-TYPE
OBJECTS { aprisaXEEventCardSlot,
aprisaXEEventCardPort,
aprisaXEEventAlarmStatus
}
STATUS current
DESCRIPTION "Event indicating a change in RAI state for a port."
::= { aprisaXELinkAlarmsEventsV2 42 }
aprisaXEQuadE1RMAIEvent NOTIFICATION-TYPE
OBJECTS { aprisaXEEventCardSlot,
aprisaXEEventCardPort,
aprisaXEEventAlarmStatus
}
STATUS current
DESCRIPTION "Event indicating a change in RMAI state for a port."
::= { aprisaXELinkAlarmsEventsV2 43 }
aprisaXEQuadE1TS16AISEvent NOTIFICATION-TYPE
OBJECTS { aprisaXEEventCardSlot,
aprisaXEEventCardPort,
aprisaXEEventAlarmStatus
}
STATUS current
DESCRIPTION "Event indicating a change in TS16AIS state for a port."
::= { aprisaXELinkAlarmsEventsV2 44 }
aprisaXEQuadE1TS16LOSEvent NOTIFICATION-TYPE
OBJECTS { aprisaXEEventCardSlot,
aprisaXEEventCardPort,
aprisaXEEventAlarmStatus
}
STATUS current
DESCRIPTION "Event indicating a change in TS16LOS state for a port."
::= { aprisaXELinkAlarmsEventsV2 45 }
aprisaXEQuadE1LOFEvent NOTIFICATION-TYPE
OBJECTS { aprisaXEEventCardSlot,
aprisaXEEventCardPort,
aprisaXEEventAlarmStatus
}
STATUS current
DESCRIPTION "Event indicating a change in loss of frame state for a port."
::= { aprisaXELinkAlarmsEventsV2 46 }
-- ***************************************************************************
-- FXO Traps
-- ***************************************************************************
aprisaXEFXOCodecOvldEvent NOTIFICATION-TYPE
OBJECTS { aprisaXEEventCardSlot,
aprisaXEEventCardPort,
aprisaXEEventAlarmStatus
}
STATUS current
DESCRIPTION "Event indicating a change in Codec Ovld state for a port."
::= { aprisaXELinkAlarmsEventsV2 50 }
aprisaXEFXOBillToneOvldEvent NOTIFICATION-TYPE
OBJECTS { aprisaXEEventCardSlot,
aprisaXEEventCardPort,
aprisaXEEventAlarmStatus
}
STATUS current
DESCRIPTION "Event indicating a change in Billing Tone Ovld state for a port."
::= { aprisaXELinkAlarmsEventsV2 51 }
aprisaXEFXOCurrentOvldEvent NOTIFICATION-TYPE
OBJECTS { aprisaXEEventCardSlot,
aprisaXEEventCardPort,
aprisaXEEventAlarmStatus
}
STATUS current
DESCRIPTION "Event indicating a change in Current Ovld state for a port."
::= { aprisaXELinkAlarmsEventsV2 52 }
aprisaXEFXOUnplugEvent NOTIFICATION-TYPE
OBJECTS { aprisaXEEventCardSlot,
aprisaXEEventCardPort,
aprisaXEEventAlarmStatus
}
STATUS current
DESCRIPTION "Event indicating a change in Unplug state for a port."
::= { aprisaXELinkAlarmsEventsV2 53 }
-- ***************************************************************************
-- FXS Traps
-- ***************************************************************************
aprisaXEFXSCalibrateErrorEvent NOTIFICATION-TYPE
OBJECTS { aprisaXEEventCardSlot,
aprisaXEEventCardPort,
aprisaXEEventAlarmStatus
}
STATUS current
DESCRIPTION "Event indicating a common mode error during Pro-SLIC initialisation."
::= { aprisaXELinkAlarmsEventsV2 60 }
aprisaXEFXSDCDCErrorEvent NOTIFICATION-TYPE
OBJECTS { aprisaXEEventCardSlot,
aprisaXEEventCardPort,
aprisaXEEventAlarmStatus
}
STATUS obsolete
DESCRIPTION "Event indicating a DC-DC converter error during Pro-SLIC initialisation "
::= { aprisaXELinkAlarmsEventsV2 61 }
aprisaXEFXSCASLockEvent NOTIFICATION-TYPE
OBJECTS { aprisaXEEventCardSlot,
aprisaXEEventCardPort,
aprisaXEEventAlarmStatus
}
STATUS current
DESCRIPTION "Event indicating the FPGA has not locked onto a CAS frame. "
::= { aprisaXELinkAlarmsEventsV2 62 }
-- ***************************************************************************
-- HSS Traps
-- ***************************************************************************
aprisaXEHSSTDMLockEvent NOTIFICATION-TYPE
OBJECTS { aprisaXEEventCardSlot,
aprisaXEEventAlarmStatus
}
STATUS current
DESCRIPTION "Event indicating an HSS TDM Lock error."
::= { aprisaXELinkAlarmsEventsV2 70 }
aprisaXEHSS32MHzResetEvent NOTIFICATION-TYPE
OBJECTS { aprisaXEEventCardSlot,
aprisaXEEventAlarmStatus
}
STATUS current
DESCRIPTION "Event indicating a 32MHz clock reset error."
::= { aprisaXELinkAlarmsEventsV2 71 }
aprisaXEHSSTDMResetEvent NOTIFICATION-TYPE
OBJECTS { aprisaXEEventCardSlot,
aprisaXEEventAlarmStatus
}
STATUS current
DESCRIPTION "Event indicating a TDM reset error."
::= { aprisaXELinkAlarmsEventsV2 72 }
aprisaXEHSSPatternLossEvent NOTIFICATION-TYPE
OBJECTS { aprisaXEEventCardSlot,
aprisaXEEventAlarmStatus
}
STATUS current
DESCRIPTION "Event indicating a Pattern Loss error."
::= { aprisaXELinkAlarmsEventsV2 73 }
aprisaXEHSSRxFifoFullEvent NOTIFICATION-TYPE
OBJECTS { aprisaXEEventCardSlot,
aprisaXEEventAlarmStatus
}
STATUS current
DESCRIPTION "Event indicating an Rx FIFO Full error."
::= { aprisaXELinkAlarmsEventsV2 74 }
aprisaXEHSSRxFifoEmptyEvent NOTIFICATION-TYPE
OBJECTS { aprisaXEEventCardSlot,
aprisaXEEventAlarmStatus
}
STATUS current
DESCRIPTION "Event indicating an Rx FIFO Empty error."
::= { aprisaXELinkAlarmsEventsV2 75 }
aprisaXEHSSTxFifoFullEvent NOTIFICATION-TYPE
OBJECTS { aprisaXEEventCardSlot,
aprisaXEEventAlarmStatus
}
STATUS current
DESCRIPTION "Event indicating a Tx FIFO Full error."
::= { aprisaXELinkAlarmsEventsV2 76 }
aprisaXEHSSTxFifoEmptyEvent NOTIFICATION-TYPE
OBJECTS { aprisaXEEventCardSlot,
aprisaXEEventAlarmStatus
}
STATUS current
DESCRIPTION "Event indicating a Tx FIFO Empty error."
::= { aprisaXELinkAlarmsEventsV2 77 }
aprisaXEHSSRxClockValidEvent NOTIFICATION-TYPE
OBJECTS { aprisaXEEventCardSlot,
aprisaXEEventAlarmStatus
}
STATUS current
DESCRIPTION "Event indicating an Rx Clock Valid error."
::= { aprisaXELinkAlarmsEventsV2 78 }
aprisaXEHSSTxClockValidEvent NOTIFICATION-TYPE
OBJECTS { aprisaXEEventCardSlot,
aprisaXEEventAlarmStatus
}
STATUS current
DESCRIPTION "Event indicating a Tx Clock Valid error."
::= { aprisaXELinkAlarmsEventsV2 79 }
-- ***************************************************************************
-- V24 Traps
-- ***************************************************************************
aprisaXEV24ControlLineLossEvent NOTIFICATION-TYPE
OBJECTS { aprisaXEEventCardSlot,
aprisaXEEventCardPort,
aprisaXEEventAlarmStatus
}
STATUS current
DESCRIPTION "Event indicating V24 control line aren't in sync."
::= { aprisaXELinkAlarmsEventsV2 80 }
-- ***************************************************************************
-- Other Traps
-- ***************************************************************************
aprisaXEUnexpectedCardEvent NOTIFICATION-TYPE
OBJECTS { aprisaXEEventCardSlot,
aprisaXEEventCardExpected,
aprisaXEEventCardInstalled,
aprisaXEEventCardStatus
}
STATUS current
DESCRIPTION "Event indicating an mismatch between the MIB and the installed
MUX cards. The radio will not operate correctly if the MIB and
MUX cards do not match."
::= { aprisaXELinkAlarmsEventsV2 100 }
aprisaXECLKSyncEvent NOTIFICATION-TYPE
OBJECTS { aprisaXEEventAlarmStatus }
STATUS current
DESCRIPTION "Event indicating a change in state of the clock sync state."
::= { aprisaXELinkAlarmsEventsV2 110 }
aprisaXENetClkConfigEvent NOTIFICATION-TYPE
OBJECTS { aprisaXEEventAlarmStatus }
STATUS current
DESCRIPTION "Event indicating a change in state of the network clock config."
::= { aprisaXELinkAlarmsEventsV2 111 }
aprisaXECharacterisationEEFailEvent NOTIFICATION-TYPE
OBJECTS { aprisaXEEventCardSlot,
aprisaXEEventCardInstalled,
aprisaXEEventCharacterisationStatus
}
STATUS current
DESCRIPTION "Event indicating a failed read of characterisation data from
EEPROM."
::= { aprisaXELinkAlarmsEventsV2 120 }
aprisaXEMibEEFailEvent NOTIFICATION-TYPE
OBJECTS { aprisaXEEventCardSlot,
aprisaXEEventCardInstalled,
aprisaXEEventMibStatus
}
STATUS current
DESCRIPTION "Event indicating a failed read of mib data from EEPROM."
::= { aprisaXELinkAlarmsEventsV2 121 }
aprisaXEMhsbSwitchToStandbyEvent NOTIFICATION-TYPE
OBJECTS { aprisaXEEventAlarmStatus }
STATUS current
DESCRIPTION "Event indicating a Monitored Hot Standby switch to Standby Event."
::= { aprisaXELinkAlarmsEventsV2 130 }
aprisaXEAlternateImageTableEvent NOTIFICATION-TYPE
OBJECTS { aprisaXEEventAlarmStatus }
STATUS current
DESCRIPTION "Event indicating an Alternate Image Table Event."
::= { aprisaXELinkAlarmsEventsV2 131 }
aprisaXEDefaultImageTableEvent NOTIFICATION-TYPE
OBJECTS { aprisaXEEventAlarmStatus }
STATUS current
DESCRIPTION "Event indicating a Default Image Table Event."
::= { aprisaXELinkAlarmsEventsV2 132 }
aprisaXEUploadFailEvent NOTIFICATION-TYPE
OBJECTS { aprisaXEEventAlarmStatus }
STATUS current
DESCRIPTION "Event indicating the failure of the previous upload."
::= { aprisaXELinkAlarmsEventsV2 133 }
-- ***************************************************************************
-- Psc Traps
-- ***************************************************************************
aprisaXEPscDemuxAlignmentEvent NOTIFICATION-TYPE
OBJECTS { aprisaXEEventAlarmStatus }
STATUS current
DESCRIPTION "Event indicating a change in state of the PSC Demux alignment ."
::= { aprisaXELinkAlarmsEventsV2 140 }
aprisaXEPscTDMAlignmentEvent NOTIFICATION-TYPE
OBJECTS { aprisaXEEventAlarmStatus }
STATUS current
DESCRIPTION "Event indicating a change in state of the PSC TDM alignment."
::= { aprisaXELinkAlarmsEventsV2 141 }
aprisaXEPscMuxAlignmentErrorEvent NOTIFICATION-TYPE
OBJECTS { aprisaXEEventAlarmStatus }
STATUS current
DESCRIPTION "Event indicating if the TDM mux loses alignment to the TDM bus."
::= { aprisaXELinkAlarmsEventsV2 142 }
aprisaXEPscCompanionTxFailEvent NOTIFICATION-TYPE
OBJECTS { aprisaXEEventAlarmStatus }
STATUS current
DESCRIPTION "Event indicating that the HRSD Companion transmitter has failed."
::= { aprisaXELinkAlarmsEventsV2 143 }
aprisaXEPscSoftwareOverrideEvent NOTIFICATION-TYPE
OBJECTS { aprisaXEEventAlarmStatus }
STATUS current
DESCRIPTION "Event indicating a software override of the PSC Mode Switch."
::= { aprisaXELinkAlarmsEventsV2 144 }
aprisaXEPscInvalidSwitchValueEvent NOTIFICATION-TYPE
OBJECTS { aprisaXEEventAlarmStatus }
STATUS current
DESCRIPTION "Event indicating that the PSC Mode Switch value is invalid."
::= { aprisaXELinkAlarmsEventsV2 145 }
-- ***************************************************************************
-- DualE1 Traps
-- ***************************************************************************
aprisaXEDualE1LOSEvent NOTIFICATION-TYPE
OBJECTS { aprisaXEEventCardSlot,
aprisaXEEventCardPort,
aprisaXEEventAlarmStatus
}
STATUS current
DESCRIPTION "Event indicating a change in LOS state for a port."
::= { aprisaXELinkAlarmsEventsV2 150 }
aprisaXEDualE1AISEvent NOTIFICATION-TYPE
OBJECTS { aprisaXEEventCardSlot,
aprisaXEEventCardPort,
aprisaXEEventAlarmStatus
}
STATUS current
DESCRIPTION "Event indicating a change in AIS state for a port."
::= { aprisaXELinkAlarmsEventsV2 151 }
-- ***************************************************************************
-- SingleE1 Traps
-- ***************************************************************************
aprisaXESingleE1LOSEvent NOTIFICATION-TYPE
OBJECTS { aprisaXEEventCardSlot,
aprisaXEEventCardPort,
aprisaXEEventAlarmStatus
}
STATUS current
DESCRIPTION "Event indicating a change in LOS state for a port."
::= { aprisaXELinkAlarmsEventsV2 160 }
aprisaXESingleE1AISEvent NOTIFICATION-TYPE
OBJECTS { aprisaXEEventCardSlot,
aprisaXEEventCardPort,
aprisaXEEventAlarmStatus
}
STATUS current
DESCRIPTION "Event indicating a change in AIS state for a port."
::= { aprisaXELinkAlarmsEventsV2 161 }
-- ***************************************************************************
-- HRSD Traps
-- ***************************************************************************
aprisaXEHrsdCompareOidEvent NOTIFICATION-TYPE
OBJECTS { aprisaXEEventAlarmStatus }
STATUS current
DESCRIPTION "Event indicating that an OID failed its comparison check."
::= { aprisaXELinkAlarmsEventsV2 170 }
aprisaXEHrsdCompanionLostEvent NOTIFICATION-TYPE
OBJECTS { aprisaXEEventAlarmStatus }
STATUS current
DESCRIPTION "Event indicating that the HRSD Companion Heartbeat is lost."
::= { aprisaXELinkAlarmsEventsV2 171 }
-- ***************************************************************************
-- End Traps
-- ***************************************************************************
END

10023
priv/mibs/4rf/4RF-APRISAXE-MIB Normal file
View file

File diff suppressed because it is too large Load diff

1116
priv/mibs/4rf/4RF-APRISAXE-TC Normal file
View file

File diff suppressed because it is too large Load diff

708
priv/mibs/4rf/4RF-COMMON-MIB Normal file
View file

@ -0,0 +1,708 @@
COMMON-4RF DEFINITIONS ::= BEGIN
--
-- File: $Id: 4RF-COMMON-MIB.txt,v 1.23 2007/07/11 22:04:16 di Exp $
--
-- Copyright: 2004 4RF COMMUNICATIONS LTD
--
-- Description:
-- Common MIB sub-tree for 4RF Communications Ltd., used by all products.
-- It defines some useful TEXT-CONVENTIONS and basic MIB objects relating
-- to 4RF products.
--
-- Versions:
--
-- Notes:
-- None
--
IMPORTS
-- Standard imports
MODULE-IDENTITY, OBJECT-TYPE, OBJECT-IDENTITY, NOTIFICATION-TYPE,
Integer32, Unsigned32, Counter32, IpAddress
FROM SNMPv2-SMI
TEXTUAL-CONVENTION, DisplayString, DateAndTime
FROM SNMPv2-TC
MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP
FROM SNMPv2-CONF
-- 4RF Specific imports
fourRFCommon
FROM PRODUCTS-MIB-4RF
FourRFImageVersion, FourRFSerialNumber, FourRFResetType,
FourRFProcessResultType, FourRFTftpFileName, FourRFFileSize,
FourRFImageStatus, FourRFImageType, FourRFWebUserEnabled,
FourRFWebUserGroup, FourRFTimeZone
FROM COMMON-TC-4RF
fourRFGeneric, fourRFModules
FROM MIB-4RF;
-- Module Identification
fourRFCommonModule MODULE-IDENTITY
LAST-UPDATED "200704300000Z"
ORGANIZATION "www.4rf.com"
CONTACT-INFO
"postal: 4RF Communications Ltd
26 Glover Street
Ngauranga
PO Box 13-506
Wellington 6032
New Zealand
phone: +64 4 499 6000
email: support@4rf.com"
DESCRIPTION "Common 4RF MIB Objects."
-- Revision history
-- (in reverse chronological order)
REVISION "200704300000Z"
DESCRIPTION "Second draft"
REVISION "200502110000Z"
DESCRIPTION "First draft"
::= { fourRFModules 3 }
--
-- Currently the MIB is still being defined, all objects are placed
-- under fourRFExperimental, when the MIB has been completed these
-- objects will be moved to fourRFGeneric.
--
fourRFGroups OBJECT-IDENTITY
STATUS current
DESCRIPTION "The root of the OID sub-tree for the 4RF common object groups."
::= { fourRFCommon 1 }
fourRFObjects OBJECT-IDENTITY
STATUS current
DESCRIPTION "The root of the OID sub-tree for the 4RF common objects."
::= { fourRFCommon 2 }
fourRFEvents OBJECT-IDENTITY
STATUS current
DESCRIPTION "The root of the OID sub-tree for the 4RF common events."
::= { fourRFCommon 3 }
fourRFEventsV2 OBJECT-IDENTITY
STATUS current
DESCRIPTION "The root of the OID sub-tree for the 4RF common events."
::= { fourRFEvents 0 }
-- ***************************************************************************
-- Basic terminal details
--
-- The name, location and contact details are stored in the MIB-II System
-- entries sysName, sysLocation and sysContact respectively.
--
-- ***************************************************************************
fourRFSystem OBJECT IDENTIFIER ::= { fourRFObjects 1 }
fourRFSystemID OBJECT-TYPE
SYNTAX DisplayString ( SIZE (0..255) )
MAX-ACCESS read-write
STATUS current
DESCRIPTION "The terminal identifier, user defined."
::= { fourRFSystem 1 }
fourRFSystemSoftwareVersion OBJECT-TYPE
SYNTAX FourRFImageVersion
MAX-ACCESS read-only
STATUS current
DESCRIPTION "The terminal software version details."
::= { fourRFSystem 2 }
fourRFSystemIpAddress OBJECT-TYPE
SYNTAX IpAddress
MAX-ACCESS read-write
STATUS current
DESCRIPTION "IP address of terminal, care should be taken when changing
this value."
::= { fourRFSystem 3 }
fourRFSystemRemoteIpAddress OBJECT-TYPE
SYNTAX IpAddress
MAX-ACCESS read-write
STATUS current
DESCRIPTION "IP address of remote terminal, this is the other end of the
radio link. This must be configured at commissioning."
::= { fourRFSystem 4 }
fourRFSystemSubnetMask OBJECT-TYPE
SYNTAX IpAddress
MAX-ACCESS read-write
STATUS current
DESCRIPTION "The subnet mask for the terminal. This must be configured at
commissioning."
::= { fourRFSystem 5 }
fourRFSystemDefaultGateway OBJECT-TYPE
SYNTAX IpAddress
MAX-ACCESS read-write
STATUS current
DESCRIPTION "The default gateway for the terminal. This must be configured
at commissioning."
::= { fourRFSystem 6 }
fourRFSystemIpAssignment OBJECT-TYPE
SYNTAX INTEGER { useDHCP (0),
userAssigned (1)
}
MAX-ACCESS read-write
STATUS current
DESCRIPTION "This indicates how the terminal IP address is configured.
This must be configured at commissioning. The IP address can
be assigned manually or by a DHCP server."
::= { fourRFSystem 7 }
fourRFSystemDateAndTime OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-write
STATUS current
DESCRIPTION "This indicates the current time from the terminal's real-time clock,
the time is measured in seconds since Midnight GMT on January 1 1970."
::= { fourRFSystem 8 }
fourRFSystemTftpServerAddress OBJECT-TYPE
SYNTAX IpAddress
MAX-ACCESS read-write
STATUS current
DESCRIPTION "IP address of TFTP server used for uploading and downloading files."
::= { fourRFSystem 9 }
fourRFSystemSerialNumber OBJECT-TYPE
SYNTAX FourRFSerialNumber
MAX-ACCESS read-only
STATUS current
DESCRIPTION "The unique serial number for the terminal."
::= { fourRFSystem 10 }
fourRFSystemLastReset OBJECT-TYPE
SYNTAX FourRFResetType
MAX-ACCESS read-only
STATUS current
DESCRIPTION "The type of the last system reset."
::= { fourRFSystem 11 }
fourRFSystemTimeZone OBJECT-TYPE
SYNTAX Integer32
MAX-ACCESS read-write
STATUS current
DESCRIPTION "This indicates the offset from UTC time in minutes."
::= { fourRFSystem 12 }
fourRFSystemSyslogAddress OBJECT-TYPE
SYNTAX IpAddress
MAX-ACCESS read-write
STATUS current
DESCRIPTION "The IP address of a remote syslogd server used to log system events."
::= { fourRFSystem 13 }
fourRFSystemSyslogPort OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-write
STATUS current
DESCRIPTION "The port to use when logging to a remote syslogd, the default is port 514."
::= { fourRFSystem 14 }
fourRFSystemTimeDaylightSavings OBJECT-TYPE
SYNTAX INTEGER { daylightSavingsDisabled (0),
daylightSavingsEnabled (1)
}
MAX-ACCESS read-write
STATUS current
DESCRIPTION "Indicates whether daylight savings is in use."
::= { fourRFSystem 15 }
fourRFSystemTimeZoneGMTOffset OBJECT-TYPE
SYNTAX FourRFTimeZone
MAX-ACCESS read-write
STATUS current
DESCRIPTION "This indicates the timezone offset from GMT."
::= { fourRFSystem 16 }
fourRFSystemMACAddress OBJECT-TYPE
SYNTAX DisplayString ( SIZE (0..32) )
MAX-ACCESS read-only
STATUS current
DESCRIPTION "The MAC Address for the terminal."
::= { fourRFSystem 17 }
fourRFSystemLocalRadioBIpAddress OBJECT-TYPE
SYNTAX IpAddress
MAX-ACCESS read-write
STATUS current
DESCRIPTION "IP address of local Radio B terminal, this is the partner
radio of a SD link. This must be configured at commissioning."
::= { fourRFSystem 18 }
fourRFSystemRemoteRadioBIpAddress OBJECT-TYPE
SYNTAX IpAddress
MAX-ACCESS read-write
STATUS current
DESCRIPTION "IP address of remote Radio B terminal, this is the partner
radio of a SD link. This must be configured at commissioning."
::= { fourRFSystem 19 }
fourRFSystemLocalRadioAIpAddress OBJECT-TYPE
SYNTAX IpAddress
MAX-ACCESS read-write
STATUS current
DESCRIPTION "IP address of local Radio A terminal, this is the partner
radio of a SD link. This must be configured at commissioning."
::= { fourRFSystem 20 }
fourRFSystemGroup OBJECT-GROUP
OBJECTS { fourRFSystemID,
fourRFSystemSoftwareVersion,
fourRFSystemIpAddress,
fourRFSystemRemoteIpAddress,
fourRFSystemSubnetMask,
fourRFSystemDefaultGateway,
fourRFSystemIpAssignment,
fourRFSystemDateAndTime,
fourRFSystemTftpServerAddress,
fourRFSystemSerialNumber,
fourRFSystemLastReset,
fourRFSystemTimeZone,
fourRFSystemSyslogAddress,
fourRFSystemSyslogPort,
fourRFSystemTimeDaylightSavings,
fourRFSystemTimeZoneGMTOffset,
fourRFSystemMACAddress,
fourRFSystemLocalRadioBIpAddress,
fourRFSystemRemoteRadioBIpAddress,
fourRFSystemLocalRadioAIpAddress
}
STATUS current
DESCRIPTION "The 4RF common system settings group."
::= { fourRFGroups 1 }
-- ***************************************************************************
-- System reset handling
--
-- These MIB entries allow the system to be reset, currently two types
-- of reset are possible, shutdown and a restart. It may be that other
-- options should be supported to reset just the Linux software or to
-- perform a complete hardware reset. A reset can be instigated immediately
-- or at a specified time. In the case of a timed reset the reset may be
-- cancelled if required.
--
-- An SNMP trap reset4RFEvent will be generated just before the reset is
-- performed.
--
-- ***************************************************************************
fourRFReset OBJECT IDENTIFIER ::= { fourRFObjects 2 }
fourRFResetType OBJECT-TYPE
SYNTAX INTEGER { none (0),
softReset (1),
hardReset (2)
}
MAX-ACCESS read-write
STATUS current
DESCRIPTION "Identifies the type of reset operation:
none - do nothing!
hardReset - complete reset of all components
softReset - reset of the CPU only, traffic is unaffected.
The values mirror the ResetType textual convention but the
user cannot instigate a watchdog reset. This value is not
therefore not allowed."
::= { fourRFReset 1 }
fourRFResetTime OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-write
STATUS current
DESCRIPTION "Identifies the time of a delayed reset operation. This allows an
absolute time to be specified based on the system real-time clock.
The time is measured in seconds since Midnight GMT on January 1 1970."
::= { fourRFReset 2 }
fourRFResetCommand OBJECT-TYPE
SYNTAX INTEGER { none (0),
resetNow (1),
timedReset (2),
cancelReset (3)
}
MAX-ACCESS read-write
STATUS current
DESCRIPTION "Command to instigate or cancel a system reset, the reset may
happen immediately or at a specified time. Only a timed reset
can be cancelled."
::= { fourRFReset 3 }
fourRFResetGroup OBJECT-GROUP
OBJECTS { fourRFResetType,
fourRFResetTime,
fourRFResetCommand
}
STATUS current
DESCRIPTION "The 4RF common reset group."
::= { fourRFGroups 2 }
-- ***************************************************************************
-- MIB configuration backup/restore
--
-- These objects are used to control the backup of the MIB configuration
-- data. The configuration is downloaded to the TFTP server as a backup.
--
-- SNMP traps will be generated each time a backup is performed to
-- indicate whether the file transfer was successful or not.
--
-- ***************************************************************************
fourRFMibBackup OBJECT IDENTIFIER ::= { fourRFObjects 3 }
fourRFMibBackupFile OBJECT-TYPE
SYNTAX FourRFTftpFileName
MAX-ACCESS read-write
STATUS current
DESCRIPTION "Path and file name for remote (TFTP) backup, relative to TFTP root."
::= { fourRFMibBackup 1 }
fourRFMibBackupCommand OBJECT-TYPE
SYNTAX INTEGER { none (0),
remoteBackup (1),
localBackup (2)
}
MAX-ACCESS read-write
STATUS current
DESCRIPTION "Configuration command to backup a configuration setting the value
to localBackup or remoteBackup will instigate the backup. A local
backup simply stores the current MIB configuration into Flash memory
in the terminal. A remoteBackup uploads the MIB configuration to the
currently specified TFTP server"
::= { fourRFMibBackup 2 }
fourRFMibBackupResult OBJECT-TYPE
SYNTAX FourRFProcessResultType
MAX-ACCESS read-only
STATUS current
DESCRIPTION "Configuration backup status, if no backup has been performed the
value is none otherwise the result from the last backup will be
returned. If a backup is in progress executing is returned."
::= { fourRFMibBackup 3 }
fourRFMibBackupGroup OBJECT-GROUP
OBJECTS { fourRFMibBackupFile,
fourRFMibBackupCommand,
fourRFMibBackupResult
}
STATUS current
DESCRIPTION "The 4RF common configuration backup group."
::= { fourRFGroups 3 }
-- ***************************************************************************
-- File upload handling, files will always be uploaded to the backup location
-- in flash so we don't overwrite the currently running image/configuration.
-- This means we don't need to specify a target location for the download.
--
-- It is possible to upload four types of files, a kernel image, a root file
-- system, MIB configuration and firmware (FPGA). The images may have extra
-- data added to allow the version information to be determined easily or
-- this could be coded into the file name. File uploads are always performed
-- immediately.
--
-- ***************************************************************************
fourRFUpload OBJECT IDENTIFIER ::= { fourRFObjects 4 }
fourRFUploadType OBJECT-TYPE
SYNTAX FourRFImageType
MAX-ACCESS read-write
STATUS current
DESCRIPTION "Identifies the type of image to be uploaded."
::= { fourRFUpload 1 }
fourRFUploadFile OBJECT-TYPE
SYNTAX FourRFTftpFileName
MAX-ACCESS read-write
STATUS current
DESCRIPTION "Path and file name for remote (TFTP) upload/download, relative
to the TFTP server root."
::= { fourRFUpload 2 }
fourRFUploadCommand OBJECT-TYPE
SYNTAX INTEGER { none (0),
upload (1)
}
MAX-ACCESS read-write
STATUS current
DESCRIPTION "Command used to instigate a file upload."
::= { fourRFUpload 3 }
fourRFUploadResult OBJECT-TYPE
SYNTAX FourRFProcessResultType
MAX-ACCESS read-only
STATUS current
DESCRIPTION "Status of a file upload, this will have to be polled to follow
the upload progress."
::= { fourRFUpload 4 }
fourRFUploadGroup OBJECT-GROUP
OBJECTS { fourRFUploadType,
fourRFUploadFile,
fourRFUploadCommand,
fourRFUploadResult
}
STATUS current
DESCRIPTION "The 4RF common file upload group."
::= { fourRFGroups 4 }
--
-- Image table, gives details of all the images currently stored in flash.
-- The details include the image type, status and version. Only one image of
-- each kernel or rootfs type may be active at any time. We may have one or more
-- inactive images however.
--
-- The approach here allows the different elements making up the running
-- software to be updated and configured independently. It also also makes
-- it easier to handle more than two images if required.
--
-- Example
--
-- imageIndex imageType imageStatus imageVersion
-- 1 kernel active 2.4.20
-- 2 rootfs inactive version 1
-- 3 kernel inactive 2.4.21
-- 4 configuration active Working version 5.0 29/6/03
--
-- MIB images are not stored in this table
--
fourRFImageTable OBJECT-TYPE
SYNTAX SEQUENCE OF FourRFImageTableEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION "This table is used to report the image information for each
image stored in flash."
::= { fourRFObjects 5 }
fourRFImageTableEntry OBJECT-TYPE
SYNTAX FourRFImageTableEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION "Identifies the image table index."
INDEX { fourRFImageIndex }
::= { fourRFImageTable 1 }
FourRFImageTableEntry ::= SEQUENCE {
fourRFImageIndex Integer32,
fourRFImageType INTEGER,
fourRFImageStatus INTEGER,
fourRFImageSize Unsigned32,
fourRFImageVersion OCTET STRING
}
fourRFImageIndex OBJECT-TYPE
SYNTAX Integer32
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION "The image table index."
::= { fourRFImageTableEntry 1 }
fourRFImageType OBJECT-TYPE
SYNTAX FourRFImageType
MAX-ACCESS read-only
STATUS current
DESCRIPTION "The type of image, kernel, rootfs or firmware."
::= { fourRFImageTableEntry 2 }
fourRFImageStatus OBJECT-TYPE
SYNTAX FourRFImageStatus
MAX-ACCESS read-only
STATUS current
DESCRIPTION "The image status, if current then the image is the current
running image. If selected the image will be used following
the next system reboot."
::= { fourRFImageTableEntry 3 }
fourRFImageSize OBJECT-TYPE
SYNTAX FourRFFileSize
MAX-ACCESS read-only
STATUS current
DESCRIPTION "The image size in bytes."
::= { fourRFImageTableEntry 4 }
fourRFImageVersion OBJECT-TYPE
SYNTAX FourRFImageVersion
MAX-ACCESS read-only
STATUS current
DESCRIPTION "The image version, string which can be used to identify the
image. This may include the firmware type, version number or
the build date. The exect format of this string will product
and/or image specific."
::= { fourRFImageTableEntry 5 }
-- ***************************************************************************
-- The following objects allow the status of an image to be updated. A new
-- image can be selected to run. The new image will pnly be used following
-- a system reboot.
--
-- ***************************************************************************
fourRFImageControl OBJECT IDENTIFIER ::= { fourRFObjects 6 }
fourRFImageTableIndex OBJECT-TYPE
SYNTAX Integer32
MAX-ACCESS read-write
STATUS current
DESCRIPTION "The image table index, the table entry to be updated."
::= { fourRFImageControl 1 }
fourRFImageTableCommand OBJECT-TYPE
SYNTAX INTEGER { none (0),
deactivateImage (1),
activateImage (2),
deleteImage (3)
}
MAX-ACCESS read-write
STATUS current
DESCRIPTION "Allows an image to be activated or deactivated, activating an
image will change its state to selected but the new image will
only be used following a reboot of the system."
::= { fourRFImageControl 2 }
fourRFImageControlGroup OBJECT-GROUP
OBJECTS { fourRFImageTableIndex,
fourRFImageTableCommand
}
STATUS current
DESCRIPTION "The 4RF common image control group."
::= { fourRFGroups 6 }
-- ***************************************************************************
-- Web User Management
--
-- These objects are used to control webaccess to the terminal. It allows
-- users to be added, deleted and modified.
--
-- ***************************************************************************
fourRFWebUserManagementTable OBJECT-TYPE
SYNTAX SEQUENCE OF FourRFWebUserEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION "This table is used to view and modify the current web
interface users. Up to 16 different users may be defined."
::= { fourRFObjects 7 }
fourRFWebUserEntry OBJECT-TYPE
SYNTAX FourRFWebUserEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION "Identifies the user management table index."
INDEX { fourRFWebUserIndex }
::= { fourRFWebUserManagementTable 1 }
FourRFWebUserEntry ::= SEQUENCE {
fourRFWebUserIndex Integer32,
fourRFWebUserName OCTET STRING,
fourRFWebUserPassword OCTET STRING,
fourRFWebUserGroup INTEGER,
fourRFWebUserEnabled INTEGER,
fourRFWebUserPasswordConfirm OCTET STRING
}
fourRFWebUserIndex OBJECT-TYPE
SYNTAX Integer32 (0..10)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION "The user management table index."
::= { fourRFWebUserEntry 1 }
fourRFWebUserName OBJECT-TYPE
SYNTAX DisplayString ( SIZE (0..32) )
MAX-ACCESS read-write
STATUS current
DESCRIPTION "The web user name."
::= { fourRFWebUserEntry 2 }
fourRFWebUserPassword OBJECT-TYPE
SYNTAX OCTET STRING ( SIZE (4..32) )
MAX-ACCESS read-write
STATUS current
DESCRIPTION "The password entry of a given user."
::= { fourRFWebUserEntry 3 }
fourRFWebUserGroup OBJECT-TYPE
SYNTAX FourRFWebUserGroup
MAX-ACCESS read-write
STATUS current
DESCRIPTION "The group to which the user belongs."
::= { fourRFWebUserEntry 4 }
fourRFWebUserEnabled OBJECT-TYPE
SYNTAX FourRFWebUserEnabled
MAX-ACCESS read-write
STATUS current
DESCRIPTION "Determines if the user is enabled."
::= { fourRFWebUserEntry 5 }
fourRFWebUserPasswordConfirm OBJECT-TYPE
SYNTAX OCTET STRING ( SIZE (4..32) )
MAX-ACCESS read-write
STATUS current
DESCRIPTION "Dummy OID used for password confirmation in the web management interface."
::= { fourRFWebUserEntry 6 }
-- ***************************************************************************
-- Common traps
--
-- ***************************************************************************
--
-- Reset event, triggered when the terminal is about to reset.
--
fourRFResetEvent NOTIFICATION-TYPE
OBJECTS { fourRFResetType }
STATUS current
DESCRIPTION "Event indicating that a system reset is about to occur."
::= { fourRFEventsV2 1 }
--
-- Backup status event, used to indicate whether a MIB configuration backup
-- to the TFTP server was successful
--
fourRFMibBackupStatusEvent NOTIFICATION-TYPE
OBJECTS { fourRFMibBackupFile,
fourRFMibBackupCommand,
fourRFMibBackupResult
}
STATUS current
DESCRIPTION "Event indicating the status of a configuration backup operation."
::= { fourRFEventsV2 2 }
--
-- Upload status event, used to indicate whether a file upload from
-- the TFTP server was successful
--
fouRFUploadStatusEvent NOTIFICATION-TYPE
OBJECTS { fourRFUploadFile,
fourRFUploadType,
fourRFUploadResult
}
STATUS current
DESCRIPTION "Event indicating the status of a file upload operation."
::= { fourRFEventsV2 3 }
END

448
priv/mibs/4rf/4RF-COMMON-TC Normal file
View file

@ -0,0 +1,448 @@
COMMON-TC-4RF DEFINITIONS ::= BEGIN
--
-- File: $Id: 4RF-COMMON-TC.txt,v 1.27 2007/05/07 00:19:51 pk Exp $
--
-- Copyright: 2004 4RF COMMUNICATIONS LTD
--
-- Description:
-- Common MIB sub-tree for 4RF Communications Ltd., used by all products.
-- It defines some useful TEXT-CONVENTIONS relating to 4RF products.
--
-- Versions:
--
-- Notes:
-- None
--
IMPORTS
-- Standard imports
MODULE-IDENTITY, OBJECT-IDENTITY
Integer32, Unsigned32, Counter32
FROM SNMPv2-SMI
TEXTUAL-CONVENTION, DisplayString, DateAndTime
FROM SNMPv2-TC
-- 4RF Specific imports
fourRFGeneric, fourRFModules
FROM MIB-4RF;
-- Module Identification
fourRFCommonTCModule MODULE-IDENTITY
LAST-UPDATED "200704300000Z"
ORGANIZATION "www.4rf.com"
CONTACT-INFO
"postal: 4RF Communications Ltd
26 Glover Street
Ngauranga
PO Box 13-506
Wellington 6032
New Zealand
phone: +64 4 499 6000
email: support@4rf.com"
DESCRIPTION "Common 4RF MIB Textual Conventions."
-- Revision history
-- (in reverse chronological order)
REVISION "200704300000Z"
DESCRIPTION "Second draft"
REVISION "200402130000Z"
DESCRIPTION "First draft"
::= { fourRFModules 4 }
--
-- LED control types
--
FourRFSimpleLedState ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION "The possible states for a simple LED."
SYNTAX INTEGER { off (0),
on (1)
}
FourRFTriColourLedState ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION "The possible states of a three-colour LED."
SYNTAX INTEGER { off (0),
green (1),
red (2),
orange (3) }
--
-- Basic alarm control types
--
FourRFAlarmSeverity ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION "The possible alarm severities, not all values need be used."
SYNTAX INTEGER { noSeverity (0),
-- informational (1),
-- warning (2),
minor (3),
major (4)
-- critical (5)
}
FourRFAlarmPresent ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION "The possible alarm states, alarmPresent indicates that the
alarm is active."
SYNTAX INTEGER { noAlarmPresent (0),
alarmPresent (1)
}
FourRFAlarmEnabled ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION "Indicates whether an alarm is enabled or not, it may be useful
to allow specific alarms to be enabled or disabled by the user."
SYNTAX INTEGER { disabled (0),
enabled (1)
}
FourRFAlarmStatus ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION "This is used to identify current alarm status."
SYNTAX INTEGER { noAlarm (0),
informationAlarm (1),
warningAlarm (2),
minorAlarm (3),
majorAlarm (4),
criticalAlarm (5)
}
FourRFMHSBStatus ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION "This is used to give the state of an MHSB terminal."
SYNTAX INTEGER { notAvailable (0),
active (1),
standby (2)
}
FourRFMHSBCommand ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION "This is used to send a command to an MHSB terminal."
SYNTAX INTEGER { noCommand (0),
clearSwitchedAlarm (1),
forceSwitchover (2)
}
--
-- Hardware version - an 8 bit integer value
--
FourRFHardwareVersion ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION "The hardware version details."
SYNTAX DisplayString ( SIZE (0..32) )
--
-- Terminal/Module Serial Number
--
FourRFSerialNumber ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION "A module/terminal serial number format xxxx-xxx."
SYNTAX OCTET STRING ( SIZE (8) )
--
-- Reset types
--
FourRFResetType ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION "The possible types of reset."
SYNTAX INTEGER { none (0),
softReset (1),
hardReset (2),
watchdogReset (3)
}
--
-- Image details
--
FourRFImageType ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION "The possible image types to upload."
SYNTAX INTEGER { none (0),
kernel (1),
rootfs (2),
mib (3),
configuration (4),
firmware (5)
}
FourRFImageStatus ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"The possible image status values, currentImage means it is the running.
selectedImage means that the image has been selected and will be used
following the next reboot of the system, currentNotSelected means that
the image is currently in use but won't be following a reboot."
SYNTAX INTEGER { inactiveImage (0),
currentImage (1),
currentNotSelected (2),
selectedImage (3)
}
FourRFImageVersion ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION "The image version details."
SYNTAX DisplayString ( SIZE (0..64) )
--
-- Other Types
--
FourRFProcessResultType ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION "The possible states for a process which takes time to complete."
SYNTAX INTEGER { none (0),
executing (1),
writingToFlash (2),
succeeded (3),
failed (4)
}
FourRFTftpFileName ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION "The name of a file to transfered using TFTP."
SYNTAX DisplayString ( SIZE (0..255) )
FourRFFileSize ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION "A size of a file in bytes."
SYNTAX Unsigned32
--
-- Useful Radio Related Types
--
FourRFFrequency ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION "A frequency value in Hz."
SYNTAX Unsigned32
FourRFTxPower ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION "A transmitter power value in dBm."
SYNTAX INTEGER { noPower (0),
dbm10 (10),
dbm11 (11),
dbm12 (12),
dbm13 (13),
dbm14 (14),
dbm15 (15),
dbm16 (16),
dbm17 (17),
dbm18 (18),
dbm19 (19),
dbm20 (20),
dbm21 (21),
dbm22 (22),
dbm23 (23),
dbm24 (24),
dbm25 (25),
dbm26 (26),
dbm27 (27),
dbm28 (28),
dbm29 (29),
dbm30 (30),
dbm31 (31),
dbm32 (32),
dbm33 (33),
dbm34 (34),
dbm35 (35),
dbm36 (36),
dbm37 (37),
dbm38 (38),
dbm39 (39),
dbm40 (40)
}
FourRFChannelWidth ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION "The possible channel width values."
SYNTAX INTEGER { invalidChannel (0),
channel20KHz (1),
channel25KHz (2),
channel50KHz (3),
channel75KHz (4),
channel100KHz (5),
channel125KHz (6),
channel150KHz (7),
channel200KHz (9),
channel250KHz (10),
channel400KHz (13),
channel500KHz (20),
channel800KHz (25),
channel1MHz (30),
channel1point25MHz (33),
channel1point35MHz (35),
channel1point75MHz (40),
channel2MHz (42),
channel2point5MHz (45),
channel3point5MHz (50),
channel5point25MHz (55),
channel7MHz (60),
channel14MHz (70)
}
FourRFNetworkClockStatus ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION "The possible modulation types for the radio."
SYNTAX INTEGER { active (0),
inactive (1),
holdover (2)
}
FourRFRSSI ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d-1"
STATUS current
DESCRIPTION "A receiver RSSI value, in dBm."
SYNTAX Integer32(-2000..2000)
FourRFSNR ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d-2"
STATUS current
DESCRIPTION "A signal to noise ratio in dBm."
SYNTAX Integer32
FourRFModulationType ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION "The possible modulation types for the radio."
SYNTAX INTEGER { modQPSK (0),
mod16QAM (1),
mod32QAM (2),
mod64QAM (3),
mod128QAM (4),
mod256QAM (5),
-- Modulation off
modNone (6)
}
FourRFTemperature ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION "A temperature value in degrees Celcius."
SYNTAX Integer32
FourRFErrorCounter ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION "An error counter, e.g. for the uncorrectable error count."
SYNTAX Counter32
FourRFRfBand ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION "This is used to identify the frequency band of the transmitter
The bands are:
330 to 400 MHz (300 MHz)
400 to 470 MHz (400 MHz)
1350 to 1550 MHz (1400 MHz) ."
SYNTAX INTEGER { invalidBand (0),
band300MHz (10),
band400MHz (20),
band700MHz (24),
band800MHz (26),
band900MHz (28),
band1400MHz (30)
}
FourRFFanStatus ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION "This is used to identify current fan status."
SYNTAX INTEGER { notFitted (0),
fanOkay (1),
fanFailed (2)
}
FourRFClockSource ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION "This is used to identify the clock source for the terminal."
SYNTAX INTEGER { networkClock (0),
linkClock (1),
internalClock (2)
}
FourRFNetworkClockSelect ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION "This is used to select the priority of the clocks to use."
SYNTAX INTEGER { none (0),
primary (1),
secondary (2)
}
FourRFLoopback ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION "This is used to control loopback or monitor status."
SYNTAX INTEGER { loopbackOff (0),
loopbackOn (1)
}
--
-- Web User Handling
--
FourRFWebUserGroup ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION "This is used to identify the group to which a web user belongs."
SYNTAX INTEGER { readOnlyGroup (0),
readWriteGroup (1),
adminGroup (2)
}
FourRFWebUserEnabled ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION "This is used to identify whether a web user is enabled."
SYNTAX INTEGER { userDisabled (0),
userEnabled (1)
}
FourRFTimeZone ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION "This is used to assign an offset in minutes based on GMT timezone."
SYNTAX INTEGER { gmtMinusTwelve (-720),
gmtMinusEleven (-660),
gmtMinusTen (-600),
gmtMinusNine (-540),
gmtMinusEight (-480),
gmtMinusSeven (-420),
gmtMinusSix (-360),
gmtMinusFive (-300),
gmtMinusFour (-240),
gmtMinusThreePointFive (-210),
gmtMinusThree (-180),
gmtMinusTwo (-120),
gmtMinusOne (-60),
gmt (0),
gmtPlusOne (60),
gmtPlusTwo (120),
gmtPlusThree (180),
gmtPlusFour (240),
gmtPlusFive (300),
gmtPlusSix (360),
gmtPlusSeven (420),
gmtPlusEight (480),
gmtPlusNine (540),
gmtPlusTen (600),
gmtPlusEleven (660),
gmtPlusTwelve (720),
gmtPlusThirteen (800)
}
END

104
priv/mibs/4rf/4RF-MIB Normal file
View file

@ -0,0 +1,104 @@
MIB-4RF DEFINITIONS ::= BEGIN
--
-- File: $Id: 4RF-MIB.txt,v 1.3 2007/05/02 00:26:45 pk Exp $
--
-- Copyright: 2002 4RF COMMUNICATIONS LTD
--
-- Description:
-- Top-level MIB sub-tree for 4RF Communications Ltd.
--
-- Versions:
--
-- Notes:
-- None
--
IMPORTS
-- Standard imports
MODULE-IDENTITY, OBJECT-IDENTITY, enterprises
FROM SNMPv2-SMI;
-- Module Identification
fourRFRootModule MODULE-IDENTITY
LAST-UPDATED "200704300000Z"
ORGANIZATION "www.4rf.com"
CONTACT-INFO
"postal: 4RF Communications Ltd
26 Glover Street
Ngauranga
PO Box 13-506
Wellington 6032
New Zealand
phone: +64 4 499 6000
email: support@4rf.com"
DESCRIPTION "The root MIB module for 4RF Communications Ltd."
-- Revision history
-- (in reverse chronological order)
REVISION "200704300000Z"
DESCRIPTION "Second draft"
REVISION "200402130000Z"
DESCRIPTION "First draft"
::= { fourRFModules 1 }
--
--
-- Root of OID sub-tree for 4RF as assigned by IANA
--
-- This value MUST NOT BE MODIFIED
--
--
fourRFRoot OBJECT-IDENTITY
STATUS current
DESCRIPTION "The root of the OID sub-tree for 4RF Communications Ltd."
::= { enterprises 14817 }
--
-- Top Level OID Registrations
--
fourRFRegistrations OBJECT-IDENTITY
STATUS current
DESCRIPTION "Sub-tree for registrations."
::= { fourRFRoot 1 }
fourRFModules OBJECT-IDENTITY
STATUS current
DESCRIPTION "Sub-tree for module registrations."
::= { fourRFRoot 2 }
fourRFGeneric OBJECT-IDENTITY
STATUS current
DESCRIPTION "Sub-tree for common object and event definitions."
::= { fourRFRoot 3 }
fourRFProducts OBJECT-IDENTITY
STATUS current
DESCRIPTION "Sub-tree for specific object and event definitions."
::= { fourRFRoot 4 }
fourRFCapabilities OBJECT-IDENTITY
STATUS current
DESCRIPTION "Sub-tree for agent profiles/capabilities."
::= { fourRFRoot 5 }
fourRFRequirements OBJECT-IDENTITY
STATUS current
DESCRIPTION "Sub-tree for management application requirements."
::= { fourRFRoot 6 }
fourRFExperimental OBJECT-IDENTITY
STATUS current
DESCRIPTION "Sub-tree for experimental definitions."
::= { fourRFRoot 7 }
END

84
priv/mibs/4rf/4RF-PRODUCTS-MIB Normal file
View file

@ -0,0 +1,84 @@
PRODUCTS-MIB-4RF DEFINITIONS ::= BEGIN
--
-- File: $Id: 4RF-PRODUCTS-MIB.txt,v 1.3 2007/05/02 00:26:45 pk Exp $
--
-- Copyright: 2002 4RF COMMUNICATIONS LTD
--
-- Description:
-- Products MIB sub-tree for 4RF Communications Ltd. It defines the root
-- identifiers for all 4RF SNMP managed products.
--
-- Versions:
--
-- Notes:
-- None
--
IMPORTS
-- Standard imports
MODULE-IDENTITY, OBJECT-IDENTITY, enterprises
FROM SNMPv2-SMI
-- 4RF Specific imports
fourRFModules, fourRFProducts, fourRFExperimental
FROM MIB-4RF;
-- Module Identification
fourRFProductsModule MODULE-IDENTITY
LAST-UPDATED "200704300000Z"
ORGANIZATION "www.4rf.com"
CONTACT-INFO
"postal: 4RF Communications Ltd
26 Glover Street
Ngauranga
PO Box 13-506
Wellington 6032
New Zealand
phone: +64 4 499 6000
email: support@4rf.com"
DESCRIPTION
"4RF product registrations, all 4RF SNMP managed products have
a root identifier specified here."
-- Revision history
-- (in reverse chronological order)
REVISION "200704300000Z"
DESCRIPTION "Second draft"
REVISION "200402130000Z"
DESCRIPTION "First draft"
::= { fourRFModules 2 }
--
-- OID Registrations
--
--
-- Currently the MIB is still being defined, all objects are placed
-- under fourRFExperimental, when the MIB has been completed these
-- objects will be moved to fourRFProducts.
--
fourRFCommon OBJECT-IDENTITY
STATUS current
DESCRIPTION "Sub-tree for common elements."
::= { fourRFExperimental 1 }
fourRFAprisa OBJECT-IDENTITY
STATUS current
DESCRIPTION "Sub-tree for Aprisa/AprisaView."
::= { fourRFExperimental 2 }
fourRFAprisaXE OBJECT-IDENTITY
STATUS current
DESCRIPTION "Sub-tree for AprisaXE."
::= { fourRFExperimental 3 }
END

1221
priv/mibs/ADSL-LINE-EXT-MIB Normal file
View file

File diff suppressed because it is too large Load diff

4382
priv/mibs/ADSL-LINE-MIB Normal file
View file

File diff suppressed because it is too large Load diff

113
priv/mibs/ADSL-TC-MIB Normal file
View file

@ -0,0 +1,113 @@
ADSL-TC-MIB DEFINITIONS ::= BEGIN
IMPORTS
transmission,
MODULE-IDENTITY, Gauge32 FROM SNMPv2-SMI
TEXTUAL-CONVENTION FROM SNMPv2-TC;
adsltcmib MODULE-IDENTITY
LAST-UPDATED "9908190000Z"
ORGANIZATION "IETF ADSL MIB Working Group"
CONTACT-INFO
"
Gregory Bathrick
AG Communication Systems
A Subsidiary of Lucent Technologies
2500 W Utopia Rd.
Phoenix, AZ 85027 USA
Tel: +1 602-582-7679
Fax: +1 602-582-7697
E-mail: bathricg@agcs.com
Faye Ly
Copper Mountain Networks
Norcal Office
2470 Embarcadero Way
Palo Alto, CA 94303
Tel: +1 650-858-8500
Fax: +1 650-858-8085
E-Mail: faye@coppermountain.com
IETF ADSL MIB Working Group (adsl@xlist.agcs.com)
"
DESCRIPTION
"The MIB module which provides a ADSL
Line Coding Textual Convention to be used
by ADSL Lines."
-- Revision history
REVISION "9908190000Z" -- 19 August 1999, midnight
DESCRIPTION "Initial Version, published as RFC 2662"
::= { transmission 94 2 } -- adslMIB 2
AdslLineCodingType ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"This data type is used as the syntax for the ADSL
Line Code."
SYNTAX INTEGER {
other(1),-- none of the following
dmt (2), -- Discrete MultiTone
cap (3), -- Carrierless Amplitude & Phase modulation
qam (4) -- Quadrature Amplitude Modulation
}
AdslPerfCurrDayCount ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"A counter associated with interface performance
measurements in a current 1-day (24 hour) measurement
interval.
The value of this counter starts at zero at the
beginning of an interval and is increased when
associated events occur, until the end of the
1-day interval. At that time the value of the
counter is stored in the previous 1-day history
interval, if available, and the current interval
counter is restarted at zero.
In the case where the agent has no valid data available
for this interval the corresponding object
instance is not available and upon a retrieval
request a corresponding error message shall be
returned to indicate that this instance does
not exist (for example, a noSuchName error for
SNMPv1 and a noSuchInstance for SNMPv2 GET
operation)."
SYNTAX Gauge32
AdslPerfPrevDayCount ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"A counter associated with interface performance
measurements during the most previous 1-day (24 hour)
measurement interval. The value of this counter is
equal to the value of the current day counter at
the end of its most recent interval.
In the case where the agent has no valid data available
for this interval the corresponding object
instance is not available and upon a retrieval
request a corresponding error message shall be
returned to indicate that this instance does
not exist (for example, a noSuchName error for
SNMPv1 and a noSuchInstance for SNMPv2 GET
operation)."
SYNTAX Gauge32
AdslPerfTimeElapsed ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"The number of seconds that have elapsed since
the beginning of the current measurement period.
If, for some reason, such as an adjustment in the
system's time-of-day clock, the current interval
exceeds the maximum value, the agent will return
the maximum value."
SYNTAX Gauge32
END

728
priv/mibs/ADSL2-LINE-TC-MIB Normal file
View file

@ -0,0 +1,728 @@
ADSL2-LINE-TC-MIB DEFINITIONS ::= BEGIN
IMPORTS
MODULE-IDENTITY,
transmission
FROM SNMPv2-SMI
TEXTUAL-CONVENTION
FROM SNMPv2-TC;
adsl2TCMIB MODULE-IDENTITY
LAST-UPDATED "200610040000Z"
ORGANIZATION "ADSLMIB Working Group"
CONTACT-INFO
"WG-email: adslmib@ietf.org
Info: https://www1.ietf.org/mailman/listinfo/adslmib
Chair: Mike Sneed
Sand Channel Systems
Postal: P.O. Box 37324
Raleigh NC 27627-732
Email: sneedmike@hotmail.com
Phone: +1 206 600 7022
Co-Chair & Co-editor:
Menachem Dodge
ECI Telecom Ltd.
Postal: 30 Hasivim St.
Petach Tikva 49517,
Israel.
Email: mbdodge@ieee.org
Phone: +972 3 926 8421
Co-editor: Moti Morgenstern
ECI Telecom Ltd.
Postal: 30 Hasivim St.
Petach Tikva 49517,
Israel.
Email: moti.morgenstern@ecitele.com
Phone: +972 3 926 6258
Co-editor: Scott Baillie
NEC Australia
Postal: 649-655 Springvale Road,
Mulgrave, Victoria 3170,
Australia.
Email: scott.baillie@nec.com.au
Phone: +61 3 9264 3986
Co-editor: Umberto Bonollo
NEC Australia
Postal: 649-655 Springvale Road,
Mulgrave, Victoria 3170,
Australia.
Email: umberto.bonollo@nec.com.au
Phone: +61 3 9264 3385"
DESCRIPTION
"This MIB Module provides Textual Conventions to be
used by the ADSL2-LINE-MIB module for the purpose of
managing ADSL, ADSL2, and ADSL2+ lines.
Copyright (C) The Internet Society (2006). This version of
this MIB module is part of RFC 4706: see the RFC itself for
full legal notices."
REVISION "200610040000Z"
DESCRIPTION
"Initial version, published as RFC 4706."
::= { transmission 238 2 }
-- adsl2MIB 2
--
-- ----------------------------------------------
-- Textual Conventions --
-- ----------------------------------------------
Adsl2Unit ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"Identifies a transceiver as being either an ATU-C or
an ATU-R. An ADSL line consists of two transceivers, an ATU-C
and an ATU-R. Attributes with this syntax reference the two
sides of a line. Specified as an INTEGER, the two values
are:
atuc(1) -- Central office ADSL terminal unit (ATU-C).
atur(2) -- Remote ADSL terminal unit (ATU-R)."
SYNTAX INTEGER {
atuc(1),
atur(2)
}
Adsl2Direction ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"Identifies the direction of a band as being
either upstream or downstream. Specified as an INTEGER,
the two values are:
upstream(1), and
downstream(2)."
SYNTAX INTEGER {
upstream(1),
downstream(2)
}
Adsl2TransmissionModeType ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"A set of ADSL2 line transmission modes, with one bit
per mode. The notes (F) and (L) denote Full-Rate
and Lite/splitterless, respectively:
Bit 00 : Regional Std. (ANSI T1.413) (F)
Bit 01 : Regional Std. (ETSI DTS/TM06006) (F)
Bit 02 : G.992.1 POTS non-overlapped (F)
Bit 03 : G.992.1 POTS overlapped (F)
Bit 04 : G.992.1 ISDN non-overlapped (F)
Bit 05 : G.992.1 ISDN overlapped (F)
Bit 06 : G.992.1 TCM-ISDN non-overlapped (F)
Bit 07 : G.992.1 TCM-ISDN overlapped (F)
Bit 08 : G.992.2 POTS non-overlapped (L)
Bit 09 : G.992.2 POTS overlapped (L)
Bit 10 : G.992.2 with TCM-ISDN non-overlapped (L)
Bit 11 : G.992.2 with TCM-ISDN overlapped (L)
Bit 12 : G.992.1 TCM-ISDN symmetric (F) -- not in G.997.1
Bit 13-17: Reserved
Bit 18 : G.992.3 POTS non-overlapped (F)
Bit 19 : G.992.3 POTS overlapped (F)
Bit 20 : G.992.3 ISDN non-overlapped (F)
Bit 21 : G.992.3 ISDN overlapped (F)
Bit 22-23: Reserved
Bit 24 : G.992.4 POTS non-overlapped (L)
Bit 25 : G.992.4 POTS overlapped (L)
Bit 26-27: Reserved
Bit 28 : G.992.3 Annex I All-Digital non-overlapped (F)
Bit 29 : G.992.3 Annex I All-Digital overlapped (F)
Bit 30 : G.992.3 Annex J All-Digital non-overlapped (F)
Bit 31 : G.992.3 Annex J All-Digital overlapped (F)
Bit 32 : G.992.4 Annex I All-Digital non-overlapped (L)
Bit 33 : G.992.4 Annex I All-Digital overlapped (L)
Bit 34 : G.992.3 Annex L POTS non-overlapped, mode 1,
wide U/S (F)
Bit 35 : G.992.3 Annex L POTS non-overlapped, mode 2,
narrow U/S(F)
Bit 36 : G.992.3 Annex L POTS overlapped, mode 3,
wide U/S (F)
Bit 37 : G.992.3 Annex L POTS overlapped, mode 4,
narrow U/S (F)
Bit 38 : G.992.3 Annex M POTS non-overlapped (F)
Bit 39 : G.992.3 Annex M POTS overlapped (F)
Bit 40 : G.992.5 POTS non-overlapped (F)
Bit 41 : G.992.5 POTS overlapped (F)
Bit 42 : G.992.5 ISDN non-overlapped (F)
Bit 43 : G.992.5 ISDN overlapped (F)
Bit 44-45: Reserved
Bit 46 : G.992.5 Annex I All-Digital non-overlapped (F)
Bit 47 : G.992.5 Annex I All-Digital overlapped (F)
Bit 48 : G.992.5 Annex J All-Digital non-overlapped (F)
Bit 49 : G.992.5 Annex J All-Digital overlapped (F)
Bit 50 : G.992.5 Annex M POTS non-overlapped (F)
Bit 51 : G.992.5 Annex M POTS overlapped (F)
Bit 52-55: Reserved"
SYNTAX BITS {
ansit1413(0),
etsi(1),
g9921PotsNonOverlapped(2),
g9921PotsOverlapped(3),
g9921IsdnNonOverlapped(4),
g9921isdnOverlapped(5),
g9921tcmIsdnNonOverlapped(6),
g9921tcmIsdnOverlapped(7),
g9922potsNonOverlapped(8),
g9922potsOverlapped(9),
g9922tcmIsdnNonOverlapped(10),
g9922tcmIsdnOverlapped(11),
g9921tcmIsdnSymmetric(12),
reserved1(13),
reserved2(14),
reserved3(15),
reserved4(16),
reserved5(17),
g9923PotsNonOverlapped(18),
g9923PotsOverlapped(19),
g9923IsdnNonOverlapped(20),
g9923isdnOverlapped(21),
reserved6(22),
reserved7(23),
g9924potsNonOverlapped(24),
g9924potsOverlapped(25),
reserved8(26),
reserved9(27),
g9923AnnexIAllDigNonOverlapped(28),
g9923AnnexIAllDigOverlapped(29),
g9923AnnexJAllDigNonOverlapped(30),
g9923AnnexJAllDigOverlapped(31),
g9924AnnexIAllDigNonOverlapped(32),
g9924AnnexIAllDigOverlapped(33),
g9923AnnexLMode1NonOverlapped(34),
g9923AnnexLMode2NonOverlapped(35),
g9923AnnexLMode3Overlapped(36),
g9923AnnexLMode4Overlapped(37),
g9923AnnexMPotsNonOverlapped(38),
g9923AnnexMPotsOverlapped(39),
g9925PotsNonOverlapped(40),
g9925PotsOverlapped(41),
g9925IsdnNonOverlapped(42),
g9925isdnOverlapped(43),
reserved10(44),
reserved11(45),
g9925AnnexIAllDigNonOverlapped(46),
g9925AnnexIAllDigOverlapped(47),
g9925AnnexJAllDigNonOverlapped(48),
g9925AnnexJAllDigOverlapped(49),
g9925AnnexMPotsNonOverlapped(50),
g9925AnnexMPotsOverlapped(51),
reserved12(52),
reserved13(53),
reserved14(54),
reserved15(55)
}
Adsl2RaMode ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"Specifies the rate adaptation behavior for the line.
The three possible behaviors are:
manual(1) - No Rate-Adaptation. The initialization
process attempts to synchronize to a
specified rate.
raInit(2) - Rate-Adaptation during initialization process
only, which attempts to synchronize to a rate
between minimum and maximum specified values.
dynamicRa(3) - Dynamic Rate-Adaptation during initialization
process as well as during SHOWTIME."
SYNTAX INTEGER {
manual(1),
raInit(2),
dynamicRa(3)
}
Adsl2InitResult ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"Specifies the result of a full initialization attempt; the
six possible result values are:
noFail(0) - Successful initialization.
configError(1) - Configuration failure.
configNotFeasible(2) - Configuration details not supported.
commFail(3) - Communication failure.
noPeerAtu(4) - Peer ATU not detected.
otherCause(5) - Other initialization failure reason.
The values used are as defined in ITU-T G.997.1,
paragraph 7.5.1.3"
SYNTAX INTEGER {
noFail(0),
configError(1),
configNotFeasible(2),
commFail(3),
noPeerAtu(4),
otherCause(5)
}
Adsl2OperationModes ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"The ADSL2 management model specified includes an ADSL Mode
attribute that identifies an instance of ADSL Mode-Specific
PSD Configuration object in the ADSL Line Profile. The
following classes of ADSL operating mode are defined.
The notes (F) and (L) denote Full-Rate and Lite/splitterless
respectively:
+-------+--------------------------------------------------+
| Value | ADSL operation mode description |
+-------+--------------------------------------------------+
1 - The default/generic PSD configuration. Default
configuration will be used when no other matching
mode-specific configuration can be found.
2 - ADSL family. The attributes included in the Mode-
Specific PSD Configuration are irrelevant for
ITU-T G.992.1 and G.992.2 ADSL modes. Hence, it
is possible to map those modes to this generic
class.
3-7 - Unused. Reserved for future ITU-T specification.
8 - G.992.3 POTS non-overlapped (F)
9 - G.992.3 POTS overlapped (F)
10 - G.992.3 ISDN non-overlapped (F)
11 - G.992.3 ISDN overlapped (F)
12-13 - Unused. Reserved for future ITU-T specification.
14 - G.992.4 POTS non-overlapped (L)
15 - G.992.4 POTS overlapped (L)
16-17 - Unused. Reserved for future ITU-T specification.
18 - G.992.3 Annex I All-Digital non-overlapped (F)
19 - G.992.3 Annex I All-Digital overlapped (F)
20 - G.992.3 Annex J All-Digital non-overlapped (F)
21 - G.992.3 Annex J All-Digital overlapped (F)
22 - G.992.4 Annex I All-Digital non-overlapped (L)
23 - G.992.4 Annex I All-Digital overlapped (L)
24 - G.992.3 Annex L POTS non-overlapped, mode 1,
wide U/S (F)
25 - G.992.3 Annex L POTS non-overlapped, mode 2,
narrow U/S(F)
26 - G.992.3 Annex L POTS overlapped, mode 3,
wide U/S (F)
27 - G.992.3 Annex L POTS overlapped, mode 4,
narrow U/S (F)
28 - G.992.3 Annex M POTS non-overlapped (F)
29 - G.992.3 Annex M POTS overlapped (F)
30 - G.992.5 POTS non-overlapped (F)
31 - G.992.5 POTS overlapped (F)
32 - G.992.5 ISDN non-overlapped (F)
33 - G.992.5 ISDN overlapped (F)
34-35 - Unused. Reserved for future ITU-T specification.
36 - G.992.5 Annex I All-Digital non-overlapped (F)
37 - G.992.5 Annex I All-Digital overlapped (F)
38 - G.992.5 Annex J All-Digital non-overlapped (F)
39 - G.992.5 Annex J All-Digital overlapped (F)
40 - G.992.5 Annex M POTS non-overlapped (F)
41 - G.992.5 Annex M POTS overlapped (F)"
SYNTAX INTEGER {
defMode(1),
adsl(2),
g9923PotsNonOverlapped(8),
g9923PotsOverlapped(9),
g9923IsdnNonOverlapped(10),
g9923isdnOverlapped(11),
g9924potsNonOverlapped(14),
g9924potsOverlapped(15),
g9923AnnexIAllDigNonOverlapped(18),
g9923AnnexIAllDigOverlapped(19),
g9923AnnexJAllDigNonOverlapped(20),
g9923AnnexJAllDigOverlapped(21),
g9924AnnexIAllDigNonOverlapped(22),
g9924AnnexIAllDigOverlapped(23),
g9923AnnexLMode1NonOverlapped(24),
g9923AnnexLMode2NonOverlapped(25),
g9923AnnexLMode3Overlapped(26),
g9923AnnexLMode4Overlapped(27),
g9923AnnexMPotsNonOverlapped(28),
g9923AnnexMPotsOverlapped(29),
g9925PotsNonOverlapped(30),
g9925PotsOverlapped(31),
g9925IsdnNonOverlapped(32),
g9925isdnOverlapped(33),
g9925AnnexIAllDigNonOverlapped(36),
g9925AnnexIAllDigOverlapped(37),
g9925AnnexJAllDigNonOverlapped(38),
g9925AnnexJAllDigOverlapped(39),
g9925AnnexMPotsNonOverlapped(40),
g9925AnnexMPotsOverlapped(41)
}
Adsl2PowerMngState ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"Attributes with this syntax uniquely identify each power
management state defined for the ADSL/ADSL2 or ADSL2+ link.
The possible values are:
l0(1) - L0 - Full power management state.
l1(2) - L1 - Low power management state (for G.992.2).
l2(3) - L2 - Low power management state (for G.992.3,
G.992.4, and G.992.5).
l3(4) - L3 - Idle power management state."
SYNTAX INTEGER {
l0(1),
l1(2),
l2(3),
l3(4)
}
Adsl2ConfPmsForce ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"Attributes with this syntax are configuration parameters
that reference the desired power management state for the
ADSL/ADSL2 or ADSL2+ link:
l3toL0(0) - Perform a transition from L3 to L0
(Full power management state).
l0toL2(2) - Perform a transition from L0 to L2
(Low power management state).
l0orL2toL3(3) - Perform a transition into L3 (Idle
power management state).
The values used are as defined in ITU-T G.997.1,
paragraph 7.3.1.1.3"
SYNTAX INTEGER {
l3toL0(0),
l0toL2(2),
l0orL2toL3(3)
}
Adsl2LConfProfPmMode ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"Attributes with this syntax are configuration parameters
that reference the power modes/states into which the ATU-C or
ATU-R may autonomously transit.
It is a BITS structure that allows control of the following
transit options:
allowTransitionsToIdle(0) - XTU may autonomously transit
to idle (L3) state.
allowTransitionsToLowPower(1) - XTU may autonomously transit
to low-power (L2) state."
SYNTAX BITS {
allowTransitionsToIdle(0),
allowTransitionsToLowPower(1)
}
Adsl2LineLdsf ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"Attributes with this syntax are configuration parameters
that control the Loop Diagnostic mode for the ADSL/ADSL2 or
ADSL2+ link. The possible values are:
inhibit(0) - Inhibit Loop Diagnostic mode.
force(1) - Force/Initiate Loop Diagnostic mode.
The values used are as defined in ITU-T G.997.1,
paragraph 7.3.1.1.8"
SYNTAX INTEGER {
inhibit(0),
force(1)
}
Adsl2LdsfResult ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"Possible failure reasons associated with performing
a Dual Ended Loop Test (DELT) on a DSL line.
Possible values are:
none(1) - The default value in case LDSF was never
requested for the associated line.
success(2) - The recent command completed
successfully.
inProgress(3) - The Loop Diagnostics process is in
progress.
unsupported(4) - The NE or the line card doesn't support
LDSF.
cannotRun(5) - The NE cannot initiate the command, due
to a nonspecific reason.
aborted(6) - The Loop Diagnostics process aborted.
failed(7) - The Loop Diagnostics process failed.
illegalMode(8) - The NE cannot initiate the command, due
to the specific mode of the relevant
line.
adminUp(9) - The NE cannot initiate the command, as
the relevant line is administratively
'Up'.
tableFull(10) - The NE cannot initiate the command, due
to reaching the maximum number of rows
in the results table.
noResources(11) - The NE cannot initiate the command, due
to lack of internal memory resources."
SYNTAX INTEGER {
none(1),
success(2),
inProgress(3),
unsupported(4),
cannotRun(5),
aborted(6),
failed(7),
illegalMode(8),
adminUp(9),
tableFull(10),
noResources(11)
}
Adsl2SymbolProtection ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"Attributes with this syntax are configuration parameters
that reference the minimum-length impulse noise protection
(INP) in terms of number of symbols. The possible values are:
noProtection (i.e., INP not required), halfSymbol (i.e., INP
length is 1/2 symbol), and 1-16 symbols in steps of 1 symbol."
SYNTAX INTEGER {
noProtection(1),
halfSymbol(2),
singleSymbol(3),
twoSymbols(4),
threeSymbols(5),
fourSymbols(6),
fiveSymbols(7),
sixSymbols(8),
sevenSymbols(9),
eightSymbols(10),
nineSymbols(11),
tenSymbols(12),
elevenSymbols(13),
twelveSymbols(14),
thirteeSymbols(15),
fourteenSymbols(16),
fifteenSymbols(17),
sixteenSymbols(18)
}
Adsl2MaxBer ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"Attributes with this syntax are configuration parameters
that reference the maximum Bit Error Rate (BER).
The possible values are:
eminus3(1) - Maximum BER=E^-3
eminus5(2) - Maximum BER=E^-5
eminus7(3) - Maximum BER=E^-7"
SYNTAX INTEGER {
eminus3(1),
eminus5(2),
eminus7(3)
}
Adsl2ScMaskDs ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"Each one of the 512 bits in this OCTET
STRING array represents the corresponding bin
in the downstream direction. A value of one
indicates that the bin is not in use."
SYNTAX OCTET STRING (SIZE (0..64))
Adsl2ScMaskUs ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"Each one of the 64 bits in this OCTET
STRING array represents the corresponding bin
in the upstream direction. A value of one
indicates that the bin is not in use."
SYNTAX OCTET STRING (SIZE (0..8))
Adsl2RfiDs ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"Each one of the 512 bits in this OCTET
STRING array represents the corresponding bin
in the downstream direction. A value of one
indicates that the bin is part of a notch
filter."
SYNTAX OCTET STRING (SIZE (0..64))
Adsl2PsdMaskDs ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"This is a structure that represents up to
32 PSD Mask breakpoints.
Each breakpoint occupies 3 octets: The first
two octets hold the index of the sub-carrier
associated with the breakpoint. The third octet
holds the PSD reduction at the breakpoint from 0
(0 dBm/Hz) to 255 (-127.5 dBm/Hz) using units of
0.5 dBm/Hz."
SYNTAX OCTET STRING (SIZE (0..96))
Adsl2PsdMaskUs ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"This is a structure that represents up to
4 PSD Mask breakpoints.
Each breakpoint occupies 3 octets: The first
two octets hold the index of the sub-carrier
associated with the breakpoint. The third octet
holds the PSD reduction at the breakpoint from 0
(0 dBm/Hz) to 255 (-127.5 dBm/Hz) using units of
0.5 dBm/Hz."
SYNTAX OCTET STRING (SIZE (0..12))
Adsl2Tssi ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"This is a structure that represents up to
32 transmit spectrum shaping (TSSi) breakpoints.
Each breakpoint occupies 3 octets: The first
two octets hold the index of the sub-carrier
associated with the breakpoint. The third octet
holds the shaping parameter at the breakpoint. It
is a value from 0 to 127 (units of -0.5 dB). The
special value 127 indicates that the sub-carrier
is not transmitted."
SYNTAX OCTET STRING (SIZE (0..96))
Adsl2LastTransmittedState ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"This parameter represents the last successfully
transmitted initialization state in the last full
initialization performed on the line. States are
per the specific xDSL technology and are numbered
from 0 (if G.994.1 is used) or 1 (if G.994.1 is
not used) up to Showtime."
SYNTAX INTEGER {
atucG9941(0),
atucQuiet1(1),
atucComb1(2),
atucQuiet2(3),
atucComb2(4),
atucIcomb1(5),
atucLineprob(6),
atucQuiet3(7),
atucComb3(8),
atucIComb2(9),
atucMsgfmt(10),
atucMsgpcb(11),
atucQuiet4(12),
atucReverb1(13),
atucTref1(14),
atucReverb2(15),
atucEct(16),
atucReverb3(17),
atucTref2(18),
atucReverb4(19),
atucSegue1(20),
atucMsg1(21),
atucReverb5(22),
atucSegue2(23),
atucMedley(24),
atucExchmarker(25),
atucMsg2(26),
atucReverb6(27),
atucSegue3(28),
atucParams(29),
atucReverb7(30),
atucSegue4(31),
atucShowtime(32),
aturG9941(100),
aturQuiet1(101),
aturComb1(102),
aturQuiet2(103),
aturComb2(104),
aturIcomb1(105),
aturLineprob(106),
aturQuiet3(107),
aturComb3(108),
aturIcomb2(109),
aturMsgfmt(110),
aturMsgpcb(111),
aturReverb1(112),
aturQuiet4(113),
aturReverb2(114),
aturQuiet5(115),
aturReverb3(116),
aturEct(117),
aturReverb4(118),
aturSegue1(119),
aturReverb5(120),
aturSegue2(121),
aturMsg1(122),
aturMedley(123),
aturExchmarker(124),
aturMsg2(125),
aturReverb6(126),
aturSegue3(127),
aturParams(128),
aturReverb7(129),
aturSegue4(130),
aturShowtime(131)
}
Adsl2LineStatus ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"Attributes with this syntax are status parameters
that reflect the failure status for a given endpoint of
ADSL/ADSL2 or ADSL2+ link.
This BITS structure can report the following failures:
noDefect(0) - This bit position positively reports
that no defect or failure exists.
lossOfFrame(1) - Loss of frame synchronization.
lossOfSignal(2) - Loss of signal.
lossOfPower(3) - Loss of power. Usually this failure may
be reported for ATU-Rs only.
initFailure(4) - Recent initialization process failed.
Never active on ATU-R."
SYNTAX BITS {
noDefect(0),
lossOfFrame(1),
lossOfSignal(2),
lossOfPower(3),
initFailure(4)
}
Adsl2ChAtmStatus ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"Attributes with this syntax are status parameters that
reflect the failure status for Transmission Convergence (TC)
layer of a given ATM interface (data path over an ADSL/ADSL2
or ADSL2+ link).
This BITS structure can report the following failures:
noDefect(0) - This bit position positively
reports that no defect or failure
exists.
noCellDelineation(1) - The link was successfully
initialized, but cell delineation
was never acquired on the
associated ATM data path.
lossOfCellDelineation(2) - Loss of cell delineation on the
associated ATM data path."
SYNTAX BITS {
noDefect(0),
noCellDelineation(1),
lossOfCellDelineation(2)
}
Adsl2ChPtmStatus ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"Attributes with this syntax are status parameters that
reflect the failure status for a given PTM interface (packet
data path over an ADSL/ADSL2 or ADSL2+ link).
This BITS structure can report the following failures:
noDefect(0) - This bit position positively
reports that no defect or failure exists.
outOfSync(1) - Out of synchronization."
SYNTAX BITS {
noDefect(0),
outOfSync(1)
}
END

1191
priv/mibs/ALARM-MIB Normal file
View file

File diff suppressed because it is too large Load diff

211
priv/mibs/ATM-DXI-MIB Normal file
View file

@ -0,0 +1,211 @@
ATM-DXI-MIB DEFINITIONS ::= BEGIN
IMPORTS
enterprises
FROM RFC1155-SMI
OBJECT-TYPE
FROM RFC-1212;
atmForum OBJECT IDENTIFIER ::= { enterprises 353 }
atmUniDxi OBJECT IDENTIFIER ::= { atmForum 3 }
-- This MIB is intended to be used in either of two scenarios.
-- In the first scenario, the DTE acts as a proxy for the DCE(s),
-- while, in the second scenario, the DCE contains an independent
-- SNMP agent and responds to SNMP requests directly.
--
-- In both these scenarios, specific DXI interfaces are identified
-- by a single integer-valued index. In the first scenario, the
-- DXI interfaces that connect directly to the DTE are identified
-- by the DTE's corresponding value of ifIndex. The DXI interfaces
-- that connect to the DCE are assigned interface numbers.
-- For example, see the figure below.
-- In this example, the numbers 4 and 5 are assigned to those
-- DXI interfaces that are connected to the DCE(s). The assignment
-- of numbers to these interfaces is implementation dependent.
-- An SNMP management station will see these as interfaces of a
-- special type (assigned by the IETF).
-- In the second scenario, all the DXI interfaces correspond
-- directly to DCE interfaces. In this case, all corresponding
-- instances are identified by IfIndices assigned by the DCE.
--
-- In the UNI ATM Cell Header, the VPI/VCI fields together
-- comprise a 24-bit field. The eight most significant bits
-- constitute the VPI subfield, and the least significant
-- sixteen bits constitute the VCI subfield. All zeros is an
-- invalid value and on ATM interfaces is used to designate a
-- null (or empty or unassigned) cell. Thus the valid VPI/VCI
-- values are in the range 1 thru 2**24-1 inclusive. These
-- values are used for indexing certain tables in the ATM
-- MIB(s).
-- The ATM Data Exchange Interface (DXI) object reflects
-- information about an ATM DXI between an ATM DCE (e.g., a DSU)
-- and a DTE (e.g., a Router/Host). In particular, it contains both
-- configuration and performance information specific to the
-- DXI. Each DXI instance typically corresponds to several DFAs.
-- With a 24-bit DFA, the range of valid DFA index values is
-- 1 thru 2**24 inclusive. Note that the 24-bit binary DFA
-- field (with values 0 thru 2**24-1) from the DXI
-- header must be incremented by one to yield the DFA index
-- for accessing the tables in the MIB. The DFA consisting of
-- all zeros (with corresponding MIB index value of 1) is
-- reserved for the DXI Local Management Interface (LMI) with
-- the ATM DTE.
Dfa ::= INTEGER (1..16777215)
-- *** For the DCEs, the mapping between the DXI
-- *** DFA and the ATM VPI/VCI is fixed. The LMI DFA has no
-- *** corresponding VPI/VCI. (Refer to Annex A for the bit mapping.)
atmDxi OBJECT IDENTIFIER ::= { atmUniDxi 2 }
---
--- This table is mandatory if supporting ATM DXI.
---
atmDxiConfTable OBJECT-TYPE
SYNTAX SEQUENCE OF AtmDxiConfEntry
ACCESS not-accessible
STATUS mandatory
DESCRIPTION
"This table contains
ATM DXI configuration information
including information on the mode supported
across the DXI."
::= { atmDxi 2 }
atmDxiConfEntry OBJECT-TYPE
SYNTAX AtmDxiConfEntry
ACCESS not-accessible
STATUS mandatory
DESCRIPTION
"This list contains ATM DXI configuration information."
INDEX { atmDxiConfIfIndex }
::= { atmDxiConfTable 1 }
AtmDxiConfEntry ::=
SEQUENCE {
atmDxiConfIfIndex
INTEGER,
atmDxiConfMode
INTEGER
}
atmDxiConfIfIndex OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The value of this object identifies, for SNMP, the ATM DXI
interface for which this entry contains management information.
This is the same value as used to identify the IfEntry describing
the DCE interface. Management uses and expects this value. In
the proxy mode of operation, the DCE always treats this as 0, but
preserves it in its response to the DTE. 0, the DXI value, means
the interface over which the DXI LMI request was received."
::= { atmDxiConfEntry 2 }
atmDxiConfMode OBJECT-TYPE
SYNTAX INTEGER {
mode1a (1),
mode1b (2),
mode2 (3)
}
ACCESS read-write
STATUS mandatory
DESCRIPTION
"This object identifies the dxi mode being
used at the atm dxi port."
::= { atmDxiConfEntry 3 }
atmDxiDFAConfTable OBJECT-TYPE
SYNTAX SEQUENCE OF AtmDxiDFAConfEntry
ACCESS not-accessible
STATUS mandatory
DESCRIPTION
"This table contains configuration information about
a particular DFA."
::= { atmDxi 3 }
atmDxiDFAConfEntry OBJECT-TYPE
SYNTAX AtmDxiDFAConfEntry
ACCESS not-accessible
STATUS mandatory
DESCRIPTION
"This list contains ATM DXI DFA configuration
information."
INDEX { atmDxiDFAConfIfIndex, atmDxiDFAConfDfaIndex }
::= { atmDxiDFAConfTable 1 }
AtmDxiDFAConfEntry ::=
SEQUENCE {
atmDxiDFAConfIfIndex
INTEGER,
atmDxiDFAConfDfaIndex
Dfa,
atmDxiDFAConfAALType
INTEGER
}
atmDxiDFAConfIfIndex OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The value of this object identifies, for SNMP, the ATM DXI
interface for which this entry contains management information.
This is the same value as used to identify the IfEntry describing
the DCE interface. Management uses and expects this value. In
the proxy mode of operation, the DCE always treats this as 0, but
preserves it in its response to the DTE. 0, the DXI value, means
the interface over which the DXI LMI request was received."
::= { atmDxiDFAConfEntry 1 }
atmDxiDFAConfDfaIndex OBJECT-TYPE
SYNTAX Dfa
ACCESS read-only
STATUS mandatory
DESCRIPTION
"This object identifies the DFA instance on the DXI
identified by atmDxiDFAConfIfIndex."
::= { atmDxiDFAConfEntry 2 }
atmDxiDFAConfAALType OBJECT-TYPE
SYNTAX INTEGER {
unknown (1),
none (2),
aal34 (3),
aal5 (4)
}
ACCESS read-write
STATUS mandatory
DESCRIPTION
"This object identifies the AAL type supported at this DFA.
Note, if mode 2 is supported on the DXI identified by the
corresponding instance of atmDxiDFAConfIfIndex and that
instance of atmDxiDFAConfIfIndex identifies the DCE side
of the DXI, then this object contains the AAL Type being
run on the corresponding VPI/VCI on the corresponding ATM UNI
interface."
::= { atmDxiDFAConfEntry 3 }
-- The following definition is for use only in Trap PDUs
atmDxiEnterprise OBJECT-TYPE
SYNTAX OBJECT IDENTIFIER
ACCESS not-accessible
STATUS mandatory
DESCRIPTION
"This object is included as the first ID-Value pair
in a Trap PDU for which the Generic Trap Type field
has the value 'enterpriseSpecific'. The value of the
object identifies the enterprise under whose authority
the value of the Enterprise Trap Type field is defined."
::= { atmDxi 4 }
-- End of definitions for ATM DXI-MIB
END

288
priv/mibs/ATM-FORUM-ADDR-REG Normal file
View file

@ -0,0 +1,288 @@
--------------------------------------------------------------------
-- ATM Address Registration MIB
--
-- March, 1995; Kartik Chandrasekhar
--
-- Copyright (c) 1995-1997 by cisco Systems, Inc.
-- All rights reserved.
-- *****************************************************************
--
ATM-FORUM-ADDR-REG DEFINITIONS ::= BEGIN
IMPORTS
atmfNetPrefixGroup,
atmfAddressGroup,
atmfAddressRegistrationAdminGroup,
AtmAddress,
NetPrefix FROM ATM-FORUM-TC-MIB
OBJECT-TYPE FROM RFC-1212;
-- The NetPrefix Group
--
-- The Network Prefix Table is implemented by the user-side IME.
atmfNetPrefixTable OBJECT-TYPE
SYNTAX SEQUENCE OF AtmfNetPrefixEntry
ACCESS not-accessible
STATUS mandatory
DESCRIPTION
"A table implemented by the user-side IME, containing the
network-prefix(es) for ATM-layer addresses in effect on
the user side of the UNI."
::= { atmfNetPrefixGroup 1 }
atmfNetPrefixEntry OBJECT-TYPE
SYNTAX AtmfNetPrefixEntry
ACCESS not-accessible
STATUS mandatory
DESCRIPTION
"Information about a single network-prefix for
ATM-layer addresses in effect on the user-side IME.
Note that the index variable atmNetPrefixPrefix is a
variable-length string, and as such the rule for
variable-length strings in section 4.1.6 of RFC 1212
applies."
INDEX { atmfNetPrefixPort, atmfNetPrefixPrefix }
::= { atmfNetPrefixTable 1 }
AtmfNetPrefixEntry ::=
SEQUENCE {
atmfNetPrefixPort
INTEGER,
atmfNetPrefixPrefix
NetPrefix,
atmfNetPrefixStatus
INTEGER
}
atmfNetPrefixPort OBJECT-TYPE
SYNTAX INTEGER (0..2147483647)
ACCESS read-only
STATUS mandatory
DESCRIPTION
"A unique value which identifies the UNI port for
which the network prefix for ATM addresses is in
effect. The value of 0 has the special meaning of
identifying the local UNI."
::= { atmfNetPrefixEntry 1 }
atmfNetPrefixPrefix OBJECT-TYPE
SYNTAX NetPrefix
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The network prefix for ATM addresses which is in
effect on the user side of the ATM UNI port."
::= { atmfNetPrefixEntry 2 }
atmfNetPrefixStatus OBJECT-TYPE
SYNTAX INTEGER { valid(1), invalid(2) }
ACCESS read-write
STATUS mandatory
DESCRIPTION
"An indication of the validity of the network prefix
for ATM addresses on the user side of the UNI port.
To configure a new network prefix in this table, the
network-side IME must set the appropriate instance of this
object to the value valid(1). To delete an existing
network prefix in this table, the network-side IME must
set the appropriate instance of this object to the
value invalid(2).
If circumstances occur on the user-side IME which cause a
prefix to become invalid, the user-side IME modifies the
value of the appropriate instance of this object to invalid(2).
Whenever the value of this object for a particular
prefix becomes invalid(2), the conceptual row for that
prefix may be removed from the table at any time,
either immediately or subsequently."
::= { atmfNetPrefixEntry 3 }
-- The Address Group
--
-- The Address Table is implemented by the network-side IME.
atmfAddressTable OBJECT-TYPE
SYNTAX SEQUENCE OF AtmfAddressEntry
ACCESS not-accessible
STATUS mandatory
DESCRIPTION
"A table implemented by the network-side IME, containing the
ATM-layer addresses in effect on the user side of the UNI."
::= { atmfAddressGroup 1 }
atmfAddressEntry OBJECT-TYPE
SYNTAX AtmfAddressEntry
ACCESS not-accessible
STATUS mandatory
DESCRIPTION
"Information about a single ATM-layer address in effect
on the user-side IME. Note that the index variable
atmAddressAtmAddress is a variable-length string, and as
such the rule for variable-length strings in section
4.1.6 of RFC 1212 applies."
INDEX { atmfAddressPort, atmfAddressAtmAddress }
::= { atmfAddressTable 1 }
AtmfAddressEntry ::=
SEQUENCE {
atmfAddressPort
INTEGER,
atmfAddressAtmAddress
AtmAddress,
atmfAddressStatus
INTEGER,
atmfAddressOrgScope
INTEGER
}
atmfAddressPort OBJECT-TYPE
SYNTAX INTEGER (0..2147483647)
ACCESS read-only
STATUS mandatory
DESCRIPTION
"A unique value which identifies the UNI port for
which the ATM address is in effect. The value of 0
has the special meaning of identifying the local UNI."
::= { atmfAddressEntry 1 }
atmfAddressAtmAddress OBJECT-TYPE
SYNTAX AtmAddress
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The ATM address which is in effect on the user side
of the ATM UNI port."
::= { atmfAddressEntry 2 }
atmfAddressStatus OBJECT-TYPE
SYNTAX INTEGER { valid(1), invalid(2) }
ACCESS read-write
STATUS mandatory
DESCRIPTION
"An indication of the validity of the ATM address at
the user side of the UNI port. To configure a new
address in this table, the user-side IME must set the
appropriate instance of this object to the value
valid(1). To delete an existing address in this table,
the user-side IME must set the appropriate instance of
this object to the value invalid(2).
If circumstances occur on the network-side IME which cause
an address to become invalid, the network-side IME
modifies the value of the appropriate instance of this
object to invalid(2).
Whenever the value of this object for a particular
address becomes invalid(2), the conceptual row for
that address may be removed from the table at any
time, either immediately or subsequently."
::= { atmfAddressEntry 3 }
atmfAddressOrgScope OBJECT-TYPE
SYNTAX INTEGER {
localNetwork(1),
localNetworkPlusOne(2),
localNetworkPlusTwo(3),
siteMinusOne(4),
intraSite(5),
sitePlusOne(6),
organizationMinusOne(7),
intraOrganization(8),
organizationPlusOne(9),
communityMinusOne(10),
intraCommunity(11),
communityPlusOne(12),
regional(13),
interRegional(14),
global(15)
}
ACCESS read-write
STATUS mandatory
DESCRIPTION
"This object indicates the organizational
scope for the referenced address. The information of
the referenced address shall not be distributed
outside the indicated scope. If the user-side IME does
not specify a value for the atmfAddressOrgScope object,
the network shall set the value of this object to
localNetwork(1), if the registered address is an ATM group
address, or to global(15), if the registered address is
an individual address. Refer to Annex 6.0
of ATM Forum UNI Signalling 4.0 for guidelines regarding
the use of organizational scopes.
This organization hierarchy may be mapped to ATM network's
routing hierarchy such as PNNI's routing level and
the mapping shall be configurable in
nodes. Use of this object in a public network is for
further study.
The default values for organizational scope are
localNetwork(1) for ATM group addresses, and global(15)
for individual addresses."
::= { atmfAddressEntry 4 }
-- The Address Registration Admin Group
--
-- The Address Registration Admin Table is mandatory for all IMEs.
atmfAddressRegistrationAdminTable OBJECT-TYPE
SYNTAX SEQUENCE OF AtmfAddressRegistrationAdminEntry
ACCESS not-accessible
STATUS mandatory
DESCRIPTION
"A table of Address Registration administrative
information for the ATM Interface."
::= { atmfAddressRegistrationAdminGroup 1 }
atmfAddressRegistrationAdminEntry OBJECT-TYPE
SYNTAX AtmfAddressRegistrationAdminEntry
ACCESS not-accessible
STATUS mandatory
DESCRIPTION
"An entry in the table, containing Address
Registration administrative information for the ATM
Interface."
INDEX { atmfAddressRegistrationAdminIndex }
::= { atmfAddressRegistrationAdminTable 1 }
AtmfAddressRegistrationAdminEntry ::=
SEQUENCE {
atmfAddressRegistrationAdminIndex
INTEGER,
atmfAddressRegistrationAdminStatus
INTEGER
}
atmfAddressRegistrationAdminIndex OBJECT-TYPE
SYNTAX INTEGER (0..2147483647)
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The value of 0 which has the special meaning of
identifying the ATM Interface over which this message
was received."
::= { atmfAddressRegistrationAdminEntry 1 }
atmfAddressRegistrationAdminStatus OBJECT-TYPE
SYNTAX INTEGER { supported(1), unsupported(2) }
ACCESS read-only
STATUS mandatory
DESCRIPTION
"An indication of whether or not Address Registration
is supported on this ATM Interface. Supported(1)
indicates that this ATM Interface supports address
registration. Unsupported(2) indicates that this ATM
Interface does not support address registration."
::= { atmfAddressRegistrationAdminEntry 2 }
END

2235
priv/mibs/ATM-FORUM-ILMI40-MIB Normal file
View file

File diff suppressed because it is too large Load diff

4119
priv/mibs/ATM-FORUM-M4-MIB Normal file
View file

File diff suppressed because it is too large Load diff

1257
priv/mibs/ATM-FORUM-MIB Normal file
View file

File diff suppressed because it is too large Load diff

4734
priv/mibs/ATM-FORUM-SNMP-M4-MIB Normal file
View file

File diff suppressed because it is too large Load diff

112
priv/mibs/ATM-FORUM-SRVC-REG Normal file
View file

@ -0,0 +1,112 @@
-- This ILMI MIB was specified as part of the LANE 1.0 specification
-- (af-lane-0021.000.mib).
-- This MIB has been made OBSOLETE by the specification of ILMI 4.0,
-- since an updated version is included within af-ilmi-0065.000.mib.
ATM-FORUM-SRVC-REG DEFINITIONS ::= BEGIN
IMPORTS
atmForumUni, atmForumAdmin FROM ATM-FORUM-TC-MIB
OBJECT-TYPE FROM RFC-1212;
-- Textual Convention
--
-- Representations of this MIB Module of an ATM address
-- use the data type:
AtmAddress ::= OCTET STRING (SIZE (8 | 20))
-- New MIB Groups
atmfSrvcRegistryGroup OBJECT IDENTIFIER ::= { atmForumUni 8 }
-- Object Identifier definitions
--
-- The following values are define dfor use as possible values
-- of the atmfSrvcRegServiceID object.
atmfSrvcRegTypes OBJECT IDENTIFIER ::= { atmForumAdmin 5 }
-- LAN Emulation Configuration Server (LECS)
atmfSrvcRegLecs OBJECT IDENTIFIER ::= { atmfSrvcRegTypes 1 }
-- The Service Registry Table
--
-- The Service Registry Table is implemented by the network side
-- of the ATM UNI port
atmfSrvcRegTable OBJECT-TYPE
SYNTAX SEQUENCE OF AtmfSrvcRegEntry
ACCESS not-accessible
STATUS mandatory
DESCRIPTION
"The table implemented by the UNI Management Entity on the
network side of the ATM UNI port contains all of the
services that are available to the user-side of the UNI
indexed by service identifier."
::= { atmfSrvcRegistryGroup 1 }
atmfSrvcRegEntry OBJECT-TYPE
SYNTAX AtmfSrvcRegEntry
ACCESS not-accessible
STATUS mandatory
DESCRIPTION
"Information about a single service provider that is
available to the user-side of the ATM UNI port."
INDEX { atmfSrvcRegPort, atmfSrvcRegServiceID,
atmfSrvcAddressIndex }
::= { atmfSrvcRegTable 1 }
AtmfSrvcRegEntry ::=
SEQUENCE {
atmfSrvcRegPort INTEGER,
atmfSrvcRegServiceID OBJECT IDENTIFIER,
atmfSrvcRegATMAddress AtmAddress,
atmfSrvcRegAddressIndex INTEGER
}
atmfSrvcRegPort OBJECT-TYPE
SYNTAX INTEGER (0..2147483647)
ACCESS not-accessible
STATUS mandatory
DESCRIPTION
"A unique value which identifies the UNI port for
which the service provider is available to the
user-side. The value of 0 has the special meaning
of identifying the local UNI."
::= { atmfSrvcRegEntry 1 }
atmfSrvcRegServiceID OBJECT-TYPE
SYNTAX OBJECT IDENTIFIER
ACCESS not-accessible
STATUS mandatory
DESCRIPTION
"This is the service identifier which uniquely identifies
the type of service at the address provided in the table."
::= { atmfSrvcRegEntry 2 }
atmfSrvcRegATMAddress OBJECT-TYPE
SYNTAX AtmAddress
ACCESS read-only
STATUS mandatory
DESCRIPTION
"This is the full address of the service. The user-side
ATM UNI port may use this address to establish a connection
with the service."
::= { atmfSrvcRegEntry 3 }
atmfSrvcRegAddressIndex OBJECT-TYPE
SYNTAX INTEGER
ACCESS not-accessible
STATUS mandatory
DESCRIPTION
"An arbitrary integer to differentiate multiple rows
containing different ATM addresses for the same service
on the same port."
::= { atmfSrvcRegEntry 4 }
END

188
priv/mibs/ATM-FORUM-TC-MIB Normal file
View file

@ -0,0 +1,188 @@
-- --------------------------------------------------------------------
-- ATM FORUM TC MIB
--
-- October 1996, Kartik Chandrasekhar
--
-- Copyright (c) 1996-1997 by cisco Systems, Inc.
-- All rights reserved.
-- *****************************************************************
ATM-FORUM-TC-MIB DEFINITIONS ::= BEGIN
IMPORTS
TEXTUAL-CONVENTION FROM SNMPv2-TC
enterprises FROM RFC1155-SMI;
-- Textual Conventions
-- Boolean values use this data type from RFC-1903, "Textual Conventions
-- for Version 2 of the Simple Network Management Protocol (SNMPv2)"
TruthValue ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"Boolean values use this data type from RFC-1903"
SYNTAX INTEGER {
true(1),
false(2)
}
-- CLNP address values use this data type from RFC-1238, "CLNS MIB for
-- use with Connectionless Network Protocol (ISO 8473) and End System
-- to Intermediate System (ISO 9542)"
ClnpAddress ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"CLNP address values use this data type from RFC-1238"
SYNTAX OCTET STRING (SIZE (1..21))
-- ATM Service Categories use this data type (See [TM4.0]):
AtmServiceCategory ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"ATM Service Categories use this data type"
SYNTAX INTEGER {
other(1),
cbr(2),
rtVbr(3),
nrtVbr(4),
abr(5),
ubr(6)
}
-- ATM End-System Addresses use this data type:
AtmAddress ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"ATM End-System Addresses"
SYNTAX OCTET STRING (SIZE (8 | 20))
-- Network-Prefixes for an ATM Address use this data type:
NetPrefix ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"ATM End-System Addresses"
SYNTAX OCTET STRING (SIZE (8 | 13))
-- In both the AtmAddress and NetPrefix conventions, Native E.164 addresses
-- are represented as 8 octets using the format specified in section
-- 3.1.1.3 of the ATM Forum UNI Signalling 4.0 specification.
-- In contrast, an NSAP-encoded address is 20 octets, and an NSAP-encoded
-- network prefix is 13 octets long.
-- MIB Groups
-- a subtree for defining ATM Forum MIB object types
atmForum OBJECT IDENTIFIER ::= { enterprises 353 }
-- a subtree for defining administrative object types
atmForumAdmin OBJECT IDENTIFIER ::= { atmForum 1 }
atmfTransmissionTypes OBJECT IDENTIFIER ::= { atmForumAdmin 2 }
atmfMediaTypes OBJECT IDENTIFIER ::= { atmForumAdmin 3 }
atmfTrafficDescrTypes OBJECT IDENTIFIER ::= { atmForumAdmin 4 }
atmfSrvcRegTypes OBJECT IDENTIFIER ::= { atmForumAdmin 5 }
-- a subtree for defining ATM Interface MIB object types
atmForumUni OBJECT IDENTIFIER ::= { atmForum 2 }
atmfPhysicalGroup OBJECT IDENTIFIER ::= { atmForumUni 1 }
atmfAtmLayerGroup OBJECT IDENTIFIER ::= { atmForumUni 2 }
atmfAtmStatsGroup OBJECT IDENTIFIER ::= { atmForumUni 3 }
atmfVpcGroup OBJECT IDENTIFIER ::= { atmForumUni 4 }
atmfVccGroup OBJECT IDENTIFIER ::= { atmForumUni 5 }
atmfAddressGroup OBJECT IDENTIFIER ::= { atmForumUni 6 }
atmfNetPrefixGroup OBJECT IDENTIFIER ::= { atmForumUni 7 }
atmfSrvcRegistryGroup OBJECT IDENTIFIER ::= { atmForumUni 8 }
atmfVpcAbrGroup OBJECT IDENTIFIER ::= { atmForumUni 9 }
atmfVccAbrGroup OBJECT IDENTIFIER ::= { atmForumUni 10 }
atmfAddressRegistrationAdminGroup OBJECT IDENTIFIER ::= { atmForumUni 11 }
-- Object Identifier definitions
-- Transmission Types: These values are no longer used
atmfUnknownType OBJECT IDENTIFIER ::= { atmfTransmissionTypes 1}
atmfSonetSTS3c OBJECT IDENTIFIER ::= { atmfTransmissionTypes 2 }
atmfDs3 OBJECT IDENTIFIER ::= { atmfTransmissionTypes 3 }
atmf4B5B OBJECT IDENTIFIER ::= { atmfTransmissionTypes 4 }
atmf8B10B OBJECT IDENTIFIER ::= { atmfTransmissionTypes 5 }
atmfSonetSTS12c OBJECT IDENTIFIER ::= { atmfTransmissionTypes 6 }
atmfE3 OBJECT IDENTIFIER ::= { atmfTransmissionTypes 7 }
atmfT1 OBJECT IDENTIFIER ::= { atmfTransmissionTypes 8 }
atmfE1 OBJECT IDENTIFIER ::= { atmfTransmissionTypes 9 }
-- Media Types: These values are no longer used
atmfMediaUnknownType OBJECT IDENTIFIER ::= { atmfMediaTypes 1 }
atmfMediaCoaxCable OBJECT IDENTIFIER ::= { atmfMediaTypes 2 }
atmfMediaSingleMode OBJECT IDENTIFIER ::= { atmfMediaTypes 3 }
atmfMediaMultiMode OBJECT IDENTIFIER ::= { atmfMediaTypes 4 }
atmfMediaStp OBJECT IDENTIFIER ::= { atmfMediaTypes 5 }
atmfMediaUtp OBJECT IDENTIFIER ::= { atmfMediaTypes 6 }
-- Traffic Descriptor Types: These types are combined with a five element
-- parameter vector to describe a Traffic Descriptor.
-- Traffic Descriptors along with a Best Effort Indicator are used to
-- indicate a Conformance Definition as defined in [TM4.0].
-- These types are no longer used
atmfNoDescriptor OBJECT IDENTIFIER ::= { atmfTrafficDescrTypes 1 }
atmfPeakRate OBJECT IDENTIFIER ::= { atmfTrafficDescrTypes 2 }
-- The No CLP/No SCR Type
-- Indicates the CBR.1 Conformance Definition if Best Effort is No
-- Indicates the UBR.1 and UBR.2 Conformance Definitions if Best Effort is Yes
atmfNoClpNoScr OBJECT IDENTIFIER ::= { atmfTrafficDescrTypes 3 }
-- The use of the parameter vector for this type:
-- Parameter #1 - peak cell rate in cells/second for CLP=0+1 traffic
-- Parameter #2 - CDVT in tenths of microseconds
-- Parameters #3, #4 and #5 are unused
-- These types are no longer used
atmfClpNoTaggingNoScr OBJECT IDENTIFIER ::= { atmfTrafficDescrTypes 4 }
atmfClpTaggingNoScr OBJECT IDENTIFIER ::= { atmfTrafficDescrTypes 5 }
-- The SCR/No CLP Type
-- Indicates the VBR.1 Conformance Definition
atmfNoClpScr OBJECT IDENTIFIER ::= { atmfTrafficDescrTypes 6 }
-- The use of the parameter vector for this type:
-- Parameter #1 - peak cell rate in cells/second for CLP=0+1 traffic
-- Parameter #2 - sustainable cell rate in cells/second for CLP=0+1 traffic
-- Parameter #3 - maximum burst size in cells
-- Parameter #4 - CDVT in tenths of microseconds
-- Parameter #5 - unused
-- The CLP without Tagging/SCR Type
-- Indicates the VBR.2 Conformance Definition
atmfClpNoTaggingScr OBJECT IDENTIFIER ::= { atmfTrafficDescrTypes 7 }
-- The use of the parameter vector for this type:
-- Parameter #1 - peak cell rate in cells/second for CLP=0+1 traffic
-- Parameter #2 - sustainable cell rate in cells/second for CLP=0 traffic
-- Parameter #3 - maximum burst size in cells
-- Parameter #4 - CDVT in tenths of microseconds
-- Parameter #5 - unused
-- The CLP with Tagging/SCR Type
-- Indicates the VBR.3 Conformance Definition
atmfClpTaggingScr OBJECT IDENTIFIER ::= { atmfTrafficDescrTypes 8 }
-- The use of the parameter vector for this type:
-- Parameter #1 - peak cell rate in cells/second for CLP=0+1 traffic
-- Parameter #2 - sustainable cell rate in cells/second for CLP=0
-- traffic, excess tagged as CLP=1
-- Parameter #3 - maximum burst size in cells
-- Parameter #4 - CDVT in tenths of microseconds
-- Parameter #5 - unused
-- The ABR Type
-- Indicates the ABR Conformance Definition
atmfClpNoTaggingMcr OBJECT IDENTIFIER ::= { atmfTrafficDescrTypes 9 }
-- The use of the parameter vector for this type:
-- Parameter #1 - peak cell rate in cells/second
-- parameter #2 - CDVT in tenths of microseconds
-- Parameter #3 - minimum cell rate in cells/second
-- Parameter #4 - unused
-- Parameter #5 - unused
END

3023
priv/mibs/ATM-MIB Normal file
View file

File diff suppressed because it is too large Load diff

714
priv/mibs/ATM-TC-MIB Normal file
View file

@ -0,0 +1,714 @@
ATM-TC-MIB DEFINITIONS ::= BEGIN
IMPORTS
MODULE-IDENTITY, OBJECT-IDENTITY,
TimeTicks, mib-2
FROM SNMPv2-SMI
TEXTUAL-CONVENTION
FROM SNMPv2-TC;
atmTCMIB MODULE-IDENTITY
LAST-UPDATED "9810190200Z"
ORGANIZATION "IETF AToMMIB Working Group"
CONTACT-INFO
" Michael Noto
Postal: 3Com Corporation
5400 Bayfront Plaza, M/S 3109
Santa Clara, CA 95052
USA
Tel: +1 408 326 2218
E-mail: mike_noto@3com.com
Ethan Mickey Spiegel
Postal: Cisco Systems
170 W. Tasman Dr.
San Jose, CA 95134
USA
Tel: +1 408 526 6408
E-mail: mspiegel@cisco.com
Kaj Tesink
Postal: Bellcore
331 Newman Springs Road
Red Bank, NJ 07701
USA
Tel: +1 732 758 5254
Fax: +1 732 758 4177
E-mail: kaj@bellcore.com"
DESCRIPTION
"This MIB Module provides Textual Conventions
and OBJECT-IDENTITY Objects to be used by
ATM systems."
::= { mib-2 37 3 } -- atmMIB 3 (see [3])
-- The Textual Conventions defined below are organized
-- alphabetically
AtmAddr ::= TEXTUAL-CONVENTION
DISPLAY-HINT "1x"
STATUS current
DESCRIPTION
"An ATM address. The semantics are implied by
the length. The address types are: - no
address (0 octets) - E.164 (8 octets) - NSAP
(20 octets) In addition, when subaddresses
are used the AtmAddr may represent the
concatenation of address and subaddress. The
associated address types are: - E.164, E.164
(16 octets) - E.164, NSAP (28 octets) - NSAP,
NSAP (40 octets) Address lengths other than
defined in this definition imply address
types defined elsewhere. Note: The E.164
address is encoded in BCD format."
SYNTAX OCTET STRING (SIZE(0..40))
AtmConnCastType ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"The type of topology of a connection (point-
to-point, point-to-multipoint). In the case
of point-to-multipoint, the orientation of
this VPL or VCL in the connection.
On a host:
- p2mpRoot indicates that the host
is the root of the p2mp connection.
- p2mpLeaf indicates that the host
is a leaf of the p2mp connection.
On a switch interface:
- p2mpRoot indicates that cells received
by the switching fabric from the interface
are from the root of the p2mp connection.
- p2mpLeaf indicates that cells transmitted
to the interface from the switching fabric
are to the leaf of the p2mp connection."
SYNTAX INTEGER {
p2p(1),
p2mpRoot(2),
p2mpLeaf(3)
}
AtmConnKind ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"The type of call control used for an ATM
connection at a particular interface. The use
is as follows:
pvc(1)
Virtual link of a PVC. Should not be
used for an PVC/SVC (i.e., Soft PVC)
crossconnect.
svcIncoming(2)
Virtual link established after a
received signaling request to setup
an SVC.
svcOutgoing(3)
Virtual link established after a
transmitted or forwarded signaling
request to setup an SVC.
spvcInitiator(4)
Virtual link at the PVC side of an
SVC/PVC crossconnect, where the
switch is the initiator of the Soft PVC
setup.
spvcTarget(5)
Virtual link at the PVC side of an
SVC/PVC crossconnect, where the
switch is the target of the Soft PVC
setup.
For PVCs, a pvc virtual link is always cross-
connected to a pvc virtual link.
For SVCs, an svcIncoming virtual link is always cross-
connected to an svcOutgoing virtual link.
For Soft PVCs, an spvcInitiator is either cross-connected to
an svcOutgoing or an spvcTarget, and an spvcTarget is either
cross-connected to an svcIncoming or an spvcInitiator."
SYNTAX INTEGER {
pvc(1),
svcIncoming(2),
svcOutgoing(3),
spvcInitiator(4),
spvcTarget(5)
}
AtmIlmiNetworkPrefix ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"A network prefix used for ILMI address
registration. In the case of ATM endsystem
addresses (AESAs), the network prefix is the first
13 octets of the address which includes the AFI,
IDI, and HO-DSP fields. In the case of native
E.164 addresses, the network prefix is the entire
E.164 address encoded in 8 octets, as if it were
an E.164 IDP in an ATM endsystem address
structure."
REFERENCE
"ATM Forum, Integrated Local Management Interface
(ILMI) Specification, Version 4.0,
af-ilmi-0065.000, September 1996, Section 9
ATM Forum, ATM User-Network Interface Signalling
Specification, Version 4.0 (UNI 4.0),
af-sig-0061.000, June 1996, Section 3"
SYNTAX OCTET STRING (SIZE(8|13))
AtmInterfaceType ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"The connection setup procedures used for the
identified interface.
Other: Connection setup procedures other than
those listed below.
Auto-configuration:
Indicates that the connection setup
procedures are to be determined dynamically,
or that determination has not yet been
completed. One such mechanism is via ATM
Forum ILMI auto-configuration procedures.
ITU-T DSS2:
- ITU-T Recommendation Q.2931, Broadband
Integrated Service Digital Network (B-ISDN)
Digital Subscriber Signalling System No.2
(DSS2) User-Network Interface (UNI) Layer 3
Specification for Basic Call/Connection
Control (September 1994)
- ITU-T Draft Recommendation Q.2961,
B-ISDN DSS 2 Support of Additional Traffic
Parameters (May 1995)
- ITU-T Draft Recommendation Q.2971,
B-ISDN DSS 2 User Network Interface Layer 3
Specification for Point-to-multipoint
Call/connection Control (May 1995)
ATM Forum UNI 3.0:
ATM Forum, ATM User-Network Interface,
Version 3.0 (UNI 3.0) Specification,
(1994).
ATM Forum UNI 3.1:
ATM Forum, ATM User-Network Interface,
Version 3.1 (UNI 3.1) Specification,
(November 1994).
ATM Forum UNI Signalling 4.0:
ATM Forum, ATM User-Network Interface (UNI)
Signalling Specification Version 4.0,
af-sig-0061.000 (June 1996).
ATM Forum IISP (based on UNI 3.0 or UNI 3.1) :
Interim Inter-switch Signaling Protocol
(IISP) Specification, Version 1.0,
af-pnni-0026.000, (December 1994).
ATM Forum PNNI 1.0 :
ATM Forum, Private Network-Network Interface
Specification, Version 1.0, af-pnni-0055.000,
(March 1996).
ATM Forum B-ICI:
ATM Forum, B-ICI Specification, Version 2.0,
af-bici-0013.002, (November 1995).
ATM Forum UNI PVC Only:
An ATM Forum compliant UNI with the
signalling disabled.
ATM Forum NNI PVC Only:
An ATM Forum compliant NNI with the
signalling disabled."
SYNTAX INTEGER {
other(1),
autoConfig(2),
ituDss2(3),
atmfUni3Dot0(4),
atmfUni3Dot1(5),
atmfUni4Dot0(6),
atmfIispUni3Dot0(7),
atmfIispUni3Dot1(8),
atmfIispUni4Dot0(9),
atmfPnni1Dot0(10),
atmfBici2Dot0(11),
atmfUniPvcOnly(12),
atmfNniPvcOnly(13) }
AtmServiceCategory ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"The service category for a connection."
REFERENCE
"ATM Forum Traffic Management Specification,
Version 4.0, af-tm-0056.000, June 1996."
SYNTAX INTEGER {
other(1), -- none of the following
cbr(2), -- constant bit rate
rtVbr(3), -- real-time variable bit rate
nrtVbr(4), -- non real-time variable bit rate
abr(5), -- available bit rate
ubr(6) -- unspecified bit rate
}
AtmSigDescrParamIndex ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"The value of this object identifies a row in the
atmSigDescrParamTable. The value 0 signifies that
none of the signalling parameters defined in the
atmSigDescrParamTable are applicable."
SYNTAX INTEGER (0..2147483647)
AtmTrafficDescrParamIndex ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"The value of this object identifies a row in the
atmTrafficDescrParamTable. The value 0 signifies
that no row has been identified."
SYNTAX INTEGER (0..2147483647)
AtmVcIdentifier ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"The VCI value for a VCL. The maximum VCI value
cannot exceed the value allowable by
atmInterfaceMaxVciBits defined in ATM-MIB."
SYNTAX INTEGER (0..65535)
AtmVpIdentifier ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"The VPI value for a VPL or VCL. The value VPI=0
is only allowed for a VCL. For ATM UNIs supporting
VPCs the VPI value ranges from 0 to 255. The VPI
value 0 is supported for ATM UNIs conforming to
the ATM Forum UNI 4.0 Annex 8 (Virtual UNIs)
specification. For ATM UNIs supporting VCCs the
VPI value ranges from 0 to 255. For ATM NNIs the
VPI value ranges from 0 to 4095. The maximum VPI
value cannot exceed the value allowable by
atmInterfaceMaxVpiBits defined in ATM-MIB."
SYNTAX INTEGER (0..4095)
AtmVorXAdminStatus ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"The value determines the desired administrative
status of a virtual link or cross-connect. The up
and down states indicate that the traffic flow is
enabled or disabled respectively on the virtual
link or cross-connect."
SYNTAX INTEGER {
up(1),
down(2)
}
AtmVorXLastChange ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"The value of MIB II's sysUpTime at the time a
virtual link or cross-connect entered its current
operational state. If the current state was
entered prior to the last re-initialization of the
agent then this object contains a zero value."
SYNTAX TimeTicks
AtmVorXOperStatus ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"The value determines the operational status of a
virtual link or cross-connect. The up and down
states indicate that the traffic flow is enabled
or disabled respectively on the virtual link or
cross-connect. The unknown state indicates that
the state of it cannot be determined. The state
will be down or unknown if the supporting ATM
interface(s) is down or unknown respectively."
SYNTAX INTEGER {
up(1),
down(2),
unknown(3)
}
-- OBJECT-IDENTITIES:
-- The following atmTrafficDescriptorTypes has been moved
-- from RFC1695 and no longer appear in the revision of
-- RFC1695[3].
atmTrafficDescriptorTypes OBJECT IDENTIFIER ::= {mib-2 37 1 1}
-- atmMIBObjects
-- See [3].
-- All other and new OBJECT IDENTITIES
-- are defined under the following subtree:
atmObjectIdentities OBJECT IDENTIFIER ::= {atmTCMIB 1}
-- The following values are defined for use as
-- possible values of the ATM traffic descriptor type.
atmNoTrafficDescriptor OBJECT-IDENTITY
STATUS deprecated
DESCRIPTION
"This identifies the no ATM traffic
descriptor type. Parameters 1, 2, 3, 4,
and 5 are not used. This traffic descriptor
type can be used for best effort traffic."
::= {atmTrafficDescriptorTypes 1}
atmNoClpNoScr OBJECT-IDENTITY
STATUS current
DESCRIPTION
"This traffic descriptor type is for no CLP
and no Sustained Cell Rate. The use of the
parameter vector for this type:
Parameter 1: peak cell rate in cells/second
for CLP=0+1 traffic
Parameter 2: not used
Parameter 3: not used
Parameter 4: not used
Parameter 5: not used."
REFERENCE
"ATM Forum,ATM User-Network Interface,
Version 3.0 (UNI 3.0) Specification, 1994.
ATM Forum, ATM User-Network Interface,
Version 3.1 (UNI 3.1) Specification,
November 1994."
::= {atmTrafficDescriptorTypes 2}
atmClpNoTaggingNoScr OBJECT-IDENTITY
STATUS deprecated
DESCRIPTION
"This traffic descriptor is for CLP without
tagging and no Sustained Cell Rate. The use
of the parameter vector for this type:
Parameter 1: peak cell rate in cells/second
for CLP=0+1 traffic
Parameter 2: peak cell rate in cells/second
for CLP=0 traffic
Parameter 3: not used
Parameter 4: not used
Parameter 5: not used."
::= {atmTrafficDescriptorTypes 3}
atmClpTaggingNoScr OBJECT-IDENTITY
STATUS deprecated
DESCRIPTION
"This traffic descriptor is for CLP with
tagging and no Sustained Cell Rate. The use
of the parameter vector for this type:
Parameter 1: peak cell rate in cells/second
for CLP=0+1 traffic
Parameter 2: peak cell rate in cells/second
for CLP=0 traffic, excess
tagged as CLP=1
Parameter 3: not used
Parameter 4: not used
Parameter 5: not used."
::= {atmTrafficDescriptorTypes 4}
atmNoClpScr OBJECT-IDENTITY
STATUS current
DESCRIPTION
"This traffic descriptor type is for no CLP
with Sustained Cell Rate. The use of the
parameter vector for this type:
Parameter 1: peak cell rate in cells/second
for CLP=0+1 traffic
Parameter 2: sustainable cell rate in cells/second
for CLP=0+1 traffic
Parameter 3: maximum burst size in cells
Parameter 4: not used
Parameter 5: not used."
REFERENCE
"ATM Forum,ATM User-Network Interface,
Version 3.0 (UNI 3.0) Specification, 1994.
ATM Forum, ATM User-Network Interface,
Version 3.1 (UNI 3.1) Specification,
November 1994."
::= {atmTrafficDescriptorTypes 5}
atmClpNoTaggingScr OBJECT-IDENTITY
STATUS current
DESCRIPTION
"This traffic descriptor type is for CLP with
Sustained Cell Rate and no tagging. The use
of the parameter vector for this type:
Parameter 1: peak cell rate in cells/second
for CLP=0+1 traffic
Parameter 2: sustainable cell rate in cells/second
for CLP=0 traffic
Parameter 3: maximum burst size in cells
Parameter 4: not used
Parameter 5: not used."
REFERENCE
"ATM Forum,ATM User-Network Interface,
Version 3.0 (UNI 3.0) Specification, 1994.
ATM Forum, ATM User-Network Interface,
Version 3.1 (UNI 3.1) Specification,
November 1994."
::= {atmTrafficDescriptorTypes 6}
atmClpTaggingScr OBJECT-IDENTITY
STATUS current
DESCRIPTION
"This traffic descriptor type is for CLP with
tagging and Sustained Cell Rate. The use of
the parameter vector for this type:
Parameter 1: peak cell rate in cells/second
for CLP=0+1 traffic
Parameter 2: sustainable cell rate in cells/second
for CLP=0 traffic, excess tagged as
CLP=1
Parameter 3: maximum burst size in cells
Parameter 4: not used
Parameter 5: not used."
REFERENCE
"ATM Forum,ATM User-Network Interface,
Version 3.0 (UNI 3.0) Specification, 1994.
ATM Forum, ATM User-Network Interface,
Version 3.1 (UNI 3.1) Specification,
November 1994."
::= {atmTrafficDescriptorTypes 7}
atmClpNoTaggingMcr OBJECT-IDENTITY
STATUS current
DESCRIPTION
"This traffic descriptor type is for CLP with
Minimum Cell Rate and no tagging. The use of
the parameter vector for this type:
Parameter 1: peak cell rate in cells/second
for CLP=0+1 traffic
Parameter 2: CDVT in tenths of microseconds
Parameter 3: minimum cell rate in cells/second
Parameter 4: unused
Parameter 5: unused."
REFERENCE
"ATM Forum,ATM User-Network Interface,
Version 3.0 (UNI 3.0) Specification, 1994.
ATM Forum, ATM User-Network Interface,
Version 3.1 (UNI 3.1) Specification,
November 1994."
::= {atmTrafficDescriptorTypes 8}
atmClpTransparentNoScr OBJECT-IDENTITY
STATUS current
DESCRIPTION
"This traffic descriptor type is for the CLP-
transparent model and no Sustained Cell Rate.
The use of the parameter vector for this type:
Parameter 1: peak cell rate in cells/second
for CLP=0+1 traffic
Parameter 2: CDVT in tenths of microseconds
Parameter 3: not used
Parameter 4: not used
Parameter 5: not used.
This traffic descriptor type is applicable to
connections following the CBR.1 conformance
definition.
Connections specifying this traffic descriptor
type will be rejected at UNI 3.0 or UNI 3.1
interfaces. For a similar traffic descriptor
type that can be accepted at UNI 3.0 and
UNI 3.1 interfaces, see atmNoClpNoScr."
REFERENCE
"ATM Forum,ATM User-Network Interface,
Version 3.0 (UNI 3.0) Specification, 1994.
ATM Forum, ATM User-Network Interface,
Version 3.1 (UNI 3.1) Specification,
November 1994.
ATM Forum, Traffic Management Specification,
Version 4.0, af-tm-0056.000, June 1996."
::= {atmTrafficDescriptorTypes 9}
atmClpTransparentScr OBJECT-IDENTITY
STATUS current
DESCRIPTION
"This traffic descriptor type is for the CLP-
transparent model with Sustained Cell Rate.
The use of the parameter vector for this type:
Parameter 1: peak cell rate in cells/second
for CLP=0+1 traffic
Parameter 2: sustainable cell rate in cells/second
for CLP=0+1 traffic
Parameter 3: maximum burst size in cells
Parameter 4: CDVT in tenths of microseconds
Parameter 5: not used.
This traffic descriptor type is applicable to
connections following the VBR.1 conformance
definition.
Connections specifying this traffic descriptor
type will be rejected at UNI 3.0 or UNI 3.1
interfaces. For a similar traffic descriptor
type that can be accepted at UNI 3.0 and
UNI 3.1 interfaces, see atmNoClpScr."
REFERENCE
"ATM Forum,ATM User-Network Interface,
Version 3.0 (UNI 3.0) Specification, 1994.
ATM Forum, ATM User-Network Interface,
Version 3.1 (UNI 3.1) Specification,
November 1994.
ATM Forum, Traffic Management Specification,
Version 4.0, af-tm-0056.000, June 1996."
::= {atmTrafficDescriptorTypes 10}
atmNoClpTaggingNoScr OBJECT-IDENTITY
STATUS current
DESCRIPTION
"This traffic descriptor type is for no CLP
with tagging and no Sustained Cell Rate. The
use of the parameter vector for this type:
Parameter 1: peak cell rate in cells/second
for CLP=0+1 traffic
Parameter 2: CDVT in tenths of microseconds
Parameter 3: not used
Parameter 4: not used
Parameter 5: not used.
This traffic descriptor type is applicable to
connections following the UBR.2 conformance
definition ."
REFERENCE
"ATM Forum,ATM User-Network Interface,
Version 3.0 (UNI 3.0) Specification, 1994.
ATM Forum, ATM User-Network Interface,
Version 3.1 (UNI 3.1) Specification,
November 1994.
ATM Forum, Traffic Management Specification,
Version 4.0, af-tm-0056.000, June 1996."
::= {atmTrafficDescriptorTypes 11}
atmNoClpNoScrCdvt OBJECT-IDENTITY
STATUS current
DESCRIPTION
"This traffic descriptor type is for no CLP
and no Sustained Cell Rate. The use of the
parameter vector for this type:
Parameter 1: peak cell rate in cells/second
for CLP=0+1 traffic
Parameter 2: CDVT in tenths of microseconds
Parameter 3: not used
Parameter 4: not used
Parameter 5: not used.
This traffic descriptor type is applicable to
CBR connections following the UNI 3.0/3.1
conformance definition for PCR CLP=0+1.
These CBR connections differ from CBR.1
connections in that the CLR objective
applies only to the CLP=0 cell flow.
This traffic descriptor type is also
applicable to connections following the UBR.1
conformance definition."
REFERENCE
"ATM Forum,ATM User-Network Interface,
Version 3.0 (UNI 3.0) Specification, 1994.
ATM Forum, ATM User-Network Interface,
Version 3.1 (UNI 3.1) Specification,
November 1994.
ATM Forum, Traffic Management Specification,
Version 4.0, af-tm-0056.000, June 1996."
::= {atmTrafficDescriptorTypes 12}
atmNoClpScrCdvt OBJECT-IDENTITY
STATUS current
DESCRIPTION
"This traffic descriptor type is for no CLP
with Sustained Cell Rate. The use of the
parameter vector for this type:
Parameter 1: peak cell rate in cells/second
for CLP=0+1 traffic
Parameter 2: sustainable cell rate in cells/second
for CLP=0+1 traffic
Parameter 3: maximum burst size in cells
Parameter 4: CDVT in tenths of microseconds
Parameter 5: not used.
This traffic descriptor type is applicable
to VBR connections following the UNI 3.0/3.1
conformance definition for PCR CLP=0+1 and
SCR CLP=0+1. These VBR connections
differ from VBR.1 connections in that
the CLR objective applies only to the CLP=0
cell flow."
REFERENCE
"ATM Forum,ATM User-Network Interface,
Version 3.0 (UNI 3.0) Specification, 1994.
ATM Forum, ATM User-Network Interface,
Version 3.1 (UNI 3.1) Specification,
November 1994.
ATM Forum, Traffic Management Specification,
Version 4.0, af-tm-0056.000, June 1996."
::= {atmTrafficDescriptorTypes 13}
atmClpNoTaggingScrCdvt OBJECT-IDENTITY
STATUS current
DESCRIPTION
"This traffic descriptor type is for CLP with
Sustained Cell Rate and no tagging. The use
of the parameter vector for this type:
Parameter 1: peak cell rate in cells/second
for CLP=0+1 traffic
Parameter 2: sustainable cell rate in cells/second
for CLP=0 traffic
Parameter 3: maximum burst size in cells
Parameter 4: CDVT in tenths of microseconds
Parameter 5: not used.
This traffic descriptor type is applicable to
connections following the VBR.2 conformance
definition."
REFERENCE
"ATM Forum,ATM User-Network Interface,
Version 3.0 (UNI 3.0) Specification, 1994.
ATM Forum, ATM User-Network Interface,
Version 3.1 (UNI 3.1) Specification,
November 1994.
ATM Forum, Traffic Management Specification,
Version 4.0, af-tm-0056.000, June 1996."
::= {atmTrafficDescriptorTypes 14}
atmClpTaggingScrCdvt OBJECT-IDENTITY
STATUS current
DESCRIPTION
"This traffic descriptor type is for CLP with
tagging and Sustained Cell Rate. The use of
the parameter vector for this type:
Parameter 1: peak cell rate in cells/second
for CLP=0+1 traffic
Parameter 2: sustainable cell rate in cells/second
for CLP=0 traffic, excess tagged as
CLP=1
Parameter 3: maximum burst size in cells
Parameter 4: CDVT in tenths of microseconds
Parameter 5: not used.
This traffic descriptor type is applicable to
connections following the VBR.3 conformance
definition."
REFERENCE
"ATM Forum,ATM User-Network Interface,
Version 3.0 (UNI 3.0) Specification, 1994.
ATM Forum, ATM User-Network Interface,
Version 3.1 (UNI 3.1) Specification,
November 1994.
ATM Forum, Traffic Management Specification,
Version 4.0, af-tm-0056.000, June 1996."
::= {atmTrafficDescriptorTypes 15}
END

1271
priv/mibs/BGP4-MIB Normal file
View file

File diff suppressed because it is too large Load diff

66
priv/mibs/BGP4V2-TC-MIB Normal file
View file

@ -0,0 +1,66 @@
BGP4V2-TC-MIB DEFINITIONS ::= BEGIN
IMPORTS
mib-2, MODULE-IDENTITY FROM SNMPv2-SMI
TEXTUAL-CONVENTION FROM SNMPv2-TC;
bgp4V2TC MODULE-IDENTITY
LAST-UPDATED "201002010000Z"
ORGANIZATION "IETF IDR Working Group"
CONTACT-INFO "E-mail: idr@ietf.org"
DESCRIPTION
"Textual conventions for BGP-4.
Copyright (C) The IETF Trust (2010). This
version of this MIB module is part of RFC XXX;
see the RFC itself for full legal notices."
-- RFC Editor - replace XXX with RFC number
REVISION "201002010000Z"
DESCRIPTION
"Initial version."
::= { mib-2 100}
--
-- Textual Conventions
--
Bgp4V2IdentifierTC ::= TEXTUAL-CONVENTION
DISPLAY-HINT "1d."
STATUS current
DESCRIPTION
"The representation of a BGP Identifier. BGP Identifiers
are presented in the received network byte order.
The BGP Identifier is displayed as if it is an IP address,
even if it would be an illegal one."
REFERENCE
"RFC 4273, Section 4.2"
SYNTAX OCTET STRING(SIZE (4))
Bgp4V2AddressFamilyIdentifierTC ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"The representation of a BGP AFI. The value of this object
should be restricted to be between the values of 0 and 65535."
REFERENCE
"RFC 4760, Section 3"
SYNTAX INTEGER {
ipv4(1),
ipv6(2)
}
Bgp4V2SubsequentAddressFamilyIdentifierTC ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"The representation of a BGP SAFI"
REFERENCE
"RFC 4760, Section 3. The value of this object should be
restricted to be between the values of 0 and 255."
SYNTAX INTEGER {
unicast(1),
multicast(2),
mpls(4)
}
END

1472
priv/mibs/BRIDGE-MIB Normal file
View file

File diff suppressed because it is too large Load diff

2503
priv/mibs/CAPWAP-BASE-MIB-draft06 Normal file
View file

File diff suppressed because it is too large Load diff

1289
priv/mibs/DIAL-CONTROL-MIB Normal file
View file

File diff suppressed because it is too large Load diff

68
priv/mibs/DIFFSERV-DSCP-TC Normal file
View file

@ -0,0 +1,68 @@
DIFFSERV-DSCP-TC DEFINITIONS ::= BEGIN
IMPORTS
Integer32, MODULE-IDENTITY, mib-2
FROM SNMPv2-SMI
TEXTUAL-CONVENTION
FROM SNMPv2-TC;
diffServDSCPTC MODULE-IDENTITY
LAST-UPDATED "200205090000Z"
ORGANIZATION "IETF Differentiated Services WG"
CONTACT-INFO
" Fred Baker
Cisco Systems
1121 Via Del Rey
Santa Barbara, CA 93117, USA
E-mail: fred@cisco.com
Kwok Ho Chan
Nortel Networks
600 Technology Park Drive
Billerica, MA 01821, USA
E-mail: khchan@nortelnetworks.com
Andrew Smith
Harbour Networks
Jiuling Building
21 North Xisanhuan Ave.
Beijing, 100089, PRC
E-mail: ah_smith@acm.org
Differentiated Services Working Group:
diffserv@ietf.org"
DESCRIPTION
"The Textual Conventions defined in this module should be used
whenever a Differentiated Services Code Point is used in a MIB."
REVISION "200205090000Z"
DESCRIPTION
"Initial version, published as RFC 3289."
::= { mib-2 96 }
Dscp ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d"
STATUS current
DESCRIPTION
"A Differentiated Services Code-Point that may be used for
marking a traffic stream."
REFERENCE
"RFC 2474, RFC 2780"
SYNTAX Integer32 (0..63)
DscpOrAny ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d"
STATUS current
DESCRIPTION
"The IP header Differentiated Services Code-Point that may be
used for discriminating among traffic streams. The value -1 is
used to indicate a wild card i.e. any value."
REFERENCE
"RFC 2474, RFC 2780"
SYNTAX Integer32 (-1 | 0..63)
END

3704
priv/mibs/DIFFSERV-MIB Normal file
View file

File diff suppressed because it is too large Load diff

1882
priv/mibs/DISMAN-EVENT-MIB Normal file
View file

File diff suppressed because it is too large Load diff

509
priv/mibs/DISMAN-NSLOOKUP-MIB Normal file
View file

@ -0,0 +1,509 @@
DISMAN-NSLOOKUP-MIB DEFINITIONS ::= BEGIN
IMPORTS
MODULE-IDENTITY, OBJECT-TYPE,
Unsigned32, mib-2, Integer32
FROM SNMPv2-SMI -- RFC2578
RowStatus
FROM SNMPv2-TC -- RFC2579
MODULE-COMPLIANCE, OBJECT-GROUP
FROM SNMPv2-CONF -- RFC2580
SnmpAdminString
FROM SNMP-FRAMEWORK-MIB -- RFC3411
InetAddressType, InetAddress
FROM INET-ADDRESS-MIB; -- RFC4001
lookupMIB MODULE-IDENTITY
LAST-UPDATED "200606130000Z" -- 13 June 2006
ORGANIZATION "IETF Distributed Management Working Group"
CONTACT-INFO
"Juergen Quittek
NEC Europe Ltd.
Network Laboratories
Kurfuersten-Anlage 36
69115 Heidelberg
Germany
Phone: +49 6221 4342-115
Email: quittek@netlab.nec.de"
DESCRIPTION
"The Lookup MIB (DISMAN-NSLOOKUP-MIB) enables determination
of either the name(s) corresponding to a host address or of
the address(es) associated with a host name at a remote
host.
Copyright (C) The Internet Society (2006). This version of
this MIB module is part of RFC 4560; see the RFC itself for
full legal notices."
-- Revision history
REVISION "200606130000Z" -- 13 June 2006
DESCRIPTION
"Updated version, published as RFC 4560.
- Replaced references to RFC 2575 by RFC 3415
- Replaced references to RFC 2571 by RFC 3411
- Replaced references to RFC 2851 by RFC 4001
- Added value enabled(1) to SYNTAX clause of
lookupCtlOperStatus
- Added lookupMinimumCompliance
- Defined semantics of value 0 for object
lookupPurgeTime
- Added DEFVAL { unknown } to object
lookupCtlTargetAddressType OBJECT-TYPE"
REVISION "200009210000Z" -- 21 September 2000
DESCRIPTION
"Initial version, published as RFC 2925."
::= { mib-2 82 }
-- Top level structure of the MIB
lookupObjects OBJECT IDENTIFIER ::= { lookupMIB 1 }
lookupConformance OBJECT IDENTIFIER ::= { lookupMIB 2 }
-- Simple Object Definitions
lookupMaxConcurrentRequests OBJECT-TYPE
SYNTAX Unsigned32
UNITS "requests"
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The maximum number of concurrent active lookup requests
that are allowed within an agent implementation. A value
of 0 for this object implies that there is no limit for
the number of concurrent active requests in effect.
The limit applies only to new requests being activated.
When a new value is set, the agent will continue processing
all the requests already active, even if their number
exceed the limit just imposed."
DEFVAL { 10 }
::= { lookupObjects 1 }
lookupPurgeTime OBJECT-TYPE
SYNTAX Unsigned32 (0..86400)
UNITS "seconds"
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The amount of time to wait before automatically
deleting an entry in the lookupCtlTable and any
dependent lookupResultsTable entries
after the lookup operation represented by a
lookupCtlEntry has been completed.
A lookupCtEntry is considered complete
when its lookupCtlOperStatus object has a
value of completed(3).
A value of 0 indicates that automatic deletion
of entries is disabled."
DEFVAL { 900 } -- 15 minutes as default
::= { lookupObjects 2 }
-- Lookup Control Table
lookupCtlTable OBJECT-TYPE
SYNTAX SEQUENCE OF LookupCtlEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Defines the Lookup Control Table for providing
the capability of performing a lookup operation
for a symbolic host name or for a host address
from a remote host."
::= { lookupObjects 3 }
lookupCtlEntry OBJECT-TYPE
SYNTAX LookupCtlEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Defines an entry in the lookupCtlTable. A
lookupCtlEntry is initially indexed by
lookupCtlOwnerIndex, which is a type of SnmpAdminString,
a textual convention that allows for the use of the SNMPv3
View-Based Access Control Model (RFC 3415, VACM)
and that also allows a management application to identify
its entries. The second index element,
lookupCtlOperationName, enables the same
lookupCtlOwnerIndex entity to have multiple outstanding
requests. The value of lookupCtlTargetAddressType
determines which lookup function to perform."
INDEX {
lookupCtlOwnerIndex,
lookupCtlOperationName
}
::= { lookupCtlTable 1 }
LookupCtlEntry ::=
SEQUENCE {
lookupCtlOwnerIndex SnmpAdminString,
lookupCtlOperationName SnmpAdminString,
lookupCtlTargetAddressType InetAddressType,
lookupCtlTargetAddress InetAddress,
lookupCtlOperStatus INTEGER,
lookupCtlTime Unsigned32,
lookupCtlRc Integer32,
lookupCtlRowStatus RowStatus
}
lookupCtlOwnerIndex OBJECT-TYPE
SYNTAX SnmpAdminString (SIZE(0..32))
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"To facilitate the provisioning of access control by a
security administrator using the View-Based Access
Control Model (RFC 2575, VACM) for tables in which
multiple users may need to create or
modify entries independently, the initial index is used as
an 'owner index'. Such an initial index has a syntax of
SnmpAdminString and can thus be trivially mapped to a
securityName or groupName defined in VACM, in
accordance with a security policy.
When used in conjunction with such a security policy all
entries in the table belonging to a particular user (or
group) will have the same value for this initial index.
For a given user's entries in a particular table, the
object identifiers for the information in these entries
will have the same subidentifiers (except for the
'column' subidentifier) up to the end of the encoded
owner index. To configure VACM to permit access to this
portion of the table, one would create
vacmViewTreeFamilyTable entries with the value of
vacmViewTreeFamilySubtree including the owner index
portion, and vacmViewTreeFamilyMask 'wildcarding' the
column subidentifier. More elaborate configurations
are possible."
::= { lookupCtlEntry 1 }
lookupCtlOperationName OBJECT-TYPE
SYNTAX SnmpAdminString (SIZE(0..32))
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The name of a lookup operation. This is locally unique,
within the scope of an lookupCtlOwnerIndex."
::= { lookupCtlEntry 2 }
lookupCtlTargetAddressType OBJECT-TYPE
SYNTAX InetAddressType
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Specifies the type of address for performing a
lookup operation for a symbolic host name or for a host
address from a remote host.
Specification of dns(16) as the value for this object
means that a function such as, for example, getaddrinfo()
or gethostbyname() should be performed to return one or
more numeric addresses. Use of a value of either ipv4(1)
or ipv6(2) means that a functions such as, for example,
getnameinfo() or gethostbyaddr() should be used to return
the symbolic names associated with a host."
DEFVAL { unknown }
::= { lookupCtlEntry 3 }
lookupCtlTargetAddress OBJECT-TYPE
SYNTAX InetAddress
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Specifies the address used for a resolver lookup at a
remote host. The corresponding lookupCtlTargetAddressType
objects determines its type, as well as the function
that can be requested.
A value for this object MUST be set prior to
transitioning its corresponding lookupCtlEntry to
active(1) via lookupCtlRowStatus."
::= { lookupCtlEntry 4 }
lookupCtlOperStatus OBJECT-TYPE
SYNTAX INTEGER {
enabled(1), -- operation is active
notStarted(2), -- operation has not started
completed(3) -- operation is done
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Reflects the operational state of an lookupCtlEntry:
enabled(1) - Operation is active.
notStarted(2) - Operation has not been enabled.
completed(3) - Operation has been completed.
An operation is automatically enabled(1) when its
lookupCtlRowStatus object is transitioned to active(1)
status. Until this occurs, lookupCtlOperStatus MUST
report a value of notStarted(2). After the lookup
operation is completed (success or failure), the value
for lookupCtlOperStatus MUST be transitioned to
completed(3)."
::= { lookupCtlEntry 5 }
lookupCtlTime OBJECT-TYPE
SYNTAX Unsigned32
UNITS "milliseconds"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Reports the number of milliseconds that a lookup
operation required to be completed at a remote host.
Completed means operation failure as well as
success."
::= { lookupCtlEntry 6 }
lookupCtlRc OBJECT-TYPE
SYNTAX Integer32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The system-specific return code from a lookup
operation. All implementations MUST return a value
of 0 for this object when the remote lookup
operation succeeds. A non-zero value for this
objects indicates failure. It is recommended that
implementations return the error codes that are
generated by the lookup function used."
::= { lookupCtlEntry 7 }
lookupCtlRowStatus OBJECT-TYPE
SYNTAX RowStatus
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This object allows entries to be created and deleted
in the lookupCtlTable.
A remote lookup operation is started when an
entry in this table is created via an SNMP set
request and the entry is activated. This
occurs by setting the value of this object
to CreateAndGo(4) during row creation or
by setting this object to active(1) after
the row is created.
A value MUST be specified for lookupCtlTargetAddress
prior to the acceptance of a transition to active(1) state.
A remote lookup operation starts when its entry
first becomes active(1). Transitions in and
out of active(1) state have no effect on the
operational behavior of a remote lookup
operation, with the exception that deletion of
an entry in this table by setting its RowStatus
object to destroy(6) will stop an active
remote lookup operation.
The operational state of a remote lookup operation
can be determined by examination of its
lookupCtlOperStatus object."
REFERENCE
"See definition of RowStatus in RFC 2579,
'Textual Conventions for SMIv2.'"
::= { lookupCtlEntry 8 }
-- Lookup Results Table
lookupResultsTable OBJECT-TYPE
SYNTAX SEQUENCE OF LookupResultsEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Defines the Lookup Results Table for providing
the capability of determining the results of a
operation at a remote host.
One or more entries are added to the
lookupResultsTable when a lookup operation,
as reflected by an lookupCtlEntry, is completed
successfully. All entries related to a
successful lookup operation MUST be added
to the lookupResultsTable at the same time
that the associating lookupCtlOperStatus
object is transitioned to completed(2).
The number of entries added depends on the
results determined for a particular lookup
operation. All entries associated with an
lookupCtlEntry are removed when the
lookupCtlEntry is deleted.
A remote host can be multi-homed and have more than one IP
address associated with it (returned by lookup function),
or it can have more than one symbolic name (returned
by lookup function).
A function such as, for example, getnameinfo() or
gethostbyaddr() is called with a host address as its
parameter and is used primarily to determine a symbolic
name to associate with the host address. Entries in the
lookupResultsTable MUST be made for each host name
returned. If the function identifies an 'official host
name,' then this symbolic name MUST be assigned a
lookupResultsIndex of 1.
A function such as, for example, getaddrinfo() or
gethostbyname() is called with a symbolic host name and is
used primarily to retrieve a host address. The entries
MUST be stored in the order that they are retrieved from
the lookup function. lookupResultsIndex 1 MUST be
assigned to the first entry."
::= { lookupObjects 4 }
lookupResultsEntry OBJECT-TYPE
SYNTAX LookupResultsEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Defines an entry in the lookupResultsTable. The
first two index elements identify the
lookupCtlEntry that a lookupResultsEntry belongs
to. The third index element selects a single
lookup operation result."
INDEX {
lookupCtlOwnerIndex,
lookupCtlOperationName,
lookupResultsIndex
}
::= { lookupResultsTable 1 }
LookupResultsEntry ::=
SEQUENCE {
lookupResultsIndex Unsigned32,
lookupResultsAddressType InetAddressType,
lookupResultsAddress InetAddress
}
lookupResultsIndex OBJECT-TYPE
SYNTAX Unsigned32 (1..'ffffffff'h)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Entries in the lookupResultsTable are created when
the result of a lookup operation is determined.
Entries MUST be stored in the lookupResultsTable in
the order that they are retrieved. Values assigned
to lookupResultsIndex MUST start at 1 and increase
consecutively."
::= { lookupResultsEntry 1 }
lookupResultsAddressType OBJECT-TYPE
SYNTAX InetAddressType
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Indicates the type of result of a remote lookup
operation. A value of unknown(0) implies either that
the operation hasn't been started or that
it has failed."
::= { lookupResultsEntry 2 }
lookupResultsAddress OBJECT-TYPE
SYNTAX InetAddress
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Reflects a result for a remote lookup operation
as per the value of lookupResultsAddressType.
The address type (InetAddressType) that relates to
this object is specified by the corresponding value
of lookupResultsAddress."
::= { lookupResultsEntry 3 }
-- Conformance information
-- Compliance statements
lookupCompliances OBJECT IDENTIFIER ::= { lookupConformance 1 }
lookupGroups OBJECT IDENTIFIER ::= { lookupConformance 2 }
-- Compliance statements
lookupCompliance MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"The compliance statement for SNMP entities that
fully implement the DISMAN-NSLOOKUP-MIB."
MODULE -- this module
MANDATORY-GROUPS { lookupGroup }
OBJECT lookupMaxConcurrentRequests
MIN-ACCESS read-only
DESCRIPTION
"The agent is not required to support set
operations to this object."
OBJECT lookupPurgeTime
MIN-ACCESS read-only
DESCRIPTION
"The agent is not required to support a set
operation to this object."
::= { lookupCompliances 1 }
lookupMinimumCompliance MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"The minimum compliance statement for SNMP entities
that implement the minimal subset of the
DISMAN-NSLOOKUP-MIB. Implementors might choose this
subset for small devices with limited resources."
MODULE -- this module
MANDATORY-GROUPS { lookupGroup }
OBJECT lookupMaxConcurrentRequests
MIN-ACCESS read-only
DESCRIPTION
"The agent is not required to support set
operations to this object."
OBJECT lookupPurgeTime
MIN-ACCESS read-only
DESCRIPTION
"The agent is not required to support a set
operation to this object."
OBJECT lookupCtlRowStatus
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required. If write access is
not supported, then at least one entry in the
lookupCtlTable MUST be established already when the SNMP
agent starts offering access to the NSLOOKUP-MIB module.
If, in such a case, only a single entry is offered, then
it is RECOMMENDED that this entry use strings with a
length of 0 for both of its two index objects."
::= { lookupCompliances 2 }
-- MIB groupings
lookupGroup OBJECT-GROUP
OBJECTS {
lookupMaxConcurrentRequests,
lookupPurgeTime,
lookupCtlOperStatus,
lookupCtlTargetAddressType,
lookupCtlTargetAddress,
lookupCtlTime,
lookupCtlRc,
lookupCtlRowStatus,
lookupResultsAddressType,
lookupResultsAddress
}
STATUS current
DESCRIPTION
"The group of objects that constitute the remote
Lookup operation."
::= { lookupGroups 1 }
END

1561
priv/mibs/DISMAN-PING-MIB Normal file
View file

File diff suppressed because it is too large Load diff

699
priv/mibs/DISMAN-SCHEDULE-MIB Normal file
View file

@ -0,0 +1,699 @@
DISMAN-SCHEDULE-MIB DEFINITIONS ::= BEGIN
IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE,
Integer32, Unsigned32, Counter32, mib-2, zeroDotZero
FROM SNMPv2-SMI
TEXTUAL-CONVENTION,
DateAndTime, RowStatus, StorageType, VariablePointer
FROM SNMPv2-TC
MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP
FROM SNMPv2-CONF
SnmpAdminString
FROM SNMP-FRAMEWORK-MIB;
schedMIB MODULE-IDENTITY
LAST-UPDATED "200201070000Z"
ORGANIZATION "IETF Distributed Management Working Group"
CONTACT-INFO
"WG EMail: disman@dorothy.bmc.com
Subscribe: disman-request@dorothy.bmc.com
Chair: Randy Presuhn
BMC Software, Inc.
Postal: Office 1-3141
2141 North First Street
San Jose, California 95131
USA
EMail: rpresuhn@bmc.com
Phone: +1 408 546-1006
Editor: David B. Levi
Nortel Networks
Postal: 4401 Great America Parkway
Santa Clara, CA 95052-8185
USA
EMail: dlevi@nortelnetworks.com
Phone: +1 865 686 0432
Editor: Juergen Schoenwaelder
TU Braunschweig
Postal: Bueltenweg 74/75
38106 Braunschweig
Germany
EMail: schoenw@ibr.cs.tu-bs.de
Phone: +49 531 391-3283"
DESCRIPTION
"This MIB module defines a MIB which provides mechanisms to
schedule SNMP set operations periodically or at specific
points in time."
REVISION "200201070000Z"
DESCRIPTION
"Revised version, published as RFC 3231.
This revision introduces a new object type called
schedTriggers. Created new conformance and compliance
statements that take care of the new schedTriggers object.
Several clarifications have been added to remove ambiguities
that were discovered and reported by implementors."
REVISION "199811171800Z"
DESCRIPTION
"Initial version, published as RFC 2591."
::= { mib-2 63 }
--
-- The various groups defined within this MIB definition:
--
schedObjects OBJECT IDENTIFIER ::= { schedMIB 1 }
schedNotifications OBJECT IDENTIFIER ::= { schedMIB 2 }
schedConformance OBJECT IDENTIFIER ::= { schedMIB 3 }
--
-- Textual Conventions:
--
SnmpPduErrorStatus ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"This TC enumerates the SNMPv1 and SNMPv2 PDU error status
codes as defined in RFC 1157 and RFC 1905. It also adds a
pseudo error status code `noResponse' which indicates a
timeout condition."
SYNTAX INTEGER {
noResponse(-1),
noError(0),
tooBig(1),
noSuchName(2),
badValue(3),
readOnly(4),
genErr(5),
noAccess(6),
wrongType(7),
wrongLength(8),
wrongEncoding(9),
wrongValue(10),
noCreation(11),
inconsistentValue(12),
resourceUnavailable(13),
commitFailed(14),
undoFailed(15),
authorizationError(16),
notWritable(17),
inconsistentName(18)
}
--
-- Some scalars which provide information about the local time zone.
--
schedLocalTime OBJECT-TYPE
SYNTAX DateAndTime (SIZE (11))
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The local time used by the scheduler. Schedules which
refer to calendar time will use the local time indicated
by this object. An implementation MUST return all 11 bytes
of the DateAndTime textual-convention so that a manager
may retrieve the offset from GMT time."
::= { schedObjects 1 }
--
-- The schedule table which controls the scheduler.
--
schedTable OBJECT-TYPE
SYNTAX SEQUENCE OF SchedEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table defines scheduled actions triggered by
SNMP set operations."
::= { schedObjects 2 }
schedEntry OBJECT-TYPE
SYNTAX SchedEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry describing a particular scheduled action.
Unless noted otherwise, writable objects of this row
can be modified independent of the current value of
schedRowStatus, schedAdminStatus and schedOperStatus.
In particular, it is legal to modify schedInterval
and the objects in the schedCalendarGroup when
schedRowStatus is active and schedAdminStatus and
schedOperStatus are both enabled."
INDEX { schedOwner, schedName }
::= { schedTable 1 }
SchedEntry ::= SEQUENCE {
schedOwner SnmpAdminString,
schedName SnmpAdminString,
schedDescr SnmpAdminString,
schedInterval Unsigned32,
schedWeekDay BITS,
schedMonth BITS,
schedDay BITS,
schedHour BITS,
schedMinute BITS,
schedContextName SnmpAdminString,
schedVariable VariablePointer,
schedValue Integer32,
schedType INTEGER,
schedAdminStatus INTEGER,
schedOperStatus INTEGER,
schedFailures Counter32,
schedLastFailure SnmpPduErrorStatus,
schedLastFailed DateAndTime,
schedStorageType StorageType,
schedRowStatus RowStatus,
schedTriggers Counter32
}
schedOwner OBJECT-TYPE
SYNTAX SnmpAdminString (SIZE(0..32))
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The owner of this scheduling entry. The exact semantics of
this string are subject to the security policy defined by
the security administrator."
::= { schedEntry 1 }
schedName OBJECT-TYPE
SYNTAX SnmpAdminString (SIZE(1..32))
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The locally-unique, administratively assigned name for this
scheduling entry. This object allows a schedOwner to have
multiple entries in the schedTable."
::= { schedEntry 2 }
schedDescr OBJECT-TYPE
SYNTAX SnmpAdminString
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The human readable description of the purpose of this
scheduling entry."
DEFVAL { "" }
::= { schedEntry 3 }
schedInterval OBJECT-TYPE
SYNTAX Unsigned32
UNITS "seconds"
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The number of seconds between two action invocations of
a periodic scheduler. Implementations must guarantee
that action invocations will not occur before at least
schedInterval seconds have passed.
The scheduler must ignore all periodic schedules that
have a schedInterval value of 0. A periodic schedule
with a scheduling interval of 0 seconds will therefore
never invoke an action.
Implementations may be forced to delay invocations in the
face of local constraints. A scheduled management function
should therefore not rely on the accuracy provided by the
scheduler implementation.
Note that implementations which maintain a list of pending
activations must re-calculate them when this object is
changed."
DEFVAL { 0 }
::= { schedEntry 4 }
schedWeekDay OBJECT-TYPE
SYNTAX BITS {
sunday(0),
monday(1),
tuesday(2),
wednesday(3),
thursday(4),
friday(5),
saturday(6)
}
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The set of weekdays on which the scheduled action should
take place. Setting multiple bits will include several
weekdays in the set of possible weekdays for this schedule.
Setting all bits will cause the scheduler to ignore the
weekday.
Note that implementations which maintain a list of pending
activations must re-calculate them when this object is
changed."
DEFVAL { {} }
::= { schedEntry 5 }
schedMonth OBJECT-TYPE
SYNTAX BITS {
january(0),
february(1),
march(2),
april(3),
may(4),
june(5),
july(6),
august(7),
september(8),
october(9),
november(10),
december(11)
}
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The set of months during which the scheduled action should
take place. Setting multiple bits will include several
months in the set of possible months for this schedule.
Setting all bits will cause the scheduler to ignore the
month.
Note that implementations which maintain a list of pending
activations must re-calculate them when this object is
changed."
DEFVAL { {} }
::= { schedEntry 6 }
schedDay OBJECT-TYPE
SYNTAX BITS {
d1(0), d2(1), d3(2), d4(3), d5(4),
d6(5), d7(6), d8(7), d9(8), d10(9),
d11(10), d12(11), d13(12), d14(13), d15(14),
d16(15), d17(16), d18(17), d19(18), d20(19),
d21(20), d22(21), d23(22), d24(23), d25(24),
d26(25), d27(26), d28(27), d29(28), d30(29),
d31(30),
r1(31), r2(32), r3(33), r4(34), r5(35),
r6(36), r7(37), r8(38), r9(39), r10(40),
r11(41), r12(42), r13(43), r14(44), r15(45),
r16(46), r17(47), r18(48), r19(49), r20(50),
r21(51), r22(52), r23(53), r24(54), r25(55),
r26(56), r27(57), r28(58), r29(59), r30(60),
r31(61)
}
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The set of days in a month on which a scheduled action
should take place. There are two sets of bits one can
use to define the day within a month:
Enumerations starting with the letter 'd' indicate a
day in a month relative to the first day of a month.
The first day of the month can therefore be specified
by setting the bit d1(0) and d31(30) means the last
day of a month with 31 days.
Enumerations starting with the letter 'r' indicate a
day in a month in reverse order, relative to the last
day of a month. The last day in the month can therefore
be specified by setting the bit r1(31) and r31(61) means
the first day of a month with 31 days.
Setting multiple bits will include several days in the set
of possible days for this schedule. Setting all bits will
cause the scheduler to ignore the day within a month.
Setting all bits starting with the letter 'd' or the
letter 'r' will also cause the scheduler to ignore the
day within a month.
Note that implementations which maintain a list of pending
activations must re-calculate them when this object is
changed."
DEFVAL { {} }
::= { schedEntry 7 }
schedHour OBJECT-TYPE
SYNTAX BITS {
h0(0), h1(1), h2(2), h3(3), h4(4),
h5(5), h6(6), h7(7), h8(8), h9(9),
h10(10), h11(11), h12(12), h13(13), h14(14),
h15(15), h16(16), h17(17), h18(18), h19(19),
h20(20), h21(21), h22(22), h23(23)
}
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The set of hours within a day during which the scheduled
action should take place.
Note that implementations which maintain a list of pending
activations must re-calculate them when this object is
changed."
DEFVAL { {} }
::= { schedEntry 8 }
schedMinute OBJECT-TYPE
SYNTAX BITS {
m0(0), m1(1), m2(2), m3(3), m4(4),
m5(5), m6(6), m7(7), m8(8), m9(9),
m10(10), m11(11), m12(12), m13(13), m14(14),
m15(15), m16(16), m17(17), m18(18), m19(19),
m20(20), m21(21), m22(22), m23(23), m24(24),
m25(25), m26(26), m27(27), m28(28), m29(29),
m30(30), m31(31), m32(32), m33(33), m34(34),
m35(35), m36(36), m37(37), m38(38), m39(39),
m40(40), m41(41), m42(42), m43(43), m44(44),
m45(45), m46(46), m47(47), m48(48), m49(49),
m50(50), m51(51), m52(52), m53(53), m54(54),
m55(55), m56(56), m57(57), m58(58), m59(59)
}
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The set of minutes within an hour when the scheduled action
should take place.
Note that implementations which maintain a list of pending
activations must re-calculate them when this object is
changed."
DEFVAL { {} }
::= { schedEntry 9 }
schedContextName OBJECT-TYPE
SYNTAX SnmpAdminString (SIZE(0..32))
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The context which contains the local MIB variable pointed
to by schedVariable."
DEFVAL { "" }
::= { schedEntry 10 }
schedVariable OBJECT-TYPE
SYNTAX VariablePointer
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"An object identifier pointing to a local MIB variable
which resolves to an ASN.1 primitive type of INTEGER."
DEFVAL { zeroDotZero }
::= { schedEntry 11 }
schedValue OBJECT-TYPE
SYNTAX Integer32
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The value which is written to the MIB object pointed to by
schedVariable when the scheduler invokes an action. The
implementation shall enforce the use of access control
rules when performing the set operation on schedVariable.
This is accomplished by calling the isAccessAllowed abstract
service interface as defined in RFC 2571.
Note that an implementation may choose to issue an SNMP Set
message to the SNMP engine and leave the access control
decision to the normal message processing procedure."
DEFVAL { 0 }
::= { schedEntry 12 }
schedType OBJECT-TYPE
SYNTAX INTEGER {
periodic(1),
calendar(2),
oneshot(3)
}
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The type of this schedule. The value periodic(1) indicates
that this entry specifies a periodic schedule. A periodic
schedule is defined by the value of schedInterval. The
values of schedWeekDay, schedMonth, schedDay, schedHour
and schedMinute are ignored.
The value calendar(2) indicates that this entry describes a
calendar schedule. A calendar schedule is defined by the
values of schedWeekDay, schedMonth, schedDay, schedHour and
schedMinute. The value of schedInterval is ignored. A
calendar schedule will trigger on all local times that
satisfy the bits set in schedWeekDay, schedMonth, schedDay,
schedHour and schedMinute.
The value oneshot(3) indicates that this entry describes a
one-shot schedule. A one-shot schedule is similar to a
calendar schedule with the additional feature that it
disables itself by changing in the `finished'
schedOperStatus once the schedule triggers an action.
Note that implementations which maintain a list of pending
activations must re-calculate them when this object is
changed."
DEFVAL { periodic }
::= { schedEntry 13 }
schedAdminStatus OBJECT-TYPE
SYNTAX INTEGER {
enabled(1),
disabled(2)
}
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The desired state of the schedule."
DEFVAL { disabled }
::= { schedEntry 14 }
schedOperStatus OBJECT-TYPE
SYNTAX INTEGER {
enabled(1),
disabled(2),
finished(3)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The current operational state of this schedule. The state
enabled(1) indicates this entry is active and that the
scheduler will invoke actions at appropriate times. The
disabled(2) state indicates that this entry is currently
inactive and ignored by the scheduler. The finished(3)
state indicates that the schedule has ended. Schedules
in the finished(3) state are ignored by the scheduler.
A one-shot schedule enters the finished(3) state when it
deactivates itself.
Note that the operational state must not be enabled(1)
when the schedRowStatus is not active."
::= { schedEntry 15 }
schedFailures OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This variable counts the number of failures while invoking
the scheduled action. This counter at most increments once
for a triggered action."
::= { schedEntry 16 }
schedLastFailure OBJECT-TYPE
SYNTAX SnmpPduErrorStatus
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The most recent error that occurred during the invocation of
a scheduled action. The value noError(0) is returned
if no errors have occurred yet."
DEFVAL { noError }
::= { schedEntry 17 }
schedLastFailed OBJECT-TYPE
SYNTAX DateAndTime
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The date and time when the most recent failure occurred.
The value '0000000000000000'H is returned if no failure
occurred since the last re-initialization of the scheduler."
DEFVAL { '0000000000000000'H }
::= { schedEntry 18 }
schedStorageType OBJECT-TYPE
SYNTAX StorageType
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This object defines whether this scheduled action is kept
in volatile storage and lost upon reboot or if this row is
backed up by non-volatile or permanent storage.
Conceptual rows having the value `permanent' must allow
write access to the columnar objects schedDescr,
schedInterval, schedContextName, schedVariable, schedValue,
and schedAdminStatus. If an implementation supports the
schedCalendarGroup, write access must be also allowed to
the columnar objects schedWeekDay, schedMonth, schedDay,
schedHour, schedMinute."
DEFVAL { volatile }
::= { schedEntry 19 }
schedRowStatus OBJECT-TYPE
SYNTAX RowStatus
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The status of this scheduled action. A control that allows
entries to be added and removed from this table.
Note that the operational state must change to enabled
when the administrative state is enabled and the row
status changes to active(1).
Attempts to destroy(6) a row or to set a row
notInService(2) while the operational state is enabled
result in inconsistentValue errors.
The value of this object has no effect on whether other
objects in this conceptual row can be modified."
::= { schedEntry 20 }
schedTriggers OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This variable counts the number of attempts (either
successful or failed) to invoke the scheduled action."
::= { schedEntry 21 }
--
-- Notifications that are emitted to indicate failures. The
-- definition of schedTraps makes notification registrations
-- reversible (see STD 58, RFC 2578).
--
schedTraps OBJECT IDENTIFIER ::= { schedNotifications 0 }
schedActionFailure NOTIFICATION-TYPE
OBJECTS { schedLastFailure, schedLastFailed }
STATUS current
DESCRIPTION
"This notification is generated whenever the invocation of a
scheduled action fails."
::= { schedTraps 1 }
-- conformance information
schedCompliances OBJECT IDENTIFIER ::= { schedConformance 1 }
schedGroups OBJECT IDENTIFIER ::= { schedConformance 2 }
-- compliance statements
schedCompliance2 MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"The compliance statement for SNMP entities which implement
the scheduling MIB."
MODULE -- this module
MANDATORY-GROUPS {
schedGroup2, schedNotificationsGroup
}
GROUP schedCalendarGroup
DESCRIPTION
"The schedCalendarGroup is mandatory only for those
implementations that support calendar based schedules."
OBJECT schedType
DESCRIPTION
"The values calendar(2) or oneshot(3) are not valid for
implementations that do not implement the
schedCalendarGroup. Such an implementation must return
inconsistentValue error responses for attempts to set
schedAdminStatus to calendar(2) or oneshot(3)."
::= { schedCompliances 2 }
schedGroup2 OBJECT-GROUP
OBJECTS {
schedDescr, schedInterval, schedContextName,
schedVariable, schedValue, schedType,
schedAdminStatus, schedOperStatus, schedFailures,
schedLastFailure, schedLastFailed, schedStorageType,
schedRowStatus, schedTriggers
}
STATUS current
DESCRIPTION
"A collection of objects providing scheduling capabilities."
::= { schedGroups 4 }
schedCalendarGroup OBJECT-GROUP
OBJECTS {
schedLocalTime, schedWeekDay, schedMonth,
schedDay, schedHour, schedMinute
}
STATUS current
DESCRIPTION
"A collection of objects providing calendar based schedules."
::= { schedGroups 2 }
schedNotificationsGroup NOTIFICATION-GROUP
NOTIFICATIONS {
schedActionFailure
}
STATUS current
DESCRIPTION
"The notifications emitted by the scheduler."
::= { schedGroups 3 }
--
-- Deprecated compliance and conformance group definitions
-- from RFC 2591.
--
schedCompliance MODULE-COMPLIANCE
STATUS deprecated
DESCRIPTION
"The compliance statement for SNMP entities which implement
the scheduling MIB."
MODULE -- this module
MANDATORY-GROUPS {
schedGroup, schedNotificationsGroup
}
GROUP schedCalendarGroup
DESCRIPTION
"The schedCalendarGroup is mandatory only for those
implementations that support calendar based schedules."
OBJECT schedType
DESCRIPTION
"The values calendar(2) or oneshot(3) are not valid for
implementations that do not implement the
schedCalendarGroup. Such an implementation must return
inconsistentValue error responses for attempts to set
schedAdminStatus to calendar(2) or oneshot(3)."
::= { schedCompliances 1 }
schedGroup OBJECT-GROUP
OBJECTS {
schedDescr, schedInterval, schedContextName,
schedVariable, schedValue, schedType,
schedAdminStatus, schedOperStatus, schedFailures,
schedLastFailure, schedLastFailed, schedStorageType,
schedRowStatus
}
STATUS deprecated
DESCRIPTION
"A collection of objects providing scheduling capabilities."
::= { schedGroups 1 }
END

1764
priv/mibs/DISMAN-SCRIPT-MIB Normal file
View file

File diff suppressed because it is too large Load diff

1850
priv/mibs/DISMAN-TRACEROUTE-MIB Normal file
View file

File diff suppressed because it is too large Load diff

3585
priv/mibs/DLSW-MIB Normal file
View file

File diff suppressed because it is too large Load diff

1201
priv/mibs/DNS-RESOLVER-MIB Normal file
View file

File diff suppressed because it is too large Load diff

1082
priv/mibs/DNS-SERVER-MIB Normal file
View file

File diff suppressed because it is too large Load diff

1992
priv/mibs/DOCS-CABLE-DEVICE-MIB Normal file
View file

File diff suppressed because it is too large Load diff

4046
priv/mibs/DOCS-IF-MIB Normal file
View file

File diff suppressed because it is too large Load diff

2097
priv/mibs/DOT3-OAM-MIB Normal file
View file

File diff suppressed because it is too large Load diff

2112
priv/mibs/DS1-MIB Normal file
View file

File diff suppressed because it is too large Load diff

1794
priv/mibs/DS3-MIB Normal file
View file

File diff suppressed because it is too large Load diff

837
priv/mibs/DVMRP-MIB Normal file
View file

@ -0,0 +1,837 @@
DVMRP-MIB DEFINITIONS ::= BEGIN
IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, experimental,
Integer32, Counter32, Gauge32, NOTIFICATION-TYPE,
IpAddress, TimeTicks FROM SNMPv2-SMI
DisplayString, RowStatus FROM SNMPv2-TC
MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF;
dvmrpMIB MODULE-IDENTITY
LAST-UPDATED "9804221900Z"
ORGANIZATION "IETF IDMR Working Group."
CONTACT-INFO
" Dave Thaler
Microsoft
One Microsoft Way
Redmond, WA 98052-6399
EMail: dthalerd@microsoft.com"
DESCRIPTION
"The MIB module for management of DVMRP routers."
::= { experimental 62 }
dvmrpMIBObjects OBJECT IDENTIFIER ::= { dvmrpMIB 1 }
dvmrp OBJECT IDENTIFIER ::= { dvmrpMIBObjects 1 }
dvmrpVersionString OBJECT-TYPE
SYNTAX DisplayString
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The router's DVMRP version information."
::= { dvmrp 1 }
dvmrpGenerationId OBJECT-TYPE
SYNTAX Integer32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The generation identifier for the routing process. This is
used by neighboring routers to detect whether the DVMRP
routing table should be resent."
::= { dvmrp 2 }
dvmrpNumRoutes OBJECT-TYPE
SYNTAX Gauge32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of entries in the routing table. This can be
used to monitor the routing table size to detect illegal
advertisements of unicast routes."
::= { dvmrp 9 }
dvmrpReachableRoutes OBJECT-TYPE
SYNTAX Gauge32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of entries in the routing table with non
infinite metrics. This can be used to detect network
partitions by observing the ratio of reachable routes to
total routes."
::= { dvmrp 10 }
-- The DVMRP Interface Table
dvmrpInterfaceTable OBJECT-TYPE
SYNTAX SEQUENCE OF DvmrpInterfaceEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The (conceptual) table listing the router's multicast-
capable interfaces."
::= { dvmrp 3 }
dvmrpInterfaceEntry OBJECT-TYPE
SYNTAX DvmrpInterfaceEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry (conceptual row) in the dvmrpInterfaceTable. This
row augments ipMRouteInterfaceEntry in the IP Multicast MIB,
where the threshold object resides."
INDEX { dvmrpInterfaceIfIndex }
::= { dvmrpInterfaceTable 1 }
DvmrpInterfaceEntry ::= SEQUENCE {
dvmrpInterfaceIfIndex Integer32,
dvmrpInterfaceType INTEGER, -- deprecated
dvmrpInterfaceOperState INTEGER, -- deprecated
dvmrpInterfaceLocalAddress IpAddress,
dvmrpInterfaceRemoteAddress IpAddress, -- deprecated
dvmrpInterfaceRemoteSubnetMask IpAddress, -- deprecated
dvmrpInterfaceMetric Integer32,
dvmrpInterfaceRateLimit Integer32, -- deprecated
dvmrpInterfaceInPkts Counter32, -- deprecated
dvmrpInterfaceOutPkts Counter32, -- deprecated
dvmrpInterfaceInOctets Counter32, -- deprecated
dvmrpInterfaceOutOctets Counter32, -- deprecated
dvmrpInterfaceStatus RowStatus,
dvmrpInterfaceRcvBadPkts Counter32,
dvmrpInterfaceRcvBadRoutes Counter32,
dvmrpInterfaceSentRoutes Counter32,
dvmrpInterfaceMasterKey DisplayString,
dvmrpInterfaceMasterKeyVersion Integer32
}
dvmrpInterfaceIfIndex OBJECT-TYPE
SYNTAX Integer32
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The ifIndex value of the interface for which DVMRP is
enabled."
::= { dvmrpInterfaceEntry 1 }
dvmrpInterfaceType OBJECT-TYPE
SYNTAX INTEGER { tunnel(1), srcrt(2), querier(3), subnet(4) }
MAX-ACCESS read-only
STATUS deprecated
DESCRIPTION
"The type of this DVMRP interface, whether it uses a tunnel,
source routing, a physical interface for which we are a
querier, or a physical interface for which we are not a
querier. This object is deprecated in favor of ifType."
DEFVAL { tunnel }
::= { dvmrpInterfaceEntry 2 }
dvmrpInterfaceOperState OBJECT-TYPE
SYNTAX INTEGER { up(1), down(2) }
MAX-ACCESS read-only
STATUS deprecated
DESCRIPTION
"The current operational state of this DVMRP interface. This
object is deprecated in favor of ifOperStatus."
::= { dvmrpInterfaceEntry 3 }
dvmrpInterfaceLocalAddress OBJECT-TYPE
SYNTAX IpAddress
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The IP address this system will use as a source address on
this interface. On unnumbered interfaces, it must be the
same value as dvmrpInterfaceLocalAddress for some interface
on the system."
::= { dvmrpInterfaceEntry 4 }
dvmrpInterfaceRemoteAddress OBJECT-TYPE
SYNTAX IpAddress
MAX-ACCESS read-create
STATUS deprecated
DESCRIPTION
"The IP address of the remote end of this DVMRP virtual
interface. For a tunnel (including source routed), this is
the IP address of the neighboring router. For a subnet,
this is the subnet address. This object is deprecated in
favor of address information associated with the underlying
ifEntry."
::= { dvmrpInterfaceEntry 5 }
dvmrpInterfaceRemoteSubnetMask OBJECT-TYPE
SYNTAX IpAddress
MAX-ACCESS read-only
STATUS deprecated
DESCRIPTION
"The subnet mask for a directly connected subnet. For a
tunnel, this should be 0.0.0.0. This object is deprecated
in favor of address information associated with the
underlying ifEntry."
::= { dvmrpInterfaceEntry 6 }
dvmrpInterfaceMetric OBJECT-TYPE
SYNTAX Integer32 (1..31)
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The distance metric for this interface which is used to
calculate distance vectors."
DEFVAL { 1 }
::= { dvmrpInterfaceEntry 7 }
dvmrpInterfaceRateLimit OBJECT-TYPE
SYNTAX Integer32
MAX-ACCESS read-create
STATUS deprecated
DESCRIPTION
"The rate-limit, in kilobits per second, of forwarded
multicast traffic on the interface. A rate-limit of 0
indicates that no rate limiting is done. This object has
been moved to the IP Multicast MIB."
DEFVAL { 0 }
::= { dvmrpInterfaceEntry 8 }
dvmrpInterfaceInPkts OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS deprecated
DESCRIPTION
"The number of multicast packets that have arrived on the
interface. This object is deprecated in favor of
ifInMulticastPkts in the Interfaces MIB [8]."
::= { dvmrpInterfaceEntry 9 }
dvmrpInterfaceOutPkts OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS deprecated
DESCRIPTION
"The number of multicast packets that have been sent on the
interface. This object is deprecated in favor of
ifOutMulticastPkts in the Interfaces MIB [8]."
::= { dvmrpInterfaceEntry 10 }
dvmrpInterfaceInOctets OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS deprecated
DESCRIPTION
"The number of octets in multicast packets that have arrived
on the interface. This object has been moved to the IP
Multicast MIB."
::= { dvmrpInterfaceEntry 11 }
dvmrpInterfaceOutOctets OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS deprecated
DESCRIPTION
"The number of octets in multicast packets that have been
sent on the interface. This object has been moved to the IP
Multicast MIB."
::= { dvmrpInterfaceEntry 12 }
dvmrpInterfaceStatus OBJECT-TYPE
SYNTAX RowStatus
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The status of this entry. Creating the entry enables DVMRP
on the virtual interface; destroying the entry or setting it
to notInService disables DVMRP on the virtual interface."
::= { dvmrpInterfaceEntry 13 }
dvmrpInterfaceRcvBadPkts OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of DVMRP packets received on the interface by
the DVMRP process which were subsequently discarded as
invalid (e.g. invalid packet format, or a route report from
an unknown neighbor)."
::= { dvmrpInterfaceEntry 14 }
dvmrpInterfaceRcvBadRoutes OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of routes, in valid DVMRP packets, which were
ignored because the entry was invalid."
::= { dvmrpInterfaceEntry 15 }
dvmrpInterfaceSentRoutes OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of routes, in DVMRP Report packets, which have
been sent on this interface. Together with
dvmrpNeighborRcvRoutes at a peer, this object is useful for
detecting routes being lost."
::= { dvmrpInterfaceEntry 16 }
dvmrpInterfaceMasterKey OBJECT-TYPE
SYNTAX DisplayString
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The master (shared) key for authenticating neighbors on
this interface. This object is intended solely for the
purpose of setting the master key, and MUST be accessible
only via requests using both authentication and privacy.
The agent MAY report an empty string in response to get,
get-next, get-bulk requests."
::= { dvmrpInterfaceEntry 17 }
dvmrpInterfaceMasterKeyVersion OBJECT-TYPE
SYNTAX Integer32
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The highest version number of all known master keys used
for authenticating neighbors on this interface."
::= { dvmrpInterfaceEntry 18 }
-- The DVMRP Neighbor Table
dvmrpNeighborTable OBJECT-TYPE
SYNTAX SEQUENCE OF DvmrpNeighborEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The (conceptual) table listing the router's DVMRP
neighbors, as discovered by receiving DVMRP messages."
::= { dvmrp 4 }
dvmrpNeighborEntry OBJECT-TYPE
SYNTAX DvmrpNeighborEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry (conceptual row) in the dvmrpNeighborTable."
INDEX { dvmrpNeighborIfIndex, dvmrpNeighborAddress }
::= { dvmrpNeighborTable 1 }
DvmrpNeighborEntry ::= SEQUENCE {
dvmrpNeighborIfIndex Integer32,
dvmrpNeighborAddress IpAddress,
dvmrpNeighborUpTime TimeTicks,
dvmrpNeighborExpiryTime TimeTicks,
dvmrpNeighborGenerationId Integer32,
dvmrpNeighborMajorVersion Integer32,
dvmrpNeighborMinorVersion Integer32,
dvmrpNeighborCapabilities BITS,
dvmrpNeighborRcvRoutes Counter32,
dvmrpNeighborRcvBadPkts Counter32,
dvmrpNeighborRcvBadRoutes Counter32,
dvmrpNeighborState INTEGER
}
dvmrpNeighborIfIndex OBJECT-TYPE
SYNTAX Integer32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The value of ifIndex for the virtual interface used to
reach this DVMRP neighbor."
::= { dvmrpNeighborEntry 1 }
dvmrpNeighborAddress OBJECT-TYPE
SYNTAX IpAddress
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The IP address of the DVMRP neighbor for which this entry
contains information."
::= { dvmrpNeighborEntry 2 }
dvmrpNeighborUpTime OBJECT-TYPE
SYNTAX TimeTicks
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The time since this DVMRP neighbor (last) became a neighbor
of the local router."
::= { dvmrpNeighborEntry 3 }
dvmrpNeighborExpiryTime OBJECT-TYPE
SYNTAX TimeTicks
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The minimum time remaining before this DVMRP neighbor will
be aged out."
::= { dvmrpNeighborEntry 4 }
dvmrpNeighborGenerationId OBJECT-TYPE
SYNTAX Integer32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The neighboring router's generation identifier."
::= { dvmrpNeighborEntry 6 }
dvmrpNeighborMajorVersion OBJECT-TYPE
SYNTAX Integer32 (0..255)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The neighboring router's major DVMRP version number."
::= { dvmrpNeighborEntry 7 }
dvmrpNeighborMinorVersion OBJECT-TYPE
SYNTAX Integer32 (0..255)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The neighboring router's minor DVMRP version number."
::= { dvmrpNeighborEntry 8 }
dvmrpNeighborCapabilities OBJECT-TYPE
SYNTAX BITS {
leaf(0),
prune(1),
generationID(2),
mtrace(3)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object describes the neighboring router's
capabilities. The leaf bit indicates that the neighbor has
only one interface with neighbors. The prune bit indicates
that the neighbor supports pruning. The generationID bit
indicates that the neighbor sends its generationID in Probe
messages. The mtrace bit indicates that the neighbor can
handle mtrace requests."
::= { dvmrpNeighborEntry 9 }
dvmrpNeighborRcvRoutes OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The total number of routes received in valid DVMRP packets
received from this neighbor. This can be used to diagnose
problems such as unicast route injection, as well as giving
an indication of the level of DVMRP route exchange
activity."
::= { dvmrpNeighborEntry 10 }
dvmrpNeighborRcvBadPkts OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of packet received from this neighbor which were
discarded as invalid."
::= { dvmrpNeighborEntry 11 }
dvmrpNeighborRcvBadRoutes OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of routes, in valid DVMRP packets received from
this neighbor, which were ignored because the entry was
invalid."
::= { dvmrpNeighborEntry 12 }
dvmrpNeighborState OBJECT-TYPE
SYNTAX INTEGER { oneway(1), active(2), ignoring(3), down(4) }
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"State of the neighbor adjacency."
::= { dvmrpNeighborEntry 13 }
-- The DVMRP Route Table
dvmrpRouteTable OBJECT-TYPE
SYNTAX SEQUENCE OF DvmrpRouteEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The table of routes learned through DVMRP route exchange."
::= { dvmrp 5 }
dvmrpRouteEntry OBJECT-TYPE
SYNTAX DvmrpRouteEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry (conceptual row) containing the multicast routing
information used by DVMRP in place of the unicast routing
information."
INDEX { dvmrpRouteSource, dvmrpRouteSourceMask }
::= { dvmrpRouteTable 1 }
DvmrpRouteEntry ::= SEQUENCE {
dvmrpRouteSource IpAddress,
dvmrpRouteSourceMask IpAddress,
dvmrpRouteUpstreamNeighbor IpAddress,
dvmrpRouteIfIndex Integer32,
dvmrpRouteMetric Integer32,
dvmrpRouteExpiryTime TimeTicks,
dvmrpRouteUpTime TimeTicks
}
dvmrpRouteSource OBJECT-TYPE
SYNTAX IpAddress
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The network address which when combined with the
corresponding value of dvmrpRouteSourceMask identifies the
sources for which this entry contains multicast routing
information."
::= { dvmrpRouteEntry 1 }
dvmrpRouteSourceMask OBJECT-TYPE
SYNTAX IpAddress
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The network mask which when combined with the corresponding
value of dvmrpRouteSource identifies the sources for which
this entry contains multicast routing information."
::= { dvmrpRouteEntry 2 }
dvmrpRouteUpstreamNeighbor OBJECT-TYPE
SYNTAX IpAddress
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The address of the upstream neighbor (e.g., RPF neighbor)
from which IP datagrams from these sources are received."
::= { dvmrpRouteEntry 3 }
dvmrpRouteIfIndex OBJECT-TYPE
SYNTAX Integer32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The value of ifIndex for the interface on which IP
datagrams sent by these sources are received."
::= { dvmrpRouteEntry 4 }
dvmrpRouteMetric OBJECT-TYPE
SYNTAX Integer32 (1..32)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The distance in hops to the source subnet."
::= { dvmrpRouteEntry 5 }
dvmrpRouteExpiryTime OBJECT-TYPE
SYNTAX TimeTicks
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The minimum amount of time remaining before this entry will
be aged out."
::= { dvmrpRouteEntry 6 }
dvmrpRouteUpTime OBJECT-TYPE
SYNTAX TimeTicks
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The time since the route represented by this entry was
learned by the router."
::= { dvmrpRouteEntry 7 }
-- The DVMRP Routing Next Hop Table
dvmrpRouteNextHopTable OBJECT-TYPE
SYNTAX SEQUENCE OF DvmrpRouteNextHopEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The (conceptual) table containing information on the next
hops on outgoing interfaces for routing IP multicast
datagrams."
::= { dvmrp 6 }
dvmrpRouteNextHopEntry OBJECT-TYPE
SYNTAX DvmrpRouteNextHopEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry (conceptual row) in the list of next hops on
outgoing interfaces to which IP multicast datagrams from
particular sources are routed."
INDEX { dvmrpRouteNextHopSource, dvmrpRouteNextHopSourceMask,
dvmrpRouteNextHopIfIndex }
::= { dvmrpRouteNextHopTable 1 }
DvmrpRouteNextHopEntry ::= SEQUENCE {
dvmrpRouteNextHopSource IpAddress,
dvmrpRouteNextHopSourceMask IpAddress,
dvmrpRouteNextHopIfIndex Integer32,
dvmrpRouteNextHopType INTEGER
}
dvmrpRouteNextHopSource OBJECT-TYPE
SYNTAX IpAddress
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The network address which when combined with the
corresponding value of dvmrpRouteNextHopSourceMask
identifies the sources for which this entry specifies a next
hop on an outgoing interface."
::= { dvmrpRouteNextHopEntry 1 }
dvmrpRouteNextHopSourceMask OBJECT-TYPE
SYNTAX IpAddress
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The network mask which when combined with the corresponding
value of dvmrpRouteNextHopSource identifies the sources for
which this entry specifies a next hop on an outgoing
interface."
::= { dvmrpRouteNextHopEntry 2 }
dvmrpRouteNextHopIfIndex OBJECT-TYPE
SYNTAX Integer32
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The ifIndex value of the interface for the outgoing
interface for this next hop."
::= { dvmrpRouteNextHopEntry 3 }
dvmrpRouteNextHopType OBJECT-TYPE
SYNTAX INTEGER { leaf(1), branch(2) }
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Type is leaf if no downstream dependent neighbors exist on
the outgoing virtual interface. Otherwise, type is branch."
::= { dvmrpRouteNextHopEntry 4 }
-- The DVMRP Alternate Subnet Table
dvmrpAltNetTable OBJECT-TYPE
SYNTAX SEQUENCE OF DvmrpAltNetEntry
MAX-ACCESS not-accessible
STATUS deprecated
DESCRIPTION
"The (conceptual) table listing the router's alternate
subnets on physical interfaces for use in constructing the
routing tables."
::= { dvmrp 8 }
dvmrpAltNetEntry OBJECT-TYPE
SYNTAX DvmrpAltNetEntry
MAX-ACCESS not-accessible
STATUS deprecated
DESCRIPTION
"An entry (conceptual row) in the dvmrpAltNetTable."
INDEX { dvmrpAltNetIfIndex, dvmrpAltNetAddress,
dvmrpAltNetMask }
::= { dvmrpAltNetTable 1 }
DvmrpAltNetEntry ::= SEQUENCE {
dvmrpAltNetIfIndex Integer32, -- deprecated
dvmrpAltNetAddress IpAddress, -- deprecated
dvmrpAltNetMask IpAddress, -- deprecated
dvmrpAltNetStatus RowStatus -- deprecated
}
dvmrpAltNetIfIndex OBJECT-TYPE
SYNTAX Integer32
MAX-ACCESS not-accessible
STATUS deprecated
DESCRIPTION
"The ifIndex value of the interface to which this alternate
subnet applies."
::= { dvmrpAltNetEntry 1 }
dvmrpAltNetAddress OBJECT-TYPE
SYNTAX IpAddress
MAX-ACCESS not-accessible
STATUS deprecated
DESCRIPTION
"The subnet address of the alternate subnet."
::= { dvmrpAltNetEntry 2 }
dvmrpAltNetMask OBJECT-TYPE
SYNTAX IpAddress
MAX-ACCESS not-accessible
STATUS deprecated
DESCRIPTION
"The subnet mask of the alternate subnet."
::= { dvmrpAltNetEntry 3 }
dvmrpAltNetStatus OBJECT-TYPE
SYNTAX RowStatus
MAX-ACCESS read-create
STATUS deprecated
DESCRIPTION
"The status of this row, by which new entries may be
created, or old entries deleted from this table."
::= { dvmrpAltNetEntry 4 }
-- DVMRP Traps
dvmrpTraps OBJECT IDENTIFIER ::= { dvmrp 11 }
dvmrpNeighborLoss NOTIFICATION-TYPE
OBJECTS {
dvmrpInterfaceLocalAddress, -- The originator of the trap
dvmrpNeighborIfIndex,
dvmrpNeighborAddress,
dvmrpNeighborState -- The new state
}
STATUS current
DESCRIPTION
"A dvmrpNeighborLoss trap signifies the loss of a 2-way
adjacency with a neighbor. This trap should be generated
when the neighbor state changes from active to one-way,
ignoring, or down. The trap should be generated only if the
router has no other neighbors on the same interface with a
lower IP address than itself."
::= { dvmrpTraps 1 }
dvmrpNeighborNotPruning NOTIFICATION-TYPE
OBJECTS {
dvmrpInterfaceLocalAddress, -- The originator of the trap
dvmrpNeighborIfIndex,
dvmrpNeighborAddress
}
STATUS current
DESCRIPTION
"A dvmrpNeighborNotPruning trap signifies that a non-pruning
neighbor has been detected. This trap should be generated
at most once per generation ID of the neighbor. For
example, it may be generated at the time a neighbor is first
heard from if the prune bit is not set in its capabilities.
The trap should be generated only if the router has no other
neighbors on the same interface with a lower IP address than
itself."
::= { dvmrpTraps 2 }
-- conformance information
dvmrpMIBConformance OBJECT IDENTIFIER ::= { dvmrpMIB 2 }
dvmrpMIBCompliances OBJECT IDENTIFIER ::= { dvmrpMIBConformance 1 }
dvmrpMIBGroups OBJECT IDENTIFIER ::= { dvmrpMIBConformance 2 }
-- compliance statements
dvmrpMIBCompliance MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"The compliance statement for the DVMRP MIB."
MODULE -- this module
MANDATORY-GROUPS { dvmrpGeneralGroup, dvmrpInterfaceGroup,
dvmrpNeighborGroup, dvmrpRoutingGroup
}
GROUP dvmrpSecurityGroup
DESCRIPTION
"This group is mandatory for agents which support both
authentication and privacy of SNMP messages, and only for
those network interfaces for which DVMRP is authenticating
neighbors."
::= { dvmrpMIBCompliances 1 }
-- units of conformance
dvmrpMIBGroup OBJECT-GROUP
OBJECTS { dvmrpVersionString, dvmrpGenerationId,
dvmrpNumRoutes, dvmrpReachableRoutes,
dvmrpInterfaceType, dvmrpInterfaceOperState,
dvmrpInterfaceLocalAddress, dvmrpInterfaceRemoteAddress,
dvmrpInterfaceRemoteSubnetMask,
dvmrpInterfaceMetric, dvmrpInterfaceRateLimit,
dvmrpInterfaceInPkts, dvmrpInterfaceOutPkts,
dvmrpInterfaceInOctets, dvmrpInterfaceOutOctets,
dvmrpInterfaceStatus,
dvmrpNeighborUpTime, dvmrpNeighborExpiryTime,
dvmrpNeighborGenerationId, dvmrpNeighborMajorVersion,
dvmrpNeighborMinorVersion, dvmrpNeighborCapabilities,
dvmrpRouteUpstreamNeighbor, dvmrpRouteIfIndex,
dvmrpRouteMetric, dvmrpRouteExpiryTime,
dvmrpRouteNextHopType, dvmrpAltNetStatus
}
STATUS deprecated
DESCRIPTION
"A collection of objects to support management of DVMRP
routers."
::= { dvmrpMIBGroups 1 }
dvmrpGeneralGroup OBJECT-GROUP
OBJECTS { dvmrpVersionString, dvmrpGenerationId,
dvmrpNumRoutes, dvmrpReachableRoutes
}
STATUS current
DESCRIPTION
"A collection of objects used to describe general DVMRP
configuration information."
::= { dvmrpMIBGroups 2 }
dvmrpInterfaceGroup OBJECT-GROUP
OBJECTS { dvmrpInterfaceLocalAddress, dvmrpInterfaceMetric,
dvmrpInterfaceStatus,
dvmrpInterfaceRcvBadPkts, dvmrpInterfaceRcvBadRoutes,
dvmrpInterfaceSentRoutes
}
STATUS current
DESCRIPTION
"A collection of objects used to describe DVMRP interface
configuration and statistics."
::= { dvmrpMIBGroups 3 }
dvmrpNeighborGroup OBJECT-GROUP
OBJECTS { dvmrpNeighborUpTime, dvmrpNeighborExpiryTime,
dvmrpNeighborGenerationId,
dvmrpNeighborMajorVersion, dvmrpNeighborMinorVersion,
dvmrpNeighborCapabilities, dvmrpNeighborRcvRoutes,
dvmrpNeighborRcvBadPkts, dvmrpNeighborRcvBadRoutes,
dvmrpNeighborState
}
STATUS current
DESCRIPTION
"A collection of objects used to describe DVMRP peer
configuration and statistics."
::= { dvmrpMIBGroups 4 }
dvmrpRoutingGroup OBJECT-GROUP
OBJECTS { dvmrpRouteUpstreamNeighbor, dvmrpRouteIfIndex,
dvmrpRouteMetric, dvmrpRouteExpiryTime,
dvmrpRouteUpTime, dvmrpRouteNextHopType
}
STATUS current
DESCRIPTION
"A collection of objects used to store the DVMRP routing
table."
::= { dvmrpMIBGroups 5 }
dvmrpSecurityGroup OBJECT-GROUP
OBJECTS { dvmrpInterfaceMasterKey,
dvmrpInterfaceMasterKeyVersion }
STATUS current
DESCRIPTION
"A collection of objects used to store information related
to DVMRP security."
::= { dvmrpMIBGroups 6 }
END

751
priv/mibs/DVMRP-STD-MIB Normal file
View file

@ -0,0 +1,751 @@
DVMRP-STD-MIB DEFINITIONS ::= BEGIN
IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, experimental,
Integer32, Counter32, Gauge32, NOTIFICATION-TYPE,
IpAddress, TimeTicks FROM SNMPv2-SMI
DisplayString, RowStatus FROM SNMPv2-TC
MODULE-COMPLIANCE, OBJECT-GROUP,
NOTIFICATION-GROUP FROM SNMPv2-CONF
-- SnmpAdminString FROM SNMP-FRAMEWORK-MIB
InterfaceIndexOrZero,
InterfaceIndex FROM IF-MIB;
dvmrpStdMIB MODULE-IDENTITY
LAST-UPDATED "200111211200Z"
ORGANIZATION "IETF IDMR Working Group."
CONTACT-INFO
" Dave Thaler
Microsoft
One Microsoft Way
Redmond, WA 98052-6399
EMail: dthaler@microsoft.com"
DESCRIPTION
"The MIB module for management of DVMRP routers."
REVISION "200111211200Z"
DESCRIPTION
"Initial version, published as RFC xxxx (to be filled in by
RFC-Editor)."
::= { experimental 62 }
-- NOTE TO RFC EDITOR: When this document is published as an
-- RFC, replace xx with IANA assignment, and delete this comment.
-- Also, the following statement should be restored.
dvmrpMIBObjects OBJECT IDENTIFIER ::= { dvmrpStdMIB 1 }
dvmrp OBJECT IDENTIFIER ::= { dvmrpMIBObjects 1 }
dvmrpScalar OBJECT IDENTIFIER ::= { dvmrp 1 }
dvmrpVersionString OBJECT-TYPE
SYNTAX DisplayString
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The router's DVMRP version information. Similar to
sysDescr in MIB-II, this is a free-form field which can be
used to display vendor-specific information."
::= { dvmrpScalar 1 }
-- dvmrpScalar 2 was previously used for a global
-- Generation ID. However, the DVMRP spec changed it to
-- a per-interface parameter.
dvmrpNumRoutes OBJECT-TYPE
SYNTAX Gauge32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of entries in the routing table. This can be
used to monitor the routing table size."
::= { dvmrpScalar 3 }
dvmrpReachableRoutes OBJECT-TYPE
SYNTAX Gauge32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of entries in the routing table with non
infinite metrics. This can be used to detect network
partitions by observing the ratio of reachable routes to
total routes."
::= { dvmrpScalar 4 }
-- The DVMRP Interface Table
dvmrpInterfaceTable OBJECT-TYPE
SYNTAX SEQUENCE OF DvmrpInterfaceEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The (conceptual) table listing the router's multicast-
capable interfaces."
::= { dvmrp 2 }
dvmrpInterfaceEntry OBJECT-TYPE
SYNTAX DvmrpInterfaceEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry (conceptual row) in the dvmrpInterfaceTable. This
row augments ipMRouteInterfaceEntry in the IP Multicast MIB,
where the threshold object resides."
INDEX { dvmrpInterfaceIndex }
::= { dvmrpInterfaceTable 1 }
DvmrpInterfaceEntry ::= SEQUENCE {
dvmrpInterfaceIndex InterfaceIndex,
dvmrpInterfaceLocalAddress IpAddress,
dvmrpInterfaceMetric Integer32,
dvmrpInterfaceStatus RowStatus,
dvmrpInterfaceRcvBadPkts Counter32,
dvmrpInterfaceRcvBadRoutes Counter32,
dvmrpInterfaceSentRoutes Counter32,
-- dvmrpInterfaceKey SnmpAdminString,
dvmrpInterfaceKey DisplayString,
dvmrpInterfaceKeyVersion Integer32,
dvmrpInterfaceGenerationId Integer32
}
dvmrpInterfaceIndex OBJECT-TYPE
SYNTAX InterfaceIndex
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The ifIndex value of the interface for which DVMRP is
enabled."
::= { dvmrpInterfaceEntry 1 }
dvmrpInterfaceLocalAddress OBJECT-TYPE
SYNTAX IpAddress
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The IP address this system will use as a source address on
this interface. On unnumbered interfaces, it must be the
same value as dvmrpInterfaceLocalAddress for some interface
on the system."
::= { dvmrpInterfaceEntry 2 }
dvmrpInterfaceMetric OBJECT-TYPE
SYNTAX Integer32 (1..31)
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The distance metric for this interface which is used to
calculate distance vectors."
DEFVAL { 1 }
::= { dvmrpInterfaceEntry 3 }
dvmrpInterfaceStatus OBJECT-TYPE
SYNTAX RowStatus
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The status of this entry. Creating the entry enables DVMRP
on the virtual interface; destroying the entry or setting it
to notInService disables DVMRP on the virtual interface."
::= { dvmrpInterfaceEntry 4 }
dvmrpInterfaceRcvBadPkts OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of DVMRP messages received on the interface by
the DVMRP process which were subsequently discarded as
invalid (e.g. invalid packet format, or a route report from
an unknown neighbor)."
::= { dvmrpInterfaceEntry 5 }
dvmrpInterfaceRcvBadRoutes OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of routes, in valid DVMRP packets, which were
ignored because the entry was invalid."
::= { dvmrpInterfaceEntry 6 }
dvmrpInterfaceSentRoutes OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of routes, in DVMRP Report packets, which have
been sent on this interface. Together with
dvmrpNeighborRcvRoutes at a peer, this object is useful for
detecting routes being lost."
::= { dvmrpInterfaceEntry 7 }
dvmrpInterfaceKey OBJECT-TYPE
-- SYNTAX SnmpAdminString
SYNTAX DisplayString
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The (shared) key for authenticating neighbors on this
interface. This object is intended solely for the purpose
of setting the interface key, and MUST be accessible only
via requests using both authentication and privacy. The
agent MAY report an empty string in response to get, get-
next, get-bulk requests."
::= { dvmrpInterfaceEntry 8 }
dvmrpInterfaceKeyVersion OBJECT-TYPE
SYNTAX Integer32
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The highest version number of all known interface keys for
this interface used for authenticating neighbors."
::= { dvmrpInterfaceEntry 9 }
dvmrpInterfaceGenerationId OBJECT-TYPE
SYNTAX Integer32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The generation identifier for the interface. This is used
by neighboring routers to detect whether the DVMRP routing
table should be resent."
::= { dvmrpInterfaceEntry 10 }
-- The DVMRP Neighbor Table
dvmrpNeighborTable OBJECT-TYPE
SYNTAX SEQUENCE OF DvmrpNeighborEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The (conceptual) table listing the router's DVMRP
neighbors, as discovered by receiving DVMRP messages."
::= { dvmrp 3 }
dvmrpNeighborEntry OBJECT-TYPE
SYNTAX DvmrpNeighborEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry (conceptual row) in the dvmrpNeighborTable."
INDEX { dvmrpNeighborIfIndex, dvmrpNeighborAddress }
::= { dvmrpNeighborTable 1 }
DvmrpNeighborEntry ::= SEQUENCE {
dvmrpNeighborIfIndex InterfaceIndex,
dvmrpNeighborAddress IpAddress,
dvmrpNeighborUpTime TimeTicks,
dvmrpNeighborExpiryTime TimeTicks,
dvmrpNeighborGenerationId Integer32,
dvmrpNeighborMajorVersion Integer32,
dvmrpNeighborMinorVersion Integer32,
dvmrpNeighborCapabilities BITS,
dvmrpNeighborRcvRoutes Counter32,
dvmrpNeighborRcvBadPkts Counter32,
dvmrpNeighborRcvBadRoutes Counter32,
dvmrpNeighborState INTEGER
}
dvmrpNeighborIfIndex OBJECT-TYPE
SYNTAX InterfaceIndex
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The value of ifIndex for the virtual interface used to
reach this DVMRP neighbor."
::= { dvmrpNeighborEntry 1 }
dvmrpNeighborAddress OBJECT-TYPE
SYNTAX IpAddress
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The IP address of the DVMRP neighbor for which this entry
contains information."
::= { dvmrpNeighborEntry 2 }
dvmrpNeighborUpTime OBJECT-TYPE
SYNTAX TimeTicks
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The time since this DVMRP neighbor (last) became a neighbor
of the local router."
::= { dvmrpNeighborEntry 3 }
dvmrpNeighborExpiryTime OBJECT-TYPE
SYNTAX TimeTicks
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The minimum time remaining before this DVMRP neighbor will
be aged out."
::= { dvmrpNeighborEntry 4 }
dvmrpNeighborGenerationId OBJECT-TYPE
SYNTAX Integer32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The neighboring router's generation identifier."
::= { dvmrpNeighborEntry 5 }
dvmrpNeighborMajorVersion OBJECT-TYPE
SYNTAX Integer32 (0..255)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The neighboring router's major DVMRP version number."
::= { dvmrpNeighborEntry 6 }
dvmrpNeighborMinorVersion OBJECT-TYPE
SYNTAX Integer32 (0..255)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The neighboring router's minor DVMRP version number."
::= { dvmrpNeighborEntry 7 }
dvmrpNeighborCapabilities OBJECT-TYPE
SYNTAX BITS {
leaf(0),
prune(1),
generationID(2),
mtrace(3)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object describes the neighboring router's
capabilities. The leaf bit indicates that the neighbor has
only one interface with neighbors. The prune bit indicates
that the neighbor supports pruning. The generationID bit
indicates that the neighbor sends its generationID in Probe
messages. The mtrace bit indicates that the neighbor can
handle mtrace requests."
::= { dvmrpNeighborEntry 8 }
dvmrpNeighborRcvRoutes OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The total number of routes received in valid DVMRP packets
received from this neighbor. This can be used to diagnose
problems such as unicast route injection, as well as giving
an indication of the level of DVMRP route exchange
activity."
::= { dvmrpNeighborEntry 9 }
dvmrpNeighborRcvBadPkts OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of packet received from this neighbor which were
discarded as invalid."
::= { dvmrpNeighborEntry 10 }
dvmrpNeighborRcvBadRoutes OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of routes, in valid DVMRP packets received from
this neighbor, which were ignored because the entry was
invalid."
::= { dvmrpNeighborEntry 11 }
dvmrpNeighborState OBJECT-TYPE
SYNTAX INTEGER { oneway(1), active(2), ignoring(3), down(4) }
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"State of the neighbor adjacency."
::= { dvmrpNeighborEntry 12 }
-- The DVMRP Route Table
dvmrpRouteTable OBJECT-TYPE
SYNTAX SEQUENCE OF DvmrpRouteEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The table of routes learned through DVMRP route exchange."
::= { dvmrp 4 }
dvmrpRouteEntry OBJECT-TYPE
SYNTAX DvmrpRouteEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry (conceptual row) containing the multicast routing
information used by DVMRP in place of the unicast routing
information."
INDEX { dvmrpRouteSource, dvmrpRouteSourceMask }
::= { dvmrpRouteTable 1 }
DvmrpRouteEntry ::= SEQUENCE {
dvmrpRouteSource IpAddress,
dvmrpRouteSourceMask IpAddress,
dvmrpRouteUpstreamNeighbor IpAddress,
dvmrpRouteIfIndex InterfaceIndexOrZero,
dvmrpRouteMetric Integer32,
dvmrpRouteExpiryTime TimeTicks,
dvmrpRouteUpTime TimeTicks
}
dvmrpRouteSource OBJECT-TYPE
SYNTAX IpAddress
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The network address which when combined with the
corresponding value of dvmrpRouteSourceMask identifies the
sources for which this entry contains multicast routing
information."
::= { dvmrpRouteEntry 1 }
dvmrpRouteSourceMask OBJECT-TYPE
SYNTAX IpAddress
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The network mask which when combined with the corresponding
value of dvmrpRouteSource identifies the sources for which
this entry contains multicast routing information."
::= { dvmrpRouteEntry 2 }
dvmrpRouteUpstreamNeighbor OBJECT-TYPE
SYNTAX IpAddress
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The address of the upstream neighbor (e.g., RPF neighbor)
from which IP datagrams from these sources are received."
::= { dvmrpRouteEntry 3 }
dvmrpRouteIfIndex OBJECT-TYPE
SYNTAX InterfaceIndexOrZero
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The value of ifIndex for the interface on which IP
datagrams sent by these sources are received. A value of 0
typically means the route is an aggregate for which no next-
hop interface exists."
::= { dvmrpRouteEntry 4 }
dvmrpRouteMetric OBJECT-TYPE
SYNTAX Integer32 (1..32)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The distance in hops to the source subnet."
::= { dvmrpRouteEntry 5 }
dvmrpRouteExpiryTime OBJECT-TYPE
SYNTAX TimeTicks
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The minimum amount of time remaining before this entry will
be aged out."
::= { dvmrpRouteEntry 6 }
dvmrpRouteUpTime OBJECT-TYPE
SYNTAX TimeTicks
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The time since the route represented by this entry was
learned by the router."
::= { dvmrpRouteEntry 7 }
-- The DVMRP Routing Next Hop Table
dvmrpRouteNextHopTable OBJECT-TYPE
SYNTAX SEQUENCE OF DvmrpRouteNextHopEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The (conceptual) table containing information on the next
hops on outgoing interfaces for routing IP multicast
datagrams."
::= { dvmrp 5 }
dvmrpRouteNextHopEntry OBJECT-TYPE
SYNTAX DvmrpRouteNextHopEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry (conceptual row) in the list of next hops on
outgoing interfaces to which IP multicast datagrams from
particular sources are routed."
INDEX { dvmrpRouteNextHopSource, dvmrpRouteNextHopSourceMask,
dvmrpRouteNextHopIfIndex }
::= { dvmrpRouteNextHopTable 1 }
DvmrpRouteNextHopEntry ::= SEQUENCE {
dvmrpRouteNextHopSource IpAddress,
dvmrpRouteNextHopSourceMask IpAddress,
dvmrpRouteNextHopIfIndex InterfaceIndex,
dvmrpRouteNextHopType INTEGER
}
dvmrpRouteNextHopSource OBJECT-TYPE
SYNTAX IpAddress
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The network address which when combined with the
corresponding value of dvmrpRouteNextHopSourceMask
identifies the sources for which this entry specifies a next
hop on an outgoing interface."
::= { dvmrpRouteNextHopEntry 1 }
dvmrpRouteNextHopSourceMask OBJECT-TYPE
SYNTAX IpAddress
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The network mask which when combined with the corresponding
value of dvmrpRouteNextHopSource identifies the sources for
which this entry specifies a next hop on an outgoing
interface."
::= { dvmrpRouteNextHopEntry 2 }
dvmrpRouteNextHopIfIndex OBJECT-TYPE
SYNTAX InterfaceIndex
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The ifIndex value of the interface for the outgoing
interface for this next hop."
::= { dvmrpRouteNextHopEntry 3 }
dvmrpRouteNextHopType OBJECT-TYPE
SYNTAX INTEGER { leaf(1), branch(2) }
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Type is leaf if no downstream dependent neighbors exist on
the outgoing virtual interface. Otherwise, type is branch."
::= { dvmrpRouteNextHopEntry 4 }
-- The DVMRP Prune Table
dvmrpPruneTable OBJECT-TYPE
SYNTAX SEQUENCE OF DvmrpPruneEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The (conceptual) table listing the router's upstream prune
state."
::= { dvmrp 6 }
dvmrpPruneEntry OBJECT-TYPE
SYNTAX DvmrpPruneEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry (conceptual row) in the dvmrpPruneTable."
INDEX { dvmrpPruneGroup, dvmrpPruneSource,
dvmrpPruneSourceMask }
::= { dvmrpPruneTable 1 }
DvmrpPruneEntry ::= SEQUENCE {
dvmrpPruneGroup IpAddress,
dvmrpPruneSource IpAddress,
dvmrpPruneSourceMask IpAddress,
dvmrpPruneExpiryTime TimeTicks
}
dvmrpPruneGroup OBJECT-TYPE
SYNTAX IpAddress
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The group address which has been pruned."
::= { dvmrpPruneEntry 1 }
dvmrpPruneSource OBJECT-TYPE
SYNTAX IpAddress
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The address of the source or source network which has been
pruned."
::= { dvmrpPruneEntry 2 }
dvmrpPruneSourceMask OBJECT-TYPE
SYNTAX IpAddress
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The address of the source or source network which has been
pruned. The mask must either be all 1's, or else
dvmrpPruneSource and dvmrpPruneSourceMask must match
dvmrpRouteSource and dvmrpRouteSourceMask for some entry in
the dvmrpRouteTable."
::= { dvmrpPruneEntry 3 }
dvmrpPruneExpiryTime OBJECT-TYPE
SYNTAX TimeTicks
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The amount of time remaining before this prune should
expire at the upstream neighbor. This value should be the
minimum of the default prune lifetime and the remaining
prune lifetimes of the local router's downstream neighbors,
if any."
::= { dvmrpPruneEntry 4 }
-- DVMRP Traps
dvmrpTraps OBJECT IDENTIFIER ::= { dvmrp 7 }
dvmrpNeighborLoss NOTIFICATION-TYPE
OBJECTS {
dvmrpInterfaceLocalAddress, -- The originator of the trap
dvmrpNeighborState -- The new state
}
STATUS current
DESCRIPTION
"A dvmrpNeighborLoss trap signifies the loss of a 2-way
adjacency with a neighbor. This trap should be generated
when the neighbor state changes from active to one-way,
ignoring, or down. The trap should be generated only if the
router has no other neighbors on the same interface with a
lower IP address than itself."
--#ENABLE FALSE
::= { dvmrpTraps 1 }
dvmrpNeighborNotPruning NOTIFICATION-TYPE
OBJECTS {
dvmrpInterfaceLocalAddress, -- The originator of the trap
dvmrpNeighborCapabilities
}
STATUS current
DESCRIPTION
"A dvmrpNeighborNotPruning trap signifies that a non-pruning
neighbor has been detected (in an implementation-dependent
manner). This trap should be generated at most once per
generation ID of the neighbor. For example, it should be
generated at the time a neighbor is first heard from if the
prune bit is not set in its capabilities. It should also be
generated if the local system has the ability to tell that a
neighbor which sets the the prune bit in its capabilities is
not pruning any branches over an extended period of time.
The trap should be generated only if the router has no other
neighbors on the same interface with a lower IP address than
itself."
--#ENABLE FALSE
::= { dvmrpTraps 2 }
-- conformance information
dvmrpMIBConformance OBJECT IDENTIFIER ::= { dvmrpStdMIB 2 }
dvmrpMIBCompliances OBJECT IDENTIFIER ::= { dvmrpMIBConformance 1 }
dvmrpMIBGroups OBJECT IDENTIFIER ::= { dvmrpMIBConformance 2 }
-- compliance statements
dvmrpMIBCompliance MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"The compliance statement for the DVMRP MIB."
MODULE -- this module
MANDATORY-GROUPS { dvmrpGeneralGroup, dvmrpInterfaceGroup,
dvmrpNeighborGroup, dvmrpRoutingGroup, dvmrpTreeGroup
}
GROUP dvmrpSecurityGroup
DESCRIPTION
"This group is mandatory for agents which support both
authentication and privacy of SNMP messages, and only for
those network interfaces for which DVMRP is authenticating
neighbors."
::= { dvmrpMIBCompliances 1 }
-- units of conformance
dvmrpGeneralGroup OBJECT-GROUP
OBJECTS { dvmrpVersionString, dvmrpNumRoutes, dvmrpReachableRoutes
}
STATUS current
DESCRIPTION
"A collection of objects used to describe general DVMRP
configuration information."
::= { dvmrpMIBGroups 2 }
dvmrpInterfaceGroup OBJECT-GROUP
OBJECTS { dvmrpInterfaceLocalAddress, dvmrpInterfaceMetric,
dvmrpInterfaceStatus, dvmrpInterfaceGenerationId,
dvmrpInterfaceRcvBadPkts, dvmrpInterfaceRcvBadRoutes,
dvmrpInterfaceSentRoutes
}
STATUS current
DESCRIPTION
"A collection of objects used to describe DVMRP interface
configuration and statistics."
::= { dvmrpMIBGroups 3 }
dvmrpNeighborGroup OBJECT-GROUP
OBJECTS { dvmrpNeighborUpTime, dvmrpNeighborExpiryTime,
dvmrpNeighborGenerationId,
dvmrpNeighborMajorVersion, dvmrpNeighborMinorVersion,
dvmrpNeighborCapabilities, dvmrpNeighborRcvRoutes,
dvmrpNeighborRcvBadPkts, dvmrpNeighborRcvBadRoutes,
dvmrpNeighborState
}
STATUS current
DESCRIPTION
"A collection of objects used to describe DVMRP peer
configuration and statistics."
::= { dvmrpMIBGroups 4 }
dvmrpRoutingGroup OBJECT-GROUP
OBJECTS { dvmrpRouteUpstreamNeighbor, dvmrpRouteIfIndex,
dvmrpRouteMetric, dvmrpRouteExpiryTime,
dvmrpRouteUpTime, dvmrpRouteNextHopType
}
STATUS current
DESCRIPTION
"A collection of objects used to store the DVMRP routing
table."
::= { dvmrpMIBGroups 5 }
dvmrpSecurityGroup OBJECT-GROUP
OBJECTS { dvmrpInterfaceKey,
dvmrpInterfaceKeyVersion }
STATUS current
DESCRIPTION
"A collection of objects used to store information related
to DVMRP security."
::= { dvmrpMIBGroups 6 }
dvmrpTreeGroup OBJECT-GROUP
OBJECTS { dvmrpPruneExpiryTime }
STATUS current
DESCRIPTION
"A collection of objects used to store information related
to DVMRP prune state."
::= { dvmrpMIBGroups 7 }
dvmrpNotificationGroup NOTIFICATION-GROUP
NOTIFICATIONS { dvmrpNeighborLoss,
dvmrpNeighborNotPruning }
STATUS current
DESCRIPTION
"A collection of notifications for signaling important DVMRP
events."
::= { dvmrpMIBGroups 8 }
END

1585
priv/mibs/ENTITY-MIB Normal file
View file

File diff suppressed because it is too large Load diff

460
priv/mibs/ENTITY-SENSOR-MIB Normal file
View file

@ -0,0 +1,460 @@
-- WinAgents MIB Extraction Wizard
-- Extracted from rfc3433.txt 16.03.2005 20:21:58
ENTITY-SENSOR-MIB DEFINITIONS ::= BEGIN
IMPORTS
MODULE-IDENTITY, OBJECT-TYPE,
Integer32, Unsigned32, mib-2
FROM SNMPv2-SMI
MODULE-COMPLIANCE, OBJECT-GROUP
FROM SNMPv2-CONF
TEXTUAL-CONVENTION, TimeStamp
FROM SNMPv2-TC
entPhysicalIndex, entityPhysicalGroup
FROM ENTITY-MIB
SnmpAdminString
FROM SNMP-FRAMEWORK-MIB;
entitySensorMIB MODULE-IDENTITY
LAST-UPDATED "200212160000Z"
ORGANIZATION "IETF Entity MIB Working Group"
CONTACT-INFO
" Andy Bierman
Cisco Systems, Inc.
Tel: +1 408-527-3711
E-mail: abierman@cisco.com
Postal: 170 West Tasman Drive
San Jose, CA USA 95134
Dan Romascanu
Avaya Inc.
Tel: +972-3-645-8414
Email: dromasca@avaya.com
Postal: Atidim technology Park, Bldg. #3
Tel Aviv, Israel, 61131
K.C. Norseth
L-3 Communications
Tel: +1 801-594-2809
Email: kenyon.c.norseth@L-3com.com
Postal: 640 N. 2200 West.
Salt Lake City, Utah 84116-0850
Send comments to <entmib@ietf.org>
Mailing list subscription info:
http://www.ietf.org/mailman/listinfo/entmib "
DESCRIPTION
"This module defines Entity MIB extensions for physical
sensors.
Copyright (C) The Internet Society (2002). This version
of this MIB module is part of RFC 3433; see the RFC
itself for full legal notices."
REVISION "200212160000Z"
DESCRIPTION
"Initial version of the Entity Sensor MIB module, published
as RFC 3433."
::= { mib-2 99 }
entitySensorObjects OBJECT IDENTIFIER
::= { entitySensorMIB 1 }
-- entitySensorNotifications OBJECT IDENTIFIER
-- ::= { entitySensorMIB 2 }
entitySensorConformance OBJECT IDENTIFIER
::= { entitySensorMIB 3 }
--
-- Textual Conventions
--
EntitySensorDataType ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"An object using this data type represents the Entity Sensor
measurement data type associated with a physical sensor
value. The actual data units are determined by examining an
object of this type together with the associated
EntitySensorDataScale object.
An object of this type SHOULD be defined together with
objects of type EntitySensorDataScale and
EntitySensorPrecision. Together, associated objects of
these three types are used to identify the semantics of an
object of type EntitySensorValue.
Valid values are:
other(1): a measure other than those listed below
unknown(2): unknown measurement, or arbitrary,
relative numbers
voltsAC(3): electric potential
voltsDC(4): electric potential
amperes(5): electric current
watts(6): power
hertz(7): frequency
celsius(8): temperature
percentRH(9): percent relative humidity
rpm(10): shaft revolutions per minute
cmm(11),: cubic meters per minute (airflow)
truthvalue(12): value takes { true(1), false(2) }
"
SYNTAX INTEGER {
other(1),
unknown(2),
voltsAC(3),
voltsDC(4),
amperes(5),
watts(6),
hertz(7),
celsius(8),
percentRH(9),
rpm(10),
cmm(11),
truthvalue(12)
}
EntitySensorDataScale ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"An object using this data type represents a data scaling
factor, represented with an International System of Units
(SI) prefix. The actual data units are determined by
examining an object of this type together with the
associated EntitySensorDataType object.
An object of this type SHOULD be defined together with
objects of type EntitySensorDataType and
EntitySensorPrecision. Together, associated objects of
these three types are used to identify the semantics of an
object of type EntitySensorValue."
REFERENCE
"The International System of Units (SI),
National Institute of Standards and Technology,
Spec. Publ. 330, August 1991."
SYNTAX INTEGER {
yocto(1), -- 10^-24
zepto(2), -- 10^-21
atto(3), -- 10^-18
femto(4), -- 10^-15
pico(5), -- 10^-12
nano(6), -- 10^-9
micro(7), -- 10^-6
milli(8), -- 10^-3
units(9), -- 10^0
kilo(10), -- 10^3
mega(11), -- 10^6
giga(12), -- 10^9
tera(13), -- 10^12
exa(14), -- 10^15
peta(15), -- 10^18
zetta(16), -- 10^21
yotta(17) -- 10^24
}
EntitySensorPrecision ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"An object using this data type represents a sensor
precision range.
An object of this type SHOULD be defined together with
objects of type EntitySensorDataType and
EntitySensorDataScale. Together, associated objects of
these three types are used to identify the semantics of an
object of type EntitySensorValue.
If an object of this type contains a value in the range 1 to
9, it represents the number of decimal places in the
fractional part of an associated EntitySensorValue fixed-
point number.
If an object of this type contains a value in the range -8
to -1, it represents the number of accurate digits in the
associated EntitySensorValue fixed-point number.
The value zero indicates the associated EntitySensorValue
object is not a fixed-point number.
Agent implementors must choose a value for the associated
EntitySensorPrecision object so that the precision and
accuracy of the associated EntitySensorValue object is
correctly indicated.
For example, a physical entity representing a temperature
sensor that can measure 0 degrees to 100 degrees C in 0.1
degree increments, +/- 0.05 degrees, would have an
EntitySensorPrecision value of '1', an EntitySensorDataScale
value of 'units(9)', and an EntitySensorValue ranging from
'0' to '1000'. The EntitySensorValue would be interpreted
as 'degrees C * 10'."
SYNTAX Integer32 (-8..9)
EntitySensorValue ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"An object using this data type represents an Entity Sensor
value.
An object of this type SHOULD be defined together with
objects of type EntitySensorDataType, EntitySensorDataScale
and EntitySensorPrecision. Together, associated objects of
those three types are used to identify the semantics of an
object of this data type.
The semantics of an object using this data type are
determined by the value of the associated
EntitySensorDataType object.
If the associated EntitySensorDataType object is equal to
'voltsAC(3)', 'voltsDC(4)', 'amperes(5)', 'watts(6),
'hertz(7)', 'celsius(8)', or 'cmm(11)', then an object of
this type MUST contain a fixed point number ranging from
-999,999,999 to +999,999,999. The value -1000000000
indicates an underflow error. The value +1000000000
indicates an overflow error. The EntitySensorPrecision
indicates how many fractional digits are represented in the
associated EntitySensorValue object.
If the associated EntitySensorDataType object is equal to
'percentRH(9)', then an object of this type MUST contain a
number ranging from 0 to 100.
If the associated EntitySensorDataType object is equal to
'rpm(10)', then an object of this type MUST contain a number
ranging from -999,999,999 to +999,999,999.
If the associated EntitySensorDataType object is equal to
'truthvalue(12)', then an object of this type MUST contain
either the value 'true(1)' or the value 'false(2)'.
If the associated EntitySensorDataType object is equal to
'other(1)' or unknown(2)', then an object of this type MUST
contain a number ranging from -1000000000 to 1000000000."
SYNTAX Integer32 (-1000000000..1000000000)
EntitySensorStatus ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"An object using this data type represents the operational
status of a physical sensor.
The value 'ok(1)' indicates that the agent can obtain the
sensor value.
The value 'unavailable(2)' indicates that the agent
presently cannot obtain the sensor value.
The value 'nonoperational(3)' indicates that the agent
believes the sensor is broken. The sensor could have a hard
failure (disconnected wire), or a soft failure such as out-
of-range, jittery, or wildly fluctuating readings."
SYNTAX INTEGER {
ok(1),
unavailable(2),
nonoperational(3)
}
--
-- Entity Sensor Table
--
entPhySensorTable OBJECT-TYPE
SYNTAX SEQUENCE OF EntPhySensorEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table contains one row per physical sensor represented
by an associated row in the entPhysicalTable."
::= { entitySensorObjects 1 }
entPhySensorEntry OBJECT-TYPE
SYNTAX EntPhySensorEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Information about a particular physical sensor.
An entry in this table describes the present reading of a
sensor, the measurement units and scale, and sensor
operational status.
Entries are created in this table by the agent. An entry
for each physical sensor SHOULD be created at the same time
as the associated entPhysicalEntry. An entry SHOULD be
destroyed if the associated entPhysicalEntry is destroyed."
INDEX { entPhysicalIndex } -- SPARSE-AUGMENTS
::= { entPhySensorTable 1 }
EntPhySensorEntry ::= SEQUENCE {
entPhySensorType EntitySensorDataType,
entPhySensorScale EntitySensorDataScale,
entPhySensorPrecision EntitySensorPrecision,
entPhySensorValue EntitySensorValue,
entPhySensorOperStatus EntitySensorStatus,
entPhySensorUnitsDisplay SnmpAdminString,
entPhySensorValueTimeStamp TimeStamp,
entPhySensorValueUpdateRate Unsigned32
}
entPhySensorType OBJECT-TYPE
SYNTAX EntitySensorDataType
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The type of data returned by the associated
entPhySensorValue object.
This object SHOULD be set by the agent during entry
creation, and the value SHOULD NOT change during operation."
::= { entPhySensorEntry 1 }
entPhySensorScale OBJECT-TYPE
SYNTAX EntitySensorDataScale
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The exponent to apply to values returned by the associated
entPhySensorValue object.
This object SHOULD be set by the agent during entry
creation, and the value SHOULD NOT change during operation."
::= { entPhySensorEntry 2 }
entPhySensorPrecision OBJECT-TYPE
SYNTAX EntitySensorPrecision
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of decimal places of precision in fixed-point
sensor values returned by the associated entPhySensorValue
object.
This object SHOULD be set to '0' when the associated
entPhySensorType value is not a fixed-point type: e.g.,
'percentRH(9)', 'rpm(10)', 'cmm(11)', or 'truthvalue(12)'.
This object SHOULD be set by the agent during entry
creation, and the value SHOULD NOT change during operation."
::= { entPhySensorEntry 3 }
entPhySensorValue OBJECT-TYPE
SYNTAX EntitySensorValue
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The most recent measurement obtained by the agent for this
sensor.
To correctly interpret the value of this object, the
associated entPhySensorType, entPhySensorScale, and
entPhySensorPrecision objects must also be examined."
::= { entPhySensorEntry 4 }
entPhySensorOperStatus OBJECT-TYPE
SYNTAX EntitySensorStatus
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The operational status of the sensor."
::= { entPhySensorEntry 5 }
entPhySensorUnitsDisplay OBJECT-TYPE
SYNTAX SnmpAdminString
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"A textual description of the data units that should be used
in the display of entPhySensorValue."
::= { entPhySensorEntry 6 }
entPhySensorValueTimeStamp OBJECT-TYPE
SYNTAX TimeStamp
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The value of sysUpTime at the time the status and/or value
of this sensor was last obtained by the agent."
::= { entPhySensorEntry 7 }
entPhySensorValueUpdateRate OBJECT-TYPE
SYNTAX Unsigned32
UNITS "milliseconds"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"An indication of the frequency that the agent updates the
associated entPhySensorValue object, representing in
milliseconds.
The value zero indicates:
- the sensor value is updated on demand (e.g.,
when polled by the agent for a get-request),
- the sensor value is updated when the sensor
value changes (event-driven),
- the agent does not know the update rate.
"
::= { entPhySensorEntry 8 }
--
-- Conformance Section
--
entitySensorCompliances OBJECT IDENTIFIER
::= { entitySensorConformance 1 }
entitySensorGroups OBJECT IDENTIFIER
::= { entitySensorConformance 2 }
entitySensorCompliance MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"Describes the requirements for conformance to the Entity
Sensor MIB module."
MODULE -- this module
MANDATORY-GROUPS { entitySensorValueGroup }
MODULE ENTITY-MIB
MANDATORY-GROUPS { entityPhysicalGroup }
::= { entitySensorCompliances 1 }
-- Object Groups
entitySensorValueGroup OBJECT-GROUP
OBJECTS {
entPhySensorType,
entPhySensorScale,
entPhySensorPrecision,
entPhySensorValue,
entPhySensorOperStatus,
entPhySensorUnitsDisplay,
entPhySensorValueTimeStamp,
entPhySensorValueUpdateRate
}
STATUS current
DESCRIPTION
"A collection of objects representing physical entity sensor
information."
::= { entitySensorGroups 1 }
END

458
priv/mibs/ENTITY-STATE-MIB Normal file
View file

@ -0,0 +1,458 @@
ENTITY-STATE-MIB DEFINITIONS ::= BEGIN
IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, mib-2
FROM SNMPv2-SMI
DateAndTime, TEXTUAL-CONVENTION
FROM SNMPv2-TC
MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP
FROM SNMPv2-CONF
entPhysicalIndex
FROM ENTITY-MIB;
entityStateMIB MODULE-IDENTITY
LAST-UPDATED "200609060000Z"
ORGANIZATION "IETF Entity MIB Working Group"
CONTACT-INFO
" General Discussion: entmib@ietf.org
To Subscribe:
http://www.ietf.org/mailman/listinfo/entmib
http://www.ietf.org/html.charters/entmib-charter.html
Sharon Chisholm
Nortel Networks
PO Box 3511 Station C
Ottawa, Ont. K1Y 4H7
Canada
schishol@nortel.com
David T. Perkins
548 Qualbrook Ct
San Jose, CA 95110
USA
Phone: 408 394-8702
dperkins@snmpinfo.com
"
DESCRIPTION
"This MIB defines a state extension to the Entity MIB.
Copyright at The Internet Society 2005. This version
of this MIB module is part of RFC 4268; see the RFC
itself for full legal notices."
REVISION "200609060000Z"
DESCRIPTION
"Initial version, published as RFC 4268."
::= { mib-2 131 }
-- Entity State Objects
entStateObjects OBJECT IDENTIFIER ::= { entityStateMIB 1 }
-- Textual Conventions
EntityAdminState ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
" Represents the various possible administrative states.
A value of 'locked' means the resource is administratively
prohibited from use. A value of 'shuttingDown' means that
usage is administratively limited to current instances of
use. A value of 'unlocked' means the resource is not
administratively prohibited from use. A value of
'unknown' means that this resource is unable to
report administrative state."
SYNTAX INTEGER
{
unknown (1),
locked (2),
shuttingDown (3),
unlocked (4)
}
EntityOperState ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
" Represents the possible values of operational states.
A value of 'disabled' means the resource is totally
inoperable. A value of 'enabled' means the resource
is partially or fully operable. A value of 'testing'
means the resource is currently being tested
and cannot therefore report whether it is operational
or not. A value of 'unknown' means that this
resource is unable to report operational state."
SYNTAX INTEGER
{
unknown (1),
disabled (2),
enabled (3),
testing (4)
}
EntityUsageState ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
" Represents the possible values of usage states.
A value of 'idle' means the resource is servicing no
users. A value of 'active' means the resource is
currently in use and it has sufficient spare capacity
to provide for additional users. A value of 'busy'
means the resource is currently in use, but it
currently has no spare capacity to provide for
additional users. A value of 'unknown' means
that this resource is unable to report usage state."
SYNTAX INTEGER
{
unknown (1),
idle (2),
active (3),
busy (4)
}
EntityAlarmStatus ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
" Represents the possible values of alarm status.
An Alarm [RFC 3877] is a persistent indication
of an error or warning condition.
When no bits of this attribute are set, then no active
alarms are known against this entity and it is not under
repair.
When the 'value of underRepair' is set, the resource is
currently being repaired, which, depending on the
implementation, may make the other values in this bit
string not meaningful.
When the value of 'critical' is set, one or more critical
alarms are active against the resource. When the value
of 'major' is set, one or more major alarms are active
against the resource. When the value of 'minor' is set,
one or more minor alarms are active against the resource.
When the value of 'warning' is set, one or more warning
alarms are active against the resource. When the value
of 'indeterminate' is set, one or more alarms of whose
perceived severity cannot be determined are active
against this resource.
A value of 'unknown' means that this resource is
unable to report alarm state."
SYNTAX BITS
{
unknown (0),
underRepair (1),
critical(2),
major(3),
minor(4),
-- The following are not defined in X.733
warning (5),
indeterminate (6)
}
EntityStandbyStatus ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
" Represents the possible values of standby status.
A value of 'hotStandby' means the resource is not
providing service, but it will be immediately able to
take over the role of the resource to be backed up,
without the need for initialization activity, and will
contain the same information as the resource to be
backed up. A value of 'coldStandy' means that the
resource is to back up another resource, but will not
be immediately able to take over the role of a resource
to be backed up, and will require some initialization
activity. A value of 'providingService' means the
resource is providing service. A value of
'unknown' means that this resource is unable to
report standby state."
SYNTAX INTEGER
{
unknown (1),
hotStandby (2),
coldStandby (3),
providingService (4)
}
--entity State Table
entStateTable OBJECT-TYPE
SYNTAX SEQUENCE OF EntStateEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A table of information about state/status of entities.
This is a sparse augment of the entPhysicalTable. Entries
appear in this table for values of
entPhysicalClass [RFC 4133] that in this implementation
are able to report any of the state or status stored in
this table. "
::= { entStateObjects 1 }
entStateEntry OBJECT-TYPE
SYNTAX EntStateEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"State information about this physical entity."
INDEX { entPhysicalIndex }
::= { entStateTable 1 }
EntStateEntry ::= SEQUENCE {
entStateLastChanged DateAndTime,
entStateAdmin EntityAdminState,
entStateOper EntityOperState,
entStateUsage EntityUsageState,
entStateAlarm EntityAlarmStatus,
entStateStandby EntityStandbyStatus
}
entStateLastChanged OBJECT-TYPE
SYNTAX DateAndTime
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The value of this object is the date and
time when the value of any of entStateAdmin,
entStateOper, entStateUsage, entStateAlarm,
or entStateStandby changed for this entity.
If there has been no change since
the last re-initialization of the local system,
this object contains the date and time of
local system initialization. If there has been
no change since the entity was added to the
local system, this object contains the date and
time of the insertion."
::= { entStateEntry 1 }
entStateAdmin OBJECT-TYPE
SYNTAX EntityAdminState
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The administrative state for this entity.
This object refers to an entities administrative
permission to service both other entities within
its containment hierarchy as well other users of
its services defined by means outside the scope
of this MIB.
Setting this object to 'notSupported' will result
in an 'inconsistentValue' error. For entities that
do not support administrative state, all set
operations will result in an 'inconsistentValue'
error.
Some physical entities exhibit only a subset of the
remaining administrative state values. Some entities
cannot be locked, and hence this object exhibits only
the 'unlocked' state. Other entities cannot be shutdown
gracefully, and hence this object does not exhibit the
'shuttingDown' state. A value of 'inconsistentValue'
will be returned if attempts are made to set this
object to values not supported by its administrative
model."
::= { entStateEntry 2 }
entStateOper OBJECT-TYPE
SYNTAX EntityOperState
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The operational state for this entity.
Note that unlike the state model used within the
Interfaces MIB [RFC 2863], this object does not follow
the administrative state. An administrative state of
down does not predict an operational state
of disabled.
A value of 'testing' means that entity currently being
tested and cannot therefore report whether it is
operational or not.
A value of 'disabled' means that an entity is totally
inoperable and unable to provide service both to entities
within its containment hierarchy, or to other receivers
of its service as defined in ways outside the scope of
this MIB.
A value of 'enabled' means that an entity is fully or
partially operable and able to provide service both to
entities within its containment hierarchy, or to other
receivers of its service as defined in ways outside the
scope of this MIB.
Note that some implementations may not be able to
accurately report entStateOper while the
entStateAdmin object has a value other than 'unlocked'.
In these cases, this object MUST have a value
of 'unknown'."
::= { entStateEntry 3 }
entStateUsage OBJECT-TYPE
SYNTAX EntityUsageState
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The usage state for this entity.
This object refers to an entity's ability to service more
physical entities in a containment hierarchy. A value
of 'idle' means this entity is able to contain other
entities but that no other entity is currently
contained within this entity.
A value of 'active' means that at least one entity is
contained within this entity, but that it could handle
more. A value of 'busy' means that the entity is unable
to handle any additional entities being contained in it.
Some entities will exhibit only a subset of the
usage state values. Entities that are unable to ever
service any entities within a containment hierarchy will
always have a usage state of 'busy'. Some entities will
only ever be able to support one entity within its
containment hierarchy and will therefore only exhibit
values of 'idle' and 'busy'."
::= { entStateEntry 4 }
entStateAlarm OBJECT-TYPE
SYNTAX EntityAlarmStatus
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The alarm status for this entity. It does not include
the alarms raised on child components within its
containment hierarchy.
A value of 'unknown' means that this entity is
unable to report alarm state. Note that this differs
from 'indeterminate', which means that alarm state
is supported and there are alarms against this entity,
but the severity of some of the alarms is not known.
If no bits are set, then this entity supports reporting
of alarms, but there are currently no active alarms
against this entity."
::= { entStateEntry 5 }
entStateStandby OBJECT-TYPE
SYNTAX EntityStandbyStatus
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The standby status for this entity.
Some entities will exhibit only a subset of the
remaining standby state values. If this entity
cannot operate in a standby role, the value of this
object will always be 'providingService'."
::= { entStateEntry 6 }
-- Notifications
entStateNotifications OBJECT IDENTIFIER ::= { entityStateMIB 0 }
entStateOperEnabled NOTIFICATION-TYPE
OBJECTS { entStateAdmin,
entStateAlarm
}
STATUS current
DESCRIPTION
"An entStateOperEnabled notification signifies that the
SNMP entity, acting in an agent role, has detected that
the entStateOper object for one of its entities has
transitioned into the 'enabled' state.
The entity this notification refers can be identified by
extracting the entPhysicalIndex from one of the
variable bindings. The entStateAdmin and entStateAlarm
varbinds may be examined to find out additional
information on the administrative state at the time of
the operation state change as well as to find out whether
there were any known alarms against the entity at that
time that may explain why the physical entity has become
operationally disabled."
::= { entStateNotifications 1 }
entStateOperDisabled NOTIFICATION-TYPE
OBJECTS { entStateAdmin,
entStateAlarm }
STATUS current
DESCRIPTION
"An entStateOperDisabled notification signifies that the
SNMP entity, acting in an agent role, has detected that
the entStateOper object for one of its entities has
transitioned into the 'disabled' state.
The entity this notification refers can be identified by
extracting the entPhysicalIndex from one of the
variable bindings. The entStateAdmin and entStateAlarm
varbinds may be examined to find out additional
information on the administrative state at the time of
the operation state change as well as to find out whether
there were any known alarms against the entity at that
time that may affect the physical entity's
ability to stay operationally enabled."
::= { entStateNotifications 2 }
-- Conformance and Compliance
entStateConformance OBJECT IDENTIFIER ::= { entityStateMIB 2 }
entStateCompliances OBJECT IDENTIFIER
::= { entStateConformance 1 }
entStateCompliance MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"The compliance statement for systems supporting
the Entity State MIB."
MODULE -- this module
MANDATORY-GROUPS {
entStateGroup
}
GROUP entStateNotificationsGroup
DESCRIPTION
"This group is optional."
OBJECT entStateAdmin
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
::= { entStateCompliances 1 }
entStateGroups OBJECT IDENTIFIER ::= { entStateConformance 2 }
entStateGroup OBJECT-GROUP
OBJECTS {
entStateLastChanged,
entStateAdmin,
entStateOper,
entStateUsage,
entStateAlarm,
entStateStandby
}
STATUS current
DESCRIPTION
"Standard Entity State group."
::= { entStateGroups 1}
entStateNotificationsGroup NOTIFICATION-GROUP
NOTIFICATIONS {
entStateOperEnabled,
entStateOperDisabled
}
STATUS current
DESCRIPTION
"Standard Entity State Notification group."
::= { entStateGroups 2}
END

178
priv/mibs/ENTITY-STATE-TC-MIB Normal file
View file

@ -0,0 +1,178 @@
ENTITY-STATE-TC-MIB DEFINITIONS ::= BEGIN
IMPORTS
MODULE-IDENTITY, mib-2 FROM SNMPv2-SMI
TEXTUAL-CONVENTION FROM SNMPv2-TC;
entityStateTc MODULE-IDENTITY
LAST-UPDATED "200511220000Z"
ORGANIZATION "IETF Entity MIB Working Group"
CONTACT-INFO
"General Discussion: entmib@ietf.org
To Subscribe:
http://www.ietf.org/mailman/listinfo/entmib
http://www.ietf.org/html.charters/entmib-charter.html
Sharon Chisholm
Nortel Networks
PO Box 3511 Station C
Ottawa, Ont. K1Y 4H7
Canada
schishol@nortel.com
David T. Perkins
548 Qualbrook Ct
San Jose, CA 95110
USA
Phone: 408 394-8702
dperkins@snmpinfo.com"
DESCRIPTION
"This MIB defines state textual conventions.
Copyright (C) The Internet Society 2005. This version
of this MIB module is part of RFC 4268; see the RFC
itself for full legal notices."
REVISION "200511220000Z"
DESCRIPTION
"Initial version, published as RFC 4268."
::= { mib-2 130 }
EntityAdminState ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
" Represents the various possible administrative states.
A value of 'locked' means the resource is administratively
prohibited from use. A value of 'shuttingDown' means that
usage is administratively limited to current instances of
use. A value of 'unlocked' means the resource is not
administratively prohibited from use. A value of
'unknown' means that this resource is unable to
report administrative state."
SYNTAX INTEGER
{
unknown (1),
locked (2),
shuttingDown (3),
unlocked (4)
}
EntityOperState ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
" Represents the possible values of operational states.
A value of 'disabled' means the resource is totally
inoperable. A value of 'enabled' means the resource
is partially or fully operable. A value of 'testing'
means the resource is currently being tested
and cannot therefore report whether it is operational
or not. A value of 'unknown' means that this
resource is unable to report operational state."
SYNTAX INTEGER
{
unknown (1),
disabled (2),
enabled (3),
testing (4)
}
EntityUsageState ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
" Represents the possible values of usage states.
A value of 'idle' means the resource is servicing no
users. A value of 'active' means the resource is
currently in use and it has sufficient spare capacity
to provide for additional users. A value of 'busy'
means the resource is currently in use, but it
currently has no spare capacity to provide for
additional users. A value of 'unknown' means
that this resource is unable to report usage state."
SYNTAX INTEGER
{
unknown (1),
idle (2),
active (3),
busy (4)
}
EntityAlarmStatus ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
" Represents the possible values of alarm status.
An Alarm [RFC3877] is a persistent indication
of an error or warning condition.
When no bits of this attribute are set, then no active
alarms are known against this entity and it is not under
repair.
When the 'value of underRepair' is set, the resource is
currently being repaired, which, depending on the
implementation, may make the other values in this bit
string not meaningful.
When the value of 'critical' is set, one or more critical
alarms are active against the resource. When the value
of 'major' is set, one or more major alarms are active
against the resource. When the value of 'minor' is set,
one or more minor alarms are active against the resource.
When the value of 'warning' is set, one or more warning
alarms are active against the resource. When the value
of 'indeterminate' is set, one or more alarms of whose
perceived severity cannot be determined are active
against this resource.
A value of 'unknown' means that this resource is
unable to report alarm state."
SYNTAX BITS
{
unknown (0),
underRepair (1),
critical(2),
major(3),
minor(4),
-- The following are not defined in X.733
warning (5),
indeterminate (6)
}
EntityStandbyStatus ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
" Represents the possible values of standby status.
A value of 'hotStandby' means the resource is not
providing service, but it will be immediately able to
take over the role of the resource to be backed up,
without the need for initialization activity, and will
contain the same information as the resource to be
backed up. A value of 'coldStandy' means that the
resource is to back up another resource, but will not
be immediately able to take over the role of a resource
to be backed up, and will require some initialization
activity. A value of 'providingService' means the
resource is providing service. A value of
'unknown' means that this resource is unable to
report standby state."
SYNTAX INTEGER
{
unknown (1),
hotStandby (2),
coldStandby (3),
providingService (4)
}
END

1862
priv/mibs/EtherLike-MIB Normal file
View file

File diff suppressed because it is too large Load diff

2844
priv/mibs/FCMGMT-MIB Normal file
View file

File diff suppressed because it is too large Load diff

2150
priv/mibs/FDDI-SMT73-MIB Normal file
View file

File diff suppressed because it is too large Load diff

61
priv/mibs/FLOAT-TC-MIB Normal file
View file

@ -0,0 +1,61 @@
FLOAT-TC-MIB DEFINITIONS ::= BEGIN
IMPORTS
MODULE-IDENTITY,
mib-2 FROM SNMPv2-SMI -- RFC 2578
TEXTUAL-CONVENTION FROM SNMPv2-TC; -- RFC 2579
floatTcMIB MODULE-IDENTITY
LAST-UPDATED "201107270000Z" -- July 27, 2011
ORGANIZATION "IETF OPSAWG Working Group"
CONTACT-INFO "WG Email: opsawg@ietf.org
Editor: Randy Presuhn
randy_presuhn@mindspring.com"
DESCRIPTION "Textual conventions for the representation
of floating-point numbers.
Copyright (c) 2011 IETF Trust and the persons
identified as authors of the code. All rights
reserved.
Redistribution and use in source and binary forms,
with or without modification, is permitted pursuant
to, and subject to the license terms contained in,
the Simplified BSD License set forth in Section
4.c of the IETF Trust's Legal Provisions Relating
to IETF Documents
(http://trustee.ietf.org/license-info).
This version of this MIB module is part of RFC 6340;
see the RFC itself for full legal notices."
REVISION "201107270000Z" -- July 27, 2011
DESCRIPTION "Initial version, published as RFC 6340."
::= { mib-2 201 }
Float32TC ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION "This type represents a 32-bit (4-octet) IEEE
floating-point number in binary interchange format."
REFERENCE "IEEE Standard for Floating-Point Arithmetic,
Standard 754-2008"
SYNTAX OCTET STRING (SIZE(4))
Float64TC ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION "This type represents a 64-bit (8-octet) IEEE
floating-point number in binary interchange format."
REFERENCE "IEEE Standard for Floating-Point Arithmetic,
Standard 754-2008"
SYNTAX OCTET STRING (SIZE(8))
Float128TC ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION "This type represents a 128-bit (16-octet) IEEE
floating-point number in binary interchange format."
REFERENCE "IEEE Standard for Floating-Point Arithmetic,
Standard 754-2008"
SYNTAX OCTET STRING (SIZE(16))
END

1084
priv/mibs/FRAME-RELAY-DTE-MIB Normal file
View file

File diff suppressed because it is too large Load diff

368
priv/mibs/FROGFOOT-RESOURCES-MIB Normal file
View file

@ -0,0 +1,368 @@
FROGFOOT-RESOURCES-MIB
-- -*- mib -*-
DEFINITIONS ::= BEGIN
-- Frogfoot Networks CC Resources MIB
--
-- The idea behind this is to measure usage of resources.
-- It does not contain information about the system such as
-- cpu/disk types, etc.
--
IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, Integer32, Gauge32,
enterprises
FROM SNMPv2-SMI
TEXTUAL-CONVENTION, DisplayString
FROM SNMPv2-TC
MODULE-COMPLIANCE, OBJECT-GROUP
FROM SNMPv2-CONF;
resources MODULE-IDENTITY
LAST-UPDATED "200407170000Z"
ORGANIZATION "Frogfoot Networks"
CONTACT-INFO
" Abraham van der Merwe
Postal: Frogfoot Networks CC
P.O. Box 23618
Claremont
Cape Town
7735
South Africa
Phone: +27 82 565 4451
Email: abz@frogfoot.net"
DESCRIPTION
"The MIB module to describe system resources."
::= { system 1 }
frogfoot OBJECT IDENTIFIER ::= { enterprises 10002 }
servers OBJECT IDENTIFIER ::= { frogfoot 1 }
system OBJECT IDENTIFIER ::= { servers 1 }
memory OBJECT IDENTIFIER ::= { resources 1 }
swap OBJECT IDENTIFIER ::= { resources 2 }
storage OBJECT IDENTIFIER ::= { resources 3 }
load OBJECT IDENTIFIER ::= { resources 4 }
resMIB OBJECT IDENTIFIER ::= { resources 31 }
resMIBObjects OBJECT IDENTIFIER ::= { resMIB 1 }
resConformance OBJECT IDENTIFIER ::= { resMIB 2 }
resGroups OBJECT IDENTIFIER ::= { resConformance 1 }
resCompliances OBJECT IDENTIFIER ::= { resConformance 2 }
TableIndex ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d"
STATUS current
DESCRIPTION
"A unique value, greater than zero. It is recommended
that values are assigned contiguously starting from 1."
SYNTAX Integer32 (1..2147483647)
--
-- Memory statistics
--
memTotal OBJECT-TYPE
SYNTAX Gauge32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Total usable physical memory (in KB)"
::= { memory 1 }
memFree OBJECT-TYPE
SYNTAX Gauge32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Available physical memory (in KB)"
::= { memory 2 }
memBuffer OBJECT-TYPE
SYNTAX Gauge32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Physical memory used by buffers (in KB)"
::= { memory 3 }
memCache OBJECT-TYPE
SYNTAX Gauge32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Physical memory used for caching (in KB)"
::= { memory 4 }
--
-- Swap space statistics
--
swapTotal OBJECT-TYPE
SYNTAX Gauge32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Total swap space size (in KB)"
::= { swap 1 }
swapFree OBJECT-TYPE
SYNTAX Gauge32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Swap space still available (in KB)"
::= { swap 2 }
--
-- Disk space statistics
--
diskNumber OBJECT-TYPE
SYNTAX Integer32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of mounted disks present on this system."
::= { storage 1 }
diskTable OBJECT-TYPE
SYNTAX SEQUENCE OF DiskEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A table of mounted disks on this system."
::= { storage 2 }
diskEntry OBJECT-TYPE
SYNTAX DiskEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry containing management information applicable
to a particular mounted disk on the system."
INDEX { diskIndex }
::= { diskTable 1 }
DiskEntry ::=
SEQUENCE {
diskIndex TableIndex,
diskDev DisplayString,
diskDir DisplayString,
diskFSType INTEGER,
diskTotal Gauge32,
diskFree Gauge32
}
diskIndex OBJECT-TYPE
SYNTAX TableIndex
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A unique value, greater than zero, for each disk on the
system. It is recommended that values are assigned contiguously
starting from 1."
::= { diskEntry 1 }
diskDev OBJECT-TYPE
SYNTAX DisplayString
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"A textual string containing the disk device name."
::= { diskEntry 2 }
diskDir OBJECT-TYPE
SYNTAX DisplayString
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"A textual string containing the disk mount point."
::= { diskEntry 3 }
diskFSType OBJECT-TYPE
SYNTAX INTEGER {
unknown(0), -- Unknown File System
adfs(1), -- Acorn Advanced Disc Filing System
affs(2), -- Amiga Fast File System
coda(3), -- CODA File System
cramfs(4), -- cram File System for small storage (ROMs etc)
ext2(5), -- Ext2 File System
hpfs(6), -- OS/2 HPFS File System
iso9660(7), -- ISO 9660 (CDROM) File System
jffs2(8), -- Journalling Flash File System
jfs(9), -- JFS File System
minix(10), -- Minix File System
msdos(11), -- FAT-based File Systems
ncpfs(12), -- Novell Netware(tm) File System
nfs(13), -- Network File Sharing Protocol
ntfs(14), -- NTFS File System (Windows NT)
qnx4(15), -- QNX4 File System
reiserfs(16), -- ReiserFS Journalling File System
romfs(17), -- ROM File System
smbfs(18), -- Server Message Block (SMB) Protocol
sysv(19), -- SystemV/V7/Xenix/Coherent File System
tmpfs(20), -- Virtual Memory File System
udf(21), -- UDF (DVD, CDRW, etc) File System
ufs(22), -- UFS File System (SunOS, FreeBSD, etc)
vxfs(23), -- VERITAS VxFS(TM) File System
xfs(24) -- XFS (SGI) Journalling File System
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The type of file system present on the disk. This
does not include fake file systems such as the proc file
system, devfs, etc. Additional types may be assigned by
Frogfoot Networks in the future."
::= { diskEntry 4 }
diskTotal OBJECT-TYPE
SYNTAX Gauge32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Total space on disk (in MB)"
::= { diskEntry 5 }
diskFree OBJECT-TYPE
SYNTAX Gauge32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Disk space still available (in MB)"
::= { diskEntry 6 }
--
-- Load Average statistics
--
loadNumber OBJECT-TYPE
SYNTAX Integer32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of load averages stored in the
load average table."
::= { load 1 }
loadTable OBJECT-TYPE
SYNTAX SEQUENCE OF LoadEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Load average information."
::= { load 2 }
loadEntry OBJECT-TYPE
SYNTAX LoadEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry containing load average information."
INDEX { loadIndex }
::= { loadTable 1 }
LoadEntry ::=
SEQUENCE {
loadIndex TableIndex,
loadDescr DisplayString,
loadValue Gauge32
}
loadIndex OBJECT-TYPE
SYNTAX TableIndex
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A unique value, greater than zero, for each
load average stored."
::= { loadEntry 1 }
loadDescr OBJECT-TYPE
SYNTAX DisplayString
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"A description of each load average."
::= { loadEntry 2 }
loadValue OBJECT-TYPE
SYNTAX Gauge32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The 1,5 and 10 minute load averages. These values are
stored as a percentage of processor load."
::= { loadEntry 3 }
--
-- Compliance Statements
--
resCompliance MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"The compliance statement for SNMP entities which have
system resources such as volatile and non-volatile
storage."
MODULE
MANDATORY-GROUPS { resMemGroup, resSwapGroup, resDiskGroup, resLoadGroup }
GROUP resMemGroup
DESCRIPTION
"This group is mandatory for those systems which have
any form of volatile storage."
GROUP resSwapGroup
DESCRIPTION
"This group is mandatory for those systems which have
the ability to temporarily swap unused pages to disk."
GROUP resDiskGroup
DESCRIPTION
"This group is mandatory for those systems which have
any form of non-volatile storage."
GROUP resLoadGroup
DESCRIPTION
"This group is mandatory for those systems which store
any form of processor load average information."
::= { resCompliances 1 }
resMemGroup OBJECT-GROUP
OBJECTS { memTotal, memFree, memBuffer, memCache }
STATUS current
DESCRIPTION
"A collection of objects providing information specific to
volatile system storage."
::= { resGroups 1 }
resSwapGroup OBJECT-GROUP
OBJECTS { swapTotal, swapFree }
STATUS current
DESCRIPTION
"A collection of objects providing information specific to
storage used for swapping pages to disk."
::= { resGroups 2 }
resDiskGroup OBJECT-GROUP
OBJECTS { diskNumber, diskDev, diskDir, diskFSType, diskTotal, diskFree }
STATUS current
DESCRIPTION
"A collection of objects providing information specific to
non-volatile system storage."
::= { resGroups 3 }
resLoadGroup OBJECT-GROUP
OBJECTS { loadNumber, loadDescr, loadValue }
STATUS current
DESCRIPTION
"A collection of objects providing information specific to
processor load averages."
::= { resGroups 4 }
END

2168
priv/mibs/GBOND-MIB Normal file
View file

File diff suppressed because it is too large Load diff

683
priv/mibs/HC-ALARM-MIB Normal file
View file

@ -0,0 +1,683 @@
HC-ALARM-MIB DEFINITIONS ::= BEGIN
IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE,
Integer32, Counter32, Unsigned32
FROM SNMPv2-SMI
MODULE-COMPLIANCE, OBJECT-GROUP,
NOTIFICATION-GROUP
FROM SNMPv2-CONF
RowStatus, VariablePointer, StorageType,
TEXTUAL-CONVENTION
FROM SNMPv2-TC
CounterBasedGauge64
FROM HCNUM-TC
rmon, OwnerString, rmonEventGroup
FROM RMON-MIB;
hcAlarmMIB MODULE-IDENTITY
LAST-UPDATED "200212160000Z"
ORGANIZATION "Netgear Inc"
CONTACT-INFO ""
DESCRIPTION
"This module defines Remote Monitoring MIB extensions for
High Capacity Alarms.
Copyright (C) The Internet Society (2002). This version
of this MIB module is part of RFC 3434; see the RFC
itself for full legal notices."
REVISION "200212160000Z"
DESCRIPTION
"Initial version of the High Capacity Alarm MIB module.
This version published as RFC 3434."
::= { rmon 29 }
hcAlarmObjects OBJECT IDENTIFIER ::= { hcAlarmMIB 1 }
hcAlarmNotifications OBJECT IDENTIFIER ::= { hcAlarmMIB 2 }
hcAlarmConformance OBJECT IDENTIFIER ::= { hcAlarmMIB 3 }
hcAlarmControlObjects OBJECT IDENTIFIER ::= { hcAlarmObjects 1 }
hcAlarmCapabilitiesObjects OBJECT IDENTIFIER
::= { hcAlarmObjects 2 }
--
-- Textual Conventions
--
HcValueStatus ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"This data type indicates the validity and sign of the data
in associated object instances which represent the absolute
value of a high capacity numeric quantity. Such an object
may be represented with one or more object instances. An
object of type HcValueStatus MUST be defined within the same
structure as the object(s) representing the high capacity
absolute value.
If the associated object instance(s) representing the high
capacity absolute value could not be accessed during the
sampling interval, and is therefore invalid, then the
associated HcValueStatus object will contain the value
'valueNotAvailable(1)'.
If the associated object instance(s) representing the high
capacity absolute value are valid and actual value of the
sample is greater than or equal to zero, then the associated
HcValueStatus object will contain the value
'valuePositive(2)'.
If the associated object instance(s) representing the high
capacity absolute value are valid and the actual value of
the sample is less than zero, then the associated
HcValueStatus object will contain the value
'valueNegative(3)'. The associated absolute value should be
multiplied by -1 to obtain the true sample value."
SYNTAX INTEGER {
valueNotAvailable(1),
valuePositive(2),
valueNegative(3)
}
--
-- High Capacity Alarm Table
--
hcAlarmTable OBJECT-TYPE
SYNTAX SEQUENCE OF HcAlarmEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A list of entries for the configuration of high capacity
alarms."
::= { hcAlarmControlObjects 1 }
hcAlarmEntry OBJECT-TYPE
SYNTAX HcAlarmEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A conceptual row in the hcAlarmTable. Entries are usually
created in this table by management application action, but
may also be created by agent action as well."
INDEX { hcAlarmIndex }
::= { hcAlarmTable 1 }
HcAlarmEntry ::= SEQUENCE {
hcAlarmIndex Integer32,
hcAlarmInterval Integer32,
hcAlarmVariable VariablePointer,
hcAlarmSampleType INTEGER,
hcAlarmAbsValue CounterBasedGauge64,
hcAlarmValueStatus HcValueStatus,
hcAlarmStartupAlarm INTEGER,
hcAlarmRisingThreshAbsValueLo Unsigned32,
hcAlarmRisingThreshAbsValueHi Unsigned32,
hcAlarmRisingThresholdValStatus HcValueStatus,
hcAlarmFallingThreshAbsValueLo Unsigned32,
hcAlarmFallingThreshAbsValueHi Unsigned32,
hcAlarmFallingThresholdValStatus HcValueStatus,
hcAlarmRisingEventIndex Integer32,
hcAlarmFallingEventIndex Integer32,
hcAlarmValueFailedAttempts Counter32,
hcAlarmOwner OwnerString,
hcAlarmStorageType StorageType,
hcAlarmStatus RowStatus }
hcAlarmIndex OBJECT-TYPE
SYNTAX Integer32 (1..65535)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An arbitrary integer index value used to uniquely identify
this high capacity alarm entry."
::= { hcAlarmEntry 1 }
hcAlarmInterval OBJECT-TYPE
SYNTAX Integer32 (1..2147483647)
UNITS "seconds"
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The interval in seconds over which the data is sampled and
compared with the rising and falling thresholds. When
setting this variable, care should be taken in the case of
deltaValue sampling - the interval should be set short
enough that the sampled variable is very unlikely to
increase or decrease by more than 2^63 - 1 during a single
sampling interval.
This object may not be modified if the associated
hcAlarmStatus object is equal to active(1)."
::= { hcAlarmEntry 2 }
hcAlarmVariable OBJECT-TYPE
SYNTAX VariablePointer
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The object identifier of the particular variable to be
sampled. Only variables that resolve to an ASN.1 primitive
type of INTEGER (INTEGER, Integer32, Counter32, Counter64,
Gauge, or TimeTicks) may be sampled.
Because SNMP access control is articulated entirely in terms
of the contents of MIB views, no access control mechanism
exists that can restrict the value of this object to
identify only those objects that exist in a particular MIB
view. Because there is thus no acceptable means of
restricting the read access that could be obtained through
the alarm mechanism, the probe must only grant write access
to this object in those views that have read access to all
objects on the probe.
This object may not be modified if the associated
hcAlarmStatus object is equal to active(1)."
::= { hcAlarmEntry 3 }
hcAlarmSampleType OBJECT-TYPE
SYNTAX INTEGER {
absoluteValue(1),
deltaValue(2)
}
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The method of sampling the selected variable and
calculating the value to be compared against the thresholds.
If the value of this object is absoluteValue(1), the value
of the selected variable will be compared directly with the
thresholds at the end of the sampling interval. If the
value of this object is deltaValue(2), the value of the
selected variable at the last sample will be subtracted from
the current value, and the difference compared with the
thresholds.
If the associated hcAlarmVariable instance could not be
obtained at the previous sample interval, then a delta
sample is not possible, and the value of the associated
hcAlarmValueStatus object for this interval will be
valueNotAvailable(1).
This object may not be modified if the associated
hcAlarmStatus object is equal to active(1)."
::= { hcAlarmEntry 4 }
hcAlarmAbsValue OBJECT-TYPE
SYNTAX CounterBasedGauge64
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The absolute value (i.e., unsigned value) of the
hcAlarmVariable statistic during the last sampling period.
The value during the current sampling period is not made
available until the period is completed.
To obtain the true value for this sampling interval, the
associated instance of hcAlarmValueStatus must be checked,
and the value of this object adjusted as necessary.
If the MIB instance could not be accessed during the
sampling interval, then this object will have a value of
zero and the associated instance of hcAlarmValueStatus will
be set to 'valueNotAvailable(1)'."
::= { hcAlarmEntry 5 }
hcAlarmValueStatus OBJECT-TYPE
SYNTAX HcValueStatus
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object indicates the validity and sign of the data for
the hcAlarmAbsValue object, as described in the
HcValueStatus textual convention."
::= { hcAlarmEntry 6 }
hcAlarmStartupAlarm OBJECT-TYPE
SYNTAX INTEGER {
risingAlarm(1),
fallingAlarm(2),
risingOrFallingAlarm(3)
}
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The alarm that may be sent when this entry is first set to
active. If the first sample after this entry becomes active
is greater than or equal to the rising threshold and this
object is equal to risingAlarm(1) or
risingOrFallingAlarm(3), then a single rising alarm will be
generated. If the first sample after this entry becomes
valid is less than or equal to the falling threshold and
this object is equal to fallingAlarm(2) or
risingOrFallingAlarm(3), then a single falling alarm will be
generated.
This object may not be modified if the associated
hcAlarmStatus object is equal to active(1)."
::= { hcAlarmEntry 7 }
hcAlarmRisingThreshAbsValueLo OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The lower 32 bits of the absolute value for threshold for
the sampled statistic. The actual threshold value is
determined by the associated instances of the
hcAlarmRisingThreshAbsValueHi and
hcAlarmRisingThresholdValStatus objects, as follows:
ABS(threshold) = hcAlarmRisingThreshAbsValueLo +
(hcAlarmRisingThreshAbsValueHi * 2^^32)
The absolute value of the threshold is adjusted as required,
as described in the HcValueStatus textual convention. These
three object instances are conceptually combined to
represent the rising threshold for this entry.
When the current sampled value is greater than or equal to
this threshold, and the value at the last sampling interval
was less than this threshold, a single event will be
generated. A single event will also be generated if the
first sample after this entry becomes valid is greater than
or equal to this threshold and the associated
hcAlarmStartupAlarm is equal to risingAlarm(1) or
risingOrFallingAlarm(3).
After a rising event is generated, another such event will
not be generated until the sampled value falls below this
threshold and reaches the threshold identified by the
hcAlarmFallingThreshAbsValueLo,
hcAlarmFallingThreshAbsValueHi, and
hcAlarmFallingThresholdValStatus objects.
This object may not be modified if the associated
hcAlarmStatus object is equal to active(1)."
::= { hcAlarmEntry 8 }
hcAlarmRisingThreshAbsValueHi OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The upper 32 bits of the absolute value for threshold for
the sampled statistic. The actual threshold value is
determined by the associated instances of the
hcAlarmRisingThreshAbsValueLo and
hcAlarmRisingThresholdValStatus objects, as follows:
ABS(threshold) = hcAlarmRisingThreshAbsValueLo +
(hcAlarmRisingThreshAbsValueHi * 2^^32)
The absolute value of the threshold is adjusted as required,
as described in the HcValueStatus textual convention. These
three object instances are conceptually combined to
represent the rising threshold for this entry.
When the current sampled value is greater than or equal to
this threshold, and the value at the last sampling interval
was less than this threshold, a single event will be
generated. A single event will also be generated if the
first sample after this entry becomes valid is greater than
or equal to this threshold and the associated
hcAlarmStartupAlarm is equal to risingAlarm(1) or
risingOrFallingAlarm(3).
After a rising event is generated, another such event will
not be generated until the sampled value falls below this
threshold and reaches the threshold identified by the
hcAlarmFallingThreshAbsValueLo,
hcAlarmFallingThreshAbsValueHi, and
hcAlarmFallingThresholdValStatus objects.
This object may not be modified if the associated
hcAlarmStatus object is equal to active(1)."
::= { hcAlarmEntry 9 }
hcAlarmRisingThresholdValStatus OBJECT-TYPE
SYNTAX HcValueStatus
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This object indicates the sign of the data for the rising
threshold, as defined by the hcAlarmRisingThresAbsValueLo
and hcAlarmRisingThresAbsValueHi objects, as described in
the HcValueStatus textual convention.
The enumeration 'valueNotAvailable(1)' is not allowed, and
the associated hcAlarmStatus object cannot be equal to
'active(1)' if this object is set to this value.
This object may not be modified if the associated
hcAlarmStatus object is equal to active(1)."
::= { hcAlarmEntry 10 }
hcAlarmFallingThreshAbsValueLo OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The lower 32 bits of the absolute value for threshold for
the sampled statistic. The actual threshold value is
determined by the associated instances of the
hcAlarmFallingThreshAbsValueHi and
hcAlarmFallingThresholdValStatus objects, as follows:
ABS(threshold) = hcAlarmFallingThreshAbsValueLo +
(hcAlarmFallingThreshAbsValueHi * 2^^32)
The absolute value of the threshold is adjusted as required,
as described in the HcValueStatus textual convention. These
three object instances are conceptually combined to
represent the falling threshold for this entry.
When the current sampled value is less than or equal to this
threshold, and the value at the last sampling interval was
greater than this threshold, a single event will be
generated. A single event will also be generated if the
first sample after this entry becomes valid is less than or
equal to this threshold and the associated
hcAlarmStartupAlarm is equal to fallingAlarm(2) or
risingOrFallingAlarm(3).
After a falling event is generated, another such event will
not be generated until the sampled value rises above this
threshold and reaches the threshold identified by the
hcAlarmRisingThreshAbsValueLo,
hcAlarmRisingThreshAbsValueHi, and
hcAlarmRisingThresholdValStatus objects.
This object may not be modified if the associated
hcAlarmStatus object is equal to active(1)."
::= { hcAlarmEntry 11 }
hcAlarmFallingThreshAbsValueHi OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The upper 32 bits of the absolute value for threshold for
the sampled statistic. The actual threshold value is
determined by the associated instances of the
hcAlarmFallingThreshAbsValueLo and
hcAlarmFallingThresholdValStatus objects, as follows:
ABS(threshold) = hcAlarmFallingThreshAbsValueLo +
(hcAlarmFallingThreshAbsValueHi * 2^^32)
The absolute value of the threshold is adjusted as required,
as described in the HcValueStatus textual convention. These
three object instances are conceptually combined to
represent the falling threshold for this entry.
When the current sampled value is less than or equal to this
threshold, and the value at the last sampling interval was
greater than this threshold, a single event will be
generated. A single event will also be generated if the
first sample after this entry becomes valid is less than or
equal to this threshold and the associated
hcAlarmStartupAlarm is equal to fallingAlarm(2) or
risingOrFallingAlarm(3).
After a falling event is generated, another such event will
not be generated until the sampled value rises above this
threshold and reaches the threshold identified by the
hcAlarmRisingThreshAbsValueLo,
hcAlarmRisingThreshAbsValueHi, and
hcAlarmRisingThresholdValStatus objects.
This object may not be modified if the associated
hcAlarmStatus object is equal to active(1)."
::= { hcAlarmEntry 12 }
hcAlarmFallingThresholdValStatus OBJECT-TYPE
SYNTAX HcValueStatus
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This object indicates the sign of the data for the falling
threshold, as defined by the hcAlarmFallingThreshAbsValueLo
and hcAlarmFallingThreshAbsValueHi objects, as described in
the HcValueStatus textual convention.
The enumeration 'valueNotAvailable(1)' is not allowed, and
the associated hcAlarmStatus object cannot be equal to
'active(1)' if this object is set to this value.
This object may not be modified if the associated
hcAlarmStatus object is equal to active(1)."
::= { hcAlarmEntry 13 }
hcAlarmRisingEventIndex OBJECT-TYPE
SYNTAX Integer32 (0..65535)
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The index of the eventEntry that is used when a rising
threshold is crossed. The eventEntry identified by a
particular value of this index is the same as identified by
the same value of the eventIndex object. If there is no
corresponding entry in the eventTable, then no association
exists. In particular, if this value is zero, no associated
event will be generated, as zero is not a valid event index.
This object may not be modified if the associated
hcAlarmStatus object is equal to active(1)."
::= { hcAlarmEntry 14 }
hcAlarmFallingEventIndex OBJECT-TYPE
SYNTAX Integer32 (0..65535)
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The index of the eventEntry that is used when a falling
threshold is crossed. The eventEntry identified by a
particular value of this index is the same as identified by
the same value of the eventIndex object. If there is no
corresponding entry in the eventTable, then no association
exists. In particular, if this value is zero, no associated
event will be generated, as zero is not a valid event index.
This object may not be modified if the associated
hcAlarmStatus object is equal to active(1)."
::= { hcAlarmEntry 15 }
hcAlarmValueFailedAttempts OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of times the associated hcAlarmVariable instance
was polled on behalf of this hcAlarmEntry, (while in the
active state) and the value was not available. This counter
may experience a discontinuity if the agent restarts,
indicated by the value of sysUpTime."
::= { hcAlarmEntry 16 }
hcAlarmOwner OBJECT-TYPE
SYNTAX OwnerString
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The entity that configured this entry and is therefore
using the resources assigned to it."
::= { hcAlarmEntry 17 }
hcAlarmStorageType OBJECT-TYPE
SYNTAX StorageType
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The type of non-volatile storage configured for this entry.
If this object is equal to 'permanent(4)', then the
associated hcAlarmRisingEventIndex and
hcAlarmFallingEventIndex objects must be writable."
::= { hcAlarmEntry 18 }
hcAlarmStatus OBJECT-TYPE
SYNTAX RowStatus
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The status of this row.
An entry MUST NOT exist in the active state unless all
objects in the entry have an appropriate value, as described
in the description clause for each writable object.
The hcAlarmStatus object may be modified if the associated
instance of this object is equal to active(1),
notInService(2), or notReady(3). All other writable objects
may be modified if the associated instance of this object is
equal to notInService(2) or notReady(3)."
::= { hcAlarmEntry 19 }
--
-- Capabilities
--
hcAlarmCapabilities OBJECT-TYPE
SYNTAX BITS {
hcAlarmCreation(0),
hcAlarmNvStorage(1)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"An indication of the high capacity alarm capabilities
supported by this agent.
If the 'hcAlarmCreation' BIT is set, then this agent allows
NMS applications to create entries in the hcAlarmTable.
If the 'hcAlarmNvStorage' BIT is set, then this agent allows
entries in the hcAlarmTable which will be recreated after a
system restart, as controlled by the hcAlarmStorageType
object."
::= { hcAlarmCapabilitiesObjects 1 }
--
-- Notifications
--
hcAlarmNotifPrefix OBJECT IDENTIFIER
::= { hcAlarmNotifications 0 }
hcRisingAlarm NOTIFICATION-TYPE
OBJECTS { hcAlarmVariable,
hcAlarmSampleType,
hcAlarmAbsValue,
hcAlarmValueStatus,
hcAlarmRisingThreshAbsValueLo,
hcAlarmRisingThreshAbsValueHi,
hcAlarmRisingThresholdValStatus,
hcAlarmRisingEventIndex }
STATUS current
DESCRIPTION
"The SNMP notification that is generated when a high
capacity alarm entry crosses its rising threshold and
generates an event that is configured for sending SNMP
traps.
The hcAlarmEntry object instances identified in the OBJECTS
clause are from the entry that causes this notification to
be generated."
::= { hcAlarmNotifPrefix 1 }
hcFallingAlarm NOTIFICATION-TYPE
OBJECTS { hcAlarmVariable,
hcAlarmSampleType,
hcAlarmAbsValue,
hcAlarmValueStatus,
hcAlarmFallingThreshAbsValueLo,
hcAlarmFallingThreshAbsValueHi,
hcAlarmFallingThresholdValStatus,
hcAlarmFallingEventIndex }
STATUS current
DESCRIPTION
"The SNMP notification that is generated when a high
capacity alarm entry crosses its falling threshold and
generates an event that is configured for sending SNMP
traps.
The hcAlarmEntry object instances identified in the OBJECTS
clause are from the entry that causes this notification to
be generated."
::= { hcAlarmNotifPrefix 2 }
--
-- Conformance Section
--
hcAlarmCompliances OBJECT IDENTIFIER ::= { hcAlarmConformance 1 }
hcAlarmGroups OBJECT IDENTIFIER ::= { hcAlarmConformance 2 }
hcAlarmCompliance MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"Describes the requirements for conformance to the High
Capacity Alarm MIB."
MODULE -- this module
MANDATORY-GROUPS {
hcAlarmControlGroup,
hcAlarmCapabilitiesGroup,
hcAlarmNotificationsGroup
}
MODULE RMON-MIB
MANDATORY-GROUPS { rmonEventGroup }
::= { hcAlarmCompliances 1 }
-- Object Groups
hcAlarmControlGroup OBJECT-GROUP
OBJECTS {
hcAlarmInterval,
hcAlarmVariable,
hcAlarmSampleType,
hcAlarmAbsValue,
hcAlarmValueStatus,
hcAlarmStartupAlarm,
hcAlarmRisingThreshAbsValueLo,
hcAlarmRisingThreshAbsValueHi,
hcAlarmRisingThresholdValStatus,
hcAlarmFallingThreshAbsValueLo,
hcAlarmFallingThreshAbsValueHi,
hcAlarmFallingThresholdValStatus,
hcAlarmRisingEventIndex,
hcAlarmFallingEventIndex,
hcAlarmValueFailedAttempts,
hcAlarmOwner,
hcAlarmStorageType,
hcAlarmStatus
}
STATUS current
DESCRIPTION
"A collection of objects used to configure entries for high
capacity alarm threshold monitoring purposes."
::= { hcAlarmGroups 1 }
hcAlarmCapabilitiesGroup OBJECT-GROUP
OBJECTS {
hcAlarmCapabilities
}
STATUS current
DESCRIPTION
"A collection of objects used to indicate an agent's high
capacity alarm threshold monitoring capabilities."
::= { hcAlarmGroups 2 }
hcAlarmNotificationsGroup NOTIFICATION-GROUP
NOTIFICATIONS {
hcRisingAlarm,
hcFallingAlarm
}
STATUS current
DESCRIPTION
"A collection of notifications to deliver information
related to a high capacity rising or falling threshold event
to a management application."
::= { hcAlarmGroups 3 }
END

231
priv/mibs/HC-PerfHist-TC-MIB Normal file
View file

@ -0,0 +1,231 @@
-- *****************************************************************
-- HC-PerfHist-TC-MIB.my : 64 bits perf hist counter MIB file
--
-- June 2004
--
-- Copyright (c) 2004 by cisco Systems, Inc.
-- All rights reserved.
--
-- *****************************************************************
--
HC-PerfHist-TC-MIB DEFINITIONS ::= BEGIN
IMPORTS
MODULE-IDENTITY,
Counter64,
Unsigned32,
Integer32,
mib-2 FROM SNMPv2-SMI
TEXTUAL-CONVENTION FROM SNMPv2-TC;
hcPerfHistTCMIB MODULE-IDENTITY
LAST-UPDATED "200402030000Z" -- February 3, 2004
ORGANIZATION "ADSLMIB Working Group"
CONTACT-INFO "WG-email: adslmib@ietf.org
Info: https://www1.ietf.org/mailman/listinfo/adslmib
Chair: Mike Sneed
Sand Channel Systems
Postal: P.O. Box 37324
Raleigh NC 27627-7324
USA
Email: sneedmike@hotmail.com
Phone: +1 206 600 7022
Co-editor: Bob Ray
PESA Switching Systems, Inc.
Postal: 330-A Wynn Drive
Huntsville, AL 35805
USA
Email: rray@pesa.com
Phone: +1 256 726 9200 ext. 142
Co-editor: Rajesh Abbi
Alcatel USA
Postal: 2301 Sugar Bush Road
Raleigh, NC 27612-3339
USA
Email: Rajesh.Abbi@alcatel.com
Phone: +1 919 850 6194
"
DESCRIPTION
"This MIB Module provides Textual Conventions to be
used by systems supporting 15 minute based performance
history counts that require high-capacity counts.
Copyright (C) The Internet Society (2004). This version
of this MIB module is part of RFC 3705: see the RFC
itself for full legal notices."
REVISION "200402030000Z" -- February 3, 2004
DESCRIPTION "Initial version, published as RFC 3705."
::= { mib-2 107 }
HCPerfValidIntervals ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"The number of near end intervals for which data was
collected. The value of an object with an
HCPerfValidIntervals syntax will be 96 unless the
measurement was (re-)started within the last 1440 minutes,
in which case the value will be the number of complete 15
minute intervals for which the agent has at least some data.
In certain cases (e.g., in the case where the agent is a
proxy) it is possible that some intervals are unavailable.
In this case, this interval is the maximum interval number
for which data is available."
SYNTAX Integer32 (0..96)
HCPerfInvalidIntervals ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"The number of near end intervals for which no data is
available. The value of an object with an
HCPerfInvalidIntervals syntax will typically be zero except
in cases where the data for some intervals are not available
(e.g., in proxy situations)."
SYNTAX Integer32 (0..96)
HCPerfTimeElapsed ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"The number of seconds that have elapsed since the beginning
of the current measurement period. If, for some reason,
such as an adjustment in the system's time-of-day clock or
the addition of a leap second, the duration of the current
interval exceeds the maximum value, the agent will return
the maximum value.
For 15 minute intervals, the range is limited to (0..899).
For 24 hour intervals, the range is limited to (0..86399)."
SYNTAX Integer32 (0..86399)
HCPerfIntervalThreshold ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"This convention defines a range of values that may be set
in a fault threshold alarm control. As the number of
seconds in a 15-minute interval numbers at most 900,
objects of this type may have a range of 0...900, where the
value of 0 disables the alarm."
SYNTAX Unsigned32 (0..900)
HCPerfCurrentCount ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"A gauge associated with a performance measurement in a
current 15 minute measurement interval. The value of an
object with an HCPerfCurrentCount syntax starts from zero
and is increased when associated events occur, until the
end of the 15 minute interval. At that time the value of
the gauge is stored in the first 15 minute history
interval, and the gauge is restarted at zero. In the case
where the agent has no valid data available for the
current interval, the corresponding object instance is not
available and upon a retrieval request a corresponding
error message shall be returned to indicate that this
instance does not exist.
This count represents a non-negative integer, which
may increase or decrease, but shall never exceed 2^64-1
(18446744073709551615 decimal), nor fall below 0. The
value of an object with HCPerfCurrentCount syntax
assumes its maximum value whenever the underlying count
exceeds 2^64-1. If the underlying count subsequently
decreases below 2^64-1 (due, e.g., to a retroactive
adjustment as a result of entering or exiting unavailable
time), then the object's value also decreases.
Note that this TC is not strictly supported in SMIv2,
because the 'always increasing' and 'counter wrap'
semantics associated with the Counter64 base type are not
preserved. It is possible that management applications
which rely solely upon the (Counter64) ASN.1 tag to
determine object semantics will mistakenly operate upon
objects of this type as they would for Counter64 objects.
This textual convention represents a limited and short-
term solution, and may be deprecated as a long term
solution is defined and deployed to replace it."
SYNTAX Counter64
HCPerfIntervalCount ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"A gauge associated with a performance measurement in
a previous 15 minute measurement interval. In the case
where the agent has no valid data available for a
particular interval, the corresponding object instance is
not available and upon a retrieval request a corresponding
error message shall be returned to indicate that this
instance does not exist.
Let X be an object with HCPerfIntervalCount syntax.
Let Y be an object with HCPerfCurrentCount syntax.
Let Z be an object with HCPerfTotalCount syntax.
Then, in a system supporting a history of n intervals with
X(1) and X(n) the most and least recent intervals
respectively, the following applies at the end of a 15
minute interval:
- discard the value of X(n)
- the value of X(i) becomes that of X(i-1)
for n >= i > 1
- the value of X(1) becomes that of Y.
- the value of Z, if supported, is adjusted.
This count represents a non-negative integer, which
may increase or decrease, but shall never exceed 2^64-1
(18446744073709551615 decimal), nor fall below 0. The
value of an object with HCPerfIntervalCount syntax
assumes its maximum value whenever the underlying count
exceeds 2^64-1. If the underlying count subsequently
decreases below 2^64-1 (due, e.g., to a retroactive
adjustment as a result of entering or exiting unavailable
time), then the value of the object also decreases.
Note that this TC is not strictly supported in SMIv2,
because the 'always increasing' and 'counter wrap'
semantics associated with the Counter64 base type are not
preserved. It is possible that management applications
which rely solely upon the (Counter64) ASN.1 tag to
determine object semantics will mistakenly operate upon
objects of this type as they would for Counter64 objects.
This textual convention represents a limited and short-
term solution, and may be deprecated as a long term
solution is defined and deployed to replace it."
SYNTAX Counter64
HCPerfTotalCount ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"A gauge representing the aggregate of previous valid 15
minute measurement intervals. Intervals for which no
valid data was available are not counted.
This count represents a non-negative integer, which
may increase or decrease, but shall never exceed 2^64-1
(18446744073709551615 decimal), nor fall below 0. The
value of an object with HCPerfTotalCount syntax
assumes its maximum value whenever the underlying count
exceeds 2^64-1. If the underlying count subsequently
decreases below 2^64-1 (due, e.g., to a retroactive
adjustment as a result of entering or exiting unavailable
time), then the object's value also decreases.
Note that this TC is not strictly supported in SMIv2,
because the 'always increasing' and 'counter wrap'
semantics associated with the Counter64 base type are not
preserved. It is possible that management applications
which rely solely upon the (Counter64) ASN.1 tag to
determine object semantics will mistakenly operate upon
objects of this type as they would for Counter64 objects.
This textual convention represents a limited and short-
term solution, and may be deprecated as a long term
solution is defined and deployed to replace it."
SYNTAX Counter64
END

3149
priv/mibs/HC-RMON-MIB Normal file
View file

File diff suppressed because it is too large Load diff

118
priv/mibs/HCNUM-TC Normal file
View file

@ -0,0 +1,118 @@
HCNUM-TC DEFINITIONS ::= BEGIN
IMPORTS
MODULE-IDENTITY, mib-2, Counter64
FROM SNMPv2-SMI
TEXTUAL-CONVENTION
FROM SNMPv2-TC;
hcnumTC MODULE-IDENTITY
LAST-UPDATED "200006080000Z"
ORGANIZATION "IETF OPS Area"
CONTACT-INFO
" E-mail: mibs@ops.ietf.org
Subscribe: majordomo@psg.com
with msg body: subscribe mibs
Andy Bierman
Cisco Systems Inc.
170 West Tasman Drive
San Jose, CA 95134 USA
+1 408-527-3711
abierman@cisco.com
Keith McCloghrie
Cisco Systems Inc.
170 West Tasman Drive
San Jose, CA 95134 USA
+1 408-526-5260
kzm@cisco.com
Randy Presuhn
BMC Software, Inc.
Office 1-3141
2141 North First Street
San Jose, California 95131 USA
+1 408 546-1006
rpresuhn@bmc.com"
DESCRIPTION
"A MIB module containing textual conventions
for high capacity data types. This module
addresses an immediate need for data types not directly
supported in the SMIv2. This short-term solution
is meant to be deprecated as a long-term solution
is deployed."
REVISION "200006080000Z"
DESCRIPTION
"Initial Version of the High Capacity Numbers
MIB module, published as RFC 2856."
::= { mib-2 78 }
CounterBasedGauge64 ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"The CounterBasedGauge64 type represents a non-negative
integer, which may increase or decrease, but shall never
exceed a maximum value, nor fall below a minimum value. The
maximum value can not be greater than 2^64-1
(18446744073709551615 decimal), and the minimum value can
not be smaller than 0. The value of a CounterBasedGauge64
has its maximum value whenever the information being modeled
is greater than or equal to its maximum value, and has its
minimum value whenever the information being modeled is
smaller than or equal to its minimum value. If the
information being modeled subsequently decreases below
(increases above) the maximum (minimum) value, the
CounterBasedGauge64 also decreases (increases).
Note that this TC is not strictly supported in SMIv2,
because the 'always increasing' and 'counter wrap' semantics
associated with the Counter64 base type are not preserved.
It is possible that management applications which rely
solely upon the (Counter64) ASN.1 tag to determine object
semantics will mistakenly operate upon objects of this type
as they would for Counter64 objects.
This textual convention represents a limited and short-term
solution, and may be deprecated as a long term solution is
defined and deployed to replace it."
SYNTAX Counter64
ZeroBasedCounter64 ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"This TC describes an object which counts events with the
following semantics: objects of this type will be set to
zero(0) on creation and will thereafter count appropriate
events, wrapping back to zero(0) when the value 2^64 is
reached.
Provided that an application discovers the new object within
the minimum time to wrap it can use the initial value as a
delta since it last polled the table of which this object is
part. It is important for a management station to be aware
of this minimum time and the actual time between polls, and
to discard data if the actual time is too long or there is
no defined minimum time.
Typically this TC is used in tables where the INDEX space is
constantly changing and/or the TimeFilter mechanism is in
use.
Note that this textual convention does not retain all the
semantics of the Counter64 base type. Specifically, a
Counter64 has an arbitrary initial value, but objects
defined with this TC are required to start at the value
zero. This behavior is not likely to have any adverse
effects on management applications which are expecting
Counter64 semantics.
This textual convention represents a limited and short-term
solution, and may be deprecated as a long term solution is
defined and deployed to replace it."
SYNTAX Counter64
END

2429
priv/mibs/HDSL2-SHDSL-LINE-MIB Normal file
View file

File diff suppressed because it is too large Load diff

1540
priv/mibs/HOST-RESOURCES-MIB Normal file
View file

File diff suppressed because it is too large Load diff

389
priv/mibs/HOST-RESOURCES-TYPES Normal file
View file

@ -0,0 +1,389 @@
HOST-RESOURCES-TYPES DEFINITIONS ::= BEGIN
IMPORTS
MODULE-IDENTITY, OBJECT-IDENTITY FROM SNMPv2-SMI
hrMIBAdminInfo, hrStorage, hrDevice FROM HOST-RESOURCES-MIB;
hostResourcesTypesModule MODULE-IDENTITY
LAST-UPDATED "200003060000Z" -- 6 March, 2000
ORGANIZATION "IETF Host Resources MIB Working Group"
CONTACT-INFO
"Steve Waldbusser
Postal: Lucent Technologies, Inc.
1213 Innsbruck Dr.
Sunnyvale, CA 94089
USA
Phone: 650-318-1251
Fax: 650-318-1633
Email: waldbusser@ins.com
In addition, the Host Resources MIB mailing list is dedicated
to discussion of this MIB. To join the mailing list, send a
request message to hostmib-request@andrew.cmu.edu. The mailing
list address is hostmib@andrew.cmu.edu."
DESCRIPTION
"This MIB module registers type definitions for
storage types, device types, and file system types.
After the initial revision, this module will be
maintained by IANA."
REVISION "200003060000Z" -- 6 March 2000
DESCRIPTION
"The original version of this module, published as RFC
2790."
::= { hrMIBAdminInfo 4 }
-- Registrations for some storage types, for use with hrStorageType
hrStorageTypes OBJECT IDENTIFIER ::= { hrStorage 1 }
hrStorageOther OBJECT-IDENTITY
STATUS current
DESCRIPTION
"The storage type identifier used when no other defined
type is appropriate."
::= { hrStorageTypes 1 }
hrStorageRam OBJECT-IDENTITY
STATUS current
DESCRIPTION
"The storage type identifier used for RAM."
::= { hrStorageTypes 2 }
hrStorageVirtualMemory OBJECT-IDENTITY
STATUS current
DESCRIPTION
"The storage type identifier used for virtual memory,
temporary storage of swapped or paged memory."
::= { hrStorageTypes 3 }
hrStorageFixedDisk OBJECT-IDENTITY
STATUS current
DESCRIPTION
"The storage type identifier used for non-removable
rigid rotating magnetic storage devices."
::= { hrStorageTypes 4 }
hrStorageRemovableDisk OBJECT-IDENTITY
STATUS current
DESCRIPTION
"The storage type identifier used for removable rigid
rotating magnetic storage devices."
::= { hrStorageTypes 5 }
hrStorageFloppyDisk OBJECT-IDENTITY
STATUS current
DESCRIPTION
"The storage type identifier used for non-rigid rotating
magnetic storage devices."
::= { hrStorageTypes 6 }
hrStorageCompactDisc OBJECT-IDENTITY
STATUS current
DESCRIPTION
"The storage type identifier used for read-only rotating
optical storage devices."
::= { hrStorageTypes 7 }
hrStorageRamDisk OBJECT-IDENTITY
STATUS current
DESCRIPTION
"The storage type identifier used for a file system that
is stored in RAM."
::= { hrStorageTypes 8 }
hrStorageFlashMemory OBJECT-IDENTITY
STATUS current
DESCRIPTION
"The storage type identifier used for flash memory."
::= { hrStorageTypes 9 }
hrStorageNetworkDisk OBJECT-IDENTITY
STATUS current
DESCRIPTION
"The storage type identifier used for a
networked file system."
::= { hrStorageTypes 10 }
-- Registrations for some device types, for use with hrDeviceType
hrDeviceTypes OBJECT IDENTIFIER ::= { hrDevice 1 }
hrDeviceOther OBJECT-IDENTITY
STATUS current
DESCRIPTION
"The device type identifier used when no other defined
type is appropriate."
::= { hrDeviceTypes 1 }
hrDeviceUnknown OBJECT-IDENTITY
STATUS current
DESCRIPTION
"The device type identifier used when the device type is
unknown."
::= { hrDeviceTypes 2 }
hrDeviceProcessor OBJECT-IDENTITY
STATUS current
DESCRIPTION
"The device type identifier used for a CPU."
::= { hrDeviceTypes 3 }
hrDeviceNetwork OBJECT-IDENTITY
STATUS current
DESCRIPTION
"The device type identifier used for a network interface."
::= { hrDeviceTypes 4 }
hrDevicePrinter OBJECT-IDENTITY
STATUS current
DESCRIPTION
"The device type identifier used for a printer."
::= { hrDeviceTypes 5 }
hrDeviceDiskStorage OBJECT-IDENTITY
STATUS current
DESCRIPTION
"The device type identifier used for a disk drive."
::= { hrDeviceTypes 6 }
hrDeviceVideo OBJECT-IDENTITY
STATUS current
DESCRIPTION
"The device type identifier used for a video device."
::= { hrDeviceTypes 10 }
hrDeviceAudio OBJECT-IDENTITY
STATUS current
DESCRIPTION
"The device type identifier used for an audio device."
::= { hrDeviceTypes 11 }
hrDeviceCoprocessor OBJECT-IDENTITY
STATUS current
DESCRIPTION
"The device type identifier used for a co-processor."
::= { hrDeviceTypes 12 }
hrDeviceKeyboard OBJECT-IDENTITY
STATUS current
DESCRIPTION
"The device type identifier used for a keyboard device."
::= { hrDeviceTypes 13 }
hrDeviceModem OBJECT-IDENTITY
STATUS current
DESCRIPTION
"The device type identifier used for a modem."
::= { hrDeviceTypes 14 }
hrDeviceParallelPort OBJECT-IDENTITY
STATUS current
DESCRIPTION
"The device type identifier used for a parallel port."
::= { hrDeviceTypes 15 }
hrDevicePointing OBJECT-IDENTITY
STATUS current
DESCRIPTION
"The device type identifier used for a pointing device
(e.g., a mouse)."
::= { hrDeviceTypes 16 }
hrDeviceSerialPort OBJECT-IDENTITY
STATUS current
DESCRIPTION
"The device type identifier used for a serial port."
::= { hrDeviceTypes 17 }
hrDeviceTape OBJECT-IDENTITY
STATUS current
DESCRIPTION
"The device type identifier used for a tape storage device."
::= { hrDeviceTypes 18 }
hrDeviceClock OBJECT-IDENTITY
STATUS current
DESCRIPTION
"The device type identifier used for a clock device."
::= { hrDeviceTypes 19 }
hrDeviceVolatileMemory OBJECT-IDENTITY
STATUS current
DESCRIPTION
"The device type identifier used for a volatile memory
storage device."
::= { hrDeviceTypes 20 }
hrDeviceNonVolatileMemory OBJECT-IDENTITY
STATUS current
DESCRIPTION
"The device type identifier used for a non-volatile memory
storage device."
::= { hrDeviceTypes 21 }
-- Registrations for some popular File System types,
-- for use with hrFSType.
hrFSTypes OBJECT IDENTIFIER ::= { hrDevice 9 }
hrFSOther OBJECT-IDENTITY
STATUS current
DESCRIPTION
"The file system type identifier used when no other
defined type is appropriate."
::= { hrFSTypes 1 }
hrFSUnknown OBJECT-IDENTITY
STATUS current
DESCRIPTION
"The file system type identifier used when the type of
file system is unknown."
::= { hrFSTypes 2 }
hrFSBerkeleyFFS OBJECT-IDENTITY
STATUS current
DESCRIPTION
"The file system type identifier used for the
Berkeley Fast File System."
::= { hrFSTypes 3 }
hrFSSys5FS OBJECT-IDENTITY
STATUS current
DESCRIPTION
"The file system type identifier used for the
System V File System."
::= { hrFSTypes 4 }
hrFSFat OBJECT-IDENTITY
STATUS current
DESCRIPTION
"The file system type identifier used for
DOS's FAT file system."
::= { hrFSTypes 5 }
hrFSHPFS OBJECT-IDENTITY
STATUS current
DESCRIPTION
"The file system type identifier used for OS/2's
High Performance File System."
::= { hrFSTypes 6 }
hrFSHFS OBJECT-IDENTITY
STATUS current
DESCRIPTION
"The file system type identifier used for the
Macintosh Hierarchical File System."
::= { hrFSTypes 7 }
hrFSMFS OBJECT-IDENTITY
STATUS current
DESCRIPTION
"The file system type identifier used for the
Macintosh File System."
::= { hrFSTypes 8 }
hrFSNTFS OBJECT-IDENTITY
STATUS current
DESCRIPTION
"The file system type identifier used for the
Windows NT File System."
::= { hrFSTypes 9 }
hrFSVNode OBJECT-IDENTITY
STATUS current
DESCRIPTION
"The file system type identifier used for the
VNode File System."
::= { hrFSTypes 10 }
hrFSJournaled OBJECT-IDENTITY
STATUS current
DESCRIPTION
"The file system type identifier used for the
Journaled File System."
::= { hrFSTypes 11 }
hrFSiso9660 OBJECT-IDENTITY
STATUS current
DESCRIPTION
"The file system type identifier used for the
ISO 9660 File System for CD's."
::= { hrFSTypes 12 }
hrFSRockRidge OBJECT-IDENTITY
STATUS current
DESCRIPTION
"The file system type identifier used for the
RockRidge File System for CD's."
::= { hrFSTypes 13 }
hrFSNFS OBJECT-IDENTITY
STATUS current
DESCRIPTION
"The file system type identifier used for the
NFS File System."
::= { hrFSTypes 14 }
hrFSNetware OBJECT-IDENTITY
STATUS current
DESCRIPTION
"The file system type identifier used for the
Netware File System."
::= { hrFSTypes 15 }
hrFSAFS OBJECT-IDENTITY
STATUS current
DESCRIPTION
"The file system type identifier used for the
Andrew File System."
::= { hrFSTypes 16 }
hrFSDFS OBJECT-IDENTITY
STATUS current
DESCRIPTION
"The file system type identifier used for the
OSF DCE Distributed File System."
::= { hrFSTypes 17 }
hrFSAppleshare OBJECT-IDENTITY
STATUS current
DESCRIPTION
"The file system type identifier used for the
AppleShare File System."
::= { hrFSTypes 18 }
hrFSRFS OBJECT-IDENTITY
STATUS current
DESCRIPTION
"The file system type identifier used for the
RFS File System."
::= { hrFSTypes 19 }
hrFSDGCFS OBJECT-IDENTITY
STATUS current
DESCRIPTION
"The file system type identifier used for the
Data General DGCFS."
::= { hrFSTypes 20 }
hrFSBFS OBJECT-IDENTITY
STATUS current
DESCRIPTION
"The file system type identifier used for the
SVR4 Boot File System."
::= { hrFSTypes 21 }
hrFSFAT32 OBJECT-IDENTITY
STATUS current
DESCRIPTION
"The file system type identifier used for the
Windows FAT32 File System."
::= { hrFSTypes 22 }
hrFSLinuxExt2 OBJECT-IDENTITY
STATUS current
DESCRIPTION
"The file system type identifier used for the
Linux EXT2 File System."
::= { hrFSTypes 23 }
END

175
priv/mibs/IANA-ADDRESS-FAMILY-NUMBERS-MIB Normal file
View file

@ -0,0 +1,175 @@
IANA-ADDRESS-FAMILY-NUMBERS-MIB DEFINITIONS ::= BEGIN
IMPORTS
MODULE-IDENTITY,
mib-2 FROM SNMPv2-SMI
TEXTUAL-CONVENTION FROM SNMPv2-TC;
ianaAddressFamilyNumbers MODULE-IDENTITY
LAST-UPDATED "201911040000Z" -- November 4, 2019
ORGANIZATION "IANA"
CONTACT-INFO
"Postal: Internet Assigned Numbers Authority
Internet Corporation for Assigned Names and Numbers
12025 Waterfront Drive, Suite 300
Los Angeles, CA 90094-2536
USA
Tel: +1 310-301-5800
E-Mail: iana&iana.org"
DESCRIPTION
"The MIB module defines the AddressFamilyNumbers
textual convention."
-- revision history
REVISION "201911040000Z" -- November 4, 2019
DESCRIPTION "Assigned value 16397."
REVISION "201409020000Z" -- September 2, 2014
DESCRIPTION "Assigned value 16396."
REVISION "201309250000Z" -- September 25, 2013
DESCRIPTION "Assigned values 16391-16395."
REVISION "201307160000Z" -- July 16, 2013
DESCRIPTION "Fixed labels for 16389-16390."
REVISION "201306260000Z" -- June 26, 2013
DESCRIPTION "Added assignments 26-28."
REVISION "201306180000Z" -- June 18, 2013
DESCRIPTION "Added assignments 16384-16390. Assignment
25 added in 2007 revision."
REVISION "200203140000Z" -- March 14, 2002
DESCRIPTION "AddressFamilyNumbers assignment 22 to
fibreChannelWWPN. AddressFamilyNumbers
assignment 23 to fibreChannelWWNN.
AddressFamilyNumers assignment 24 to gwid."
REVISION "200009080000Z" -- September 8, 2000
DESCRIPTION "AddressFamilyNumbers assignment 19 to xtpOverIpv4.
AddressFamilyNumbers assignment 20 to xtpOverIpv6.
AddressFamilyNumbers assignment 21 to xtpNativeModeXTP."
REVISION "200003010000Z" -- March 1, 2000
DESCRIPTION "AddressFamilyNumbers assignment 17 to distinguishedName.
AddressFamilyNumbers assignment 18 to asNumber."
REVISION "200002040000Z" -- February 4, 2000
DESCRIPTION "AddressFamilyNumbers assignment 16 to dns."
REVISION "9908260000Z" -- August 26, 1999
DESCRIPTION "Initial version, published as RFC 2677."
::= { mib-2 72 }
AddressFamilyNumbers ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"The definition of this textual convention with the
addition of newly assigned values is published
periodically by the IANA, in either the Assigned
Numbers RFC, or some derivative of it specific to
Internet Network Management number assignments.
(The latest arrangements can be obtained by
contacting the IANA.)
The enumerations are described as:
other(0), -- none of the following
ipV4(1), -- IP Version 4
ipV6(2), -- IP Version 6
nsap(3), -- NSAP
hdlc(4), -- (8-bit multidrop)
bbn1822(5),
all802(6), -- (includes all 802 media
-- plus Ethernet 'canonical format')
e163(7),
e164(8), -- (SMDS, Frame Relay, ATM)
f69(9), -- (Telex)
x121(10), -- (X.25, Frame Relay)
ipx(11), -- IPX (Internet Protocol Exchange)
appleTalk(12), -- Apple Talk
decnetIV(13), -- DEC Net Phase IV
banyanVines(14), -- Banyan Vines
e164withNsap(15),
-- (E.164 with NSAP format subaddress)
dns(16), -- (Domain Name System)
distinguishedName(17), -- (Distinguished Name, per X.500)
asNumber(18), -- (16-bit quantity, per the AS number space)
xtpOverIpv4(19), -- XTP over IP version 4
xtpOverIpv6(20), -- XTP over IP version 6
xtpNativeModeXTP(21), -- XTP native mode XTP
fibreChannelWWPN(22), -- Fibre Channel World-Wide Port Name
fibreChannelWWNN(23), -- Fibre Channel World-Wide Node Name
gwid(24), -- Gateway Identifier
afi(25), -- AFI for L2VPN information
mplsTpSectionEndpointIdentifier(26), -- MPLS-TP Section Endpoint Identifier
mplsTpLspEndpointIdentifier(27), -- MPLS-TP LSP Endpoint Identifier
mplsTpPseudowireEndpointIdentifier(28), -- MPLS-TP Pseudowire Endpoint Identifier
eigrpCommonServiceFamily(16384), -- EIGRP Common Service Family
eigrpIpv4ServiceFamily(16385), -- EIGRP IPv4 Service Family
eigrpIpv6ServiceFamily(16386), -- EIGRP IPv6 Service Family
lispCanonicalAddressFormat(16387), -- LISP Canonical Address Format (LCAF)
bgpLs(16388), -- BGP-LS
fortyeightBitMacBitMac(16389), -- 48-bit MAC
sixtyfourBitMac(16390), -- 64-bit MAC
oui(16391), -- OUI
mac24(16392), -- MAC/24
mac40(16393), -- MAC/40
ipv664(16394), -- IPv6/64
rBridgePortID(16395), -- RBridge Port ID
trillNickname(16396), -- TRILL Nickname
universallyUniqueIdentifier(16397), -- Universally Unique Identifier (UUID)
reserved(65535)
Requests for new values should be made to IANA via
email (iana&iana.org)."
SYNTAX INTEGER {
other(0),
ipV4(1),
ipV6(2),
nsap(3),
hdlc(4),
bbn1822(5),
all802(6),
e163(7),
e164(8),
f69(9),
x121(10),
ipx(11),
appleTalk(12),
decnetIV(13),
banyanVines(14),
e164withNsap(15),
dns(16),
distinguishedName(17), -- (Distinguished Name, per X.500)
asNumber(18), -- (16-bit quantity, per the AS number space)
xtpOverIpv4(19),
xtpOverIpv6(20),
xtpNativeModeXTP(21),
fibreChannelWWPN(22),
fibreChannelWWNN(23),
gwid(24),
afi(25),
mplsTpSectionEndpointIdentifier(26),
mplsTpLspEndpointIdentifier(27),
mplsTpPseudowireEndpointIdentifier(28),
eigrpCommonServiceFamily(16384),
eigrpIpv4ServiceFamily(16385),
eigrpIpv6ServiceFamily(16386),
lispCanonicalAddressFormat(16387),
bgpLs(16388),
fortyeightBitMac(16389),
sixtyfourBitMac(16390),
oui(16391),
mac24(16392),
mac40(16393),
ipv664(16394),
rBridgePortID(16395),
trillNickname(16396),
universallyUniqueIdentifier(16397),
reserved(65535)
}
END

345
priv/mibs/IANA-CHARSET-MIB Normal file
View file

@ -0,0 +1,345 @@
IANA-CHARSET-MIB DEFINITIONS ::= BEGIN
-- http://www.iana.org/assignments/ianacharset-mib
IMPORTS
MODULE-IDENTITY,
mib-2
FROM SNMPv2-SMI -- [RFC2578]
TEXTUAL-CONVENTION
FROM SNMPv2-TC; -- [RFC2579]
ianaCharsetMIB MODULE-IDENTITY
LAST-UPDATED "200705140000Z"
ORGANIZATION "IANA"
CONTACT-INFO " Internet Assigned Numbers Authority
Postal: ICANN
4676 Admiralty Way, Suite 330
Marina del Rey, CA 90292
Tel: +1 310 823 9358
E-Mail: iana&iana.org"
DESCRIPTION "This MIB module defines the IANACharset
TEXTUAL-CONVENTION. The IANACharset TC is used to
specify the encoding of string objects defined in
a MIB.
Each version of this MIB will be released based on
the IANA Charset Registry file (see RFC 2978) at
http://www.iana.org/assignments/character-sets.
Note: The IANACharset TC, originally defined in
RFC 1759, was inaccurately named CodedCharSet.
Note: Best practice is to define new MIB string
objects with invariant UTF-8 (RFC 3629) syntax
using the SnmpAdminString TC (defined in RFC 3411)
in accordance with IETF Policy on Character Sets and
Languages (RFC 2277).
Copyright (C) The Internet Society (2004). The
initial version of this MIB module was published
in RFC 3808; for full legal notices see the RFC
itself. Supplementary information may be
available on
http://www.ietf.org/copyrights/ianamib.html."
-- revision history
REVISION "200705140000Z"
DESCRIPTION "Registration of new charset 2107."
REVISION "200612070000Z"
DESCRIPTION "Registration of new charsets numbered 118, 119,
and 2106."
REVISION "200406080000Z"
DESCRIPTION "Original version transferred from Printer MIB,
generated from the IANA maintained assignments
http://www.iana.org/assignments/character-sets."
::= { mib-2 106 }
IANACharset ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"Specifies an IANA registered 'charset' - coded character set
(CCS) plus optional character encoding scheme (CES) - terms
defined in 'IANA Charset Registration Procedures' (RFC 2978).
Objects of this syntax are used to specify the encoding for
string objects defined in one or more MIBs. For example, the
prtLocalizationCharacterSet, prtInterpreterDefaultCharSetIn, and
prtInterpreterDefaultCharSetOut objects defined in Printer MIB.
The current list of 'charset' names and enumerated values
is contained in the IANA Character Set Registry at:
http://www.iana.org/assignments/character-sets
Enum names are derived from the IANA Charset Registry 'Alias'
fields that begin with 'cs' (for character set).
Enum values are derived from the parallel 'MIBenum' fields."
SYNTAX INTEGER {
other(1), -- used if the designated
-- character set is not currently
-- registered by IANA
unknown(2), -- used as a default value
csASCII(3),
csISOLatin1(4),
csISOLatin2(5),
csISOLatin3(6),
csISOLatin4(7),
csISOLatinCyrillic(8),
csISOLatinArabic(9),
csISOLatinGreek(10),
csISOLatinHebrew(11),
csISOLatin5(12),
csISOLatin6(13),
csISOTextComm(14),
csHalfWidthKatakana(15),
csJISEncoding(16),
csShiftJIS(17),
csEUCPkdFmtJapanese(18),
csEUCFixWidJapanese(19),
csISO4UnitedKingdom(20),
csISO11SwedishForNames(21),
csISO15Italian(22),
csISO17Spanish(23),
csISO21German(24),
csISO60DanishNorwegian(25),
csISO69French(26),
csISO10646UTF1(27),
csISO646basic1983(28),
csINVARIANT(29),
csISO2IntlRefVersion(30),
csNATSSEFI(31),
csNATSSEFIADD(32),
csNATSDANO(33),
csNATSDANOADD(34),
csISO10Swedish(35),
csKSC56011987(36),
csISO2022KR(37),
csEUCKR(38),
csISO2022JP(39),
csISO2022JP2(40),
csISO13JISC6220jp(41),
csISO14JISC6220ro(42),
csISO16Portuguese(43),
csISO18Greek7Old(44),
csISO19LatinGreek(45),
csISO25French(46),
csISO27LatinGreek1(47),
csISO5427Cyrillic(48),
csISO42JISC62261978(49),
csISO47BSViewdata(50),
csISO49INIS(51),
csISO50INIS8(52),
csISO51INISCyrillic(53),
csISO54271981(54),
csISO5428Greek(55),
csISO57GB1988(56),
csISO58GB231280(57),
csISO61Norwegian2(58),
csISO70VideotexSupp1(59),
csISO84Portuguese2(60),
csISO85Spanish2(61),
csISO86Hungarian(62),
csISO87JISX0208(63),
csISO88Greek7(64),
csISO89ASMO449(65),
csISO90(66),
csISO91JISC62291984a(67),
csISO92JISC62991984b(68),
csISO93JIS62291984badd(69),
csISO94JIS62291984hand(70),
csISO95JIS62291984handadd(71),
csISO96JISC62291984kana(72),
csISO2033(73),
csISO99NAPLPS(74),
csISO102T617bit(75),
csISO103T618bit(76),
csISO111ECMACyrillic(77),
csa71(78),
csa72(79),
csISO123CSAZ24341985gr(80),
csISO88596E(81),
csISO88596I(82),
csISO128T101G2(83),
csISO88598E(84),
csISO88598I(85),
csISO139CSN369103(86),
csISO141JUSIB1002(87),
csISO143IECP271(88),
csISO146Serbian(89),
csISO147Macedonian(90),
csISO150(91),
csISO151Cuba(92),
csISO6937Add(93),
csISO153GOST1976874(94),
csISO8859Supp(95),
csISO10367Box(96),
csISO158Lap(97),
csISO159JISX02121990(98),
csISO646Danish(99),
csUSDK(100),
csDKUS(101),
csKSC5636(102),
csUnicode11UTF7(103),
csISO2022CN(104),
csISO2022CNEXT(105),
csUTF8(106),
csISO885913(109),
csISO885914(110),
csISO885915(111),
csISO885916(112),
csGBK(113),
csGB18030(114),
csOSDEBCDICDF0415(115),
csOSDEBCDICDF03IRV(116),
csOSDEBCDICDF041(117),
csISO115481(118),
csKZ1048(119),
csUnicode(1000),
csUCS4(1001),
csUnicodeASCII(1002),
csUnicodeLatin1(1003),
csUnicodeIBM1261(1005),
csUnicodeIBM1268(1006),
csUnicodeIBM1276(1007),
csUnicodeIBM1264(1008),
csUnicodeIBM1265(1009),
csUnicode11(1010),
csSCSU(1011),
csUTF7(1012),
csUTF16BE(1013),
csUTF16LE(1014),
csUTF16(1015),
csCESU8(1016),
csUTF32(1017),
csUTF32BE(1018),
csUTF32LE(1019),
csBOCU1(1020),
csWindows30Latin1(2000),
csWindows31Latin1(2001),
csWindows31Latin2(2002),
csWindows31Latin5(2003),
csHPRoman8(2004),
csAdobeStandardEncoding(2005),
csVenturaUS(2006),
csVenturaInternational(2007),
csDECMCS(2008),
csPC850Multilingual(2009),
csPCp852(2010),
csPC8CodePage437(2011),
csPC8DanishNorwegian(2012),
csPC862LatinHebrew(2013),
csPC8Turkish(2014),
csIBMSymbols(2015),
csIBMThai(2016),
csHPLegal(2017),
csHPPiFont(2018),
csHPMath8(2019),
csHPPSMath(2020),
csHPDesktop(2021),
csVenturaMath(2022),
csMicrosoftPublishing(2023),
csWindows31J(2024),
csGB2312(2025),
csBig5(2026),
csMacintosh(2027),
csIBM037(2028),
csIBM038(2029),
csIBM273(2030),
csIBM274(2031),
csIBM275(2032),
csIBM277(2033),
csIBM278(2034),
csIBM280(2035),
csIBM281(2036),
csIBM284(2037),
csIBM285(2038),
csIBM290(2039),
csIBM297(2040),
csIBM420(2041),
csIBM423(2042),
csIBM424(2043),
csIBM500(2044),
csIBM851(2045),
csIBM855(2046),
csIBM857(2047),
csIBM860(2048),
csIBM861(2049),
csIBM863(2050),
csIBM864(2051),
csIBM865(2052),
csIBM868(2053),
csIBM869(2054),
csIBM870(2055),
csIBM871(2056),
csIBM880(2057),
csIBM891(2058),
csIBM903(2059),
csIBBM904(2060),
csIBM905(2061),
csIBM918(2062),
csIBM1026(2063),
csIBMEBCDICATDE(2064),
csEBCDICATDEA(2065),
csEBCDICCAFR(2066),
csEBCDICDKNO(2067),
csEBCDICDKNOA(2068),
csEBCDICFISE(2069),
csEBCDICFISEA(2070),
csEBCDICFR(2071),
csEBCDICIT(2072),
csEBCDICPT(2073),
csEBCDICES(2074),
csEBCDICESA(2075),
csEBCDICESS(2076),
csEBCDICUK(2077),
csEBCDICUS(2078),
csUnknown8BiT(2079),
csMnemonic(2080),
csMnem(2081),
csVISCII(2082),
csVIQR(2083),
csKOI8R(2084),
csHZGB2312(2085),
csIBM866(2086),
csPC775Baltic(2087),
csKOI8U(2088),
csIBM00858(2089),
csIBM00924(2090),
csIBM01140(2091),
csIBM01141(2092),
csIBM01142(2093),
csIBM01143(2094),
csIBM01144(2095),
csIBM01145(2096),
csIBM01146(2097),
csIBM01147(2098),
csIBM01148(2099),
csIBM01149(2100),
csBig5HKSCS(2101),
csIBM1047(2102),
csPTCP154(2103),
csAmiga1251(2104),
csKOI7switched(2105),
csBRF(2106),
csTSCII(2107),
cswindows1250(2250),
cswindows1251(2251),
cswindows1252(2252),
cswindows1253(2253),
cswindows1254(2254),
cswindows1255(2255),
cswindows1256(2256),
cswindows1257(2257),
cswindows1258(2258),
csTIS620(2259),
reserved(3000)
}
END

160
priv/mibs/IANA-ENTITY-MIB Normal file
View file

@ -0,0 +1,160 @@
IANA-ENTITY-MIB DEFINITIONS ::= BEGIN
IMPORTS
MODULE-IDENTITY, mib-2
FROM SNMPv2-SMI -- RFC 2578
TEXTUAL-CONVENTION
FROM SNMPv2-TC -- RFC 2579
;
ianaEntityMIB MODULE-IDENTITY
LAST-UPDATED "201507160000Z" -- July 16, 2015
ORGANIZATION "IANA"
CONTACT-INFO
"Internet Assigned Numbers Authority
Postal: ICANN
12025 Waterfront Drive, Suite 300
Los Angeles, CA 90094-2536
Phone: +1-310-301-5800
EMail: iana&iana.org"
DESCRIPTION
"This MIB module defines a TEXTUAL-CONVENTION that provides
an indication of the general hardware type of a particular
physical entity.
Copyright (c) 2013 IETF Trust and the persons identified as
authors of the code. All rights reserved.
Redistribution and use in source and binary forms, with or
without modification, is permitted pursuant to, and subject
to the license terms contained in, the Simplified BSD
License set forth in Section 4.c of the IETF Trust's Legal
Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info).
The initial version of this MIB module was published in
RFC 6933; for full legal notices see the RFC itself."
REVISION "201507160000Z" -- July 16, 2015
DESCRIPTION "Removed space between 'battery' and '(14)'."
REVISION "201507160000Z" -- July 16, 2015
DESCRIPTION "Added storageDrive(15)."
REVISION "201304050000Z" -- April 5, 2013
DESCRIPTION "Initial version of this MIB as published in
RFC 6933."
::= { mib-2 216 }
-- Textual Conventions
IANAPhysicalClass ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"An enumerated value that provides an indication of the
general hardware type of a particular physical entity.
There are no restrictions as to the number of
entPhysicalEntries of each entPhysicalClass, which must
be instantiated by an agent.
The enumeration 'other' is applicable if the physical
entity class is known but does not match any of the
supported values.
The enumeration 'unknown' is applicable if the physical
entity class is unknown to the agent.
The enumeration 'chassis' is applicable if the physical
entity class is an overall container for networking
equipment. Any class of physical entity, except a stack,
may be contained within a chassis; a chassis may only
be contained within a stack.
The enumeration 'backplane' is applicable if the physical
entity class is some sort of device for aggregating and
forwarding networking traffic, such as a shared
backplane in a modular ethernet switch. Note that an
agent may model a backplane as a single physical entity,
which is actually implemented as multiple discrete
physical components (within a chassis or stack).
The enumeration 'container' is applicable if the
physical entity class is capable of containing one or
more removable physical entities, possibly of different
types. For example, each (empty or full) slot in a
chassis will be modeled as a container. Note that all
removable physical entities should be modeled within
a container entity, such as field-replaceable modules,
fans, or power supplies. Note that all known containers
should be modeled by the agent, including empty
containers.
The enumeration 'powerSupply' is applicable if the
physical entity class is a power-supplying component.
The enumeration 'fan' is applicable if the physical
entity class is a fan or other heat-reduction component.
The enumeration 'sensor' is applicable if the physical
entity class is some sort of sensor, such as a
temperature sensor within a router chassis.
The enumeration 'module' is applicable if the physical
entity class is some sort of self-contained sub-system.
If the enumeration 'module' is removable, then it should
be modeled within a container entity; otherwise, it
should be modeled directly within another physical
entity (e.g., a chassis or another module).
The enumeration 'port' is applicable if the physical
entity class is some sort of networking port, capable
of receiving and/or transmitting networking traffic.
The enumeration 'stack' is applicable if the physical
entity class is some sort of super-container (possibly
virtual) intended to group together multiple chassis
entities. A stack may be realized by a 'virtual' cable,
a real interconnect cable attached to multiple chassis,
or multiple interconnect cables. A stack should not be
modeled within any other physical entities, but a stack
may be contained within another stack. Only chassis
entities should be contained within a stack.
The enumeration 'cpu' is applicable if the physical
entity class is some sort of central processing unit.
The enumeration 'energyObject' is applicable if the
physical entity is some sort of energy object, i.e.,
a piece of equipment that is part of or attached to
a communications network that is monitored, controlled,
or aids in the management of another device for Energy
Management.
The enumeration 'battery' is applicable if the physical
entity class is some sort of battery.
The enumeration 'storageDrive' is applicable if the
physical entity class is some sort of entity with data
storage capability as main functionality, e.g. disk drive
(HDD), solid state device (SSD), hybrid (SSHD), object
storage (OSD) or other."
SYNTAX INTEGER {
other(1),
unknown(2),
chassis(3),
backplane(4),
container(5), -- e.g., chassis slot or daughter-card holder
powerSupply(6),
fan(7),
sensor(8),
module(9), -- e.g., plug-in card or daughter-card
port(10),
stack(11), -- e.g., stack of multiple chassis entities
cpu(12),
energyObject(13),
battery(14),
storageDrive(15)
}
END

330
priv/mibs/IANA-GMPLS-TC-MIB Normal file
View file

@ -0,0 +1,330 @@
-- extracted from rfc4802.txt
-- at Thu Mar 1 06:08:22 2007
IANA-GMPLS-TC-MIB DEFINITIONS ::= BEGIN
IMPORTS
MODULE-IDENTITY, mib-2 FROM SNMPv2-SMI -- RFC 2578
TEXTUAL-CONVENTION FROM SNMPv2-TC; -- RFC 2579
ianaGmpls MODULE-IDENTITY
LAST-UPDATED
"200702270000Z" -- 27 February 2007 00:00:00 GMT
ORGANIZATION
"IANA"
CONTACT-INFO
"Internet Assigned Numbers Authority
Postal: 4676 Admiralty Way, Suite 330
Marina del Rey, CA 90292
Tel: +1 310 823 9358
E-Mail: iana@iana.org"
DESCRIPTION
"Copyright (C) The IETF Trust (2007). The initial version
of this MIB module was published in RFC 4802. For full legal
notices see the RFC itself. Supplementary information
may be available on:
http://www.ietf.org/copyrights/ianamib.html"
REVISION
"200702270000Z" -- 27 February 2007 00:00:00 GMT
DESCRIPTION
"Initial version issued as part of RFC 4802."
::= { mib-2 152 }
IANAGmplsLSPEncodingTypeTC ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"This type is used to represent and control
the LSP encoding type of an LSP signaled by a GMPLS
signaling protocol.
This textual convention is strongly tied to the LSP
Encoding Types sub-registry of the GMPLS Signaling
Parameters registry managed by IANA. Values should be
assigned by IANA in step with the LSP Encoding Types
sub-registry and using the same registry management rules.
However, the actual values used in this textual convention
are solely within the purview of IANA and do not
necessarily match the values in the LSP Encoding Types
sub-registry.
The definition of this textual convention with the
addition of newly assigned values is published
periodically by the IANA, in either the Assigned
Numbers RFC, or some derivative of it specific to
Internet Network Management number assignments. (The
latest arrangements can be obtained by contacting the
IANA.)
Requests for new values should be made to IANA via
email (iana@iana.org)."
REFERENCE
"1. Generalized Multi-Protocol Label Switching (GMPLS)
Signaling Functional Description, RFC 3471, section
3.1.1.
2. Generalized MPLS Signalling Extensions for G.709 Optical
Transport Networks Control, RFC 4328, section 3.1.1."
SYNTAX INTEGER {
tunnelLspNotGmpls(0), -- GMPLS is not in use
tunnelLspPacket(1), -- Packet
tunnelLspEthernet(2), -- Ethernet
tunnelLspAnsiEtsiPdh(3), -- PDH
-- the value 4 is deprecated
tunnelLspSdhSonet(5), -- SDH or SONET
-- the value 6 is deprecated
tunnelLspDigitalWrapper(7), -- Digital Wrapper
tunnelLspLambda(8), -- Lambda
tunnelLspFiber(9), -- Fiber
-- the value 10 is deprecated
tunnelLspFiberChannel(11), -- Fiber Channel
tunnelDigitalPath(12), -- Digital Path
tunnelOpticalChannel(13) -- Optical Channel
}
IANAGmplsSwitchingTypeTC ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"This type is used to represent and
control the LSP switching type of an LSP signaled by a
GMPLS signaling protocol.
This textual convention is strongly tied to the Switching
Types sub-registry of the GMPLS Signaling Parameters
registry managed by IANA. Values should be assigned by
IANA in step with the Switching Types sub-registry and
using the same registry management rules. However, the
actual values used in this textual convention are solely
within the purview of IANA and do not necessarily match
the values in the Switching Types sub-registry.
The definition of this textual convention with the
addition of newly assigned values is published
periodically by the IANA, in either the Assigned
Numbers RFC, or some derivative of it specific to
Internet Network Management number assignments. (The
latest arrangements can be obtained by contacting the
IANA.)
Requests for new values should be made to IANA via
email (iana@iana.org)."
REFERENCE
"1. Routing Extensions in Support of Generalized
Multi-Protocol Label Switching, RFC 4202, section 2.4.
2. Generalized Multi-Protocol Label Switching (GMPLS)
Signaling Functional Description, RFC 3471, section
3.1.1."
SYNTAX INTEGER {
unknown(0), -- none of the following, or not known
psc1(1), -- Packet-Switch-Capable 1
psc2(2), -- Packet-Switch-Capable 2
psc3(3), -- Packet-Switch-Capable 3
psc4(4), -- Packet-Switch-Capable 4
l2sc(51), -- Layer-2-Switch-Capable
tdm(100), -- Time-Division-Multiplex
lsc(150), -- Lambda-Switch-Capable
fsc(200) -- Fiber-Switch-Capable
}
IANAGmplsGeneralizedPidTC ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"This data type is used to represent and control the LSP
Generalized Protocol Identifier (G-PID) of an LSP
signaled by a GMPLS signaling protocol.
This textual convention is strongly tied to the Generalized
PIDs (G-PID) sub-registry of the GMPLS Signaling Parameters
registry managed by IANA. Values should be assigned by
IANA in step with the Generalized PIDs (G-PID) sub-registry
and using the same registry management rules. However, the
actual values used in this textual convention are solely
within the purview of IANA and do not necessarily match the
values in the Generalized PIDs (G-PID) sub-registry.
The definition of this textual convention with the
addition of newly assigned values is published
periodically by the IANA, in either the Assigned
Numbers RFC, or some derivative of it specific to
Internet Network Management number assignments. (The
latest arrangements can be obtained by contacting the
IANA.)
Requests for new values should be made to IANA via
email (iana@iana.org)."
REFERENCE
"1. Generalized Multi-Protocol Label Switching (GMPLS)
Signaling Functional Description, RFC 3471, section
3.1.1.
2. Generalized MPLS Signalling Extensions for G.709 Optical
Transport Networks Control, RFC 4328, section 3.1.3."
SYNTAX INTEGER {
unknown(0), -- unknown or none of the following
-- the values 1, 2, 3 and 4 are reserved in RFC 3471
asynchE4(5),
asynchDS3T3(6),
asynchE3(7),
bitsynchE3(8),
bytesynchE3(9),
asynchDS2T2(10),
bitsynchDS2T2(11),
reservedByRFC3471first(12),
asynchE1(13),
bytesynchE1(14),
bytesynch31ByDS0(15),
asynchDS1T1(16),
bitsynchDS1T1(17),
bytesynchDS1T1(18),
vc1vc12(19),
reservedByRFC3471second(20),
reservedByRFC3471third(21),
ds1SFAsynch(22),
ds1ESFAsynch(23),
ds3M23Asynch(24),
ds3CBitParityAsynch(25),
vtLovc(26),
stsSpeHovc(27),
posNoScramble16BitCrc(28),
posNoScramble32BitCrc(29),
posScramble16BitCrc(30),
posScramble32BitCrc(31),
atm(32),
ethernet(33),
sdhSonet(34),
digitalwrapper(36),
lambda(37),
ansiEtsiPdh(38),
lapsSdh(40),
fddi(41),
dqdb(42),
fiberChannel3(43),
hdlc(44),
ethernetV2DixOnly(45),
ethernet802dot3Only(46),
g709ODUj(47),
g709OTUk(48),
g709CBRorCBRa(49),
g709CBRb(50),
g709BSOT(51),
g709BSNT(52),
gfpIPorPPP(53),
gfpEthernetMAC(54),
gfpEthernetPHY(55),
g709ESCON(56),
g709FICON(57),
g709FiberChannel(58)
}
IANAGmplsAdminStatusInformationTC ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"This data type determines the setting of the
Admin Status flags in the Admin Status object or TLV, as
described in RFC 3471. Setting this object to a non-zero
value will result in the inclusion of the Admin Status
object or TLV on signaling messages.
This textual convention is strongly tied to the
Administrative Status Information Flags sub-registry of
the GMPLS Signaling Parameters registry managed by IANA.
Values should be assigned by IANA in step with the
Administrative Status Flags sub-registry and using the
same registry management rules. However, the actual
values used in this textual convention are solely
within the purview of IANA and do not necessarily match
the values in the Administrative Status Information
Flags sub-registry.
The definition of this textual convention with the
addition of newly assigned values is published
periodically by the IANA, in either the Assigned
Numbers RFC, or some derivative of it specific to
Internet Network Management number assignments. (The
latest arrangements can be obtained by contacting the
IANA.)
Requests for new values should be made to IANA via
email (iana@iana.org)."
REFERENCE
"1. Generalized Multi-Protocol Label Switching (GMPLS)
Signaling Functional Description, RFC 3471, section 8.
2. Generalized MPLS Signaling - RSVP-TE Extensions,
RFC 3473, section 7.
3. GMPLS - Communication of Alarm Information,
RFC 4783, section 3.2.1."
SYNTAX BITS {
reflect(0), -- Reflect bit (RFC 3471)
reserved1(1), -- reserved
reserved2(2), -- reserved
reserved3(3), -- reserved
reserved4(4), -- reserved
reserved5(5), -- reserved
reserved6(6), -- reserved
reserved7(7), -- reserved
reserved8(8), -- reserved
reserved9(9), -- reserved
reserved10(10), -- reserved
reserved11(11), -- reserved
reserved12(12), -- reserved
reserved13(13), -- reserved
reserved14(14), -- reserved
reserved15(15), -- reserved
reserved16(16), -- reserved
reserved17(17), -- reserved
reserved18(18), -- reserved
reserved19(19), -- reserved
reserved20(20), -- reserved
reserved21(21), -- reserved
reserved22(22), -- reserved
reserved23(23), -- reserved
reserved24(24), -- reserved
reserved25(25), -- reserved
reserved26(26), -- reserved
reserved27(27), -- Inhibit Alarm bit (RFC 4783)
reserved28(28), -- reserved
testing(29), -- Testing bit (RFC 3473)
administrativelyDown(30), -- Admin down (RFC 3473)
deleteInProgress(31) -- Delete bit (RFC 3473)
}
END
--
-- Copyright (C) The IETF Trust (2007).
--
-- This document is subject to the rights, licenses and restrictions
-- contained in BCP 78, and except as set forth therein, the authors
-- retain all their rights.
--
-- This document and the information contained herein are provided on an
-- "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
-- OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND
-- THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS
-- OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
-- THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
-- WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
--
-- Intellectual Property
--
-- The IETF takes no position regarding the validity or scope of any
-- Intellectual Property Rights or other rights that might be claimed to
-- pertain to the implementation or use of the technology described in
-- this document or the extent to which any license under such rights
-- might or might not be available; nor does it represent that it has
-- made any independent effort to identify any such rights. Information
-- on the procedures with respect to rights in RFC documents can be
-- found in BCP 78 and BCP 79.
--
-- Copies of IPR disclosures made to the IETF Secretariat and any
-- assurances of licenses to be made available, or the result of an
-- attempt made to obtain a general license or permission for the use of
-- such proprietary rights by implementers or users of this
-- specification can be obtained from the IETF on-line IPR repository at
-- http://www.ietf.org/ipr.
--
-- The IETF invites any interested party to bring to its attention any
-- copyrights, patents or patent applications, or other proprietary
-- rights that may cover technology that may be required to implement
-- this standard. Please address the information to the IETF at
-- ietf-ipr@ietf.org.
--

335
priv/mibs/IANA-ITU-ALARM-TC-MIB Normal file
View file

@ -0,0 +1,335 @@
IANA-ITU-ALARM-TC-MIB DEFINITIONS ::= BEGIN
IMPORTS
MODULE-IDENTITY, mib-2 FROM SNMPv2-SMI
TEXTUAL-CONVENTION FROM SNMPv2-TC;
ianaItuAlarmNumbers MODULE-IDENTITY
LAST-UPDATED "201405220000Z" -- May 22, 2014
ORGANIZATION "IANA"
CONTACT-INFO
"Postal: Internet Assigned Numbers Authority
Internet Corporation for Assigned Names
and Numbers
12025 Waterfront Drive, Suite 300
Los Angeles, CA 90094-2536
USA
Tel: +1 310-301-5800
E-Mail: iana&iana.org"
DESCRIPTION
"The MIB module defines the ITU Alarm
textual convention for objects expected to require
regular extension.
Copyright (C) The Internet Society (2004). The
initial version of this MIB module was published
in RFC 3877. For full legal notices see the RFC
itself. Supplementary information may be available on:
http://www.ietf.org/copyrights/ianamib.html"
REVISION "201405220000Z"
DESCRIPTION
"Updated contact info."
REVISION "200409090000Z"
DESCRIPTION
"Initial version, published as RFC 3877."
::= { mib-2 119 }
IANAItuProbableCause ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"ITU-T probable cause values. Duplicate values defined in
X.733 are appended with X733 to ensure syntactic uniqueness.
Probable cause value 0 is reserved for special purposes.
The Internet Assigned Number Authority (IANA) is responsible
for the assignment of the enumerations in this TC.
IANAItuProbableCause value of 0 is reserved for special
purposes and MUST NOT be assigned.
Values of IANAItuProbableCause in the range 1 to 1023 are
reserved for causes that correspond to ITU-T probable cause.
All other requests for new causes will be handled on a
first-come, first served basis and will be assigned
enumeration values starting with 1025.
Request should come in the form of well-formed
SMI [RFC2578] for enumeration names that are unique and
sufficiently descriptive.
While some effort will be taken to ensure that new probable
causes do not conceptually duplicate existing probable
causes it is acknowledged that the existence of conceptual
duplicates in the starting probable cause list is an known
industry reality.
To aid IANA in the administration of probable cause names
and values, the OPS Area Director will appoint one or more
experts to help review requests.
See http://www.iana.org"
REFERENCE
"ITU Recommendation M.3100, 'Generic Network Information
Model', 1995
ITU Recommendation X.733, 'Information Technology - Open
Systems Interconnection - System Management: Alarm
Reporting Function', 1992
ITU Recommendation X.736, 'Information Technology - Open
Systems Interconnection - System Management: Security
Alarm Reporting Function', 1992"
SYNTAX INTEGER
{
-- The following probable causes were defined in M.3100
aIS (1),
callSetUpFailure (2),
degradedSignal (3),
farEndReceiverFailure (4),
framingError (5),
lossOfFrame (6),
lossOfPointer (7),
lossOfSignal (8),
payloadTypeMismatch (9),
transmissionError (10),
remoteAlarmInterface (11),
excessiveBER (12),
pathTraceMismatch (13),
unavailable (14),
signalLabelMismatch (15),
lossOfMultiFrame (16),
receiveFailure (17),
transmitFailure (18),
modulationFailure (19),
demodulationFailure (20),
broadcastChannelFailure (21),
connectionEstablishmentError (22),
invalidMessageReceived (23),
localNodeTransmissionError (24),
remoteNodeTransmissionError (25),
routingFailure (26),
--Values 27-50 are reserved for communications alarm related
--probable causes
-- The following are used with equipment alarm.
backplaneFailure (51),
dataSetProblem (52),
equipmentIdentifierDuplication (53),
externalIFDeviceProblem (54),
lineCardProblem (55),
multiplexerProblem (56),
nEIdentifierDuplication (57),
powerProblem (58),
processorProblem (59),
protectionPathFailure (60),
receiverFailure (61),
replaceableUnitMissing (62),
replaceableUnitTypeMismatch (63),
synchronizationSourceMismatch (64),
terminalProblem (65),
timingProblem (66),
transmitterFailure (67),
trunkCardProblem (68),
replaceableUnitProblem (69),
realTimeClockFailure (70),
--An equipment alarm to be issued if the system detects that the
--real time clock has failed
antennaFailure (71),
batteryChargingFailure (72),
diskFailure (73),
frequencyHoppingFailure (74),
iODeviceError (75),
lossOfSynchronisation (76),
lossOfRedundancy (77),
powerSupplyFailure (78),
signalQualityEvaluationFailure (79),
tranceiverFailure (80),
protectionMechanismFailure (81),
protectingResourceFailure (82),
-- Values 83-100 are reserved for equipment alarm related probable
-- causes
-- The following are used with environmental alarm.
airCompressorFailure (101),
airConditioningFailure (102),
airDryerFailure (103),
batteryDischarging (104),
batteryFailure (105),
commercialPowerFailure (106),
coolingFanFailure (107),
engineFailure (108),
fireDetectorFailure (109),
fuseFailure (110),
generatorFailure (111),
lowBatteryThreshold (112),
pumpFailure (113),
rectifierFailure (114),
rectifierHighVoltage (115),
rectifierLowFVoltage (116),
ventilationsSystemFailure (117),
enclosureDoorOpen (118),
explosiveGas (119),
fire (120),
flood (121),
highHumidity (122),
highTemperature (123),
highWind (124),
iceBuildUp (125),
intrusionDetection (126),
lowFuel (127),
lowHumidity (128),
lowCablePressure (129),
lowTemperatue (130),
lowWater (131),
smoke (132),
toxicGas (133),
coolingSystemFailure (134),
externalEquipmentFailure (135),
externalPointFailure (136),
-- Values 137-150 are reserved for environmental alarm related
-- probable causes
-- The following are used with Processing error alarm.
storageCapacityProblem (151),
memoryMismatch (152),
corruptData (153),
outOfCPUCycles (154),
sfwrEnvironmentProblem (155),
sfwrDownloadFailure (156),
lossOfRealTimel (157),
--A processing error alarm to be issued after the system has
--reinitialised. This will indicate
--to the management systems that the view they have of the managed
--system may no longer
--be valid. Usage example: The managed
--system issues this alarm after a reinitialization with severity
--warning to inform the
--management system about the event. No clearing notification will
--be sent.
applicationSubsystemFailure (158),
configurationOrCustomisationError (159),
databaseInconsistency (160),
fileError (161),
outOfMemory (162),
softwareError (163),
timeoutExpired (164),
underlayingResourceUnavailable (165),
versionMismatch (166),
--Values 168-200 are reserved for processing error alarm related
-- probable causes.
bandwidthReduced (201),
congestion (202),
excessiveErrorRate (203),
excessiveResponseTime (204),
excessiveRetransmissionRate (205),
reducedLoggingCapability (206),
systemResourcesOverload (207 ),
-- The following were defined X.733
adapterError (500),
applicationSubsystemFailture (501),
bandwidthReducedX733 (502),
callEstablishmentError (503),
communicationsProtocolError (504),
communicationsSubsystemFailure (505),
configurationOrCustomizationError (506),
congestionX733 (507),
coruptData (508),
cpuCyclesLimitExceeded (509),
dataSetOrModemError (510),
degradedSignalX733 (511),
dteDceInterfaceError (512),
enclosureDoorOpenX733 (513),
equipmentMalfunction (514),
excessiveVibration (515),
fileErrorX733 (516),
fireDetected (517),
framingErrorX733 (518),
heatingVentCoolingSystemProblem (519),
humidityUnacceptable (520),
inputOutputDeviceError (521),
inputDeviceError (522),
lanError (523),
leakDetected (524),
localNodeTransmissionErrorX733 (525),
lossOfFrameX733 (526),
lossOfSignalX733 (527),
materialSupplyExhausted (528),
multiplexerProblemX733 (529),
outOfMemoryX733 (530),
ouputDeviceError (531),
performanceDegraded (532),
powerProblems (533),
pressureUnacceptable (534),
processorProblems (535),
pumpFailureX733 (536),
queueSizeExceeded (537),
receiveFailureX733 (538),
receiverFailureX733 (539),
remoteNodeTransmissionErrorX733 (540),
resourceAtOrNearingCapacity (541),
responseTimeExecessive (542),
retransmissionRateExcessive (543),
softwareErrorX733 (544),
softwareProgramAbnormallyTerminated (545),
softwareProgramError (546),
storageCapacityProblemX733 (547),
temperatureUnacceptable (548),
thresholdCrossed (549),
timingProblemX733 (550),
toxicLeakDetected (551),
transmitFailureX733 (552),
transmiterFailure (553),
underlyingResourceUnavailable (554),
versionMismatchX733 (555),
-- The following are defined in X.736
authenticationFailure (600),
breachOfConfidentiality (601),
cableTamper (602),
delayedInformation (603),
denialOfService (604),
duplicateInformation (605),
informationMissing (606),
informationModificationDetected (607),
informationOutOfSequence (608),
keyExpired (609),
nonRepudiationFailure (610),
outOfHoursActivity (611),
outOfService (612),
proceduralError (613),
unauthorizedAccessAttempt (614),
unexpectedInformation (615),
other (1024)
}
IANAItuEventType ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"The ITU event Type values.
The Internet Assigned Number Authority (IANA) is
responsible for the assignment of the enumerations
in this TC.
Request should come in the form of well-formed
SMI [RFC2578] for enumeration names that are unique
and sufficiently descriptive.
See http://www.iana.org "
REFERENCE
"ITU Recommendation X.736, 'Information Technology - Open
Systems Interconnection - System Management: Security
Alarm Reporting Function', 1992"
SYNTAX INTEGER
{
other (1),
communicationsAlarm (2),
qualityOfServiceAlarm (3),
processingErrorAlarm (4),
equipmentAlarm (5),
environmentalAlarm (6),
integrityViolation (7),
operationalViolation (8),
physicalViolation (9),
securityServiceOrMechanismViolation (10),
timeDomainViolation (11)
}
END

126
priv/mibs/IANA-LANGUAGE-MIB Normal file
View file

@ -0,0 +1,126 @@
IANA-LANGUAGE-MIB DEFINITIONS ::= BEGIN
IMPORTS
MODULE-IDENTITY, OBJECT-IDENTITY, mib-2
FROM SNMPv2-SMI;
ianaLanguages MODULE-IDENTITY
LAST-UPDATED "201405220000Z" -- May 22, 2014
ORGANIZATION "IANA"
CONTACT-INFO
"Internet Assigned Numbers Authority (IANA)
Postal: ICANN
12025 Waterfront Drive, Suite 300
Los Angeles, CA 90094-2536
Tel: +1 310-301-5800
E-Mail: iana&iana.org"
DESCRIPTION
"The MIB module registers object identifier values for
well-known programming and scripting languages. Every
language registration MUST describe the format used
when transferring scripts written in this language.
Any additions or changes to the contents of this MIB
module require Designated Expert Review as defined in
the Guidelines for Writing IANA Considerations Section
document. The Designated Expert will be selected by
the IESG Area Director of the OPS Area.
Note, this module does not have to register all possible
languages since languages are identified by object
identifier values. It is therefore possible to registered
languages in private OID trees. The references given below are not
normative with regard to the language version. Other
references might be better suited to describe some newer
versions of this language. The references are only
provided as `a pointer into the right direction'."
-- Revision log, in reverse chronological order
REVISION "201405220000Z" -- May 22, 2014
DESCRIPTION "Updated contact info."
REVISION "200005100000Z" -- May 10, 2000
DESCRIPTION "Import mib-2 instead of experimental, so that
this module compiles"
REVISION "199909090900Z" -- September 9, 1999
DESCRIPTION "Initial version as published at time of
publication of RFC 2591."
::= { mib-2 73 }
ianaLangJavaByteCode OBJECT-IDENTITY
STATUS current
DESCRIPTION
"Java byte code to be processed by a Java virtual machine.
A script written in Java byte code is transferred by using
the Java archive file format (JAR)."
REFERENCE
"The Java Virtual Machine Specification.
ISBN 0-201-63452-X"
::= { ianaLanguages 1 }
ianaLangTcl OBJECT-IDENTITY
STATUS current
DESCRIPTION
"The Tool Command Language (Tcl). A script written in the
Tcl language is transferred in Tcl source code format."
REFERENCE
"Tcl and the Tk Toolkit.
ISBN 0-201-63337-X"
::= { ianaLanguages 2 }
ianaLangPerl OBJECT-IDENTITY
STATUS current
DESCRIPTION
"The Perl language. A script written in the Perl language
is transferred in Perl source code format."
REFERENCE
"Programming Perl.
ISBN 1-56592-149-6"
::= { ianaLanguages 3 }
ianaLangScheme OBJECT-IDENTITY
STATUS current
DESCRIPTION
"The Scheme language. A script written in the Scheme
language is transferred in Scheme source code format."
REFERENCE
"The Revised^4 Report on the Algorithmic Language Scheme.
MIT Press"
::= { ianaLanguages 4 }
ianaLangSRSL OBJECT-IDENTITY
STATUS current
DESCRIPTION
"The SNMP Script Language defined by SNMP Research. A
script written in the SNMP Script Language is transferred
in the SNMP Script Language source code format."
::= { ianaLanguages 5 }
ianaLangPSL OBJECT-IDENTITY
STATUS current
DESCRIPTION
"The Patrol Script Language defined by BMC Software. A script
written in the Patrol Script Language is transferred in the
Patrol Script Language source code format."
REFERENCE
"PATROL Script Language Reference Manual, Version 3.0,
November 30, 1995. BMC Software, Inc. 2101 City West Blvd.,
Houston, Texas 77042."
::= { ianaLanguages 6 }
ianaLangSMSL OBJECT-IDENTITY
STATUS current
DESCRIPTION
"The Systems Management Scripting Language. A script written
in the SMSL language is transferred in the SMSL source code
format."
REFERENCE
"ISO/ITU Command Sequencer.
ISO 10164-21 or ITU X.753"
::= { ianaLanguages 7 }
END

903
priv/mibs/IANA-MAU-MIB Normal file
View file

@ -0,0 +1,903 @@
IANA-MAU-MIB DEFINITIONS ::= BEGIN
IMPORTS
MODULE-IDENTITY, OBJECT-IDENTITY, mib-2
FROM SNMPv2-SMI
TEXTUAL-CONVENTION
FROM SNMPv2-TC
;
ianaMauMIB MODULE-IDENTITY
LAST-UPDATED "201002230000Z" -- February 23, 2010
ORGANIZATION "IANA"
CONTACT-INFO " Internet Assigned Numbers Authority
Postal: ICANN
4676 Admiralty Way, Suite 330
Marina del Rey, CA 90292
Tel: +1-310-823-9358
EMail: iana&iana.org"
DESCRIPTION
"This MIB module defines dot3MauType OBJECT-IDENTITIES and
IANAifMauListBits, IANAifMauMediaAvailable,
IANAifMauAutoNegCapBits, and IANAifJackType
TEXTUAL-CONVENTIONs, specifying enumerated values of the
ifMauTypeListBits, ifMauMediaAvailable / rpMauMediaAvailable,
ifMauAutoNegCapabilityBits / ifMauAutoNegCapAdvertisedBits /
ifMauAutoNegCapReceivedBits and ifJackType / rpJackType objects
respectively, defined in the MAU-MIB.
It is intended that each new MAU type, Media Availability
state, Auto Negotiation capability and/or Jack type defined by
the IEEE 802.3 working group and approved for publication in a
revision of IEEE Std 802.3 will be added to this MIB module,
provided that it is suitable for being managed by the base
objects in the MAU-MIB. An Expert Review, as defined in
RFC 2434 [RFC2434], is REQUIRED for such additions.
The following reference is used throughout this MIB module:
[IEEE802.3] refers to:
IEEE Std 802.3, 2005 Edition: 'IEEE Standard for
Information technology - Telecommunications and information
exchange between systems - Local and metropolitan area
networks - Specific requirements -
Part 3: Carrier sense multiple access with collision
detection (CSMA/CD) access method and physical layer
specifications'.
This reference should be updated as appropriate when new
MAU types, Media Availability states, Auto Negotiation
capabilities, and/or Jack types are added to this MIB module.
Copyright (C) The IETF Trust (2007).
The initial version of this MIB module was published in
RFC 4836; for full legal notices see the RFC itself.
Supplementary information may be available at:
http://www.ietf.org/copyrights/ianamib.html"
REVISION "201002230000Z" -- February 23, 2010
DESCRIPTION "Added assignments that will be included in
Clause 14 of IEEE P802.3.1."
REVISION "200704210000Z" -- April 21, 2007
DESCRIPTION "Initial version of this MIB as published in
RFC 4836."
::= { mib-2 154 }
-- Textual Conventions
IANAifMauTypeListBits ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"This data type is used as the syntax of the ifMauTypeListBits
object in the (updated) definition of MAU-MIB's ifMauTable.
The most recent version of this textual convention is available
in the online version of this MIB module on the IANA web site.
Requests for new values should be made to IANA via email
(iana&iana.org).
Note that changes in this textual convention SHALL be
synchronized with relevant changes in the dot3MauType
OBJECT-IDENTITIES."
REFERENCE
"[IEEE802.3], Section 30.5.1.1.2"
SYNTAX BITS {
bOther(0), -- other or unknown
bAUI(1), -- AUI
b10base5(2), -- 10BASE-5
bFoirl(3), -- FOIRL
b10base2(4), -- 10BASE-2
b10baseT(5), -- 10BASE-T duplex mode unknown
b10baseFP(6), -- 10BASE-FP
b10baseFB(7), -- 10BASE-FB
b10baseFL(8), -- 10BASE-FL duplex mode unknown
b10broad36(9), -- 10BROAD36
b10baseTHD(10), -- 10BASE-T half duplex mode
b10baseTFD(11), -- 10BASE-T full duplex mode
b10baseFLHD(12), -- 10BASE-FL half duplex mode
b10baseFLFD(13), -- 10BASE-FL full duplex mode
b100baseT4(14), -- 100BASE-T4
b100baseTXHD(15), -- 100BASE-TX half duplex mode
b100baseTXFD(16), -- 100BASE-TX full duplex mode
b100baseFXHD(17), -- 100BASE-FX half duplex mode
b100baseFXFD(18), -- 100BASE-FX full duplex mode
b100baseT2HD(19), -- 100BASE-T2 half duplex mode
b100baseT2FD(20), -- 100BASE-T2 full duplex mode
b1000baseXHD(21), -- 1000BASE-X half duplex mode
b1000baseXFD(22), -- 1000BASE-X full duplex mode
b1000baseLXHD(23), -- 1000BASE-LX half duplex mode
b1000baseLXFD(24), -- 1000BASE-LX full duplex mode
b1000baseSXHD(25), -- 1000BASE-SX half duplex mode
b1000baseSXFD(26), -- 1000BASE-SX full duplex mode
b1000baseCXHD(27), -- 1000BASE-CX half duplex mode
b1000baseCXFD(28), -- 1000BASE-CX full duplex mode
b1000baseTHD(29), -- 1000BASE-T half duplex mode
b1000baseTFD(30), -- 1000BASE-T full duplex mode
b10GbaseX(31), -- 10GBASE-X
b10GbaseLX4(32), -- 10GBASE-LX4
b10GbaseR(33), -- 10GBASE-R
b10GbaseER(34), -- 10GBASE-ER
b10GbaseLR(35), -- 10GBASE-LR
b10GbaseSR(36), -- 10GBASE-SR
b10GbaseW(37), -- 10GBASE-W
b10GbaseEW(38), -- 10GBASE-EW
b10GbaseLW(39), -- 10GBASE-LW
b10GbaseSW(40), -- 10GBASE-SW
-- new since RFC 3636
b10GbaseCX4(41), -- 10GBASE-CX4
b2BaseTL(42), -- 2BASE-TL
b10PassTS(43), -- 10PASS-TS
b100BaseBX10D(44), -- 100BASE-BX10D
b100BaseBX10U(45), -- 100BASE-BX10U
b100BaseLX10(46), -- 100BASE-LX10
b1000BaseBX10D(47), -- 1000BASE-BX10D
b1000BaseBX10U(48), -- 1000BASE-BX10U
b1000BaseLX10(49), -- 1000BASE-LX10
b1000BasePX10D(50), -- 1000BASE-PX10D
b1000BasePX10U(51), -- 1000BASE-PX10U
b1000BasePX20D(52), -- 1000BASE-PX20D
b1000BasePX20U(53), -- 1000BASE-PX20U
b10GbaseT(54), -- 10GBASE-T
b10GbaseLRM(55), -- 10GBASE-LRM
b1000baseKX(56), -- 1000BASE-KX
b10GbaseKX4(57), -- 10GBASE-KX4
b10GbaseKR(58), -- 10GBASE-KR
b10G1GbasePRXD1(59),-- 10/1GBASE-PRX-D1
b10G1GbasePRXD2(60),-- 10/1GBASE-PRX-D2
b10G1GbasePRXD3(61),-- 10/1GBASE-PRX-D3
b10G1GbasePRXU1(62),-- 10/1GBASE-PRX-U1
b10G1GbasePRXU2(63),-- 10/1GBASE-PRX-U2
b10G1GbasePRXU3(64),-- 10/1GBASE-PRX-U3
b10GbasePRD1(65), -- 10GBASE-PR-D1
b10GbasePRD2(66), -- 10GBASE-PR-D2
b10GbasePRD3(67), -- 10GBASE-PR-D3
b10GbasePRU1(68), -- 10GBASE-PR-U1
b10GbasePRU3(69) -- 10GBASE-PR-U3
}
IANAifMauMediaAvailable ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"This data type is used as the syntax of the
ifMauMediaAvailable and rpMauMediaAvailable objects in the
(updated) definition of MAU-MIB's ifMauTable and rpMauTable
respectively.
Possible values are:
other(1) - undefined (not listed below)
unknown(2) - MAU's true state is unknown; e.g.,
during initialization
available(3) - link, light, or loopback is normal
notAvailable(4) - link loss, low light, or no loopback
remoteFault(5) - a fault has been detected at the
remote end of the link. This value
applies to 10BASE-FB, 100BASE-T4 Far
End Fault Indication and non-specified
remote faults from a system running
auto-negotiation
invalidSignal(6) - invalid signal has been received from
the other end of the link, 10BASE-FB
only
remoteJabber(7) - remote fault, due to jabber
remoteLinkLoss(8) - remote fault, due to link loss
remoteTest(9) - remote fault, due to test
offline(10) - offline, Clause 37 Auto-Negotiation
only
autoNegError(11) - Auto-Negotiation Error, Clause 37
Auto-Negotiation only
pmdLinkFault(12) - PMA/PMD receive link fault. In case
of PAF (2BASE-TL / 10PASS-TS PHYs),
all PMEs in the aggregation group have
detected a link fault
wisFrameLoss(13) - WIS loss of frame, 10GBASE-W only
wisSignalLoss(14) - WIS loss of signal, 10GBASE-W only
pcsLinkFault(15) - PCS receive link fault
excessiveBER(16) - PCS Bit Error Ratio monitor
reporting excessive error ratio
dxsLinkFault(17) - DTE XGXS receive link fault, XAUI only
pxsLinkFault(18) - PHY XGXS receive link fault, XAUI only
availableReduced(19) - link normal, reduced bandwidth,
2BASE-TL / 10PASS-TS only
ready(20) - at least one PME in the aggregation
group is detecting handshake tones,
2BASE-TL / 10PASS-TS only
If the MAU is a 10M b/s link or fiber type (FOIRL, 10BASE-T,
10BASE-F), then this is equivalent to the link test fail
state/low light function. For an AUI, 10BASE2, 10BASE5, or
10BROAD36 MAU, this indicates whether loopback is detected on
the DI circuit. The value of this attribute persists between
packets for MAU types AUI, 10BASE5, 10BASE2, 10BROAD36, and
10BASEFP.
At power-up or following a reset, the Media Available state
will be unknown(2) for AUI, 10BASE5, 10BASE2, 10BROAD36, and
10BASE-FP MAUs. For these MAUs loopback will be tested on each
transmission during which no collision is detected.
If DI is receiving input when DO returns to IDL after a
transmission and there has been no collision during the
transmission, then loopback will be detected. The Media
Available state will only change during noncollided
transmissions for AUI, 10BASE2, 10BASE5, 10BROAD36, and
10BASE-FP MAUs.
For 100BASE-T2, 100BASE-T4, 100BASE-TX, 100BASE-FX,
100BASE-LX10, and 100BASE-BX10 PHYs the enumerations match the
states within the link integrity state diagram.
Any MAU that implements management of [IEEE802.3] Clause
28 Auto-Negotiation, will map remote fault indication to
remoteFault(5).
Any MAU that implements management of Clause 37
Auto-Negotiation, will map the received RF1 and RF2 bits as
follows: Offline maps to offline(10), Link_Failure maps to
remoteFault(5), and Auto-Negotiation Error maps to
autoNegError(11).
The value remoteFault(5) applies to 10BASE-FB remote
fault indication, the 100BASE-X far-end fault indication, and
nonspecified remote faults from a system running Clause 28
Auto-Negotiation.
The value remoteJabber(7), remoteLink loss(8), or remoteTest(9)
SHOULD be used instead of remoteFault(5) where the reason for
remote fault is identified in the remote signaling protocol.
Where a Clause 22 MII or Clause 35 GMII is present, a logic
one in the remote fault bit maps to the value remoteFault(5),
a logic zero in the link status bit maps to the enumeration
notAvailable(4). The value notAvailable(4) takes precedence
over remoteFault(5).
For 2BASE-TL and 10PASS-TS PHYs, the value unknown(2) maps to
the condition where the PHY (PCS with connected PMEs) is
initializing, the value ready(20) maps to the condition where
the interface is down and at least one PME in the aggregation
group is ready for handshake, the value available(3) maps to
the condition where all the PMEs in the aggregation group are
up, the value notAvailable(4) maps to the condition where all
the PMEs in the aggregation group are down and no handshake
tones are detected, the value availableReduced(19) maps to the
condition where the interface is up, a link fault is detected
at the receive direction by one or more PMEs in the
aggregation group, but at least one PME is up and the
enumeration pmdLinkFault(12) maps to the condition where a link
fault is detected at the receive direction by all of the PMEs
in the aggregation group.
For 10 Gb/s the enumerations map to value of the link_fault
variable within the Link Fault Signaling state diagram
as follows: the value OK maps to the value available(3),
the value Local Fault maps to the value notAvailable(4),
and the value Remote Fault maps to the value remoteFault(5).
The value pmdLinkFault(12), wisFrameLoss(13),
wisSignalLoss(14), pcsLinkFault(15), excessiveBER(16), or
dxsLinkFault(17) SHOULD be used instead of the value
notAvailable(4), where the reason for the Local Fault state can
be identified through the use of the Clause 45 MDIO Interface.
Where multiple reasons for the Local Fault state can be
identified, only the highest precedence error SHOULD be
reported. This precedence in descending order is as follows:
pxsLinkFault
pmdLinkFault
wisFrameLoss
wisSignalLoss
pcsLinkFault
excessiveBER
dxsLinkFault.
Where a Clause 45 MDIO interface is present a logic zero in
the PMA/PMD Receive link status bit ([IEEE802.3]
Section 45.2.1.2.2) maps to the value pmdLinkFault(12),
logic one in the LOF status bit (Section 45.2.2.10.4) maps
to the value wisFrameLoss(13), a logic one in the LOS
status bit (Section 45.2.2.10.5) maps to the value
wisSignalLoss, a logic zero in the PCS Receive
link status bit (Section 45.2.3.2.2) maps to the value
pcsLinkFault(15), a logic one in the 10GBASE-R PCS Latched
high BER status bit (Section 45.2.3.12.2) maps to the value
excessiveBER, a logic zero in the DTE XS receive link status
bit (Section 45.2.5.2.2) maps to the value dxsLinkFault(17)
and a logic zero in the PHY XS transmit link status bit
(Section 45.2.4.2.2) maps to the value pxsLinkFault(18).
The most recent version of this textual convention is available
in the online version of this MIB module on the IANA web site.
Requests for new values should be made to IANA via email
(iana&iana.org)."
REFERENCE
"[IEEE802.3], Section 30.5.1.1.4"
SYNTAX INTEGER {
other(1),
unknown(2),
available(3),
notAvailable(4),
remoteFault(5),
invalidSignal(6),
remoteJabber(7),
remoteLinkLoss(8),
remoteTest(9),
offline(10),
autoNegError(11),
pmdLinkFault(12),
wisFrameLoss(13),
wisSignalLoss(14),
pcsLinkFault(15),
excessiveBER(16),
dxsLinkFault(17),
pxsLinkFault(18),
availableReduced(19),
ready(20)
}
IANAifMauAutoNegCapBits ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"This data type is used as the syntax of the
ifMauAutoNegCapabilityBits, ifMauAutoNegCapAdvertisedBits, and
ifMauAutoNegCapReceivedBits objects in the (updated) definition
of MAU-MIB's ifMauAutoNegTable.
The most recent version of this textual convention is available
in the online version of this MIB module on the IANA web site.
Requests for new values should be made to IANA via email
(iana&iana.org)."
REFERENCE
"[IEEE802.3], Section 30.6.1.1.5"
SYNTAX BITS {
bOther(0), -- other or unknown
b10baseT(1), -- 10BASE-T half duplex mode
b10baseTFD(2), -- 10BASE-T full duplex mode
b100baseT4(3), -- 100BASE-T4
b100baseTX(4), -- 100BASE-TX half duplex mode
b100baseTXFD(5), -- 100BASE-TX full duplex mode
b100baseT2(6), -- 100BASE-T2 half duplex mode
b100baseT2FD(7), -- 100BASE-T2 full duplex mode
bFdxPause(8), -- PAUSE for full-duplex links
bFdxAPause(9), -- Asymmetric PAUSE for full-duplex
-- links
bFdxSPause(10), -- Symmetric PAUSE for full-duplex
-- links
bFdxBPause(11), -- Asymmetric and Symmetric PAUSE for
-- full-duplex links
b1000baseX(12), -- 1000BASE-X, -LX, -SX, -CX half
-- duplex mode
b1000baseXFD(13), -- 1000BASE-X, -LX, -SX, -CX full
-- duplex mode
b1000baseT(14), -- 1000BASE-T half duplex mode
b1000baseTFD(15), -- 1000BASE-T full duplex mode
b10GbaseT(16), -- 10GBASE-T
b1000baseKX(17), -- 1000BASE-KX
b10GbaseKX4(18), -- 10GBASE-KX4
b10GbaseKR(19) -- 10GBASE-KR
}
IANAifJackType ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"Common enumeration values for repeater and interface MAU
jack types. This data type is used as the syntax of the
ifJackType and rpJackType objects in the (updated) definition
of MAU-MIB's ifJackTable and rpJackTable respectively.
Possible values are:
other(1) - undefined or unknown
rj45(2) - RJ45
rj45S(3) - RJ45 shielded
db9(4) - DB9
bnc(5) - BNC
fAUI(6) - AUI female
mAUI(7) - AUI male
fiberSC(8) - SC fiber
fiberMIC(9) - MIC fiber
fiberST(10) - ST fiber
telco(11) - Telco
mtrj(12) - MT-RJ fiber
hssdc(13) - fiber channel style-2
fiberLC(14) - LC fiber
cx4(15) - IB4X for 10GBASE-CX4
The most recent version of this textual convention is available
in the online version of this MIB module on the IANA web site.
Requests for new values should be made to IANA via email
(iana&iana.org)."
SYNTAX INTEGER {
other(1),
rj45(2),
rj45S(3),
db9(4),
bnc(5),
fAUI(6),
mAUI(7),
fiberSC(8),
fiberMIC(9),
fiberST(10),
telco(11),
mtrj(12),
hssdc(13),
fiberLC(14),
-- new since RFC 3636
cx4(15)
}
-- OBJECT IDENTITIES for MAU types
-- (see rpMauType and ifMauType of MAU-MIB for usage)
-- The following definitions has been moved from RFC 3636 and
-- no longer appear in its revision.
dot3MauType OBJECT IDENTIFIER ::= { mib-2 snmpDot3MauMgt(26) 4 }
dot3MauTypeAUI OBJECT-IDENTITY
STATUS current
DESCRIPTION "no internal MAU, view from AUI"
REFERENCE "[IEEE802.3], Section 7"
::= { dot3MauType 1 }
dot3MauType10Base5 OBJECT-IDENTITY
STATUS current
DESCRIPTION "thick coax MAU"
REFERENCE "[IEEE802.3], Section 7"
::= { dot3MauType 2 }
dot3MauTypeFoirl OBJECT-IDENTITY
STATUS current
DESCRIPTION "FOIRL MAU"
REFERENCE "[IEEE802.3], Section 9.9"
::= { dot3MauType 3 }
dot3MauType10Base2 OBJECT-IDENTITY
STATUS current
DESCRIPTION "thin coax MAU"
REFERENCE "[IEEE802.3], Section 10"
::= { dot3MauType 4 }
dot3MauType10BaseT OBJECT-IDENTITY
STATUS current
DESCRIPTION "UTP MAU.
Note that it is strongly recommended that
agents return either dot3MauType10BaseTHD or
dot3MauType10BaseTFD if the duplex mode is
known. However, management applications should
be prepared to receive this MAU type value from
older agent implementations."
REFERENCE "[IEEE802.3], Section 14"
::= { dot3MauType 5 }
dot3MauType10BaseFP OBJECT-IDENTITY
STATUS current
DESCRIPTION "passive fiber MAU"
REFERENCE "[IEEE802.3], Section 16"
::= { dot3MauType 6 }
dot3MauType10BaseFB OBJECT-IDENTITY
STATUS current
DESCRIPTION "sync fiber MAU"
REFERENCE "[IEEE802.3], Section 17"
::= { dot3MauType 7 }
dot3MauType10BaseFL OBJECT-IDENTITY
STATUS current
DESCRIPTION "async fiber MAU.
Note that it is strongly recommended that
agents return either dot3MauType10BaseFLHD or
dot3MauType10BaseFLFD if the duplex mode is
known. However, management applications should
be prepared to receive this MAU type value from
older agent implementations."
REFERENCE "[IEEE802.3], Section 18"
::= { dot3MauType 8 }
dot3MauType10Broad36 OBJECT-IDENTITY
STATUS current
DESCRIPTION "broadband DTE MAU.
Note that 10BROAD36 MAUs can be attached to
interfaces but not to repeaters."
REFERENCE "[IEEE802.3], Section 11"
::= { dot3MauType 9 }
------ new since RFC 1515:
dot3MauType10BaseTHD OBJECT-IDENTITY
STATUS current
DESCRIPTION "UTP MAU, half duplex mode"
REFERENCE "[IEEE802.3], Section 14"
::= { dot3MauType 10 }
dot3MauType10BaseTFD OBJECT-IDENTITY
STATUS current
DESCRIPTION "UTP MAU, full duplex mode"
REFERENCE "[IEEE802.3], Section 14"
::= { dot3MauType 11 }
dot3MauType10BaseFLHD OBJECT-IDENTITY
STATUS current
DESCRIPTION "async fiber MAU, half duplex mode"
REFERENCE "[IEEE802.3], Section 18"
::= { dot3MauType 12 }
dot3MauType10BaseFLFD OBJECT-IDENTITY
STATUS current
DESCRIPTION "async fiber MAU, full duplex mode"
REFERENCE "[IEEE802.3], Section 18"
::= { dot3MauType 13 }
dot3MauType100BaseT4 OBJECT-IDENTITY
STATUS current
DESCRIPTION "4 pair category 3 UTP"
REFERENCE "[IEEE802.3], Section 23"
::= { dot3MauType 14 }
dot3MauType100BaseTXHD OBJECT-IDENTITY
STATUS current
DESCRIPTION "2 pair category 5 UTP, half duplex mode"
REFERENCE "[IEEE802.3], Section 25"
::= { dot3MauType 15 }
dot3MauType100BaseTXFD OBJECT-IDENTITY
STATUS current
DESCRIPTION "2 pair category 5 UTP, full duplex mode"
REFERENCE "[IEEE802.3], Section 25"
::= { dot3MauType 16 }
dot3MauType100BaseFXHD OBJECT-IDENTITY
STATUS current
DESCRIPTION "X fiber over PMT, half duplex mode"
REFERENCE "[IEEE802.3], Section 26"
::= { dot3MauType 17 }
dot3MauType100BaseFXFD OBJECT-IDENTITY
STATUS current
DESCRIPTION "X fiber over PMT, full duplex mode"
REFERENCE "[IEEE802.3], Section 26"
::= { dot3MauType 18 }
dot3MauType100BaseT2HD OBJECT-IDENTITY
STATUS current
DESCRIPTION "2 pair category 3 UTP, half duplex mode"
REFERENCE "[IEEE802.3], Section 32"
::= { dot3MauType 19 }
dot3MauType100BaseT2FD OBJECT-IDENTITY
STATUS current
DESCRIPTION "2 pair category 3 UTP, full duplex mode"
REFERENCE "[IEEE802.3], Section 32"
::= { dot3MauType 20 }
------ new since RFC 2239:
dot3MauType1000BaseXHD OBJECT-IDENTITY
STATUS current
DESCRIPTION "PCS/PMA, unknown PMD, half duplex mode"
REFERENCE "[IEEE802.3], Section 36"
::= { dot3MauType 21 }
dot3MauType1000BaseXFD OBJECT-IDENTITY
STATUS current
DESCRIPTION "PCS/PMA, unknown PMD, full duplex mode"
REFERENCE "[IEEE802.3], Section 36"
::= { dot3MauType 22 }
dot3MauType1000BaseLXHD OBJECT-IDENTITY
STATUS current
DESCRIPTION "Fiber over long-wavelength laser, half duplex
mode"
REFERENCE "[IEEE802.3], Section 38"
::= { dot3MauType 23 }
dot3MauType1000BaseLXFD OBJECT-IDENTITY
STATUS current
DESCRIPTION "Fiber over long-wavelength laser, full duplex
mode"
REFERENCE "[IEEE802.3], Section 38"
::= { dot3MauType 24 }
dot3MauType1000BaseSXHD OBJECT-IDENTITY
STATUS current
DESCRIPTION "Fiber over short-wavelength laser, half
duplex mode"
REFERENCE "[IEEE802.3], Section 38"
::= { dot3MauType 25 }
dot3MauType1000BaseSXFD OBJECT-IDENTITY
STATUS current
DESCRIPTION "Fiber over short-wavelength laser, full
duplex mode"
REFERENCE "[IEEE802.3], Section 38"
::= { dot3MauType 26 }
dot3MauType1000BaseCXHD OBJECT-IDENTITY
STATUS current
DESCRIPTION "Copper over 150-Ohm balanced cable, half
duplex mode"
REFERENCE "[IEEE802.3], Section 39"
::= { dot3MauType 27 }
dot3MauType1000BaseCXFD OBJECT-IDENTITY
STATUS current
DESCRIPTION "Copper over 150-Ohm balanced cable, full
duplex mode"
REFERENCE "[IEEE802.3], Section 39"
::= { dot3MauType 28 }
dot3MauType1000BaseTHD OBJECT-IDENTITY
STATUS current
DESCRIPTION "Four-pair Category 5 UTP, half duplex mode"
REFERENCE "[IEEE802.3], Section 40"
::= { dot3MauType 29 }
dot3MauType1000BaseTFD OBJECT-IDENTITY
STATUS current
DESCRIPTION "Four-pair Category 5 UTP, full duplex mode"
REFERENCE "[IEEE802.3], Section 40"
::= { dot3MauType 30 }
------ new since RFC 2668:
dot3MauType10GigBaseX OBJECT-IDENTITY
STATUS current
DESCRIPTION "X PCS/PMA, unknown PMD."
REFERENCE "[IEEE802.3], Section 48"
::= { dot3MauType 31 }
dot3MauType10GigBaseLX4 OBJECT-IDENTITY
STATUS current
DESCRIPTION "X fiber over WWDM optics"
REFERENCE "[IEEE802.3], Section 53"
::= { dot3MauType 32 }
dot3MauType10GigBaseR OBJECT-IDENTITY
STATUS current
DESCRIPTION "R PCS/PMA, unknown PMD."
REFERENCE "[IEEE802.3], Section 49"
::= { dot3MauType 33 }
dot3MauType10GigBaseER OBJECT-IDENTITY
STATUS current
DESCRIPTION "R fiber over 1550 nm optics"
REFERENCE "[IEEE802.3], Section 52"
::= { dot3MauType 34 }
dot3MauType10GigBaseLR OBJECT-IDENTITY
STATUS current
DESCRIPTION "R fiber over 1310 nm optics"
REFERENCE "[IEEE802.3], Section 52"
::= { dot3MauType 35 }
dot3MauType10GigBaseSR OBJECT-IDENTITY
STATUS current
DESCRIPTION "R fiber over 850 nm optics"
REFERENCE "[IEEE802.3], Section 52"
::= { dot3MauType 36 }
dot3MauType10GigBaseW OBJECT-IDENTITY
STATUS current
DESCRIPTION "W PCS/PMA, unknown PMD."
REFERENCE "[IEEE802.3], Section 49 and 50"
::= { dot3MauType 37 }
dot3MauType10GigBaseEW OBJECT-IDENTITY
STATUS current
DESCRIPTION "W fiber over 1550 nm optics"
REFERENCE "[IEEE802.3], Section 52"
::= { dot3MauType 38 }
dot3MauType10GigBaseLW OBJECT-IDENTITY
STATUS current
DESCRIPTION "W fiber over 1310 nm optics"
REFERENCE "[IEEE802.3], Section 52"
::= { dot3MauType 39 }
dot3MauType10GigBaseSW OBJECT-IDENTITY
STATUS current
DESCRIPTION "W fiber over 850 nm optics"
REFERENCE "[IEEE802.3], Section 52"
::= { dot3MauType 40 }
------ new since RFC 3636:
dot3MauType10GigBaseCX4 OBJECT-IDENTITY
STATUS current
DESCRIPTION "X copper over 8 pair 100-Ohm balanced cable"
REFERENCE "[IEEE802.3], Section 54"
::= { dot3MauType 41 }
dot3MauType2BaseTL OBJECT-IDENTITY
STATUS current
DESCRIPTION "Voice grade UTP copper, up to 2700m, optional PAF"
REFERENCE "[IEEE802.3], Sections 61 and 63"
::= { dot3MauType 42 }
dot3MauType10PassTS OBJECT-IDENTITY
STATUS current
DESCRIPTION "Voice grade UTP copper, up to 750m, optional PAF"
REFERENCE "[IEEE802.3], Sections 61 and 62"
::= { dot3MauType 43 }
dot3MauType100BaseBX10D OBJECT-IDENTITY
STATUS current
DESCRIPTION "One single-mode fiber OLT, long wavelength, 10km"
REFERENCE "[IEEE802.3], Section 58"
::= { dot3MauType 44 }
dot3MauType100BaseBX10U OBJECT-IDENTITY
STATUS current
DESCRIPTION "One single-mode fiber ONU, long wavelength, 10km"
REFERENCE "[IEEE802.3], Section 58"
::= { dot3MauType 45 }
dot3MauType100BaseLX10 OBJECT-IDENTITY
STATUS current
DESCRIPTION "Two single-mode fibers, long wavelength, 10km"
REFERENCE "[IEEE802.3], Section 58"
::= { dot3MauType 46 }
dot3MauType1000BaseBX10D OBJECT-IDENTITY
STATUS current
DESCRIPTION "One single-mode fiber OLT, long wavelength, 10km"
REFERENCE "[IEEE802.3], Section 59"
::= { dot3MauType 47 }
dot3MauType1000BaseBX10U OBJECT-IDENTITY
STATUS current
DESCRIPTION "One single-mode fiber ONU, long wavelength, 10km"
REFERENCE "[IEEE802.3], Section 59"
::= { dot3MauType 48 }
dot3MauType1000BaseLX10 OBJECT-IDENTITY
STATUS current
DESCRIPTION "Two sigle-mode fiber, long wavelength, 10km"
REFERENCE "[IEEE802.3], Section 59"
::= { dot3MauType 49 }
dot3MauType1000BasePX10D OBJECT-IDENTITY
STATUS current
DESCRIPTION "One single-mode fiber EPON OLT, 10km"
REFERENCE "[IEEE802.3], Section 60"
::= { dot3MauType 50 }
dot3MauType1000BasePX10U OBJECT-IDENTITY
STATUS current
DESCRIPTION "One single-mode fiber EPON ONU, 10km"
REFERENCE "[IEEE802.3], Section 60"
::= { dot3MauType 51 }
dot3MauType1000BasePX20D OBJECT-IDENTITY
STATUS current
DESCRIPTION "One single-mode fiber EPON OLT, 20km"
REFERENCE "[IEEE802.3], Section 60"
::= { dot3MauType 52 }
dot3MauType1000BasePX20U OBJECT-IDENTITY
STATUS current
DESCRIPTION "One single-mode fiber EPON ONU, 20km"
REFERENCE "[IEEE802.3], Section 60"
::= { dot3MauType 53 }
dot3MauType10GbaseT OBJECT-IDENTITY
STATUS current
DESCRIPTION "Four-pair Category 6A or better, full duplex mode only"
REFERENCE "IEEE Std 802.3, Clause 55"
::= { dot3MauType 54 }
dot3MauType10GbaseLRM OBJECT-IDENTITY
STATUS current
DESCRIPTION "R multimode fiber over 1310 nm optics"
REFERENCE "IEEE Std 802.3, Clause 68"
::= { dot3MauType 55 }
dot3MauType1000baseKX OBJECT-IDENTITY
STATUS current
DESCRIPTION "X backplane, full duplex mode only"
REFERENCE "IEEE Std 802.3, Clause 70"
::= { dot3MauType 56 }
dot3MauType10GbaseKX4 OBJECT-IDENTITY
STATUS current
DESCRIPTION "4 lane X backplane, full duplex mode only"
REFERENCE "IEEE Std 802.3, Clause 71"
::= { dot3MauType 57 }
dot3MauType10GbaseKR OBJECT-IDENTITY
STATUS current
DESCRIPTION "R backplane, full duplex mode only"
REFERENCE "IEEE Std 802.3, Clause 72"
::= { dot3MauType 58 }
dot3MauType10G1GbasePRXD1 OBJECT-IDENTITY
STATUS current
DESCRIPTION "One single-mode fiber asymmetric-rate EPON OLT, supporting low
power budget (PRX10)"
REFERENCE "IEEE Std 802.3, Clause 75"
::= { dot3MauType 59 }
dot3MauType10G1GbasePRXD2 OBJECT-IDENTITY
STATUS current
DESCRIPTION "One single-mode fiber asymmetric-rate EPON OLT, supporting
medium power budget (PRX20)"
REFERENCE "IEEE Std 802.3, Clause 75"
::= { dot3MauType 60 }
dot3MauType10G1GbasePRXD3 OBJECT-IDENTITY
STATUS current
DESCRIPTION "One single-mode fiber asymmetric-rate EPON OLT, supporting high
power budget (PRX30)"
REFERENCE "IEEE Std 802.3, Clause 75"
::= { dot3MauType 61 }
dot3MauType10G1GbasePRXU1 OBJECT-IDENTITY
STATUS current
DESCRIPTION "One single-mode fiber asymmetric-rate EPON ONU, supporting low
power budget (PRX10)"
REFERENCE "IEEE Std 802.3, Clause 75"
::= { dot3MauType 62 }
dot3MauType10G1GbasePRXU2 OBJECT-IDENTITY
STATUS current
DESCRIPTION "One single-mode fiber asymmetric-rate EPON ONU, supporting
medium power budget (PRX20)"
REFERENCE "IEEE Std 802.3, Clause 75"
::= { dot3MauType 63 }
dot3MauType10G1GbasePRXU3 OBJECT-IDENTITY
STATUS current
DESCRIPTION "One single-mode fiber asymmetric-rate EPON ONU, supporting high
power budget (PRX30)"
REFERENCE "IEEE Std 802.3, Clause 75"
::= { dot3MauType 64 }
dot3MauType10GbasePRD1 OBJECT-IDENTITY
STATUS current
DESCRIPTION "One single-mode fiber symmetric-rate EPON OLT, supporting low
power budget (PR10)"
REFERENCE "IEEE Std 802.3, Clause 75"
::= { dot3MauType 65 }
dot3MauType10GbasePRD2 OBJECT-IDENTITY
STATUS current
DESCRIPTION "One single-mode fiber symmetric-rate EPON OLT, supporting
medium power budget (PR20)"
REFERENCE "IEEE Std 802.3, Clause 75"
::= { dot3MauType 66 }
dot3MauType10GbasePRD3 OBJECT-IDENTITY
STATUS current
DESCRIPTION "One single-mode fiber symmetric-rate EPON OLT, supporting high
power budget (PR30)"
REFERENCE "IEEE Std 802.3, Clause 75"
::= { dot3MauType 67 }
dot3MauType10GbasePRU1 OBJECT-IDENTITY
STATUS current
DESCRIPTION "One single-mode fiber symmetric-rate EPON ONU, supporting
low and medium power budget (PR10 and PR20)"
REFERENCE "IEEE Std 802.3, Clause 75"
::= { dot3MauType 68 }
dot3MauType10GbasePRU3 OBJECT-IDENTITY
STATUS current
DESCRIPTION "One single-mode fiber symmetric-rate EPON ONU, supporting high
power budget (PR30)"
REFERENCE "IEEE Std 802.3, Clause 75"
::= { dot3MauType 69 }
END

1311
priv/mibs/IANA-PRINTER-MIB Normal file
View file

File diff suppressed because it is too large Load diff

137
priv/mibs/IANA-PWE3-MIB Normal file
View file

@ -0,0 +1,137 @@
IANA-PWE3-MIB DEFINITIONS ::= BEGIN
IMPORTS
MODULE-IDENTITY, mib-2
FROM SNMPv2-SMI -- [RFC2578]
TEXTUAL-CONVENTION
FROM SNMPv2-TC; -- [RFC2579]
ianaPwe3MIB MODULE-IDENTITY
LAST-UPDATED "200906110000Z" -- 11 June 2009 00:00:00 GMT
ORGANIZATION "IANA"
CONTACT-INFO
"Internet Assigned Numbers Authority
Internet Corporation for Assigned Names and Numbers
4676 Admiralty Way, Suite 330
Marina del Rey, CA 90292-6601
Phone: +1 310 823 9358
EMail: iana@iana.org"
DESCRIPTION
"This MIB module defines the IANAPwTypeTC and
IANAPwPsnTypeTC textual conventions for use in PWE3
MIB modules.
Any additions or changes to the contents of this MIB
module require either publication of an RFC, Designated
Expert Review as defined in RFC 5226, Guidelines for
Writing an IANA Considerations Section in RFCs, and should
be based on the procedures defined in [RFC4446]. The
Designated Expert will be selected by the IESG Area
Director(s) of the internet Area.
Copyright (c) 2009 IETF Trust and the persons identified as
authors of the code. All rights reserved.
Redistribution and use in source and binary forms, with or
without modification, are permitted provided that the
following conditions are met:
- Redistributions of source code must retain the above
copyright notice, this list of conditions and the
following disclaimer.
- Redistributions in binary form must reproduce the above
copyright notice, this list of conditions and the
following disclaimer in the documentation and/or other
materials provided with the distribution.
- Neither the name of Internet Society, IETF or IETF Trust,
nor the names of specific contributors, may be used to
endorse or promote products derived from this software
without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND
CONTRIBUTORS 'AS IS' AND ANY EXPRESS OR IMPLIED WARRANTIES,
INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR
CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT,
INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE
GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR
BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF
LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT
OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
POSSIBILITY OF SUCH DAMAGE. "
REVISION "200906110000Z" -- 11 June 2009 00:00:00 GMT
DESCRIPTION "Original version, published as part of RFC 5601."
::= { mib-2 174 }
IANAPwTypeTC ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"Indicates the PW type (i.e., the carried service). "
SYNTAX INTEGER {
other(0),
frameRelayDlciMartiniMode(1),
atmAal5SduVcc(2),
atmTransparent(3),
ethernetTagged(4),
ethernet(5),
hdlc(6),
ppp(7),
cem(8), -- Historic type
atmCellNto1Vcc(9),
atmCellNto1Vpc(10),
ipLayer2Transport(11),
atmCell1to1Vcc(12),
atmCell1to1Vpc(13),
atmAal5PduVcc(14),
frameRelayPortMode(15),
cep(16),
e1Satop(17),
t1Satop(18),
e3Satop(19),
t3Satop(20),
basicCesPsn(21),
basicTdmIp(22),
tdmCasCesPsn(23),
tdmCasTdmIp(24),
frDlci(25),
wildcard (32767)
}
IANAPwPsnTypeTC ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"Identifies the PSN type that the PW will use over the
network."
SYNTAX INTEGER {
mpls (1),
l2tp (2),
udpOverIp (3),
mplsOverIp (4),
mplsOverGre (5),
other (6)
}
IANAPwCapabilities ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"This TC describes a collection of capabilities related to
a specific PW.
Values may be added in the future based on new capabilities
introduced in IETF documents.
"
SYNTAX BITS {
pwStatusIndication (0), -- Applicable only if maintenance
-- protocol is in use.
pwVCCV (1)
}
END

102
priv/mibs/IANA-RTPROTO-MIB Normal file
View file

@ -0,0 +1,102 @@
IANA-RTPROTO-MIB DEFINITIONS ::= BEGIN
IMPORTS
MODULE-IDENTITY, mib-2 FROM SNMPv2-SMI
TEXTUAL-CONVENTION FROM SNMPv2-TC;
ianaRtProtoMIB MODULE-IDENTITY
LAST-UPDATED "201604250000Z" -- April 25, 2016
ORGANIZATION "IANA"
CONTACT-INFO
" Internet Assigned Numbers Authority
Internet Corporation for Assigned Names and Numbers
12025 Waterfront Drive, Suite 300
Los Angeles, CA 90094-2536
Phone: +1 310 301 5800
EMail: iana&iana.org"
DESCRIPTION
"This MIB module defines the IANAipRouteProtocol and
IANAipMRouteProtocol textual conventions for use in MIBs
which need to identify unicast or multicast routing
mechanisms.
Any additions or changes to the contents of this MIB module
require either publication of an RFC, or Designated Expert
Review as defined in RFC 2434, Guidelines for Writing an
IANA Considerations Section in RFCs. The Designated Expert
will be selected by the IESG Area Director(s) of the Routing
Area."
REVISION "201604250000Z" -- April 25, 2016
DESCRIPTION "Corrected typographical error in revision date."
REVISION "201604060000Z" -- April 6, 2016
DESCRIPTION "Added ttdp(20)."
REVISION "201208300000Z" -- August 30, 2012
DESCRIPTION "Added dhcp(19)."
REVISION "201107220000Z" -- July 22, 2011
DESCRIPTION "Added rpl(18) ."
REVISION "200009260000Z" -- September 26, 2000
DESCRIPTION "Original version, published in coordination
with RFC 2932."
::= { mib-2 84 }
IANAipRouteProtocol ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"A mechanism for learning routes. Inclusion of values for
routing protocols is not intended to imply that those
protocols need be supported."
SYNTAX INTEGER {
other (1), -- not specified
local (2), -- local interface
netmgmt (3), -- static route
icmp (4), -- result of ICMP Redirect
-- the following are all dynamic
-- routing protocols
egp (5), -- Exterior Gateway Protocol
ggp (6), -- Gateway-Gateway Protocol
hello (7), -- FuzzBall HelloSpeak
rip (8), -- Berkeley RIP or RIP-II
isIs (9), -- Dual IS-IS
esIs (10), -- ISO 9542
ciscoIgrp (11), -- Cisco IGRP
bbnSpfIgp (12), -- BBN SPF IGP
ospf (13), -- Open Shortest Path First
bgp (14), -- Border Gateway Protocol
idpr (15), -- InterDomain Policy Routing
ciscoEigrp (16), -- Cisco EIGRP
dvmrp (17), -- DVMRP
rpl (18), -- RPL [RFC-ietf-roll-rpl-19]
dhcp (19), -- DHCP [RFC2132]
ttdp (20) -- Train Topology Discovery Protocol (TTDP) [IEC 61375-2-5]
}
IANAipMRouteProtocol ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"The multicast routing protocol. Inclusion of values for
multicast routing protocols is not intended to imply that
those protocols need be supported."
SYNTAX INTEGER {
other(1), -- none of the following
local(2), -- e.g., manually configured
netmgmt(3), -- set via net.mgmt protocol
dvmrp(4),
mospf(5),
pimSparseDense(6), -- PIMv1, both DM and SM
cbt(7),
pimSparseMode(8), -- PIM-SM
pimDenseMode(9), -- PIM-DM
igmpOnly(10),
bgmp(11),
msdp(12)
}
END

750
priv/mibs/IANAifType-MIB Normal file
View file

@ -0,0 +1,750 @@
IANAifType-MIB DEFINITIONS ::= BEGIN
IMPORTS
MODULE-IDENTITY, mib-2 FROM SNMPv2-SMI
TEXTUAL-CONVENTION FROM SNMPv2-TC;
ianaifType MODULE-IDENTITY
LAST-UPDATED "202004020000Z" -- April 2, 2020
ORGANIZATION "IANA"
CONTACT-INFO " Internet Assigned Numbers Authority
Postal: ICANN
12025 Waterfront Drive, Suite 300
Los Angeles, CA 90094-2536
Tel: +1 310-301-5800
E-Mail: iana&iana.org"
DESCRIPTION "This MIB module defines the IANAifType Textual
Convention, and thus the enumerated values of
the ifType object defined in MIB-II's ifTable."
REVISION "202004020000Z" -- April 2, 2020
DESCRIPTION "Added reference to ifType definitions registry."
REVISION "202001100000Z" -- January 10, 2020
DESCRIPTION "Addition of IANAifType 299."
REVISION "201912030000Z" -- December 3, 2019
DESCRIPTION "Updated email address for IANA"
REVISION "201910160000Z" -- October 16, 2019
DESCRIPTION "Addition of IANAifTypes 297-298."
REVISION "201902140000Z" -- February 14, 2019
DESCRIPTION "Registration of new tunnelType 18."
REVISION "201902080000Z" -- February 8, 2019
DESCRIPTION "Added missing commas for 295-296."
REVISION "201901310000Z" -- January 31, 2019
DESCRIPTION "Registration of new IANAifTypes 295-296."
REVISION "201807040000Z" -- July 4, 2018
DESCRIPTION "Added missing commas for 291-293."
REVISION "201806280000Z" -- June 28, 2018
DESCRIPTION "Registration of new IANAifType 294."
REVISION "201806280000Z" -- June 28, 2018
DESCRIPTION "Registration of new IANAifType 293."
REVISION "201806220000Z" -- June 22, 2018
DESCRIPTION "Registration of new IANAifType 292."
REVISION "201806210000Z" -- June 21, 2018
DESCRIPTION "Registration of new IANAifType 291."
REVISION "201703300000Z" -- March 30, 2017
DESCRIPTION "Registration of new IANAifType 290."
REVISION "201701190000Z" -- January 19, 2017
DESCRIPTION "Registration of new IANAifType 289."
REVISION "201611230000Z" -- November 23, 2016
DESCRIPTION "Registration of new IANAifTypes 283-288."
REVISION "201606160000Z" -- June 16, 2016
DESCRIPTION "Updated IANAtunnelType DESCRIPTION per RFC 7870"
REVISION "201606090000Z" -- June 9, 2016
DESCRIPTION "Registration of new IANAifType 282."
REVISION "201606080000Z" -- June 8, 2016
DESCRIPTION "Updated description for tunnelType 17."
REVISION "201605190000Z" -- May 19, 2016
DESCRIPTION "Updated description for tunnelType 16."
REVISION "201605030000Z" -- May 3, 2016
DESCRIPTION "Registration of new IANAifType 281."
REVISION "201604290000Z" -- April 29, 2016
DESCRIPTION "Registration of new tunnelTypes 16 and 17."
REVISION "201409240000Z" -- September 24, 2014
DESCRIPTION "Registration of new IANAifType 280."
REVISION "201409190000Z" -- September 19, 2014
DESCRIPTION "Registration of new IANAifType 279."
REVISION "201407030000Z" -- July 3, 2014
DESCRIPTION "Registration of new IANAifTypes 277-278."
REVISION "201405220000Z" -- May 22, 2014
DESCRIPTION "Updated contact info."
REVISION "201205170000Z" -- May 17, 2012
DESCRIPTION "Registration of new IANAifType 272."
REVISION "201201110000Z" -- January 11, 2012
DESCRIPTION "Registration of new IANAifTypes 266-271."
REVISION "201112180000Z" -- December 18, 2011
DESCRIPTION "Registration of new IANAifTypes 263-265."
REVISION "201110260000Z" -- October 26, 2011
DESCRIPTION "Registration of new IANAifType 262."
REVISION "201109070000Z" -- September 7, 2011
DESCRIPTION "Registration of new IANAifTypes 260 and 261."
REVISION "201107220000Z" -- July 22, 2011
DESCRIPTION "Registration of new IANAifType 259."
REVISION "201106030000Z" -- June 03, 2011
DESCRIPTION "Registration of new IANAifType 258."
REVISION "201009210000Z" -- September 21, 2010
DESCRIPTION "Registration of new IANAifTypes 256 and 257."
REVISION "201007210000Z" -- July 21, 2010
DESCRIPTION "Registration of new IANAifType 255."
REVISION "201002110000Z" -- February 11, 2010
DESCRIPTION "Registration of new IANAifType 254."
REVISION "201002080000Z" -- February 08, 2010
DESCRIPTION "Registration of new IANAifTypes 252 and 253."
REVISION "200905060000Z" -- May 06, 2009
DESCRIPTION "Registration of new IANAifType 251."
REVISION "200902060000Z" -- February 06, 2009
DESCRIPTION "Registration of new IANAtunnelType 15."
REVISION "200810090000Z" -- October 09, 2008
DESCRIPTION "Registration of new IANAifType 250."
REVISION "200808120000Z" -- August 12, 2008
DESCRIPTION "Registration of new IANAifType 249."
REVISION "200807220000Z" -- July 22, 2008
DESCRIPTION "Registration of new IANAifTypes 247 and 248."
REVISION "200806240000Z" -- June 24, 2008
DESCRIPTION "Registration of new IANAifType 246."
REVISION "200805290000Z" -- May 29, 2008
DESCRIPTION "Registration of new IANAifType 245."
REVISION "200709130000Z" -- September 13, 2007
DESCRIPTION "Registration of new IANAifTypes 243 and 244."
REVISION "200705290000Z" -- May 29, 2007
DESCRIPTION "Changed the description for IANAifType 228."
REVISION "200703080000Z" -- March 08, 2007
DESCRIPTION "Registration of new IANAifType 242."
REVISION "200701230000Z" -- January 23, 2007
DESCRIPTION "Registration of new IANAifTypes 239, 240, and 241."
REVISION "200610170000Z" -- October 17, 2006
DESCRIPTION "Deprecated/Obsoleted IANAifType 230. Registration of
IANAifType 238."
REVISION "200609250000Z" -- September 25, 2006
DESCRIPTION "Changed the description for IANA ifType
184 and added new IANA ifType 237."
REVISION "200608170000Z" -- August 17, 2006
DESCRIPTION "Changed the descriptions for IANAifTypes
20 and 21."
REVISION "200608110000Z" -- August 11, 2006
DESCRIPTION "Changed the descriptions for IANAifTypes
7, 11, 62, 69, and 117."
REVISION "200607250000Z" -- July 25, 2006
DESCRIPTION "Registration of new IANA ifType 236."
REVISION "200606140000Z" -- June 14, 2006
DESCRIPTION "Registration of new IANA ifType 235."
REVISION "200603310000Z" -- March 31, 2006
DESCRIPTION "Registration of new IANA ifType 234."
REVISION "200603300000Z" -- March 30, 2006
DESCRIPTION "Registration of new IANA ifType 233."
REVISION "200512220000Z" -- December 22, 2005
DESCRIPTION "Registration of new IANA ifTypes 231 and 232."
REVISION "200510100000Z" -- October 10, 2005
DESCRIPTION "Registration of new IANA ifType 230."
REVISION "200509090000Z" -- September 09, 2005
DESCRIPTION "Registration of new IANA ifType 229."
REVISION "200505270000Z" -- May 27, 2005
DESCRIPTION "Registration of new IANA ifType 228."
REVISION "200503030000Z" -- March 3, 2005
DESCRIPTION "Added the IANAtunnelType TC and deprecated
IANAifType sixToFour (215) per RFC4087."
REVISION "200411220000Z" -- November 22, 2004
DESCRIPTION "Registration of new IANA ifType 227 per RFC4631."
REVISION "200406170000Z" -- June 17, 2004
DESCRIPTION "Registration of new IANA ifType 226."
REVISION "200405120000Z" -- May 12, 2004
DESCRIPTION "Added description for IANAifType 6, and
changed the descriptions for IANAifTypes
180, 181, and 182."
REVISION "200405070000Z" -- May 7, 2004
DESCRIPTION "Registration of new IANAifType 225."
REVISION "200308250000Z" -- Aug 25, 2003
DESCRIPTION "Deprecated IANAifTypes 7 and 11. Obsoleted
IANAifTypes 62, 69, and 117. ethernetCsmacd (6)
should be used instead of these values"
REVISION "200308180000Z" -- Aug 18, 2003
DESCRIPTION "Registration of new IANAifType
224."
REVISION "200308070000Z" -- Aug 7, 2003
DESCRIPTION "Registration of new IANAifTypes
222 and 223."
REVISION "200303180000Z" -- Mar 18, 2003
DESCRIPTION "Registration of new IANAifType
221."
REVISION "200301130000Z" -- Jan 13, 2003
DESCRIPTION "Registration of new IANAifType
220."
REVISION "200210170000Z" -- Oct 17, 2002
DESCRIPTION "Registration of new IANAifType
219."
REVISION "200207160000Z" -- Jul 16, 2002
DESCRIPTION "Registration of new IANAifTypes
217 and 218."
REVISION "200207100000Z" -- Jul 10, 2002
DESCRIPTION "Registration of new IANAifTypes
215 and 216."
REVISION "200206190000Z" -- Jun 19, 2002
DESCRIPTION "Registration of new IANAifType
214."
REVISION "200201040000Z" -- Jan 4, 2002
DESCRIPTION "Registration of new IANAifTypes
211, 212 and 213."
REVISION "200112200000Z" -- Dec 20, 2001
DESCRIPTION "Registration of new IANAifTypes
209 and 210."
REVISION "200111150000Z" -- Nov 15, 2001
DESCRIPTION "Registration of new IANAifTypes
207 and 208."
REVISION "200111060000Z" -- Nov 6, 2001
DESCRIPTION "Registration of new IANAifType
206."
REVISION "200111020000Z" -- Nov 2, 2001
DESCRIPTION "Registration of new IANAifType
205."
REVISION "200110160000Z" -- Oct 16, 2001
DESCRIPTION "Registration of new IANAifTypes
199, 200, 201, 202, 203, and 204."
REVISION "200109190000Z" -- Sept 19, 2001
DESCRIPTION "Registration of new IANAifType
198."
REVISION "200105110000Z" -- May 11, 2001
DESCRIPTION "Registration of new IANAifType
197."
REVISION "200101120000Z" -- Jan 12, 2001
DESCRIPTION "Registration of new IANAifTypes
195 and 196."
REVISION "200012190000Z" -- Dec 19, 2000
DESCRIPTION "Registration of new IANAifTypes
193 and 194."
REVISION "200012070000Z" -- Dec 07, 2000
DESCRIPTION "Registration of new IANAifTypes
191 and 192."
REVISION "200012040000Z" -- Dec 04, 2000
DESCRIPTION "Registration of new IANAifType
190."
REVISION "200010170000Z" -- Oct 17, 2000
DESCRIPTION "Registration of new IANAifTypes
188 and 189."
REVISION "200010020000Z" -- Oct 02, 2000
DESCRIPTION "Registration of new IANAifType 187."
REVISION "200009010000Z" -- Sept 01, 2000
DESCRIPTION "Registration of new IANAifTypes
184, 185, and 186."
REVISION "200008240000Z" -- Aug 24, 2000
DESCRIPTION "Registration of new IANAifType 183."
REVISION "200008230000Z" -- Aug 23, 2000
DESCRIPTION "Registration of new IANAifTypes
174-182."
REVISION "200008220000Z" -- Aug 22, 2000
DESCRIPTION "Registration of new IANAifTypes 170,
171, 172 and 173."
REVISION "200004250000Z" -- Apr 25, 2000
DESCRIPTION "Registration of new IANAifTypes 168 and 169."
REVISION "200003060000Z" -- Mar 6, 2000
DESCRIPTION "Fixed a missing semi-colon in the IMPORT.
Also cleaned up the REVISION log a bit.
It is not complete, but from now on it will
be maintained and kept up to date with each
change to this MIB module."
REVISION "199910081430Z" -- Oct 08, 1999
DESCRIPTION "Include new name assignments up to cnr(85).
This is the first version available via the WWW
at: ftp://ftp.isi.edu/mib/ianaiftype.mib"
REVISION "199401310000Z" -- Jan 31, 1994
DESCRIPTION "Initial version of this MIB as published in
RFC 1573."
::= { mib-2 30 }
IANAifType ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"This data type is used as the syntax of the ifType
object in the (updated) definition of MIB-II's
ifTable.
The definition of this textual convention with the
addition of newly assigned values is published
periodically by the IANA, in either the Assigned
Numbers RFC, or some derivative of it specific to
Internet Network Management number assignments. (The
latest arrangements can be obtained by contacting the
IANA.)
Interface types must not be directly added to the
IANAifType-MIB MIB module. They must instead be added
to the 'ifType definitions' registry at
https://www.iana.org/assignments/smi-numbers.
The relationship between the assignment of ifType
values and of OIDs to particular media-specific MIBs
is solely the purview of IANA and is subject to change
without notice. Quite often, a media-specific MIB's
OID-subtree assignment within MIB-II's 'transmission'
subtree will be the same as its ifType value.
However, in some circumstances this will not be the
case, and implementors must not pre-assume any
specific relationship between ifType values and
transmission subtree OIDs."
SYNTAX INTEGER {
other(1), -- none of the following
regular1822(2),
hdh1822(3),
ddnX25(4),
rfc877x25(5),
ethernetCsmacd(6), -- for all ethernet-like interfaces,
-- regardless of speed, as per RFC3635
iso88023Csmacd(7), -- Deprecated via RFC3635
-- ethernetCsmacd (6) should be used instead
iso88024TokenBus(8),
iso88025TokenRing(9),
iso88026Man(10),
starLan(11), -- Deprecated via RFC3635
-- ethernetCsmacd (6) should be used instead
proteon10Mbit(12),
proteon80Mbit(13),
hyperchannel(14),
fddi(15),
lapb(16),
sdlc(17),
ds1(18), -- DS1-MIB
e1(19), -- Obsolete see DS1-MIB
basicISDN(20), -- no longer used
-- see also RFC2127
primaryISDN(21), -- no longer used
-- see also RFC2127
propPointToPointSerial(22), -- proprietary serial
ppp(23),
softwareLoopback(24),
eon(25), -- CLNP over IP
ethernet3Mbit(26),
nsip(27), -- XNS over IP
slip(28), -- generic SLIP
ultra(29), -- ULTRA technologies
ds3(30), -- DS3-MIB
sip(31), -- SMDS, coffee
frameRelay(32), -- DTE only.
rs232(33),
para(34), -- parallel-port
arcnet(35), -- arcnet
arcnetPlus(36), -- arcnet plus
atm(37), -- ATM cells
miox25(38),
sonet(39), -- SONET or SDH
x25ple(40),
iso88022llc(41),
localTalk(42),
smdsDxi(43),
frameRelayService(44), -- FRNETSERV-MIB
v35(45),
hssi(46),
hippi(47),
modem(48), -- Generic modem
aal5(49), -- AAL5 over ATM
sonetPath(50),
sonetVT(51),
smdsIcip(52), -- SMDS InterCarrier Interface
propVirtual(53), -- proprietary virtual/internal
propMultiplexor(54),-- proprietary multiplexing
ieee80212(55), -- 100BaseVG
fibreChannel(56), -- Fibre Channel
hippiInterface(57), -- HIPPI interfaces
frameRelayInterconnect(58), -- Obsolete, use either
-- frameRelay(32) or
-- frameRelayService(44).
aflane8023(59), -- ATM Emulated LAN for 802.3
aflane8025(60), -- ATM Emulated LAN for 802.5
cctEmul(61), -- ATM Emulated circuit
fastEther(62), -- Obsoleted via RFC3635
-- ethernetCsmacd (6) should be used instead
isdn(63), -- ISDN and X.25
v11(64), -- CCITT V.11/X.21
v36(65), -- CCITT V.36
g703at64k(66), -- CCITT G703 at 64Kbps
g703at2mb(67), -- Obsolete see DS1-MIB
qllc(68), -- SNA QLLC
fastEtherFX(69), -- Obsoleted via RFC3635
-- ethernetCsmacd (6) should be used instead
channel(70), -- channel
ieee80211(71), -- radio spread spectrum
ibm370parChan(72), -- IBM System 360/370 OEMI Channel
escon(73), -- IBM Enterprise Systems Connection
dlsw(74), -- Data Link Switching
isdns(75), -- ISDN S/T interface
isdnu(76), -- ISDN U interface
lapd(77), -- Link Access Protocol D
ipSwitch(78), -- IP Switching Objects
rsrb(79), -- Remote Source Route Bridging
atmLogical(80), -- ATM Logical Port
ds0(81), -- Digital Signal Level 0
ds0Bundle(82), -- group of ds0s on the same ds1
bsc(83), -- Bisynchronous Protocol
async(84), -- Asynchronous Protocol
cnr(85), -- Combat Net Radio
iso88025Dtr(86), -- ISO 802.5r DTR
eplrs(87), -- Ext Pos Loc Report Sys
arap(88), -- Appletalk Remote Access Protocol
propCnls(89), -- Proprietary Connectionless Protocol
hostPad(90), -- CCITT-ITU X.29 PAD Protocol
termPad(91), -- CCITT-ITU X.3 PAD Facility
frameRelayMPI(92), -- Multiproto Interconnect over FR
x213(93), -- CCITT-ITU X213
adsl(94), -- Asymmetric Digital Subscriber Loop
radsl(95), -- Rate-Adapt. Digital Subscriber Loop
sdsl(96), -- Symmetric Digital Subscriber Loop
vdsl(97), -- Very H-Speed Digital Subscrib. Loop
iso88025CRFPInt(98), -- ISO 802.5 CRFP
myrinet(99), -- Myricom Myrinet
voiceEM(100), -- voice recEive and transMit
voiceFXO(101), -- voice Foreign Exchange Office
voiceFXS(102), -- voice Foreign Exchange Station
voiceEncap(103), -- voice encapsulation
voiceOverIp(104), -- voice over IP encapsulation
atmDxi(105), -- ATM DXI
atmFuni(106), -- ATM FUNI
atmIma (107), -- ATM IMA
pppMultilinkBundle(108), -- PPP Multilink Bundle
ipOverCdlc (109), -- IBM ipOverCdlc
ipOverClaw (110), -- IBM Common Link Access to Workstn
stackToStack (111), -- IBM stackToStack
virtualIpAddress (112), -- IBM VIPA
mpc (113), -- IBM multi-protocol channel support
ipOverAtm (114), -- IBM ipOverAtm
iso88025Fiber (115), -- ISO 802.5j Fiber Token Ring
tdlc (116), -- IBM twinaxial data link control
gigabitEthernet (117), -- Obsoleted via RFC3635
-- ethernetCsmacd (6) should be used instead
hdlc (118), -- HDLC
lapf (119), -- LAP F
v37 (120), -- V.37
x25mlp (121), -- Multi-Link Protocol
x25huntGroup (122), -- X25 Hunt Group
transpHdlc (123), -- Transp HDLC
interleave (124), -- Interleave channel
fast (125), -- Fast channel
ip (126), -- IP (for APPN HPR in IP networks)
docsCableMaclayer (127), -- CATV Mac Layer
docsCableDownstream (128), -- CATV Downstream interface
docsCableUpstream (129), -- CATV Upstream interface
a12MppSwitch (130), -- Avalon Parallel Processor
tunnel (131), -- Encapsulation interface
coffee (132), -- coffee pot
ces (133), -- Circuit Emulation Service
atmSubInterface (134), -- ATM Sub Interface
l2vlan (135), -- Layer 2 Virtual LAN using 802.1Q
l3ipvlan (136), -- Layer 3 Virtual LAN using IP
l3ipxvlan (137), -- Layer 3 Virtual LAN using IPX
digitalPowerline (138), -- IP over Power Lines
mediaMailOverIp (139), -- Multimedia Mail over IP
dtm (140), -- Dynamic syncronous Transfer Mode
dcn (141), -- Data Communications Network
ipForward (142), -- IP Forwarding Interface
msdsl (143), -- Multi-rate Symmetric DSL
ieee1394 (144), -- IEEE1394 High Performance Serial Bus
if-gsn (145), -- HIPPI-6400
dvbRccMacLayer (146), -- DVB-RCC MAC Layer
dvbRccDownstream (147), -- DVB-RCC Downstream Channel
dvbRccUpstream (148), -- DVB-RCC Upstream Channel
atmVirtual (149), -- ATM Virtual Interface
mplsTunnel (150), -- MPLS Tunnel Virtual Interface
srp (151), -- Spatial Reuse Protocol
voiceOverAtm (152), -- Voice Over ATM
voiceOverFrameRelay (153), -- Voice Over Frame Relay
idsl (154), -- Digital Subscriber Loop over ISDN
compositeLink (155), -- Avici Composite Link Interface
ss7SigLink (156), -- SS7 Signaling Link
propWirelessP2P (157), -- Prop. P2P wireless interface
frForward (158), -- Frame Forward Interface
rfc1483 (159), -- Multiprotocol over ATM AAL5
usb (160), -- USB Interface
ieee8023adLag (161), -- IEEE 802.3ad Link Aggregate
bgppolicyaccounting (162), -- BGP Policy Accounting
frf16MfrBundle (163), -- FRF .16 Multilink Frame Relay
h323Gatekeeper (164), -- H323 Gatekeeper
h323Proxy (165), -- H323 Voice and Video Proxy
mpls (166), -- MPLS
mfSigLink (167), -- Multi-frequency signaling link
hdsl2 (168), -- High Bit-Rate DSL - 2nd generation
shdsl (169), -- Multirate HDSL2
ds1FDL (170), -- Facility Data Link 4Kbps on a DS1
pos (171), -- Packet over SONET/SDH Interface
dvbAsiIn (172), -- DVB-ASI Input
dvbAsiOut (173), -- DVB-ASI Output
plc (174), -- Power Line Communtications
nfas (175), -- Non Facility Associated Signaling
tr008 (176), -- TR008
gr303RDT (177), -- Remote Digital Terminal
gr303IDT (178), -- Integrated Digital Terminal
isup (179), -- ISUP
propDocsWirelessMaclayer (180), -- Cisco proprietary Maclayer
propDocsWirelessDownstream (181), -- Cisco proprietary Downstream
propDocsWirelessUpstream (182), -- Cisco proprietary Upstream
hiperlan2 (183), -- HIPERLAN Type 2 Radio Interface
propBWAp2Mp (184), -- PropBroadbandWirelessAccesspt2multipt
-- use of this iftype for IEEE 802.16 WMAN
-- interfaces as per IEEE Std 802.16f is
-- deprecated and ifType 237 should be used instead.
sonetOverheadChannel (185), -- SONET Overhead Channel
digitalWrapperOverheadChannel (186), -- Digital Wrapper
aal2 (187), -- ATM adaptation layer 2
radioMAC (188), -- MAC layer over radio links
atmRadio (189), -- ATM over radio links
imt (190), -- Inter Machine Trunks
mvl (191), -- Multiple Virtual Lines DSL
reachDSL (192), -- Long Reach DSL
frDlciEndPt (193), -- Frame Relay DLCI End Point
atmVciEndPt (194), -- ATM VCI End Point
opticalChannel (195), -- Optical Channel
opticalTransport (196), -- Optical Transport
propAtm (197), -- Proprietary ATM
voiceOverCable (198), -- Voice Over Cable Interface
infiniband (199), -- Infiniband
teLink (200), -- TE Link
q2931 (201), -- Q.2931
virtualTg (202), -- Virtual Trunk Group
sipTg (203), -- SIP Trunk Group
sipSig (204), -- SIP Signaling
docsCableUpstreamChannel (205), -- CATV Upstream Channel
econet (206), -- Acorn Econet
pon155 (207), -- FSAN 155Mb Symetrical PON interface
pon622 (208), -- FSAN622Mb Symetrical PON interface
bridge (209), -- Transparent bridge interface
linegroup (210), -- Interface common to multiple lines
voiceEMFGD (211), -- voice E&M Feature Group D
voiceFGDEANA (212), -- voice FGD Exchange Access North American
voiceDID (213), -- voice Direct Inward Dialing
mpegTransport (214), -- MPEG transport interface
sixToFour (215), -- 6to4 interface (DEPRECATED)
gtp (216), -- GTP (GPRS Tunneling Protocol)
pdnEtherLoop1 (217), -- Paradyne EtherLoop 1
pdnEtherLoop2 (218), -- Paradyne EtherLoop 2
opticalChannelGroup (219), -- Optical Channel Group
homepna (220), -- HomePNA ITU-T G.989
gfp (221), -- Generic Framing Procedure (GFP)
ciscoISLvlan (222), -- Layer 2 Virtual LAN using Cisco ISL
actelisMetaLOOP (223), -- Acteleis proprietary MetaLOOP High Speed Link
fcipLink (224), -- FCIP Link
rpr (225), -- Resilient Packet Ring Interface Type
qam (226), -- RF Qam Interface
lmp (227), -- Link Management Protocol
cblVectaStar (228), -- Cambridge Broadband Networks Limited VectaStar
docsCableMCmtsDownstream (229), -- CATV Modular CMTS Downstream Interface
adsl2 (230), -- Asymmetric Digital Subscriber Loop Version 2
-- (DEPRECATED/OBSOLETED - please use adsl2plus 238 instead)
macSecControlledIF (231), -- MACSecControlled
macSecUncontrolledIF (232), -- MACSecUncontrolled
aviciOpticalEther (233), -- Avici Optical Ethernet Aggregate
atmbond (234), -- atmbond
voiceFGDOS (235), -- voice FGD Operator Services
mocaVersion1 (236), -- MultiMedia over Coax Alliance (MoCA) Interface
-- as documented in information provided privately to IANA
ieee80216WMAN (237), -- IEEE 802.16 WMAN interface
adsl2plus (238), -- Asymmetric Digital Subscriber Loop Version 2,
-- Version 2 Plus and all variants
dvbRcsMacLayer (239), -- DVB-RCS MAC Layer
dvbTdm (240), -- DVB Satellite TDM
dvbRcsTdma (241), -- DVB-RCS TDMA
x86Laps (242), -- LAPS based on ITU-T X.86/Y.1323
wwanPP (243), -- 3GPP WWAN
wwanPP2 (244), -- 3GPP2 WWAN
voiceEBS (245), -- voice P-phone EBS physical interface
ifPwType (246), -- Pseudowire interface type
ilan (247), -- Internal LAN on a bridge per IEEE 802.1ap
pip (248), -- Provider Instance Port on a bridge per IEEE 802.1ah PBB
aluELP (249), -- Alcatel-Lucent Ethernet Link Protection
gpon (250), -- Gigabit-capable passive optical networks (G-PON) as per ITU-T G.948
vdsl2 (251), -- Very high speed digital subscriber line Version 2 (as per ITU-T Recommendation G.993.2)
capwapDot11Profile (252), -- WLAN Profile Interface
capwapDot11Bss (253), -- WLAN BSS Interface
capwapWtpVirtualRadio (254), -- WTP Virtual Radio Interface
bits (255), -- bitsport
docsCableUpstreamRfPort (256), -- DOCSIS CATV Upstream RF Port
cableDownstreamRfPort (257), -- CATV downstream RF port
vmwareVirtualNic (258), -- VMware Virtual Network Interface
ieee802154 (259), -- IEEE 802.15.4 WPAN interface
otnOdu (260), -- OTN Optical Data Unit
otnOtu (261), -- OTN Optical channel Transport Unit
ifVfiType (262), -- VPLS Forwarding Instance Interface Type
g9981 (263), -- G.998.1 bonded interface
g9982 (264), -- G.998.2 bonded interface
g9983 (265), -- G.998.3 bonded interface
aluEpon (266), -- Ethernet Passive Optical Networks (E-PON)
aluEponOnu (267), -- EPON Optical Network Unit
aluEponPhysicalUni (268), -- EPON physical User to Network interface
aluEponLogicalLink (269), -- The emulation of a point-to-point link over the EPON layer
aluGponOnu (270), -- GPON Optical Network Unit
aluGponPhysicalUni (271), -- GPON physical User to Network interface
vmwareNicTeam (272), -- VMware NIC Team
docsOfdmDownstream (277), -- CATV Downstream OFDM interface
docsOfdmaUpstream (278), -- CATV Upstream OFDMA interface
gfast (279), -- G.fast port
sdci (280), -- SDCI (IO-Link)
xboxWireless (281), -- Xbox wireless
fastdsl (282), -- FastDSL
docsCableScte55d1FwdOob (283), -- Cable SCTE 55-1 OOB Forward Channel
docsCableScte55d1RetOob (284), -- Cable SCTE 55-1 OOB Return Channel
docsCableScte55d2DsOob (285), -- Cable SCTE 55-2 OOB Downstream Channel
docsCableScte55d2UsOob (286), -- Cable SCTE 55-2 OOB Upstream Channel
docsCableNdf (287), -- Cable Narrowband Digital Forward
docsCableNdr (288), -- Cable Narrowband Digital Return
ptm (289), -- Packet Transfer Mode
ghn (290), -- G.hn port
otnOtsi (291), -- Optical Tributary Signal
otnOtuc (292), -- OTN OTUCn
otnOduc (293), -- OTN ODUC
otnOtsig (294), -- OTN OTUC Signal
microwaveCarrierTermination (295), -- air interface of a single microwave carrier
microwaveRadioLinkTerminal (296), -- radio link interface for one or several aggregated microwave carriers
ieee8021axDrni (297), -- IEEE 802.1AX Distributed Resilient Network Interface
ax25 (298), -- AX.25 network interfaces
ieee19061nanocom (299) -- Nanoscale and Molecular Communication
}
IANAtunnelType ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"The encapsulation method used by a tunnel. The value
direct indicates that a packet is encapsulated
directly within a normal IP header, with no
intermediate header, and unicast to the remote tunnel
endpoint (e.g., an RFC 2003 IP-in-IP tunnel, or an RFC
1933 IPv6-in-IPv4 tunnel). The value minimal indicates
that a Minimal Forwarding Header (RFC 2004) is
inserted between the outer header and the payload
packet. The value UDP indicates that the payload
packet is encapsulated within a normal UDP packet
(e.g., RFC 1234).
The values sixToFour, sixOverFour, and isatap
indicates that an IPv6 packet is encapsulated directly
within an IPv4 header, with no intermediate header,
and unicast to the destination determined by the 6to4,
6over4, or ISATAP protocol.
The remaining protocol-specific values indicate that a
header of the protocol of that name is inserted
between the outer header and the payload header.
The IP Tunnel MIB [RFC4087] is designed to manage
tunnels of any type over IPv4 and IPv6 networks;
therefore, it already supports IP-in-IP tunnels.
But in a DS-Lite scenario, the tunnel type is
point-to-multipoint IP-in-IP tunnels. The direct(2)
defined in the IP Tunnel MIB only supports point-to-point
tunnels. So, it needs to define a new tunnel type for
DS-Lite.
The assignment policy for IANAtunnelType values is
identical to the policy for assigning IANAifType
values."
SYNTAX INTEGER {
other(1), -- none of the following
direct(2), -- no intermediate header
gre(3), -- GRE encapsulation
minimal(4), -- Minimal encapsulation
l2tp(5), -- L2TP encapsulation
pptp(6), -- PPTP encapsulation
l2f(7), -- L2F encapsulation
udp(8), -- UDP encapsulation
atmp(9), -- ATMP encapsulation
msdp(10), -- MSDP encapsulation
sixToFour(11), -- 6to4 encapsulation
sixOverFour(12), -- 6over4 encapsulation
isatap(13), -- ISATAP encapsulation
teredo(14), -- Teredo encapsulation
ipHttps(15), -- IPHTTPS
softwireMesh(16), -- softwire mesh tunnel
dsLite(17), -- DS-Lite tunnel
aplusp(18) -- A+P encapsulation
}
END

6858
priv/mibs/IEEE-802DOT17-RPR-MIB Normal file
View file

File diff suppressed because it is too large Load diff

2334
priv/mibs/IEEE8021-BRIDGE-MIB Normal file
View file

File diff suppressed because it is too large Load diff

3707
priv/mibs/IEEE8021-CFM-MIB Normal file
View file

File diff suppressed because it is too large Load diff

2990
priv/mibs/IEEE8021-CFMD8-MIB Normal file
View file

File diff suppressed because it is too large Load diff

1919
priv/mibs/IEEE8021-PAE-MIB Normal file
View file

File diff suppressed because it is too large Load diff

2519
priv/mibs/IEEE8021-Q-BRIDGE-MIB Normal file
View file

File diff suppressed because it is too large Load diff

1954
priv/mibs/IEEE8021-SECY-MIB Normal file
View file

File diff suppressed because it is too large Load diff

597
priv/mibs/IEEE8021-TC-MIB Normal file
View file

@ -0,0 +1,597 @@
IEEE8021-TC-MIB DEFINITIONS ::= BEGIN
-- =============================================================
-- TEXTUAL-CONVENTIONs MIB for IEEE 802.1
-- =============================================================
IMPORTS
MODULE-IDENTITY, Unsigned32, org
FROM SNMPv2-SMI -- RFC 2578
TEXTUAL-CONVENTION
FROM SNMPv2-TC; -- RFC 2579
ieee8021TcMib MODULE-IDENTITY
LAST-UPDATED "201202150000Z" -- February 15, 2012
ORGANIZATION "IEEE 802.1 Working Group"
CONTACT-INFO
" WG-URL: http://grouper.ieee.org/groups/802/1/index.html
WG-EMail: stds-802-1@ieee.org
Contact: David Levi
Postal: C/O IEEE 802.1 Working Group
IEEE Standards Association
445 Hoes Lane
P.O. Box 1331
Piscataway
NJ 08855-1331
USA
E-mail: STDS-802-1-L@LISTSERV.IEEE.ORG
Contact: Kevin Nolish
Postal: C/O IEEE 802.1 Working Group
IEEE Standards Association
445 Hoes Lane
P.O. Box 1331
Piscataway
NJ 08855-1331
USA
E-mail: STDS-802-1-L@LISTSERV.IEEE.ORG"
DESCRIPTION
"Textual conventions used throughout the various IEEE 802.1 MIB
modules.
Unless otherwise indicated, the references in this MIB
module are to IEEE 802.1Q-2011.
Copyright (C) IEEE.
This version of this MIB module is part of IEEE802.1Q;
see the draft itself for full legal notices."
REVISION "201202150000Z" -- February 15, 2012
DESCRIPTION
"Modified IEEE8021BridgePortType textual convention to
include stationFacingBridgePort,
uplinkAccessPort, and uplinkRelayPort types."
REVISION "201108230000Z" -- August 23, 2011
DESCRIPTION
"Modified textual conventions to support the IEEE 802.1
MIBs for PBB-TE Infrastructure Protection Switching."
REVISION "201104060000Z" -- April 6, 2011
DESCRIPTION
"Modified textual conventions to support Remote Customer
Service Interfaces."
REVISION "201102270000Z" -- February 27, 2011
DESCRIPTION
"Minor edits to contact information etc. as part of
2011 revision of IEEE Std 802.1Q."
REVISION "200811180000Z" -- November 18, 2008
DESCRIPTION
"Added textual conventions needed to support the IEEE 802.1
MIBs for PBB-TE. Additionally, some textual conventions were
modified for the same reason."
REVISION "200810150000Z" -- October 15, 2008
DESCRIPTION
"Initial version."
::= { org ieee(111) standards-association-numbers-series-standards(2)
lan-man-stds(802) ieee802dot1(1) 1 1 }
ieee802dot1mibs OBJECT IDENTIFIER
::= { org ieee(111) standards-association-numbers-series-standards(2)
lan-man-stds(802) ieee802dot1(1) 1 }
-- =============================================================
-- Textual Conventions
-- =============================================================
IEEE8021PbbComponentIdentifier ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d"
STATUS current
DESCRIPTION
"The component identifier is used to distinguish between the
multiple virtual bridge instances within a PB or PBB. Each
virtual bridge instance is called a component. In simple
situations where there is only a single component the default
value is 1. The component is identified by a component
identifier unique within the BEB and by a MAC address unique
within the PBBN. Each component is associated with a Backbone
Edge Bridge (BEB) Configuration managed object."
REFERENCE "12.3 l)"
SYNTAX Unsigned32 (1..4294967295)
IEEE8021PbbComponentIdentifierOrZero ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d"
STATUS current
DESCRIPTION
"The component identifier is used to distinguish between the
multiple virtual bridge instances within a PB or PBB. In simple
situations where there is only a single component the default
value is 1. The component is identified by a component
identifier unique within the BEB and by a MAC address unique
within the PBBN. Each component is associated with a Backbone
Edge Bridge (BEB) Configuration managed object.
The special value '0' means 'no component identifier'. When
this TC is used as the SYNTAX of an object, that object must
specify the exact meaning for this value."
REFERENCE "12.3 l)"
SYNTAX Unsigned32 (0 | 1..4294967295)
IEEE8021PbbServiceIdentifier ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d"
STATUS current
DESCRIPTION
"The service instance identifier is used at the Customer
Backbone Port of a PBB to distinguish a service instance
(Local-SID). If the Local-SID field is supported, it is
used to perform a bidirectional 1:1 mapping between the
Backbone I-SID and the Local-SID. If the Local-SID field
is not supported, the Local-SID value is the same as the
Backbone I-SID value."
REFERENCE "12.16.3, 12.16.5"
SYNTAX Unsigned32 (256..16777214)
IEEE8021PbbServiceIdentifierOrUnassigned ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d"
STATUS current
DESCRIPTION
"The service instance identifier is used at the Customer
Backbone Port of a PBB to distinguish a service instance
(Local-SID). If the Local-SID field is supported, it is
used to perform a bidirectional 1:1 mapping between the
Backbone I-SID and the Local-SID. If the Local-SID field
is not supported, the Local-SID value is the same as the
Backbone I-SID value.
The special value of 1 indicates an unassigned I-SID."
REFERENCE "12.16.3, 12.16.5"
SYNTAX Unsigned32 (1|256..16777214)
IEEE8021PbbIngressEgress ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"A 2 bit selector which determines if frames on this VIP may
ingress to the PBBN but not egress the PBBN, egress to the
PBBN but not ingress the PBBN, or both ingress and egress
the PBBN."
REFERENCE "12.16.3, 12.16.5, 12.16.6"
SYNTAX BITS {
ingress(0),
egress(1)
}
IEEE8021PriorityCodePoint ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"Bridge ports may encode or decode the PCP value of the
frames that traverse the port. This textual convention
names the possible encoding and decoding schemes that
the port may use. The priority and drop_eligible
parameters are encoded in the Priority Code Point (PCP)
field of the VLAN tag using the Priority Code Point
Encoding Table for the Port, and they are decoded from
the PCP using the Priority Code Point Decoding Table."
REFERENCE "12.6.2.6"
SYNTAX INTEGER {
codePoint8p0d(1),
codePoint7p1d(2),
codePoint6p2d(3),
codePoint5p3d(4)
}
IEEE8021BridgePortNumber ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d"
STATUS current
DESCRIPTION
"An integer that uniquely identifies a bridge port, as
specified in 17.3.2.2 of IEEE 802.1ap.
This value is used within the spanning tree
protocol to identify this port to neighbor bridges."
REFERENCE "17.3.2.2"
SYNTAX Unsigned32 (1..65535)
IEEE8021BridgePortNumberOrZero ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d"
STATUS current
DESCRIPTION
"An integer that uniquely identifies a bridge port, as
specified in 17.3.2.2 of IEEE 802.1ap. The value 0
means no port number, and this must be clarified in the
DESCRIPTION clause of any object defined using this
TEXTUAL-CONVENTION."
REFERENCE "17.3.2.2"
SYNTAX Unsigned32 (0..65535)
IEEE8021BridgePortType ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"A port type. The possible port types are:
customerVlanPort(2) - Indicates a port is a C-tag
aware port of an enterprise VLAN aware bridge.
providerNetworkPort(3) - Indicates a port is an S-tag
aware port of a Provider Bridge or Backbone Edge
Bridge used for connections within a PBN or PBBN.
customerNetworkPort(4) - Indicates a port is an S-tag
aware port of a Provider Bridge or Backbone Edge
Bridge used for connections to the exterior of a
PBN or PBBN.
customerEdgePort(5) - Indicates a port is a C-tag
aware port of a Provider Bridge used for connections
to the exterior of a PBN or PBBN.
customerBackbonePort(6) - Indicates a port is a I-tag
aware port of a Backbone Edge Bridge's B-component.
virtualInstancePort(7) - Indicates a port is a virtual
S-tag aware port within a Backbone Edge Bridge's
I-component which is responsible for handling
S-tagged traffic for a specific backbone service
instance.
dBridgePort(8) - Indicates a port is a VLAN-unaware
member of an 802.1D bridge.
remoteCustomerAccessPort (9) - Indicates a port is an
S-tag aware port of a Provider Bridge used for
connections to remote customer interface LANs
through another PBN.
stationFacingBridgePort (10) - Indicates a port of a
Bridge that supports the EVB status parameters
(6.6.5) with an EVBMode parameter value of
EVB Bridge.
uplinkAccessPort (11) - Indicates a port on a
Port-mapping S-VLAN component that connects an EVB
Bridge with an EVB station.
uplinkRelayPort (12) - Indicates a port of an edge relay
that supports the EVB status parameters (6.6.5)
with an EVBMode parameter value of EVB station."
REFERENCE "12.16.1.1.3 h4), 12.16.2.1/2,
12.13.1.1, 12.13.1.2, 12.15.2.1, 12.15.2.2"
SYNTAX INTEGER {
none(1),
customerVlanPort(2),
providerNetworkPort(3),
customerNetworkPort(4),
customerEdgePort(5),
customerBackbonePort(6),
virtualInstancePort(7),
dBridgePort(8),
remoteCustomerAccessPort(9),
stationFacingBridgePort(10),
uplinkAccessPort(11),
uplinkRelayPort(12)
}
IEEE8021VlanIndex ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d"
STATUS current
DESCRIPTION
"A value used to index per-VLAN tables: values of 0 and
4095 are not permitted. If the value is between 1 and
4094 inclusive, it represents an IEEE 802.1Q VLAN-ID with
global scope within a given bridged domain (see VlanId
textual convention). If the value is greater than 4095,
then it represents a VLAN with scope local to the
particular agent, i.e., one without a global VLAN-ID
assigned to it. Such VLANs are outside the scope of
IEEE 802.1Q, but it is convenient to be able to manage them
in the same way using this MIB."
REFERENCE "9.6"
SYNTAX Unsigned32 (1..4094|4096..4294967295)
IEEE8021VlanIndexOrWildcard ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d"
STATUS current
DESCRIPTION
"A value used to index per-VLAN tables. The value 0 is not
permitted, while the value 4095 represents a 'wildcard'
value. An object whose SYNTAX is IEEE8021VlanIndexOrWildcard
must specify in its DESCRIPTION the specific meaning of the
wildcard value. If the value is between 1 and
4094 inclusive, it represents an IEEE 802.1Q VLAN-ID with
global scope within a given bridged domain (see VlanId
textual convention). If the value is greater than 4095,
then it represents a VLAN with scope local to the
particular agent, i.e., one without a global VLAN-ID
assigned to it. Such VLANs are outside the scope of
IEEE 802.1Q, but it is convenient to be able to manage them
in the same way using this MIB."
REFERENCE "9.6"
SYNTAX Unsigned32 (1..4294967295)
IEEE8021MstIdentifier ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d"
STATUS current
DESCRIPTION
"In an MSTP Bridge, an MSTID, i.e., a value used to identify
a spanning tree (or MST) instance. In the PBB-TE environment
the value 4094 is used to identify VIDs managed by the PBB-TE
procedures."
SYNTAX Unsigned32 (1..4094)
IEEE8021ServiceSelectorType ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"A value that represents a type (and thereby the format)
of a IEEE8021ServiceSelectorValue. The value can be one of
the following:
ieeeReserved(0) Reserved for definition by IEEE 802.1
recommend to not use zero unless
absolutely needed.
vlanId(1) 12-Bit identifier as described in IEEE802.1Q.
isid(2) 24-Bit identifier as described in IEEE802.1ah.
tesid(3) 32 Bit identifier as described below.
segid(4) 32 Bit identifier as described below.
ieeeReserved(xx) Reserved for definition by IEEE 802.1
xx values can be [5..7].
To support future extensions, the IEEE8021ServiceSelectorType
textual convention SHOULD NOT be sub-typed in object type
definitions. It MAY be sub-typed in compliance statements in
order to require only a subset of these address types for a
compliant implementation.
The tesid is used as a service selector for MAs that are present
in bridges that implement PBB-TE functionality. A selector of
this type is interpreted as a 32 bit unsigned value of type
IEEE8021PbbTeTSidId. This type is used to index the
Ieee8021PbbTeTeSidTable to find the ESPs which comprise the TE
Service Instance named by this TE-SID value.
The segid is used as a service selector for MAs that are present
in bridges that implement IPS functionality. A selector of
this type is interpreted as a 32 bit unsigned value of type
IEEE8021TeipsSegid. This type is used to index the
Ieee8021TeipsSegTable to find the SMPs which comprise the
Infrastructure Segment named by this segid value.
Implementations MUST ensure that IEEE8021ServiceSelectorType
objects and any dependent objects (e.g.,
IEEE8021ServiceSelectorValue objects) are consistent. An
inconsistentValue error MUST be generated if an attempt to
change an IEEE8021ServiceSelectorType object would, for
example, lead to an undefined IEEE8021ServiceSelectorValue value."
SYNTAX INTEGER {
vlanId(1),
isid(2),
tesid(3),
segid(4)
}
IEEE8021ServiceSelectorValueOrNone ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d"
STATUS current
DESCRIPTION
"An integer that uniquely identifies a generic MAC service,
or none. Examples of service selectors are a VLAN-ID
(IEEE 802.1Q) and an I-SID (IEEE 802.1ah).
An IEEE8021ServiceSelectorValueOrNone value is always
interpreted within the context of an
IEEE8021ServiceSelectorType value. Every usage of the
IEEE8021ServiceSelectorValueOrNone textual convention is
required to specify the IEEE8021ServiceSelectorType object
that provides the context. It is suggested that the
IEEE8021ServiceSelectorType object be logically registered
before the object(s) that use the
IEEE8021ServiceSelectorValueOrNone textual convention, if
they appear in the same logical row.
The value of an IEEE8021ServiceSelectorValueOrNone object
must always be consistent with the value of the associated
IEEE8021ServiceSelectorType object. Attempts to set an
IEEE8021ServiceSelectorValueOrNone object to a value
inconsistent with the associated
IEEE8021ServiceSelectorType must fail with an
inconsistentValue error.
The special value of zero is used to indicate that no
service selector is present or used. This can be used in
any situation where an object or a table entry MUST either
refer to a specific service, or not make a selection.
Note that a MIB object that is defined using this
TEXTUAL-CONVENTION SHOULD clarify the meaning of
'no service' (i.e., the special value 0), as well as the
maximum value (i.e., 4094, for a VLAN ID)."
SYNTAX Unsigned32 (0 | 1..4294967295)
IEEE8021ServiceSelectorValue ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d"
STATUS current
DESCRIPTION
"An integer that uniquely identifies a generic MAC service.
Examples of service selectors are a VLAN-ID (IEEE 802.1Q)
and an I-SID (IEEE 802.1ah).
An IEEE8021ServiceSelectorValue value is always interpreted
within the context of an IEEE8021ServiceSelectorType value.
Every usage of the IEEE8021ServiceSelectorValue textual
convention is required to specify the
IEEE8021ServiceSelectorType object that provides the context.
It is suggested that the IEEE8021ServiceSelectorType object
be logically registered before the object(s) that use the
IEEE8021ServiceSelectorValue textual convention, if they
appear in the same logical row.
The value of an IEEE8021ServiceSelectorValue object must
always be consistent with the value of the associated
IEEE8021ServiceSelectorType object. Attempts to set an
IEEE8021ServiceSelectorValue object to a value inconsistent
with the associated IEEE8021ServiceSelectorType must fail
with an inconsistentValue error.
Note that a MIB object that is defined using this
TEXTUAL-CONVENTION SHOULD clarify the
maximum value (i.e., 4094, for a VLAN ID)."
SYNTAX Unsigned32 (1..4294967295)
IEEE8021PortAcceptableFrameTypes ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"Acceptable frame types on a port."
REFERENCE "12.10.1.3, 12.13.3.3, 12.13.3.4"
SYNTAX INTEGER {
admitAll(1),
admitUntaggedAndPriority(2),
admitTagged(3)
}
IEEE8021PriorityValue ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d"
STATUS current
DESCRIPTION
"An 802.1Q user priority value."
REFERENCE "12.13.3.3"
SYNTAX Unsigned32 (0..7)
IEEE8021PbbTeProtectionGroupId ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d"
STATUS current
DESCRIPTION
"The PbbTeProtectionGroupId identifier is used to distinguish
protection group instances present in the B Component of
an IB-BEB."
REFERENCE "12.19.2"
SYNTAX Unsigned32 (1..429467295)
IEEE8021PbbTeEsp ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"This textual convention is used to represent the logical
components that comprise the 3-tuple that identifies an
Ethernet Switched Path. The 3-tuple consists of a
destination MAC address, a source MAC address and a VID.
Bytes (1..6) of this textual convention contain the
ESP-MAC-DA, bytes (7..12) contain the ESP-MAC-SA, and bytes
(13..14) contain the ESP-VID."
REFERENCE "802.1Qay 3.2"
SYNTAX OCTET STRING ( SIZE(14))
IEEE8021PbbTeTSidId ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d"
STATUS current
DESCRIPTION
"This textual convention is used to represent an identifier
that refers to a TE Service Instance. Note that, internally
a TE-SID is implementation dependent. This textual convention
defines the external representation of TE-SID values."
REFERENCE
"802.1Qay 3.11"
SYNTAX Unsigned32 (1..42947295)
IEEE8021PbbTeProtectionGroupConfigAdmin ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"This textual convention is used to represent administrative
commands that can be issued to a protection group. The value
noAdmin(1) is used to indicate that no administrative action
is to be performed."
REFERENCE "26.10.3.3.5
26.10.3.3.6
26.10.3.3.7
12.19.2.3.2"
SYNTAX INTEGER {
clear(1),
lockOutProtection(2),
forceSwitch(3),
manualSwitchToProtection(4),
manualSwitchToWorking(5)
}
IEEE8021PbbTeProtectionGroupActiveRequests ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"This textual convention is used to represent the status of
active requests within a protection group."
REFERENCE
"12.19.2.1.3 d)"
SYNTAX INTEGER {
noRequest(1),
loP(2),
fs(3),
pSFH(4),
wSFH(5),
manualSwitchToProtection(6),
manualSwitchToWorking(7)
}
IEEE8021TeipsIpgid ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d"
STATUS current
DESCRIPTION
"The TEIPS IPG identifier is used to distinguish
IPG instances present in a PBB."
REFERENCE "12.24.1.1.3 a)"
SYNTAX Unsigned32 (1..429467295)
IEEE8021TeipsSegid ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d"
STATUS current
DESCRIPTION
"This textual convention is used to represent an
identifier that refers to an Infrastructure Segment.
Note that, internally a SEG-ID implementation
dependent. This textual convention defines the
external representation of SEG-ID values."
REFERENCE
"26.11.1"
SYNTAX Unsigned32 (1..42947295)
IEEE8021TeipsSmpid ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"This textual convention is used to represent the logical
components that comprise the 3-tuple that identifies a
Segment Monitoring Path (SMP). The 3-tuple consists of a
destination MAC address, a source MAC address and a VID.
Bytes (1..6) of this textual convention contain the
SMP-MAC-DA, bytes (7..12) contain the SMP-MAC-SA, and bytes
(13..14) contain the SMP-VID."
REFERENCE "26.11.1"
SYNTAX OCTET STRING ( SIZE(14))
IEEE8021TeipsIpgConfigAdmin ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"This textual convention is used to represent administrative
commands that can be issued to an IPG. The value
clear(1) is used to indicate that no administrative action
is to be performed."
REFERENCE "12.24.2.1.3 h)"
SYNTAX INTEGER {
clear(1),
lockOutProtection(2),
forceSwitch(3),
manualSwitchToProtection(4),
manualSwitchToWorking(5)
}
IEEE8021TeipsIpgConfigActiveRequests ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"This textual convention is used to represent the status of
active requests within an IPG."
REFERENCE
"12.24.2.1.3 d)"
SYNTAX INTEGER {
noRequest(1),
loP(2),
fs(3),
pSFH(4),
wSFH(5),
manualSwitchToProtection(6),
manualSwitchToWorking(7)
}
END

3146
priv/mibs/IEEE802171-CFM-MIB Normal file
View file

File diff suppressed because it is too large Load diff

1400
priv/mibs/IEEE8023-LAG-MIB Normal file
View file

File diff suppressed because it is too large Load diff

2977
priv/mibs/IEEE802dot11-MIB Normal file
View file

File diff suppressed because it is too large Load diff

1814
priv/mibs/IF-MIB Normal file
View file

File diff suppressed because it is too large Load diff

598
priv/mibs/IGMP-MIB Normal file
View file

@ -0,0 +1,598 @@
-- *****************************************************************
-- IGMP-MIB.my: IGMP MIB file
--
-- November 1994.
--
-- Copyright (c) 1994-1997 by cisco Systems, Inc.
-- All rights reserved.
--
-- *****************************************************************
-- This mib was extracted from draft-ietf-idmr-igmp-mib-00.txt.
IGMP-MIB DEFINITIONS ::= BEGIN
IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, experimental, Counter32, Gauge32,
Integer32, IpAddress, TimeTicks FROM SNMPv2-SMI
RowStatus, TruthValue FROM SNMPv2-TC
MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF;
igmpMIB MODULE-IDENTITY
LAST-UPDATED "9712180000Z"
ORGANIZATION "IETF IDMR Working Group."
CONTACT-INFO
" Keith McCloghrie
Cisco Systems, Inc.
170 West Tasman Drive
San Jose, CA 9513401706
US
Phone: +1 408 526 5260
EMail: kzm@cisco.com"
DESCRIPTION
"The MIB module for IGMP Management."
REVISION "9508150000Z"
DESCRIPTION
"Added more contact information."
REVISION "9701060000Z"
DESCRIPTION
"Update per draft-ietf-idmr-igmp-mib-04.txt."
REVISION "9712180000Z"
DESCRIPTION
"Update per draft-ietf-idmr-igmp-mib-05.txt."
::= { experimental 59 }
igmpMIBObjects OBJECT IDENTIFIER ::= { igmpMIB 1 }
igmp OBJECT IDENTIFIER ::= { igmpMIBObjects 1 }
--
-- The IGMP Interface Table
--
igmpInterfaceTable OBJECT-TYPE
SYNTAX SEQUENCE OF IgmpInterfaceEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The (conceptual) table listing the interfaces on
which IGMP is enabled."
::= { igmp 1 }
igmpInterfaceEntry OBJECT-TYPE
SYNTAX IgmpInterfaceEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry (conceptual row) representing an
interface on which IGMP is enabled."
INDEX { igmpInterfaceIfIndex }
::= { igmpInterfaceTable 1 }
IgmpInterfaceEntry ::= SEQUENCE {
igmpInterfaceIfIndex Integer32 (0..2147483647),
igmpInterfaceQueryInterval Integer32,
igmpInterfaceStatus RowStatus,
igmpInterfaceVersion INTEGER,
igmpInterfaceQuerier IpAddress,
igmpInterfaceQueryMaxResponseTime Integer32,
igmpInterfaceQuerierPresentTimeout Integer32, -- deprecated
igmpInterfaceLeaveEnabled TruthValue, -- deprecated
igmpInterfaceVersion1QuerierTimer Integer32,
igmpInterfaceWrongVersionQueries Counter32,
igmpInterfaceJoins Counter32,
igmpInterfaceLeaves Counter32, -- deprecated
igmpInterfaceGroups Gauge32,
igmpInterfaceRobustness Integer32
}
igmpInterfaceIfIndex OBJECT-TYPE
SYNTAX Integer32 (0..2147483647)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The interface for which IGMP is enabled."
::= { igmpInterfaceEntry 1 }
igmpInterfaceQueryInterval OBJECT-TYPE
SYNTAX Integer32
UNITS "seconds"
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The frequency at which IGMP Host-Query packets
are transmitted on this interface."
DEFVAL { 60 }
::= { igmpInterfaceEntry 2 }
igmpInterfaceStatus OBJECT-TYPE
SYNTAX RowStatus
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The activation of a row enables IGMP on the
interface. The destruction of a row disables IGMP
on the interface."
::= { igmpInterfaceEntry 3 }
igmpInterfaceVersion OBJECT-TYPE
SYNTAX INTEGER { version1 (1), version2 (2) }
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The version of IGMP which is running on this interface.
This object can be used to configure a router capable of
running either value. For IGMP to function correctly, all
routers on a LAN must be configured to run the same version
of IGMP on that LAN."
DEFVAL { version2 }
::= { igmpInterfaceEntry 4 }
igmpInterfaceQuerier OBJECT-TYPE
SYNTAX IpAddress
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The address of the IGMP Querier on the IP subnet to which
this interface is attached."
::= { igmpInterfaceEntry 5 }
igmpInterfaceQueryMaxResponseTime OBJECT-TYPE
SYNTAX Integer32
UNITS "seconds"
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The maximum query response time advertised in IGMPv2
queries on this interface."
DEFVAL { 10 }
::= { igmpInterfaceEntry 6 }
igmpInterfaceQuerierPresentTimeout OBJECT-TYPE
SYNTAX Integer32
UNITS "seconds"
MAX-ACCESS read-create
STATUS deprecated
DESCRIPTION
"A timeout interval. If no IGMPv2 queries are heard on this
interface within this timeout interval, the local router
will take over the Querier on the IP subnet to which this
interface is attached. This object is now deprecated,
since its value can be derived from
igmpInterfaceRobustness."
DEFVAL { 255 }
::= { igmpInterfaceEntry 7 }
igmpInterfaceLeaveEnabled OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-create
STATUS deprecated
DESCRIPTION
"An indication of whether the processing of IGMPv2 Leave
messages is enabled on this interface. This object is
now deprecated since it must be true when
igmpInterfaceVersion is version2, and must be false when
it is version1 to comply with the IGMP specfication."
DEFVAL { true }
::= { igmpInterfaceEntry 8 }
igmpInterfaceVersion1QuerierTimer OBJECT-TYPE
SYNTAX Integer32
UNITS "seconds"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The time remaining until the host assumes that there are no
IGMPv1 routers present on the interface. While this is
non-zero, the host will reply to all queries with version 1
membership reports."
::= { igmpInterfaceEntry 9 }
igmpInterfaceWrongVersionQueries OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of queries received whose IGMP version does not
match igmpInterfaceVersion. IGMP requires that all routers
on a LAN be configured to run the same version of IGMP.
Thus, if any queries are received with the wrong version,
this indicates a configuration error."
::= { igmpInterfaceEntry 10 }
igmpInterfaceJoins OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of times a group membership has been added on
this interface; that is, the number of times an entry for
this interface has been added to the Cache Table. This
object gives an indication of the amount of IGMP activity
over time."
::= { igmpInterfaceEntry 11 }
igmpInterfaceLeaves OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS deprecated
DESCRIPTION
"The number of times a group membership has been removed
from this interface; that is, the number of times an entry
for this interface has been deleted from the Cache Table.
This object is deprecated since its value cannot be
usefully compared with igmpInterfaceJoins to get the
number of groups joined. Instead, igmpInterfaceGroups
gives the number of groups joined, which may be compared
with igmpInterfaceJoins to derive the number of leaves."
::= { igmpInterfaceEntry 12 }
igmpInterfaceGroups OBJECT-TYPE
SYNTAX Gauge32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The current number of entries for this interface in
the Cache Table."
::= { igmpInterfaceEntry 13 }
igmpInterfaceRobustness OBJECT-TYPE
SYNTAX Integer32
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The Robustness Variable allows tuning for the expected
packet loss on a subnet. If a subnet is expected to be
lossy, the Robustness Variable may be increased. IGMP
is robust to (Robustness Variable-1) packet losses."
DEFVAL { 2 }
::= { igmpInterfaceEntry 14 }
--
-- The IGMP Cache Table
--
igmpCacheTable OBJECT-TYPE
SYNTAX SEQUENCE OF IgmpCacheEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The (conceptual) table listing the IP multicast
groups for which there are members on a particular
interface."
::= { igmp 2 }
igmpCacheEntry OBJECT-TYPE
SYNTAX IgmpCacheEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry (conceptual row) in the igmpCacheTable."
INDEX { igmpCacheAddress, igmpCacheIfIndex }
::= { igmpCacheTable 1 }
IgmpCacheEntry ::= SEQUENCE {
igmpCacheAddress IpAddress,
igmpCacheIfIndex Integer32 (0..2147483647),
igmpCacheSelf TruthValue,
igmpCacheLastReporter IpAddress,
igmpCacheUpTime TimeTicks,
igmpCacheExpiryTime TimeTicks,
igmpCacheStatus RowStatus,
igmpCacheVersion1HostTimer Integer32
}
igmpCacheAddress OBJECT-TYPE
SYNTAX IpAddress
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The IP multicast group address for which this
entry contains information."
::= { igmpCacheEntry 1 }
igmpCacheIfIndex OBJECT-TYPE
SYNTAX Integer32 (0..2147483647)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The interface for which this entry contains
information for an IP multicast group address."
::= { igmpCacheEntry 2 }
igmpCacheSelf OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"An indication of whether the local system is a
member of this group address on this interface."
DEFVAL { true }
::= { igmpCacheEntry 3 }
igmpCacheLastReporter OBJECT-TYPE
SYNTAX IpAddress
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The IP address of the source of the last
membership report received for this IP Multicast
group address on this interface. If no membership
report has been received, this object has the
value 0.0.0.0."
::= { igmpCacheEntry 4 }
igmpCacheUpTime OBJECT-TYPE
SYNTAX TimeTicks
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The time since the system joined this group
address, or zero if the system is not currently a
member."
::= { igmpCacheEntry 5 }
igmpCacheExpiryTime OBJECT-TYPE
SYNTAX TimeTicks
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The minimum amount of time remaining before this
entry will be aged out."
::= { igmpCacheEntry 6 }
igmpCacheStatus OBJECT-TYPE
SYNTAX RowStatus
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The status of this entry."
::= { igmpCacheEntry 7 }
igmpCacheVersion1HostTimer OBJECT-TYPE
SYNTAX Integer32
UNITS "seconds"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The time remaining until the local router will assume that
there are no longer any IGMP version 1 members on the IP
subnet attached to this interface. Upon hearing any IGMPv1
Membership Report, this value is reset to the group
membership timer. While this time remaining is non-zero,
the local router ignores any IGMPv2 Leave messages for this
group that it receives on this interface."
::= { igmpCacheEntry 8 }
-- conformance information
igmpMIBConformance
OBJECT IDENTIFIER ::= { igmpMIB 2 }
igmpMIBCompliances
OBJECT IDENTIFIER ::= { igmpMIBConformance 1 }
igmpMIBGroups OBJECT IDENTIFIER ::= { igmpMIBConformance 2 }
-- compliance statements
igmpV1HostMIBCompliance MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"The compliance statement for hosts running IGMPv1 and
implementing the IGMP MIB."
MODULE -- this module
MANDATORY-GROUPS { igmpBaseMIBGroup }
OBJECT igmpInterfaceStatus
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
::= { igmpMIBCompliances 1 }
igmpV1RouterMIBCompliance MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"The compliance statement for routers running IGMPv1 and
implementing the IGMP MIB."
MODULE -- this module
MANDATORY-GROUPS { igmpBaseMIBGroup,
igmpRouterMIBGroup
}
OBJECT igmpInterfaceStatus
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
::= { igmpMIBCompliances 2 }
igmpV2HostMIBCompliance MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"The compliance statement for hosts running IGMPv2 and
implementing the IGMP MIB."
MODULE -- this module
MANDATORY-GROUPS { igmpBaseMIBGroup,
igmpV2HostMIBGroup
}
OBJECT igmpInterfaceStatus
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
::= { igmpMIBCompliances 3 }
igmpV2RouterMIBCompliance MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"The compliance statement for routers running IGMPv2 and
implementing the IGMP MIB."
MODULE -- this module
MANDATORY-GROUPS { igmpBaseMIBGroup,
igmpRouterMIBGroup,
igmpV2RouterMIBGroup
}
OBJECT igmpInterfaceStatus
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
::= { igmpMIBCompliances 4 }
-- units of conformance
igmpBaseMIBGroup OBJECT-GROUP
OBJECTS { igmpCacheSelf, igmpCacheLastReporter,
igmpCacheStatus, igmpInterfaceStatus
}
STATUS current
DESCRIPTION
"The basic collection of objects providing
management of IGMP version 1 or 2."
::= { igmpMIBGroups 1 }
igmpRouterMIBGroup OBJECT-GROUP
OBJECTS { igmpCacheUpTime, igmpCacheExpiryTime,
igmpInterfaceQueryInterval
}
STATUS current
DESCRIPTION
"A collection of additional objects for management
of IGMP version 1 or 2 in routers."
::= { igmpMIBGroups 2 }
igmpV2HostMIBGroup OBJECT-GROUP
OBJECTS { igmpInterfaceQuerier,
igmpInterfaceVersion1QuerierTimer
}
STATUS current
DESCRIPTION
"A collection of additional objects for management of
IGMP version 2 in hosts."
::= { igmpMIBGroups 3 }
igmpRouterVersion2MIBGroup OBJECT-GROUP
OBJECTS { igmpInterfaceVersion,
igmpInterfaceQueryMaxResponseTime,
igmpInterfaceQuerierPresentTimeout,
igmpInterfaceLeaveEnabled,
igmpInterfaceWrongVersionQueries,
igmpInterfaceJoins,
igmpInterfaceLeaves,
igmpCacheVersion1HostTimer
}
STATUS deprecated
DESCRIPTION
"A collection of additional objects for management
of IGMP version 2 in routers. This group has been
obsoleted by igmpV2RouterMIBGroup."
::= { igmpMIBGroups 4 }
igmpV2RouterMIBGroup OBJECT-GROUP
OBJECTS { igmpInterfaceVersion, igmpInterfaceQuerier,
igmpInterfaceQueryMaxResponseTime,
igmpInterfaceRobustness,
igmpInterfaceWrongVersionQueries,
igmpInterfaceJoins, igmpInterfaceGroups,
igmpCacheVersion1HostTimer
}
STATUS current
DESCRIPTION
"A collection of additional objects for management
of IGMP version 2 in routers."
::= { igmpMIBGroups 5 }
END

511
priv/mibs/IGMP-STD-MIB Normal file
View file

@ -0,0 +1,511 @@
IGMP-STD-MIB DEFINITIONS ::= BEGIN
IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, experimental, Counter32, Gauge32,
Integer32, IpAddress, TimeTicks FROM SNMPv2-SMI
RowStatus, TruthValue FROM SNMPv2-TC
MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF
InterfaceIndexOrZero,
InterfaceIndex FROM IF-MIB;
igmpStdMIB MODULE-IDENTITY
LAST-UPDATED "9909171200Z" -- September 17, 1999
ORGANIZATION "IETF IDMR Working Group."
CONTACT-INFO
" Dave Thaler
Microsoft Corporation
One Microsoft Way
Redmond, WA 98052-6399
US
Phone: +1 425 703 8835
EMail: dthaler@dthaler.microsoft.com"
DESCRIPTION
"The MIB module for IGMP Management."
REVISION "9909171200Z" -- September 17, 1999
DESCRIPTION
"Initial version, published as RFC xxxx (to be filled in by
RFC-Editor)."
-- ::= { mib-2 xx }
::= { experimental 59 } -- $$$ This value to be changed later !!!
-- NOTE TO RFC EDITOR: When this document is published as
-- an RFC, replace XX with IANA-assigned value and delete
-- this comment.
igmpMIBObjects OBJECT IDENTIFIER ::= { igmpStdMIB 1 }
igmp OBJECT IDENTIFIER ::= { igmpMIBObjects 1 }
--
-- The IGMP Interface Table
--
igmpInterfaceTable OBJECT-TYPE
SYNTAX SEQUENCE OF IgmpInterfaceEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The (conceptual) table listing the interfaces on which IGMP
is enabled."
::= { igmp 1 }
igmpInterfaceEntry OBJECT-TYPE
SYNTAX IgmpInterfaceEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry (conceptual row) representing an interface on
which IGMP is enabled."
INDEX { igmpInterfaceIfIndex }
::= { igmpInterfaceTable 1 }
IgmpInterfaceEntry ::= SEQUENCE {
igmpInterfaceIfIndex InterfaceIndex,
igmpInterfaceQueryInterval Integer32,
igmpInterfaceStatus RowStatus,
igmpInterfaceVersion INTEGER,
igmpInterfaceQuerier IpAddress,
igmpInterfaceQueryMaxResponseTime Integer32,
igmpInterfaceVersion1QuerierTimer TimeTicks,
igmpInterfaceWrongVersionQueries Counter32,
igmpInterfaceJoins Counter32,
igmpInterfaceGroups Gauge32,
igmpInterfaceRobustness Integer32,
igmpInterfaceLastMembQueryIntvl Integer32,
igmpInterfaceProxyIfIndex InterfaceIndexOrZero,
igmpInterfaceQuerierUpTime TimeTicks,
igmpInterfaceQuerierExpiryTime TimeTicks
}
igmpInterfaceIfIndex OBJECT-TYPE
SYNTAX InterfaceIndex
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The ifIndex value of the interface for which IGMP is
enabled."
::= { igmpInterfaceEntry 1 }
igmpInterfaceQueryInterval OBJECT-TYPE
SYNTAX Integer32
UNITS "seconds"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The frequency at which IGMP Host-Query packets are
transmitted on this interface."
DEFVAL { 125 }
::= { igmpInterfaceEntry 2 }
igmpInterfaceStatus OBJECT-TYPE
SYNTAX RowStatus
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The activation of a row enables IGMP on the interface. The
destruction of a row disables IGMP on the interface."
::= { igmpInterfaceEntry 3 }
igmpInterfaceVersion OBJECT-TYPE
SYNTAX INTEGER { version1(1), version2(2) }
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The version of IGMP which is running on this interface.
This object can be used to configure a router capable of
running either value. For IGMP to function correctly, all
routers on a LAN must be configured to run the same version
of IGMP on that LAN."
DEFVAL { version2 }
::= { igmpInterfaceEntry 4 }
igmpInterfaceQuerier OBJECT-TYPE
SYNTAX IpAddress
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The address of the IGMP Querier on the IP subnet to which
this interface is attached."
::= { igmpInterfaceEntry 5 }
igmpInterfaceQueryMaxResponseTime OBJECT-TYPE
SYNTAX Integer32
UNITS "tenths of seconds"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The maximum query response time advertised in IGMPv2
queries on this interface."
DEFVAL { 100 }
::= { igmpInterfaceEntry 6 }
igmpInterfaceVersion1QuerierTimer OBJECT-TYPE
SYNTAX TimeTicks
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The time remaining until the host assumes that there are no
IGMPv1 routers present on the interface. While this is non-
zero, the host will reply to all queries with version 1
membership reports."
::= { igmpInterfaceEntry 9 }
igmpInterfaceWrongVersionQueries OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of queries received whose IGMP version does not
match igmpInterfaceVersion. IGMP requires that all routers
on a LAN be configured to run the same version of IGMP.
Thus, if any queries are received with the wrong version,
this indicates a configuration error."
::= { igmpInterfaceEntry 10 }
igmpInterfaceJoins OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of times a group membership has been added on
this interface; that is, the number of times an entry for
this interface has been added to the Cache Table. This
object gives an indication of the amount of IGMP activity
over time."
::= { igmpInterfaceEntry 11 }
igmpInterfaceGroups OBJECT-TYPE
SYNTAX Gauge32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The current number of entries for this interface in the
Cache Table."
::= { igmpInterfaceEntry 13 }
igmpInterfaceRobustness OBJECT-TYPE
SYNTAX Integer32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The Robustness Variable allows tuning for the expected
packet loss on a subnet. If a subnet is expected to be
lossy, the Robustness Variable may be increased. IGMP is
robust to (Robustness Variable-1) packet losses."
DEFVAL { 2 }
::= { igmpInterfaceEntry 14 }
igmpInterfaceLastMembQueryIntvl OBJECT-TYPE
SYNTAX Integer32
UNITS "tenths of seconds"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The Last Member Query Interval is the Max Response Time
inserted into Group-Specific Queries sent in response to
Leave Group messages, and is also the amount of time between
Group-Specific Query messages. This value may be tuned to
modify the leave latency of the network. A reduced value
results in reduced time to detect the loss of the last
member of a group. The value of this object is irrelevant
if igmpInterfaceVersion is version1."
DEFVAL { 10 }
::= { igmpInterfaceEntry 15 }
igmpInterfaceProxyIfIndex OBJECT-TYPE
SYNTAX InterfaceIndexOrZero
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Some devices implement a form of IGMP proxying whereby
memberships learned on the interface represented by this
row, cause IGMP Host Membership Reports to be sent on the
interface whose ifIndex value is given by this object. Such
a device would implement the igmpV2RouterMIBGroup only on
its router interfaces (those interfaces with non-zero
igmpInterfaceProxyIfIndex). Typically, the value of this
object is 0, indicating that no proxying is being done."
DEFVAL { 0 }
::= { igmpInterfaceEntry 16 }
igmpInterfaceQuerierUpTime OBJECT-TYPE
SYNTAX TimeTicks
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The time since igmpInterfaceQuerier was last changed."
::= { igmpInterfaceEntry 17 }
igmpInterfaceQuerierExpiryTime OBJECT-TYPE
SYNTAX TimeTicks
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The amount of time remaining before the Other Querier
Present Timer expires. If the local system is the querier,
the value of this object is zero."
::= { igmpInterfaceEntry 18 }
--
-- The IGMP Cache Table
--
igmpCacheTable OBJECT-TYPE
SYNTAX SEQUENCE OF IgmpCacheEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The (conceptual) table listing the IP multicast groups for
which there are members on a particular interface."
::= { igmp 2 }
igmpCacheEntry OBJECT-TYPE
SYNTAX IgmpCacheEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry (conceptual row) in the igmpCacheTable."
INDEX { igmpCacheAddress, igmpCacheIfIndex }
::= { igmpCacheTable 1 }
IgmpCacheEntry ::= SEQUENCE {
igmpCacheAddress IpAddress,
igmpCacheIfIndex InterfaceIndex,
igmpCacheSelf TruthValue,
igmpCacheLastReporter IpAddress,
igmpCacheUpTime TimeTicks,
igmpCacheExpiryTime TimeTicks,
igmpCacheStatus RowStatus,
igmpCacheVersion1HostTimer TimeTicks
}
igmpCacheAddress OBJECT-TYPE
SYNTAX IpAddress
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The IP multicast group address for which this entry
contains information."
::= { igmpCacheEntry 1 }
igmpCacheIfIndex OBJECT-TYPE
SYNTAX InterfaceIndex
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The interface for which this entry contains information for
an IP multicast group address."
::= { igmpCacheEntry 2 }
igmpCacheSelf OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"An indication of whether the local system is a member of
this group address on this interface."
DEFVAL { true }
::= { igmpCacheEntry 3 }
igmpCacheLastReporter OBJECT-TYPE
SYNTAX IpAddress
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The IP address of the source of the last membership report
received for this IP Multicast group address on this
interface. If no membership report has been received, this
object has the value 0.0.0.0."
::= { igmpCacheEntry 4 }
igmpCacheUpTime OBJECT-TYPE
SYNTAX TimeTicks
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The time elapsed since this entry was created."
::= { igmpCacheEntry 5 }
igmpCacheExpiryTime OBJECT-TYPE
SYNTAX TimeTicks
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The minimum amount of time remaining before this entry will
be aged out. A value of 0 indicates that the entry is only
present because igmpCacheSelf is true and that if the router
left the group, this entry would be aged out immediately.
Note that some implementations may process membership
reports from the local system in the same way as reports
from other hosts, so a value of 0 is not required."
::= { igmpCacheEntry 6 }
igmpCacheStatus OBJECT-TYPE
SYNTAX RowStatus
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The status of this entry."
::= { igmpCacheEntry 7 }
igmpCacheVersion1HostTimer OBJECT-TYPE
SYNTAX TimeTicks
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The time remaining until the local router will assume that
there are no longer any IGMP version 1 members on the IP
subnet attached to this interface. Upon hearing any IGMPv1
Membership Report, this value is reset to the group
membership timer. While this time remaining is non-zero,
the local router ignores any IGMPv2 Leave messages for this
group that it receives on this interface."
::= { igmpCacheEntry 8 }
-- conformance information
igmpMIBConformance
OBJECT IDENTIFIER ::= { igmpStdMIB 2 }
igmpMIBCompliances
OBJECT IDENTIFIER ::= { igmpMIBConformance 1 }
igmpMIBGroups OBJECT IDENTIFIER ::= { igmpMIBConformance 2 }
-- compliance statements
igmpV1HostMIBCompliance MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"The compliance statement for hosts running IGMPv1 and
implementing the IGMP MIB."
MODULE -- this module
MANDATORY-GROUPS { igmpBaseMIBGroup }
OBJECT igmpInterfaceStatus
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
::= { igmpMIBCompliances 1 }
igmpV1RouterMIBCompliance MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"The compliance statement for routers running IGMPv1 and
implementing the IGMP MIB."
MODULE -- this module
MANDATORY-GROUPS { igmpBaseMIBGroup,
igmpRouterMIBGroup
}
OBJECT igmpInterfaceStatus
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
::= { igmpMIBCompliances 2 }
igmpV2HostMIBCompliance MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"The compliance statement for hosts running IGMPv2 and
implementing the IGMP MIB."
MODULE -- this module
MANDATORY-GROUPS { igmpBaseMIBGroup,
igmpV2HostMIBGroup
}
OBJECT igmpInterfaceStatus
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
::= { igmpMIBCompliances 3 }
igmpV2RouterMIBCompliance MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"The compliance statement for routers running IGMPv2 and
implementing the IGMP MIB."
MODULE -- this module
MANDATORY-GROUPS { igmpBaseMIBGroup,
igmpRouterMIBGroup,
igmpV2RouterMIBGroup
}
OBJECT igmpInterfaceStatus
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
::= { igmpMIBCompliances 4 }
-- units of conformance
igmpBaseMIBGroup OBJECT-GROUP
OBJECTS { igmpCacheSelf,
igmpCacheStatus, igmpInterfaceStatus
}
STATUS current
DESCRIPTION
"The basic collection of objects providing management of
IGMP version 1 or 2."
::= { igmpMIBGroups 1 }
igmpRouterMIBGroup OBJECT-GROUP
OBJECTS { igmpCacheUpTime, igmpCacheExpiryTime,
igmpInterfaceJoins, igmpInterfaceGroups,
igmpCacheLastReporter, igmpInterfaceQuerierUpTime,
igmpInterfaceQuerierExpiryTime,
igmpInterfaceQueryInterval
}
STATUS current
DESCRIPTION
"A collection of additional objects for management of IGMP
version 1 or 2 in routers."
::= { igmpMIBGroups 2 }
igmpV2HostMIBGroup OBJECT-GROUP
OBJECTS { igmpInterfaceVersion1QuerierTimer }
STATUS current
DESCRIPTION
"A collection of additional objects for management of IGMP
version 2 in hosts."
::= { igmpMIBGroups 3 }
igmpHostOptMIBGroup OBJECT-GROUP
OBJECTS { igmpCacheLastReporter, igmpInterfaceQuerier }
STATUS current
DESCRIPTION
"A collection of optional objects for IGMP hosts.
Supporting this group can be especially useful in an
environment with a router which does not support the IGMP
MIB."
::= { igmpMIBGroups 4 }
igmpV2RouterMIBGroup OBJECT-GROUP
OBJECTS { igmpInterfaceVersion, igmpInterfaceQuerier,
igmpInterfaceQueryMaxResponseTime,
igmpInterfaceRobustness,
igmpInterfaceWrongVersionQueries,
igmpInterfaceLastMembQueryIntvl,
igmpCacheVersion1HostTimer
}
STATUS current
DESCRIPTION
"A collection of additional objects for management of IGMP
version 2 in routers."
::= { igmpMIBGroups 5 }
igmpV2ProxyMIBGroup OBJECT-GROUP
OBJECTS { igmpInterfaceProxyIfIndex }
STATUS current
DESCRIPTION
"A collection of additional objects for management of IGMP
proxy devices."
::= { igmpMIBGroups 6 }
END

402
priv/mibs/INET-ADDRESS-MIB Normal file
View file

@ -0,0 +1,402 @@
INET-ADDRESS-MIB DEFINITIONS ::= BEGIN
IMPORTS
MODULE-IDENTITY, mib-2, Unsigned32 FROM SNMPv2-SMI
TEXTUAL-CONVENTION FROM SNMPv2-TC;
inetAddressMIB MODULE-IDENTITY
LAST-UPDATED "200502040000Z"
ORGANIZATION
"IETF Operations and Management Area"
CONTACT-INFO
"Juergen Schoenwaelder (Editor)
International University Bremen
P.O. Box 750 561
28725 Bremen, Germany
Phone: +49 421 200-3587
EMail: j.schoenwaelder@iu-bremen.de
Send comments to <ietfmibs@ops.ietf.org>."
DESCRIPTION
"This MIB module defines textual conventions for
representing Internet addresses. An Internet
address can be an IPv4 address, an IPv6 address,
or a DNS domain name. This module also defines
textual conventions for Internet port numbers,
autonomous system numbers, and the length of an
Internet address prefix.
Copyright (C) The Internet Society (2005). This version
of this MIB module is part of RFC 4001, see the RFC
itself for full legal notices."
REVISION "200502040000Z"
DESCRIPTION
"Third version, published as RFC 4001. This revision
introduces the InetZoneIndex, InetScopeType, and
InetVersion textual conventions."
REVISION "200205090000Z"
DESCRIPTION
"Second version, published as RFC 3291. This
revision contains several clarifications and
introduces several new textual conventions:
InetAddressPrefixLength, InetPortNumber,
InetAutonomousSystemNumber, InetAddressIPv4z,
and InetAddressIPv6z."
REVISION "200006080000Z"
DESCRIPTION
"Initial version, published as RFC 2851."
::= { mib-2 76 }
InetAddressType ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"A value that represents a type of Internet address.
unknown(0) An unknown address type. This value MUST
be used if the value of the corresponding
InetAddress object is a zero-length string.
It may also be used to indicate an IP address
that is not in one of the formats defined
below.
ipv4(1) An IPv4 address as defined by the
InetAddressIPv4 textual convention.
ipv6(2) An IPv6 address as defined by the
InetAddressIPv6 textual convention.
ipv4z(3) A non-global IPv4 address including a zone
index as defined by the InetAddressIPv4z
textual convention.
ipv6z(4) A non-global IPv6 address including a zone
index as defined by the InetAddressIPv6z
textual convention.
dns(16) A DNS domain name as defined by the
InetAddressDNS textual convention.
Each definition of a concrete InetAddressType value must be
accompanied by a definition of a textual convention for use
with that InetAddressType.
To support future extensions, the InetAddressType textual
convention SHOULD NOT be sub-typed in object type definitions.
It MAY be sub-typed in compliance statements in order to
require only a subset of these address types for a compliant
implementation.
Implementations must ensure that InetAddressType objects
and any dependent objects (e.g., InetAddress objects) are
consistent. An inconsistentValue error must be generated
if an attempt to change an InetAddressType object would,
for example, lead to an undefined InetAddress value. In
particular, InetAddressType/InetAddress pairs must be
changed together if the address type changes (e.g., from
ipv6(2) to ipv4(1))."
SYNTAX INTEGER {
unknown(0),
ipv4(1),
ipv6(2),
ipv4z(3),
ipv6z(4),
dns(16)
}
InetAddress ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"Denotes a generic Internet address.
An InetAddress value is always interpreted within the context
of an InetAddressType value. Every usage of the InetAddress
textual convention is required to specify the InetAddressType
object that provides the context. It is suggested that the
InetAddressType object be logically registered before the
object(s) that use the InetAddress textual convention, if
they appear in the same logical row.
The value of an InetAddress object must always be
consistent with the value of the associated InetAddressType
object. Attempts to set an InetAddress object to a value
inconsistent with the associated InetAddressType
must fail with an inconsistentValue error.
When this textual convention is used as the syntax of an
index object, there may be issues with the limit of 128
sub-identifiers specified in SMIv2, STD 58. In this case,
the object definition MUST include a 'SIZE' clause to
limit the number of potential instance sub-identifiers;
otherwise the applicable constraints MUST be stated in
the appropriate conceptual row DESCRIPTION clauses, or
in the surrounding documentation if there is no single
DESCRIPTION clause that is appropriate."
SYNTAX OCTET STRING (SIZE (0..255))
InetAddressIPv4 ::= TEXTUAL-CONVENTION
DISPLAY-HINT "1d.1d.1d.1d"
STATUS current
DESCRIPTION
"Represents an IPv4 network address:
Octets Contents Encoding
1-4 IPv4 address network-byte order
The corresponding InetAddressType value is ipv4(1).
This textual convention SHOULD NOT be used directly in object
definitions, as it restricts addresses to a specific format.
However, if it is used, it MAY be used either on its own or in
conjunction with InetAddressType, as a pair."
SYNTAX OCTET STRING (SIZE (4))
InetAddressIPv6 ::= TEXTUAL-CONVENTION
DISPLAY-HINT "2x:2x:2x:2x:2x:2x:2x:2x"
STATUS current
DESCRIPTION
"Represents an IPv6 network address:
Octets Contents Encoding
1-16 IPv6 address network-byte order
The corresponding InetAddressType value is ipv6(2).
This textual convention SHOULD NOT be used directly in object
definitions, as it restricts addresses to a specific format.
However, if it is used, it MAY be used either on its own or in
conjunction with InetAddressType, as a pair."
SYNTAX OCTET STRING (SIZE (16))
InetAddressIPv4z ::= TEXTUAL-CONVENTION
DISPLAY-HINT "1d.1d.1d.1d%4d"
STATUS current
DESCRIPTION
"Represents a non-global IPv4 network address, together
with its zone index:
Octets Contents Encoding
1-4 IPv4 address network-byte order
5-8 zone index network-byte order
The corresponding InetAddressType value is ipv4z(3).
The zone index (bytes 5-8) is used to disambiguate identical
address values on nodes that have interfaces attached to
different zones of the same scope. The zone index may contain
the special value 0, which refers to the default zone for each
scope.
This textual convention SHOULD NOT be used directly in object
definitions, as it restricts addresses to a specific format.
However, if it is used, it MAY be used either on its own or in
conjunction with InetAddressType, as a pair."
SYNTAX OCTET STRING (SIZE (8))
InetAddressIPv6z ::= TEXTUAL-CONVENTION
DISPLAY-HINT "2x:2x:2x:2x:2x:2x:2x:2x%4d"
STATUS current
DESCRIPTION
"Represents a non-global IPv6 network address, together
with its zone index:
Octets Contents Encoding
1-16 IPv6 address network-byte order
17-20 zone index network-byte order
The corresponding InetAddressType value is ipv6z(4).
The zone index (bytes 17-20) is used to disambiguate
identical address values on nodes that have interfaces
attached to different zones of the same scope. The zone index
may contain the special value 0, which refers to the default
zone for each scope.
This textual convention SHOULD NOT be used directly in object
definitions, as it restricts addresses to a specific format.
However, if it is used, it MAY be used either on its own or in
conjunction with InetAddressType, as a pair."
SYNTAX OCTET STRING (SIZE (20))
InetAddressDNS ::= TEXTUAL-CONVENTION
DISPLAY-HINT "255a"
STATUS current
DESCRIPTION
"Represents a DNS domain name. The name SHOULD be fully
qualified whenever possible.
The corresponding InetAddressType is dns(16).
The DESCRIPTION clause of InetAddress objects that may have
InetAddressDNS values MUST fully describe how (and when)
these names are to be resolved to IP addresses.
The resolution of an InetAddressDNS value may require to
query multiple DNS records (e.g., A for IPv4 and AAAA for
IPv6). The order of the resolution process and which DNS
record takes precedence depends on the configuration of the
resolver.
This textual convention SHOULD NOT be used directly in object
definitions, as it restricts addresses to a specific format.
However, if it is used, it MAY be used either on its own or in
conjunction with InetAddressType, as a pair."
SYNTAX OCTET STRING (SIZE (1..255))
InetAddressPrefixLength ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d"
STATUS current
DESCRIPTION
"Denotes the length of a generic Internet network address
prefix. A value of n corresponds to an IP address mask
that has n contiguous 1-bits from the most significant
bit (MSB), with all other bits set to 0.
An InetAddressPrefixLength value is always interpreted within
the context of an InetAddressType value. Every usage of the
InetAddressPrefixLength textual convention is required to
specify the InetAddressType object that provides the
context. It is suggested that the InetAddressType object be
logically registered before the object(s) that use the
InetAddressPrefixLength textual convention, if they appear
in the same logical row.
InetAddressPrefixLength values larger than
the maximum length of an IP address for a specific
InetAddressType are treated as the maximum significant
value applicable for the InetAddressType. The maximum
significant value is 32 for the InetAddressType
'ipv4(1)' and 'ipv4z(3)' and 128 for the InetAddressType
'ipv6(2)' and 'ipv6z(4)'. The maximum significant value
for the InetAddressType 'dns(16)' is 0.
The value zero is object-specific and must be defined as
part of the description of any object that uses this
syntax. Examples of the usage of zero might include
situations where the Internet network address prefix
is unknown or does not apply.
The upper bound of the prefix length has been chosen to
be consistent with the maximum size of an InetAddress."
SYNTAX Unsigned32 (0..2040)
InetPortNumber ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d"
STATUS current
DESCRIPTION
"Represents a 16 bit port number of an Internet transport
layer protocol. Port numbers are assigned by IANA. A
current list of all assignments is available from
<http://www.iana.org/>.
The value zero is object-specific and must be defined as
part of the description of any object that uses this
syntax. Examples of the usage of zero might include
situations where a port number is unknown, or when the
value zero is used as a wildcard in a filter."
REFERENCE "STD 6 (RFC 768), STD 7 (RFC 793) and RFC 2960"
SYNTAX Unsigned32 (0..65535)
InetAutonomousSystemNumber ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d"
STATUS current
DESCRIPTION
"Represents an autonomous system number that identifies an
Autonomous System (AS). An AS is a set of routers under a
single technical administration, using an interior gateway
protocol and common metrics to route packets within the AS,
and using an exterior gateway protocol to route packets to
other ASes'. IANA maintains the AS number space and has
delegated large parts to the regional registries.
Autonomous system numbers are currently limited to 16 bits
(0..65535). There is, however, work in progress to enlarge the
autonomous system number space to 32 bits. Therefore, this
textual convention uses an Unsigned32 value without a
range restriction in order to support a larger autonomous
system number space."
REFERENCE "RFC 1771, RFC 1930"
SYNTAX Unsigned32
InetScopeType ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"Represents a scope type. This textual convention can be used
in cases where a MIB has to represent different scope types
and there is no context information, such as an InetAddress
object, that implicitly defines the scope type.
Note that not all possible values have been assigned yet, but
they may be assigned in future revisions of this specification.
Applications should therefore be able to deal with values
not yet assigned."
REFERENCE "RFC 3513"
SYNTAX INTEGER {
-- reserved(0),
interfaceLocal(1),
linkLocal(2),
subnetLocal(3),
adminLocal(4),
siteLocal(5), -- site-local unicast addresses
-- have been deprecated by RFC 3879
-- unassigned(6),
-- unassigned(7),
organizationLocal(8),
-- unassigned(9),
-- unassigned(10),
-- unassigned(11),
-- unassigned(12),
-- unassigned(13),
global(14)
-- reserved(15)
}
InetZoneIndex ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d"
STATUS current
DESCRIPTION
"A zone index identifies an instance of a zone of a
specific scope.
The zone index MUST disambiguate identical address
values. For link-local addresses, the zone index will
typically be the interface index (ifIndex as defined in the
IF-MIB) of the interface on which the address is configured.
The zone index may contain the special value 0, which refers
to the default zone. The default zone may be used in cases
where the valid zone index is not known (e.g., when a
management application has to write a link-local IPv6
address without knowing the interface index value). The
default zone SHOULD NOT be used as an easy way out in
cases where the zone index for a non-global IPv6 address
is known."
REFERENCE "RFC4007"
SYNTAX Unsigned32
InetVersion ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"A value representing a version of the IP protocol.
unknown(0) An unknown or unspecified version of the IP
protocol.
ipv4(1) The IPv4 protocol as defined in RFC 791 (STD 5).
ipv6(2) The IPv6 protocol as defined in RFC 2460.
Note that this textual convention SHOULD NOT be used to
distinguish different address types associated with IP
protocols. The InetAddressType has been designed for this
purpose."
REFERENCE "RFC 791, RFC 2460"
SYNTAX INTEGER {
unknown(0),
ipv4(1),
ipv6(2)
}
END

Some files were not shown because too many files have changed in this diff Show more