Event Details - Host Category View

Below details mentioned are event details listed on a per Category basis.

 

Severity Level

Policy ID

Description

Cause

Resolution

7

HOST.X1.1

HOST.X1.1: /mnt is filling up

HOST.X1.1: Alert when the log data partition is over 70 percent capacity

HOST.X1.1: If the event persists, contact Panzura Technical Support.

5

HOST.X1.2

HOST.X1.2: /cache is filling up

HOST.X1.2: Alert when the cloud staging partition is over 80 percent capacity

HOST.X1.2: Check Dashboard for Cache size and Dirty cache. If the Filer is at capacity and the slowness persists, consider stopping writes to Filer.

9

HOST.X1.3

HOST.X1.3: /tmp is filling up

HOST.X1.3: Alert when the /tmp partition is over 80 percent capacity

HOST.X1.3: If the event persists, contact Panzura Technical Support.

5

HOST.X1.4

HOST.X1.4: System CPU usage above 70 percent

HOST.X1.4: Alert when the CPU load is above 70 percent limit

HOST.X1.4: Check for stuck process/leaks or bottlenecks.

9

HOST.X1.5

HOST.X1.5: Zombie Processes are occurring

HOST.X1.5: Alert when zombie processes are higher than normal

HOST.X1.5: Processes that are not able to terminate and are building up and consuming space need support attention. If this event persists, monitor the snapshot sync for 3-4 hours, if the snapshot has a continuous deficit, contact Panzura Technical Support immediately.

9

HOST.X1.6

HOST.X1.6: System Clock has skewed away from the configured AD server, client authentication will fail

HOST.X1.6: Alert when the System Clock skew has drifted from AD and the drift exceeds 1 minutes

HOST.X1.6: Check that the Filer and AD use the same NTP service. If problem still persists, please contact Panzura Technical Support.

5

HOST.X1.7

HOST.X1.7: Core or crash dumps have occurred

HOST.X1.7: Alert when there are any core or crash dumps

HOST.X1.7: If the event persists, contact Panzura Technical Support.

5

HOST.X1.9

HOST.X1.9: System experiencing high syslog message rate

HOST.X1.9: Alert when PZOS is experiencing high syslog rates

HOST.X1.9: Review syslogs for high rate loggers. When no specific culprit is found, check Debug level in WebUI.

5

HOST.L1.9

-OSE-HOST.L1.9: MCA memory error: $0

HOST.L1.9: Alert when kernel memory has errors

HOST.L1.9: This may be a hardware or a VM issue. If issue persists, contact Panzura Technical Support team immediately

5

HOST.L1.2

-OSE-HOST.L1.2: /mnt free space insufficient ($0MB)

-OSE-HOST.L1.2: root zpool free space insufficient ($0MB)

HOST.L1.2: Alert when the PZOS partition does not have enough space available for an upgrade

HOST.L1.2: This applies to /mnt and root / partition. Expand and reboot if possible, or rebuild and DR.

5

HOST.L1.3

-OSE-HOST.L1.3: System rebooted by $0

-OSE-HOST.L1.3: System powercycled or rebooted by $0

HOST.L1.3: Alert when the system has rebooted

HOST.L1.3: If this is an unexpected reboot, contact Panzura Technical Support.

3

FILE.L1.5

-OSE-FILE.L1.5: zfs free space insufficient ($1 bytes available)

FILE.L1.5: Alert when local disk space is running low.

FILE.L1.5: This occurs when there is too much local write traffic and data cannot be moved to the cloud fast enough. Check cloud write bandwidth or slow high rate clients.

6

SYS.WUI1.1

SYS.WUI1.1: *

SYS.WUI1.1: Alert when there are errors from cifsd, exportd, mountd, export_path, nanny

SYS.WUI1.1: Check configuration of shares and exports. If the event persists, contact Panzura Technical Support.

6

SYS.ICAP1.1

SYS.ICAP1.1: ICAP: Server %s options request failed

SYS.WUI1.1: Alert when there are errors from cifsd, exportd, mountd, export_path, nanny

SYS.ICAP1.1: Check ICAP server configuration. If the event persists, contact Panzura Technical Support.

2

SYS.ICAP1.2

SYS.ICAP1.2: ICAP: Quarantine {%s} [%d] %s

SYS.ICAP1.2: Alert when a file is quarantined via ICAP

SYS.ICAP1.2: Review logs on Anti-Virus Scanner for threat analysis.

8

SYS.ICAP1.3

SYS.ICAP1.3: ICAP: Server %s is down

SYS.ICAP1.3: Alert when a configured ICAP Server is down or unavailable

SYS.ICAP1.3: Checks to make sure that each ICAP Server is functional and able to be used. Investigate ICAP server for signs of issues. If the ICAP server is working well and the issue persists, contact Panzura Technical Support.