- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - Linux
- >
- Inquiry: Ineffective Port-Level Configuration Chan...
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-16-2024 08:11 AM - last edited on 03-18-2024 08:57 PM by support_s
03-16-2024 08:11 AM - last edited on 03-18-2024 08:57 PM by support_s
Inquiry: Ineffective Port-Level Configuration Changes via SysFS Interface
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.
Could you please provide guidance on resolving this discrepancy? Your assistance in troubleshooting and rectifying this matter would be greatly appreciated.
Thank you for your attention to this issue.
Thanks, Akankshya
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 .
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
Not only this value , any of the port level value changes are not reflecting in the output.
I tried to change it in SysFS file as well "/sys/class/net/bond0/bonding/". That change also not reflecting.
- Tags:
- Operating System
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-18-2024 07:00 AM
03-18-2024 07:00 AM
Re: Inquiry: Ineffective Port-Level Configuration Changes via SysFS Interface
Hello,
You may check if the drivers for the network controller are installed so that it is properly responding to the commands.
Regards,
Views expressed herein are my personal opinion and are not the views of HPE