![background image](http://html1.mh-extra.com/html/3com/v6100/v6100_user-manual-manual_3139483373.webp)
V6100 and V7122 User Guide
373
SNMP NAT Traversal
A NAT placed between the gateway and the element manager calls for traversal solutions:
Trap source port – all traps are sent out from the SNMP port (default 161). A manager
receiving these traps can use the binding information (in the UDP layer) to traverse the
NAT back to the device.
The trap destination address (port and IP) are as configured in the snmpTargetMIB.
acKeepAliveTrap – this trap is designed to be a constant life signal from the device to the
manager allowing the manager NAT traversal at all times. The
acBoardTrapGlobalsAdditionalInfo1 varbind has the device’s serial number.
The destination port (i.e., the manager port for this trap) can be set to be different than
the port to which all other traps are sent. To do this, use the
acSysSNMPKeepAliveTrapPort object in the acSystem MIB or the
ini
file parameter
KeepAliveTrapPort.
The Trap is instigated in three ways:
Via
an
ini
file parameter (‘SendKeepAliveTrap = 1’). This ensures that the trap is
continuously sent. The frequency is set via the 9/10 of the
acSysSTUNBindingLifeTime object.
After the STUN client has discovered a NAT (any NAT).
If the STUN client cannot contact a STUN server.
The two latter options require the STUN client be enabled (EnableSTUN). Also,
once the acKeepAlive trap is instigated it does not stop.
The manager can see the NAT type in the MIB:
3Com(5003).acProducts(9).acBoardMibs(10).acSystem(10).acSystemStatus(2).
acSysNetwork(6).acSysNAT(2).acSysNATType(1)
The manger also has access to the STUN client configuration:
3Com(5003).acProducts(9).acBoardMibs(10).acSystem(10).acSystemConfiguration(1).a
cSysNetworkConfig(3).acSysNATTraversal(6).acSysSTUN(21)
acNATTraversalAlarm
- When the NAT is placed in front a device that is identified as a
symmetric NAT, this alarm is raised. It is cleared when a non-symmetric NAT or no NAT
replace the symmetric one.
3Com’ Element Management System
Using 3Com’ Element Management System (EMS) is recommended to Customers requiring
large deployments (multiple media gateways in globally distributed enterprise offices, for
example), that need to be managed by central personnel.
The EMS is not included in the device’s supplied package. Contact 3Com for detailed
information on 3Com’ EMS and on 3Com’ EVN - Enterprise VoIP Network – solution for large
VoIP deployments.
The EMS doesn’t apply to the TP-260.
Summary of Contents for V6100
Page 28: ...28 V6100 and V7122 User Guide Reader s Notes...
Page 48: ...48 V6100 and V7122 User Guide Reader s Notes...
Page 72: ...72 V6100 and V7122 User Guide Reader s Notes...
Page 80: ...80 V6100 and V7122 User Guide Reader s Notes...
Page 152: ...152 V6100 and V7122 User Guide Reader s Notes...
Page 262: ...262 V6100 and V7122 User Guide Reader s Notes...
Page 284: ...284 V6100 and V7122 User Guide Reader s Notes...
Page 291: ...V6100 and V7122 User Guide 291 Figure 95 V7122 Startup Process...
Page 324: ...324 V6100 and V7122 User Guide Reader s Notes...
Page 354: ...354 V6100 and V7122 User Guide Reader s Notes...
Page 374: ...374 V6100 and V7122 User Guide Reader s Notes...
Page 382: ...382 V6100 and V7122 User Guide Figure 130 Example of a User Information File Reader s Notes...
Page 392: ...392 V6100 and V7122 User Guide Reader s Notes...
Page 409: ...V6100 and V7122 User Guide 409 Reader s Notes...
Page 413: ...V6100 and V7122 User Guide 413 Reader s Notes...
Page 425: ...V6100 and V7122 User Guide 425 Figure 145 UDP2File Utility Reader s Notes...
Page 431: ...V6100 and V7122 User Guide 431 Reader s Notes...
Page 447: ...V6100 and V7122 User Guide 447 Reader s Notes...
Page 483: ...V6100 and V7122 User Guide 483 Reader s Notes...