We have just brought some remote clinics online. We have a point-to-point between our PA5520 at the main hospital and a PA820 at our remote site. We're routing between P2P with static routing at the moment. Data/Voice is working, as the VLANs are on the remote site switches themselves. However, we've been asked to get another VLAN working that is at our main hospital. Here's a quick crude drawing I put together in like 5 minutes:
Each one of the remote switches is also connected via a P2P, be it direct connect or layer 2 transport, so the only way I can think of getting the devices at the remote clinics talking, is more routing, or NATing somehow. Any guidance would be appreciated. I now wish I would've went layer 2 instead of layer 3 for this...
Agreed! If you need VLAN 176, you may need to rethink your deployment.
You could be very easy to use a feature called VWire, to connect from the clinic switch, to the (upstream device) that is allowing P2P (some interconnecting switch or whatever.
Consider that Vwire is sort of like a "intelligent" repeater. Whatever is plugged into (port 3) goes out port 4. A bump in the wire.
No L2 or Layer3 addressing (no mac or spanning tree, and definitely no routing)
Just create a VWire object, and assign 2 ports (not your L3 interfaces) and create 2 more zones (untrusted-vwire and trusted-vwire)
You may need to create similar policies to mimic what you have.
If you do this, then you would not even need routing, the traffic goes from vlan176 in the clinic, through the FW, through the P2P to the other side, by the hospital.
Just an idea.
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!