Fix(eos_designs)!: Endpoints PoE and 802.1x configuration for port-ch…

…annel members (#4627)

Co-authored-by: Shivani-gslab <[email protected]>

ansible_collections/arista/avd/docs/porting-guides/5.x.x.md

@@ -401,6 +401,44 @@ It is possible to forcefully add or remove BGP configuration per VRF by setting:
           enabled: <bool>  # <-- New optional setting to either always or never configure BGP for the VRF
 ```
 
+### Connected endpoints and network ports now renders PoE and 802.1x configuration for port-channel members and ignores PoE and 802.1x from LACP fallback individual profile
+
+With AVD version 5.0.0, port-channel members generated from connected endpoints or `network_ports` will now include 802.1x (`dot1x`) and PoE (`poe`) configuration.
+Previously, the member interface configuration only included `dot1x` or `poe` if it was defined under the port profile set in `lacp_fallback.individual.profile`.
+The LACP fallback individual profiles now ignores any `dot1x` or `poe` settings.
+
+It may be required to move the `dot1x` and `poe` settings from the fallback profile to the adapter profile:
+
+```diff
+ port_profiles:
+   - name: MY_LACP_INDIVIDUAL_FALLBACK_PROFILE
+     <...>
+-    poe:
+-      <...>
+-    dot1x:
+-      <...>
+   - name: MY_SERVER_PROFILE
+     <...>
++    poe:
++      <...>
++    dot1x:
++      <...>
+
+servers:
+  - name: MYSERVER1
+    adapters:
+      - <...>
+        profile: MY_SERVER_PROFILE
+        port_channel:
+          <...>
+          lacp_fallback:
+            mode: individual
+            individual:
+              profile: MY_LACP_INDIVIDUAL_FALLBACK_PROFILE
+```
+
+No changes are needed if the LACP fallback individual profile is the same as the adapter profile.
+
 ### Default interface descriptions are changed for more consistency
 
 With AVD version 5.0.0, the default interface descriptions have been changed to improve consistency. The detailed changes are described in the subsections below.