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

VENDOR: JUNIPER


 Home MIB: Juniper-HTTP-Profile-MIB
Download as:   
SNMPv2-CONF, SNMPv2-SMI, Juniper-MIBs, Juniper-TC, SNMPv2-TC

Download standard MIB format if you are planning to load a MIB file into some system (OS, Zabbix, PRTG ...) or view it with a MIB browser. CSV is more suitable for analyzing and viewing OID' and other MIB objects in excel. JSON and YAML formats are usually used in programing even though some systems can use MIB in YAML format (like Logstash).
Keep in mind that standard MIB files can be successfully loaded by systems and programs only if all the required MIB's from the "Imports" section are already loaded.
The tree-like SNMP object navigator requires no explanations because it is very simple to use. And if you stumbled on this MIB from Google note that you can always go back to the home page if you need to perform another MIB or OID lookup.


Object Name OID Type Access Info
 juniHttpProfileMIB 1.3.6.1.4.1.4874.2.2.79
The HTTP rofile MIB for the Juniper Networks, Inc. enterprise.
       juniHttpProfileObjects 1.3.6.1.4.1.4874.2.2.79.1
           juniHttpProfile 1.3.6.1.4.1.4874.2.2.79.1.1
               juniHttpProfileTable 1.3.6.1.4.1.4874.2.2.79.1.1.1 no-access
This 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.
                   juniHttpProfileEntry 1.3.6.1.4.1.4874.2.2.79.1.1.1.1 no-access
A profile describing VCC configuration of an ATM subinterface.
                       juniHttpProfileId 1.3.6.1.4.1.4874.2.2.79.1.1.1.1.1 unsigned32 no-access
The integer identifier associated with this profile. A value for this identifier is determined by locating or creating a profile name in the juniProfileNameTable.
                       juniHttpProfileSetMap 1.3.6.1.4.1.4874.2.2.79.1.1.1.1.2 junisetmap read-write
A 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.
                       juniHttpProfileRedirectUrl 1.3.6.1.4.1.4874.2.2.79.1.1.1.1.3 displaystring read-write
This 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.
       juniHttpProfileConformance 1.3.6.1.4.1.4874.2.2.79.4
           juniHttpProfileCompliances 1.3.6.1.4.1.4874.2.2.79.4.1
               juniHttpProfileCompliance 1.3.6.1.4.1.4874.2.2.79.4.1.1
Compliance statement for entities which implement the Juniper HTTP Profile MIB.
           juniHttpProfileGroups 1.3.6.1.4.1.4874.2.2.79.4.2
               juniHttpProfileGroup 1.3.6.1.4.1.4874.2.2.79.4.2.1
Current collection of objects providing management of profile functionality for per Interface HTTP objects in a Juniper product.