Juniper-SNMP-MIB: View SNMP OID List / Download MIB

MIB objects for configuring SNMP-based management access into Juniper E-series products.

The maximum sized SNMP PDU, in bytes, that this agent is capable of handling. The default is 1500 bytes. The possibility of IP fragmentation should be considered when setting this object to large values.

The interface table mode for the SNMP agent(s) associated with this system. verbose(1) - the standard ifTable, ifXTable and ifStackTable contain entries for every standard and proprietary interface type supported by this system. compress(2) - the standard ifTable, ifXTable and ifStackTable contain a subset of interface types. Certain interface types like HDLC and IP and others are excluded from the standard tables but are manageable from proprietary MIBs. enhanced(3) - the standard ifTable, ifXTable and ifStackTable contain a subset of interface types. Enhanced mode cannot by configured at this time via SNMP. Attempts to set this value will fail. This object became obsolete when individual objects were added for each mode. Enumeration: 'compress': 2, 'verbose': 1, 'enhanced': 3.

true(1) - the standard ifTable, ifXTable and ifStackTable contain a subset of interface types. Certain interface types like HDLC and IP and others are excluded from the standard tables but are manageable from proprietary MIBs. false(2) - the standard ifTable, ifXTable and ifStackTable contain entries for every standard and proprietary interface type supported by this system. This configuration is applicable to all interface related tables until interface compression based on interface table-types is applied. If interface table-type based compression is applied, get operation on this object will correspond only to ifTable/ifXTable/juniIfTable and set operation on this object will fail.

This object governs which interface types are visible to SNMP management clients that use the standard ifTable, ifXTable and ifStackTable. The object is a variable length octet string that is interpreted as a bit mask. Each bit respresents a specific Juniper interface type that can be included or excluded in the standard interface tables. For each bit position in each octet of the string, a '1' or '0' indicates the corresponding interface type is either removed (compressed) from the standard interface MIB tables, or included respectively. Individual bit definitions follow the JuniIfType convention defined in the Juniper-UNI-IF-MIB. For example, ip(0) and ppp(1) correspond to bit definitions 0 and 1 respectively. In each octet, bit 0 is least significant, bit 7 most significant. This configuration is applicable to all interface related tables until interface compression based on interface table-types is applied. If interface table-type based compression is applied, get operation on this object will correspond only to ifTable/ifXTable/juniIfTable and set operation on this object will fail.

This object displays the excluded interface types in human readable form. Three dots (...) at the end of display string indicates that the output has been truncated. The syntax rules are the same as for SNMP-FRAMEWORK-MIB.SnmpAdminString, except for the size constraint. This configuration is applicable to all interface related tables until interface compression based on interface table-types is applied. If interface table-type based compression is applied, this object will be applicable only to ifTable/ifXTable/juniIfTable.

This object governs which interface instances appear to SNMP management clients that use the standard ifTable, ifXTable and ifStackTable. The control is based on a set of interface restrictions defined by JuniSnmpInterfaceModeRestrictedMask. For each bit position in each octet of the string, a '1' or '0' controls whether an interface instance that matches the restriction is removed or included in the standard interface MIB tables. For example, setting the value of this object to 1 will remove all interface instances with an ifAdminStatus of down(2). In each octet, bit 0 is least significant, bit 7 most significant.

This object displays the restrictions in human readable form. Three dots (...) at the end of display string indicates that the output has been truncated.

This table contains enhanced compression bitmask based on table-type.

Each entry corresponds to a table type for which interface compression mask is applied.

SNMP interface tables for which interface compression bitmask will be applicable. Supported values are: others : All the other interface related tables except ifTables and ifStackTables. Currently only ipNetToMediaTable is supported. ifTables : It consists of ifTable, ifXTable and juniIfTable. ifStackTables : It consists of ifStackTable, ifInvStackTable and juniIfInvStackTable. Enumeration: 'ifTables': 1, 'ifStackTables': 2, 'others': 0.

