JUNIPER-JS-UTM-AV-MIB
Updated Feb 8, 2011The JUNIPER-JS-UTM-AV-MIB module provides SNMP access to monitor and manage antivirus engine states, threat detection counters, and signature database status on Juniper Networks UTM appliances. It enables the tracking of specific security metrics including active scan sessions, detected malware counts, and engine health indicators for enterprise-grade intrusion prevention and malware filtering.
Imported Objects
Objects
45 total| Object Name |
|---|
jnxJsAntiVirusThis module defines the MIB for Juniper Enterprise specific
antivirus functionality. Juniper documentation is recommended
as the reference. MODULE-IDENTITY .1.3.6.1.4.1.2636.3.39.1.13.1 |
jnxJsAntiVirusTrapsPrefix OBJECT IDENTIFIER .1.3.6.1.4.1.2636.3.39.1.13.1.0 |
jnxJsAvPatternUpdateTrapThis traps is raised when the Anti-Virus pattern database is
updated successfully. NOTIFICATION-TYPE .1.3.6.1.4.1.2636.3.39.1.13.1.0.1 |
jnxJsAntiVirusObjects OBJECT IDENTIFIER .1.3.6.1.4.1.2636.3.39.1.13.1.1 |
jnxJsAntiVirusEngine OBJECT IDENTIFIER .1.3.6.1.4.1.2636.3.39.1.13.1.1.1 |
jnxJsAVEngineTypeThe scan engine type in use. User can use CLI to set the
engine type to either full AV (kaspersky-lab-engine),
express AV (juniper-express-engine) or Sophos AV
(sophos-engine). If AV is not configured then engine type
is not known.rodeprecated Enumeration .1.3.6.1.4.1.2636.3.39.1.13.1.1.1.1 |
jnxJsAVCurrentPatternVersionStringAnti-Virus pattern database version currently in use.rodeprecated DisplayString .1.3.6.1.4.1.2636.3.39.1.13.1.1.1.2 |
jnxJsAVDatabaseTypeThe Database type in use. User can use CLI to set the
engine type to full AV, express AV or Sophos AV.
Corresponding database types are Full for KL Engine,
Express for Juniper Express Engine and Sophos for Sophos
AV Engine.rodeprecated Enumeration .1.3.6.1.4.1.2636.3.39.1.13.1.1.1.3 |
jnxJsAntiVirusStats OBJECT IDENTIFIER .1.3.6.1.4.1.2636.3.39.1.13.1.1.2 |
jnxJsAVScanCodeCleanNumber of requests passed Anti-Virus scan.rodeprecated Integer32 .1.3.6.1.4.1.2636.3.39.1.13.1.1.2.1 |
jnxJsAVScanCodeInfectedNumber of requests found infected by Anti-Virus scan engine.rodeprecated Integer32 .1.3.6.1.4.1.2636.3.39.1.13.1.1.2.2 |
jnxJsAVScanCodeProtectedNumber of requests cannot be scanned due to protected by password.rodeprecated Integer32 .1.3.6.1.4.1.2636.3.39.1.13.1.1.2.3 |
jnxJsAVScanCodeDecompressNumber of requests cannot be scanned due to exceeding max
decmopress layer.rodeprecated Integer32 .1.3.6.1.4.1.2636.3.39.1.13.1.1.2.4 |
jnxJsAVScanCodeCorruptedNumber of requests cannot be scanned due to file corrupted.rodeprecated Integer32 .1.3.6.1.4.1.2636.3.39.1.13.1.1.2.5 |
jnxJsAVScanCodeNoResourceNumber of requests cannot be scanned due to out-of-resource.rodeprecated Integer32 .1.3.6.1.4.1.2636.3.39.1.13.1.1.2.6 |
jnxJsAVScanCodeInternalErrorNumber of requests cannot be scanned due to internal error.rodeprecated Integer32 .1.3.6.1.4.1.2636.3.39.1.13.1.1.2.7 |
jnxJsAVScanCodeMaxContentSizeNumber of requests cannot be scanned due to exceeding max content
size limit.rodeprecated Integer32 .1.3.6.1.4.1.2636.3.39.1.13.1.1.2.8 |
jnxJsAVScanCodeTooManyReqNumber of requests cannot be scanned due to exceeding maximum
requests limit.rodeprecated Integer32 .1.3.6.1.4.1.2636.3.39.1.13.1.1.2.9 |
jnxJsAVScanCodeTimeoutNumber of requests cannot be scanned due to scan timeout.rodeprecated Integer32 .1.3.6.1.4.1.2636.3.39.1.13.1.1.2.10 |
jnxJsAVScanCodeEngineNotReadyNumber of requests cannot be scanned due to scan engine not ready.rodeprecated Integer32 .1.3.6.1.4.1.2636.3.39.1.13.1.1.2.11 |
jnxJsUTMAntiVirusEngineTable of anti-virus engine objects. SEQUENCE OF JnxJsUTMAntiVirusEngineEntry .1.3.6.1.4.1.2636.3.39.1.13.1.1.3 |
jnxJsUTMAntiVirusEngineEntryEntry for anti-virus engine table. JnxJsUTMAntiVirusEngineEntry .1.3.6.1.4.1.2636.3.39.1.13.1.1.3.1 |
jnxJsUTMAVEngineIndexIndex is the cluster node number. If the device is
not in a cluster mode then it will be the local node
number. Integer32 (0..'7fffffff'h) .1.3.6.1.4.1.2636.3.39.1.13.1.1.3.1.1 |
jnxJsUTMAVEngineTypeThe scan engine type in use. User can use CLI to set the
engine type to either full AV (kaspersky-lab-engine),
express AV (juniper-express-engine) or Sophos AV
(sophos-engine). If AV is not configured then engine type
is not known.ro Enumeration .1.3.6.1.4.1.2636.3.39.1.13.1.1.3.1.2 |
jnxJsUTMAVPatternVersionStringAnti-Virus pattern database version currently in use.ro DisplayString .1.3.6.1.4.1.2636.3.39.1.13.1.1.3.1.3 |
jnxJsUTMAVDatabaseTypeThe Database type in use. User can use CLI to set the
engine type to full AV, express AV or Sophos AV.
Corresponding database types are Full for KL Engine,
Express for Juniper Express Engine and Sophos for Sophos
AV Engine.ro Enumeration .1.3.6.1.4.1.2636.3.39.1.13.1.1.3.1.4 |
jnxJsUTMAntiVirusStatsTable of anti-virus stats objects. SEQUENCE OF JnxJsUTMAntiVirusStatsEntry .1.3.6.1.4.1.2636.3.39.1.13.1.1.4 |
jnxJsUTMAntiVirusStatsEntryEntry of anti-virus stats object. JnxJsUTMAntiVirusStatsEntry .1.3.6.1.4.1.2636.3.39.1.13.1.1.4.1 |
jnxJsUTMAVStatsIndexIndex is the cluster node number. If the device is
not in a cluster mode then it will be the local node
number. Integer32 (0..'7fffffff'h) .1.3.6.1.4.1.2636.3.39.1.13.1.1.4.1.1 |
jnxJsUTMAVScanCodeCleanNumber of requests passed Anti-Virus scan.ro Integer32 .1.3.6.1.4.1.2636.3.39.1.13.1.1.4.1.2 |
jnxJsUTMAVScanCodeInfectedNumber of requests found infected by Anti-Virus scan engine.ro Integer32 .1.3.6.1.4.1.2636.3.39.1.13.1.1.4.1.3 |
jnxJsUTMAVScanCodeProtectedNumber of requests cannot be scanned due to protected by password.ro Integer32 .1.3.6.1.4.1.2636.3.39.1.13.1.1.4.1.4 |
jnxJsUTMAVScanCodeDecompressNumber of requests cannot be scanned due to exceeding max
decmopress layer.ro Integer32 .1.3.6.1.4.1.2636.3.39.1.13.1.1.4.1.5 |
jnxJsUTMAVScanCodeCorruptedNumber of requests cannot be scanned due to file corrupted.ro Integer32 .1.3.6.1.4.1.2636.3.39.1.13.1.1.4.1.6 |
jnxJsUTMAVScanCodeNoResourceNumber of requests cannot be scanned due to out-of-resource.ro Integer32 .1.3.6.1.4.1.2636.3.39.1.13.1.1.4.1.7 |
jnxJsUTMAVScanCodeInternalErrorNumber of requests cannot be scanned due to internal error.ro Integer32 .1.3.6.1.4.1.2636.3.39.1.13.1.1.4.1.8 |
jnxJsUTMAVScanCodeMaxContentSizeNumber of requests cannot be scanned due to exceeding max content
size limit.ro Integer32 .1.3.6.1.4.1.2636.3.39.1.13.1.1.4.1.9 |
jnxJsUTMAVScanCodeTooManyReqNumber of requests cannot be scanned due to exceeding maximum
requests limit.ro Integer32 .1.3.6.1.4.1.2636.3.39.1.13.1.1.4.1.10 |
jnxJsUTMAVScanCodeTimeoutNumber of requests cannot be scanned due to scan timeout.ro Integer32 .1.3.6.1.4.1.2636.3.39.1.13.1.1.4.1.11 |
jnxJsUTMAVScanCodeEngineNotReadyNumber of requests cannot be scanned due to scan engine not ready.ro Integer32 .1.3.6.1.4.1.2636.3.39.1.13.1.1.4.1.12 |
jnxJsUTMAVScanCodeServerConnErrorNumber of requests cannot be scanned due to server connection error.ro Integer32 .1.3.6.1.4.1.2636.3.39.1.13.1.1.4.1.13 |
jnxJsAntiVirusTraps OBJECT IDENTIFIER .1.3.6.1.4.1.2636.3.39.1.13.1.2 |
jnxJsAntiVirusTrapVars OBJECT IDENTIFIER .1.3.6.1.4.1.2636.3.39.1.13.1.3 |
jnxAVPatternVersionStringAnti-Virus last successfully updated pattern database version.ro DisplayString .1.3.6.1.4.1.2636.3.39.1.13.1.3.1 |
jnxAVPatternTimestampAnti-Virus last successfully updated pattern database timestamp.ro DisplayString .1.3.6.1.4.1.2636.3.39.1.13.1.3.2 |
More MIBs from Juniper Networks
Browse all Juniper NetworksMIBs →The JUNIPER-CHASSIS-DEFINES-MIB establishes the foundational Object Identifier (OID) namespace and data type definitions required to map and identify specific Juniper chassis hardware platforms and their internal physical components. This module serves as the structural prerequisite for the JUNIPER-CHASSIS-MIB, enabling the retrieval of inventory data, component status, and hardware topology details for Juniper MX, PTX, and EX series devices.
The JUNIPER-MOBILE-GATEWAY-GTP-MIB provides SNMP objects for monitoring GTP (GPRS Tunneling Protocol) session states, tunnel endpoints, and protocol counters on Juniper mobile gateway platforms. It enables administrators to track GTP-C and GTP-U traffic statistics, error conditions, and active tunnel metrics essential for validating mobile core network connectivity.
SNMP MIB module
SNMP MIB module
The JUNIPER-MOBILE-GATEWAY-SGW-GTP-MIB module enables monitoring of GTP (GPRS Tunneling Protocol) session states and traffic counters on Juniper Mobile Gateway Serving Gateways (SGW). It provides specific objects for tracking GTP-C and GTP-U tunnel establishment, teardown, and packet throughput metrics essential for validating mobile core network connectivity.
The JUNIPER-IPSEC-FLOW-MON-MIB monitors Juniper Networks IPsec VPN infrastructure by exposing tables for IKE tunnels, IPSec tunnels, and IPSec security associations to track tunnel states, association parameters, and flow statistics. This module facilitates the management of IPsec security policies and the operational status of encrypted traffic flows within the device's security architecture.