TELDAT-MON-PROTOCOL-NAT-MIB :: telProdNpMonProtIPNATConnType

MIB Reference — IPNetwork Monitor · Updated September 21, 2026

All MIBs › TELDAT-MON-PROTOCOL-NAT-MIB › telProdNpMonProtIPNATConnType

telProdNpMonProtIPNATConnType

Module: TELDAT-MON-PROTOCOL-NAT-MIB

OID (symbolic): TELDAT-MON-PROTOCOL-NAT-MIB::telProdNpMonProtIPNATConnType

OID (numeric): 1.3.6.1.4.1.2007.4.1.2.3.1.10.1.1.2

Node type: OBJECT-TYPE

Type: INTEGER

Access: read-only

Description: The type of connection of the NAT router. It can be a clear connection, normal (1) or a non clear connection, that needs to perform more translations in the data side of the packet. In case of static NAT, only control of FTP connections with the following features belong to this class: client in local domain and server in global domain and PORT commands trasnmitted with a change in packet length, ftp(2). The only connections that generate an entry to this table are the control of FTP connections

What is telProdNpMonProtIPNATConnType?

This value classifies the tracked NAT connection as either a plain translated flow, normal(1), or an FTP control connection, ftp(2), that needs extra data-side translation. It matters because only FTP control sessions with a local client and global-domain server whose PORT commands change packet length are singled out this way, while normal(1) covers everything else. For example, a value of ftp(2) flags an active FTP control session whose embedded PORT commands the router is rewriting during translation.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.2007.4.1.2.3.1.10.1.1.2
snmpwalk -v2c -c public <target> TELDAT-MON-PROTOCOL-NAT-MIB::telProdNpMonProtIPNATConnType

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.2007.4.1.2.3.1.10.1.1.2.1
snmpget -v2c -c public <target> TELDAT-MON-PROTOCOL-NAT-MIB::telProdNpMonProtIPNATConnType.1

Start monitoring Teldat router performing NAT (translation-binding/capacity status) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the TELDAT-MON-PROTOCOL-NAT-MIB::telProdNpMonProtIPNATConnType OID value, configure state conditions and alerts, and monitor any Teldat router performing NAT (translation-binding/capacity status) 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.2007teldatTELDAT-MIB
1.3.6.1.4.1.2007.4telproductsTELDAT-MIB
1.3.6.1.4.1.2007.4.1telProductsNucleoxTELDAT-SW-STRUCTURE-MIB
1.3.6.1.4.1.2007.4.1.2telProductsNpMonitTELDAT-SW-STRUCTURE-MIB
1.3.6.1.4.1.2007.4.1.2.3telProdNpMonProtocolsTELDAT-SW-STRUCTURE-MIB
1.3.6.1.4.1.2007.4.1.2.3.1telProdNpMonProtIPTELDAT-SW-STRUCTURE-MIB
Numeric OIDNameModule
1.3.6.1.4.1.2007.4.1.2.3.1.10telProdNpMonProtIPNATMonitTELDAT-MON-PROTOCOL-NAT-MIB
1.3.6.1.4.1.2007.4.1.2.3.1.10.1telProdNpMonProtIPNATConnTableTELDAT-MON-PROTOCOL-NAT-MIB
1.3.6.1.4.1.2007.4.1.2.3.1.10.1.1telProdNpMonProtIPNATConnEntryTELDAT-MON-PROTOCOL-NAT-MIB
1.3.6.1.4.1.2007.4.1.2.3.1.10.1.1.2telProdNpMonProtIPNATConnTypeTELDAT-MON-PROTOCOL-NAT-MIB