Below details mentioned are event details listed on a per Category basis.
|
Severity Level |
Policy ID |
Description |
Cause |
Resolution |
|
10 |
SYS.HA1.1 |
SYS.HA1.1: Active: Snapshots in dirty cache (%lu) exceeds max allowed (%d) |
SYS.HA1.1: Alert when dirty cache exceeds max allowed for HA takeover |
SYS.HA1.1: This event is informational for Panzura Technical Support. |
|
10 |
SYS.HA1.2 |
SYS.HA1.2: Standby: Snapshots received far behind generated snapshots |
SYS.HA1.2: Alert when snapshots received are too far behind generated for HA takeover |
SYS.HA1.2: This event is informational for Panzura Technical Support. |
|
10 |
SYS.HA1.3 |
SYS.HA1.3: Peer-CC thinks he is Active. Changing our state to standby |
SYS.HA1.3: Alert when HA Peer-CC is Active and changing to Standby |
SYS.HA1.3: This event is informational for Panzura Technical Support. |
|
10 |
SYS.HA1.4 |
SYS.HA1.4: Peer-CC thinks he is Standby. Changing our state to Active |
SYS.HA1.4: Alert when the HA standby Filer is now the active Filer and a takeover has occurred |
SYS.HA1.4: If this was an unexpected takeover, contact Panzura Technical Support to review. |
|
10 |
SYS.HA1.5 |
SYS.HA1.5: Received autofo disabled message from the cloud |
SYS.HA1.5: Alert when HA Received auto failover disabled from cloud |
SYS.HA1.5: This event is informational for Panzura Technical Support. |
|
10 |
SYS.HA1.6 |
SYS.HA1.6: Active: State Change request from Standby is Rejected Dirty Cache |
SYS.HA1.6: Alert when HA Active received state change and is rejecting |
SYS.HA1.6: If this event persists, check if HA received auto failover is disabled from the cloud and contact Panzura Technical Support. |
|
10 |
SYS.HA1.7 |
SYS.HA1.7: Received a State change trigger flag |
SYS.HA1.7: Alert when HA Received State change trigger flag |
SYS.HA1.7: This event is informational for Panzura Technical Support. |
|
8 |
SYS.HA1.8 |
SYS.HA1.8: Takeover is not Feasible %s |
SYS.HA1.8: Alert when the HA auto failover takeover ability on the Active HA failover is not feasible |
SYS.HA1.8: Active HA Filer may not be able to perform a takeover. If this event persists, check if Active HA received auto failover is disabled from the cloud and contact Panzura Technical Support. |
|
8 |
SYS.HA1.9 |
SYS.HA1.9: Active Triggering a State change : %s |
SYS.HA1.9: Alert when HA Active triggering a state change |
SYS.HA1.9: The active Filer will change its state to standby and stop cloud sync when the health status is displaying an error for 20 min or more than 160 errors. If the state change is unable to occur or the active Filer sync does not stop, contact Panzura Technical Support. |
|
8 |
SYS.HA1.10 |
SYS.HA1.10: Disabled Cloud and Sync for Active. If Takeover Not Feasible Reboot Required To Recover |
SYS.HA1.10: Alert when HA Active disabled cloud and sync |
SYS.HA1.10: This event is informational for Panzura Technical Support. |
|
10 |
SYS.HA1.11 |
SYS.HA1.11: Active: Changing state to Standby |
SYS.HA1.11: Alert when HA Active changing to Standby |
SYS.HA1.11: This event is informational for Panzura Technical Support. |
|
10 |
SYS.HA1.12 |
SYS.HA1.12: Cannot download the cloud state file |
SYS.HA1.12: Alert when HA Cloud heart-beat download fails |
SYS.HA1.12: Check network and cloud service availability to see why standby cannot download hastate-ccid-file. If the problem persists, contact Panzura Technical Support. |
|
8 |
SYS.HA1.13 |
SYS.HA1.13: Takeover is not Feasible: %s |
SYS.HA1.13: Alert when the HA auto failover takeover ability on the HA failover is not feasible due to {cloud,FS,HA-Monitor} |
SYS.HA1.13: HA Filer may not be able to perform a takeover. If this event persists, check if HA received auto failover is disabled from the cloud and contact Panzura Technical Support. |
|
10 |
SYS.HA1.14 |
SYS.HA1.14: Takeover is not Feasible %s |
SYS.HA1.14: Alert when the HA auto failover takeover ability on the Standby HA failover is not feasible |
SYS.HA1.14: Standby HA Filer may not be able to perform a takeover. If this event persists, check if Standby HA received auto failover is disabled from the cloud and contact Panzura Technical Support. |
|
8 |
SYS.HA1.15 |
SYS.HA1.15: Takeover is not Feasible: %s |
SYS.HA1.15: Alert when the HA auto failover takeover ability on the Standby HA failover is not feasible |
SYS.HA1.15: Standby HA Filer may not be able to perform a takeover. If this event persists, check if Standby HA received auto failover is disabled from the cloud and contact Panzura Technical Support. |
|
10 |
SYS.HA1.16 |
SYS.HA1.16: Exceeded the Peer reboot wait time.. Triggering a takeover |
SYS.HA1.16: Alert when the HA Filer peer reboot time exceeds the trigger takeover time |
SYS.HA1.16: The standby Filer will start a takeover because the reboot time of the Active Filer has exceeded 12 mins. |
|
10 |
SYS.HA1.17 |
SYS.HA1.17: Standby Initiating Takeover Action (%s) |
SYS.HA1.17: Alert when HA Standby initiating takeover |
SYS.HA1.17: This event is informational for Panzura Technical Support. |
|
10 |
SYS.HA1.18 |
SYS.HA1.18: Standby: Takeover Aborted, Standby not fully up |
SYS.HA1.18: Alert when HA takeover aborted, Standby not fully up |
SYS.HA1.18: This event is informational for Panzura Technical Support. |
|
10 |
SYS.HA1.19 |
SYS.HA1.19: Snapshot Sync process is still not fully up after role change-- Takeover is not feasible yet |
SYS.HA1.19: Alert when HA Snapshot sync is not ready and takeover is infeasible |
SYS.HA1.19: This event is informational for Panzura Technical Support. |
|
10 |
SYS.HA1.20 |
SYS.HA1.20: Starting the takeover process |
SYS.HA1.20: Alert when HA Standby is starting takeover process |
SYS.HA1.20: This event is informational for Panzura Technical Support. |
|
10 |
SYS.HA1.21 |
SYS.HA1.21: Takeover Process did not complete |
SYS.HA1.21: Alert when HA Standby takeover process did not complete |
SYS.HA1.21: This event is informational for Panzura Technical Support. |
|
5 |
SYS.X1.1 |
SYS.X1.1: Few vnodes, $0 available |
SYS.X1.1: Alert when system vnodes are not available |
SYS.X1.1: Checks vnode usage as reaching max will cause slow system performance. If the issue still persists, contact Panzura Technical Support. |
|
9 |
SYS.X1.2 |
SYS.X1.2: No more files can be opened, $0 used |
SYS.X1.2: Alert when system file handles are not available |
SYS.X1.2: Go to Maintenance - Diagnostic Tools - Command Type: show-log-tail and Log File: messages , search 'table is full' in output and contact Panzura Technical Support if this output is visible. |
|
8 |
SYS.X1.3 |
SYS.X1.3: No more sockets can be opened, $0 used |
SYS.X1.3: Alert when no system sockets are available |
SYS.X1.3: Check for network saturation and contact Panzura Technical Support. |
|
8 |
SYS.X1.4 |
SYS.X1.4: Memory limit $3 hit for z_memory $0 |
SYS.X1.4: Alert when a system memory pool has hit limits |
SYS.X1.4: Check memory pools as memory exhaustion may cause an impact to user experience. Contact Panzura Technical Support if this issue persists. |
|
9 |
SYS.X1.6 |
SYS.X1.6: 1GB or less memory available |
SYS.X1.6: Alert when under 1GB of system memory is free |
SYS.X1.6: Review Filer health in the WebUI. If this issue persists, contact Panzura Technical Support. |
|
5 |
SYS.X1.7 |
SYS.X1.7: High user connection load |
SYS.X1.7: Alert when the max user count [CIFS or NFS] exceeds the limit for the hardware configuration |
SYS.X1.7: Check local CPU, Memory, Network capacity. Increase capacity as needed. If this event occurs, contact Panzura Technical Support immediately. |
|
9 |
SYS.X1.8 |
SYS.X1.8: Filer is running in maintenance mode |
SYS.X1.8: Alert when PZOS is running in maintenance mode |
SYS.X1.8: If this event occurs, contact Panzura Technical Support immediately. |
|
6 |
SYS.X1.11 |
SYS.X1.11: PRC effectiveness is below 50 percent |
SYS.X1.11: Alert when the performance is degraded due to a small PRC relative to the working load |
SYS.X1.11: Check for new loads that might have increased cache requirements. For example: large uploads, large downloads or an increase in user count. If new loads are expected to remain, add PRC storage capacity. |
|
5 |
SYS.X1.12 |
SYS.X1.12: Local SMTP Service Configuration check with Filer |
SYS.X1.12: Alert when there is a failure with the configured SMTP service |
SYS.X1.12: Check that the SMTP configuration on the Filer matches the with SMTP service |
|
6 |
SYS.X1.13 |
SYS.X1.13: .startupscript_post is inconsistent |
SYS.X1.13: Alert when /mnt/.startupscript_post has errors |
SYS.X1.13: Either exec permissions on the /mnt/.startupscript_post file are incorrect or it has ddt-rewrite settings that are not consistent with peers. |
|
5 |
SYS.X1.14 |
SYS.X1.14: High swap usage |
SYS.X1.14: Alert when the swap usage exceeds 0 GBs |
SYS.X1.14: Filer may be using swap space due to available memory exhaustion. Go to the dashboard, create a new dashlet, and select the metrics swap_used and swap_total to view memory usage. |
|
7 |
SYS.X1.15 |
SYS.X1.15: Very High swap usage |
SYS.X1.15: Alert when the swap usage exceeds 2 GBs |
SYS.X1.15: Filer may be using swap space due to available memory exhaustion. Go to the dashboard, create a new dashlet, and select the metrics swap_used and swap_total to view memory usage. |
|
5 |
SYS.X1.18 |
SYS.X1.18: Filer Disk Storage Check |
SYS.X1.18: Alert when the Filer used local disk storage exceeds 65 percent |
SYS.X1.18: Go to the dashboard, review the Filer health to check the normal operations state and if the issue persists, contact Panzura Technical Support. |
|
9 |
SYS.X1.19 |
SYS.X1.19: Filer Disk Storage exhausted |
SYS.X1.19: Alert when the Filer used local disk storage exceeds 80 percent |
SYS.X1.19: Local storage is used for write buffering, PRC cache and meta-data. As it fills, PZOS will rate limit users and reduce user io capacity. Add local storage to the Filer to increase capacity. If this event persists, contact Panzura Technical Support. |
|
7 |
SYS.X1.20 |
SYS.X1.20: Metadata has spilled to slow media |
SYS.X1.20: Alert when Metadata has been written to a non SSD drive |
SYS.X1.20: User performance, cloud synchronization, and peer sync will all be affected. Add SSD capacity as soon as possible. If this event persists, contact Panzura Technical Support. |
|
10 |
SYS.TRP1.1 |
SYS.TRP1.1: Threshold trap: IP: %s \t Trap ID: %d \t Trap Name: %s \t current_alarm_value: %d \t threshold_value: %d |
SYS.TRP1.1: Verify system Threshold Traps - {pzCloudControllerHighCPUUsage, pzCloudControllerHighMemoryUsage, pzCloudControllerHighDiskUsage, pzCloudControllerHighCloudUsage, pzCloudControllerMetaDataUsage, pzSwapUsage} |
SYS.TRP1.1: Contact Technical Panzura Support |
|
10 |
SYS.TRP1.2 |
SYS.TRP1.2: Non-Threshold trap: IP: %s \t Trap ID: %d \t Trap Name: %s |
SYS.TRP1.2: Alert when metadata allocation fails - {pzTrapMetaAllocFail} |
SYS.TRP1.2: Adding disks will resolve a meta-data capacity shortage. If the event persists and user impact is observed, contact Panzura Technical Support. |
|
10 |
SYS.TRP1.3 |
SYS.TRP1.3: Non-Threshold trap: IP: %s \t Trap ID: %d \t Trap Name: %s |
SYS.TRP1.3: Alert when active Filer down - {pzTrapActiveDown} |
SYS.TRP1.3: In an HA configured pair, the secondary has noticed that the primary is inactive or unavailable. If HA autofailover is not engaged, the administrator must verify the primary Filer availability or trigger an HA failover from this secondary. |
|
9 |
SYS.TRP1.4 |
SYS.TRP1.4: Non-Threshold trap: Trap ID: %d \t Trap Name: %s \t desc: %s |
SYS.TRP1.4: Alert on system Non-Threshold Traps - {pzAutoFailover, pzRegularFailover, pzAlertTrap, pzCloudWriteFailureTrap, pzWarnTrap, pzInfoTrap} |
SYS.TRP1.4: This event is a general system information Event. It alerts when HA failover occurs, a cloud write failure occurs, etc. |
|
9 |
SYS.WUI1.2 |
SYS.WUI1.2: Metadata spilled over to HDD devices |
SYS.WUI1.2: Alert when metadata spills over to HDD devices. |
SYS.WUI1.2: This occurs on hybrid (Flash and spinning disk) systems when meta-data overflows onto spinning disk from Flash. This will impact user performance. Additional meta-data Flash capacity should be added. If the event persists and user impact is observed, contact Panzura Technical Support. |