11-11-2008 12:45 PM - edited 03-04-2019 12:17 AM
Hi,
I've upgraded four pieces of SCE devices and SML Application. Printout "show version" doesn't contain info about Protocol Pack. I tried to install SPQI protocol pack trough SCA BB Console I see error message like this: Protocol Pack Installation on 'SCE 3 F-OFDM' [10.48.64.75]: Operation failed: Error while importing DSS: Index uniquness violation error: duplicate Signature index 120586496
Does anybody have an idea how to solve it ? Thanks and regards...
Solved! Go to Solution.
11-17-2008 03:14 PM
In order to upgrade the SCABB from 3.0.5 to 3.1.6, you did the following:
* Upgrade the SCABB console
* Apply the new PQI file to the SCE
* Try to install the protocol pack. This is the step that failed
* Apply the default PQB file with the 3.1.6 SCABB
* Installing the protocol pack again. This time, the upgrade was successful
* Now, you need to apply the old policy on the SCE but you don't know how to make it compatible.
This behaviour is expected, and is due to a missing point in the upgrade guide. Before you can install a protocol pack, the PQB applied to the SCE has to be one created with the new version.
At this point, in order to reapply the old configuration on the SCE, you would need to do the following:
* Get the "engage/temp.dss" file from the SCE. This file contains the changes introduced in the protocol pack, and it's needed by the SCABB console.
* Open the old PQB with the new SCABB console
* Use the "Configuration --> Signature settings --> Signatures Script -->
Import from file" menu to import the DSS file you took from the SCE
* Apply the configuration
Importing the DSS file is only needed to apply configurations that were created with a different protocol pack (it is needed also with the default ones), so, it would not be needed if you retrieve the configuration from the SCE and then modify it.
I hope you find this information useful,
11-17-2008 03:14 PM
In order to upgrade the SCABB from 3.0.5 to 3.1.6, you did the following:
* Upgrade the SCABB console
* Apply the new PQI file to the SCE
* Try to install the protocol pack. This is the step that failed
* Apply the default PQB file with the 3.1.6 SCABB
* Installing the protocol pack again. This time, the upgrade was successful
* Now, you need to apply the old policy on the SCE but you don't know how to make it compatible.
This behaviour is expected, and is due to a missing point in the upgrade guide. Before you can install a protocol pack, the PQB applied to the SCE has to be one created with the new version.
At this point, in order to reapply the old configuration on the SCE, you would need to do the following:
* Get the "engage/temp.dss" file from the SCE. This file contains the changes introduced in the protocol pack, and it's needed by the SCABB console.
* Open the old PQB with the new SCABB console
* Use the "Configuration --> Signature settings --> Signatures Script -->
Import from file" menu to import the DSS file you took from the SCE
* Apply the configuration
Importing the DSS file is only needed to apply configurations that were created with a different protocol pack (it is needed also with the default ones), so, it would not be needed if you retrieve the configuration from the SCE and then modify it.
I hope you find this information useful,
11-19-2008 07:13 AM
THX,
It helped me a lot... Where did you find instructions how to do it ?
Regards
Robert
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide