MIBファイル: ASYNCOS-MAIL-MIB.txt
LAST-UPDATED: 202006150000Z
2024年1月

No
TYPE
1 OBJECT-TYPEOBJECT
asyncOSMailObjects (1)OID.1.3.6.1.4.1.15497.1.1.1

SYNTAX-DESCRIPTION

備考

-

2

perCentMemoryUtilization (1).1.3.6.1.4.1.15497.1.1.1.1

Integer32

This object provides a general idea of how much
メモリ使用率memory is being consumed by the appliance software.

3

perCentCPUUtilization (2).1.3.6.1.4.1.15497.1.1.1.2

Integer32

This object provides a general idea of how busy the
CPU使用率CPU is according to the appliance software, within
the last 5 seconds of utilization.
This measurement may or may not reflect the overall
CPU utilization of the appliance, and may or may not
be a per-process or a per-thread CPU utilization
value.

4

perCentDiskIOUtilization (3).1.3.6.1.4.1.15497.1.1.1.3

Integer32

This object provides a general idea of how much disk ディスクI/O使用率
I/O has been generated within the last 5-15 seconds.

5

perCentQueueUtilization (4).1.3.6.1.4.1.15497.1.1.1.4

Integer32

Percent of total queue capacity used.

6

queueAvailabilityStatus (5).1.3.6.1.4.1.15497.1.1.1.5

INTEGERqueueSpaceAvailable (1)queueSpaceShortage (2)queueFull (3)Queue space status: enough space, queue near full or キュー容量
queue full.
1: キュー容量が十分
2: キュー容量が不足
3: キュー容量がいっぱい

7

resourceConservationReason (6).1.3.6.1.4.1.15497.1.1.1.6

INTEGER
noResourceConservation (1)memoryShortage (2)queueSpaceShortage (3)queueFull (4)Reason system is in Resource Conservation Mode.

リソース節約モードに入る理由
1: リソース節約モードではない (平常時)
2: メモリが不足
3: キュー容量が不足
4: キュー容量がいっぱい

8

memoryAvailabilityStatus (7).1.3.6.1.4.1.15497.1.1.1.7

INTEGER
memoryAvailable (1)memoryShortage (2)memoryFull (3)Mail Transfer process's memory availability status.

メール転送プロセスのメモリ使用状況
1: メモリ容量が十分
2: メモリ容量が不足
3: メモリ容量がいっぱい

9

powerSupplyTable (8).1.3.6.1.4.1.15497.1.1.1.8

10

powerSupplyEntry (1)-.1.3.6.1.4.1.15497.1.1.1.8.1-

キュー使用率A table of one or power supply entries.
Entry containing the status of a power supply and thecorresponding power supply configuration redundancy
state.

11

powerSupplyIndex (1).1.3.6.1.4.1.15497.1.1.1.8.1.1

Integer32

Unique index for a power supply source. This index isfor SNMP purposes only; it has no intrinsic value.

12

powerSupplyStatus (2).1.3.6.1.4.1.15497.1.1.1.8.1.2

INTEGERpowerSupplyNotInstalled (1)powerSupplyHealthy (2)powerSupplyNoAC (3)powerSupplyFaulty (4)Represents the status of a power supply.
powerSupplyNotInstalled The power supply is not detected by the chassis as
being physically present.

電源装置の状態
1: 電源装置が認識されていない
2: 電源装置が電力を供給している
3: 電源装置が電力を供給していない
4: 電源装置が故障している

powerSupplyHealthy The power supply is physically present and is actively
servicing the appliance with power.
powerSupplyNoAC The power supply is physically present but is not
actively servicing the appliance with power.
powerSupplyFaulty The power supply is failed per the vendor defined
operating specifications for the power supply.
13

powerSupplyRedundancy (3).1.3.6.1.4.1.15497.1.1.1.8.1.3

INTEGERpowerSupplyRedundancyOK (1)powerSupplyRedundancyLost (2)Represents the status of a collection of one or more
power supplies.

電源冗長性の状態
1: 冗長性が正常
2: 冗長性が損失

powerSupplyRedundancyOK All power supplies are in a powerSupplyHealthy state.
powerSupplyRedundancyLost One or more power supplies are in a
powerSupplyNotInstalled, powerSupplyNoAC, or
powerSupplyFaulty state.
14
15
16

powerSupplyName (4)temperatureTable (9)temperatureEntry (1).1.3.6.1.4.1.15497.1.1.1.8.1.4

