AD | Application | AWS | Azure | Cloud | Database | Enterprise | Environmental | Event Log | File System | Infra | IoT | IT Service | Linux | Network/System | Performance | Protocol | SaaS | Security | Service Level | SNMP | Storage | VMware | VoIP | Web | Wireless

Crumbtrail

MonitorTools.com » Technical documentation » SNMP » MIB » Enterasys-Networks-Inc » CHASSIS-MIB » Objects

CHASSIS-MIB.mib object view, vendor Enterasys-Networks-Inc

Introduction

Most network devices and programs ship with so-called MIB files to describe the parameters and meanings (i.e.: friendly names) which are available for monitoring via SNMP.
ActiveXperts Network Monitor 2024 can import vendor-specific MIB files, so it can be used to monitor specific OID's (Object Identifiers). This way, you can monitor your devices, computers, etc. by selecting your relevant OID's by name.

ActiveXperts Network Monitor 2024 can import MIB file CHASSIS-MIB and use it to monitor vendor specific OID's.

CHASSIS-MIB file content

Object view of CHASSIS-MIB:

Scalar Object
chType .1.3.6.1.4.1.52.4.1.1.2.1
Identifies the type of hub-based or standalone device. A vendor's authoritative identification of this chassis or device. By convention, this value is allocated within the SMI enterprises subtree(1.3.6.1.4.1), and provides an easy and unambiguous means for determining `what kind of box' is being managed. If this information is not present or unknown, its value should be set to the OBJECT IDENTIFIER { 0 0 }, which is a syntactically valid object identifier.
chBackplaneEntry .1.3.6.1.4.1.52.4.1.1.2.2.1
A backplane entry containing objects for a particular backplane.
chNumSlots .1.3.6.1.4.1.52.4.1.1.2.3
Number of slots in a chassis. For bounded, slot-less systems, the value of this object shall be zero(0).
chCompEntry .1.3.6.1.4.1.52.4.1.1.2.4.1
A component entry containing objects for a particular component.
chSlotEntry .1.3.6.1.4.1.52.4.1.1.2.5.1
A slot entry containing objects for a particular module.
chCompMIBEntry .1.3.6.1.4.1.52.4.1.1.2.6.1
A MIB entry containing objects for a MIB that is realized by a particular module.
chPhysicalChanges .1.3.6.1.4.1.52.4.1.1.2.7
Depicts the number of physical changes that have occured to the chassis MIB. This includes additions and removal of components in the component table.
chLogicalChanges .1.3.6.1.4.1.52.4.1.1.2.8
Depicts the number of logical changes that have occured to the chassis MIB. This includes all sets to name strings etc.
chCompGlobalBasicCommStr .1.3.6.1.4.1.52.4.1.1.2.9
This is defined as the base read only community string to access MIBs on this module. A write to this object will change all instances of chCompBasicCommStr.
chCompGlobalROCommStr .1.3.6.1.4.1.52.4.1.1.2.10
This is defined as the expanded read only community string to access MIBs on this module. A write to this object will change all instances of chCompROCommStr.
chCompGlobalRWCommStr .1.3.6.1.4.1.52.4.1.1.2.11
This is defined as the read write community string to access MIBs on this module. A write to this object will change all instances of chCompRWCommStr.
chCompGlobalSUCommStr .1.3.6.1.4.1.52.4.1.1.2.12
This is defined as the super user community string to access MIBs on this module. A write to this object will change all instances of chCompSUCommStr.
Tabular Object
chBackplaneID .1.3.6.1.4.1.52.4.1.1.2.2.1.1
An unique value identifying a backplane within the chassis.
chBackplaneType .1.3.6.1.4.1.52.4.1.1.2.2.1.2
An authoritative identification that is specific to the particular media being used to realize the backplane. For example, if the backplane is realized by an Ethernet, then the value of this object refers to a well known OID defined for Ethernet. If this information is not present or unknown, its value should be set to OBJECT IDENTIFIER { 0 0 }, which is a syntactically valid object identifier.
chCompID .1.3.6.1.4.1.52.4.1.1.2.4.1.1
An unique value identifying a component, which includes, but is not limited to, routers, bridges, and terminal servers. Multiple instances of a functional device may exist within the same chassis.
chCompAdminStatus .1.3.6.1.4.1.52.4.1.1.2.4.1.2
Provides the state of the given component. A component is activated by writing a value of enabled(3). Once enabled, a component enters testing mode, which is denoted by testing(4), when this object is read. After tests are complete, the component either enters the operational(5), or the error(6) state. The component may be de-activated by writing a value of disabled(7). In a disabled state, a component does exist within the given chassis, but is benign. A disabled component is available for subsequent activation.
chCompArg .1.3.6.1.4.1.52.4.1.1.2.4.1.3
A variable that may be passed to a component, when it is being either enabled or disabled.
chCompType .1.3.6.1.4.1.52.4.1.1.2.4.1.4
Identifies a component within this chassis. A vendor's authoritative identification of this component type. By convention, this value is allocated within the SMI enterprises subtree(1.3.6.1.4.1), and provides an easy and unambiguous means for determining the component type. If this information is not present or unknown, its value should be set to the OBJECT IDENTIFIER { 0 0 }, which is a syntactically valid object identifier.
chCompName .1.3.6.1.4.1.52.4.1.1.2.4.1.5
A textual description of the component.
chCompVersion .1.3.6.1.4.1.52.4.1.1.2.4.1.6
A textual description of the version/revision level for this component's software.
chCompTimeStamp .1.3.6.1.4.1.52.4.1.1.2.4.1.7
The value of sysUpTime of this management entity, when this component was last (re-)initialized.
chCompAccessPolicy .1.3.6.1.4.1.52.4.1.1.2.4.1.8
Defines access information for the pertinent component.
chCompBasicCommStr .1.3.6.1.4.1.52.4.1.1.2.4.1.9
Read-only community string for the pertinent component. If the value of chCompAccessPolicy is otherCommStr(4) or other(5), then this object shall determine the read-only Community String to be used when accessing this component. This also defined the basic read only community string to access MIBs registered to this component.
chCompROCommStr .1.3.6.1.4.1.52.4.1.1.2.4.1.10
Read-only community string for the pertinent component. If the value of chCompAccessPolicy is otherCommStr(4) or other(5), then this object shall determine the read-only Community String to be used when accessing this component. This also defined the read only community string to access MIBs registered to this component.
chCompRWCommStr .1.3.6.1.4.1.52.4.1.1.2.4.1.11
Read-write community string for the pertinent component. If the value of chCompAccessPolicy is otherCommStr(4) or other(5), then this object shall determine the read-write Community String to be used when accessing this component. This also defined the read write community string to access MIBs registered to this component.
chCompSUCommStr .1.3.6.1.4.1.52.4.1.1.2.4.1.12
Super user community string for the pertinent component. If the value of chCompAccessPolicy is otherCommStr(4) or other(5), then this object shall determine the read-write Community String to be used when accessing this component. This also defined the read write community string to access MIBs registered to this component.
chCompNetAdr .1.3.6.1.4.1.52.4.1.1.2.4.1.13
If the value of chCompAccessPolicy is other(5), then this object shall determine the Network Address to be used to access this component. In all other cases, a value of 0.0.0.0 shall be returned, when read.
chSlotID .1.3.6.1.4.1.52.4.1.1.2.5.1.1
The slot number containing this module. An unique value, in the range between 0 and and the value of chNumSlots.
chSlotCompID .1.3.6.1.4.1.52.4.1.1.2.5.1.2
The ID value for the component incorporated within this module. This object is similar to chCompID.
chSlotClass .1.3.6.1.4.1.52.4.1.1.2.5.1.3
The class (or type) of slot. For example, slots that only allow for power supply modules fall into a class that is different from slots that allow only interface cards.
chSlotModuleType .1.3.6.1.4.1.52.4.1.1.2.5.1.4
Uniquely defines the module type. A vendor's authoritative identification for a module. By convention, this value is allocated within the SMI enterprises subtree(1.3.6.1.4.1), and provides an easy and unambiguous means for determining the type of module.
chSlotModuleName .1.3.6.1.4.1.52.4.1.1.2.5.1.5
A textual description of the module.
chSlotModuleVersion .1.3.6.1.4.1.52.4.1.1.2.5.1.6
A textual description of the version/revision level for this module's hardware and firmware.
chSlotModuleTimeStamp .1.3.6.1.4.1.52.4.1.1.2.5.1.7
The value of sysUpTime for this management entity, when this module was last (re-)initialized.
chCompMIBID .1.3.6.1.4.1.52.4.1.1.2.6.1.1
An unique value identifying an instance of a MIB.
chCompMIBSlotID .1.3.6.1.4.1.52.4.1.1.2.6.1.2
The slot number for the module that incorporates this MIB. The value shall be in the range between 0 and chNumSlots. A non-zero values indicates that the information presented by this entry is realized only on the module in the specified slot. A zero value indicates that this information pertains to the entire component, without partitioning across modules. This object is similar to chSlotID.
chCompMIBCompID .1.3.6.1.4.1.52.4.1.1.2.6.1.3
The component related to this MIB. This object is similar to chCompID.
chCompMIBGrpOID .1.3.6.1.4.1.52.4.1.1.2.6.1.4
A reference to a specific MIB group definition. For example, in the case of MIB-II, the value of this object may refer to an applicable group, which has been implemented. The access is read-write. This will allow network administrators, to register MIBs for a module that is known to the chassis management entity, by type alone: that is, a module for which component information is unknown.
chCompMIBVectorObjectBase .1.3.6.1.4.1.52.4.1.1.2.6.1.5
A reference to a specific entry of a vector object within this MIB, associated with the module identified by chCompMIBSlotID. For example, in the case of a repeater, the value of this object may refer to an entry in prtrBasicPortTable. This object facilitates logical to physical mapping of entities such as channels, links, interfaces, and ports.
chCompMIBVectorNum .1.3.6.1.4.1.52.4.1.1.2.6.1.6
A value indicating the number of entries, starting with the one denoted by chCompMIBVectorObjectBase, that are realized on this module.
chCompMIBType .1.3.6.1.4.1.52.4.1.1.2.6.1.7
Depicts whether the MIB in question is instanced or not. For reason similar to ones that apply to chCompMIBGrpOID, the access mode is read-write.
chCompMIBStatus .1.3.6.1.4.1.52.4.1.1.2.6.1.8
Depicts the status of the MIB. If marked as agent the MIB is generated based upon the components defined. If marked as management the entry was entered via a management station. If marked invalid the entry is to be deleted.
Table
chBackplaneTable .1.3.6.1.4.1.52.4.1.1.2.2
A list of backplanes resident in this chassis.
chCompTable .1.3.6.1.4.1.52.4.1.1.2.4
A list of components installed in this chassis.
chSlotTable .1.3.6.1.4.1.52.4.1.1.2.5
A list of modules installed in this chassis. A component, such as a router, may be incorporated on one or more modules. More than one component may be incorporated on each module.
chCompMIBTable .1.3.6.1.4.1.52.4.1.1.2.6
A list of MIBs incorporated on components and their respective modules, within this chassis.