I'm trying to migrate from one T1 to another T1 without dropping my website/email from the internet. I have a 1720 and I have two T1's. The old circuit is a 207 number and the new one is a 63 number. Anyway, they are both NAT'd by Qwest to my shop (and my webserver at 10.80.15.1) where I have the two circuits connected via two WICs on the back of the 1720. The 207 number is my current circuit and works perfect, but when I hit the 63 ip address the browser says its loading and then times out. Qwest is telling me that my idea of migrating from one circuit to the other won't work because of the router rip is set to take all traffic and send it out the old circuit. So when I hit the website using the new cirucuit (the 63 ip address) and then the webserver responds the traffic is being send back out via the old circuit (207 ip address) and getting lost. I'm not buying this story, but I don't know how to fix it. HELLLP!
I'm not 100% clear on your scenario but it seems to be that if Qwest is doing the NAT'ing, all you should have to do is change your default route to point out the new serial1 interface. Then Qwest, if they're set up correctly, will receive and route the traffic appropriately. As it currently stands, all outbound traffic is going out serial0 per the default route. This will need changed once you switch to the serial1 circuit.
Quest is correct, based on what you have described. When using NAT, all traffic MUST traverse the same path in both directions, otherwise the wrong address translation will be used and communications will fail.
The normal approach to this migration need is to set up the web server to use two IP addresses, one for each link, and use policy routing outbound to route based on which IP is the SOURCE of the outbound packet.
Two sets of IPs for the webserver... I hadn't thought of that. I do have a new webserver I'm about to put into service and was thinking of using it to test my new circuit. The problem is that I'll end up with some email and files on the old server and some on the new server and that just has trouble written all over it.
What I want to do is be able to test the new circuit (63 ip address) and make sure it works. Then once I know it works contact my registar (dotearth) and have them change the IP address that www.coloradoprinting.com resolves to. Then as that change happens around the globe, the nameserver will resolve from the old to the new ip address as their particular nameserver is updated. Follow? The idea is to not loser our web presence or email.
If you can describe to me your desired set up I will help you with the configuration. Are you looking to phase out the old t1 and go with the new one ? Does your new ISP have a DNS record already set up for the new t1 ? If you can provide the details I can provide the configuration.
Yes, I'm trying to phase out my old T1 and start using the new one. What I want to do is be able to test the new circuit (63 ip address) and make sure it works. Then once I know it works contact my registar (dotearth) and have them change the IP address that www.coloradoprinting.com resolves to. Then as that change happens around the globe, the nameserver will resolve from the old to the new ip address as their particular nameserver is updated. Follow? The idea is to not loser our web presence or email.
This is actually a pretty cool feature, i didn't even know it existed until I was looking for a solution to advertise a subnet (prefix in BGP talk), only if a certain condition existed. This is exactly what conditional advertisements does
j ai une question j ai achete un routeur cisco 887VA-k9 , je le configuré avec la configuration ci- dessous
si je le lier avec mon pc portable sur l un de ses ports directement ça marche toute est bien ( la connexion internet + m...
Attached policy provides CLI access to the Cisco 4G router over text messaging. Two files are in the attached .tar file:
2. PDF with instructions on how to load and use the .tcl file.