Virtual Router inconsistency when viewing Panorama config

Showing results for 
Show  only  | Search instead for 
Did you mean: 

Virtual Router inconsistency when viewing Panorama config

L1 Bithead



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.



Eli Wasserman

Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!

The LIVEcommunity thanks you for your participation!