CHIPNET-MIB: View SNMP OID List / Download MIB

VENDOR: CHIPPCOM


 Home MIB: CHIPNET-MIB
Download as:   

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
 chipcom 1.3.6.1.4.1.49
       chipmib02 1.3.6.1.4.1.49.2
           chipGen 1.3.6.1.4.1.49.2.1
           chipEcho 1.3.6.1.4.1.49.2.2
           chipProducts 1.3.6.1.4.1.49.2.3
               online 1.3.6.1.4.1.49.2.3.1
                   olAgents 1.3.6.1.4.1.49.2.3.1.1
                   olConc 1.3.6.1.4.1.49.2.3.1.2
                   olEnv 1.3.6.1.4.1.49.2.3.1.3
                   olModules 1.3.6.1.4.1.49.2.3.1.4
                       olSpecMods 1.3.6.1.4.1.49.2.3.1.4.4
                           ol50nnMCTL 1.3.6.1.4.1.49.2.3.1.4.4.3
                           ol51nnMMGT 1.3.6.1.4.1.49.2.3.1.4.4.4
                           ol51nnMFIB 1.3.6.1.4.1.49.2.3.1.4.4.5
                           ol51nnMUTP 1.3.6.1.4.1.49.2.3.1.4.4.6
                           ol51nnMTP 1.3.6.1.4.1.49.2.3.1.4.4.7
                           ol51nnMBNC 1.3.6.1.4.1.49.2.3.1.4.4.8
                           ol51nnBEE 1.3.6.1.4.1.49.2.3.1.4.4.9
                           ol51nnRES 1.3.6.1.4.1.49.2.3.1.4.4.10
                           ol51nnREE 1.3.6.1.4.1.49.2.3.1.4.4.11
                           ol51nnMAUIF 1.3.6.1.4.1.49.2.3.1.4.4.12
                           ol51nnMAUIM 1.3.6.1.4.1.49.2.3.1.4.4.13
                           ol5208MTP 1.3.6.1.4.1.49.2.3.1.4.4.14
                           ol51nnMFP 1.3.6.1.4.1.49.2.3.1.4.4.15
                           ol51nnMFBP 1.3.6.1.4.1.49.2.3.1.4.4.16
                           ol51nnMTPL 1.3.6.1.4.1.49.2.3.1.4.4.17
                           ol51nnMTPPL 1.3.6.1.4.1.49.2.3.1.4.4.18
                           ol52nnMTP 1.3.6.1.4.1.49.2.3.1.4.4.19
                           ol52nnMFR 1.3.6.1.4.1.49.2.3.1.4.4.20
                           ol51nnMTS 1.3.6.1.4.1.49.2.3.1.4.4.21
                           ol51nnMFL 1.3.6.1.4.1.49.2.3.1.4.4.22
                           ol50nnMRCTL 1.3.6.1.4.1.49.2.3.1.4.4.23
                           ol51nnMFB 1.3.6.1.4.1.49.2.3.1.4.4.24
                           ol53nnMMGT 1.3.6.1.4.1.49.2.3.1.4.4.25
                           ol53nnMFBMIC 1.3.6.1.4.1.49.2.3.1.4.4.26
                           ol53nnMFIBST 1.3.6.1.4.1.49.2.3.1.4.4.27
                           ol53nnMSTP 1.3.6.1.4.1.49.2.3.1.4.4.28
                           ol51nnMTPCL 1.3.6.1.4.1.49.2.3.1.4.4.29
                           ol52nnBTT 1.3.6.1.4.1.49.2.3.1.4.4.30
                           ol51nnIx 1.3.6.1.4.1.49.2.3.1.4.4.31
                           ol52nnMMGT 1.3.6.1.4.1.49.2.3.1.4.4.32
                           ol50nnMHCTL 1.3.6.1.4.1.49.2.3.1.4.4.33
                   olNets 1.3.6.1.4.1.49.2.3.1.5
                       olNet 1.3.6.1.4.1.49.2.3.1.5.1
                           olNetDPTable 1.3.6.1.4.1.49.2.3.1.5.1.1 no-access
A table that contains information linking physical backplane allocation to logical networks. This information is useful: (1) to determine the physical allocation of networks on the backplane, and (2) to determine the remaining capacity of the backplane for future network growth. Since unknown modules are managed via dip switches, this is useful in order to set the dips to the appropriate settings. Ethernet is a bus architecture. Once a path is allocated, all modules and ports can access that path. Token Ring and FDDI are ring architectures. Each module on a ring requires a path. Therefore, 4 paths could be used to link 4 modules together on one ring, or 2 modules on 2 separate rings. It is possible to have a module allocated to a ring (and thus a data path) without linking to another module. These rules can be used to determine the remaining capacity for network growth.
                               olNetDPEntry 1.3.6.1.4.1.49.2.3.1.5.1.1.1 no-access
A list of information about each data path in the concentrator.
                                   olNetDPDataPath 1.3.6.1.4.1.49.2.3.1.5.1.1.1.1 integer read-only
