ERI-DNX-NEST-SYS-MIB :: dbSyncCmdStatus

MIB Reference — IPNetwork Monitor · Updated October 05, 2026

All MIBs › ERI-DNX-NEST-SYS-MIB › dbSyncCmdStatus

dbSyncCmdStatus

Module: ERI-DNX-NEST-SYS-MIB

OID (symbolic): ERI-DNX-NEST-SYS-MIB::dbSyncCmdStatus

OID (numeric): 1.3.6.1.4.1.644.2.4.1.12.1.2.4

Node type: OBJECT-TYPE

Type: INTEGER

Access: read-write

Description: The command status for this DB Synchronization. The value used in a SET will be replaced by a response value in the GET RESPONSE indicating success or failure.

Default Response State used in GET RESPONSE Command ready-for-command (0) initial default status for a row

DB Sync Commands used in SET Command (1..99) update (1) Change the auto sync mode startDBSync (2) Starts the DB synchronization process

Response States used in GET RESPONSE Command (100..199) update-successful (101) Auto Sync data has been successfully changed sync-start-successful (102) DB Sync process has been successfully started sync-completed-successful (120) DB Sync process has been successfully finished

DB Sync Error Codes used in GET RESPONSE Command (200..799) err-gen-dbsync-cfg-error (200) Unknown DB Sync configuration error occurred. err-standby-not-present (201) DB Synchronization cannot be started without standby systemManager Device. err-dbsync-failed (202) DB Synchronization process has failed err-invalid-dbsync-command (203, Unrecognized DB Sync command action err-invalid-dbsync-mode (204) Unrecognized auto sync setting err-data-locked-by-another-user (450) Another administrative user is making changes to this part of the system via a terminal session. Check Event Log for user name err-snmp-parse-failed (500) Agent could not parse variable err-invalid-snmp-type (501) Variable ASN type does not match Agent defined type err-invalid-snmp-var-size (502) Variable size is too big

What is dbSyncCmdStatus?

A command/response object used to control database synchronization: an admin sets it to update(1) to change the auto-sync mode or startDBSync(2) to kick off a manual sync, and the agent overwrites it with a response code such as sync-completed-successful(120) or an error like err-standby-not-present(201) if there's no standby System Manager to sync with.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.644.2.4.1.12.1.2.4
snmpwalk -v2c -c public <target> ERI-DNX-NEST-SYS-MIB::dbSyncCmdStatus

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.644.2.4.1.12.1.2.4.1
snmpget -v2c -c public <target> ERI-DNX-NEST-SYS-MIB::dbSyncCmdStatus.1

Set instance 1 (SNMPv2c):

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

Start monitoring Eastern Research Inc. DNX-88/DNX-11 nest multiplexer chassis (slot/redundancy administration) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the ERI-DNX-NEST-SYS-MIB::dbSyncCmdStatus OID value, configure state conditions and alerts, and monitor any Eastern Research Inc. DNX-88/DNX-11 nest multiplexer chassis (slot/redundancy administration) from a single console.

OID Breakdown

Upper-level ancestors (12 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.644eriEnterpriseRootERI-ROOT-SMI
1.3.6.1.4.1.644.2eriProductsERI-ROOT-SMI
1.3.6.1.4.1.644.2.4dnxERI-DNX-SMC-MIB
1.3.6.1.4.1.644.2.4.1sysMgrERI-DNX-SMC-MIB
1.3.6.1.4.1.644.2.4.1.12utilitiesERI-DNX-SMC-MIB
1.3.6.1.4.1.644.2.4.1.12.1databaseERI-DNX-SMC-MIB
Numeric OIDNameModule
1.3.6.1.4.1.644.2.4.1.12.1.2dbSyncronizeERI-DNX-NEST-SYS-MIB
1.3.6.1.4.1.644.2.4.1.12.1.2.4dbSyncCmdStatusERI-DNX-NEST-SYS-MIB