Cisco Nexus vPC unable to Ping port-channel server

[Stryderusa]

Non-Cisco network guy here just learning Cisco.  I have setup vPC on two Nexus 9300 series switches - configured vpc peer keep-alive link, peer link, etd.  i am not doing any special L3 routing except for the peer keep-alive link and inter-VLAN routing.  Everything seems to be working with the vPC configuration - status show "up" and "successful".  However, when I try to Ping any of my ESXi servers connected to these Nexus 9300 switches via virtual port-channels I get "no route to host" error messages.  Note that ESXI vmkernel ports configured as regular access ports are reachable via Ping.  This makes me think there must be a problem with the vPC configuration somewhere.  Please help.

[MHM Cisco World]

this one NSK other NSK can see show ethechannel summary 

[Stryderusa]

Not sure what you are asking?

[Stryderusa]

SH_PFSW# show start vpc

!Command: show startup-config vpc
!Time: Wed Jun 28 14:40:56 2023
!Startup config saved at: Wed Jun 28 11:50:42 2023

version 9.3(9) Bios:version 01.06
feature vpc

vpc domain 1
peer-keepalive destination 192.168.1.2 source 192.168.1.1 vrf keepalive
delay restore 360
peer-gateway
auto-recovery
ip arp synchronize

interface port-channel1
vpc 1

interface port-channel3
vpc 3

interface port-channel5
vpc 5

interface port-channel7
vpc 7

interface port-channel9
vpc 9

interface port-channel11
vpc 11

interface port-channel13
vpc 13

interface port-channel15
vpc 15

interface port-channel21
vpc 21

interface port-channel22
vpc 22

interface port-channel23
vpc 23

interface port-channel24
vpc 24

interface port-channel25
vpc 25

interface port-channel26
vpc 26

interface port-channel27
vpc 27

interface port-channel28
vpc 28

interface port-channel29
vpc peer-link

SH_PFSW#

[MHM Cisco World]

SH_BFSW the PO22 is SU and port is P
SH_PFSW <<- this NSK PO22 is same ?

[Stryderusa]

Yes, correct.

[MHM Cisco World]

from SH_BFSW/SH_PFSW
ping x.x.x.x source VLANx <<- use source in your testing ping