LACP/2/hwLacpPDUChange_active

Message

LACP/2/hwLacpPDUChange_active: The LACP member interface's status changed from selected to unselected due to the PDU change. (TrunkIndex=[TrunkIndex], PortIfIndex=[PortIfIndex], TrunkId=[TrunkId], TrunkName=[TrunkName], PortName=[PortName], OldPduInfo=[OldPduInfo], NewPduInfo=[NewPduInfo], ReasonCode=[ReasonString])

Description

The status of an Eth-Trunk's member interface changed from selected to unselected due to an LACPDU change.

Parameters

Parameter Name	Parameter Meaning
TrunkIndex	Index of an Eth-Trunk interface in static LACP mode
PortIfIndex	Index of a member interface of an Eth-Trunk interface in static LACP mode
TrunkId	ID of an Eth-Trunk interface in static LACP mode
TrunkName	Name of an Eth-Trunk interface in static LACP mode
PortName	Name of a member interface of an Eth-Trunk interface in static LACP mode
OldPduInfo	Original LACPDU
NewPduInfo	New LACPDU
ReasonString	Reason for the LACPDU change

Possible Causes

Cause 1: Partner system ID changed in the received PDU.
Cause 2: Partner system priority changed in the received PDU.
Cause 3: Partner key changed in the received PDU.
Cause 4: Partner port number changed in the received PDU.
Cause 5: Partner port priority changed in the received PDU.
Cause 6: Partner state's aggregation bit changed in the received PDU.
Cause 7: Actor system ID changed in the received PDU.
Cause 8: Actor system priority changed in the received PDU.
Cause 9: Actor key changed in the received PDU.
Cause 10: Actor port priority changed in the received PDU.
Cause 11: Actor port number changed in the received PDU.
Cause 12: Actor state's aggregation bit changed in the received PDU.
Cause 13: Actor state's synchronization bit changed in the received PDU.
Cause 14: Actor aggregation delay changed in the received PDU.

Procedure

Cause 1: Partner system ID changed in the received PDU.
1. Run the display interface brief command to check whether the member interface is Down.
- If the member interface is Down, go to Step 2.
- If the member interface is not Down, go to Step 5.
2. Run the undo shutdown command to activate the interface. Then, check whether the alarm is cleared. If the alarm persists, go to Step 3.

3. Check whether the physical connection of the interface is proper (for example, whether the network cable is properly connected and optical module is properly inserted).
- If the physical connection is proper, go to Step 5.
- If the physical connection is improper, go to Step 4.
4. Repair the physical link and check whether the alarm is cleared. If the alarm persists, go to Step 5.

5. Run the display eth-trunk [ trunk-id [ interface interface-type interface-number | verbose ] ] command to check whether the Eth-Trunk interface has member interfaces.
- If the Eth-Trunk interface has member interfaces, go to Step 7.
- If the Eth-Trunk interface does not have member interfaces, go to Step 6.
6. Run the eth-trunk trunk-id command in an Ethernet interface view to add the interface to the Eth-Trunk interface and check whether the alarm is cleared. If the alarm persists, go to Step 7.

7. Run the display trunkmembership eth-trunk trunk-id command to check whether the minimum number of member links in the Up state is configured and causes the negotiation failure of the Eth-Trunk member interfaces.
- If the minimum number of member links in the Up state is configured, go to Step 8.
- If the minimum number of member links in the Up state is not configured, go to Step 9.
8. Run the least active-linknumber link-number command in the Eth-Trunk interface view to modify the minimum number to a proper value. Then, check whether the alarm is cleared. If the alarm persists, go to Step 9.

9. Collect alarm information and configuration information, and then contact technical support personnel.
Cause 2: Partner system priority changed in the received PDU.
1. Run the display interface brief command to check whether the member interface is Down.
- If the member interface is Down, go to Step 2.
- If the member interface is not Down, go to Step 5.
2. Run the undo shutdown command to activate the interface. Then, check whether the alarm is cleared. If the alarm persists, go to Step 3.

3. Check whether the physical connection of the interface is proper (for example, whether the network cable is properly connected and optical module is properly inserted).
- If the physical connection is proper, go to Step 5.
- If the physical connection is improper, go to Step 4.
4. Repair the physical link and check whether the alarm is cleared. If the alarm persists, go to Step 5.

