[BUG][4.002]Error using Join function with 1 UTM

I have used the join function successfully in SUM 4.002 to tidy up the orphaned devices in the Gateway manager (due to V9 reinstalls, etc.).. but I have one pair that refuse to join. This is the error that I see:

2012:10:18-12:27:20 sum01 accd: 2536170 [0xf37ddb70] ERROR server.user.DeviceTransferGuidCallback null - Transferring 81808972-6562-11DE-9EFA-CBC089C37731 to 635F0658-F786-11E1-9D9A-9198EEC2D6D2 failed: JSON-RPC method/notification 'set_agent_guid' does not exist.
2012:10:18-12:27:22 sum01 accd: 2538385 [0xf17d9b70] ERROR server.user.DeviceTransferGuidCallback null - Transferring 81808972-6562-11DE-9EFA-CBC089C37731 to 635F0658-F786-11E1-9D9A-9198EEC2D6D2 failed: JSON-RPC method/notification 'set_agent_guid' does not exist.

Parents

0 Hakan Yueksel over 12 years ago

Hi Bruce,

the device claims that it does not support this new method which was introduced with
UTM V9. Could you please verify that it doesn't have a version
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 BrucekConvergent over 12 years ago in reply to Hakan Yueksel

That must be it... on all the other ones, I had the old one (disconnected) that was a V8 install, and was joining it with a V9 (the replacement) device. So what you're saying is that you can't do the join operation with both devices running Version 8?

CTO, Convergent Information Security Solutions, LLC

https://www.convergesecurity.com

Advice given as posted on this forum does not construe a support relationship or other relationship with Convergent Information Security Solutions, LLC or its subsidiaries. Use the advice given at your own risk.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Hakan Yueksel over 12 years ago in reply to BrucekConvergent

Yes.

A device is identified by the SUM by a guid that it sends to the SUM.

The join buttons functionality is that the guid from the old installation is taken and sent
to the new installation. Then the device-agent of the new installation replaces its newly
created guid by the one that has been sent from the SUMs join button. I.e. there is
some new functionality on the device introduced by V9. That's why it can't work with
versions here.

Regards, Hakan
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Reply

0 Hakan Yueksel over 12 years ago in reply to BrucekConvergent

Yes.

A device is identified by the SUM by a guid that it sends to the SUM.

The join buttons functionality is that the guid from the old installation is taken and sent
to the new installation. Then the device-agent of the new installation replaces its newly
created guid by the one that has been sent from the SUMs join button. I.e. there is
some new functionality on the device introduced by V9. That's why it can't work with
versions here.

Regards, Hakan
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Children

0 BrucekConvergent over 12 years ago in reply to Hakan Yueksel

Thanks for the info Hakan!

So far 4.002 seems to work quite well! SSO works much better (more reliably) with V8 and V9.

CTO, Convergent Information Security Solutions, LLC

https://www.convergesecurity.com

Advice given as posted on this forum does not construe a support relationship or other relationship with Convergent Information Security Solutions, LLC or its subsidiaries. Use the advice given at your own risk.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel