![background image](http://html1.mh-extra.com/html/d-link/netdefend-dfl-260e/netdefend-dfl-260e_log-reference-manual_3185262466.webp)
2.38. LACP
These log messages refer to the LACP (Link Aggregation Control Protocol) category.
2.38.1. lacp_up (ID: 07700001)
Default Severity
Log Message
Negotiation was successful and <physiface> was added to the
<laiface> aggregation.
Explanation
LACP has successfully negotiated with a partner system and the
specified Member interface is now fully operational. This event is
generated independently for each Member interface.
Gateway Action
include_link
Recommended Action
None.
Revision
1
Parameters
physiface
laiface
2.38.2. lacp_expired (ID: 07700002)
Default Severity
Log Message
The partner system on <physiface> has timed out due to no
message being received in <timeout> seconds.
Explanation
LACP has not received a periodic message from the established
partner system in some time and the link has been excluded from
the aggregation.
Gateway Action
exclude_link
Recommended Action
If this occurs frequently, look for an unstable link or partner system.
Revision
1
Parameters
physiface
laiface
timeout
2.38.3. lacp_down (ID: 07700003)
Default Severity
Log Message
No response has been received on <physiface>. The link will not be
used in the <laiface> aggregation.
Explanation
No LACP message has been received on the link.
Chapter 2: Log Message Reference
466
Summary of Contents for NetDefend DFL-260E
Page 32: ...List of Tables 1 Abbreviations 35 32...
Page 33: ...List of Examples 1 Log Message Parameters 34 2 Conditional Log Message Parameters 34 33...
Page 42: ...routemetric Route metric cost Chapter 1 Introduction 42...
Page 44: ...Chapter 1 Introduction 44...
Page 216: ...Rule Information Connection Chapter 2 Log Message Reference 216...
Page 243: ...client_ip Context Parameters Rule Name Packet Buffer Chapter 2 Log Message Reference 243...
Page 556: ...logger Chapter 2 Log Message Reference 556...
Page 613: ...Parameters location Chapter 2 Log Message Reference 613...