11-12-2014 06:41 AM - edited 03-11-2019 10:04 PM
I am changing the way Vlans access the CORE network.
Currently: The ASA interfaces connect to the DMZ switch stack via trunks. The DMZ switch stack has a trunk to the CORE Network
Several of the sub-interface Vlan(s) on the ASA do not get trunked to the Core.
There are other Vlans on the DMZ switch stack, that are not on the ASA that do get trunked to the core.
See diagram_1
The new way will be to connect any of the Vlans that were trunked to the CORE will now go thru the ASA Inside and DMZ interfaces directly to the CORE.
See Diagram_2
I am trying to figure out how to configure the ASA and the DMZ switch to make that happen.
11-12-2014 01:49 PM
To possibly refine the above scenario
The goal: Any vlan that is currently being trunked to Core will now have to pass through the ASA, which will connect to Core.
Protecting Core behind ASA seems best practice.
Topology: WAN router connects to DMZ switch. On the DMZ switch there are:
TRUNK To CORE passing (8) vlans
(2) Vlans have SVI on CORE
(Server and Netwk Mgmnt)
(2) Vlans have an SVI on the DMZ switch & and SVI on the ASA
(Inside and BP_1)
(2) other Vlans have SVI on ASA
(Internal DMZ and BP_2)
(2) Vlans have no SVI to be found. Could be Business Partners using L2 across DMZ switch to Core.
The ASA has (4) interface
0 - OUTSIDE
1 - INSIDE
2 - DMZ Trunks (has 6 subinterfaces/vlans. BP_1 lives here and is the Only 1 of these vlans to get trunked to Core)
3 - InternalDMZ and BP_2
The Server and Netwk Mgmnt Vlans have the SVI on the Core.
How can I get these to pass throught the ASA.
Create sub-int on ASA for this Vlan
This means I would have to change the default gateway on the Servers on the DMZ to the ASA sun int.
Anyone have any guidance on this issue?
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide