L2STS links failing

[Fraida Fund]

Hi!

I’m using fablib to create a topology with 4 VMs and 6 L2STS links (using Basic NICs) and am having some trouble getting it up. I keep getting errors like these on the network links –

failed lease update- all units failed priming: Exception during create for unit: 2f8847c1-ed42-4139-8363-6318988f5373 Playbook has failed tasks: NSO commit returned JSON-RPC error: type: rpc.method.failed, code: -32000, message: Method failed, data: message: External error in the NED implementation for device tacc-data-sw: Sun Sep 3 02:53:16.538 UTCrnrn Failed to commit one or more configuration items during a pseudo-atomic operation. All changes made have been reverted.rn SEMANTIC ERRORS: This configuration was rejected by rn the system due to semantic errors. The individual rn errors with each failed configuration command can be rn found below.rnrnrnl2vpnrn bridge group bg-net-r1-d-2f8847c1-ed42-4139-rn bridge-domain bd-net-r1-d-2f8847c1-ed42-4rn interface HundredGigE0/0/0/9.2055rn Invalid argument: Interface already used for L2VPNrn rn rn rnrnend, internal: jsonrpc_tx_commit357#all units failed priming: Exception during create for unit: 2f8847c1-ed42-4139-8363-6318988f5373 Playbook has failed tasks: NSO commit returned JSON-RPC error: type: rpc.method.failed, code: -32000, message: Method failed, data: message: External error in the NED implementation for device tacc-data-sw: Sun Sep 3 02:53:16.538 UTCrnrn Failed to commit one or more configuration items during a pseudo-atomic operation. All changes made have been reverted.rn SEMANTIC ERRORS: This configuration was rejected by rn the system due to semantic errors. The individual rn errors with each failed configuration command can be rn found below.rnrnrnl2vpnrn bridge group bg-net-r1-d-2f8847c1-ed42-4139-rn bridge-domain bd-net-r1-d-2f8847c1-ed42-4rn interface HundredGigE0/0/0/9.2055rn Invalid argument: Interface already used for L2VPNrn rn rn rnrnend, internal: jsonrpc_tx_commit357#

failed lease update- all units failed priming: Exception during create for unit: 8b64af2d-3bff-4e2a-bf88-d2dc9834548e Playbook has failed tasks: NSO commit returned JSON-RPC error: type: rpc.method.failed, code: -32000, message: Method failed, data: message: External error in the NED implementation for device mass-data-sw: Sun Sep 3 02:45:40.905 UTCrnrn Failed to commit one or more configuration items during a pseudo-atomic operation. All changes made have been reverted.rn SEMANTIC ERRORS: This configuration was rejected by rn the system due to semantic errors. The individual rn errors with each failed configuration command can be rn found below.rnrnrnl2vpnrn bridge group bg-net-direct-8b64af2d-3bff-4e2rn bridge-domain bd-net-direct-8b64af2d-3bffrn interface HundredGigE0/0/0/5.2054rn Invalid argument: Interface already used for L2VPNrn rn rn rnrnend, internal: jsonrpc_tx_commit357#all units failed priming: Exception during create for unit: 8b64af2d-3bff-4e2a-bf88-d2dc9834548e Playbook has failed tasks: NSO commit returned JSON-RPC error: type: rpc.method.failed, code: -32000, message: Method failed, data: message: External error in the NED implementation for device mass-data-sw: Sun Sep 3 02:45:40.905 UTCrnrn Failed to commit one or more configuration items during a pseudo-atomic operation. All changes made have been reverted.rn SEMANTIC ERRORS: This configuration was rejected by rn the system due to semantic errors. The individual rn errors with each failed configuration command can be rn found below.rnrnrnl2vpnrn bridge group bg-net-direct-8b64af2d-3bff-4e2rn bridge-domain bd-net-direct-8b64af2d-3bffrn interface HundredGigE0/0/0/5.2054rn Invalid argument: Interface already used for L2VPNrn rn rn rnrnend, internal: jsonrpc_tx_commit357#

(happening on more than one slice, and on more than one site.)

(I also noticed that despite the error, the slice ends up in StableOK, even though the link is missing. Is this the expected behavior? I had assumed that “StableOK” means “we were able to supply what you asked for, and it’s ready for you to use.” If not, is there some way to check if everything in the request was satisfied?)

[Komal Thareja]

Hi Fraida,

Thank you for reporting this issue. There was a leaked network service. I have cleared it up. Please try your slice again and it should work. Regarding the Slice state, it is a bug and we working on it.

Thanks,

Komal

[Author]

Posts