Support Forum
The Forums are a place to find answers on a range of Fortinet products from peers and product experts.
melamin
New Contributor

2 VDOMS UTILIZING SAME WAN PORT

I currently have  2 vdoms setup. I have not been able to configure both vdoms with the same wan port. Is this possible? The reason I am trying to approach it this way as opposed to having  separate external interfaces for each vdom is because i want to setup wan failover to cover both vdoms.

2 Solutions
Carl_Wallmark
Valued Contributor

Hi,

 

You can use the same physically interface, by using VLANs on the interface,

VLAN1(wan1) = VDOM1

VLAN2(wan1) = VDOM2

etc...

 

If you need the same logical interface, all you can do is create a VDOM-link between the two vdoms and create firewall rules for that.

 

VDOM1 -> WAN1

VDOM2 -> VDOM-link to VDOM1 -> WAN1

FCNSA, FCNSP
---
FortiGate 200A/B, 224B, 110C, 100A/D, 80C/CM/Voice, 60B/C/CX/D, 50B, 40C, 30B
FortiAnalyzer 100B, 100C
FortiMail 100,100C
FortiManager VM
FortiAuthenticator VM
FortiToken
FortiAP 220B/221B, 11C

View solution in original post

FCNSA, FCNSP---FortiGate 200A/B, 224B, 110C, 100A/D, 80C/CM/Voice, 60B/C/CX/D, 50B, 40C, 30BFortiAnalyzer 100B, 100CFortiMail 100,100CFortiManager VMFortiAuthenticator VMFortiTokenFortiAP 220B/221B, 11C
emnoc
Esteemed Contributor III

A meshed vdom is what you want.  Be advise fwpolicies resources are doubled for every meshed-vdom

 

http://socpuppet.blogspot.com/2014/09/a-stacked-vdom-concept-with-fortigate.html

http://socpuppet.blogspot.com/2014/09/a-meshed-vdom-transparent-using-inter.html

 

I really wished FTNT would come up a with solution that allows you to share a interface similar to the cisco ASA & across multi-contexts.

 

 

PCNSE 

NSE 

StrongSwan  

View solution in original post

PCNSE NSE StrongSwan
4 REPLIES 4
Carl_Wallmark
Valued Contributor

Hi,

 

You can use the same physically interface, by using VLANs on the interface,

VLAN1(wan1) = VDOM1

VLAN2(wan1) = VDOM2

etc...

 

If you need the same logical interface, all you can do is create a VDOM-link between the two vdoms and create firewall rules for that.

 

VDOM1 -> WAN1

VDOM2 -> VDOM-link to VDOM1 -> WAN1

FCNSA, FCNSP
---
FortiGate 200A/B, 224B, 110C, 100A/D, 80C/CM/Voice, 60B/C/CX/D, 50B, 40C, 30B
FortiAnalyzer 100B, 100C
FortiMail 100,100C
FortiManager VM
FortiAuthenticator VM
FortiToken
FortiAP 220B/221B, 11C

FCNSA, FCNSP---FortiGate 200A/B, 224B, 110C, 100A/D, 80C/CM/Voice, 60B/C/CX/D, 50B, 40C, 30BFortiAnalyzer 100B, 100CFortiMail 100,100CFortiManager VMFortiAuthenticator VMFortiTokenFortiAP 220B/221B, 11C
MikePruett

Yeah, it gets a little messy. In situations like that I tend to go the three VDOM route making a pseudo pyramid.

 

Have VDOM1 be the NAT vdom for the WAN port and have the two other vdoms underneath it that link up to the main one.

Mike Pruett Fortinet GURU | Fortinet Training Videos
emnoc
Esteemed Contributor III

A meshed vdom is what you want.  Be advise fwpolicies resources are doubled for every meshed-vdom

 

http://socpuppet.blogspot.com/2014/09/a-stacked-vdom-concept-with-fortigate.html

http://socpuppet.blogspot.com/2014/09/a-meshed-vdom-transparent-using-inter.html

 

I really wished FTNT would come up a with solution that allows you to share a interface similar to the cisco ASA & across multi-contexts.

 

 

PCNSE 

NSE 

StrongSwan  

PCNSE NSE StrongSwan
Carl_Wallmark
Valued Contributor

lets hope they have a solution for this kind of situation for FortiOS 5.6 which is scheduled for Q1 2017.

I asked for virtual routing tables when they planned 5.4

FCNSA, FCNSP
---
FortiGate 200A/B, 224B, 110C, 100A/D, 80C/CM/Voice, 60B/C/CX/D, 50B, 40C, 30B
FortiAnalyzer 100B, 100C
FortiMail 100,100C
FortiManager VM
FortiAuthenticator VM
FortiToken
FortiAP 220B/221B, 11C

FCNSA, FCNSP---FortiGate 200A/B, 224B, 110C, 100A/D, 80C/CM/Voice, 60B/C/CX/D, 50B, 40C, 30BFortiAnalyzer 100B, 100CFortiMail 100,100CFortiManager VMFortiAuthenticator VMFortiTokenFortiAP 220B/221B, 11C
Labels
Top Kudoed Authors