Message: <error message>.
Message Type: LOG
Severity: ERROR
Probable Cause: Indicates a configuration error.
Recommended Action: Make sure to input or pass the right parameter through the CLI or other daemon.
Message: <message>.
Message Type: LOG
Severity: INFO
Probable Cause: Indicates a Border Gateway Protocol (BGP) interface state change or external link-state database (LSDB) overflow notification.
Recommended Action: No action is required.
Message: <error message>.
Message Type: LOG
Severity: ERROR
Probable Cause: Indicates that the length, format, or content of the received packet is incorrect.
Recommended Action:Check the configuration at the local or remote node.
Message: <message>.
Message Type: LOG
Severity: WARNING
Probable Cause: Indicates a Border Gateway Protocol (BGP) interface state change or external link-state database (LSDB) overflow warning.
Recommended Action:No action is required.
Message: <message>.
Message Type: LOG
Severity: INFO
Probable Cause: Indicates a Border Gateway Protocol (BGP) Peer Session state UP.
Recommended Action:No action is required.
Message: <message>.
Message Type: LOG
Severity: INFO
Probable Cause: Indicates a Border Gateway Protocol (BGP) Peer Session state DOWN.
Recommended Action:No action is required.
Message: <message>.
Message Type: LOG
Severity: CRITICAL
Probable Cause: Indicates a Border Gateway Protocol (BGP). Process restarted Cold.
Recommended Action:No action is required.
Message: <message>.
Message Type: LOG
Severity: WARNING
Probable Cause: Indicates the current memory usage.
Recommended Action:No action is required.
Message: <message>.
Message Type: LOG
Severity: WARNING
Probable Cause: Indicates routes dampened due to frequent moves.
Recommended Action:No action is required.
Message: <message>.
Message Type: LOG
Severity: WARNING
Probable Cause: Indicates no. of prefixes received from a peer have reached max/warning limit.
Recommended Action:No action is required.
Message: <message>.
Message Type: LOG
Severity: WARNING
Probable Cause:Indicates flowspec route-map can't be advertised by BGP.
Recommended Action:No action is required.
Message: <message>.
Message Type: LOG
Severity: WARNING
Probable Cause:flowspec rule gets generated from dup rmap stanza when the original stanza is modified.
Recommended Action:No action is required.
Message: <message>.
Message Type: LOG
Severity: WARNING
Probable Cause:flowspec rule is not generated from duplicate rmap stanza.
Recommended Action:No action is required.
Message: <message>.
Message Type: LOG
Severity: WARNING
Probable Cause:BGP ORF Prefix list send limit reached.
Recommended Action:No action is required.
Message: <message>.
Message Type: LOG
Severity: WARNING
Probable Cause:BGP ORF Prefix list send limit reached.
Recommended Action:No action is required.
Message: <message>.
Message Type: LOG
Severity: WARNING
Probable Cause:TCP flags match sub-component is more than a byte in the Flowspec rule.
Recommended Action:No action is required.
Message: <message>.
Message Type: LOG
Severity: WARNING
Probable Cause:Mac-address mismatch.
Recommended Action:No action is required.
Message: <message>.
Message Type: LOG
Severity: WARNING
Probable Cause:IP configured is not SAG.
Recommended Action:No action is required.
Message: <message>.
Message Type: LOG
Severity: WARNING
Probable Cause:Mismatch for virtual IPV6.
Recommended Action:No action is required.
Message: <message>.
Message Type: LOG
Severity: WARNING
Probable Cause:NLRI dropped.
Recommended Action:No action is required.