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 » CT-CONTAINER-MIB » Objects

CT-CONTAINER-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 CT-CONTAINER-MIB and use it to monitor vendor specific OID's.

CT-CONTAINER-MIB file content

Object view of CT-CONTAINER-MIB:

Scalar Object
contTypeDevice .1.3.6.1.4.1.52.4.1.1.9.1.1
Identifies the type of device or container. This could be a chassis, module, a standalone box etc. A vendor's authoritative identification of this device or container. 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 contUnknownTypeID, which is defined below.
contTypePhysicalEntries .1.3.6.1.4.1.52.4.1.1.9.1.2
Number of slots in the device. For bounded, slot-less systems, the value of this object shall be zero(0).
contTypePhysicalChanges .1.3.6.1.4.1.52.4.1.1.9.1.3
Depicts the number of physical changes that have occured to this MIB. This includes additions and removal of components in the component table.
contTypeLogicalChanges .1.3.6.1.4.1.52.4.1.1.9.1.4
Depicts the number of logical changes that have occured to this MIB. This includes all sets to name strings etc.
contTypeSerialNumber .1.3.6.1.4.1.52.4.1.1.9.1.5
Reflects the revision level of the device. If no serial number is available for the device then this object will be the zero length string.
contTypeContainingDevice .1.3.6.1.4.1.52.4.1.1.9.1.6
Identifies the type of device or container that this device or containeris installed or contained. A vendor's authoritative identification of this container 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' . 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.
contTypeContainingPhysicalEntries .1.3.6.1.4.1.52.4.1.1.9.1.7
Number of slots in the container in which the device is installed. For bounded, slot-less systems, the value of this object shall be zero(0).
contTypeContainingPhysicalEntryID .1.3.6.1.4.1.52.4.1.1.9.1.8
The slot number in a container in which the device is installed. If the slot number is unknown then this value will be zero.
contTypeContainingSerialNumber .1.3.6.1.4.1.52.4.1.1.9.1.9
Reflects the revision level of the device or container in which this device is installed. If no serial number is available for the device or container then this object will be the zero length string.
contLogicalEntry .1.3.6.1.4.1.52.4.1.1.9.2.1.1
A component entry containing objects for a particular component.
contPhysicalEntry .1.3.6.1.4.1.52.4.1.1.9.3.1.1
A slot entry containing objects for a particular module.
contLogicalToPhysicalMapEntry .1.3.6.1.4.1.52.4.1.1.9.3.2.1
A slot entry containing the objects for a particular module.
contResourceEntry .1.3.6.1.4.1.52.4.1.1.9.4.1.1
Defines a specific physical resource entry
contROCommStr .1.3.6.1.4.1.52.4.1.1.9.5.1
This is defined as the base read only community string to access MIBs in this container or on this module. A write to this object will change all instances of contLogicalEntryROCommStr.
contRWCommStr .1.3.6.1.4.1.52.4.1.1.9.5.2
This is defined as the read write community string to access MIBs in this container or on this module.A write to this object will change all instances of contLogicalEntryRWCommStr.
contSUCommStr .1.3.6.1.4.1.52.4.1.1.9.5.3
This is defined as the super user community string to access MIBs in this container or on this module.A write to this object will change all instances of contLogicalEntrySUCommStr.
contNetAddressEntry .1.3.6.1.4.1.52.4.1.1.9.6.1.1
An entry containing objects for a particular network address.
Tabular Object
contLogicalEntryID .1.3.6.1.4.1.52.4.1.1.9.2.1.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 container.
contLogicalEntryType .1.3.6.1.4.1.52.4.1.1.9.2.1.1.2
Identifies a component within this container. 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.
contLogicalEntryName .1.3.6.1.4.1.52.4.1.1.9.2.1.1.3
A textual description of the component.
contLogicalEntryVersion .1.3.6.1.4.1.52.4.1.1.9.2.1.1.4
A textual description of the version/revision level for this component's software.
contLogicalEntryROCommStr .1.3.6.1.4.1.52.4.1.1.9.2.1.1.5
This is defined as the read only community string to access MIBs registered to this component.
contLogicalEntryRWCommStr .1.3.6.1.4.1.52.4.1.1.9.2.1.1.6
This is defined as the read write community string to access MIBs registered to this component.
contLogicalEntrySUCommStr .1.3.6.1.4.1.52.4.1.1.9.2.1.1.7
This is defined as the super user community string to access MIBs registered to this component.
contLogicalEntryAdminStatus .1.3.6.1.4.1.52.4.1.1.9.2.1.1.8
contLogicalEntryOperStatus .1.3.6.1.4.1.52.4.1.1.9.2.1.1.9
contPhysicalEntryID .1.3.6.1.4.1.52.4.1.1.9.3.1.1.1
The slot number containing this module.
contPhysicalEntries .1.3.6.1.4.1.52.4.1.1.9.3.1.1.2
The number of slots that this module occupies. Some modules require more than one physical front panel slot while only using a single backpanel slot. In this case this object will reflect the number of slots occupied by the physical module. This object will have a value of 1 for all single slot modules.
contPhysicalEntryClass .1.3.6.1.4.1.52.4.1.1.9.3.1.1.3
The class (or type) of slot. For example, in a chassis slots that only allow for power supply modules fall into a class that is different from slots that allow only interface cards.
contPhysicalEntryType .1.3.6.1.4.1.52.4.1.1.9.3.1.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.
contPhysicalEntryTimeStamp .1.3.6.1.4.1.52.4.1.1.9.3.1.1.5
The value of sysUpTime for this management entity, when this module was last (re-)initialized.
contPhysicalEntryStatus .1.3.6.1.4.1.52.4.1.1.9.3.1.1.6
The module status.
contPhysicalEntryMapID .1.3.6.1.4.1.52.4.1.1.9.3.2.1.1
The slot number of a container slot. An unique value, in the range between 0 and and the value of containerNumSlots. This object is similiar to contPhysicalEntryID.
contLogicalEntryMapID .1.3.6.1.4.1.52.4.1.1.9.3.2.1.2
The ID value for the component incorporated within this module. This object is similar to contLogicalEntryID.
contResourceID .1.3.6.1.4.1.52.4.1.1.9.4.1.1.1
A unique index that defines a specific physcial resource for which this relationship exists.
contResourceType .1.3.6.1.4.1.52.4.1.1.9.4.1.1.2
Defines the type of physical resource for which this relationship is defined.
contResourceMibPointer .1.3.6.1.4.1.52.4.1.1.9.4.1.1.3
The value of this object defines the start of a MIB that can be used to determine more specific information about the given resource. This may include information about what physcial modules the resource is connected. It also may provide specific control information about the physcial resource. For example for a backplane the MIB may refer contain information on insert/bypass status of any given physical module.
contNetAddressIndex .1.3.6.1.4.1.52.4.1.1.9.6.1.1.1
An unique value identifying a network address.
contNetAddressNetworkType .1.3.6.1.4.1.52.4.1.1.9.6.1.1.2
Identifies the Network type e.g Inband, etc.
contNetAddress .1.3.6.1.4.1.52.4.1.1.9.6.1.1.3
Indicates the network address of the device for a particular network.
contNetAddressMask .1.3.6.1.4.1.52.4.1.1.9.6.1.1.4
Indicates the subnet mask for the network address of the device for a particular network
Table
contLogicalEntryTable .1.3.6.1.4.1.52.4.1.1.9.2.1
A list of components installed in this container.
contPhysicalEntryTable .1.3.6.1.4.1.52.4.1.1.9.3.1
A list of modules installed in this container. A component, such as a router, may be incorporated on one or more modules. More than one component may be incorporated on each module.
contLogicalToPhysicalMapTable .1.3.6.1.4.1.52.4.1.1.9.3.2
A list of components that reside in a container slot. More than one component may reside in a container slot.
contResourceTable .1.3.6.1.4.1.52.4.1.1.9.4.1
This table defines the potential physical resources that may be utilized by a given physical module within the container.
contNetAddressTable .1.3.6.1.4.1.52.4.1.1.9.6.1
A list of Global network addresses with which this device can be managed.
Object Identifier
contType .1.3.6.1.4.1.52.4.1.1.9.1
contLogical .1.3.6.1.4.1.52.4.1.1.9.2
contPhysical .1.3.6.1.4.1.52.4.1.1.9.3
contResource .1.3.6.1.4.1.52.4.1.1.9.4
contCommStr .1.3.6.1.4.1.52.4.1.1.9.5
contAddress .1.3.6.1.4.1.52.4.1.1.9.6
contTypeID .1.3.6.1.4.1.52.4.1.1.9.7
contUnknownTypeID .1.3.6.1.4.1.52.4.1.1.9.7.1