Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Controller Bridge settings

Sub-menu: /interface bridge port-controller

Property

Description

bridge (name; Default: none)The bridge interface where ports will be extended.
cascade-ports (interfaces; Default: none)Interfaces that will act as cascade ports.
switch (name; Default: none)The switch that will act as the controller and ensure the control and network traffic. 

List of available configuration properties, monitoring options. Neighbor discovery changes (how PE and CB discover each other using LLDP TLVs, on PE control-ports discovery is automatically enabled and disabled on extended ports (they get controlled by the CB settings), on CB cascade ports discovery is automatically enabled), automatic bridge port configuration, how to apply and remove (device remove, port remove, other settings where an extended interface is configured will stay and should be removed manually) the configuration for extender ports (PE can even be disconnected and still apply configuration on CB), extended port naming, ECP protocol for control information between PE and CB.

Port Extender settings

Similar as CBSub-menu: /interface bridge port-extender

Property

Description

control-ports (interfaces; Default: none)Interfaces that will either connect to the CB (an upstream port) or connect other PE devices in series (a cascade port).
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.

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)

...