...
| Note |
|---|
Make sure not to include the cascade-ports and control-ports in any routing or bridging configurations. These ports are recommended only for a CB and PE usage. |
Packet flow and forwarding
ETAG usage, packet flooding (broadcast, multicast, unicast), unicast forwarding, learning.
Controller Bridge settings and monitoring
...
Property | Description |
|---|---|
| device (name) | Automatically assigned PE device name. |
| name (name) | Automatically assigned PE port name. |
| pcid (integer) | Automatically assigned port identifier. |
| port-status (dev-inactive | not-added | ok) | PE port status. |
| rate (bps) | Data rate of the connection. |
| status (link-ok | no-link | unknown) | PE port link status. |
...
| . |
Port Extender settings
This section describes the Port Extender settings.
Sub-menu: /interface bridge port-extender
Property | Description |
|---|---|
| control-ports (interfaces; Default: none) | Interfaces that will either connect to the CB (upstream port) or connect other PE devices in series (cascade port). A bonding interface with 802.3ad or balance-xor mode is also supported. |
| excluded-ports (interfaces; Default: none) | Interfaces that will not be extended. |
| switch (name; Default: none) | The switch that will act as the extender and ensure the control and network traffic. The PE will only enable when this property is specified, otherwise, it will be in a disabled state. |
Limitations
Known limitation (e.g. only single CB possible, ingress-filtering on extended ports) and recommendations (e.g use control/cascade ports only for communication between CB and PE, do not use these ports for bridging or routing)
Examples
...