Versions Compared

Key

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

...

ETAG usage, packet flooding (broadcast, multicast, unicast), unicast forwarding, learning.

Controller Bridge settings and monitoring

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 CB and ensure the control and network traffic

Sub-menu: /interface bridge port-controller device

Print:


Property

Description

control-ports (interfaces)PE device control ports.
descr (name)Short PE device description.
name (name)Automatically assigned PE device name.
pe-mac (MAC address)PE device MAC address.

Monitor:

Property

Description

connected-via-devs (name)Shows the connected devices from PE to CB. 
connected-via-ports (name)Shows the PE device connection path from PE to CB.
name (name)Automatically assigned PE device name.
status (active | inactive)PE device status.

Sub-menu: /interface bridge port-controller port

Print:


Property

Description

device (name)Automatically assigned PE device name.
name (name)Automatically assigned PE port name.

Monitor:

Property

Description

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.



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.

...