true(1) - the standard ifTable, ifXTable and ifStackTable contain a subset of interface types. Certain interface types like HDLC and IP and others are excluded from the standard tables but are manageable from proprietary MIBs. false(2) - the standard ifTable, ifXTable and ifStackTable contain entries for every standard and proprietary interface type supported by this system.

This object governs which interface types are visible to SNMP management clients. The object is a variable length octet string that is interpreted as a bit mask. Each bit respresents a specific Juniper interface type that can be included or excluded in the standard interface tables. For each bit position in each octet of the string, a '1' or '0' indicates the corresponding interface type is either filtered (compressed) from the interface MIB tables, or included respectively. Individual bit definitions follow the JuniIfType convention defined in the Juniper-UNI-IF-MIB. For example, ip(0) and ppp(1) correspond to bit definitions 0 and 1 respectively. In each octet, bit 0 is least significant, bit 7 most significant.

This object displays the excluded interface types in human readable form. Three dots (...) at the end of display string indicates that the output has been truncated. The syntax rules are the same as for SNMP-FRAMEWORK-MIB.SnmpAdminString, except for the size constraint.

Enable/disable SNMP proxy between virtual routers.

The access permission to the MIB objects of this SNMP agent. noAccess - No access permission granted. readAccess - Read access permission granted. readWriteAccess - Read and write access permission granted. Enumeration: 'readAccess': 2, 'readWriteAccess': 3, 'noAccess': 1.

This table contains entries for each management application supported by the router entry created in the juniRouterTable.

Each entry provides administrative control on a management application for the router designated by the first indice to this table. The second indice identifies the router management application. Entries in this table are created as a side-effect of row creation in the juniRouterTable.

The routerIndex of this router. This object is the same as the juniRouterIndex object defined in the juniRouterTable.

Identities the management application.

Controls creation/deletion of entries in this table. Only 'createAndGo' and 'destroy' enumeration values are supported.

Table of SNMP management clients. Authentic SNMP clients are identified by a combination community name and IP address. Upon receipt of an SNMP request, this table is scanned for a matching community name. If an entry containing a matching community name is found, the entry's IP access list, if nonzero, is used to validate the source IP address received in the request; else, if the IP access list number in the matching entry is zero, the source IP address is accepted. Finally, the type of SNMP request is validated with respect to the access privilege of the matching entry (e.g. a SET Request is rejected for an entry having read-only privilege). Use of this table constitutes 'trivial authentication', i.e., no mechanism is employed to confirm the received SNMP request was indeed originated by the host identified by the IP source address.

A table entry describing an authentic SNMP Community.

An SNMP community name.

Controls creation/deletion of entries in this table. Only 'createAndGo' and 'destroy' enumeration values are supported.

The access privilege for an SNMP Community authenticated by this entry (used in conjunction with MIB view as specified via juniSnmpCommunityView). readOnly Read-only access to MIB with associated view. readWrite Read-write access to MIB with associated view. admin Read-write access to entire MIB (for backward compatibility, automatically defaults to 'everything' view and 'readWrite' privilege). Enumeration: 'readWrite': 2, 'admin': 3, 'readOnly': 1.

If nonzero, the number of an IP access list that describes the IP hosts permitted SNMP management access to this device via the corresponding community name contained in this entry.

If not null, the name of an IP access list that describes the IP hosts permitted SNMP management access to this device via the corresponding community name contained in this entry.

The view associated with an SNMP Community authenticated by this entry. Following is the list of built-in system views. everything Access to the entire MIB except packet mirror MIB. user Access to non-administrative portions of MIB. nothing No access. mirrorAdmin Access to packet mirror MIB. 'Administrative' portions of the MIB are those portions that pertain to management access into the managed device. Administrator can also create a new SNMP MIB view dynamically and assign it to community entry. Access to packet mirror MIB is only thorugh 'mirrorAdmin' view. A community with 'mirrorAdmin' view can be configure only through CLI administrator with mirror configuration privileges.

This object provides global control over trap generation by this agent. For each bit position, a '1' or '0' indicates the corresponding trap category is enabled or disabled, respectively. For security reasons, Mirror category will not be allowed to be configured through SNMP.

