DASAN-SMI: View SNMP OID List / Download MIB

VENDOR: DASAN CO.,LTD.


 Home MIB: DASAN-SMI
Download as:   
SNMPv2-CONF, SNMPv2-SMI, SNMPv2-TC

Download standard MIB format if you are planning to load a MIB file into some system (OS, Zabbix, PRTG ...) or view it with a MIB browser. CSV is more suitable for analyzing and viewing OID' and other MIB objects in excel. JSON and YAML formats are usually used in programing even though some systems can use MIB in YAML format (like Logstash).
Keep in mind that standard MIB files can be successfully loaded by systems and programs only if all the required MIB's from the "Imports" section are already loaded.
The tree-like SNMP object navigator requires no explanations because it is very simple to use. And if you stumbled on this MIB from Google note that you can always go back to the home page if you need to perform another MIB or OID lookup.


Object Name OID Type Access Info
 dasan 1.3.6.1.4.1.6296
The Structure of Management Information for the Dasan enterprise.
           dasanEvents 1.3.6.1.4.1.6296.0
dasanEvents is the root OBJECT IDENTIFIER of EVENTS(or TRAPS). Each EVENT(TRAP) is defined in Each Product MIB file.
           dasanProducts 1.3.6.1.4.1.6296.1
dasanProducts is the root OBJECT IDENTIFIER from which sysObjectID values are assigned. Actual values are defined in DASAN-PRODUCTS-MIB.
           local 1.3.6.1.4.1.6296.2
Subtree beneath which pre-10.2 MIBS were built.
           temporary 1.3.6.1.4.1.6296.3
Subtree beneath which pre-10.2 experiments were placed.
           pakmon 1.3.6.1.4.1.6296.4
reserved for pakmon
           workgroup 1.3.6.1.4.1.6296.5
subtree reserved for use by the Workgroup Business Unit
           otherEnterprises 1.3.6.1.4.1.6296.6
otherEnterprises provides a root object identifier from which mibs produced by other companies may be placed. mibs produced by other enterprises are typicially implemented with the object identifiers as defined in the mib, but if the mib is deemed to be uncontrolled, we may reroot the mib at this subtree in order to have a controlled version.
               dsShe 1.3.6.1.4.1.6296.6.2
           dasanAgentCapability 1.3.6.1.4.1.6296.7
dasanAgentCapability provides a root object identifier from which AGENT-CAPABILITIES values may be assigned.
           dasanConfig 1.3.6.1.4.1.6296.8
dasanConfig is the main subtree for configuration mibs.
           dasanMgmt 1.3.6.1.4.1.6296.9
dasanMgmt is the main subtree for new mib development.
           dasanExperiment 1.3.6.1.4.1.6296.10
dasanExperiment 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 dasan work-in-process which has not been assigned a permanent object identifier by the dasan assigned number authority, typicially because the mib is not ready for deployment. NOTE WELL: support for mibs in the dasanExperiment subtree will be deleted when a permanent object identifier assignment is made.
           dasanAdmin 1.3.6.1.4.1.6296.11
dasanAdmin is reserved for administratively assigned OBJECT IDENTIFIERS, i.e. those not associated with MIB objects
           dasanModules 1.3.6.1.4.1.6296.12
dasanModules provides a root object identifier from which MODULE-IDENTITY values may be assigned.
           lightstream 1.3.6.1.4.1.6296.13
subtree reserved for use by Lightstream
           dasanworks 1.3.6.1.4.1.6296.14
dasanworks provides a root object identifier beneath which mibs applicable to the dasanWorks family of network management products are defined.
           newport 1.3.6.1.4.1.6296.15
subtree reserved for use by the former Newport Systems Solutions, now a portion of the Access Business Unit.
           dasanPartnerProducts 1.3.6.1.4.1.6296.16
dasanPartnerProducts is the root OBJECT IDENTIFIER from which partner sysObjectID values may be assigned. Such sysObjectID values are composed of the dasanPartnerProducts prefix, followed by a single identifier that is unique for each partner, followed by the value of sysObjectID of the dasan product from which partner product is derived. Note that the chassisPartner MIB object defines the value of the identifier assigned to each partner.
           dasanPolicy 1.3.6.1.4.1.6296.17
dasanPolicy is the root of the dasan-assigned OID subtree for use with Policy Management.
           sleMgmt 1.3.6.1.4.1.6296.101
SLE Mgmt.
           sleV2Mgmt 1.3.6.1.4.1.6296.102
sleV2Management.