RFC 3417:Transport Mappings for the S...
RFC-Ref

SNMP


Click on the red underlined text to get to the source

... MIB objects are generally accessed through the Simple Network Management Protocol (SNMP). Objects in the MIB are defined using the mechanisms defined in the ...
... RFC3416] may be carried over a variety of protocol suites. It is the purpose of this document to define how the SNMP maps onto an initial set of transport domains. At the time of this writing, work was in progress to define an IPv6 ...


... DESCRIPTION "The MIB module for SNMP transport mappings. ...
... ::= { snmpModules 19 } -- SNMP over UDP over IPv4 ...
... STATUS current DESCRIPTION "The SNMP over UDP over IPv4 transport domain ...
... SYNTAX OCTET STRING (SIZE (6)) -- SNMP over OSI snmpCLNSDomain OBJECT-IDENTITY ...
... STATUS current DESCRIPTION "The SNMP over CLNS transport domain. The corresponding transport address ...
... STATUS current DESCRIPTION "The SNMP over CONS transport domain. The corresponding transport address ...
... SYNTAX OCTET STRING (SIZE (1 | 4..85)) -- SNMP over DDP ...
... STATUS current DESCRIPTION "The SNMP over DDP transport domain. The corresponding ...
... SYNTAX OCTET STRING (SIZE (3..99)) -- SNMP over IPX ...
... STATUS current DESCRIPTION "The SNMP over IPX transport domain. The corresponding ...


... SNMP over UDP over IPv4 ...
... It is suggested that administrators configure their SNMP entities supporting command responder applications to listen on UDP port ...
... responder applications to listen on UDP port 161. Further, it is suggested that SNMP entities supporting notification receiver ...
... UDP port 162. When an SNMP entity uses this transport mapping, it must be capable ...


... SNMP over OSI ...
... It is suggested that administrators configure their SNMP entities supporting command responder applications to listen on transport ...
... using a CL-mode network service to realize the CLTS. Further, it is suggested that SNMP entities supporting notification receiver ...
... receivers, respectively. When an SNMP entity uses this transport mapping, it must be capable ...


... SNMP over DDP ...
... SNMP messages are sent using DDP protocol type 8. SNMP entities ...
... SNMP messages are sent using DDP protocol type 8. SNMP entities supporting command responder applications listen on DDP ...
... DDP socket number 8, while SNMP entities supporting notification receiver applications ...
... Administrators must configure their SNMP entities supporting command responder applications to use NBP type "SNMP Agent ...
... SNMP entities supporting command responder applications to use NBP type "SNMP Agent" (which consists of ten ASCII characters) while those supporting notification ...
... notification receiver applications must be configured to use NBP type "SNMP Trap Handler" (which consists of seventeen ASCII characters). ...
... ASCII characters). The NBP name for SNMP entities supporting command responders and notification ...
... suggested that the NBP name be stored in some form of stable storage. When an SNMP entity uses this transport mapping, it must be capable ...
... AppleTalk's naming strategy and the dynamic nature of address assignment can cause problems for SNMP entities that wish to manage AppleTalk networks ...
... reboot (or more frequently). Thus, when SNMP is mapped over DDP, nodes are identified by a "name", ...
... address will be possible. In determining the SNMP identity to register for an SNMP ...
... SNMP identity to register for an SNMP entity, it is suggested that the SNMP ...
... SNMP entity, it is suggested that the SNMP identity be a name which is associated with other network services ...
... table inconsistencies) which would not prevent direct AppleTalk communications between two SNMP entities. Thus, it is recommended that NBP lookups ...
... cache of name-to-address mappings. These cached mappings should then be used for any further SNMP traffic. It is recommended that SNMP ...
... SNMP traffic. It is recommended that SNMP entities supporting command generator applications should maintain this cache between reboots. This ...
... An SNMP entity supporting command generator applications may have a pre-configured list of names of "known" SNMP ...
... SNMP entity supporting command generator applications may have a pre-configured list of names of "known" SNMP entities supporting command responder applications. Similarly, an SNMP ...
... SNMP entities supporting command responder applications. Similarly, an SNMP entity supporting command generator or notification ...
... notification receiver applications might interact with an operator. Finally, an SNMP entity supporting command generator or notification ...
... notification receiver applications might communicate with all SNMP entities supporting command responder or notification ...
... When an SNMP entity uses a cache entry to address ...
... entity uses a cache entry to address an SNMP packet, it should attempt to confirm the validity mapping, if the mapping hasn't ...
... be configurable. An SNMP entity supporting a command generator application may decide to prime its cache ...
... to prime its cache of names prior to actually communicating with another SNMP entity. In general, it is expected that such an entity ...
... routers) may be deemed "more important". Note that an SNMP entity supporting command generator applications should not prime its entire cache ...
... lookup in a given zone. An SNMP entity supporting command responder applications must never ...
... entity does not need to confirm a cache entry. An SNMP entity supporting notification ...
... notification originator applications should do NBP lookups (or confirms) only when it needs to send an SNMP trap or inform. ...
... DDP address mapping can also be confirmed implicitly using only SNMP transactions. For example, an SNMP entity ...
... using only SNMP transactions. For example, an SNMP entity supporting command generator applications issuing a retrieval operation could ...
... group [RFC1742] for the SNMP entity supporting the command responder application. This ...
... Under some circumstances, there may be connectivity between two SNMP entities, but the NBP mapping machinery may be broken, e.g., ...
... node. An SNMP entity supporting command generator applications which is dedicated to AppleTalk ...
... entity could send an NBP FwdReq to the network in which the SNMP entity supporting the command responder ...


... SNMP over IPX ...
... SNMP messages are sent using IPX packet type 4 (i.e., Packet Exchange ...
... It is suggested that administrators configure their SNMP entities supporting command responder applications to listen on IPX ...
... socket 36880 (9010 hexadecimal). When an SNMP entity uses this transport mapping, it must be capable ...


... transport domain, rfc1157Domain, which indicates the transport mapping for SNMP messages as defined in [RFC1157]. ...


... It is then a customer/user responsibility to ensure that the SNMP entity giving access to a MIB ...


... View-based Access Control Model (VACM) for the Simple Network Management Protocol (SNMP)", STD 62, RFC 3415std62, December 2002. ...
... Presuhn, R., Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, "Version 2 of the Protocol Operations for the Simple Network Management Protocol (SNMP)", STD 62, RFC 3416std62, December 2002. ...



Google
Web
RFC-Ref