5. Run the display eth-trunk [ trunk-id [ interface interface-type interface-number | verbose ]] command to check whether the Eth-Trunk interface has member interfaces.
- If the Eth-Trunk interface has member interfaces, go to Step 7.
- If the Eth-Trunk interface does not have member interfaces, go to Step 6.
6. Run the eth-trunk trunk-id command in an Ethernet interface view to add the interface to the Eth-Trunk interface and check whether the alarm is cleared. If the alarm persists, go to Step 7.

7. Run the display trunkmembership eth-trunk trunk-id command to check whether the minimum number of member links in the Up state is configured and causes the negotiation failure of the Eth-Trunk member interfaces.
- If the minimum number of member links in the Up state is configured, go to Step 8.
- If the minimum number of member links in the Up state is not configured, go to Step 9.
8. Run the least active-linknumber link-number command in the Eth-Trunk interface view to modify the minimum number to a proper value. Then, check whether the alarm is cleared. If the alarm persists, go to Step 9.

9. Collect alarm information and configuration information, and then contact technical support personnel.
Cause 3: Partner key changed in the received PDU.
1. Run the display interface brief command to check whether the member interface is Down.
- If the member interface is Down, go to Step 2.
- If the member interface is not Down, go to Step 5.
2. Run the undo shutdown command to activate the interface. Then, check whether the alarm is cleared. If the alarm persists, go to Step 3.

3. Check whether the physical connection of the interface is proper (for example, whether the network cable is properly connected and optical module is properly inserted).
- If the physical connection is proper, go to Step 5.
- If the physical connection is improper, go to Step 4.
4. Repair the physical link and check whether the alarm is cleared. If the alarm persists, go to Step 5.

5. Run the display eth-trunk [ trunk-id [ interface interface-type interface-number | verbose ] ] command to check whether the Eth-Trunk interface has member interfaces.
- If the Eth-Trunk interface has member interfaces, go to Step 7.
- If the Eth-Trunk interface does not have member interfaces, go to Step 6.
6. Run the eth-trunk trunk-id command in an Ethernet interface view to add the interface to the Eth-Trunk interface and check whether the alarm is cleared. If the alarm persists, go to Step 7.

7. Run the display trunkmembership eth-trunk trunk-id command to check whether the minimum number of member links in the Up state is configured and causes the negotiation failure of the Eth-Trunk member interfaces.
- If the minimum number of member links in the Up state is configured, go to Step 8.
- If the minimum number of member links in the Up state is not configured, go to Step 9.
8. Run the least active-linknumber link-number command in the Eth-Trunk interface view to modify the minimum number to a proper value. Then, check whether the alarm is cleared. If the alarm persists, go to Step 9.

9. Collect alarm information and configuration information, and then contact technical support personnel.
Cause 4: Partner port number changed in the received PDU.
1. Run the display interface brief command to check whether the member interface is Down.
- If the member interface is Down, go to Step 2.
- If the member interface is not Down, go to Step 5.
2. Run the undo shutdown command to activate the interface. Then, check whether the alarm is cleared. If the alarm persists, go to Step 3.

3. Check whether the physical connection of the interface is proper (for example, whether the network cable is properly connected and optical module is properly inserted).
- If the physical connection is proper, go to Step 5.
- If the physical connection is improper, go to Step 4.
4. Repair the physical link and check whether the alarm is cleared. If the alarm persists, go to Step 5.

5. Run the display eth-trunk [ trunk-id [ interface interface-type interface-number | verbose ] ] command to check whether the Eth-Trunk interface has member interfaces.
- If the Eth-Trunk interface has member interfaces, go to Step 7.
- If the Eth-Trunk interface does not have member interfaces, go to Step 6.
6. Run the eth-trunk trunk-id command in an Ethernet interface view to add the interface to the Eth-Trunk interface and check whether the alarm is cleared. If the alarm persists, go to Step 7.

7. Run the display trunkmembership eth-trunk trunk-id command to check whether the minimum number of member links in the Up state is configured and causes the negotiation failure of the Eth-Trunk member interfaces.
- If the minimum number of member links in the Up state is configured, go to Step 8.
- If the minimum number of member links in the Up state is not configured, go to Step 9.
8. Run the least active-linknumber link-number command in the Eth-Trunk interface view to modify the minimum number to a proper value. Then, check whether the alarm is cleared. If the alarm persists, go to Step 9.

