Important Notes on SOLIDserver v7.

1
Copyright © 2000-2019 EfficientIP

All specifications and information regarding the products in this document are subject to
change without notice and should not be construed as a commitment by EfficientIP. Efficien-
tIP assumes no responsibility or liability for any mistakes or inaccuracies that may appear
in this document. All statements and recommendations in this document are believed to be
accurate but are presented without warranty. Users must take full responsibility for their
application of any product.
June 28, 2019

The following is a PDF version of the Important Notes on SOLIDserver 7.1, available on EfficientIP
Knowledge Base at https://kb.efficientip.com/index.php/Important_Notes_on_Version_7.1.

This document gathers a set of important notes and changes listed by module and use that might
come in handy if you are contemplating a migration from your current version of SOLIDserver
to version 7.1.

If you are upgrading appliances from a version 5.0.4.x, please also refer to the Important
Notes on Version 6.0.0 and 6.0.1 at https://downloads.efficientip.com/support/downloads/docs/.

If you are upgrading appliances from a version 6.0.x, please also refer to the Important
Notes on Version 6.0.1 and 7.0 at https://downloads.efficientip.com/support/downloads/docs/.

Best Practices When Upgrading to Version 7.1

Upgrade Procedure
To properly upgrade to SOLIDserver 7.1, from version 5.0.4, you must:

1. Take into account the Important Notes 6.0.0.

2. Take into account the Important Notes 6.0.1.
3. Upgrade to the latest patch of version 5.0.4 to update the databases.
4. Run the post-migration and correct the issues it returns.
5. Upgrade to the latest patch of version 6.0.2 to update the databases.
6. Take into account the Important Notes 7.0.
7. Upgrade to SOLIDserver 7.1.

To properly upgrade to SOLIDserver 7.1, from version 6.0.0 or 6.0.1, you must:

1. Take into account the Important Notes 6.0.0.

2. Take into account the Important Notes 6.0.1.
3. Upgrade to the latest patch of version 6.0.2 to update the databases.
4. Take into account the Important Notes 7.0.
5. Upgrade to SOLIDserver 7.1.

1
 Important Notes on SOLIDserver
v7.1

To properly upgrade to SOLIDserver 7.1, from version 6.0.2, you must:

1. Upgrade to the latest patch of version 6.0.2 to update the databases.

2. Take into account the Important Notes 7.0.
3. Upgrade to SOLIDserver 7.1.

To properly upgrade to SOLIDserver 7.1, from version 7.0, you must:

1. Take into account the Important Notes 7.0.

2. Upgrade to SOLIDserver 7.1.

For more details refer to the chapter Upgrading of the Administrator Guide, available at https://down-
loads.efficientip.com/support/downloads/docs/7.1/.

Guardian Specificities
To properly upgrade Guardian and use the GUI to the fullest, we recommend:

1. Ensuring all servers, local and remote, are upgraded before editing Guardian parameters.
2. Taking into account the following configurations:
a. If your Guardian configuration included triggers at the time of the upgrade to version 7.1,
the GUI does not reflect the actual configuration that you can display via CLI. You must
recreate all triggers in the GUI before deploying them on Guardian servers.
b. If your server belonged to a smart architecture, the server keeps its parameters but the
smart is given the default values for each parameter.

NetChange
On the Page All discovered items, the Column Source Has Evolved
Since the page now returns IPv4 and IPv6 addresses, the column Source no longer returns the
value ARP. It now returns Network device when an IP address is found in the table ARP (for
IPv4 addresses) or the table NDP (for IPv6 addresses) of the network device.

On the Page All routes, a Column Was Renamed

The column Route Distinguisher is now called VRF RD.

VRF
On the Page All VRFs, a Column and a Field Were Renamed
The column RD ID is now called RD.

In the VRF addition wizard, the field RD ID is now called RD.

On the Page All VRF Route Targets, Some Columns Were Renamed
The column Source RD ID is now called Source RD.

The column Target RD ID is now called Target RD.