AS7816-64X untagged VLAN issue

[titanlock]

I am trying to setup my ports to be untagged VLANs but when I do this I am not able to get any traffic through the ports. If I do "show interface status" it shows that the port is "trunk".

This is true for either using a command to set the VLAN or from the config_db.json.

Here is what my VLAN config looks like:

    "VLAN": {
        "Vlan3002": { 
                "members": [
                        "Ethernet0",
                        "Ethernet4",
                        "Ethernet8",
                        "Ethernet12",
                        "Ethernet16",
                        "Ethernet20",
                        "Ethernet24",
                        "Ethernet28",
                        "Ethernet32",
                        "Ethernet36",
                        "Ethernet40",
                        "Ethernet44",
                        "Ethernet120",
                        "Ethernet252"
                ],
                "vlanid": "3002"
        }
    },
    "VLAN_MEMBER": {
            "Vlan3002|Ethernet0": {
                    "tagging_mode": "untagged"
            },
            "Vlan3002|Ethernet4": {
                    "tagging_mode": "tagged"
            },
            "Vlan3002|Ethernet8": {
                    "tagging_mode": "tagged"
            },
            "Vlan3002|Ethernet12": {
                    "tagging_mode": "tagged"
            },
            "Vlan3002|Ethernet16": {
                    "tagging_mode": "tagged"
            },
            "Vlan3002|Ethernet20": {
                    "tagging_mode": "tagged"
            },
            "Vlan3002|Ethernet24": {
                    "tagging_mode": "tagged"
            },
            "Vlan3002|Ethernet28": {
                    "tagging_mode": "tagged"
            },
            "Vlan3002|Ethernet32": {
                    "tagging_mode": "tagged"
            },
            "Vlan3002|Ethernet36": {
                    "tagging_mode": "tagged"
            },
            "Vlan3002|Ethernet40": {
                    "tagging_mode": "tagged"
            },
            "Vlan3002|Ethernet44": {
                    "tagging_mode": "tagged"
            },
            "Vlan3002|Ethernet252": {
                    "tagging_mode": "tagged"
            }
    }

"show vlan config"

Name        VID  Member       Mode
--------  -----  -----------  --------
Vlan3002   3002  Ethernet0    untagged
Vlan3002   3002  Ethernet4    tagged
Vlan3002   3002  Ethernet8    tagged
Vlan3002   3002  Ethernet12   tagged
Vlan3002   3002  Ethernet16   tagged
Vlan3002   3002  Ethernet20   tagged
Vlan3002   3002  Ethernet24   tagged
Vlan3002   3002  Ethernet28   tagged
Vlan3002   3002  Ethernet32   tagged
Vlan3002   3002  Ethernet36   tagged
Vlan3002   3002  Ethernet40   tagged
Vlan3002   3002  Ethernet44   tagged
Vlan3002   3002  Ethernet252  tagged

Here is what "show interface status" shows:

  Interface            Lanes    Speed    MTU          Alias    Vlan    Oper    Admin             Type    Asym PFC
-----------  ---------------  -------  -----  -------------  ------  ------  -------  ---------------  ----------
  Ethernet0      73,74,75,76      40G   1500   hundredGigE1   trunk    down       up  QSFP28 or later         N/A
  Ethernet4      65,66,67,68     100G   9100   hundredGigE2   trunk    down       up  QSFP28 or later         N/A
  Ethernet8      81,82,83,84     100G   9100   hundredGigE3   trunk    down       up  QSFP28 or later         N/A
 Ethernet12      89,90,91,92     100G   9100   hundredGigE4   trunk    down       up   QSFP+ or later         N/A
 Ethernet16  105,106,107,108     100G   9100   hundredGigE5   trunk    down       up   QSFP+ or later         N/A
 Ethernet20     97,98,99,100     100G   9100   hundredGigE6   trunk    down       up              N/A         N/A
 Ethernet24  113,114,115,116     100G   9100   hundredGigE7   trunk    down       up              N/A         N/A
 Ethernet28  121,122,123,124     100G   9100   hundredGigE8   trunk    down       up              N/A         N/A
 Ethernet32      41,42,43,44     100G   9100   hundredGigE9   trunk    down       up              N/A         N/A
 Ethernet36      33,34,35,36     100G   9100  hundredGigE10   trunk    down       up              N/A         N/A
 Ethernet40      49,50,51,52     100G   9100  hundredGigE11   trunk    down       up              N/A         N/A
 Ethernet44      57,58,59,60     100G   9100  hundredGigE12   trunk    down       up              N/A         N/A