9. Collect alarm information and configuration information, and then contact technical support personnel.
Cause 5: Partner port priority changed in the received PDU.
1. Run the display interface brief command to check whether the member interface is Down.
- If the member interface is Down, go to Step 2.
- If the member interface is not Down, go to Step 5.
2. Run the undo shutdown command to activate the interface. Then, check whether the alarm is cleared. If the alarm persists, go to Step 3.

3. Check whether the physical connection of the interface is proper (for example, whether the network cable is properly connected and optical module is properly inserted).
- If the physical connection is proper, go to Step 5.
- If the physical connection is improper, go to Step 4.
4. Repair the physical link and check whether the alarm is cleared. If the alarm persists, go to Step 5.

5. Run the display eth-trunk [ trunk-id [ interface interface-type interface-number | verbose ] ] command to check whether the Eth-Trunk interface has member interfaces.
- If the Eth-Trunk interface has member interfaces, go to Step 7.
- If the Eth-Trunk interface does not have member interfaces, go to Step 6.
6. Run the eth-trunk trunk-id command in an Ethernet interface view to add the interface to the Eth-Trunk interface and check whether the alarm is cleared. If the alarm persists, go to Step 7.

7. Run the display trunkmembership eth-trunk trunk-id command to check whether the minimum number of member links in the Up state is configured and causes the negotiation failure of the Eth-Trunk member interfaces.
- If the minimum number of member links in the Up state is configured, go to Step 8.
- If the minimum number of member links in the Up state is not configured, go to Step 9.
8. Run the least active-linknumber link-number command in the Eth-Trunk interface view to modify the minimum number to a proper value. Then, check whether the alarm is cleared. If the alarm persists, go to Step 9.

9. Collect alarm information and configuration information, and then contact technical support personnel.
Cause 6: Partner state's aggregation bit changed in the received PDU.
1. Run the display interface brief command to check whether the member interface is Down.
- If the member interface is Down, go to Step 2.
- If the member interface is not Down, go to Step 5.
2. Run the undo shutdown command to activate the interface. Then, check whether the alarm is cleared. If the alarm persists, go to Step 3.

3. Check whether the physical connection of the interface is proper (for example, whether the network cable is properly connected and optical module is properly inserted).
- If the physical connection is proper, go to Step 5.
- If the physical connection is improper, go to Step 4.
4. Repair the physical link and check whether the alarm is cleared. If the alarm persists, go to Step 5.

5. Run the display eth-trunk [ trunk-id [ interface interface-type interface-number | verbose ] ] command to check whether the Eth-Trunk interface has member interfaces.
- If the Eth-Trunk interface has member interfaces, go to Step 7.
- If the Eth-Trunk interface does not have member interfaces, go to Step 6.
6. Run the eth-trunk trunk-id command in an Ethernet interface view to add the interface to the Eth-Trunk interface and check whether the alarm is cleared. If the alarm persists, go to Step 7.

7. Run the display trunkmembership eth-trunk trunk-id command to check whether the minimum number of member links in the Up state is configured and causes the negotiation failure of the Eth-Trunk member interfaces.
- If the minimum number of member links in the Up state is configured, go to Step 8.
- If the minimum number of member links in the Up state is not configured, go to Step 9.
8. Run the least active-linknumber link-number command in the Eth-Trunk interface view to modify the minimum number to a proper value. Then, check whether the alarm is cleared. If the alarm persists, go to Step 9.

9. Collect alarm information and configuration information, and then contact technical support personnel.
Cause 7: Actor system ID changed in the received PDU.
1. Run the display interface brief command to check whether the member interface is Down.
- If the member interface is Down, go to Step 2.
- If the member interface is not Down, go to Step 5.
2. Run the undo shutdown command to activate the interface. Then, check whether the alarm is cleared. If the alarm persists, go to Step 3.

3. Check whether the physical connection of the interface is proper (for example, whether the network cable is properly connected and optical module is properly inserted).
- If the physical connection is proper, go to Step 5.
- If the physical connection is improper, go to Step 4.
4. Repair the physical link and check whether the alarm is cleared. If the alarm persists, go to Step 5.

