SCTE-HMS-QAM-MIB :: qamChannelInterleaverMode

MIB Reference — IPNetwork Monitor · Updated October 06, 2026

All MIBs › SCTE-HMS-QAM-MIB › qamChannelInterleaverMode

qamChannelInterleaverMode

Module: SCTE-HMS-QAM-MIB

OID (symbolic): SCTE-HMS-QAM-MIB::qamChannelInterleaverMode

OID (numeric): 1.3.6.1.4.1.5591.1.11.5.3.1.1.1.1.4

Node type: OBJECT-TYPE

Type: QAMChannelInterleaveMode

Access: read-only

Description: The interleaving depth or operation mode of the interleaver. 'taps8Increment16': protection 5.9/4.1 usec, latency .22/.15 msec 'taps16Increment8': protection 12/8.2 usec, latency .48/.33 msec 'taps32Increment4': protection 24/16 usec, latency .98/.68 msec 'taps64Increment2': protection 47/33 usec, latency 2/1.4 msec 'taps128Increment1': protection 95/66 usec, latency 4/2.8 msec 'taps12increment17': protection 18/14 usec, latency 0.43/0.32 msec 'taps128increment2': protection 190/132 usec, latency 8/5.6 msec 'taps128increment3': protection 285/198 usec, latency 12/8.4 msec 'taps128increment4': protection 380/264 usec, latency 16/11 msec 'taps128increment5': protection 475/330 usec, latency 20/14 msec 'taps128increment6': protection 570/396 usec, latency 24/17 msec 'taps128increment7: protection 664/462 usec, latency 28/20 msec 'taps128increment8': protection 759/528 usec, latency 32/22 msec

The value 'taps12increment17' is supported by EuroDOCSIS cable systems only, and the others by DOCSIS cable systems.

If the QAM chammel interface is down, this object either returns the configured value, or the value of 'unknown'. The value of 'other' is returned if the interleave is known but not defined in the above list.

When the qamChannelInterleaverLevel is set to 'level 1', a single interleaving depth is supported, namely 'taps128Increment1'.

When the qamChannelInterleaverLevel is set to 'level2', all the other interleaving depths are also supported.

What is qamChannelInterleaverMode?

This read-only object reports the specific interleaver depth/increment mode, such as taps128Increment1, in use on a QAM channel, each with documented protection-time and latency tradeoffs per the source description. Admins use this to understand the exact noise-burst protection and added latency currently configured for that channel. For example, seeing taps128Increment1 configured, with its documented ~95 microsecond burst protection and ~4 millisecond latency, tells the admin this channel is tuned for maximum burst-noise resilience at the cost of higher delay.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.5591.1.11.5.3.1.1.1.1.4
snmpwalk -v2c -c public <target> SCTE-HMS-QAM-MIB::qamChannelInterleaverMode

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.5591.1.11.5.3.1.1.1.1.4.1
snmpget -v2c -c public <target> SCTE-HMS-QAM-MIB::qamChannelInterleaverMode.1

Start monitoring cable headend QAM modulator, vendor-neutral SCTE HMS standard (per-channel RF frequency/power status) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the SCTE-HMS-QAM-MIB::qamChannelInterleaverMode OID value, configure state conditions and alerts, and monitor any cable headend QAM modulator, vendor-neutral SCTE HMS standard (per-channel RF frequency/power status) from a single console.

OID Breakdown

Upper-level ancestors (10 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.5591scteRootSCTE-ROOT
1.3.6.1.4.1.5591.1scteHmsTreeSCTE-ROOT
1.3.6.1.4.1.5591.1.11insidePlantIdentSCTE-HMS-ROOTS
1.3.6.1.4.1.5591.1.11.5heDigitalSCTE-HMS-HEADENDIDENT-MIB
Numeric OIDNameModule
1.3.6.1.4.1.5591.1.11.5.3.1heDigitalQamMIBSCTE-HMS-QAM-MIB
1.3.6.1.4.1.5591.1.11.5.3.1.1qamMIBObjectsSCTE-HMS-QAM-MIB
1.3.6.1.4.1.5591.1.11.5.3.1.1.1qamChannelTableSCTE-HMS-QAM-MIB
1.3.6.1.4.1.5591.1.11.5.3.1.1.1.1qamChannelEntrySCTE-HMS-QAM-MIB
1.3.6.1.4.1.5591.1.11.5.3.1.1.1.1.4qamChannelInterleaverModeSCTE-HMS-QAM-MIB