All MIBs › C-PRODUCT-GROUP-MIB
Category: Hardware Inventory
Description:
Manages group and chassis-level configuration across C-PRODUCT multi-slot platforms.
Imported Objects
From A3Com-products-MIB
| atmAccess | OBJECT-IDENTITY |
What Is C-PRODUCT-GROUP-MIB?
C-PRODUCT-GROUP-MIB manages group- and chassis-level configuration across the "C-PRODUCT" family of multi-slot platforms, appearing to be an enterprise MIB for a modular networking chassis line whose members are named directly as OID nodes (access9600, access9300, access9100, and mojave). It exposes configuration objects that tie individual chassis/product variants into a shared management-group structure rather than granular runtime counters. Because module_desc is empty, no specific hardware/software status objects such as uptime, temperature, or CPU load are confirmed by name, though the group/config framing suggests it underlies platform identification consumed by monitoring performed elsewhere in the C-PRODUCT MIB suite. It relies on sibling C-PRODUCT MIB modules for the actual chassis physical-status objects. It is deployed on multi-slot chassis-based access/aggregation platforms identified by product codes like access9600, access9300, and access9100, and a C-PRODUCT-GROUP-MIB SNMP walk against a live shelf returns only these registration/grouping nodes rather than counters.
IPNetwork Monitor allows you to monitor SNMP objects defined in C-PRODUCT-GROUP-MIB. Use the built-in SNMP Monitoring Browser to explore available variables, view their current values and descriptions, and select the objects you want to monitor. You can then create SNMP monitors, configure thresholds, and receive alerts when monitored values change.
Supported Devices
- C-PRODUCT multi-slot chassis platforms (access9600/access9300/access9100/mojave series)
Monitoring Examples
The sample objects config, access9600, access9300, access9100, mojave, and c-product read as registration/grouping nodes distinguishing which chassis product variant is being managed, rather than pollable counters. An admin would use these nodes to determine which product-specific config subtree applies to a given chassis (for example access9600 versus access9300) before drilling into that product's own status objects. No concrete counter-level monitoring example can be given honestly since no leaf/runtime objects were provided.
OIDs
| OID symbolic | OID numeric | Type | Access | Description |
|---|---|---|---|---|
| config | 1.3.6.1.4.1.43.1.12.3.1 | |||
| c_product | 1.3.6.1.4.1.43.1.12.3.1.1 | |||
| sys | 1.3.6.1.4.1.43.1.12.3.1.1.1 | |||
| shelf | 1.3.6.1.4.1.43.1.12.3.1.1.2 | |||
| card | 1.3.6.1.4.1.43.1.12.3.1.1.3 | |||
| port | 1.3.6.1.4.1.43.1.12.3.1.1.4 | |||
| circuit | 1.3.6.1.4.1.43.1.12.3.1.1.5 | |||
| fault | 1.3.6.1.4.1.43.1.12.3.1.1.6 | |||
| ds3card | 1.3.6.1.4.1.43.1.12.3.1.1.11 | |||
| qsim | 1.3.6.1.4.1.43.1.12.3.1.1.12 | |||
| e3card | 1.3.6.1.4.1.43.1.12.3.1.1.13 | |||
| hssicard | 1.3.6.1.4.1.43.1.12.3.1.1.14 | |||
| cbr | 1.3.6.1.4.1.43.1.12.3.1.1.15 | |||
| oc3card | 1.3.6.1.4.1.43.1.12.3.1.1.16 | |||
| enetcard | 1.3.6.1.4.1.43.1.12.3.1.1.17 | |||
| mcpu | 1.3.6.1.4.1.43.1.12.3.1.1.18 | |||
| ima | 1.3.6.1.4.1.43.1.12.3.1.1.19 | |||
| ctx | 1.3.6.1.4.1.43.1.12.3.1.1.20 | |||
| access9600 | 1.3.6.1.4.1.43.1.12.3.2 | |||
| access9300 | 1.3.6.1.4.1.43.1.12.3.3 | |||
| access9100 | 1.3.6.1.4.1.43.1.12.3.4 | |||
| mojave | 1.3.6.1.4.1.43.1.12.3.5 |
RFC description
Vendor product group MIB defining managed object collections for a specific product family.
Start monitoring Networking equipment with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.