Bug with virtual-wire

Reply
L1 Bithead

Bug with virtual-wire

There seems to a bug with Expedition.

 

In Project\Network\Zones, both trust and untrusted has been deleted.

In Project\Network\Virtual Wires, existing wires deleted and is empty.

 

Yet, I am still getting this error message when doing API Output Manager to the device

 

{"3":{"device":"PA-850VideoPro","status":"fail","text":"<msg><line><![CDATA[ vsys1 -> zone -> trust -> network -> virtual-wire \\'ethernet1\/2\\' is not a valid reference]]><\/line><line><![CDATA[ vsys1 -> zone -> trust -> network -> virtual-wire is invalid]]><\/line><\/msg>","date":"2019-03-22 16:59:36"}}

 

This seems to happen when my base image has virtual wires and trust and untrust zone.  Even though I deleted them in Expedition, it still say virtual wire invalid.

Highlighted
L4 Transporter

Re: Bug with virtual-wire

you need to manually remove the default virtual wire config on the target device for your command to complete.

 

This is a required step (and not a bug) for an initial device turn up if you intend to not use the default virtual wire config (which used eth1/1 and eth1/2 on the firewalls).

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 Live Community as a whole!

The Live Community thanks you for your participation!