5. Run the display eth-trunk [ trunk-id [ interface interface-type interface-number | verbose ] ] command to check whether the Eth-Trunk interface has member interfaces.
- If the Eth-Trunk interface has member interfaces, go to Step 7.
- If the Eth-Trunk interface does not have member interfaces, go to Step 6.
6. Run the eth-trunk trunk-id command in an Ethernet interface view to add the interface to the Eth-Trunk interface and check whether the alarm is cleared. If the alarm persists, go to Step 7.

7. Run the display trunkmembership eth-trunk trunk-id command to check whether the minimum number of member links in the Up state is configured and causes the negotiation failure of the Eth-Trunk member interfaces.
- If the minimum number of member links in the Up state is configured, go to Step 8.
- If the minimum number of member links in the Up state is not configured, go to Step 9.
8. Run the least active-linknumber link-number command in the Eth-Trunk interface view to modify the minimum number to a proper value. Then, check whether the alarm is cleared. If the alarm persists, go to Step 9.

9. Collect alarm information and configuration information, and then contact technical support personnel.
Cause 8: Actor system priority changed in the received PDU.
1. Run the display interface brief command to check whether the member interface is Down.
- If the member interface is Down, go to Step 2.
- If the member interface is not Down, go to Step 5.
2. Run the undo shutdown command to activate the interface. Then, check whether the alarm is cleared. If the alarm persists, go to Step 3.

3. Check whether the physical connection of the interface is proper (for example, whether the network cable is properly connected and optical module is properly inserted).
- If the physical connection is proper, go to Step 5.
- If the physical connection is improper, go to Step 4.
4. Repair the physical link and check whether the alarm is cleared. If the alarm persists, go to Step 5.

5. Run the display eth-trunk [ trunk-id [ interface interface-type interface-number | verbose ]] command to check whether the Eth-Trunk interface has member interfaces.
- If the Eth-Trunk interface has member interfaces, go to Step 7.
- If the Eth-Trunk interface does not have member interfaces, go to Step 6.
6. Run the eth-trunk trunk-id command in an Ethernet interface view to add the interface to the Eth-Trunk interface and check whether the alarm is cleared. If the alarm persists, go to Step 7.

7. Run the display trunkmembership eth-trunk trunk-id command to check whether the minimum number of member links in the Up state is configured and causes the negotiation failure of the Eth-Trunk member interfaces.
- If the minimum number of member links in the Up state is configured, go to Step 8.
- If the minimum number of member links in the Up state is not configured, go to Step 9.
8. Run the least active-linknumber link-number command in the Eth-Trunk interface view to modify the minimum number to a proper value. Then, check whether the alarm is cleared. If the alarm persists, go to Step 9.

9. Collect alarm information and configuration information, and then contact technical support personnel.
Cause 9: Actor key changed in the received PDU.
1. Run the display interface brief command to check whether the member interface is Down.
- If the member interface is Down, go to Step 2.
- If the member interface is not Down, go to Step 5.
2. Run the undo shutdown command to activate the interface. Then, check whether the alarm is cleared. If the alarm persists, go to Step 3.

3. Check whether the physical connection of the interface is proper (for example, whether the network cable is properly connected and optical module is properly inserted).
- If the physical connection is proper, go to Step 5.
- If the physical connection is improper, go to Step 4.
4. Repair the physical link and check whether the alarm is cleared. If the alarm persists, go to Step 5.

5. Run the display eth-trunk [ trunk-id [ interface interface-type interface-number | verbose ]] command to check whether the Eth-Trunk interface has member interfaces.
- If the Eth-Trunk interface has member interfaces, go to Step 7.
- If the Eth-Trunk interface does not have member interfaces, go to Step 6.
6. Run the eth-trunk trunk-id command in an Ethernet interface view to add the interface to the Eth-Trunk interface and check whether the alarm is cleared. If the alarm persists, go to Step 7.

7. Run the display trunkmembership eth-trunk trunk-id command to check whether the minimum number of member links in the Up state is configured and causes the negotiation failure of the Eth-Trunk member interfaces.
- If the minimum number of member links in the Up state is configured, go to Step 8.
- If the minimum number of member links in the Up state is not configured, go to Step 9.
8. Run the least active-linknumber link-number command in the Eth-Trunk interface view to modify the minimum number to a proper value. Then, check whether the alarm is cleared. If the alarm persists, go to Step 9.

