Cisco Cisco Firepower Management Center 4000

Page of 1844
 
6-36
FireSIGHT System User Guide
 
Chapter 6      Managing Devices 
  Clustering Devices
Contact Support if the messages sent increment at a similar rate to the total bytes received.
Bytes Sent
Bytes sent are the total number of bytes sent that make up the cluster synchronization messages sent 
to the peer. 
This data are useful in comparison to the number of messages received. During active use, the values 
may not match, but should be close. The number of bytes received on the peer should be close to, 
but not more than this value. 
Contact Support if the total bytes received is not incrementing at about the same rate as the bytes 
sent.
Tx Errors
Tx errors are the number of memory allocation failures the system encounters when trying to 
allocate space for messages to be sent to the clustered peer.
This value should be zero at all times on both peers. Contact Support if this number is not zero or if 
the number steadily increases, which indicates the system has encountered an error where it cannot 
allocate memory.
Tx Overruns
Tx overruns are the number of times the system attempts and fails to place a message into the transit 
queue.
This value should be zero at all times on both peers. When the value is not zero or is steadily 
increasing, it indicates that the system is sharing too much data across the HA link that cannot be 
sent quickly enough.
You should increase the HA link MTU if it was previously set below the default value (9918 or 
9922). You can change the minimum flow lifetime and minimum synchronization interval settings 
to reduce the amount of data shared across the HA link to prevent the number from incrementing.
Contact Support if this value persists or continues to increase.
Recent Logs
The system log displays the most recent clustered synchronization messages. The log should not 
display any ERROR or WARN messages. It should remain comparable between the peers, such as 
the same number of sockets being connected. 
However, the data displayed may be opposite in some instances, for example, one peer reports that 
it received a connection from the other peer and references different IP addresses. The log provides 
a comprehensive view of the clustered state sharing connection, and any errors within the 
connection. 
Contact Support if the log displays an ERROR or WARN message, or any message that does not 
appear to be purely informational.
To view clustered state sharing statistics:
Access: 
Admin/Network Admin
Step 1
Select 
Devices > Device Management
.
The Device Management page appears.
Step 2
Next to the device cluster you want to edit, click the edit icon (
).