Virtual Router inconsistency when viewing Panorama config

[ewasserman]

Hi,

My objective is to import a Panorama config to Expedition in order to make changes to a template that are not possible locally on panorama - for example moving ethernet interfaces and having all the dependencies move with them.  

I connected my panorama to expedition, created a project and imported the panorama device to the project. The issue begins when I view the configuration within the expedition project, some of the ethernet interfaces which had no virtual router assigned, were now associated with a VR in error.  ( i.e.  virtual wires are not ABLE to be placed in a VR, and were now placed in an incorrect VR within expedition).

I can manually correct this issue and then make my needed changes, however I am not sure how comfortable I will be with trusting expedition to make the entire change seamlessly. I look forward to hearing the communities thoughts.

Thanks,

Eli Wasserman