MIBs Depot

FORCE10-SMI

Last updated
2007-06-15 12:00
Organization
Force10 Networks, Inc.
Revisions
2007-06-15 12:00, 1900-10-10 00:00
Namespace
dell
Source file
FORCE10-SMI
Digest
sha256:48cc0f0d6481d5dbd7aae27bedda8a398e6cc1275e8b9c404726dfde2b311eac

Description

The Structure of Management Information for the Force10 enterprise.

Contact

Force10 Networks, Inc 1440 McCarthy Blvd Milpitas, CA 95035 (408) 571-3500 support@force10networks.com http://www.force10networks.com

Imports

FromSymbols
SNMPv2-CONFMODULE-COMPLIANCE, NOTIFICATION-GROUP
SNMPv2-SMIMODULE-IDENTITY, NOTIFICATION-TYPE, OBJECT-IDENTITY, OBJECT-TYPE, enterprises, iso
SNMPv2-TCDisplayString, TEXTUAL-CONVENTION

Imported by

16 module(s) in this corpus import this one.

Load order

Every file a consumer needs in order to load this module, dependencies first.

FORCE10-SMI
SNMPv2-CONF
SNMPv2-SMI
SNMPv2-TC

Objects

NameOIDSyntaxAccessStatus
f10Products
OBJECT-IDENTITY
Force10 Products' OID.
1.3.6.1.4.1.6027.1current
f10Common
OBJECT-IDENTITY
All Force10 shared TEXTTUAL-CONVENTION definitions
1.3.6.1.4.1.6027.2current
f10Mgmt
OBJECT-IDENTITY
f10Mgmt is the main subtree for Force10 mib development.
1.3.6.1.4.1.6027.3current
f10Modules
OBJECT-IDENTITY
f10Modules provides a root object identifier from which MODULE-IDENTITY values may be based.
1.3.6.1.4.1.6027.4current
f10Experiment
OBJECT-IDENTITY
f10Experiment provides a root object identifier from which experimental mibs may be temporarily based. mibs are typicially based here if they fall in one of two categories 1) are IETF work-in-process mibs which have not been assigned a permanent object identifier by the IANA. 2) are force10 work-in-process which has not been assigned a permanent object identifier by the force10 assigned number authority, typicially because the mib is not ready for deployment. NOTE WELL: support for mibs in the f10Experiment subtree will be deleted when a permanent object identifier assignment is made.
1.3.6.1.4.1.6027.20current