|
dgrunblatt -> RE: routing within sites using MPLS (21.Feb.2007 12:20:17 PM)
|
Tom, thanks again! I wish this could be the answer of my questions but it's not. Here's why: 1) Installed ISA Servers in 6 sites 2) Added a new network interface on each ISA Server for the 10.170.98.x network (MPLS) 3) Created a route relationship between Internal and MPLS network 4) Created subnets for all the sites in order to not being recognized as spoofed packets. 5) Created an access rule that allows all outbound protocols between internal, localhost and mpls networks. Up to here I can successfully use the 10 network with the 192 network for each site BUT... how ISA server knows that, for example, If I'm located in the main site and I want to ping the 192.168.4.x network, it has to travel through the MPLS (10.170.x.x) network? the answer would be: create a permanent rule in the main site: 192.168.4.0 mask 255.255.255.0 10.170.98.97 (= DG for the MPLS main site network). Well... I did it and guess what? you're right! it didn't work :) I WAS able to ping from ISA1 to ISA2 if I create the static route but can't go beyond (can't reach the other servers, DCs, workstations in the remote sites). I don't know if this will sound crazy but now that I was writing to you, I will try to create another static route in the remote sites to route the incoming traffic from the 10 network to the 192 network. Will what happens... if you have other ideas, LMK! I will try to post a jpg with the idea I'm trying to reach. Thanks one more time! Daniel.
|
|
|
|