Event Details - CloudFS Category View

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


Severity Level

Policy ID






CLOUDFS.X1.1: Active remote filesystem without a CCID

CLOUDFS.X1.1: Alert when the active filesystems are missing a CCID GUID

CLOUDFS.X1.1: Check that all nodes in the CloudFS show as UP from the dashboard section on the GUI



CLOUDFS.X1.2: System is generating Master Snapshot

CLOUDFS.X1.2: Alert when a Master Snapshot is being generated

CLOUDFS.X1.2:Check for Normal Operations



CLOUDFS.X1.3: System is ${RESULTS} snapshots behind on upload

CLOUDFS.X1.3: Alert when dirty data is over threshold snapshots behind (30 minutes)

CLOUDFS.X1.3: Data upload to the cloud is falling behind or there may be a heavy load of data ingest. If there is a momentary heavy ingest of data that is higher than cloud upload capabilities, this may be as expected. This can be compared in the dashboard. If user workload lowers and node does not catch up, contact Panzura Technical Support



CLOUDFS.X1.4: System is ${RESULTS} snapshots behind on download

CLOUDFS.X1.4: Alert when remote system sync for some peer file systems is more than threshold snap shots behind

CLOUDFS.X1.4: Check Dashboard if problem persists, contact Panzura Technical Support



CLOUDFS.X1.5: Excessive site-to-site service latency with $0, $1ms more than ${CLOUDFS.X1.5_site2siteLatency}ms

CLOUDFS.X1.5: Alert when cross-site collaboration within applications, and cross-site file operations are slow

CLOUDFS.X1.5: This event may occur if the lock management and file open times are longer than usual due to the excess latency. Check ping times and link congestion to/from the site reporting the problem from the Diagnostic Tools and have the network team investigate the link.



CLOUDFS.X1.6: Master Snapshot has not been generated in more than twice the scheduled interval

CLOUDFS.X1.6: Alert when a node fails to update the master snapshot on schedule

CLOUDFS.X1.6: A validation failure or new peer syncing this filesystem may be preventing master snapshot generation. Check all peers are in sync with this filesystem, then attempt to run master snapshot from maintenance page, after hours. If it still fails, contact Panzura Technical Support



CLOUDFS.X1.8: Cloud mirrors are out of sync

CLOUDFS.X1.8: Alert when Cloud mirrors are out of sync

CLOUDFS.X1.8: Check the Cloud Mirror Status from the WebUI. Wait for sometime, if this problem persists, please check your network connection and contact Panzura Technical Support



CLOUDFS.X1.9: Delete Queue Depth

CLOUDFS.X1.9: Alert when there is 250GB or more cloud data pending deleted

CLOUDFS.X1.9: Cloud deletes for obsolete objects are taking too long. Check cloud connectivity. Upgrade to the latest PZOS version (minimum PZOS version - 8.0)



CLOUDFS.X1.10: New Cloud Mirror is fully synchronized

CLOUDFS.X1.10: Alert when cloud mirror is fully synchronised for the first time

CLOUDFS.X1.10: Check the Cloud Mirror Status from the WebUI. If synchronization rate is significantly slower than expected, please check your network connection and contact Panzura Technical Support



CLOUDFS.X1.11: Peer node Sync issue encountered

CLOUDFS.X1.11: Alert when node cannot reach all peers in the same CloudFS

CLOUDFS.X1.11: Some nodes are unable to reach peer nodes over port 22. In the WebUI go to Maintenance - Diagnostic Tools. For Command Type, select ping. For Parameter, enter the name/IP of a peer node that is showing issues and press Run. Also from Diagnostic tools, enter the name/IP of the peer node and port 22. Check with network team to ensure port 22 is open between the nodes



CLOUDFS.X1.12: Cloud download synchronization is not progressing

CLOUDFS.X1.12: Alert when cloud download sync processes are stuck for more than 15 minutes

CLOUDFS.X1.12: Some snapshot receive processes are taking too long to complete. If the problem persists, verify whether the cloud connectivity is good, if not, contact Panzura Technical Support for further diagnosis



CLOUDFS.X1.13: Snapshots are being retained too long

CLOUDFS.X1.13: Alert when user snapshots are being retained past their limits in the user snapshot schedule

CLOUDFS.X1.13: Expired snapshots may be getting retained for too long. Check snapshot manager under configuration for old snapshots which can be deleted. If snapshots older than the schedule are not visible, and the issue persists, contact Panzura Technical Support



CLOUDFS.X1.14: Found orphaned file systems

CLOUDFS.X1.14: Alert when there are orphaned file systems that were not deleted after decommission

CLOUDFS.X1.14: Decommissioned filesystems are no longer deleted in order to retain access to their snapshots. However, they should be declared by a decommission-cc command in the configuration. This alert indicates there may be an incorrect configuration for a previously decommissioned node. Contact Panzura Technical Support



FS.RL1.1: Active CC %s is unresponsive

FS.RL1.1: Alert when not all active CCs are connected

FS.RL1.14: Contact Panzura Technical Support in case this event occurs



SYS.WUI1.3: Domain Name conflicts with CloudFS CloudController list.

SYS.WUI1.3: Alert when a domain name conflicts in the CloudFS CloudController list

SYS.WUI1.3: Check all node domain names against the configured node list



CLOUDFS.X1.15: System has finished generating Master Snapshot

CLOUDFS.X1.15: Alert when a Master Snapshot is finished generated

CLOUDFS.X1.15:Check for Normal Operations