39
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
Configuration guidelines
Follow these guidelines when configuring an Ethernet port interface or LAG interface:
An Ethernet interface always exists, cannot be deleted, can be modified, and is associated
with a specific companion Ethernet port (GE or 10GE).
A LAG interface can be created, deleted, and modified.
A port is always a member of exactly one interface, even when it is being used in a
standalone manner.
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.
