Jon,

Thanks. The new network is being configured and will be set in production next month. I have not gotten to the configuring the LAN switch, yet. My guess is the traffic would be 50% accessing the resources in the MPLS network and 50% traffic would be directed to the internet.

The MPLS router is managed by the ISP. We do not have access to the MPLS router. How and where is your second suggestion configured? "...any traffic not destined for the private addresses in the MPLS network get routed back to the ASA. "

Thanks.

Said

Said

Is the LAN switch layer 2 only or layer 3 capable. If you do not have access to the MPLS router you have 2 options

1) Add a route on the ASA for the private MPLS networks pointing to the MPLS router. You will need to enable hairpinning on the ASA.

Set the default-gateway of the clients on your LAN switch to be the ASA.

2) If your switch is a Layer 3 switch then you can do this in a much cleaner way. Create the L3 vlan interface(s) for the client vlan(s) on the switch and then you can use statics on the L3 switch eg.

ip route 0.0.0.0 0.0.0.0 "ASA inside interface"

ip route "MPLS private net" "subnet mask" "MPLS router inside interface"

Jon

Jon,

The branch office networks will have layer 2 LAN switches, All hosts will be on 1 VLAN.

The Corp LAN switch will have a layer 3 switch assigned with several VLANS.

I am confused on your second suggestion. The VLANS on the Corp L3 switch would are for subnets in local location. The MPLS network will include the servers IP of at Corp and rest of networks. This is my first professional/production experience. Could you elaborate on the second suggestion.

Thanks.

Said

Jon,

Thank you.

Said