EZ5 MIB Catalog

JUNIPER-JS-UTM-AV-MIB

2011-02-08

This module defines the MIB for Juniper Enterprise specific antivirus functionality. Juniper documentation is recommended as the reference.

Download JUNIPER-JS-UTM-AV-MIB.txt Open JUNIPER-JS-UTM-AV-MIB.txt in a new tab

SCALARS (16) · TABLES (2) · TRAPS (1)

Scalars (16)

NameOID
jnxJsAVEngineType1.3.6.1.4.1.2636.3.39.1.13.1.1.1.1
jnxJsAVCurrentPatternVersionString1.3.6.1.4.1.2636.3.39.1.13.1.1.1.2
jnxJsAVDatabaseType1.3.6.1.4.1.2636.3.39.1.13.1.1.1.3
jnxJsAVScanCodeClean1.3.6.1.4.1.2636.3.39.1.13.1.1.2.1
jnxJsAVScanCodeInfected1.3.6.1.4.1.2636.3.39.1.13.1.1.2.2
jnxJsAVScanCodeProtected1.3.6.1.4.1.2636.3.39.1.13.1.1.2.3
jnxJsAVScanCodeDecompress1.3.6.1.4.1.2636.3.39.1.13.1.1.2.4
jnxJsAVScanCodeCorrupted1.3.6.1.4.1.2636.3.39.1.13.1.1.2.5
jnxJsAVScanCodeNoResource1.3.6.1.4.1.2636.3.39.1.13.1.1.2.6
jnxJsAVScanCodeInternalError1.3.6.1.4.1.2636.3.39.1.13.1.1.2.7
jnxJsAVScanCodeMaxContentSize1.3.6.1.4.1.2636.3.39.1.13.1.1.2.8
jnxJsAVScanCodeTooManyReq1.3.6.1.4.1.2636.3.39.1.13.1.1.2.9
jnxJsAVScanCodeTimeout1.3.6.1.4.1.2636.3.39.1.13.1.1.2.10
jnxJsAVScanCodeEngineNotReady1.3.6.1.4.1.2636.3.39.1.13.1.1.2.11
jnxAVPatternVersionString1.3.6.1.4.1.2636.3.39.1.13.1.3.1
jnxAVPatternTimestamp1.3.6.1.4.1.2636.3.39.1.13.1.3.2

Tables (2)

NameOID
jnxJsUTMAntiVirusEngine1.3.6.1.4.1.2636.3.39.1.13.1.1.3
jnxJsUTMAntiVirusStats1.3.6.1.4.1.2636.3.39.1.13.1.1.4

Traps (1)

NameOID
jnxJsAvPatternUpdateTrap1.3.6.1.4.1.2636.3.39.1.13.1.0.1

END OF TOC

Scalar details

jnxJsAVEngineType

1.3.6.1.4.1.2636.3.39.1.13.1.1.1.1

INTEGER1 = unknown-engine2 = kaspersky-lab-engine3 = juniper-express-engine4 = sophos-engine · Integer32

The 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.

jnxJsAVCurrentPatternVersionString

1.3.6.1.4.1.2636.3.39.1.13.1.1.1.2

DisplayStringRepresents textual information taken from the NVT ASCII character set, as defined in pages 4, 10-11 of RFC 854. To summarize RFC 854, the NVT ASCII repertoire specifies: - the use of character codes 0-127 (decimal) - the graphics characters (32-126) are interpreted as US ASCII - NUL, LF, CR, BEL, BS, HT, VT and FF have the special meanings specified in RFC 854 - the other 25 codes have no standard interpretation - the sequence 'CR LF' means newline - the sequence 'CR NUL' means carriage-return - an 'LF' not preceded by a 'CR' means moving to the same column on the next line. - the sequence 'CR x' for any x other than LF or NUL is illegal. (Note that this also means that a string may end with either 'CR LF' or 'CR NUL', but not with CR.) Any object defined using this syntax may not exceed 255 characters in length. SIZE (1..255) · OCTET STRING · hint 255a

