...
Property | Description |
---|---|
bridge (name; Default: none) | The bridge interface where ports will be extended. The Controller Bridge will only enable when bridge and switch properties are specified. |
cascade-ports (interfaces; Default: none) | Interfaces that will act as cascade ports. |
switch (name; Default: none) | The switch that will act as the CB and ensure the control and network traffic. The Controller Bridge will only enable when bridge and switch properties are specified. |
After CB and PE devices are configured and connected, each PE device will be automatically visible on the device menu, use print
and monitor
commands to see more details.
Code Block | ||
---|---|---|
| ||
[admin@Controller] > interface bridge port-controller device print Flags: I - inactive 0 name="pe1" pe-mac=64:D1:54:EB:AE:BC descr="MikroTik RouterOS 6.48beta35 (testing) CRS328-24P-4S+" control-ports=pe1-sfpplus1,pe1-sfpplus2 1 name="pe2" pe-mac=64:D1:54:C7:3A:58 descr="MikroTik RouterOS 6.48beta35 (testing) CRS326-24G-2S+" control-ports=pe2-sfpplus1 [admin@Controller] > interface bridge port-controller device monitor pe2 name: pe2 status: active connected-via-ports: sfp-sfpplus1==pe1-sfpplus1,pe1-sfpplus2==pe2-sfpplus1 connected-via-devs: controller,pe1 |
Sub-menu: /interface bridge port-controller device
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. |
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. |
status (active | inactive) | PE device status. |
Additionally, each PE device port can be monitored on the port menu, use print
and monitor
commands to see more details.
Code Block | ||
---|---|---|
| ||
[admin@Controller] > interface bridge port-controller port print where !disabled
Flags: I - inactive, X - disabled, R - running, U - upstream-port, C - cascade-port
# NAME DEVICE
0 I pe1-ether1 pe1
1 R pe1-ether2 pe1
2 R pe1-ether3 pe1
3 R pe1-ether4 pe1
4 U pe1-sfpplus1 pe1
5 RC pe1-sfpplus2 pe1
6 I pe2-ether1 pe2
7 R pe2-ether2 pe2
8 R pe2-ether3 pe2
9 R pe2-ether4 pe2
10 U pe2-sfpplus1 pe2
[admin@Controller] > interface bridge port-controller port monitor [find where !disabled]
name: pe1-ether1 pe1-ether2 pe1-ether3 pe1-ether4 pe1-sfpplus1 pe1-sfpplus2 pe2-ether1 pe2-ether2 pe2-ether3 pe2-ether4 pe2-sfpplus1
status: unknown link-ok link-ok link-ok no-link link-ok unknown link-ok link-ok link-ok no-link
rate: 1Gbps 1Gbps 1Gbps 10Gbps 10Gbps 1Gbps 1Gbps 1Gbps 10Gbps
port-status: not-added ok ok ok ok ok not-added ok ok ok ok
pcid: 457 458 459 480 481 509 510 511 532 |
Sub-menu: /interface bridge port-controller port
Print:
Property | Description | Property | Description
---|---|---|
device (name) | Automatically assigned PE device name. name | (name)Automatically assigned PE port name. |
Monitor:
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.
...