Juniper-HTTP-Profile-MIB
Imported Objects
Objects
13 total| Object Name |
|---|
juniHttpProfileMIBThe HTTP rofile MIB for the Juniper Networks, Inc. enterprise. MODULE-IDENTITY .1.3.6.1.4.1.4874.2.2.79 |
juniHttpProfileObjects OBJECT IDENTIFIER .1.3.6.1.4.1.4874.2.2.79.1 |
juniHttpProfile OBJECT IDENTIFIER .1.3.6.1.4.1.4874.2.2.79.1.1 |
juniHttpProfileTableThis table contains profiles for configuring bulk ATM circuits. Entries in this table are created/deleted as a side-effect of corresponding operations to the juniProfileNameTable in the Juniper-PROFILE-MIB. SEQUENCE OF JuniHttpProfileEntry .1.3.6.1.4.1.4874.2.2.79.1.1.1 |
juniHttpProfileEntryA profile describing VCC configuration of an ATM subinterface. JuniHttpProfileEntry .1.3.6.1.4.1.4874.2.2.79.1.1.1.1 |
juniHttpProfileIdThe integer identifier associated with this profile. A value for this identifier is determined by locating or creating a profile name in the juniProfileNameTable. Unsigned32 .1.3.6.1.4.1.4874.2.2.79.1.1.1.1.1 |
juniHttpProfileSetMapA bitmap representing which objects in this entry have been explicitly configured. See the definition of the JuniSetMap TEXTUAL-CONVENTION for details of use. The INDEX object(s) and this object are excluded from representation (i.e. their bits are never set). When a SET request does not explicitly configure JuniSetMap, bits in JuniSetMap are set as a side-effect of configuring other profile attributes in the same entry. If, however, a SET request explicitly configures JuniSetMap, the explicitly configured value overrides 1) any previous bit settings, and 2) any simultaneous 'side-effect' settings that would otherwise occur. Once set, bits can only be cleared by explicitly configuring JuniSetMap.rw JuniSetMap (Juniper-TC) .1.3.6.1.4.1.4874.2.2.79.1.1.1.1.2 |
juniHttpProfileRedirectUrlThis object is a 64 byte string that will be used as the redirect URL when requests arrive at the HTTP server over the Ip Interface configured.rw DisplayString .1.3.6.1.4.1.4874.2.2.79.1.1.1.1.3 |
juniHttpProfileConformance OBJECT IDENTIFIER .1.3.6.1.4.1.4874.2.2.79.4 |
juniHttpProfileCompliances OBJECT IDENTIFIER .1.3.6.1.4.1.4874.2.2.79.4.1 |
juniHttpProfileComplianceCompliance statement for entities which implement the Juniper HTTP Profile MIB. Unknown .1.3.6.1.4.1.4874.2.2.79.4.1.1 |
juniHttpProfileGroups OBJECT IDENTIFIER .1.3.6.1.4.1.4874.2.2.79.4.2 |
juniHttpProfileGroupCurrent collection of objects providing management of profile functionality for per Interface HTTP objects in a Juniper product. Unknown .1.3.6.1.4.1.4874.2.2.79.4.2.1 |
More MIBs from Unisphere
Browse all UnisphereMIBs →SNMP MIB module
The Unisphere-Data-BGP-MIB enables monitoring and management of Border Gateway Protocol (BGP) session states, routing table statistics, and neighbor relationships on Dell EMC Unisphere for Data storage systems. It provides access to standard BGP MIB objects for tracking peer connectivity, route advertisements, and protocol error counters within the storage network infrastructure.
The Juniper-RADIUS-CLIENT-MIB enables monitoring of RADIUS client authentication sessions, accounting records, and server reachability states on Juniper network devices. It provides specific counters and gauges for tracking authentication failures, successful logins, and RADIUS server response times to validate access control infrastructure health.
The Juniper-UNI-ATM-MIB module provides SNMP management capabilities for Juniper devices configured with Asynchronous Transfer Mode (ATM) user-network interfaces, enabling the monitoring of ATM-specific performance counters, interface states, and VPI/VCI traffic statistics.
The Juniper-AAA-MIB enables monitoring of authentication, authorization, and accounting events on Juniper Networks devices, specifically tracking user session states, login success/failure counts, and accounting record generation for RADIUS and TACACS+ protocols.
SNMP MIB module