MOXA-NP6000-MIB :: deviceControlMaxConnection

MIB Reference — IPNetwork Monitor · Updated October 06, 2026

All MIBs › MOXA-NP6000-MIB › deviceControlMaxConnection

deviceControlMaxConnection

Module: MOXA-NP6000-MIB

OID (symbolic): MOXA-NP6000-MIB::deviceControlMaxConnection

OID (numeric): 1.3.6.1.4.1.8691.2.8.1.4.1.2.1.1.1.2

Node type: OBJECT-TYPE

Type: INTEGER

Access: read-write

Description: Max connection is usually used when the user needs to receive data from different hosts simultaneously. The factory default is 1. In this case, only one specific host can access this port of the NPort 6000 series device server, and the Real COM driver on that host will have full control over the port. Max. connection = 1: Allows only a single hosts Real COM driver to open the specific NPort 6000 series device servers serial port. Max connection = 2 to 8: Allows 2 to 8 hosts Real COM drivers to open the specific NPort 6000 series device servers serial port, at the same time. When multiple hosts Real COM drivers open the serial port at the same time, the COM driver only provides a pure data tunnel without control ability. The serial port parameter will use the firmware settings instead of getting the settings from your application program (AP).

What is deviceControlMaxConnection?

Sets how many hosts' Real COM drivers may open this serial port at once, from 1 (the factory default, giving one host exclusive control including the port's baud rate/parity settings) up to 8 (a shared raw data tunnel without per-host control). An admin raises it only when several applications genuinely need to read the same serial stream simultaneously.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.8691.2.8.1.4.1.2.1.1.1.2
snmpwalk -v2c -c public <target> MOXA-NP6000-MIB::deviceControlMaxConnection

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.8691.2.8.1.4.1.2.1.1.1.2.1
snmpget -v2c -c public <target> MOXA-NP6000-MIB::deviceControlMaxConnection.1

Set instance 1 (SNMPv2c):

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

SNMPv3 example:

snmpget -v3 -l authPriv -u snmpv3-user -a SHA -A "AuthPassword1" -x AES -X "PrivPassword1" <target> deviceControlMaxConnection.1

Start monitoring Moxa NPort 6000 series secure serial device server with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the MOXA-NP6000-MIB::deviceControlMaxConnection OID value, configure state conditions and alerts, and monitor any Moxa NPort 6000 series secure serial device server 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.4privateAirPair-MIB
1.3.6.1.4.1enterprisesAirPair-MIB
1.3.6.1.4.1.8691moxaMOXA-CN2600-MIB
1.3.6.1.4.1.8691.2nportMOXA-CN2600-MIB
Numeric OIDNameModule
1.3.6.1.4.1.8691.2.8np6000MOXA-NP6000-MIB
1.3.6.1.4.1.8691.2.8.1swMgmtMOXA-NP6000-MIB
1.3.6.1.4.1.8691.2.8.1.4portSettingMOXA-NP6000-MIB
1.3.6.1.4.1.8691.2.8.1.4.1opModeSettingMOXA-NP6000-MIB
1.3.6.1.4.1.8691.2.8.1.4.1.2applicationMOXA-NP6000-MIB
1.3.6.1.4.1.8691.2.8.1.4.1.2.1deviceControlMOXA-NP6000-MIB
1.3.6.1.4.1.8691.2.8.1.4.1.2.1.1deviceControlTableMOXA-NP6000-MIB
1.3.6.1.4.1.8691.2.8.1.4.1.2.1.1.1deviceControlEntryMOXA-NP6000-MIB
1.3.6.1.4.1.8691.2.8.1.4.1.2.1.1.1.2deviceControlMaxConnectionMOXA-NP6000-MIB