The unique type identifier for this module. This type
is used to identify the branch in olSpecMods (see below).
module-unmanageable(1) means that only the following
objects are valid for this module:
ocModSlotIndex
ocModClass
ocModVersion
ocModVendor
ocModReset
ocModConfigToDips (deprecated)
ocModConfigured
module-unknown(2) means that all the generic attributes
are manageable, but there is no olSpecMods branch
for this module as viewed by this agent.
Parsed from file isd_mib.txt
Company: None
Module: CHIPCOMMIB
The unique type identifier for this module. This type
is used to identify the branch in olSpecMods (see below).
module-unmanageable(1) means that only the following
objects are valid for this module:
ocModSlotIndex
ocModClass
ocModVersion
ocModVendor
ocModReset
ocModConfigToDips
ocModConfigured
module-unknown(2) means that all the generic attributes
are manageable, but there is no olSpecMods branch
for this module as viewed by this agent.
Parsed from file CHIPCOMMIB.mib
Module: CHIPCOMMIB
Vendor: Chippcom
Module: CHIPCOMMIB
[Automatically extracted from oidview.com]
ocModType OBJECT-TYPE SYNTAX INTEGER { module-unmanageable(1), module-unknown(2), module-50nnM-CTL(3), module-51nnM-MGT(4), module-51nnM-FIB(5), module-51nnM-UTP(6), module-51nnM-TP(7), module-51nnM-BNC(8), module-51nnB-EE(9), module-51nnR-ES(10), module-51nnR-EE(11), module-51nnM-AUIF(12), module-51nnM-AUIM(13), module-5208M-TP(14), module-51nnM-FP(15), module-51nnM-FBP(16), module-51nnM-TPL(17), module-51nnM-TPPL(18), module-52nnM-TP(19), module-52nnM-FR(20), module-51nnM-TS(21), module-51nnM-FL(22), module-50nnM-RCTL(23), module-51nnM-FB(24), module-53nnM-MGT(25), module-53nnM-FBMIC(26), module-53nnM-FIBST(27), module-53nnM-STP(28), module-51nnM-TPCL(29), module-52nnB-TT(30), module-51nnI-x(31), module-52nnM-MGT(32), module-50nnM-HCTL(33), module-61nnM-CAR(35), module-62nnM-TP(36), module-62nnM-ATP(37), module-62nnM-ATPP(38), module-62nnM-DFR(40), module-67nnM-6E(42), module-60nnM-MGT(43), module-62nnD-MGT(44), module-61nnD-MGT(45), module-61nnM-FBP(46), module-61nnM-TPL(47), module-51nnM-TPLS(48), module-60nnM-RCTL(50), module-50nnM-RCLS(51), module-41nnH-MTP(52), module-41nnH-ETP(53), module-52nnM-CR(59), module-61nnM-TPP(60), module-6100D-SEC(61), module-52nnM-EC(62), module-5201M-DEK(63), module-5101M-DEK(64), module-53nnM-TDDI(65), module-52nnM-ATP(67), module-RMON-EMP(68), module-42nnMH(69), module-42nnEH(70), module-64nnM-100-MIC(71), module-64nnM-25-TP(72), module-61nnM-MOD(73), module-61nnM-TPCL(74), module-64nnSW(77), module-4200M-FR(84), module-4200M-CR(85), module-41nnMH(86), module-41nnEH(87), module-61nnD-BNC(90), module-61nnD-AUIF(91), module-61nnD-AUIM(92), module-61nnD-FIB(93), module-61nnD-TPP(94), module-5104R-WFn(95), module-66nnM-LS(96), module-61nnD-AMGT(97), module-4201M-DEK(98), module-6102M-DEK(99), module-60nnM-AMGT(105), module-60nnM-ARCTL(106), module-67nnR-TCS(119), module-51nnM-TPCP(122), module-64nnM-155(123), module-64nnM-100-SC(125), module-64nnD-155-MMF(126), module-62nnM-DCR(128), module-62nnM-QFR(129), module-64nnD-155-SMF(132), module-64nnD-155RJ-TP(133), module-64nnD-155D9-STP(134), module-64nnB-RJ45(135), module-64nnU-2RJ(136), module-67nnR-ECS(137), module-64nnM-Car(138), module-965nnM-SM(140), module-96512M-TX(147), module-96513M-TXFX(148), module-64nnM-155-3P(153), module-64nnM-CarPO-1S(154), module-64nnM-CarPO-2S(155), module-64nnM-CarPO-3S(156), module-not-installed(255) } ACCESS read-only STATUS mandatory DESCRIPTION "The unique type identifier for this module. This type is used to identify the branch in olSpecMods (see below). module-unmanageable(1) means that only the following objects are valid for this module: ocModSlotIndex ocModClass ocModVersion ocModVendor ocModReset ocModConfigToDips (deprecated) ocModConfigured module-unknown(2) means that all the generic attributes are manageable, but there is no olSpecMods branch for this module as viewed by this agent." ::= { ocModEntry 3 }
ocModType OBJECT-TYPE SYNTAX INTEGER { module-unmanageable(1), module-unknown(2), module-50nnM-CTL(3), module-51nnM-MGT(4), module-51nnM-FIB(5), module-51nnM-UTP(6), module-51nnM-TP(7), module-51nnM-BNC(8), module-51nnB-EE(9), module-51nnR-ES(10), module-51nnR-EE(11), module-51nnM-AUIF(12), module-51nnM-AUIM(13), module-5208M-TP(14), module-51nnM-FP(15), module-51nnM-FBP(16), module-51nnM-TPL(17), module-51nnM-TPPL(18), module-52nnM-TP(19), module-52nnM-FR(20), module-51nnM-TS(21), module-51nnM-FL(22), module-50nnM-RCTL(23), module-51nnM-FB(24), module-53nnM-MGT(25), module-53nnM-FBMIC(26), module-53nnM-FIBST(27), module-53nnM-STP(28), module-51nnM-TPCL(29), module-52nnB-TT(30), module-51nnI-x(31), module-52nnM-MGT(32), module-50nnM-HCTL(33), module-61nnM-CAR(35), module-60nnM-MGT(43), module-61nnD-MGT(45), module-61nnM-FBP(46), module-61nnM-TPL(47), module-51nnM-TPLS(48), module-60nnM-RCTL(50), module-50nnM-RCLS(51), module-41nnH-MTP(52), module-41nnH-ETP(53), module-52nnM-EC(62) , module-53nnM-TDDI(65) } ACCESS read-only STATUS mandatory DESCRIPTION "The unique type identifier for this module. This type is used to identify the branch in olSpecMods (see below). module-unmanageable(1) means that only the following objects are valid for this module: ocModSlotIndex ocModClass ocModVersion ocModVendor ocModReset ocModConfigToDips ocModConfigured module-unknown(2) means that all the generic attributes are manageable, but there is no olSpecMods branch for this module as viewed by this agent." ::= { ocModEntry 3 }
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.49.2.3.1.4.6.1.1 | ocModSlotIndex | 0 | 0 | The unique slot number of this module. Its value ranges between 1 and olConcNumSlots and remains constant at least from one re-i… |
| 1.3.6.1.4.1.49.2.3.1.4.6.1.2 | ocModSubSlotIndex | 0 | 0 | The unique subslot number of this module. Its value ranges between 1 and the value of ocModNumSubSlots for the mother board in t… |
| 1.3.6.1.4.1.49.2.3.1.4.6.1.4 | ocModClass | 0 | 0 | The class of this module. The class defines the internal data structure used to manage this module. |
| 1.3.6.1.4.1.49.2.3.1.4.6.1.5 | ocModDescr | 0 | 0 | A textual string containing information about the module. |
| 1.3.6.1.4.1.49.2.3.1.4.6.1.6 | ocModVersion | 0 | 0 | The software version number of this module. |
| 1.3.6.1.4.1.49.2.3.1.4.6.1.7 | ocModVendor | 0 | 0 | The vendor of this module. |
| 1.3.6.1.4.1.49.2.3.1.4.6.1.8 | ocModResetModule | 0 | 0 | Setting this object to reset(2) causes this module to reset. |
| 1.3.6.1.4.1.49.2.3.1.4.6.1.9 | ocModConfigToDips | 0 | 0 | Setting this object to configure(2) causes this module to configure based on the dip switch settings. Note, if the NV dip switch… |
| 1.3.6.1.4.1.49.2.3.1.4.6.1.10 | ocModConfigured | 0 | 0 | This object indicates whether this module has already been configured. An unconfigured module is configured to a safe state (por… |
| 1.3.6.1.4.1.49.2.3.1.4.6.1.11 | ocModNetwork | 0 | 0 | The network that this module is attached to. Setting this module to a value that it does not support will return an invalidData e… |
| 1.3.6.1.4.1.49.2.3.1.4.6.1.12 | ocModNetworkType | 0 | 0 | The network type of this module. The network type reflects the valid values for ocModNetwork. |
| 1.3.6.1.4.1.49.2.3.1.4.6.1.13 | ocModStatus | 0 | 0 | The module's status. |
| 1.3.6.1.4.1.49.2.3.1.4.6.1.14 | ocModNumPorts | 0 | 0 | The number of ports on this module. Note, ports may be physical ports like 10BASE-T ports, or logical, like the bridge module po… |
| 1.3.6.1.4.1.49.2.3.1.4.6.1.15 | ocModNumTrunks | 0 | 0 | The number of trunks on this module. Note, trunks are links that are, by definition, backbone connections. Examples of trunks ar… |
| 1.3.6.1.4.1.49.2.3.1.4.6.1.16 | ocModNumSubSlots | 0 | 0 | The number of possible submodules that can exist in this slot. |
| 1.3.6.1.4.1.49.2.3.1.4.6.1.17 | ocModNumOccupiedSlots | 0 | 0 | The number of slots, or daughter card slots, that this module occupies. This information is useful to determine that this module… |
| 1.3.6.1.4.1.49.2.3.1.4.6.1.18 | ocModSlotOffset | 0 | 0 | The slot (or daughter card subslot) offset that this module reports is its slot (or subslot) number, starting from 1. For example,… |
| 1.3.6.1.4.1.49.2.3.1.4.6.1.19 | ocModNumBridgePorts | 0 | 0 | The number of bridge ports on this module. Note, ports may be physical or logical. |