CDD-564 :: cdd564WorkingMode

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsCDD-564cdd564WorkingMode

cdd564WorkingMode

Module: CDD-564

OID (symbolic): CDD-564::cdd564WorkingMode

OID (numeric): 1.3.6.1.4.1.6247.25.1.1.2.6

Node type: OBJECT-TYPE

Type: INTEGER

Access: read-write

Description: Configure the system's working mode.

The CDM-IP can operate in any of these modes.

1. Router - Small Network Mode - The system functions as router and uses the route table to determine how to forward packets in a small network HDLC address mode. The HDLC packet uses a 1 byte HDLC address. The valid values are from 1 to 254 (0x1 - 0xFE).

2. Router - Small Network Mode - The system functions as router and uses the route table to determine how to forward packets in a large network HDLC address mode. The HDLC packet uses a 2- byte HDLC address. The valid values are from 1 to 32766 (0x1 - 0x7FFE).

3. Router - Point To Point Mode - The system functions as router but does not use HDLC addresses.

4. Router - Vipersat Mode - The system functions as router and is configured to work in a Vipersat network.

*** IMPORTANT NOTE *** Changing Working mode requires the system to reboot. System configuration is saved before rebooting.

Please make sure you are setting the correct value.

What is cdd564WorkingMode?

This selects the overall routing and addressing architecture of the satellite link, notably switching between a 1-byte HDLC address space (small network mode, addressing up to 254 remote sites) and a 2-byte space (large network mode, addressing up to roughly 32,766 remotes), plus dedicated point-to-point and Vipersat variants. Because the addressing scheme is tied directly to the projected number of remote sites, this choice is normally locked in at network design time -- picking routerSmallNetworkMode(1) for a network that later grows past 254 sites forces a disruptive re-addressing migration to large-network mode down the road. For example, a network planned to eventually exceed 254 remote terminals would be built on routerLargeNetworkMode(2) from the outset to avoid that later migration entirely.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.6247.25.1.1.2.6
snmpwalk -v2c -c public <target> CDD-564::cdd564WorkingMode

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.6247.25.1.1.2.6.1
snmpget -v2c -c public <target> CDD-564::cdd564WorkingMode.1

Set instance 1 (SNMPv2c):

snmpset -v2c -c private <target> 1.3.6.1.4.1.6247.25.1.1.2.6.1 i <value>

Start monitoring Comtech EF Data CDD-564 satellite demodulator with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the CDD-564::cdd564WorkingMode OID value, configure state conditions and alerts, and monitor any Comtech EF Data CDD-564 satellite demodulator from a single console.

OID Breakdown

Upper-level ancestors (7 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.6247comtechEFDataComtechEFData
Numeric OIDNameModule
1.3.6.1.4.1.6247.25cdd564CDD-564
1.3.6.1.4.1.6247.25.1cdd564ObjectsCDD-564
1.3.6.1.4.1.6247.25.1.1cdd564AdministrationCDD-564
1.3.6.1.4.1.6247.25.1.1.2cdd564FeaturesCDD-564
1.3.6.1.4.1.6247.25.1.1.2.6cdd564WorkingModeCDD-564