All MIBs › RAISECOM-NAT-MIB › natBindAction
natBindAction
Module: RAISECOM-NAT-MIB
OID (symbolic): RAISECOM-NAT-MIB::natBindAction
OID (numeric): 1.3.6.1.4.1.8886.15.1.1.2.8.1.17
Node type: OBJECT-TYPE
Type: RowStatus
Access: read-write
Description: A new static bind may be created or an existing one may be deleted by setting the multiple variable bindings of natBindProto and natBindAction. For example, to create a new static TCP bind of local host 192.168.10.10, local port 23, and global port 23, create a new oid natBindProto.192.168.10.23.0.0.0.0.23 and set it to 'tcp', and natBindAction.192.168.10.23.0.0.0.0.23 and set it to 'create and go'. Similarly, to delete the static bind, set natBindProto.23.0.0.0.0.23 to 'tcp' and natBindAction.192.168.10.23.0.0.0.0.23 to 'destroy'. To do this, your mib browser must be able to support multiple variable bindings access.
Note that you can create and delete only TCP and UDP static entries which apply only in NAPT mode.
What is natBindAction?
A RowStatus-typed control used together with natBindProto to create or delete a static NAT bind via SNMP; the DESCRIPTION gives a worked example of creating a static TCP bind for local host 192.168.10.10 port 23 by setting natBindProto to 'tcp' and natBindAction to 'createAndGo' on the matching indexed OID, noting only TCP and UDP static entries in NAPT mode can be managed this way.
Examples
Walk all instances (SNMPv2c):
snmpwalk -v2c -c public <target> 1.3.6.1.4.1.8886.15.1.1.2.8.1.17 snmpwalk -v2c -c public <target> RAISECOM-NAT-MIB::natBindAction
Get a specific instance (index 1):
snmpget -v2c -c public <target> 1.3.6.1.4.1.8886.15.1.1.2.8.1.17.1 snmpget -v2c -c public <target> RAISECOM-NAT-MIB::natBindAction.1
Set instance 1 (SNMPv2c):
snmpset -v2c -c private <target> 1.3.6.1.4.1.8886.15.1.1.2.8.1.17.1 s <value>
Start monitoring Raisecom gateway/CPE router or switch (NAT address mapping) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the RAISECOM-NAT-MIB::natBindAction OID value, configure state conditions and alerts, and monitor any Raisecom gateway/CPE router or switch (NAT address mapping) from a single console.
OID Breakdown
Upper-level ancestors (9 from the standard OID tree / other modules)
| Numeric OID | Name | Module |
|---|---|---|
| 1 | iso | LANART-AGENT |
| 1.3 | org | AirPair-MIB |
| 1.3.6 | dod | AirPair-MIB |
| 1.3.6.1 | internet | AirPair-MIB |
| 1.3.6.1.4 | private | AirPair-MIB |
| 1.3.6.1.4.1 | enterprises | AirPair-MIB |
| 1.3.6.1.4.1.8886 | raisecom | RAISECOM-BASE-MIB |
| 1.3.6.1.4.1.8886.15 | raisecomOptSysCommon | RAISECOM-BASE-MIB |
| 1.3.6.1.4.1.8886.15.1 | optSysMgmt | RAISECOM-BASE-MIB |
| Numeric OID | Name | Module |
|---|---|---|
| 1.3.6.1.4.1.8886.15.1.1 | raisecomNatMIB | RAISECOM-NAT-MIB |
| 1.3.6.1.4.1.8886.15.1.1.2 | natBind | RAISECOM-NAT-MIB |
| 1.3.6.1.4.1.8886.15.1.1.2.8 | natBindTable | RAISECOM-NAT-MIB |
| 1.3.6.1.4.1.8886.15.1.1.2.8.1 | natBindEntry | RAISECOM-NAT-MIB |
| 1.3.6.1.4.1.8886.15.1.1.2.8.1.17 | natBindAction | RAISECOM-NAT-MIB |