CBRE: Object Receive End
-
PDF of this doc site
- Install and upgrade software
-
Install and maintain hardware
- SG5700 storage appliances
- SG5600 storage appliances
-
Configure and manage
- Administer StorageGRID
- Use StorageGRID
-
Monitor and troubleshoot
- Monitor a StorageGRID system
Collection of separate PDF docs
Creating your file...
When transfer of a content block from one node to another is completed, this message is issued by the destination entity.
Code | Field | Description |
---|---|---|
CNID |
Connection Identifier |
The unique identifier of the node-to-node session/connection. |
CBID |
Content Block Identifier |
The unique identifier of the content block being transferred. |
CTDR |
Transfer Direction |
Indicates if the CBID transfer was push-initiated or pull-initiated: PUSH: The transfer operation was requested by the sending entity. PULL: The transfer operation was requested by the receiving entity. |
CTSR |
Source Entity |
The node ID of the source (sender) of the CBID transfer. |
CTDS |
Destination Entity |
The node ID of the destination (receiver) of the CBID transfer. |
CTSS |
Start Sequence Count |
Indicates the sequence count on which the transfer started. |
CTAS |
Actual End Sequence Count |
Indicates the last sequence count successfully transferred. If the Actual End Sequence Count is the same as the Start Sequence Count, and the Transfer Result was not successful, no data was exchanged. |
RSLT |
Transfer Result |
The result of the transfer operation (from the perspective of the sending entity): SUCS: transfer successfully completed; all requested sequence counts were sent. CONL: connection lost during transfer CTMO: connection timed-out during establishment or transfer UNRE: destination node ID unreachable CRPT: transfer ended due to reception of corrupt or invalid data (might indicate tampering) |
This audit message means a node-to-node data transfer operation was completed. If the Transfer Result was successful, the operation transferred data from "Start Sequence Count" to "Actual End Sequence Count". Sending and receiving nodes are identified by their node IDs. This information can be used to track system data flow and to locate, tabulate, and analyze errors. When combined with storage audit messages, it can also be used to verify replica counts.