RFC1232-MIB :: ds1ZeroCoding

MIB Reference — IPNetwork Monitor · Updated October 06, 2026

All MIBs › RFC1232-MIB › ds1ZeroCoding

ds1ZeroCoding

Module: RFC1232-MIB

OID (symbolic): RFC1232-MIB::ds1ZeroCoding

OID (numeric): 1.3.6.1.2.1.10.18.1.1.6

Node type: OBJECT-TYPE

Type: INTEGER

Access: read-only

Description: This variable describes the variety of Zero Code Suppression used on the link, which in turn affects a number of its characteristics.

ds1JammedBit refers the Jammed bit Zero Encoding, in which the AT&T specification of at least one pulse every 8 bit periods is literally implemented by forcing a pulse in bit 8 of each channel. Thus, only seven bits per channel, or 1.344 Mbps, is available for data.

ds1B8ZS refers to the use of a specified pattern of normal bits and bipolar violations which are used to replace a sequence of eight zero bits (see [14]). In this context, all eight bits in a channel are technically available for data, but care must be taken with D4 encoded data to avoid having HDLC Flag streams imitate spurious Yellow Alarm conditions. Typically, one bit per frame is ignored to force flag streams to rotate, thereby avoiding this error type. CCITT Recommendation G.703 [11] may be referred to for further definition of these.

ds1InvertedHDLC refers to the practice, common on HDLC encoded DS1 data links, of inverting the data between the serial interface chip and the CSU. Since HDLC guarantees one zero every 6 bits in the worst case, while the standards call for (in effect) at least one pulse every eight, inverted HDLC enjoys 4/24 one's density on the line, which may improve the effective clock stability of a DS1 line. As with B8ZS, all eight bits in a channel are technically available for data, but care must be taken with D4 encoded data to avoid having HDLC Flag streams imitate spurious Yellow Alarm conditions. Typically, one bit per frame is ignored to force flag streams to rotate, thereby avoiding this error type.

ANSI Clear Channels may use ds1ZBTSI, or Zero Byte Time Slot Interchange (see [14]).

G.704 links, with or without CRC, use ds1HDB3 (see [11]).

What is ds1ZeroCoding?

Reports the zero-code suppression scheme used on this DS1 link, such as B8ZS or HDB3, which affects how many bits per channel are actually usable for data and how the line avoids long runs of zeros.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.2.1.10.18.1.1.6
snmpwalk -v2c -c public <target> RFC1232-MIB::ds1ZeroCoding

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.2.1.10.18.1.1.6.1
snmpget -v2c -c public <target> RFC1232-MIB::ds1ZeroCoding.1

Start monitoring vendor-neutral, standards-based MIB, WAN routers and CSU/DSU equipment with T1/E1 interfaces with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the RFC1232-MIB::ds1ZeroCoding OID value, configure state conditions and alerts, and monitor any vendor-neutral, standards-based MIB, WAN routers and CSU/DSU equipment with T1/E1 interfaces from a single console.

OID Breakdown

Upper-level ancestors (8 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.2mgmtAPERTUS-NPG-MIB
1.3.6.1.2.1mib_2AXON-MIB
1.3.6.1.2.1.10transmissionCHECKPOINT-MIB-2
1.3.6.1.2.1.10.18ds1DS1-MIB
Numeric OIDNameModule
1.3.6.1.2.1.10.18.1ds1ConfigTableRFC1232-MIB
1.3.6.1.2.1.10.18.1.1ds1ConfigEntryRFC1232-MIB
1.3.6.1.2.1.10.18.1.1.6ds1ZeroCodingRFC1232-MIB