27
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
Interface roles
Each GE and 10GE interface in the system has one of the following configuration-role
types:
Trunk: A port connecting to other equipment belonging to the service provider or to
another service domain with consistent VLAN tagging levels. These ports may also be
referred to as Network ports or Provider ports in industry standards. These ports support
outer VLAN tag plus MAC switching.
Examples of trunk ports are 10G ERPS transport ports and GE uplinks. Trunk ports can be
configured for link aggregation, RSTP, or ERPS. To properly process ingress double tags, the
GE network interface (uplink) must be configured as a Trunk role.
Edge: A port facing customer equipment or facing reduced functionality devices, alternative
administrative domains, or managed CPE. Generally, this E-Series Ethernet port interface is
where all classification is first performed on ingress traffic (if customer facing). The E-Series
Ethernet interface is also expected to add, replace, or remove one or more VLAN tags on
edge traffic. RSTP and LAG networking protocols are supported.
Examples of an edge port would include GE ports to managed CPE, a GE/10GE port to
external equipment which may use different tagging levels, or GPON ports.
Access: A port facing untrusted customer equipment or other devices serving subscribers.
Generally, this port interface is where individual subscriber services are defined and enforced
(bandwidth limits, security, multicast profiles). Networking protocols are not supported.
Examples of an access port would be point-to-point connections to subscribers or other
devices serving subscribers.
VLAN support
By default, every Ethernet port with a trunk or edge interface on the unit is a member of
VLAN 1, the Native VLAN. The Native VLAN is available to pass any untagged traffic. You
can provision an Ethernet port interface to use a different existing VLAN as the Native
VLAN.
To forward untagged traffic on Ethernet ports with an access interface, an add-tag action
must be applied to untagged frames, assigning the traffic to a designated VLAN.
Tagged traffic that does not match any of the tagging criteria is dropped.
For modular chassis nodes, any VLAN created on the system is automatically mapped to the
Stacking Ports. The remaining port interfaces in the system must be a VLAN member for
traffic to pass on the VLAN through the interface.
To Next Page
Loading...
Need help?
General
