SNMP Transport Requirements
SNMP can be implemented over two different transport layers: TCP (Transmission Control Protocol) and UDP (User Datagram Protocol). Each transport protocol has its own advantages and disadvantages.
UDP
SNMP was originally designed for UDP transport only. UDP is a connectionless protocol that does not support the robust error-recovery services of TCP. Delivery is not guaranteed, and messages are not necessarily delivered in the order they were sent.
Because UDP doesn't have the data recovery features of TCP, it consumes fewer network resources. UDP is well suited for repetitive, low-priority functions like alarm monitoring.
TCP
SNMP can also be transported via TCP, which has become increasingly popular. TCP offers robust error-recovery; delivery is guaranteed and messages are delivered in sequence.
Some modern SNMP managers only support SNMP over TCP.
So, which transport protocol should you choose? Quality SNMP equipment will support both protocols, giving you the greatest compatibility with other equipment and the greatest flexibility in designing your network management.
top
What Do You Want To Do With SNMP?
- Mediate SNMP and Other Protocols
- Display SNMP Alarm Data at Your NOC and in Your Web Browser
- Monitor Discrete, Analog, and Ping Alarms via SNMP
- Automatically Dispatch Repair Personnel
- Control Remote Equipment via SNMP
- Use Dial-Up Connections to Link SNMP Remotes to LAN
- Find the SNMP Alarm Monitoring Capacity That's Right for Your Size Site
- Use T1 Connection to Link SNMP Remotes to LAN
What Do You Want To Learn About SNMP?
- SNMP Tutorials - Learn More About SNMP
- 8 things you need to know before selecting an SNMP proxy agent to monitor your non-SNMP managed devices
Request Info