ICR-1601
190
using a switch or a router with UDP forwarding.
If you want to manage some devices and they all have supported SNMP protocol, use either one
application scenario, especially the management of devices in the Intranet.
In managing devices in the Internet, the TR-069 is the better solution. Please refer to last sub-section.
Scenario Description
The NMS server can monitor and configure the managed devices by using SNMP protocol, and those
devices are located at where UDP packets can reach from NMS.
The managed devices report urgent trap events to the NMS servers.
Use SNMPv3 version of protocol can protected the transmitting of SNMP commands and responses.
The remote NMS with privilege IP address can manage the devices, but other remote NMS can't.
Parameter Setup Example
Following tables list the parameter configuration as an example for the Gateway 1 in above diagram
with "SNMP" enabling at LAN and WAN interfaces.
Use default value for those parameters that are not mentioned in the tables.
ReadCommunity / WriteCommunity
[SNMP]-[User Privacy Definition]
Scenario Operation Procedure
In above diagram, the NMS server can manage multiple devices in the Intranet or a UDP-reachable
network. The "Gateway 1" is one of the managed devices, and it has the IP address of 10.0.75.2 for LAN
interface and 118.18.81.33 for WAN-1 interface. It serves as a NAT router.
At first stage, the NMS manager prepares related information for all managed devices and records them
in the NMS system. Then NMS system gets the status of all managed devices by using SNMP get
commands.
When the manager wants to configure the managed devices, the NMS system allows him to do that by
using SNMP set commands. The "UserName1" account is used if the manager uses SNMPv3 protocol
To Next Page
Loading...
