
Differences From Prior Releases of EQ/OS
The following are differences from previous versions of EQ/OS:
New Command Line Interface
The Equalizer Command Line Interface, CLI, gives you complete administrative control over Equalizer and is one
of the major new features in EQ/OS 10. The GUI is also available to view and modify the configuration, however,
not all administrative options have been enabled in the GUI.
“eqadmin” Console Command No Longer Supported
All of the functionality that was available in previous releases using the eqadmin console command is now
provided in the CLI.
No Default Match Rules
In previous releases, some cluster flags and options appeared both in the cluster configuration screens and in a
“Default” match rule that could not be changed. In EQ/OS 10, there are no Default match rules. All cluster flags and
options are set in the cluster context, and match rules are only needed if you want to override one or more of the
options set in the cluster context. Otherwise, match rule processing occurs in the same fashion as in previous
releases.
Load Balancing Policy Specified on Server Pools
In version 8.6, you can use a match rule to select a new load balancing policy. This works differently in EQ OS 10
because of the re-architecture of server pools. In EQ/OS 10, the load balancing policy is specified on a server pool,
and a server pool is attached to a match rule. If you want to assign a different load balancing policy on a match
rule, you can create a different server pool with a different policy and attach that server pool to the match rule.
Capability of Adding Responders to Clusters
A responder can now be added directly to a cluster; this responder is used if none of the servers in the server pool
specified in the cluster context are available. Responders cannot be added to match rules, as in previous releases.
VLANs and Subnets
In previous releases, only one subnet was permitted in a VLAN. In EQ/OS 10, multiple subnets can be assigned to
a single VLAN.
VLAN/Subnet Routing
In previous releases, VLAN traffic was forwarded between ports by default. For example, if a packet tagged for
VLAN_2 arrived on a port configured only for VLAN_1, the packet for VLAN_2 would be forwarded to other ports
instead of being dropped. In EQ/OS 10, packet forwarding between VLANs is disabled by default, and must be
enabled by adding entries to the “permit” list for the appropriate VLAN subnets.
Servers Are Now Global Objects
In previous releases,
servers
were defined directly within
clusters
. In EQ/OS 10, servers are global objects in the
object tree (as displayed in the left navigational pane of the GUI interface) and are associated with clusters via
server pools
.
Server pools
are new in EQ/OS 10 and are also global objects in the tree. In general, you create
objects in this order:
Copyright © 2013 Coyote Point Systems. A subsidiary of Fortinet, Inc.
All Rights Reserved.
25
Equalizer Administration Guide
Kommentare zu diesen Handbüchern