Design/Configuration for migration
- June 15, 2019
- 2 replies
- 7271 views
Hello All,
As I am new to the forum so please pardon for which place or topic option will be suitable for my query.
As you can see in attached we are separating the same physical site into two sites with the name Site-A and Site-B. Both having separate ISP's.
On Site-A, intervlan routing, DHCP, ACL's and default route towards firewall happening on Core switch and Site-A firewall only be used for internal/external policies. Please note that communication between core and firewall is layer3.
On Site-B we have been told to use separate zones for each department, printer, Server's (DMZ), intervlan routing, DHCP, etc on the internal firewall.
The main requirement
The main requirement is Site-A users or vlans should access or communicate with the Site-B DNS/domain controller. For example, if support person from Site-A needs to add PC in Domain, that should be successful.
- Please suggest the design between Site-A and Site-B.
- It's appropriate with the firewall to firewall connectivity or it can be between core and a site-b firewall.
- what will be the configuration for smooth connectivity?
We tried a lot of connectivity configuration but failed.
Please Note: All the firewalls are Fortigate and all switches are Cisco. Before going to production we deploy it in EVE and tested but communication between Site-A and Site-B failed, apart from that everything fine. We cannot go directly to production until we sure that is the way.
Your help will highly appreciated.