Opened 6 years ago

Last modified 6 years ago

#193 new

stitching sliver with 2 link on 1 VM fails with NDL exception

Reported by: lnevers@bbn.com Owned by: somebody
Priority: major Milestone:
Component: AM Version: SPIRAL5
Keywords: Network Stitching Cc:
Dependencies:

Description

Run a stitching scenario which includes 1 VM at GPO EG (via ExoSM) and 1 VM at IG Utah with the following links:

  • Utah IG if0 <-link1-> GPO EG if0
  • Utah IG if1 <-link2-> GPO EG if1

Submitting the createsliver request results in the following NDL converter error:

10:36:58 ERROR    omni:  {'output': 'ERROR: Exception encountered: orca.ndl.NdlException: 
Interface bbnNet.rdf#BbnNet/IBM/G8052/GigabitEthernet/1/2/ethernet should be owned by 
exactly two entities (a node and a connection/vlan), instead: 4', 'code': {'geni_code': 2}}

10:36:58 WARNING  stitcher: Stitching failed but will retry: Circuit reservation failed at
<Aggregate urn:publicid:IDN+exogeni.net:bbnvmsite+authority+am> (AMAPIError: Error from
Aggregate: code 2: ERROR: Exception encountered: orca.ndl.NdlException: Interface
bbnNet.rdf#BbnNet/IBM/G8052/GigabitEthernet/1/2/ethernet should be owned by exactly
two entities (a node and a connection/vlan), instead: 4.). Try again from the SCS 

Attaching rspec

Attachments (1)

stitch-eg-gpo-ig-gpo-loop.rspec (1.7 KB) - added by lnevers@bbn.com 6 years ago.

Download all attachments as: .zip

Change History (2)

Changed 6 years ago by lnevers@bbn.com

comment:1 Changed 6 years ago by lnevers@bbn.com

Not addressed by software update on 2014-01-14.

Note: See TracTickets for help on using tickets.