[action] [PR:17888] update d18u8s4 PT0 ASN to 4 bytes#19474
Merged
mssonicbld merged 1 commit intosonic-net:202411from Jul 9, 2025
Merged
[action] [PR:17888] update d18u8s4 PT0 ASN to 4 bytes#19474mssonicbld merged 1 commit intosonic-net:202411from
mssonicbld merged 1 commit intosonic-net:202411from
Conversation
What is the motivation for this PR? Fix topo error. How did you do it? How did you verify/test it? admin@sonic:~$ show ip bgp summary IPv4 Unicast Summary: BGP router identifier 10.1.0.32, local AS number 65100 vrf-id 0 BGP table version 2 RIB entries 3, using 672 bytes of memory Peers 12, using 8903712 KiB of memory Peer groups 5, using 320 bytes of memory Neighbhor V AS MsgRcvd MsgSent TblVer InQ OutQ Up/Down State/PfxRcd NeighborName ----------- --- ---------- --------- --------- -------- ----- ------ --------- -------------- -------------- 10.0.0.57 4 64600 0 0 0 0 0 never Active ARISTA01T1 10.0.0.59 4 64600 0 0 0 0 0 never Active ARISTA02T1 10.0.0.61 4 64600 0 0 0 0 0 never Active ARISTA03T1 10.0.0.63 4 64600 0 0 0 0 0 never Active ARISTA04T1 10.0.0.65 4 64600 0 0 0 0 0 never Active ARISTA05T1 10.0.0.67 4 64600 0 0 0 0 0 never Active ARISTA06T1 10.0.0.69 4 64600 0 0 0 0 0 never Active ARISTA07T1 10.0.0.71 4 64600 0 0 0 0 0 never Active ARISTA08T1 10.0.0.157 4 4200000000 0 0 0 0 0 never Active ARISTA01PT0 10.0.0.159 4 4200000001 0 0 0 0 0 never Active ARISTA02PT0 10.0.0.161 4 4200000002 0 0 0 0 0 never Active ARISTA03PT0 10.0.0.163 4 4200000003 0 0 0 0 0 never Active ARISTA04PT0 Total number of neighbors 12 admin@sonic:~$ show ipv6 bgp summary IPv6 Unicast Summary: BGP router identifier 10.1.0.32, local AS number 65100 vrf-id 0 BGP table version 2 RIB entries 3, using 672 bytes of memory Peers 12, using 8903712 KiB of memory Peer groups 5, using 320 bytes of memory Neighbhor V AS MsgRcvd MsgSent TblVer InQ OutQ Up/Down State/PfxRcd NeighborName ----------- --- ---------- --------- --------- -------- ----- ------ --------- -------------- -------------- fc00::7a 4 64600 0 0 0 0 0 never Active ARISTA03T1 fc00::7e 4 64600 0 0 0 0 0 never Active ARISTA04T1 fc00::8a 4 64600 0 0 0 0 0 never Active ARISTA07T1 fc00::8e 4 64600 0 0 0 0 0 never Active ARISTA08T1 fc00::17a 4 4200000002 0 0 0 0 0 never Active ARISTA03PT0 fc00::17e 4 4200000003 0 0 0 0 0 never Active ARISTA04PT0 fc00::72 4 64600 0 0 0 0 0 never Active ARISTA01T1 fc00::76 4 64600 0 0 0 0 0 never Active ARISTA02T1 fc00::82 4 64600 0 0 0 0 0 never Active ARISTA05T1 fc00::86 4 64600 0 0 0 0 0 never Active ARISTA06T1 fc00::172 4 4200000000 0 0 0 0 0 never Active ARISTA01PT0 fc00::176 4 4200000001 0 0 0 0 0 never Active ARISTA02PT0 Total number of neighbors 12 admin@sonic:~$
11 tasks
Collaborator
Author
|
Original PR: #17888 |
Collaborator
Author
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Description of PR
Summary:
Fixes same issue in #22022 by updating the peer T0's ASN to 4 bytes ASN number.
Type of change
Back port request
Approach
What is the motivation for this PR?
Fix topo error.
How did you do it?
How did you verify/test it?
Any platform specific information?
Supported testbed topology if it's a new test case?
Documentation