DisplayString.1.3.6.1.4.1.15497.1.1.1.9

A textual name for a power supply.

-.1.3.6.1.4.1.15497.1.1.1.9.1-

A table of chassis temperature sensor states.
An entry in the temperature sensor table representing
the status of the corresponding sensor in or on theappliance.

17

temperatureIndex (1).1.3.6.1.4.1.15497.1.1.1.9.1.1

Integer32

Unique index for the temperature sensor being
instrumented.
This index is for SNMP purposes only; it has no
intrinsic value.

18

degreesCelsius (2).1.3.6.1.4.1.15497.1.1.1.9.1.2

Integer32

Temperature reading for the sensor being
instrumented in Centrigrade units.
This is correct according to the relative accuracy ofthe sensor being instrumented.

19

temperatureName (3).1.3.6.1.4.1.15497.1.1.1.9.1.3

DisplayString

Textual description for sensor being instrumented.
This description is a short textual label, suitable as ahuman-sensible identification for the rest of theinformation in the entry.

20
21

fanTable (10)fanEntry (1).1.3.6.1.4.1.15497.1.1.1.10-.1.3.6.1.4.1.15497.1.1.1.10.1-

温度測定値 (Centigrade 単位)

A table of chassis fan entries.
An entry in the chassis fan table with the speed of a
fan in the chassis, as well as the name of thecorresponding fan.

22

fanIndex (1).1.3.6.1.4.1.15497.1.1.1.10.1.1

Integer32

Unique index of the chassis fan being instrumented.
This index is for SNMP purposes only; it has no
intrinsic value.

23

fanRPMs (2).1.3.6.1.4.1.15497.1.1.1.10.1.2

Gauge32

Speed in RPMs of a chassis fan being instrumented.
The speed that corresponds to a fan failure varies
depending on the vendor specification and airflow
requirements for the appliance it's instrumented in,
but in general when fanRPMs reports 0 RPMs therespective fan has failed.

24

fanName (3).1.3.6.1.4.1.15497.1.1.1.10.1.3

DisplayString

A textual name of the chassis fan being instrumented.

25

workQueueMessages (11).1.3.6.1.4.1.15497.1.1.1.11

Gauge32

Number of messages in the work queue.

ファン速度 (RPM 単位)

作業キュー内のメッセージ数

26
27

keyExpirationTable (12)keyExpirationEntry (1).1.3.6.1.4.1.15497.1.1.1.12-.1.3.6.1.4.1.15497.1.1.1.12.1-

A table of Feature Key expiration entries.
Entry containing a Feature Key, its expiration status,
and whether or not the Feature Key is perpetual.

28

keyExpirationIndex (1).1.3.6.1.4.1.15497.1.1.1.12.1.1

Integer32

Unique index for a Feature Key applicable to theappliance.
This index is for SNMP purposes only; it has no
intrinsic value.

29

keyDescription (2).1.3.6.1.4.1.15497.1.1.1.12.1.2

DisplayString

Textual description for a Feature Key applicable tothe appliance.

30

keyIsPerpetual (3).1.3.6.1.4.1.15497.1.1.1.12.1.3

TruthValue
true (1)false (2)

Boolean value represented by True if Feature Key isperpetual, or False if the Feature Key is normal or
expired.

ライセンスキーの状態
1: ライセンスキーが永続的
2: ライセンスキーが正常または失効

31

keySecondsUntilExpire (4).1.3.6.1.4.1.15497.1.1.1.12.1.4

Gauge32

Seconds until the valid Feature Key expires.
Only applies to non-perpetual Feature Keys, and is 0
when the Feature Key has expired.

ライセンスキーが失効するまでの秒数

32
33

updateTable (13)updateEntry (1).1.3.6.1.4.1.15497.1.1.1.13-.1.3.6.1.4.1.15497.1.1.1.13.1-

A table of one or more update entries.
Entry containing a name and number of successful
and failed updates for a service, including but notlimited to: spam or virus definitions and timezone
updates.

34

updateIndex (1).1.3.6.1.4.1.15497.1.1.1.13.1.1

Integer32

Unique index for an update service.
This index is for SNMP purposes only; it has no
intrinsic value.

35

updateServiceName (2).1.3.6.1.4.1.15497.1.1.1.13.1.2

DisplayString

A textual name for an update entry.

36

