11-15-2019 07:41 AM
Hi all,
hoping some sanity can break out, have been going round and round in circles all day with this... have to admit I'm an enthusiastic amateur .... so please be kind :-)
Server1: 192.168.10.101
Gateway: 192.168.10.254 (assigned to VLAN 10 on Core-SW1)
Connected to: gi1/0/3
Server2: 192.168.10.102
VM: 192.168.200.102
Gateway: 192.168.10.254 (assigned to VLAN 10 on Core-SW1)
Connected to gi/1/0/4
PC: 192.168.200.50
Gateway: 192.168.201.254 (assigned to VLAN 200 on Core-SW1)
Connected to via remote switch port gi1/0/1
This is the current config...
hostname CORE-SW1 no ip cef ip routing ! no ipv6 cef ! spanning-tree mode pvst ! interface GigabitEthernet1/0/1 description EDGE NETWORK switchport trunk encapsulation dot1q switchport mode trunk ! interface GigabitEthernet1/0/2 ! interface GigabitEthernet1/0/3 switchport access vlan 10 switchport mode access switchport nonegotiate ! interface GigabitEthernet1/0/4 switchport trunk allowed vlan 10,200 switchport trunk encapsulation dot1q switchport mode trunk switchport nonegotiate
If I ping 192.168.10.101 from the PC all is good.
if I ping 192.168.10.102 from the PC I get nothing
likewise if I ping 192.168.200.102 from the PC I also get nothing.
in fact if I ping 192.168.10.102 from 192.168.10.101 I also get nothing and it can't ping it's own gateway address.
What is the best way to configure the switch port so that the server can support multiple VLAN's for a Hyper-V host server?
I know it's me can someone's fresh eyes enlighten me please ?
11-15-2019 07:54 AM
11-15-2019 03:52 PM
11-15-2019 08:53 AM
To be able to ping the server 192.168.10.102 add this to your configuration -
int gi1/0/4
switchport trunk native vlan 10
and for the VM have you told it to use vlan 200 ?
So in hyper-V manager edit the settings for the VM and under the "Network Adapter" settings click "Enable virtual LAN identification" and then in the box below enter the vlan number "200".
Jon
11-15-2019 03:55 PM
11-16-2019 04:30 AM
Best ignore what I put then as I was assuming this was a production setup not a PT lab.
Jon
11-16-2019 04:48 AM
11-16-2019 04:49 AM
11-16-2019 01:44 PM
11-16-2019 02:54 PM
11-20-2019 03:05 AM
Hi Jaderson, it's 7.2.2 … I think I've resolve the issue by rebooting (yeah who'd have thought eh) the core switch
thanks for your help.
Paul.
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