The ifIndex of the interface whose IP address is used as the source IP address for outbound SNMP traps. If zero, no interface is specified, the mechanism for selecting a source IP address is implementation-dependent, and may vary with each trap sent.

Table of SNMP Trap recipient.

A table entry describing an SNMP Trap recipient.

IP address of an authorized SNMP Trap recipient. This must be a host IP address.

Controls creation/deletion of entries in this table. Only 'createAndGo' and 'destroy' enumeration values are supported.

The destination UDP port to which traps will be sent.

An SNMP community name to be used in traps sent to this destination.

The format of the SNMP trap PDU to be sent to this trap destination. v1 Trap-PDU defined in RFC1157, encapsulated in the message structure also defined in RFC1157. v2c SNMPv2-Trap-PDU defined in RFC1905, encapsulated in the message structure defined in RFC1901. v3 SNMPv2-Trap-PDU defined in RFC1905, encapsulated in the message structure defined in RFC2571. Enumeration: 'v2c': 1, 'v1': 0, 'v3': 2.

Bit mask designating the specific trap types enabled for transmission to this trap destination. For each bit position, a '1' or '0' indicates the corresponding trap type is enabled or disabled, respectively. For security reasons, Mirror category will not be allowed to be configured through SNMP. Note, trap generation is further constrained by the value juniSnmpTrapGlobalFilter.

The number of traps submitted for transmission to this destination.

The number of trap requests that were discarded. A trap may be discarded because the trap type is either not a configured type in juniSnmpTrapHostFilter, or because the traps's priority is below the minimum trap severity filter defined by juniSnmpTrapHostSeverityFilter.

The minimum severity value an snmp trap must have in order to be forwarded to this host.

The maximum ping time window that this host gets pinged repeatedly.

The configuration setting for snmp trap message content. Enabling this management object configures the associated SNMP agent to include notification log name and the corresponding log index as part of the trap messages sent to this host.

The maximum number of traps to be kept in the queue.

The maximum number of traps per second to be sent to the host. Zero value indicates that there is no control over queue drain rate.

Specify the method for handling Queue-Full condition. dropLastIn -- When queue is full the most recent trap will be dropped. dropFirstIn -- When queue is full the oldest trap in the queue will be dropped. Enumeration: 'dropLastIn': 0, 'dropFirstIn': 1.

The number of trap requests that were discarded due to bad encoding.

The number of trap requests that were discarded due to the queue being full.

The number of trap requests that were discarded due to host not being available (not responding to the pings).

The configuration setting for snmp trap proxying. Enabling this management object configures the associated SNMP agent to proxy internally generated traps. Note that some implementations may support a single snmp trap proxy per system.

The severity level of the trap.

The number of trap requests that were discarded. A trap may be discarded because the trap type is either not globally configured in juniSnmpTrapGlobalFilter, or because the traps's priority is below the minimum trap severity filter defined by juniSnmpTrapGlobalSeverityFilter.

Traps flow through two levels of filtering: global and then host. The value of this object defines the global minimum severity level a trap must have in order to be forwarded to the host level trap processing. A trap will be discarded and counted in juniSnmpTrapGlobalDiscards if its severity level is less then the value of this object.

Total number of trap requests that this agent has received. Includes local submitted traps and proxied traps from other agents if this agent is the proxy agent.

The number of local traps submitted to this agent.

The number of proxied traps submitted to this agent.

The number of proxy traps submitted to this agent.

The number of trap requests that were discarded due to lack of system memory.

The number of trap requests that were discarded due to no queue resources. A trap may be discarded because the agent request queue is full juniSnmpTrapRequestQueueCongestionDiscards or the proxy agent reuest queue is full juniSnmpTrapProxyRequestQueueCongestion.

The number of trap requests that were discarded due to SNMP agent being disabled.

Total number of trap requests sent to every host that is configured to receive traps from this agent.

Total number of trap requests sent to proxy virtual router.

A table of SNMP trap Severity filter.

A table entry specifying the trap severity filter for a particular trap category.

