topic Portchannel question in Switching

Portchannel question

grapevine — Mon, 25 Aug 2025 21:52:07 GMT

We have 3 Cisco IE-9320 in a stack. We have a Portchannel connecting to ESXI from switch 2 port 3 and switch 3 port 4

4 Po4(SU) - Gi2/0/3(P) Gi3/0/4(P).

Ports are in bundled.

GigabitEthernet2/0/3 media type is 10/100/1000BaseTX SFP

GigabitEthernet3/0/4 media type is 10/100/1000BaseTX

ESXI nic teaming is configured as Route based on IP hash.

Ping to esxi is dropping intermittently

SW01#sh run int Po4
Building configuration...

Current configuration : 127 bytes
!
interface Port-channel4
switchport trunk allowed vlan 16,18
switchport mode trunk
end

SW01#sh run int Gi2/0/3
Building configuration...

Current configuration : 168 bytes
!
interface GigabitEthernet2/0/3
switchport trunk allowed vlan 16,18
switchport mode trunk
channel-group 4 mode on
end

SW01#sh run int Gi3/0/4
Building configuration...

Current configuration : 168 bytes
!
interface GigabitEthernet3/0/4
switchport trunk allowed vlan 16,18
switchport mode trunk
channel-group 4 mode on
end

arp is incomplete for esxi in firewalls. please advise how to fix it

Re: Portchannel question

paul driver — Mon, 25 Aug 2025 22:42:38 GMT

Hello
If the ESXI teaming supports it change the PC both ends from a static to dynamic (LACP)

Re: Portchannel question

grapevine — Mon, 25 Aug 2025 22:44:37 GMT

ESXI's current license doesn't support LACP

Re: Portchannel question

Kasun Bandara — Tue, 26 Aug 2025 00:51:32 GMT

@grapevine hi, looks like configuration is ok. is there any specific ARP are you looking for?

do you have any test VM on esxi with IP address form VLAN16,18 to test?

and , did you configured teaming at vswitch in esxi?

Re: Portchannel question

paul driver — Tue, 26 Aug 2025 03:14:39 GMT

Hello
On the cicso portchannel

int port 4
spanning-tree portfast trunk

Re: Portchannel question

grapevine — Tue, 26 Aug 2025 03:18:53 GMT

It was working fine and stopped all of a sudden. I am not able to ping any vms inside the esxi. There are vms in vlan 16 and 18

Re: Portchannel question

MHM Cisco World — Tue, 26 Aug 2025 03:38:05 GMT

In SW do

Show vlan brief <<- share this

MHM

Re: Portchannel question

Kasun Bandara — Tue, 26 Aug 2025 03:45:16 GMT

@grapevine ok. so its sudden issue. was there any changes on server side or switch side? and as @MHM Cisco World mentioned, can you share the vlan information from switch, and #sh etherchannel sum, and check if there is any VLAN changes at VSwitch in esxi.

Re: Portchannel question

grapevine — Tue, 26 Aug 2025 11:12:37 GMT

Re: Portchannel question

grapevine — Tue, 26 Aug 2025 11:16:59 GMT

No changes were made as far as I remember

Re: Portchannel question

MHM Cisco World — Tue, 26 Aug 2025 11:17:13 GMT

Show interface trunk

Show switchport interface <PO>

Show switchport interface <g2/0/3 & g3/0/4>

Share this please

MHM

Re: Portchannel question

MHM Cisco World — Tue, 26 Aug 2025 11:36:21 GMT

Show switchport interface

Not show interface

Let see if port member and PO run as trunk not as access interface

MHM

Re: Portchannel question

grapevine — Tue, 26 Aug 2025 11:43:16 GMT

I dont see show switchport interface command listed

PVW-CSW01#show switch?
switch

I found out something now

Switch 3 in the stack has rebooted. We saw this in the past when switch reboots and adds in the stack the connected esxi and servers go offline, server guys did some changes in the esxi and it came back online

Switch 03
---------
Switch uptime : 18 hours, 39 minutes

Base Ethernet MAC Address :
Motherboard Assembly Number :
Motherboard Serial Number :
Model Revision Number : G0
Motherboard Revision Number : D0
Model Number : IE-9320-24T4X
System Serial Number :
Last reload reason : EHSA standby down

Re: Portchannel question

MHM Cisco World — Tue, 26 Aug 2025 14:12:04 GMT

show interface switchport <<- sorry this order
MHM

Re: Portchannel question

grapevine — Tue, 26 Aug 2025 14:38:05 GMT

Name: Gi2/0/3
Switchport: Enabled
Administrative Mode: trunk
Operational Mode: trunk (member of bundle Po4)
Administrative Trunking Encapsulation: dot1q
Operational Trunking Encapsulation: dot1q
Negotiation of Trunking: On
Access Mode VLAN: 1 (default)
Trunking Native Mode VLAN: 1 (default)
Administrative Native VLAN tagging: disabled
Voice VLAN: none
Administrative private-vlan host-association: none
Administrative private-vlan mapping: none
Administrative private-vlan trunk native VLAN: none
Administrative private-vlan trunk Native VLAN tagging: enabled
Administrative private-vlan trunk encapsulation: dot1q
Administrative private-vlan trunk normal VLANs: none
Administrative private-vlan trunk associations: none
Administrative private-vlan trunk mappings: none
Operational private-vlan: none
Trunking VLANs Enabled: 16,18
Pruning VLANs Enabled: 2-1001
Capture Mode Disabled
Capture VLANs Allowed: ALL