updates (3).1.3.6.1.4.1.15497.1.1.1.13.1.3

Counter32

The number of successful attempts that haveoccurred when updating a service.

サービスのアップデートに成功した回数

37

updateFailures (4).1.3.6.1.4.1.15497.1.1.1.13.1.4

Counter32

The number of failed attempts that have occurred
when updating a service.

サービスのアップデートに失敗した回数

38

oldestMessageAge (14).1.3.6.1.4.1.15497.1.1.1.14

Gauge32

The number of seconds the oldest message has been 最も古いメッセージがキューに存在していた秒数
in queue

39

outstandingDNSRequests (15).1.3.6.1.4.1.15497.1.1.1.15

Gauge32

Number of DNS requests that have been sent but for 応答の無いDNSリクエスト数
which no reply has been received.

40

pendingDNSRequests (16).1.3.6.1.4.1.15497.1.1.1.16

Gauge32

Number of DNS requests waiting to be sent.

41

raidEvents (17).1.3.6.1.4.1.15497.1.1.1.17

Counter32

The total number of RAID events that have occurred 電源投入後に発生したRAIDイベントの総数
since the last appliance power on event.

42

raidTable (18).1.3.6.1.4.1.15497.1.1.1.18-

43

raidEntry (1).1.3.6.1.4.1.15497.1.1.1.18.1-

送信待ちのDNSリクエスト数

Unique index for a drive being instrumented in theappliance.
This index is for SNMP purposes only; it has no
intrinsic value.
An entry in the RAID table representing the status ofa drive attached to a RAID controller in the appliance.

44

raidIndex (1).1.3.6.1.4.1.15497.1.1.1.18.1.1

Integer32

Unique index for a drive attached to a RAID controller
in the appliance.
This index is for SNMP purposes only; it has no
intrinsic value.

45

raidStatus (2).1.3.6.1.4.1.15497.1.1.1.18.1.2

INTEGERdriveHealthy (1)driveFailure (2)driveRebuild (3)Represents the status of a a drive attached to a
RAID controller in the appliance.

RAIDコントローラの状態
1: ドライブが正常
2: ドライブが異常
driveHealthy 3: ドライブが再構築中
The corresponding drive is connected to the RAID
controller and functioning as a healthy member in the
RAID volume.
driveFailure The drive is either disconnected from the RAID
controller, or has failed to operate within thresholds
defined in vendor specifications for the drive and thecontroller.
driveRebuild The corresponding drive is connected to the RAID
controller.
It is being rebuilt according to the RAID controller
specific rebuild algorithm for the current operating
mode of the RAID volume.

46

raidID (3).1.3.6.1.4.1.15497.1.1.1.18.1.3

DisplayString

A textual name for a drive attached to a RAID
controller in the appliance.

47

raidLastError (4).1.3.6.1.4.1.15497.1.1.1.18.1.4

DisplayString

The textual description of the last error message
reported by the RAID controller or corresponding
driver if one has occurred.

RAIDコントローラのエラーメッセージ (最後)This is 'No Error' if the corresponding drive's state isdriveHealthy, or a controller or driver defined specifictextual description if the drive's state is not
driveHealthy.
48

openFilesOrSockets (19).1.3.6.1.4.1.15497.1.1.1.19

Gauge32

This object notes how many files or sockets are open ファイルまたはソケットのオープン数
on the appliance.
In normal operating conditions, the measurement istaken at least once every 5-15 seconds.

49

mailTransferThreads (20).1.3.6.1.4.1.15497.1.1.1.20

Gauge32

Number of threads that perform some task related to メール転送関連のタスクを実行するスレッド数
transferring mail.

50

connectionURL (21).1.3.6.1.4.1.15497.1.1.1.21

DisplayString

The URL which will be used to test HTTP URL
connectivity.

HTTP URL接続のテストに使用されるURL

51

hsmErrorReason (22).1.3.6.1.4.1.15497.1.1.1.22

DisplayString

A textual reason describing the last HSM
authentication error.

FIPS準拠のHSM (Hardware Security Module) 関連※現時点でHSMは未実装

52

fipsMode (23).1.3.6.1.4.1.15497.1.1.1.23

TruthValue
true (1)false (2)

Boolean value represented by True if FIPS Mode isenabled, or False if the FIPS Mode is not enabled.

FIPSモードの状態
1: FIPSモードが有効
2: FIPSモードが無効

53

