10-28-2022 12:30 PM
Hi Everyone,
I recently created a new VLAN (15) on our switch and matching subinterface on our ISR.
We have a HyperV server connected on a Dell Blade server and switch, connected to our Cisco switch via portchannel, with host 10.0.11.160.
We also have another HyperV server connected directly to the switch, with a host 10.0.11.170.
From a host on the same switch, on VLAN 10 (192.168.170.250), i can ping 10.0.11.160 but not 10.0.11.170.
From the switch and ISR i can ping both 10.0.11.160 and 10.0.11.170 without issue.
The three hosts have their gateway configured to the respective subinterface on the same ISR. Could someone please take a look at our configs? I think my mistake is with the trunk link between the Blade switches and the Cisco switches but am unsure what...
From the switch config, interface GigabitEthernet1/0/31 has the host (10.0.11.170) that DOES respond to 192.168.170.250.
Port-channel1, consisting of physical ports TenGigabitEthernet1/1/1 and 2, hosts 10.0.11.160, the IP that doesnt respond from 192.168.170.250.
Internet 10.0.11.160 0 0050.56b2.d717 ARPA Vlan15
15 0050.56b2.d717 DYNAMIC Po1
Thank you for any help and suggestions,
Jesse
Solved! Go to Solution.
10-28-2022 01:36 PM
Good if you can post a small diagram of how these are connected.
high level some observation on SW01
why all these ports in same port-channel ? if they going to different switches ? -
I feel that is wrong, so correct it, also why the trunk port acting as access VLAN 10 (If you looking to allow other VLANs as the trunk, and remove access VLAN 10 config from the interface)
interface Port-channel1
description SW01-BLADE-CoLo Te0/9
switchport access vlan 10
switchport trunk allowed vlan 10,15,16,30,50
switchport mode trunk
!
interface GigabitEthernet1/0/31
description [ESX09:VMNIC2]
switchport trunk native vlan 10
switchport trunk allowed vlan 10,15,16
switchport mode trunk
!
interface GigabitEthernet1/0/42
description WINDSTREAM LINK CoLo-ISR02 PORT G0/1
switchport trunk allowed vlan 10,15,16,30,160,170
switchport mode trunk
!
interface TenGigabitEthernet1/1/1
description SW01-BLADE-CoLo Te0/9
switchport access vlan 10
switchport trunk allowed vlan 10,15,16,30,50
switchport mode trunk
ip flow monitor Scrut_mon_input input
ip flow monitor Scrut_mon_output output
channel-group 1 mode active
!
interface TenGigabitEthernet1/1/2
description BLADE-SFP2
switchport access vlan 10
switchport trunk allowed vlan 10,15,16,30,50
switchport mode trunk
ip flow monitor Scrut_mon_input input
ip flow monitor Scrut_mon_output output
channel-group 1 mode active
10-28-2022 01:36 PM
Good if you can post a small diagram of how these are connected.
high level some observation on SW01
why all these ports in same port-channel ? if they going to different switches ? -
I feel that is wrong, so correct it, also why the trunk port acting as access VLAN 10 (If you looking to allow other VLANs as the trunk, and remove access VLAN 10 config from the interface)
interface Port-channel1
description SW01-BLADE-CoLo Te0/9
switchport access vlan 10
switchport trunk allowed vlan 10,15,16,30,50
switchport mode trunk
!
interface GigabitEthernet1/0/31
description [ESX09:VMNIC2]
switchport trunk native vlan 10
switchport trunk allowed vlan 10,15,16
switchport mode trunk
!
interface GigabitEthernet1/0/42
description WINDSTREAM LINK CoLo-ISR02 PORT G0/1
switchport trunk allowed vlan 10,15,16,30,160,170
switchport mode trunk
!
interface TenGigabitEthernet1/1/1
description SW01-BLADE-CoLo Te0/9
switchport access vlan 10
switchport trunk allowed vlan 10,15,16,30,50
switchport mode trunk
ip flow monitor Scrut_mon_input input
ip flow monitor Scrut_mon_output output
channel-group 1 mode active
!
interface TenGigabitEthernet1/1/2
description BLADE-SFP2
switchport access vlan 10
switchport trunk allowed vlan 10,15,16,30,50
switchport mode trunk
ip flow monitor Scrut_mon_input input
ip flow monitor Scrut_mon_output output
channel-group 1 mode active
10-28-2022 02:15 PM
Thank you for the response. I agree about those ports not needing switchport access vlan 10. I think i found we issue though. I noticed on the blade switch i couldnt ping anything but things in the local .170 subnet. It didnt have a default route set.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide