[as4630-54pe] Branch:202012 Fixed issue for management port eth2 change to eth0(using udev method) #9465
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 name the management interface(eth2-->eth0)
How to verify it
After the modify, I set eth0 new ipaddress in DUT:
using "ifconfig eth0 192.168.1.12"
and ping 192.168.1.37(my PC host side) is success。
Test log:
root@sonic:# ifconfig eth0 192.168.1.12
root@sonic:#
root@sonic:~# ping 192.168.1.37 (Note: 192.168.1.37my local ipddress)
PING 192.168.1.37 (192.168.1.37) 56(84) bytes of data.
64 bytes from 192.168.1.37: icmp_seq=1 ttl=128 time=2.52 ms
64 bytes from 192.168.1.37: icmp_seq=2 ttl=128 time=1.49 ms
64 bytes from 192.168.1.37: icmp_seq=3 ttl=128 time=1.92 ms
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)