CNT242-MIB :: cnt2sctRxMsgs2

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsCNT242-MIBcnt2sctRxMsgs2

cnt2sctRxMsgs2

Module: CNT242-MIB

OID (symbolic): CNT242-MIB::cnt2sctRxMsgs2

OID (numeric): 1.3.6.1.4.1.333.2.4.2.5.1.11

Node type: OBJECT-TYPE

Type: Counter32

Access: read-only

Description: Receive message count.

What is cnt2sctRxMsgs2?

This Counter32 counts messages received on this subchannel entry, tracked here in the interface-indexed table. An administrator tracks this counter's growth to confirm this specific subchannel, reached via its ifIndex, is actively receiving traffic. For example, a flat cnt2sctRxMsgs2 count while cnt2sctTxMsgs2 on the same row keeps climbing shows this subchannel is currently one-way, transmit only.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.333.2.4.2.5.1.11
snmpwalk -v2c -c public <target> CNT242-MIB::cnt2sctRxMsgs2

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.333.2.4.2.5.1.11.1
snmpget -v2c -c public <target> CNT242-MIB::cnt2sctRxMsgs2.1

Start monitoring CNT Zeus ESCON channel-extension system (legacy) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the CNT242-MIB::cnt2sctRxMsgs2 OID value, configure state conditions and alerts, and monitor any CNT Zeus ESCON channel-extension system (legacy) from a single console.

How to Use in IPNetwork Monitor

Select a CNT Zeus ESCON channel-extension system (legacy) as the target host to create a monitor — the SNMP service should be up and running on it. Click New Monitor, then check SNMP Custom on the Favorites tab, click Next, and confirm the host. On the next page, click Select... to open the built-in SNMP MIB Browser and type cnt2sctRxMsgs2 into the Find box to locate it in the OID tree, selecting the specific row/instance you want to monitor since this is a table column, then select it and click OK. It reports the receive message count. On the monitor's Main parameters page you can set the target's SNMP port (default 161), credentials, polling interval, and other settings — see the SNMP Monitor help for details. On the State conditions and Alerting tabs, configure when the monitor should change state and trigger an alert; since this is a Counter32-type OID, Value bounds is the most useful condition here — trigger an alert if the counter increases sharply between polls relative to its normal baseline, since an unexpected spike often reflects a real change in traffic or activity. Click Finish to create the monitor; you can adjust any parameter later.

OID Breakdown

Upper-level ancestors (9 from the standard OID tree / other modules)
Numeric OIDNameModule
1isoLANART-AGENT
1.3orgAirPair-MIB
1.3.6dodAirPair-MIB
1.3.6.1internetAirPair-MIB
1.3.6.1.4privateAirPair-MIB
1.3.6.1.4.1enterprisesAirPair-MIB
1.3.6.1.4.1.333cntCNT2-MIB
1.3.6.1.4.1.333.2cnt2CNT2-MIB
1.3.6.1.4.1.333.2.4cnt2SubagentCNT2-MIB
Numeric OIDNameModule
1.3.6.1.4.1.333.2.4.2cnt2EsconCNT242-MIB
1.3.6.1.4.1.333.2.4.2.5cnt2SubChanTable2CNT242-MIB
1.3.6.1.4.1.333.2.4.2.5.1cnt2subchanEntry2CNT242-MIB
1.3.6.1.4.1.333.2.4.2.5.1.11cnt2sctRxMsgs2CNT242-MIB