topic R80.40 and vsx_provisioning_tool fails to commit in Firewall and Security Management

R80.40 and vsx_provisioning_tool fails to commit

Maarten_Sjouw — Wed, 19 Feb 2020 11:45:47 GMT

Today I wanted to use the vsx_provisioning_tool to create a new VS on a R80.40 management, while running the tool from the Domain environment and got an error that it could not commit the new information to the gateway.

My VSX gateway is a Security Group on a Maestro setup, however there is another Security Group on the same Maestro setup that is hooked to a R80.30 MDS management and there the provisioning tool works just fine.

Transcript of the command issued:

[Expert@MDS-25:0]# vsx_provisioning_tool -s localhost -u admin -p <Password> -f collect-vs
Version harry_main, build 994000068
Executing line number 1 - 'transaction begin'
Executing line number 2 - 'add vd name DC1P001 vsx CPFG-01 main_ip 1.2.4.42'
Executing line number 3 - 'add interface vd DC1P001 name bond0.1100 ip 1.2.8.42/28'
Executing line number 4 - 'add route vd DC1P001 destination default next_hop 1.2.4.241'
Executing line number 5 - 'transaction end'
Creating DC1CXPP001...
Generating VSX Configuration for DC1P001 on CPFG-01.
Pushing VSX Configuration to CPFG-01.
CPFG-01: processed 5% of configuration...
Failed to configure CPFG-01 with the following errors:
CPFG-01... error :Internal Error - Failed to commit changes in the OS.. libdb_do_transaction: connection closed during operation
Error: Failed to commit changes to VSX database.
Failed to execute line number 5
Failed to commit transaction which began at line number 1

Re: R80.40 and vsx_provisioning_tool fails to commit

FedericoMeiners — Wed, 19 Feb 2020 13:09:44 GMT

Hi @Maarten_Sjouw

In general when you make transactions over the same VS with file as an input is not neccesary to specify the name in each line.

Here's a script that I recently used in R80.30 to provision a new VS

To be honest I don't know if the error is realted to the syntax but it's worth the shot

Hope it helps

Re: R80.40 and vsx_provisioning_tool fails to commit

Maarten_Sjouw — Wed, 19 Feb 2020 14:02:31 GMT

Frederico,

I used the syntax that is shown when you issue the command show vd name <VS-Name>. The reason it is there is that I have more than 1 VS in the same Domain, interface commands can be issued for all VS's in that domain.
The error is specific to R80.40, I used the exact same syntax on a domain on a R80.30 MDS.

Re: R80.40 and vsx_provisioning_tool fails to commit

PhoneBoy — Thu, 20 Feb 2020 04:02:28 GMT

If it worked in R80.30 but not in R80.40, you're probably in TAC case territory. 😬

Re: R80.40 and vsx_provisioning_tool fails to commit

Maarten_Sjouw — Thu, 20 Feb 2020 05:20:12 GMT

Yep, a case is open for it.

Re: R80.40 and vsx_provisioning_tool fails to commit

Guy_Grundman — Thu, 20 Feb 2020 07:30:16 GMT

Hi,

Can you please share your ticket number so i could follow up on this ?

also, do you see any confd core dums in /var/log/dump/usermode ?

Re: R80.40 and vsx_provisioning_tool fails to commit

Maarten_Sjouw — Thu, 20 Feb 2020 07:33:33 GMT

Hi Guy,
Ticket 6-0001915272 and there are no dumps.

Re: R80.40 and vsx_provisioning_tool fails to commit

Guy_Grundman — Thu, 20 Feb 2020 09:04:37 GMT

Thank you,

I will be following up on the ticket and will hopefully have a quick resolution.