Switching

We are facing the following issue:

With an ex2200 device we set a port as a trunk one with a tagged VLAN

The we add an untagged VLAN and we set in the native VLAN value the untagged one

If we connect for example a laptop with windows operating System everything is OK and we reach bot VLAN's

If we connect a linux OS based device, server or latop we can't reach neither the tagged VLAN nor the untagged one

Is there any known issue with this kind of configuration or with this configuration with  linux devices ?

If we set the switch port as access with the untagged VLAN works fine with  linux devices

Thanks in advance for your support

Best Regards

Please, show EX config of interface in trunk mode.

Which linux are you using?

We try with centos and debian an we have the same result.

The junuper configuration is:

ge-0/0/10 {

description Pruebas;

unit 0 {

family ethernet-switching {

port-mode trunk;

vlan {

members [ Telefonia NS-ANTEL ];

}

native-vlan-id Telefonia;

}

}

}

"NS-ANTEL" is the tagged VLAN and "Telefonia" is the untagged one which is defined as native vlan

Thanks in advance

You don't needed to place the untagged vlan to vlan members list.

remove it:

delete interface ge-0/0/10 unit 0 family ethernet-switching vlan members Telefonia

That's working configuration from my servers (Centos):

/etc/sysconfig/network-scripts/ifcfg-eth1.333

VLAN=yes
DEVICE=eth1.333
PHYSDEV=eth1
TYPE=Ethernet
BOOTPROTO=static
ONBOOT=yes
IPADDR=10.200.0.2
NETMASK=255.255.255.0

...and Ubuntu (a part from /etc/networking/interfaces):

auto vlan3004
iface vlan3004 inet static
        address 10.10.12.5
        netmask 255.255.255.248
        vlan_raw_device eth0
        up route add -net 10.16.0.0 netmask 255.255.255.224 gw 10.10.12.2

OK I will try removing the untagged  VLAN form the list and let you know

In your configuration you have the VLAN 333 as tagged and 3004 as untagged is that correct ?

no no no...

Just are different real servers (Centos and Ubuntu).

Sorry to me it makes no sense that one server type works and others do not.  I would not expect and config change to make this all work.  I suggest monitor traffic at the interface and capture packets from working and non-working and compare them.  Use  monitor traffic interace <interface-name> no-resolve  to capture the traffic, or else use port mirror to some device running Wireshack/sniffer and debug this way.

OK thanks for your replay

I know it sounds strange but the problem is not the server, it seem to be the operating system

With windows operating system it works but with unix it is not

That's why I though that could be something relate to the configuration, different MTU or similar

Thanks anyway form your time 

Best Regards

Did you try setting MTU to like 9192 or something BIG?  EX device does not know the difference between external server operating systems.  It must be something different in the packet format.

Small ICMP packets are not susceptible by MTU. ICMP works or not?
First, your config for trunk interface has some mistakes.
Read carefully this KB: https://kb.juniper.net/InfoCenter/index?page=content&id=KB17419&smlogin=true&actp=search
You need to remove native-vlan form vlan members list. That is solution for untagged vlan traffic.

If this is config issue, why does it work for one type (windows) machine, and not others?

this applies for untagged traffic only. Who knows, maybe win nic driver has a different mechanism of behavior for untagged frames. But problem with tagged traffic must be within linux.

Thanks for your replies 

Yes I don't know exactly why it works under windows system but not with linux ones.

The ICMP does not work too

Anyway I will try removing the native VLAN form the tagged list in trunk section and leave it only as native and let you know

Thanks very much form you help

Best Regards,

Hello

Just to let you know that after deleting the native VLAN from the trunk section and let it only in the native section the problem disappear with linux server

Now the switch port respond to both (tagged an native) VLANS

I don't know exactly why only linux servers where affected, perhaps something in the packets level

Thanks in advance for your support