9. Collect alarm information and configuration information, and then contact technical support personnel.
Cause 10: Actor port priority changed in the received PDU.
1. Run the display interface brief command to check whether the member interface is Down.
- If the member interface is Down, go to Step 2.
- If the member interface is not Down, go to Step 5.
2. Run the undo shutdown command to activate the interface. Then, check whether the alarm is cleared. If the alarm persists, go to Step 3.

3. Check whether the physical connection of the interface is proper (for example, whether the network cable is properly connected and optical module is properly inserted).
- If the physical connection is proper, go to Step 5.
- If the physical connection is improper, go to Step 4.
4. Repair the physical link and check whether the alarm is cleared. If the alarm persists, go to Step 5.

5. Run the display eth-trunk [ trunk-id [ interface interface-type interface-number | verbose ]] command to check whether the Eth-Trunk interface has member interfaces.
- If the Eth-Trunk interface has member interfaces, go to Step 7.
- If the Eth-Trunk interface does not have member interfaces, go to Step 6.
6. Run the eth-trunk trunk-id command in an Ethernet interface view to add the interface to the Eth-Trunk interface and check whether the alarm is cleared. If the alarm persists, go to Step 7.

7. Run the display trunkmembership eth-trunk trunk-id command to check whether the minimum number of member links in the Up state is configured and causes the negotiation failure of the Eth-Trunk member interfaces.
- If the minimum number of member links in the Up state is configured, go to Step 8.
- If the minimum number of member links in the Up state is not configured, go to Step 9.
8. Run the least active-linknumber link-number command in the Eth-Trunk interface view to modify the minimum number to a proper value. Then, check whether the alarm is cleared. If the alarm persists, go to Step 9.

9. Collect alarm information and configuration information, and then contact technical support personnel.
Cause 11: Actor port number changed in the received PDU.
1. Run the display interface brief command to check whether the member interface is Down.
- If the member interface is Down, go to Step 2.
- If the member interface is not Down, go to Step 5.
2. Run the undo shutdown command to activate the interface. Then, check whether the alarm is cleared. If the alarm persists, go to Step 3.

3. Check whether the physical connection of the interface is proper (for example, whether the network cable is properly connected and optical module is properly inserted).
- If the physical connection is proper, go to Step 5.
- If the physical connection is improper, go to Step 4.
4. Repair the physical link and check whether the alarm is cleared. If the alarm persists, go to Step 5.

5. Run the display eth-trunk [ trunk-id [ interface interface-type interface-number | verbose ]] command to check whether the Eth-Trunk interface has member interfaces.
- If the Eth-Trunk interface has member interfaces, go to Step 7.
- If the Eth-Trunk interface does not have member interfaces, go to Step 6.
6. Run the eth-trunk trunk-id command in an Ethernet interface view to add the interface to the Eth-Trunk interface and check whether the alarm is cleared. If the alarm persists, go to Step 7.

7. Run the display trunkmembership eth-trunk trunk-id command to check whether the minimum number of member links in the Up state is configured and causes the negotiation failure of the Eth-Trunk member interfaces.
- If the minimum number of member links in the Up state is configured, go to Step 8.
- If the minimum number of member links in the Up state is not configured, go to Step 9.
8. Run the least active-linknumber link-number command in the Eth-Trunk interface view to modify the minimum number to a proper value. Then, check whether the alarm is cleared. If the alarm persists, go to Step 9.

9. Collect alarm information and configuration information, and then contact technical support personnel.
Cause 12: Actor state's aggregation bit changed in the received PDU.
1. Run the display interface brief command to check whether the member interface is Down.
- If the member interface is Down, go to Step 2.
- If the member interface is not Down, go to Step 5.
2. Run the undo shutdown command to activate the interface. Then, check whether the alarm is cleared. If the alarm persists, go to Step 3.

3. Check whether the physical connection of the interface is proper (for example, whether the network cable is properly connected and optical module is properly inserted).
- If the physical connection is proper, go to Step 5.
- If the physical connection is improper, go to Step 4.
4. Repair the physical link and check whether the alarm is cleared. If the alarm persists, go to Step 5.

