Znyx Networks bh5700 manual Ethernet Switch Blade Users Guide Release 3.2.2j

A sibling_addresses statement is required for each VLAN created with the zconfig commands. The two addresses in the list indicate there are two switches in the Surviving Partner group. The first address 10.0.0.30 and 11.0.0.30 are assigned to the switch on which the configuration is being run. The remaining addresses are distributed to the switches that run zspconfig -uon a first come, first serve basis.

The sibling_addresses command may also take a netmask operand similar to that given to ifconfig. For example:

sibling_addresses: zhp0 = 10.0.0.30, 10.0.0.31 netmask 255.255.255.0;

sibling_addresses: zhp1 = 11.0.0.30, 11.0.0.31 netmask 255.255.255.0;

Virtual addresses should be setup for all VLANs that connect to High Availability nodes. Usually this would include all VLANs except the interconnect VLAN or VLANs connected to upstream routers. It is possible that a setup would have VLANs that are used for management only. Virtual addresses are setup as follows:

virtual_address: zhp0 = 10.0.0.42 netmask 255.255.255.0;

virtual_address: zhp1 = 11.0.0.42 netmask 255.255.255.0;

Only a single address per VLAN is provided because this single address will move with the current Master switch, and the netmask must be the same as that provided in the sibling_addresses statement.

The last required section for the configuration is description of the ports. Particularly we need to specify one of the following for all of the ports participating in the high availability setup. The possible port types are:

interconnect - Ports connected between groups of Surviving Partner switches. VRRP heartbeat messages are sent on the interconnect ports.

Crossconnect - Crossconnect ports are ports that are connected to other Surviving Partner switches, that are not part of this Surviving Partner group. Crossconnect ports behave differently then bonding ports. The links are not brought down temporarily, and VRRP runs with the native MAC addresses to avoid MAC address duplication with the other VRRP group.

RAINlink - Ports connected to RAINLink or bonding driver nodes. These ports contain virtual addresses managed by VRRP. And during a failover event, the links are toggled down to force failover to the Master switch.

Route - Ports connected to upstream routers. VRRP does not manage virtual IP addresses for these links. Routing protocols must be used to instruct up stream routers of a different path to get to the VRRP managed networks. These port types are currently not implemented.

Ethernet Switch Blade User's Guide release 3.2.2j page 330