topic RE: Traffic Issue inside newly created VLAN in ExtremeSwitching (EXOS/Switch Engine)

Traffic Issue inside newly created VLAN

Mitch_Hubbell — Thu, 16 Mar 2017 01:42:00 GMT

I'm new to VLAN's and i'm having some issues. I've configured a test VLAN, but am unable to sucessfully ping the other client i've got sitting on this VLAN. I can ping the Primary IP for the VLAN from either of my clients however. Thanks

RE: Traffic Issue inside newly created VLAN

Patrick_Voss — Thu, 16 Mar 2017 01:47:00 GMT

Hello Mitch,

What are the IP's you are trying to Ping. Are they in the same subnet? Are they both directly connected to the switch?

RE: Traffic Issue inside newly created VLAN

Nick_Yakimenko — Thu, 16 Mar 2017 01:47:00 GMT

have you set the tag for a test vlan? Are both ports (yours and clients one) untagged and your pc and other's one have ip-s from one subnet?

RE: Traffic Issue inside newly created VLAN

Mitch_Hubbell — Thu, 16 Mar 2017 01:47:00 GMT

My PC 10.193.150.50/24
Other PC 10.193.150.51/24

Both directly connected, yes.

RE: Traffic Issue inside newly created VLAN

Nick_Yakimenko — Thu, 16 Mar 2017 01:47:00 GMT

maybe you are unable to ping each other because of a firewall? Issue command
arp -a 10.193.150.51
on your pc and show the output

RE: Traffic Issue inside newly created VLAN

Mitch_Hubbell — Thu, 16 Mar 2017 01:47:00 GMT

Interface: 169.254.74.124 --- 0xa Internet Address Physical Address Type
10.193.150.51 f4-4d-30-69-f0-d1 dynamic

RE: Traffic Issue inside newly created VLAN

Nick_Yakimenko — Thu, 16 Mar 2017 01:47:00 GMT

looks like you have more than one active physical interface on your pc and your subnet 10.193.150.0/24 is used by more than one interface
show output of
route print 10*

RE: Traffic Issue inside newly created VLAN

Mitch_Hubbell — Thu, 16 Mar 2017 01:47:00 GMT

C:\WINDOWS\system32>route print 10*===========================================================================
Interface List
13...f8 a9 63 88 8e 2d ......Intel(R) Ethernet Connection I217-LM
10...3c 18 a0 01 d5 e4 ......Thinkpad USB 3.0 Ethernet Adapter
2...c4 d9 87 c5 98 33 ......Intel(R) Centrino(R) Advanced-N 6235
12...c4 d9 87 c5 98 34 ......Microsoft Wi-Fi Direct Virtual Adapter
21...c6 d9 87 c5 98 33 ......Microsoft Hosted Network Virtual Adapter
18...c4 d9 87 c5 98 37 ......Bluetooth Device (Personal Area Network)
1...........................Software Loopback Interface 1
8...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter
17...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter #2
===========================================================================

IPv4 Route Table
===========================================================================
Active Routes:
Network Destination Netmask Gateway Interface Metric
10.193.113.0 255.255.255.0 On-link 10.193.113.65 281
10.193.113.65 255.255.255.255 On-link 10.193.113.65 281
10.193.113.255 255.255.255.255 On-link 10.193.113.65 281
===========================================================================
Persistent Routes:
None

IPv6 Route Table
===========================================================================
Active Routes:
None
Persistent Routes:
None

The "Thinkpad USB 3.0" is connected to the switch port included in my test VLAN

RE: Traffic Issue inside newly created VLAN

Patrick_Voss — Thu, 16 Mar 2017 01:47:00 GMT

To Nick's point I would make sure that all other interfaces on the laptop are turned off and then try the ping.

RE: Traffic Issue inside newly created VLAN

Nick_Yakimenko — Thu, 16 Mar 2017 01:47:00 GMT

I cannot see your thinkpad usb 3.0 adapter as properly installed one

RE: Traffic Issue inside newly created VLAN

Mitch_Hubbell — Thu, 16 Mar 2017 01:47:00 GMT

RE: Traffic Issue inside newly created VLAN

Mitch_Hubbell — Thu, 16 Mar 2017 01:47:00 GMT

I have the dumb today. I am able to ping the Primary IP from my PC's, yet still unable to ping from PC to PC

RE: Traffic Issue inside newly created VLAN

Mitch_Hubbell — Thu, 16 Mar 2017 01:47:00 GMT

What are you meaning about the thinkpad adapter not being properly installed?

RE: Traffic Issue inside newly created VLAN

Nick_Yakimenko — Thu, 16 Mar 2017 01:47:00 GMT

You are pinging Primary ip via default route on your 10.193.110.65 interface
I mean you did not configure static ip 10.193.150.50

RE: Traffic Issue inside newly created VLAN

Mitch_Hubbell — Thu, 16 Mar 2017 01:47:00 GMT

I can see both ports as active

RE: Traffic Issue inside newly created VLAN

Mitch_Hubbell — Thu, 16 Mar 2017 01:47:00 GMT

I have set the Tag for the VLAN to 5 and added the correct ports needed. Both machines are on the proper subnet created for the VLAN

RE: Traffic Issue inside newly created VLAN

Nick_Yakimenko — Thu, 16 Mar 2017 01:47:00 GMT

issue commands
show vlan port n
where n - ports of the machines

RE: Traffic Issue inside newly created VLAN

Henrique — Thu, 16 Mar 2017 01:58:00 GMT

I believe you have a simple diagram as follows:

PC1 (10.193.150.50/24) -------- Switch ------- (10.193.150.50/24) PC2

Can you ping from the switch to both PC1 and PC2? Could be a PC firewall?

RE: Traffic Issue inside newly created VLAN

Mitch_Hubbell — Thu, 16 Mar 2017 01:58:00 GMT

I am able to ping the Primary IP of the switch, just not from PC to PC. Also Windows Firewall is disabled per GPO

RE: Traffic Issue inside newly created VLAN

Ronald_Dvorak — Thu, 16 Mar 2017 02:10:00 GMT

Let's start from scratch...
1) connect the PCs back to back with a patchcable - does the ping work
2) what kind of switch model is it
3) post the output for "show vlan X"