<div>
Trap is a generated event from a system to the defined destination (trap destination). Get is a polling whereby a monitoring system connects and requests status of a particular informational counter..<br />
Trap is more like an alarm event, while get is a status inquiry mechanism.<br />
One is generated as soon as a preconfigured event occurs (trap), the other depends on the monitoring system's polling interval.<br />
<br />
Hope this clarifies it.
</div>


Trap is a generated event from a system to the defined destination (trap destination). Get is a polling whereby a monitoring system connects and requests status of a particular informational counter..
Trap is more like an alarm event, while get is a status inquiry mechanism.
One is generated as soon as a preconfigured event occurs (trap), the other depends on the monitoring system's polling interval.

Hope this clarifies it.

<div>
For trap, it also need to point to a server where it will receive the trap message, correct ?<br />
<br />
Can I say<br />
<br />
trap - push message<br />
get &nbsp; - receive message <br />
<br />
<br />
Tks
</div>


For trap, it also need to point to a server where it will receive the trap message, correct ?

Can I say

trap - push message
get   - receive message


Tks

<div>
<div class="content wysiwyg-content">
What's the difference between trap and get in SNMP ?<br />
<br />
Tks
</div>
</div>


What's the difference between trap and get in SNMP ?

Tks

Trap and Get in SNMP

Network Management involves issues that are independent of specific hardware or software, including email policies, upgrade planning, backup scheduling and working with managed service providers for Desktop-As-A-Service (DaaS), Software-As-A-Service (SaaS) and the like through the use of tools, coupled with manufacturer standards, best practice guidelines, policies and procedures plus all other relevant documentation. Network management also includes monitoring, alerting and reporting, management reporting, planning for device or service updates, the backup of configurations, the setting of key performance indicators and measures (KPIs/KPMs), associated service level agreements and problem records as part of the IT Service Management (ITSM) framework.