1. Error allocating reousrce in RUTG site

Error allocating reousrce in RUTG site

Home Forums FABRIC General Questions and Discussion Error allocating reousrce in RUTG site

Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
    Posts
  • #8087
    Yuanjun Dai
    Participant

      HI,

       

      I am trying to allocate a topology in RUTG site. However, errors happen as follow.

      4 failed lease update- all units failed priming: Exception during create for unit: 47db2d95-a8f9-4ffc-9840-1d41644f7f72 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 rutg-data-sw: Fri Jan 17 15:16:12.230 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-net14-47db2d95-a8f9-4ffc-984rn bridge-domain bd-net14-47db2d95-a8f9-4ffcrn interface HundredGigE0/0/0/5.2074rn Invalid argument: Interface already used for L2VPNrn rn rn rnrnend, internal: jsonrpc_tx_commit395#all units failed priming: Exception during create for unit: 47db2d95-a8f9-4ffc-9840-1d41644f7f72 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 rutg-data-sw: Fri Jan 17 15:16:12.230 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-net14-47db2d95-a8f9-4ffc-984rn bridge-domain bd-net14-47db2d95-a8f9-4ffcrn interface HundredGigE0/0/0/5.2074rn Invalid argument: Interface already used for L2VPNrn rn rn rnrnend, internal: jsonrpc_tx_commit395#
      #8088
      Komal Thareja
      Participant

        Hi Yuanjun,

        We had leaked config on the switch which has been cleared by help from Network Team. Could you please try your slice again? Please let us know if you still see the issue.

        Thanks,
        Komal

        #8096
        Yuanjun Dai
        Participant

          It worked now.

        Viewing 3 posts - 1 through 3 (of 3 total)
        • You must be logged in to reply to this topic.