[as4630-54pe] Branch:master Fixed issue for management port eth2 change to eth0(using udev method) #9560
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
…ge to eth0(using udev method)
Why I did it
Our management port is using eth2, but now need to change to using eth0.
How I did it
Use the method: u-dev rules to binding eth2's pci address into eth0.
How to verify it
After the modify, checking ifconfig RUNNING flags, means eth0 is linking.
Demo log:
root@sonic:~# ifconfig eth0
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.15.174 netmask 255.255.240.0 broadcast 192.168.15.255
inet6 fe80::6a21:5fff:fe48:95c3 prefixlen 64 scopeid 0x20
ether 68:21:5f:48:95:c3 txqueuelen 1000 (Ethernet)
RX packets 73 bytes 11819 (11.5 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 27 bytes 4220 (4.1 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
Which release branch to backport (provide reason below if selected)
Description for the changelog
Using udev method to manage interface: eth2 to eth0.
A picture of a cute animal (not mandatory but encouraged)