Anti-Virus pattern database version currently in use.

jnxJsAVDatabaseType

1.3.6.1.4.1.2636.3.39.1.13.1.1.1.3

INTEGER1 = full2 = express3 = unknown4 = sophos · Integer32

The 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.

jnxJsAVScanCodeClean

1.3.6.1.4.1.2636.3.39.1.13.1.1.2.1

Integer32

Number of requests passed Anti-Virus scan.

jnxJsAVScanCodeInfected

1.3.6.1.4.1.2636.3.39.1.13.1.1.2.2

Integer32

Number of requests found infected by Anti-Virus scan engine.

jnxJsAVScanCodeProtected

1.3.6.1.4.1.2636.3.39.1.13.1.1.2.3

Integer32

Number of requests cannot be scanned due to protected by password.

jnxJsAVScanCodeDecompress

1.3.6.1.4.1.2636.3.39.1.13.1.1.2.4

Integer32

Number of requests cannot be scanned due to exceeding max decmopress layer.

jnxJsAVScanCodeCorrupted

1.3.6.1.4.1.2636.3.39.1.13.1.1.2.5

Integer32

Number of requests cannot be scanned due to file corrupted.

jnxJsAVScanCodeNoResource

1.3.6.1.4.1.2636.3.39.1.13.1.1.2.6

Integer32

Number of requests cannot be scanned due to out-of-resource.

jnxJsAVScanCodeInternalError

1.3.6.1.4.1.2636.3.39.1.13.1.1.2.7

Integer32

Number of requests cannot be scanned due to internal error.

jnxJsAVScanCodeMaxContentSize

1.3.6.1.4.1.2636.3.39.1.13.1.1.2.8

Integer32

Number of requests cannot be scanned due to exceeding max content size limit.

jnxJsAVScanCodeTooManyReq

1.3.6.1.4.1.2636.3.39.1.13.1.1.2.9

Integer32

Number of requests cannot be scanned due to exceeding maximum requests limit.

jnxJsAVScanCodeTimeout

1.3.6.1.4.1.2636.3.39.1.13.1.1.2.10

Integer32

Number of requests cannot be scanned due to scan timeout.

jnxJsAVScanCodeEngineNotReady

1.3.6.1.4.1.2636.3.39.1.13.1.1.2.11

Integer32

Number of requests cannot be scanned due to scan engine not ready.

jnxAVPatternVersionString

1.3.6.1.4.1.2636.3.39.1.13.1.3.1

DisplayStringRepresents textual information taken from the NVT ASCII character set, as defined in pages 4, 10-11 of RFC 854. To summarize RFC 854, the NVT ASCII repertoire specifies: - the use of character codes 0-127 (decimal) - the graphics characters (32-126) are interpreted as US ASCII - NUL, LF, CR, BEL, BS, HT, VT and FF have the special meanings specified in RFC 854 - the other 25 codes have no standard interpretation - the sequence 'CR LF' means newline - the sequence 'CR NUL' means carriage-return - an 'LF' not preceded by a 'CR' means moving to the same column on the next line. - the sequence 'CR x' for any x other than LF or NUL is illegal. (Note that this also means that a string may end with either 'CR LF' or 'CR NUL', but not with CR.) Any object defined using this syntax may not exceed 255 characters in length. SIZE (1..255) · OCTET STRING · hint 255a

Anti-Virus last successfully updated pattern database version.

jnxAVPatternTimestamp

1.3.6.1.4.1.2636.3.39.1.13.1.3.2