The value of this object is an integer which is same as the bit position specified for a particular trap category in JuniSnmpTrapMask. For example, value of juniSnmpTrapCategory object will be 6 for BGP traps.

Traps flow through two levels of filtering: severity of a particular trap category and trap destination. If the severity of a particular category is not defined, global trap severity is used for computation. The value of this object defines trap-category based minimum severity level, a trap must have in order to be forwarded for the destination level trap filtering. A trap will be discarded and counted in juniSnmpTrapGlobalDiscards if its severity level is less than the value of this object. For security reasons, Mirror category will not be allowed to be configured through SNMP. Only those trap categories which are configured using per category based trap severity filter are displayed as part of this table. If the value of juniSnmpTrapGlobalSeverityFilter is modified, it will overwrite all the values specified in this table.

The source IP address contained in a received SNMP request that failed authentication.

The source UDP port contained in a received SNMP request that failed authentication.

The SNMP community contained in a received SNMP request that failed authentication.

The reason a received SNMP request failed authentication: other Unspecified reason. badCommunityName The community is not recognized. badCommunityUse The community does not have privilege for the SNMP request type (e.g. SET request with a community having read-only privilege). hostDenied The host IP address was denied by the community's associated access list. Enumeration: 'hostDenied': 3, 'other': 0, 'badCommunityName': 1, 'badCommmunityUse': 2.

Obsolete compliance statement for entities which implement the Juniper SNMP MIB. This statement became obsolete when View support and Named Access List support were added.

Obsolete compliance statement for entities which implement the Juniper SNMP MIB. This statement became obsolete when juniSnmpInterfaceMode was added.

Obsolete compliance statement for entities which implement the Juniper SNMP MIB. This statement became obsolete when support for interface compress, trap severities and trap severity filtering was added and juniSnmpInterfaceMode was obsoleted.

Obsolete compliance statement for entities which implement the Juniper SNMP MIB. This statement became obsolete when trap proxy enable/disable support was added.

Obsolete compliance statement for entities which implement the Juniper SNMP MIB. This statement became obsolete when support was added for ping time window and notification log data inclusion in trap varbinds.

The compliance statement for entities which implement the Juniper SNMP MIB. This statement became obsolete when support was added for access permission and management application table.

The compliance statement for entities which implement the Juniper SNMP MIB. This statement became obsolete when support was added for trap severity filter table.

The compliance statement for entities which implement the Juniper SNMP MIB. This statement became obsolete when support was added for table type based interface compression.

The compliance statement for entities which implement the Juniper SNMP MIB.

Obsolete collection of management objects pertaining to SNMP Agent capability in a Juniper product. This group became obsolete when View support and Named Access List support were added.

A collection of management objects pertaining to an SNMP authentication failure in a Juniper product.

Obsolete collection of management objects pertaining to SNMP Agent capability in a Juniper product. This group became obsolete when juniSnmpInterfaceMode was added.

Obsolete collection of management objects pertaining to SNMP Agent capability in a Juniper product. This group became obsolete when support for interface compress, trap severities and trap severity filtering was added and juniSnmpInterfaceMode was obsoleted.

Obsolete collection of management objects pertaining to general SNMP Agent capabilities in a Juniper product. This group became obsolete when proxy enable/disable support was added.

A collection of management objects pertaining to SNMP Agent access capabilities in a Juniper product.

Obsolete collection of management objects pertaining to SNMP Agent trap capabilities in a Juniper product. This group became obsolete when support was added for ping time window and notification log data inclusion in trap varbinds.

A collection of management objects pertaining to general SNMP Agent capabilities in a Juniper product. This group became obsolete when access permission was added.

Obsolete collection of management objects pertaining to SNMP Agent trap capabilities in a Juniper product. This group became obsolete when support was added for trap severity filter table.

A collection of management objects pertaining to general SNMP Agent capabilities in a Juniper product. This group became obsolete when support for interface compression based on interface table type was added.

A collection of management objects pertaining to SNMP Agent trap capabilities in a Juniper product.

A collection of management objects pertaining to general SNMP Agent capabilities in a Juniper product.