Supported SNMP Functionality
The following request/response operations and messages are supported by the SNMP agent:
Get—Allows the SNMP manager to retrieve one or more specific object values (on a device) from the SNMP agent. BTI7800 supports the use of the Get operation to retrieve objects with read access.
GetNext—Allows the SNMP manager to retrieve the next object instance in lexicographical order relative to a specified object. When an SNMP manager wants to “walk” through all elements of a table on an agent, it performs a series of GetNext operations using the last returned object as the argument for the succeeding GetNext operation.
GetBulk—Allows the SNMP manager to retrieve multiple rows of tabular objects in a single operation.
Set—Allows the SNMP manager to send one or more specific object values to the SNMP agent.
Trap—Used by the agent to asynchronously notify the SNMP manager of an event.
Inform —Traps sent by the agent for which acknowledgment is sent back.
When responding to a Get, GetNext or GetBulk request, the SNMP agent retrieves the value of the requested MIB object and responds to the SNMP manager with that value. Multiple values can be requested at the same time.
Up to 10 trap receivers can be provisioned on one BTI7800 system.
UDP port (traps)
UDP port (requests)
This value cannot be changed.
Read-only community string
Read-write community string
Please note the following when integrating BTI7800 MIBs:
Performance: It is the customer’s responsibility to conduct testing to ensure that the NE interfaces meet their proposed usage needs. Juniper Networks makes no guarantees that any proposed usage will meet customer requirements.
Changes between releases: SNMP MIBs are subject to change as support for new functionality is introduced. Although Juniper Networks makes every effort to maintain backward compatibility of BTI7800 MIBs across releases, backward compatibility cannot be guaranteed. Juniper Networks reserves the right to deprecate or remove support for obsolete MIB elements. For this reason, OSS integrators should not rely on functionality that is marked as deprecated, because there is a likelihood that it will not be supported in a subsequent release. Customers that integrate directly to the MIBs are responsible for all OSS development and integration testing that result from MIB changes between software releases.