5. Run the display eth-trunk [ trunk-id [ interface interface-type interface-number | verbose ]] command to check whether the Eth-Trunk interface has member interfaces.
- If the Eth-Trunk interface has member interfaces, go to Step 7.
- If the Eth-Trunk interface does not have member interfaces, go to Step 6.
6. Run the eth-trunk trunk-id command in an Ethernet interface view to add the interface to the Eth-Trunk interface and check whether the alarm is cleared. If the alarm persists, go to Step 7.

7. Run the display trunkmembership eth-trunk trunk-id command to check whether the minimum number of member links in the Up state is configured and causes the negotiation failure of the Eth-Trunk member interfaces.
- If the minimum number of member links in the Up state is configured, go to Step 8.
- If the minimum number of member links in the Up state is not configured, go to Step 9.
8. Run the least active-linknumber link-number command in the Eth-Trunk interface view to modify the minimum number to a proper value. Then, check whether the alarm is cleared. If the alarm persists, go to Step 9.

9. Collect alarm information and configuration information, and then contact technical support personnel.
Cause 13: Actor state's synchronization bit changed in the received PDU.
1. Run the display interface brief command to check whether the member interface is Down.
- If the member interface is Down, go to Step 2.
- If the member interface is not Down, go to Step 5.
2. Run the undo shutdown command to activate the interface. Then, check whether the alarm is cleared. If the alarm persists, go to Step 3.

3. Check whether the physical connection of the interface is proper (for example, whether the network cable is properly connected and optical module is properly inserted).
- If the physical connection is proper, go to Step 5.
- If the physical connection is improper, go to Step 4.
4. Repair the physical link and check whether the alarm is cleared. If the alarm persists, go to Step 5.

5. Run the display eth-trunk [ trunk-id [ interface interface-type interface-number | verbose ]] command to check whether the Eth-Trunk interface has member interfaces.
- If the Eth-Trunk interface has member interfaces, go to Step 7.
- If the Eth-Trunk interface does not have member interfaces, go to Step 6.
6. Run the eth-trunk trunk-id command in an Ethernet interface view to add the interface to the Eth-Trunk interface and check whether the alarm is cleared. If the alarm persists, go to Step 7.

7. Run the display trunkmembership eth-trunk trunk-id command to check whether the minimum number of member links in the Up state is configured and causes the negotiation failure of the Eth-Trunk member interfaces.
- If the minimum number of member links in the Up state is configured, go to Step 8.
- If the minimum number of member links in the Up state is not configured, go to Step 9.
8. Run the least active-linknumber link-number command in the Eth-Trunk interface view to modify the minimum number to a proper value. Then, check whether the alarm is cleared. If the alarm persists, go to Step 9.

9. Collect alarm information and configuration information, and then contact technical support personnel.
Cause 14: Actor aggregation delay changed in the received PDU.
1. Run the display interface brief command to check whether the member interface is Down.
- If the member interface is Down, go to Step 2.
- If the member interface is not Down, go to Step 5.
2. Run the undo shutdown command to activate the interface. Then, check whether the alarm is cleared. If the alarm persists, go to Step 3.

3. Check whether the physical connection of the interface is proper (for example, whether the network cable is properly connected and optical module is properly inserted).
- If the physical connection is proper, go to Step 5.
- If the physical connection is improper, go to Step 4.
4. Repair the physical link and check whether the alarm is cleared. If the alarm persists, go to Step 5.

5. Run the display eth-trunk [ trunk-id [ interface interface-type interface-number | verbose ]] command to check whether the Eth-Trunk interface has member interfaces.
- If the Eth-Trunk interface has member interfaces, go to Step 7.
- If the Eth-Trunk interface does not have member interfaces, go to Step 6.
6. Run the eth-trunk trunk-id command in an Ethernet interface view to add the interface to the Eth-Trunk interface and check whether the alarm is cleared. If the alarm persists, go to Step 7.

7. Run the display trunkmembership eth-trunk trunk-id command to check whether the minimum number of member links in the Up state is configured and causes the negotiation failure of the Eth-Trunk member interfaces.
- If the minimum number of member links in the Up state is configured, go to Step 8.
- If the minimum number of member links in the Up state is not configured, go to Step 9.
8. Run the least active-linknumber link-number command in the Eth-Trunk interface view to modify the minimum number to a proper value. Then, check whether the alarm is cleared. If the alarm persists, go to Step 9.

9. Collect alarm information and configuration information, and then contact technical support personnel.