DisplayStringRepresents textual information taken from the NVT ASCII character set, as defined in pages 4, 10-11 of RFC 854. To summarize RFC 854, the NVT ASCII repertoire specifies: - the use of character codes 0-127 (decimal) - the graphics characters (32-126) are interpreted as US ASCII - NUL, LF, CR, BEL, BS, HT, VT and FF have the special meanings specified in RFC 854 - the other 25 codes have no standard interpretation - the sequence 'CR LF' means newline - the sequence 'CR NUL' means carriage-return - an 'LF' not preceded by a 'CR' means moving to the same column on the next line. - the sequence 'CR x' for any x other than LF or NUL is illegal. (Note that this also means that a string may end with either 'CR LF' or 'CR NUL', but not with CR.) Any object defined using this syntax may not exceed 255 characters in length. SIZE (1..255) · OCTET STRING · hint 255a

Anti-Virus last successfully updated pattern database timestamp.

Table details

jnxJsUTMAntiVirusEngine

1.3.6.1.4.1.2636.3.39.1.13.1.1.3

Index: jnxJsUTMAVEngineIndex

Table of anti-virus engine objects.

jnxJsUTMAVEngineIndex

1.3.6.1.4.1.2636.3.39.1.13.1.1.3.1.1

Integer32 (0..2147483647)

Index is the cluster node number. If the device is not in a cluster mode then it will be the local node number.

jnxJsUTMAVEngineType

1.3.6.1.4.1.2636.3.39.1.13.1.1.3.1.2

INTEGER1 = unknown-engine2 = kaspersky-lab-engine3 = juniper-express-engine4 = sophos-engine · Integer32

The 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.

jnxJsUTMAVPatternVersionString

1.3.6.1.4.1.2636.3.39.1.13.1.1.3.1.3

DisplayStringRepresents textual information taken from the NVT ASCII character set, as defined in pages 4, 10-11 of RFC 854. To summarize RFC 854, the NVT ASCII repertoire specifies: - the use of character codes 0-127 (decimal) - the graphics characters (32-126) are interpreted as US ASCII - NUL, LF, CR, BEL, BS, HT, VT and FF have the special meanings specified in RFC 854 - the other 25 codes have no standard interpretation - the sequence 'CR LF' means newline - the sequence 'CR NUL' means carriage-return - an 'LF' not preceded by a 'CR' means moving to the same column on the next line. - the sequence 'CR x' for any x other than LF or NUL is illegal. (Note that this also means that a string may end with either 'CR LF' or 'CR NUL', but not with CR.) Any object defined using this syntax may not exceed 255 characters in length. SIZE (1..255) · OCTET STRING · hint 255a

Anti-Virus pattern database version currently in use.

jnxJsUTMAVDatabaseType

1.3.6.1.4.1.2636.3.39.1.13.1.1.3.1.4

INTEGER1 = full2 = express3 = unknown4 = sophos · Integer32

The 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.

jnxJsUTMAntiVirusStats

1.3.6.1.4.1.2636.3.39.1.13.1.1.4

Index: jnxJsUTMAVStatsIndex

Table of anti-virus stats objects.

jnxJsUTMAVStatsIndex

1.3.6.1.4.1.2636.3.39.1.13.1.1.4.1.1

Integer32 (0..2147483647)

Index is the cluster node number. If the device is not in a cluster mode then it will be the local node number.

jnxJsUTMAVScanCodeClean

1.3.6.1.4.1.2636.3.39.1.13.1.1.4.1.2

Integer32

Number of requests passed Anti-Virus scan.

jnxJsUTMAVScanCodeInfected

1.3.6.1.4.1.2636.3.39.1.13.1.1.4.1.3

Integer32

Number of requests found infected by Anti-Virus scan engine.

jnxJsUTMAVScanCodeProtected

1.3.6.1.4.1.2636.3.39.1.13.1.1.4.1.4

Integer32

Number of requests cannot be scanned due to protected by password.

jnxJsUTMAVScanCodeDecompress

1.3.6.1.4.1.2636.3.39.1.13.1.1.4.1.5

Integer32

Number of requests cannot be scanned due to exceeding max decmopress layer.

jnxJsUTMAVScanCodeCorrupted