I am expecting Ethernet0 to say untagged or something similar but it still says trunk. Not entirely sure what is wrong.

Also I know under "Oper" that it says down, this is not the reason for no traffic getting through this is a non production switch. The others are currently being used and I do not want to mess with them right now.

Thanks.

[prsunny]

'show int status' is currently limited to only show 'trunk' if the port is member of vlan. it doesn't differentiate between 'tagged' or 'untagged'. It is challenging here if the port is 'untagged' in one vlan but 'tagged' in other vlans. Do you want to try to fix this?

[pollyhsu2git]

@titanlock
For any issue report, to provide more info would be helpful for the community member to target your issue correctly as SONiC is being revised every day via the contribution around the globe.

1. The image version info, syslog... e.g.
2. The procedures to reproduce your issue

[titanlock]

Here is the version:

SONiC Software Version: SONiC.master.0-dirty-20190917.135340
Distribution: Debian 9.11
Kernel: 4.9.0-9-2-amd64
Build commit: a62ab789
Build date: Tue Sep 17 18:48:53 UTC 2019
Built by: opnfv@sanic

Platform: x86_64-accton_as7816_64x-r0
HwSKU: Accton-AS7816-64X
ASIC: broadcom
Serial Number: 781664X1913005
Uptime: 05:26:32 up 1 day,  1:58,  1 user,  load average: 1.18, 1.33, 1.45

Docker images:
REPOSITORY                 TAG                              IMAGE ID            SIZE
docker-syncd-brcm          latest                           986dc56543e3        392MB
docker-syncd-brcm          master.0-dirty-20190917.135340   986dc56543e3        392MB
docker-fpm-frr             latest                           ae1ce79e3a9e        319MB
docker-fpm-frr             master.0-dirty-20190917.135340   ae1ce79e3a9e        319MB
docker-lldp-sv2            latest                           601f2ec15316        298MB
docker-lldp-sv2            master.0-dirty-20190917.135340   601f2ec15316        298MB
docker-dhcp-relay          latest                           b1a05d9ec50c        289MB
docker-dhcp-relay          master.0-dirty-20190917.135340   b1a05d9ec50c        289MB
docker-database            latest                           222c94f4656e        281MB
docker-database            master.0-dirty-20190917.135340   222c94f4656e        281MB
docker-snmp-sv2            latest                           38c6edb90437        334MB
docker-snmp-sv2            master.0-dirty-20190917.135340   38c6edb90437        334MB
docker-orchagent           latest                           fc47a59bc228        321MB
docker-orchagent           master.0-dirty-20190917.135340   fc47a59bc228        321MB
docker-sflow               latest                           ec6b61903b56        303MB
docker-sflow               master.0-dirty-20190917.135340   ec6b61903b56        303MB
docker-teamd               latest                           82f07268922c        302MB
docker-teamd               master.0-dirty-20190917.135340   82f07268922c        302MB
docker-sonic-telemetry     latest                           61c0839059b4        304MB
docker-sonic-telemetry     master.0-dirty-20190917.135340   61c0839059b4        304MB
docker-router-advertiser   latest                           5b2e854c8316        281MB
docker-router-advertiser   master.0-dirty-20190917.135340   5b2e854c8316        281MB
docker-platform-monitor    latest                           2010479446c5        326MB
docker-platform-monitor    master.0-dirty-20190917.135340   2010479446c5        326MB

To reproduce, try to setup a port to be untagged on an AS7816-64X and see if you can get traffic to go through that port on an external machine connected to it that is not tagged at all.

[pollyhsu2git]

@titanlock
Again, the build of 2019-09-17, commit ID: a62ab789 had the BUILD FAILURE (https://sonic-jenkins.westus2.cloudapp.azure.com/job/broadcom/job/buildimage-brcm-all/82).
We'll suggest you to choose another PASSed one to try.

[titanlock]

So we were able to find a workaround this issues, in the config_db.json file we had to remove the interface we wanted to be untagged from the BGP_NEIGHBOR and the INTERFACE sections of the file. After applying theses changes traffic was able to go through the ports as an untagged VLAN.

Now this issue can technically be closed but this is still an issue in the code, I know there is an issue with the Broadcom platform right now from here: sonic-net/sonic-buildimage#3508. So I think there should be more attention to getting Broadcom fully functional again instead of using all of these workarounds.