Znyx Networks bh5700 Manual Do Utilizador
Coordination between the data and fabric switches can be enabled by setting the
board_synchronization_mode. Possible modes are “off” and “basic”. Board
synchronization is off by default. When board synchronization is put into basic mode, HA events
on the base switch are coordinated with the HA events on the fabric switch. The behavior of
board synchronization is dependent on the failover_mode. In switch failover_mode all VLANs
are moved to the HA partner with the most up links in unison. With board synchronization the
concept is extended so that all VLANs in both switching planes are moved to the HA partner with
the most up links in both switch planes. So, both switches failover together. In vlan and port
failover modes the number of up links is not considered in the board synchronization. Each vlan
or port can move independently across the data or fabric planes between HA partners according
to the failover_mode rules. In all failover_modes, if the data plane or fabric switch reboots or
power cycles, the HA partner will take mastership for all VLANs in both planes. The syntax for
setting the board_synchronization_mode is:
board_synchronization_mode. Possible modes are “off” and “basic”. Board
synchronization is off by default. When board synchronization is put into basic mode, HA events
on the base switch are coordinated with the HA events on the fabric switch. The behavior of
board synchronization is dependent on the failover_mode. In switch failover_mode all VLANs
are moved to the HA partner with the most up links in unison. With board synchronization the
concept is extended so that all VLANs in both switching planes are moved to the HA partner with
the most up links in both switch planes. So, both switches failover together. In vlan and port
failover modes the number of up links is not considered in the board synchronization. Each vlan
or port can move independently across the data or fabric planes between HA partners according
to the failover_mode rules. In all failover_modes, if the data plane or fabric switch reboots or
power cycles, the HA partner will take mastership for all VLANs in both planes. The syntax for
setting the board_synchronization_mode is:
board_synchronization_mode:
basic;
Additional startup scripts may be included in the configuration using the start_script
command. The files in the start_script command will be placed in a location for tftp
transfer to sibling switches that initialize using the –u option. A common use of the
start_script command might be to propagate gated configurations to all members of the
Surviving Partner group. Absolute path names must be used. Using multiple commands allows
inclusion of multiple scripts. For example:
command. The files in the start_script command will be placed in a location for tftp
transfer to sibling switches that initialize using the –u option. A common use of the
start_script command might be to propagate gated configurations to all members of the
Surviving Partner group. Absolute path names must be used. Using multiple commands allows
inclusion of multiple scripts. For example:
start_script: /etc/rcZ.d/S75gated;
start_script: /etc/rcZ.d/S80static_routes;
start_script: /etc/rcZ.d/S80static_routes;
The vrrpd_script command allows a user defined script to be run when vrrpd changes
state. This script is called at the end of the zspconfig created vrrpd.script. See vrrpd –s
for a description of when the scripts are called. zspconfig sets up vrrpd to call vrrpd.script.
The vrrpd_script command in zspconfig places a call to the user-defined script at the
end of vrrpd.script file. The following example would call the my_vrrpd_script each
time vrrpd calls its –s provided script:
state. This script is called at the end of the zspconfig created vrrpd.script. See vrrpd –s
for a description of when the scripts are called. zspconfig sets up vrrpd to call vrrpd.script.
The vrrpd_script command in zspconfig places a call to the user-defined script at the
end of vrrpd.script file. The following example would call the my_vrrpd_script each
time vrrpd calls its –s provided script:
vrrpd_script: /etc/rcZ.d/surviving_partner/my_vrrpd_script;
CAUTION: The my_vrrpd_script is not called from a different process thread.
Therefore if my_vrrpd_script crashes or has long delays, it will crash the vrrpd, or
cause delays in the Surviving Partner failover. To protect against this, write the script to
launch a second script in a background shell. The advantage to calling the user provided
script in the same process thread is that it gives synchronized control over the failover
process for those who want it.
Therefore if my_vrrpd_script crashes or has long delays, it will crash the vrrpd, or
cause delays in the Surviving Partner failover. To protect against this, write the script to
launch a second script in a background shell. The advantage to calling the user provided
script in the same process thread is that it gives synchronized control over the failover
process for those who want it.
OUTPUT FILES
The output of zspconfig is a set of configuration and script files. The configuration files
configure vrrpd and zlmd daemons. The vrrpd and zlmd daemons combined with the script
configure vrrpd and zlmd daemons. The vrrpd and zlmd daemons combined with the script
Ethernet Switch Blade User's Guide
release 3.2.2j
page 333