CHIPNET-MIB

All MIBs › CHIPNET-MIB

Category: Vendor: 3Com

Description: Provides general network management objects for Chipcom (3Com) network devices in campus LAN environments.

Start monitoring vendor-neutral, standards-based MIB, any SNMPv3-capable network device (SNMP engine identity/boot/clock status) 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.

What Is CHIPNET-MIB?

CHIPNET-MIB is a legacy proprietary MIB (enterprise OID 49) reporting physical-backplane-to-logical-network allocation on a modular chassis, used to determine remaining backplane capacity for future network growth. Its data-path table, keyed by data path, records the associated network ID, while a security-MAC table records slot/port index, MAC address, mode, and status for MAC-based port security. As a configuration/status MIB it lets an administrator confirm how much backplane capacity remains for new networks and audit MAC-based port-security bindings. It is deployed on legacy modular chassis equipment implementing this private MIB. Engineers can download the CHIPNET-MIB file directly to load it into their MIB browser.

IPNetwork Monitor allows you to monitor SNMP objects defined in CHIPNET-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

Legacy modular chassis equipment (enterprise OID 49)

Monitoring Examples

An administrator checks olNetDPTable to confirm remaining backplane capacity before provisioning a new logical network on this legacy modular chassis.

What Can Be Monitored

backplane-to-network allocation and MAC-based port security

Imported Objects

From RFC-1212

OBJECT-TYPE

From RFC1155-SMI

Counter
DisplayString
Gauge
IpAddress
NetworkAddress
TimeTicks
enterprises

OIDs

OID symbolic	OID numeric	Type	Access	Description
alarmGroup	1.3.6.1.4.1.49.2.3.4.7
boardGroup	1.3.6.1.4.1.49.2.3.4.5
chipBridge	1.3.6.1.4.1.49.2.3.6
chipcom	1.3.6.1.4.1.49
chipDownload	1.3.6.1.4.1.49.2.7
chipEcho	1.3.6.1.4.1.49.2.2
chipExperiment	1.3.6.1.4.1.49.2.4
chipExpTokenRing	1.3.6.1.4.1.49.2.4.1
chipGen	1.3.6.1.4.1.49.2.1
chipmib02	1.3.6.1.4.1.49.2
chipProducts	1.3.6.1.4.1.49.2.3
chipTFTP	1.3.6.1.4.1.49.2.6
chipTTY	1.3.6.1.4.1.49.2.5
dot1dBridge	1.3.6.1.4.1.49.2.4.14
dot5	1.3.6.1.4.1.49.2.4.1.1
emm	1.3.6.1.4.1.49.2.3.5
fmm	1.3.6.1.4.1.49.2.3.8
focus1	1.3.6.1.4.1.49.2.3.9
hardwareGroup	1.3.6.1.4.1.49.2.3.4.2
hubGroup	1.3.6.1.4.1.49.2.3.4.4
hubSysGroup	1.3.6.1.4.1.49.2.3.4.1
midnight	1.3.6.1.4.1.49.2.3.3
oebm	1.3.6.1.4.1.49.2.3.2
oeim	1.3.6.1.4.1.49.2.3.10
ol50nnMCTL	1.3.6.1.4.1.49.2.3.1.4.4.3
ol50nnMHCTL	1.3.6.1.4.1.49.2.3.1.4.4.33
ol50nnMRCTL	1.3.6.1.4.1.49.2.3.1.4.4.23
ol51nnBEE	1.3.6.1.4.1.49.2.3.1.4.4.9
ol51nnIx	1.3.6.1.4.1.49.2.3.1.4.4.31
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
ol51nnMBNC	1.3.6.1.4.1.49.2.3.1.4.4.8
ol51nnMFB	1.3.6.1.4.1.49.2.3.1.4.4.24
ol51nnMFBP	1.3.6.1.4.1.49.2.3.1.4.4.16
ol51nnMFIB	1.3.6.1.4.1.49.2.3.1.4.4.5
ol51nnMFL	1.3.6.1.4.1.49.2.3.1.4.4.22
ol51nnMFP	1.3.6.1.4.1.49.2.3.1.4.4.15
ol51nnMMGT	1.3.6.1.4.1.49.2.3.1.4.4.4
ol51nnMTP	1.3.6.1.4.1.49.2.3.1.4.4.7
ol51nnMTPCL	1.3.6.1.4.1.49.2.3.1.4.4.29
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
ol51nnMTS	1.3.6.1.4.1.49.2.3.1.4.4.21
ol51nnMUTP	1.3.6.1.4.1.49.2.3.1.4.4.6
ol51nnREE	1.3.6.1.4.1.49.2.3.1.4.4.11
ol51nnRES	1.3.6.1.4.1.49.2.3.1.4.4.10
ol5208MTP	1.3.6.1.4.1.49.2.3.1.4.4.14
ol52nnBTT	1.3.6.1.4.1.49.2.3.1.4.4.30
ol52nnMFR	1.3.6.1.4.1.49.2.3.1.4.4.20
ol52nnMMGT	1.3.6.1.4.1.49.2.3.1.4.4.32
ol52nnMTP	1.3.6.1.4.1.49.2.3.1.4.4.19
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
ol53nnMMGT	1.3.6.1.4.1.49.2.3.1.4.4.25
ol53nnMSTP	1.3.6.1.4.1.49.2.3.1.4.4.28
olAgents	1.3.6.1.4.1.49.2.3.1.1
olAlarm	1.3.6.1.4.1.49.2.3.1.7
olConc	1.3.6.1.4.1.49.2.3.1.2
olEnet	1.3.6.1.4.1.49.2.3.1.5.2
olEnv	1.3.6.1.4.1.49.2.3.1.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
olModules	1.3.6.1.4.1.49.2.3.1.4
olNet	1.3.6.1.4.1.49.2.3.1.5.1
INT 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.
olNetDPEntry	1.3.6.1.4.1.49.2.3.1.5.1.1.1		not-accessible	A list of information about each data path in the concentrator.
INT 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.
olNetDPTable	1.3.6.1.4.1.49.2.3.1.5.1.1		not-accessible	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.
olNets	1.3.6.1.4.1.49.2.3.1.5
MAC 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.
olNetSecurityMACEntry	1.3.6.1.4.1.49.2.3.1.5.1.2.1		not-accessible	A list of security configuration parameters and MAC addresses associated with each port with security configured in the concentrator.
INT 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.
INT 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.
INT 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.
INT 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.
olNetSecurityMACTable	1.3.6.1.4.1.49.2.3.1.5.1.2		not-accessible	A table of security configuration parameters and MAC addresses associated with every port with security configured in the concentrator.
olSpecMods	1.3.6.1.4.1.49.2.3.1.4.4
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
olTRnet	1.3.6.1.4.1.49.2.3.1.5.3
online	1.3.6.1.4.1.49.2.3.1
portGroup	1.3.6.1.4.1.49.2.3.4.6
softwareGroup	1.3.6.1.4.1.49.2.3.4.3
trmm	1.3.6.1.4.1.49.2.3.7
workGroupHub	1.3.6.1.4.1.49.2.3.4

RFC description

Manages Chipcom networking devices including Ethernet modules and Token Ring modules.

Start monitoring Chipcom (3Com) Ethernet/Token Ring switching hub or LAN concentrator (legacy) 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.

Download CHIPNET-MIB

What Is CHIPNET-MIB?

Supported Devices

Monitoring Examples

What Can Be Monitored

This MIB depends on

Related MIBs

RFC description