Skip to content

Show vnet route cli update on 202511#4448

Merged
vmittal-msft merged 2 commits into
sonic-net:202511from
alawing:dev/davizhang/addshowmetric202511
Apr 11, 2026
Merged

Show vnet route cli update on 202511#4448
vmittal-msft merged 2 commits into
sonic-net:202511from
alawing:dev/davizhang/addshowmetric202511

Conversation

@alawing

@alawing alawing commented Apr 10, 2026

Copy link
Copy Markdown
Contributor

What I did

It is a manually cherry-pick from #4332

Updating the show vnet cli:
1. showing new filed "metric" in show vnet route all/tunnel
2. added <vnet_name> for specific vnet name on vnet show route all/local/tunnel commands

How I did it

  1. added metric field in show vnet route
  2. changed show vnet show route all/tunnel, and added vnet show route local
  3. updated command reference document
  4. Added mock test cases and related unit tests

How to verify it

added unit tests and passed.
image

Previous command output (if the output of a command-line utility has changed)

>show vnet routes all

vnet name        prefix            nexthop                                interface
---------------  ----------------  -------------------------------------  -------------------------------
test_v4_in_v4-0  160.162.191.1/32  100.100.4.1                            Ethernet1
test_v4_in_v4-0  160.163.191.1/32  100.101.4.1, 100.101.4.2               Ethernet1, Ethernet2
test_v4_in_v4-0  160.164.191.1/32  100.102.4.1, 100.102.4.2, 100.102.4.3  Ethernet1, Ethernet2, Ethernet3
test_v4_in_v4-1  160.165.191.1/32  100.103.4.1, 100.103.4.2, 100.103.4.3  Ethernet1, Ethernet2, Ethernet3

vnet name        prefix                    endpoint                                     mac address    vni    status
---------------  ------------------------  -------------------------------------------  -------------  -----  --------
Vnet_v6_in_v6-0  fddd:a156:a251::a6:1/128  fddd:a100:a251::a10:1,fddd:a101:a251::a10:1                        active
                                           fddd:a102:a251::a10:1,fddd:a103:a251::a10:1
test_v4_in_v4-0  160.162.191.1/32          100.251.7.1                                                        active
test_v4_in_v4-0  160.163.191.1/32          100.251.7.1                                                        active
test_v4_in_v4-0  160.164.191.1/32          100.251.7.1

>show vnet routes tunnel

vnet name        prefix                    endpoint                                                                                 mac address    vni
---------------  ------------------------  ---------------------------------------------------------------------------------------  -------------  -----
Vnet_v6_in_v6-0  fddd:a156:a251::a6:1/128  fddd:a100:a251::a10:1,fddd:a101:a251::a10:1,fddd:a102:a251::a10:1,fddd:a103:a251::a10:1
test_v4_in_v4-0  160.162.191.1/32          100.251.7.1
test_v4_in_v4-0  160.163.191.1/32          100.251.7.1
test_v4_in_v4-0  160.164.191.1/32          100.251.7.1

New command output (if the output of a command-line utility has changed)

>show vnet routes all

vnet name        prefix            nexthop                                interface
---------------  ----------------  -------------------------------------  -------------------------------
test_v4_in_v4-0  160.162.191.1/32  100.100.4.1                            Ethernet1
test_v4_in_v4-0  160.163.191.1/32  100.101.4.1, 100.101.4.2               Ethernet1, Ethernet2
test_v4_in_v4-0  160.164.191.1/32  100.102.4.1, 100.102.4.2, 100.102.4.3  Ethernet1, Ethernet2, Ethernet3
test_v4_in_v4-1  160.165.191.1/32  100.103.4.1, 100.103.4.2, 100.103.4.3  Ethernet1, Ethernet2, Ethernet3

vnet name        prefix                    endpoint                                     mac address    vni    metric    status
---------------  ------------------------  -------------------------------------------  -------------  -----  --------  --------
Vnet_v6_in_v6-0  fddd:a156:a251::a6:1/128  fddd:a100:a251::a10:1,fddd:a101:a251::a10:1                                  active
                                           fddd:a102:a251::a10:1,fddd:a103:a251::a10:1
test_v4_in_v4-0  160.162.191.1/32          100.251.7.1                                                                  active
test_v4_in_v4-0  160.163.191.1/32          100.251.7.1                                                        0         active
test_v4_in_v4-0  160.164.191.1/32          100.251.7.1

>show vnet routes all test_v4_in_v4-0

vnet name        prefix            nexthop                                interface
---------------  ----------------  -------------------------------------  -------------------------------
test_v4_in_v4-0  160.162.191.1/32  100.100.4.1                            Ethernet1
test_v4_in_v4-0  160.163.191.1/32  100.101.4.1, 100.101.4.2               Ethernet1, Ethernet2
test_v4_in_v4-0  160.164.191.1/32  100.102.4.1, 100.102.4.2, 100.102.4.3  Ethernet1, Ethernet2, Ethernet3

