UDP Ports on SNMP - SNMP

This is a discussion on UDP Ports on SNMP - SNMP ; Hi all, Normally, SNMP uses the port 161 or 162 for communication. But in some applications it is possible to change this value. In what cases is this needed? Thanks in advance David...

+ Reply to Thread
Results 1 to 2 of 2

Thread: UDP Ports on SNMP

  1. UDP Ports on SNMP

    Hi all,
    Normally, SNMP uses the port 161 or 162 for communication.
    But in some applications it is possible to change this value.
    In what cases is this needed?
    Thanks in advance
    David



  2. Re: UDP Ports on SNMP

    HI,

    Yes, normally an agent (or using the language of the 3rd
    generation of the SNMP framework - a "command responder")
    listens on UDP port 161. If there are more than one instance
    of an agent running on the system, then it is usually
    easier to use different UDP ports. (Note, the source
    port can be any valid one, but is usually a dynamic port.)

    Likewise, a notification receiver (in the past, called
    a trap receiver) normally listens on UDP port 162 for
    notifications (traps or informs). However, if multiple
    instances of notification receivers exist, then
    it is usually easier to use different UDP ports.
    (Note, the source port for notifications can be
    any valid one, and does not have to be 161 or 162.)

    RFC 3417 contains definitions of "transport mappings"
    for SNMP.

    On Thu, 7 Apr 2005, David wrote:

    > Hi all,
    > Normally, SNMP uses the port 161 or 162 for communication.
    > But in some applications it is possible to change this value.
    > In what cases is this needed?
    > Thanks in advance
    > David
    >
    >
    >

    Regards,
    /david t. perkins

+ Reply to Thread