Protected: false
Unknown unicast blocked: disabled
Unknown multicast blocked: disabled
Vepa Enabled: false
App Interface: false
Appliance trust: none

Name: Gi3/0/4
Switchport: Enabled
Administrative Mode: trunk
Operational Mode: trunk (member of bundle Po4)
Administrative Trunking Encapsulation: dot1q
Operational Trunking Encapsulation: dot1q
Negotiation of Trunking: On
Access Mode VLAN: 1 (default)
Trunking Native Mode VLAN: 1 (default)
Administrative Native VLAN tagging: disabled
Voice VLAN: none
Administrative private-vlan host-association: none
Administrative private-vlan mapping: none
Administrative private-vlan trunk native VLAN: none
Administrative private-vlan trunk Native VLAN tagging: enabled
Administrative private-vlan trunk encapsulation: dot1q
Administrative private-vlan trunk normal VLANs: none
Administrative private-vlan trunk associations: none
Administrative private-vlan trunk mappings: none
Operational private-vlan: none
Trunking VLANs Enabled: 16,18
Pruning VLANs Enabled: 2-1001
Capture Mode Disabled
Capture VLANs Allowed: ALL

Protected: false
Unknown unicast blocked: disabled
Unknown multicast blocked: disabled
Vepa Enabled: false
App Interface: false
Appliance trust: none

Name: Po4
Switchport: Enabled
Administrative Mode: trunk
Operational Mode: trunk
Administrative Trunking Encapsulation: dot1q
Operational Trunking Encapsulation: dot1q
Negotiation of Trunking: On
Access Mode VLAN: 1 (default)
Trunking Native Mode VLAN: 1 (default)
Administrative Native VLAN tagging: disabled
Voice VLAN: none
Administrative private-vlan host-association: none
Administrative private-vlan mapping: none
Administrative private-vlan trunk native VLAN: none
Administrative private-vlan trunk Native VLAN tagging: enabled
Administrative private-vlan trunk encapsulation: dot1q
Administrative private-vlan trunk normal VLANs: none
Administrative private-vlan trunk associations: none
Administrative private-vlan trunk mappings: none
Operational private-vlan: none
Trunking VLANs Enabled: 16,18
Pruning VLANs Enabled: 2-1001

Protected: false
Unknown unicast blocked: disabled
Unknown multicast blocked: disabled
Vepa Enabled: false
App Interface: false
Appliance trust: none

Re: Portchannel question

MHM Cisco World — Tue, 26 Aug 2025 14:45:17 GMT

monitor capture PO type traffic interface Port-channel1 both

monitor capture PO match ipv4 host <EXSI host IP> any

monitor capture PO start <<- start ping to ESXI one for host in vlan16 and other in vlan 18

monitor capture PO stop

show monitor capture PO brief

share the output of brief

MHM

Re: Portchannel question

MHM Cisco World — Tue, 26 Aug 2025 14:48:11 GMT

before run capture
try shut/no shut PO since you run ON mode and one of stack SW is down 21 hrs ago

MHM

Re: Portchannel question

grapevine — Tue, 26 Aug 2025 14:57:53 GMT

PVW-CSW01#show monitor capture po ?
buffer Display captured buffer
parameter Display commands used to create capture point
| Output modifiers
<cr> <cr>

PVW-CSW01#show monitor capture po buffer
buffer size (KB) : 10240
buffer used (KB) : 0
packets in buf : 0
packets dropped : 0
packets per sec : 0

Re: Portchannel question

MHM Cisco World — Tue, 26 Aug 2025 15:01:08 GMT

did you start ping then stop the capture ?

PVW-CSW01#show monitor capture po buffer brief <<-

Re: Portchannel question

grapevine — Tue, 26 Aug 2025 15:10:05 GMT

Yes I started and stopped

PVW-CSW01#show monitor capture po parameter
monitor capture po interface Port-channel4 BOTH
monitor capture po match ipv4 any host 10.150.16.43
monitor capture po buffer size 10
monitor capture po limit pps 1000
PVW-CSW01#monitor capture po start
Started capture point : po
PVW-CSW01#ping 10.150.16.43
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.150.16.43, timeout is 2 seconds:
.....
Success rate is 0 percent (0/5)
PVW-CSW01#monitor capture po stop
Bytes dropped in asic - 0

Stopped capture point : po
PVW-CSW01#show monitor capture po parameter
monitor capture po interface Port-channel4 BOTH
monitor capture po match ipv4 any host 10.150.16.43
monitor capture po buffer size 10
monitor capture po limit pps 1000
PVW-CSW01#show monitor capture po buffer
buffer size (KB) : 10240
buffer used (KB) : 0
packets in buf : 0
packets dropped : 0
packets per sec : 0

PVW-CSW01#show monitor capture po buffer ?
brief brief display
detailed detailed disaply
dump for dump
| Output modifiers
<cr> <cr>

PVW-CSW01#show monitor capture po buffer br
PVW-CSW01#show monitor capture po buffer brief
----------------------------------------------------------------------------
# size timestamp source destination dscp protocol
----------------------------------------------------------------------------