The data path on the backplane. Data paths between different protocols overlap. That is, an ethernet data path will overlap with multiple token ring and fddi data paths. Enumeration: 'fddi-path-1': 24, 'fddi-path-3': 26, 'fddi-path-2': 25, 'fddi-path-5': 28, 'fddi-path-4': 27, 'fddi-path-7': 30, 'fddi-path-6': 29, 'token-ring-path-12': 20, 'token-ring-path-13': 21, 'token-ring-path-10': 18, 'token-ring-path-11': 19, 'token-ring-path-14': 22, 'token-ring-path-15': 23, 'token-ring-path-8': 16, 'token-ring-path-9': 17, 'token-ring-path-1': 9, 'token-ring-path-2': 10, 'token-ring-path-3': 11, 'token-ring-path-4': 12, 'token-ring-path-5': 13, 'token-ring-path-6': 14, 'token-ring-path-7': 15, 'fddi-path-8': 31, 'ethernet-path-3': 8, 'ethernet-path-2': 7, 'ethernet-path-1': 6.
                                   olNetDPNetID 1.3.6.1.4.1.49.2.3.1.5.1.1.1.2 integer read-only
The network that this data path corresponds to. If the data path is not being used at all, notUsed(1) is the return value. If the data path is being used by another protocol, then otherProto(2) is the return value. Enumeration: 'token-ring-1': 9, 'ethernet-1': 6, 'ethernet-2': 7, 'ethernet-3': 8, 'token-ring-5': 13, 'token-ring-4': 12, 'token-ring-7': 15, 'token-ring-6': 14, 'fddi-2': 17, 'notUsed': 1, 'token-ring-3': 11, 'otherProto': 2, 'token-ring-2': 10, 'fddi-3': 18, 'fddi-4': 19, 'fddi-1': 16.
                           olNetSecurityMACTable 1.3.6.1.4.1.49.2.3.1.5.1.2 no-access
A table of security configuration parameters and MAC addresses associated with every port with security configured in the concentrator.
                               olNetSecurityMACEntry 1.3.6.1.4.1.49.2.3.1.5.1.2.1 no-access
A list of security configuration parameters and MAC addresses associated with each port with security configured in the concentrator.
                                   olNetSecurityMACSlotIndex 1.3.6.1.4.1.49.2.3.1.5.1.2.1.1 integer read-only
The slot number that contains this port.
                                   olNetSecurityMACPortIndex 1.3.6.1.4.1.49.2.3.1.5.1.2.1.2 integer read-only
The port number within this slot.
                                   olNetSecurityMACAddress 1.3.6.1.4.1.49.2.3.1.5.1.2.1.3 macaddress read-write
The security MAC address assigned to this port.
                                   olNetSecurityMACMode 1.3.6.1.4.1.49.2.3.1.5.1.2.1.4 integer read-write
The desired security mode for this port/address. Enumeration: 'disabled': 2, 'enabled': 1.
                                   olNetSecurityMACStatus 1.3.6.1.4.1.49.2.3.1.5.1.2.1.5 integer read-write
Each instance of the olNetSecurityMACTable associated with this olNetSecurityMACEntry (slot, port, and address) will be deleted by the agent if this olNetSecurityMACEntry is not equal to valid(1). Initial creation of instances occurs via a set operation on a specific slot/port/address. Enumeration: 'valid': 1, 'invalid': 2.
                       olEnet 1.3.6.1.4.1.49.2.3.1.5.2
                       olTRnet 1.3.6.1.4.1.49.2.3.1.5.3
                       olFDDInet 1.3.6.1.4.1.49.2.3.1.5.4
                   olGroups 1.3.6.1.4.1.49.2.3.1.6
                   olAlarm 1.3.6.1.4.1.49.2.3.1.7
                       olThresh 1.3.6.1.4.1.49.2.3.1.7.1
                           olThreshControl 1.3.6.1.4.1.49.2.3.1.7.1.1
               oebm 1.3.6.1.4.1.49.2.3.2
               midnight 1.3.6.1.4.1.49.2.3.3
               workGroupHub 1.3.6.1.4.1.49.2.3.4
                   hubSysGroup 1.3.6.1.4.1.49.2.3.4.1
                   hardwareGroup 1.3.6.1.4.1.49.2.3.4.2
                   softwareGroup 1.3.6.1.4.1.49.2.3.4.3
                   hubGroup 1.3.6.1.4.1.49.2.3.4.4
                   boardGroup 1.3.6.1.4.1.49.2.3.4.5
                   portGroup 1.3.6.1.4.1.49.2.3.4.6
                   alarmGroup 1.3.6.1.4.1.49.2.3.4.7
               emm 1.3.6.1.4.1.49.2.3.5
               chipBridge 1.3.6.1.4.1.49.2.3.6
               trmm 1.3.6.1.4.1.49.2.3.7
               fmm 1.3.6.1.4.1.49.2.3.8
               focus1 1.3.6.1.4.1.49.2.3.9
               oeim 1.3.6.1.4.1.49.2.3.10
           chipExperiment 1.3.6.1.4.1.49.2.4
               chipExpTokenRing 1.3.6.1.4.1.49.2.4.1
                   dot5 1.3.6.1.4.1.49.2.4.1.1
               dot1dBridge 1.3.6.1.4.1.49.2.4.14
           chipTTY 1.3.6.1.4.1.49.2.5
           chipTFTP 1.3.6.1.4.1.49.2.6
           chipDownload 1.3.6.1.4.1.49.2.7