https://community.hpe.com/t5/operating-system-linux/inquiry-ineffective-port-level-configuration-changes-via-sysfs/m-p/7209170#M105310 <P>I'm currently engaged in configuring bond settings within the Linux kernel environment and encountering an issue regarding the modification of port-level values through the ad_user_port_key file in the SysFS interface. Despite attempting to alter these settings, I'm observing that the changes fail to reflect in the output log when inspecting via sudo cat /proc/net/bonding/bond0.</P><P>Could you please provide guidance on resolving this discrepancy? Your assistance in troubleshooting and rectifying this matter would be greatly appreciated.</P><P>Thank you for your attention to this issue.</P><P>Thanks, Akankshya</P><P>I tried "sudo ip link set bond0 type bond ad_user_port_key " this command to change the values in port level. But it is not reflecting .</P><P>Slave Interface: enp0s8 MII Status: up Speed: 1000 Mbps Duplex: full Link Failure Count: 0 Permanent HW addr: 08:00:27:76:e5:b8 Slave queue ID: 0 Aggregator ID: 1 Actor Churn State: monitoring Partner Churn State: monitoring Actor Churned Count: 0 Partner Churned Count: 0 details actor lacp pdu: system priority: 547 system mac address: 08:00:27:56:e7:b9 port key: 9 port priority: 255 port number: 2 port state: 61 details partner lacp pdu: system priority: 545 system mac address: 06:00:27:67:e5:85 oper key: 9 port priority: 255 port number: 2 port state: 63</P><P>Not only this value , any of the port level value changes are not reflecting in the output.</P><P>I tried to change it in SysFS file as well "/sys/class/net/bond0/bonding/". That change also not reflecting.</P> Tue, 19 Mar 2024 03:57:32 GMT AkankshyaDev 2024-03-19T03:57:32Z https://community.hpe.com/t5/operating-system-linux/inquiry-ineffective-port-level-configuration-changes-via-sysfs/m-p/7209170#M105310 <P>I'm currently engaged in configuring bond settings within the Linux kernel environment and encountering an issue regarding the modification of port-level values through the ad_user_port_key file in the SysFS interface. Despite attempting to alter these settings, I'm observing that the changes fail to reflect in the output log when inspecting via sudo cat /proc/net/bonding/bond0.</P><P>Could you please provide guidance on resolving this discrepancy? Your assistance in troubleshooting and rectifying this matter would be greatly appreciated.</P><P>Thank you for your attention to this issue.</P><P>Thanks, Akankshya</P><P>I tried "sudo ip link set bond0 type bond ad_user_port_key " this command to change the values in port level. But it is not reflecting .</P><P>Slave Interface: enp0s8 MII Status: up Speed: 1000 Mbps Duplex: full Link Failure Count: 0 Permanent HW addr: 08:00:27:76:e5:b8 Slave queue ID: 0 Aggregator ID: 1 Actor Churn State: monitoring Partner Churn State: monitoring Actor Churned Count: 0 Partner Churned Count: 0 details actor lacp pdu: system priority: 547 system mac address: 08:00:27:56:e7:b9 port key: 9 port priority: 255 port number: 2 port state: 61 details partner lacp pdu: system priority: 545 system mac address: 06:00:27:67:e5:85 oper key: 9 port priority: 255 port number: 2 port state: 63</P><P>Not only this value , any of the port level value changes are not reflecting in the output.</P><P>I tried to change it in SysFS file as well "/sys/class/net/bond0/bonding/". That change also not reflecting.</P> Tue, 19 Mar 2024 03:57:32 GMT https://community.hpe.com/t5/operating-system-linux/inquiry-ineffective-port-level-configuration-changes-via-sysfs/m-p/7209170#M105310 AkankshyaDev 2024-03-19T03:57:32Z https://community.hpe.com/t5/operating-system-linux/inquiry-ineffective-port-level-configuration-changes-via-sysfs/m-p/7209302#M105312 <P>Hello,</P><P>You may check if the drivers for the network controller are installed so that it is properly responding to the commands.</P><P>Regards,</P> Mon, 18 Mar 2024 14:00:14 GMT https://community.hpe.com/t5/operating-system-linux/inquiry-ineffective-port-level-configuration-changes-via-sysfs/m-p/7209302#M105312 TVVJ 2024-03-18T14:00:14Z