Znyx Networks bh5700 사용자 설명서
monitor_only - Ports that are monitored but do not have a virtual address managed on them.
They will not have their links brought down temporarily during a failover scenario. These
ports are only monitored. If a problem occurs on this type of link it will cause a failover
scenario.
They will not have their links brought down temporarily during a failover scenario. These
ports are only monitored. If a problem occurs on this type of link it will cause a failover
scenario.
configure_only - Ports are configured as per the zconfig commands, but do not participate
in the high availability network. Problems on these links will not cause a switch failover.
in the high availability network. Problems on these links will not cause a switch failover.
NOTE: The zhp specified for interconnect is important, and will be the zhp
interface/VLAN where zspconfig/HA on the the master will start the DHCP daemon.
Zre51 on the slave swtiches should be configured up into this same VLAN so that
zspconfig -u can connect to the master.
interface/VLAN where zspconfig/HA on the the master will start the DHCP daemon.
Zre51 on the slave swtiches should be configured up into this same VLAN so that
zspconfig -u can connect to the master.
Each port that is setup in a VLAN by the zconfig commands must have its port type specified.
The port type is specified on a physical port bases. That is on a zre basis, but zhp names can be
used as a quick way to setup the port type for all ports that are a member of that VLAN. It is
possible to make a port a member of more then one VLAN. That is a zre can be a member of
more then one zhp. In such cases, configuring the zhps as different port types would cause a
conflict, and will not work. To handle this setup the individual zre commands would be used to
setup the port types. Here is an example of setting up the port types as a continuation of our
current configuration:
The port type is specified on a physical port bases. That is on a zre basis, but zhp names can be
used as a quick way to setup the port type for all ports that are a member of that VLAN. It is
possible to make a port a member of more then one VLAN. That is a zre can be a member of
more then one zhp. In such cases, configuring the zhps as different port types would cause a
conflict, and will not work. To handle this setup the individual zre commands would be used to
setup the port types. Here is an example of setting up the port types as a continuation of our
current configuration:
interconnect:
zhp2; # Could also use zre14
rain link: zhp0, zhp1;
# Could also use zhp0..1,
# or list the zres
The ".." wild card is supported as in zconfig to indicate a range of numbers. The comma is
used to indicate a list. The zres that are part of the zhp could also be used. Here is a more
complex setup. The zconfig commands are also shown to understand the VLAN setup:
used to indicate a list. The zres that are part of the zhp could also be used. Here is a more
complex setup. The zconfig commands are also shown to understand the VLAN setup:
zconfig zhp0: vlan1 = zre1..4, zre23;
zconfig zhp1: vlan2 = zre5..8, zre23;
zconfig zhp1: vlan2 = zre5..8, zre23;
zconfig zhp100: vlan100 = zre23;
zconfig zhp0: vlan1 = zre1..4;
zconfig zhp1: vlan2 = zre5..8;
zconfig zhp1: vlan2 = zre5..8;
zconfig zhp2: vlan100 = zre23;
# sibling and virtual address setup omitted
interconnect:
zhp100;
rain link: zre1..8;
# Use zre definition to
# exclude zre23
If zhp0 and zhp100 are setup as different port types, there would be a conflict for port zre23.
In the particular example above, the zre23 is shared. It is used to pass VRRP interconnect
traffic and as a means to pass VLAN 1 and 2 traffic between switches. Since zre23 is an
In the particular example above, the zre23 is shared. It is used to pass VRRP interconnect
traffic and as a means to pass VLAN 1 and 2 traffic between switches. Since zre23 is an
Ethernet Switch Blade User's Guide
release 3.2.2j
page 249