fipsApplicationName (24).1.3.6.1.4.1.15497.1.1.1.24

DisplayString

The human-sensible name of the application thatfailed to enter FIPS mode.

54

failoverApplicationName (25).1.3.6.1.4.1.15497.1.1.1.25

DisplayString

The human-sensible name of the application thatcaused failover in watchdog.

※将来的な用途のために用意されている機能であり、現時点で failoverApplication は存在しない

55

perCentCPULoad (26).1.3.6.1.4.1.15497.1.1.1.26

Integer32

This object provides a general idea of how many
processes are waiting in ready queue for CPU.
This measurment tells how much the CPU is loaded.

CPU ロード率56

diskUtilization (27).1.3.6.1.4.1.15497.1.1.1.27

DisplayString

Displays the disk space utilization.

ディスク容量使用率

57

ProxyConnectionBacklog (28).1.3.6.1.4.1.15497.1.1.1.28

DisplayString

Displays the Proxy Connection Backlog.

プロキシ接続のバックログ数

58 NOTIFICATIONTYPE
59

60

asyncOSMailNotifications (2)resourceConservationMode (1)powerSupplyStatusChange (2).1.3.6.1.4.1.15497.1.1.2

-

-

-

Memory or queue utilization caused system to enter
resource conservation mode.

.1.3.6.1.4.1.15497.1.1.2.1.1.3.6.1.4.1.15497.1.1.2.2-

61

highTemperature (3).1.3.6.1.4.1.15497.1.1.2.3-

62

fanFailure (4)keyExpiration (5)updateFailure (6)A keyExpiration notification is sent when thecorresponding Feature Key is pending expiration or
has expired.
This notification contains the opaque type for the
keyDescription of the Feature Key that is pending
expiration or has expired.

ライセンスキーの失効

The number of failed attempts that have occurred
when updating a service.

サービスのアップデートの失敗

A raidStatusChange notification is sent when drivewith raidID changes states, as per one of the statesavailable in raidStatus.
This notification contains the opaque type for raidIDof the drive which has changed state.

RAIDコントローラの状態変化

A connectivityFailure notification is sent when the
URL denoted by configured connectionURL is
unreachable, or the request returned an HTTP code
was not between 200, inclusive, and 300, exclusive.
The connectionURL configured is returned when the
notification is triggered.

HTTP URL接続のテストに使用されるURLにアクセスできない-

A memoryUtilizationExceeded notification is sent
when the value in perCentMemoryUtilization has
exceeded the configured memory usage threshold.
The percentage that exceeded the threshold in
perCentMemoryUtilization is returned via thenotification.

メモリ使用率のしきい値を超える-.1.3.6.1.4.1.15497.1.1.2.5.1.3.6.1.4.1.15497.1.1.2.6-

65

raidStatusChange (7).1.3.6.1.4.1.15497.1.1.2.7
-

66

67

68

connectivityFailure (8)memoryUtilizationExceeded (9)cpuUtilizationExceeded (10).1.3.6.1.4.1.15497.1.1.2.8.1.3.6.1.4.1.15497.1.1.2.9.1.3.6.1.4.1.15497.1.1.2.10-

69

hsmInitializationFailure (11).1.3.6.1.4.1.15497.1.1.2.11-

70

hsmResetLoginFailure (12).1.3.6.1.4.1.15497.1.1.2.12-

71

fipsModeEnableFailure (13).1.3.6.1.4.1.15497.1.1.2.13-

72

fipsModeDisableFailure (14).1.3.6.1.4.1.15497.1.1.2.14-

73

failoverUnhealthy (15).1.3.6.1.4.1.15497.1.1.2.15-

74

failoverHealthy (16)A highTemperature notification is sent when the
シャーシ内の温度が高温
temperature of an instrumented sensor in the chassis
has exceeded vendor defined specifications.
This notification contains the opaque type for thetemperatureName of the sensor which has failed.
ファン速度の異常-

64

A powerSupplyStatusChange notification is sent when 電源装置の状態変化
power supply with powerSupplyName changes states,
as per one of the states available inpowerSupplyStatus.
This notification contains the opaque type forpowerSupplyName of the power supply which haschanged state.

A fanFailure notification is sent when the speed of
the fan is not operating per the vendor defined
specifications, as discussed in fanRPMs.
This notification contains the opaque type for the
fanName of the fan which has failed.".1.3.6.1.4.1.15497.1.1.2.4-

