EasyManua.ls Logo

Calix E3-48C - Page 29

Calix E3-48C
225 pages
To Next Page IconTo Next Page
To Next Page IconTo Next Page
To Previous Page IconTo Previous Page
To Previous Page IconTo Previous Page
Loading...
29
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
You can configure only one of the following attributes on a given VLAN on a given
interface:
Trunk interfaces:
VLAN member
Native VLAN
Edge interfaces:
VLAN member
Tag-action
Native VLAN
Access interfaces:
VLAN member
Tag-action
Trunk and Edge interfaces are always associated with at least one VLAN, through the
native VLAN attribute (VLAN 1, by default). Access interfaces do not support a Native
VLAN, however, tag actions can be used to assign untagged traffic to a VLAN ID.
All network connections (ERPS, RSTP, LAG, DHCP servers, multicast routers, IGMP-
enabled video servers, network-facing routers) are made on Trunk or Edge interfaces,
only.
Interfaces can be associated with additional VLANs through memberships or tag-actions.
If an Ethernet uplink Edge interface with tag actions (for double-tagged traffic) is on the
same card as Ethernet downlink Edge interfaces (that are members of the outer VLAN),
ingress double-tagged traffic from the downlink ports will not flow upstream, resulting in
a service interruption. As a workaround, for this application, ensure that one of the
following configurations are used:
The Ethernet uplink Edge port is on a different card than downlink Edge ports.
Ethernet downlink ports are configured with the Trunk interface role.
Note: For this application, if active/standby LAG is used for the uplink, you must
ensure that Ethernet downlink ports are configured with the Trunk role.
When a VLAN has DHCP snooping and Option 82 relay enabled, an Ethernet interface
can be directly added to the VLAN membership, but using a tag action to associate an
Ethernet interface to such a VLAN is not supported.
BPDU Guard and RSTP cannot be enabled on an interface, simultaneously.
For Policy maps:
For Trunk interfaces, any policy map assignment is allowed.
For Edge and Access interfaces, if a policy map contains a two-tag classification, the
edge or access link must have a tag-action that adds the outer tag being matched by
the class rule.

Table of Contents

Related product manuals