1.3.6.1.4.1.2636.3.39.1.13.1.1.4.1.6

Integer32

Number of requests cannot be scanned due to file corrupted.

jnxJsUTMAVScanCodeNoResource

1.3.6.1.4.1.2636.3.39.1.13.1.1.4.1.7

Integer32

Number of requests cannot be scanned due to out-of-resource.

jnxJsUTMAVScanCodeInternalError

1.3.6.1.4.1.2636.3.39.1.13.1.1.4.1.8

Integer32

Number of requests cannot be scanned due to internal error.

jnxJsUTMAVScanCodeMaxContentSize

1.3.6.1.4.1.2636.3.39.1.13.1.1.4.1.9

Integer32

Number of requests cannot be scanned due to exceeding max content size limit.

jnxJsUTMAVScanCodeTooManyReq

1.3.6.1.4.1.2636.3.39.1.13.1.1.4.1.10

Integer32

Number of requests cannot be scanned due to exceeding maximum requests limit.

jnxJsUTMAVScanCodeTimeout

1.3.6.1.4.1.2636.3.39.1.13.1.1.4.1.11

Integer32

Number of requests cannot be scanned due to scan timeout.

jnxJsUTMAVScanCodeEngineNotReady

1.3.6.1.4.1.2636.3.39.1.13.1.1.4.1.12

Integer32

Number of requests cannot be scanned due to scan engine not ready.

jnxJsUTMAVScanCodeServerConnError

1.3.6.1.4.1.2636.3.39.1.13.1.1.4.1.13

Integer32

Number of requests cannot be scanned due to server connection error.

Trap details

jnxJsAvPatternUpdateTrap

1.3.6.1.4.1.2636.3.39.1.13.1.0.1

This traps is raised when the Anti-Virus pattern database is updated successfully.

jnxAVPatternVersionString

1.3.6.1.4.1.2636.3.39.1.13.1.3.1

DisplayStringRepresents textual information taken from the NVT ASCII character set, as defined in pages 4, 10-11 of RFC 854. To summarize RFC 854, the NVT ASCII repertoire specifies: - the use of character codes 0-127 (decimal) - the graphics characters (32-126) are interpreted as US ASCII - NUL, LF, CR, BEL, BS, HT, VT and FF have the special meanings specified in RFC 854 - the other 25 codes have no standard interpretation - the sequence 'CR LF' means newline - the sequence 'CR NUL' means carriage-return - an 'LF' not preceded by a 'CR' means moving to the same column on the next line. - the sequence 'CR x' for any x other than LF or NUL is illegal. (Note that this also means that a string may end with either 'CR LF' or 'CR NUL', but not with CR.) Any object defined using this syntax may not exceed 255 characters in length. SIZE (1..255) · OCTET STRING · hint 255a

Anti-Virus last successfully updated pattern database version.

jnxAVPatternTimestamp

1.3.6.1.4.1.2636.3.39.1.13.1.3.2

DisplayStringRepresents textual information taken from the NVT ASCII character set, as defined in pages 4, 10-11 of RFC 854. To summarize RFC 854, the NVT ASCII repertoire specifies: - the use of character codes 0-127 (decimal) - the graphics characters (32-126) are interpreted as US ASCII - NUL, LF, CR, BEL, BS, HT, VT and FF have the special meanings specified in RFC 854 - the other 25 codes have no standard interpretation - the sequence 'CR LF' means newline - the sequence 'CR NUL' means carriage-return - an 'LF' not preceded by a 'CR' means moving to the same column on the next line. - the sequence 'CR x' for any x other than LF or NUL is illegal. (Note that this also means that a string may end with either 'CR LF' or 'CR NUL', but not with CR.) Any object defined using this syntax may not exceed 255 characters in length. SIZE (1..255) · OCTET STRING · hint 255a

Anti-Virus last successfully updated pattern database timestamp.

↑ To TOC