EQ/OS 8.6 to EQ/OS 10.0 Configuration Converter
Object Names Affected by Configuration Migration
In EQ/OS 8.6, each cluster is assigned its own servers. In EQ/OS 10, servers are global objects.
When migrated, server names are contrived using the cluster name and server name to avoid
having duplicates.
Note
- It should be noted that EQ/OS 8.6 object names in excess of 47 characters will be truncated and appended with
"
_XXX
". "
XXX
" is a number that starts with 000 and will increment. For example, two server instances may be
appended with
_000
and
_001
.
The following are examples of the name changes. If the EQ/OS 8.6 configuration was:
cluster cl00
>>
server sv00
The resulting cluster-server name in the configuration in EQ/OS 10 will be:
server cl00_sv00
EQ/OS 10 uses Server Pools that contain Server Instances. When migrating to EQ/OS 10 a Server
Pool will be created using the cluster-server details described. A server instance (
si
) will be
created for the new EQ/OS 10 server and assigned to a new cluster. For example:
A server pool (
srvpl
) is created with a new server instance (
si
):
srvpl cl00
>>
si cl00_sv00
A new cluster is created with the new server pool attached:
cluster cl00
>>
srvpl cl00
However, if there are duplicate servers shared between clusters in the EQ/OS 8.6 configuration,
there will be a configuration where we use the name of the first cluster in which it appears, and
there is a mismatch between the server name and the cluster name:
If the configuration in EQ/OS 8.6 was:
cluster cl00
>>
server sv00 (1.2.3.4 80
)
cluster cl01
>>
server sv01 (1.2.3.4 80)
The resultant EQ/OS 10 configuration will be:
server cl00_sv00
(Note only one server)
srvpl cl00
>>
si cl00_sv00
srvpl cl01
>>
si cl00_sv00
(Note the mismatch)
cluster cl00
>>
srvpl cl00
cluster cl01
>>
srvpl cl01
4
Copyright © 2015 Coyote Point Systems, A Subsidiary of Fortinet, Inc.
