Znyx Networks bh5700 Manual Do Utilizador
interconnect, it is not a bonding driver enabled port, and therefore should be setup as an
interconnect port type. To accomplish this, the zre ports are listed to avoid conflicting port
types.
interconnect port type. To accomplish this, the zre ports are listed to avoid conflicting port
types.
Note that a single line cannot contain both zhp and zre definitions. Therefore
RAINlink: zhp1, zre1..4
does not work and the definition zre1..8 is equivalent.
Optional zspconfig commands are listed below.
vrrp_msg_rate: 100; # Time in milliseconds.
# Default is 100 milliseconds
The message rate is the interval between VRRP messages sent over the interconnect link. The
time given is in milliseconds. It takes the lack of 3 VRRP messages for the Backup to assume the
role as Master. It is recommended with faster message rates to increase the default priority to
254. The higher priority will decrease the latency of the failover.
time given is in milliseconds. It takes the lack of 3 VRRP messages for the Backup to assume the
role as Master. It is recommended with faster message rates to increase the default priority to
254. The higher priority will decrease the latency of the failover.
vrrp_def_priority: 254; # default is 100.
Value from 1 to 254
The default virtual MAC address for VRRP is 00:00:5E:00:01:<vid>, where <vid> the
virtual router ID. Using this virtual address is problematic in network environments where
multiple VRRP instances might be running that are using the same <vid>. To overcome this
problem, zspconfig, uses a default MAC address derived from the physical address of the
switch on which it is running. For the slave switch, the vrrp_virtual_mac_addr command
is used to set the MAC address to the same as the Master. This statement is typically not used
within the Master switch’s configuration. It is used in the zspconfig generated Slave switch
configuration. And is retrieved by the Slave switch with zspconfig using the –u option. If in
doubt, don’t use this command.
virtual router ID. Using this virtual address is problematic in network environments where
multiple VRRP instances might be running that are using the same <vid>. To overcome this
problem, zspconfig, uses a default MAC address derived from the physical address of the
switch on which it is running. For the slave switch, the vrrp_virtual_mac_addr command
is used to set the MAC address to the same as the Master. This statement is typically not used
within the Master switch’s configuration. It is used in the zspconfig generated Slave switch
configuration. And is retrieved by the Slave switch with zspconfig using the –u option. If in
doubt, don’t use this command.
vrrp_virtual_mac_addr: 00:01:02:03:04:05
There are three failover_modes supported; switch, vlan and port. For switch failover,
if any managed link fails, the entire switch is failed over to the backup switch. In vlan failover,
if a link fails in a VLAN, only the links associated with that VLAN are failed over. In port
failover, only the port that fails is moved to the backup switch. For both vlan and port
failover, the interconnect link will need to be used to maintain connectivity between ports that
have failed over and those that have not. For vlan and port failover modes, the interconnect
link must be an in-band port, and must be included in the managed VLANs running with VLAN
tagging on.
if any managed link fails, the entire switch is failed over to the backup switch. In vlan failover,
if a link fails in a VLAN, only the links associated with that VLAN are failed over. In port
failover, only the port that fails is moved to the backup switch. For both vlan and port
failover, the interconnect link will need to be used to maintain connectivity between ports that
have failed over and those that have not. For vlan and port failover modes, the interconnect
link must be an in-band port, and must be included in the managed VLANs running with VLAN
tagging on.
failover_mode: switch;
failover_mode: vlan;
failover_mode: port;
failover_mode: port;
Ethernet Switch Blade User's Guide
release 3.2.2j
page 332