63

メモリまたはキューの使用率により、リソース節約モー
ドに入る.1.3.6.1.4.1.15497.1.1.2.16-

A cpuUtilizationExceeded notification is sent when
CPU使用率のしきい値を超える
the value in perCentCPUUtilization has exceeded theconfigured CPU usage threshold.
The percentage that exceeded the threshold in
perCentCPUUtilization is returned via the notification.
A hsmInitializationFailure notification is sent when the HSM (Hardware Security Module) カードを初期化できHardware Security Module card cannot be initialized. ない
The initialization error in hsmErrorReason is returned ※現時点でHSMは未実装
via the notification.
A hsmResetLoginFailure notification is sent when the HSM (Hardware Security Module) カードのリセット
Hardware Security Module card is reset due to※現時点でHSMは未実装
multiple Crypto Officer login failures.
The reset login error in hsmErrorReason is returned
via the notification.
A fipsModeEnableFailure notification is sent when aprocess can not enter FIPS mode.
The name in fipsApplicationName is returned via thenotification.

FIPSモードに入ることができない

A fipsModeDisableFailure notification is sent when aprocess can not exit FIPS mode.
The name in fipsApplicationName is returned via thenotification.

FIPSモードを終了できない

A failoverUnhealthy notification is sent when aprocess is deemed unhealthy and triggers a failover.
The name in failoverApplicationName is returned via
the notification.

※将来的な用途のために用意されている機能であり、現時点で failoverApplication は存在しない

A failoverHealthy notification is sent when a process
becomes healthy coming out of a failover.
The name in failoverApplicationName is returned via
the notification.

※将来的な用途のために用意されている機能であり、現時点で failoverApplication は存在しない

75 OBJECT-TYPE
76

77

asyncOSMailGatewayStatus (3)asyncOSMailGatewayStatusRates (1)injMessages (1).1.3.6.1.4.1.15497.1.1.3

-

-

-

-

.1.3.6.1.4.1.15497.1.1.3.1.1.3.6.1.4.1.15497.1.1.3.1.1
-

-

78

injMessagesInOneMin (1).1.3.6.1.4.1.15497.1.1.3.1.1.1

Integer32

Messages received in last 1 minute79

injMessagesInFiveMins (2).1.3.6.1.4.1.15497.1.1.3.1.1.2

Integer32

Messages received in last 5 minutes

80

injMessagesInFifteenMins (3).1.3.6.1.4.1.15497.1.1.3.1.1.3

Integer32

Messages received in last 15 minutes

81

injRecipients (2).1.3.6.1.4.1.15497.1.1.3.1.2
-

-

82

injRecipientsInOneMin (1).1.3.6.1.4.1.15497.1.1.3.1.2.1

Integer32

Recipients for which messages received in last 1
minute83

injRecipientsInFiveMin (2).1.3.6.1.4.1.15497.1.1.3.1.2.2

Integer32

Recipients for which messages received in last 5
minutes

injRecipientsInFifteenMins (3).1.3.6.1.4.1.15497.1.1.3.1.2.3

Integer32

Recipients for which messages received in last 15
minutes84

85

softBouncedEvents (3).1.3.6.1.4.1.15497.1.1.3.1.3
-

-

86

softBouncedEventsInOneMin (1).1.3.6.1.4.1.15497.1.1.3.1.3.1

Integer32

Soft bounced events in last 1 minute87

softBouncedEventsInFiveMin (2).1.3.6.1.4.1.15497.1.1.3.1.3.2

Integer32

Soft bounced events in last 5 minutes

88

softBouncedEventsInFifteenMins (3).1.3.6.1.4.1.15497.1.1.3.1.3.3

Integer32

Soft bounced events in last 15 minutes

89

completedRecipients (4).1.3.6.1.4.1.15497.1.1.3.1.4
-

-

90

completedRecipientsInOneMin (1).1.3.6.1.4.1.15497.1.1.3.1.4.1

Integer32

Total completed recipients in last 1 minute91

completedRecipientsInFiveMin (2).1.3.6.1.4.1.15497.1.1.3.1.4.2

Integer32

Total completed recipient in last 5 minutes

92

completedRecipientsInFifteenMins (3) .1.3.6.1.4.1.15497.1.1.3.1.4.3

Integer32

Total completed recipient in last 15 minutes

93

hardBouncedRecipients (5).1.3.6.1.4.1.15497.1.1.3.1.5
-

