Native VLAN
Starting in Juniper Cloud-Native Router Release 23.1, JCNR supports receiving and forwarding untagged packets on a trunk interface. Typically, trunk ports accept only tagged packets, and the untagged packets are dropped. You can enable a JCNR fabric trunk port to accept untagged packets by configuring a native VLAN identifier (ID) on the interface on which you want the untagged packets to be received. When a JCNR fabric trunk port is enabled to accept untagged packets, such packets are forwarded in the native VLAN domain.
Native VLAN
Enable the native-vlan-id key in the Helm chart, at the time of
deployment, to configure the VLAN identifier and associate it with untagged data packets
received on the fabric trunk interface. Edit the values.yaml file in
Juniper_Cloud_Native_Router_<release-number>/helmchart
directory and add the key native-vlan-id along with a value for it. For
example:
fabricInterface:
- eth1:
ddp: on
interface_mode: trunk
vlan-id-list: [100, 200, 300, 700-705]
storm-control-profile: rate_limit_pf1
native-vlan-id: 100
no-local-switching: trueAfter editing the values.yaml file, you have to install or upgrade
JCNR using the edited values.yaml to ensure that the
native-vlan-id key is enabled.
To verify, if native VLAN is enabled for an interface, connect to the vRouter agent by
executing the command kubectl exec -it -n contrail
contrail-vrouter-<agent container> -- bash command,
and then run the command vif --get <interface index
id>. A sample output is shown below:
vif0/1 PCI: 0000:00:00.0 (Speed 10000, Duplex 1)
Type:Physical HWaddr:6a:45:b2:a8:ce:5c
Vrf:0 Flags:L2Vof QOS:-1 Ref:11
RX port packets:36550 errors:0
RX queue packets:36550 errors:0
RX queue errors to lcore 0 0 0 0 0 0 0 0 0 0 0 0 0 0
Fabric Interface: eth_bond_bond0 Status: UP Driver: net_bonding
Slave Interface(0): 0000:3b:02.0 Status: UP Driver: net_iavf
Vlan Mode: Trunk Vlan: 100 200 300
Native vlan id: 100
RX packets:36550 bytes:5875795 errors:0
TX packets:0 bytes:0 errors:0
Drops:613