vnet name        prefix            endpoint     mac address    vni      metric  status
---------------  ----------------  -----------  -------------  -----  --------  --------
test_v4_in_v4-0  160.162.191.1/32  100.251.7.1                                  active
test_v4_in_v4-0  160.163.191.1/32  100.251.7.1                               0  active
test_v4_in_v4-0  160.164.191.1/32  100.251.7.1

> show vnet routes tunnel

vnet name        prefix                    endpoint                                     mac address    vni    metric    status
---------------  ------------------------  -------------------------------------------  -------------  -----  --------  --------
Vnet_v6_in_v6-0  fddd:a156:a251::a6:1/128  fddd:a100:a251::a10:1,fddd:a101:a251::a10:1                                  active
                                           fddd:a102:a251::a10:1,fddd:a103:a251::a10:1
test_v4_in_v4-0  160.162.191.1/32          100.251.7.1                                                                  active
test_v4_in_v4-0  160.163.191.1/32          100.251.7.1                                                        0         active
test_v4_in_v4-0  160.164.191.1/32          100.251.7.1

>show vnet routes tunnel test_v4_in_v4-0

vnet name        prefix            endpoint     mac address    vni      metric  status
---------------  ----------------  -----------  -------------  -----  --------  --------
test_v4_in_v4-0  160.162.191.1/32  100.251.7.1                                  active
test_v4_in_v4-0  160.163.191.1/32  100.251.7.1                               0  active
test_v4_in_v4-0  160.164.191.1/32  100.251.7.1

>show vnet routes local

vnet name        prefix            nexthop                                interface
---------------  ----------------  -------------------------------------  -------------------------------
test_v4_in_v4-0  160.162.191.1/32  100.100.4.1                            Ethernet1
test_v4_in_v4-0  160.163.191.1/32  100.101.4.1, 100.101.4.2               Ethernet1, Ethernet2
test_v4_in_v4-0  160.164.191.1/32  100.102.4.1, 100.102.4.2, 100.102.4.3  Ethernet1, Ethernet2, Ethernet3
test_v4_in_v4-1  160.165.191.1/32  100.103.4.1, 100.103.4.2, 100.103.4.3  Ethernet1, Ethernet2, Ethernet3

>show vnet routes local test_v4_in_v4-0

vnet name        prefix            nexthop                                interface
---------------  ----------------  -------------------------------------  -------------------------------
test_v4_in_v4-0  160.162.191.1/32  100.100.4.1                            Ethernet1
test_v4_in_v4-0  160.163.191.1/32  100.101.4.1, 100.101.4.2               Ethernet1, Ethernet2
test_v4_in_v4-0  160.164.191.1/32  100.102.4.1, 100.102.4.2, 100.102.4.3  Ethernet1, Ethernet2, Ethernet3

alawing added 2 commits April 10, 2026 14:38
@alawing
mertirc and vnetname code into 202511
3f3c605 
Signed-off-by: alawing <alawing@gmail.com>
@alawing
fix merge issue
a7e3b68 
Signed-off-by: alawing <alawing@gmail.com>
@mssonicbld

mssonicbld commented Apr 10, 2026

Copy link
Copy Markdown
Collaborator

/azp run

@azure-pipelines

azure-pipelines Bot commented Apr 10, 2026

Copy link
Copy Markdown
Azure Pipelines successfully started running 1 pipeline(s).

@vmittal-msft vmittal-msft merged commit 902205a into sonic-net:202511 Apr 11, 2026
9 checks passed
alawing added a commit to alawing/sonic-utilities that referenced this pull request Apr 17, 2026
@alawing
update command-reference.md for sonic-net#4448
8720d79 
Signed-off-by: alawing <alawing@gmail.com>
alawing added a commit to alawing/sonic-utilities that referenced this pull request Apr 17, 2026
@alawing
update command-reference.md for sonic-net#4448
b34df76 
Signed-off-by: alawing <alawing@gmail.com>
@alawing alawing mentioned this pull request Apr 17, 2026
Merged
@mssonicbld mssonicbld mentioned this pull request Apr 17, 2026
Merged
@mssonicbld

mssonicbld commented Apr 17, 2026

Copy link
Copy Markdown
Collaborator

Cherry-pick PR to msft-202506: Azure/sonic-utilities.msft#313

vmittal-msft pushed a commit that referenced this pull request Apr 18, 2026
@alawing
update command-reference.md for #4448 (#4471)
30b4d40 
Signed-off-by: alawing <alawing@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@vmittal-msft vmittal-msft vmittal-msft approved these changes
+1 more reviewer
@anish-n anish-n anish-n approved these changes
Reviewers whose approvals may not affect merge requirements

Assignees

No one assigned

Labels

Approved for msft-202506 Branch Included in msft-202506 Branch Request for msft-202506 Branch

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

5 participants

@alawing @mssonicbld @anish-n @vmittal-msft @prabhataravind