Hello @pgutierreziii
The main goal here is to ensure that the new interface seamlessly integrates into the port-channel while maintaining consistent settings on both ends of the link...
The first step is to verify the current configuration of the port-channel and its member interfaces. This includes checking the port-channel configuration and the individual interfaces already part of the group. Using commands like show etherchannel summary and show running-config ensures that the existing setup is well-understood and that the new interface will match the required settings.
When configuring the new member interface, it’s essential to ensure that its attributes, such as speed, duplex, and switchport mode, align with those of the existing port-channel. The new interface should be shut down during configuration to prevent any misalignment or traffic issues. The channel-group command is then used to assign the interface to the correct port-channel in the desired mode (e.g., `active` for LACP). Once this configuration is applied, the same steps must be mirrored on the corresponding interface at the other end of the link.
After configuration, the interfaces on both switches are brought back online using the no shutdown command. It is important to monitor the status of the port-channel to confirm that the new member has been successfully added. Command such as show etherchannel summary provide insights into whether the interface is active and correctly bundled within the port-channel.
Finally, it’s important to validate traffic flow and check for errors or mismatches. Using show interfaces on the new member interfaces helps ensure that there are no unexpected drops or errors. If everything is configured correctly and LACP negotiation is successful, the new interface will seamlessly join the port-channel, providing additional bandwidth and redundancy as you looking for...
Best regards
.ı|ı.ı|ı. If This Helps, Please Rate .ı|ı.ı|ı.
