SNMP
186 ViewCast
External SNMP Manager
With ViewCast SNMP agent enabled in each Niagara system, you can start a single SNMP manager at a
central location to manage one or multiple systems at the same time.
The external SNMP manager could be a GUI-based commercial or free application tool or an SNMP
scripting tool. The SNMP manager is your choice.
SNMP UDP Ports Used by SNMP Manager and
SNMP Agents
UDP Port for SNMP Requests
When the external SNMP manager expects to “talk” to the ViewCast SNMP agent, it sends SNMP
requests to the ViewCast SNMP agent over the default SNMP UDP port 161 with the following
parameters:
Correct IP address of the encoder system
Other parameters such as an appropriate community name
Configure the corresponding community name
Note: For SNMP v1/v2c version, a community name is treated as a password to access the resources
managed by the SNMP agent. Different community names can have different access rights such
as NOTIFY ONLY, READ ONLY, WRITE ONLY, READ WRITE and READ CREATE etc.
You can configure the ViewCast SNMP agent to receive SNMP requests over a different UDP port other
than 161 (see Use UDP Port Other Than 161 for SNMP Requests).
Note: Once you configure the SNMP UDP port, you don’t have to manually enable in the firewall
setting. Instead, it is enabled automatically when the ViewCast SNMP agent is started.
Because the ViewCast SNMP agent acts as the master agent and “talks” to the external SNMP
manager, it is not necessary to enable the firewall setting on the same UDP port for the native
SNMP service.
UDP Port for SNMP Traps
SNMP traps are sent from the SNMP agent to the SNMP trap listener. You can monitor and receive
SNMP traps over UDP port 162 from one or multiple SNMP-enabled Niagara systems. Perform the
following to monitor and receive SNMP traps:
Configure the IP address where the SNMP trap listener runs as one of the trap destinations for
each affected ViewCast SNMP agent.
Configure the corresponding community name.
Keep running an SNMP trap listener application to monitor traps over SNMP UDP port 162 with an
appropriate community name.
Allow the trap listener to pass through the firewall on UDP port 162.
Note: Choosing a trap listener is up to you. The trap listener doesn’t have to run on the system.
Instead, it runs in a centralized location.
If you use the Windows SNMP Trap Service as the trap listener, you need to make sure Windows SNMP
Trap Service is installed, started, and allowed to pass through the firewall on UDP port 162.
