Stuck L2VPN Interface on amst-data-sw

[Aggelos Pipilikas]

Hello,

I am receiving a deployment error when trying to create a slice at the Amsterdam site. It appears there is a stale configuration or a resource collision on one of the data switches that is preventing the NSO commit from succeeding.

The orchestrator is trying to assign HundredGigE0/0/0/9.2088, but the switch is rejecting it because it is already bound to an existing L2VPN.

Error:

failed lease update- all units failed priming: Exception during create for unit: d254474c-833f-479c-9509-9027f953484c 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 amst-data-sw: Wed Aug 19 08:22:36.180 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-Network-AMST-d254474c-833f-4rn bridge-domain bd-Network-AMST-d254474c-83rn interface HundredGigE0/0/0/9.2088rn Invalid argument: Interface already used for L2VPNrn rn rn rnrnend, internal: jsonrpc_tx_commit395#all units failed priming: Exception during create for unit: d254474c-833f-479c-9509-9027f953484c 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 amst-data-sw: Wed Aug 19 08:22:36.180 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-Network-AMST-d254474c-833f-4rn bridge-domain bd-Network-AMST-d254474c-83rn interface HundredGigE0/0/0/9.2088rn Invalid argument: Interface already used for L2VPNrn rn rn rnrnend, internal: jsonrpc_tx_commit395#

Can you help me resolve this issue? (Slice-id: a63a1548-ac2c-406d-a7fc-1d1432287b51)

Thank you in advance for your assistance.

[Tom Lehman]

There was an old service on the amst router, that has been cleared.  You can try the provisioning again, please let us know if any problems.  Thanks, Tom

[Author]

Posts