Confused on creating vlan for 40F

Hi,
which port binds with VLAN port2 or the hardware switch that you have created with port2. 

Regards

Mahesh

Hi,

Can you remove port 2 from the hardware switch and try creating the same VLAN on that port?

Regards

Mahesh

still no change when I plug in test device.  get ip 169.254.194.172

Plugged directly into port 2 on 40F with test device, WAN port goes to router, and port 1 goes to an unmanaged switch.  Do I need to create a network policy after that?, I thought I should be able to ping a device once the VLAN is created.

On the same token with @hbac, I would doubt your test device is not properly configured to accept the VLAN tagged ethernet frames from the 40F on port2 what ever the tag is.

Some suggestions I have on the 40F side are, you can add VLAN ID column in the interface view GUI you posted. And you can move the column around like just next to the Type column. Then don't use VLAN ID=1 because it's reserved. And then when you run sniffing in CLI like "diag sniffer packet lan2" you should see VLAN tagged traffic like below. It's obvious but below are tagged with VLAN ID 201:

0.305291 802.1Q vlan#201 P0
0.559136 802.1Q vlan#201 P0
0.559255 802.1Q vlan#201 P0
0.570233 802.1Q vlan#201 P0
0.582141 802.1Q vlan#201 P0
0.582201 802.1Q vlan#201 P0

On the other side, use a vlan capable switch to accept the vlan on a trunk port then span it to a vlan access port so that  you can hook up a simple device like a laptop without any VLAN setting.

Toshi 

You're last post shows you configured VLAN ID 10 properly. So it comes back to the doubt of the test device.

diagnose sniffer packet any 'portrange 1000-3000' 6 0 a - I tried this in CLI and it says unknown action

but basically I will need to get a managed switch in order to test off correct? I believe that makes sense for the vlan.

I have my main machine on port 1 which is hardware switch.  I'm kinda surprised I can't just replicate this on port 2 or 3 with different ip range.