Bridge Groups¶
The Local Manager can be configured with bridge groups. A bridge group is a virtual switch. All traffic that comes in the bridge is then forwarded to other ports. In this simple mode, the Local Manager doesn't need an IPv4 or IPv6 address defined, just a list of interface names to include in the bridge group.
Requirement¶
This feature requires a dedicated Ethernet card to function.
Usage Notes¶
While many uses of bridge groups do not require an IP address configured, to support Cisco switch stacks and other features, it is necessary to supply an IPv4 address to the bridge group.
The Terminal application’s ~t (TFP), ~f (FTP), ~g (SCP/SFTP) functions work with bridge groups.
The show info command on a port shows the related bridge group IP for the dedicated Ethernet interface.
When a dedicated Ethernet interface is in a bridge group, you cannot set the device's IP, but you can set the speed duplex settings in config info.
Since a bridge group applies to multiple interfaces, the Local Manager doesn't know what IP was assigned to a device connected to a particular interface (or even if the device has a static IP), then certain advanced driver functionality (ex. ROMMON recovery) does not work as they were written to set the IP of the device before requesting data over TFTP/FTP/SCP. Advanced drivers running in non-ROMMON mode should be able to use the existing TFTP/FTP/SCP fine though.
Configuring Bridge Groups¶
A bridge group can be configured using the config system bridgegroup <bridge group name> command.
[admin@LantronixLM]# config system bridgegroup one
Bridge one does not exist. Create (y/n): y
Warning: Remote connections may be lost if you commit changes.
[config bridgegroup one]#
Once in the editor you can use the ? command to view a list of the possible options.
[config bridgegroup one]# ?
Allowable arguments are:
show
[no] description <description>
[no] dhcp-server
[no] interface <Ethernet x/y>
[no] ip <IPv4>
[no] ipv6 <IPv6>
or 'exit' to quit config mode
[config bridgegroup one]# dhcp-server
[config bridgegroup one dhcp-server]# ?
Allowable arguments are:
show
[no] pool <IP start> <IP end>
[no] dns <IP>+
[no] gateway <IP>
[no] ntp <IP>+
[no] search <domain.example.com>+
[no] ttl [60 - 86400]
or 'exit' to quit config mode
Viewing Bridge Groups¶
You can view bridge groups and any DHCP leases the bridge group currently has using the show system bridgegroup <bridge group name> | * command.
[super@A600000111]# show system bridgegroup two
name two
ip 10.10.10.1/24
ipv6 fde4:12d9:b4cc::5/64
interface Ethernet2/4
interface Ethernet2/7
interface Ethernet3/3
interface Ethernet3/8
dhcp-server
pool 10.10.10.100 10.10.10.200
gateway 10.10.10.254
exit
# 10.10.10.176 00:0f:2c:01:83:f5 A600000202-E2 expires 03/01/2024 15:26:38 CST
# 10.10.10.153 00:0f:2c:00:ca:0d A400100005 expires 03/01/2024 15:21:52 CST
Importing and Exporting Bridge Group Settings¶
The bridge group settings can be imported and exported with config import and config export.
Control Center¶
The settings are sent to the Control Center where they can be viewed (Network -> Bridge Groups). While bridge groups cannot edited or created from the Control Center, individual bridge groups can be deleted from the Control Center. All bridge groups will be restored to a factory reset Local Manager when pointed back to the Control Center. If a Local Manager is replaced on the Control Center, its bridge groups will be copied to the new Local Manager.