-

94

hardBouncedRecipientsInOneMin (1).1.3.6.1.4.1.15497.1.1.3.1.5.1

Integer32

Hard bounced recipients in last 1 minute95

hardBouncedRecipientsInFiveMin (2).1.3.6.1.4.1.15497.1.1.3.1.5.2

Integer32

Hard bounced recipients in last 5 minutes

96

hardBouncedRecipientsInFifteenMins (3).1.3.6.1.4.1.15497.1.1.3.1.5.3

Integer32

Hard bounced recipients in last 15 minutes

97

deliveredRecipients (6).1.3.6.1.4.1.15497.1.1.3.1.6
-

-

98

deliveredRecipientsInOneMin (1).1.3.6.1.4.1.15497.1.1.3.1.6.1

Integer32

Delivered recipients in last 1 minute99

deliveredRecipientsInFiveMin (2).1.3.6.1.4.1.15497.1.1.3.1.6.2

Integer32

Delivered recipient in last 5 minutes

100

deliveredRecipientsInFifteenMins (3).1.3.6.1.4.1.15497.1.1.3.1.6.3

Integer32

Delivered recipient in last 15 minutes

101

asyncOSMailGatewayStatusGauges (2).1.3.6.1.4.1.15497.1.1.3.2
-

-

102

ramUtilization (1).1.3.6.1.4.1.15497.1.1.3.2.1

Integer32

Ram utilization

103

totalUtilization (2).1.3.6.1.4.1.15497.1.1.3.2.2

Integer32

Overall CPU utilization

104

cpuUtilization (3).1.3.6.1.4.1.15497.1.1.3.2.3

Integer32

CPU Utilization by other process/Mail Processing

105

avUtilization (4).1.3.6.1.4.1.15497.1.1.3.2.4

Integer32

CPU utilization by AntiVirus

106

caseUtilization (5).1.3.6.1.4.1.15497.1.1.3.2.5

Integer32

CPU Utilization by CASE/Antispam

107

diskIOUtilization (6).1.3.6.1.4.1.15497.1.1.3.2.6

Integer32

Disk I/O utilization

108

resourceConservationValue (7).1.3.6.1.4.1.15497.1.1.3.2.7

Integer32

Resource conservation value

109

loggingDiskUsage (8).1.3.6.1.4.1.15497.1.1.3.2.8

Integer32

Logging disk usage110

loggingDiskAvailable (9).1.3.6.1.4.1.15497.1.1.3.2.9

DisplayString

Logging disk available

111

connectionsInbound (10).1.3.6.1.4.1.15497.1.1.3.2.10

Integer32

Current inbound connections

112

connectionsOutbound (11).1.3.6.1.4.1.15497.1.1.3.2.11

Integer32

Current outbound connections

113

activeRecipientsInMail (12).1.3.6.1.4.1.15497.1.1.3.2.12

Integer32

Active recipients in delivery queue

114

unattemptedRecipientsInMail (13).1.3.6.1.4.1.15497.1.1.3.2.13

Integer32

Unattempted recipients in delivery queue

115

attemptedRecipientsInMail (14).1.3.6.1.4.1.15497.1.1.3.2.14

Integer32

Attempted recipients in delivery queue

116

messagesInWorkQueue (15).1.3.6.1.4.1.15497.1.1.3.2.15

Integer32

Messages in work queue

117

destinationsInMemory (16).1.3.6.1.4.1.15497.1.1.3.2.16

Integer32

Destinations in memory

118

mailQueueSpaceUsedInKB (17).1.3.6.1.4.1.15497.1.1.3.2.17

Integer32

Total mail queue space used in KB

119

mailQueueSpaceFreeInKB (18).1.3.6.1.4.1.15497.1.1.3.2.18

Integer32

Total mail queue space free in KB

120

quarantinedMessages (19).1.3.6.1.4.1.15497.1.1.3.2.19

Integer32

Messages in policy, virus and outbreak quarantine

121

spaceUsedByQuarantinedMessages (20).1.3.6.1.4.1.15497.1.1.3.2.20

Integer32

Space used by policy, virus and outbreak quarantine
in KB

122

reportingUtilization (21).1.3.6.1.4.1.15497.1.1.3.2.21

Integer32

CPU utilization by reporting123

quarantineUtilization (22).1.3.6.1.4.1.15497.1.1.3.2.22

Integer32

CPU utilization by quarantine