06-04-2014 06:57 AM - edited 03-03-2019 07:26 AM
Guys,
We have a core switch with two fibre lines connecting us through two different ISP's to the internet. These ISP's have provided us with a range of public ip's each. We have a few routers on some of these ip's and they are working fine and we can access them externally (telnet and ssh).
I am now busy setting up two servers, one on each ISP with their respective public ip's. I can ping the core switch and the isp gateways from the servers and from the core. I have triple checked that there are no active firewalls and I can see that the http ports are open and accessible (TcpView). But for the life of me I can not access those servers externally. I am now completely stumped. I do suspect though that it is a routing problem through the core.
And herewith the relevant parts from my Core switch's config:
Any ideas guys, I am at my wits end here ....
Thanks as always !
06-04-2014 07:16 AM
Some more info. I have tried setting the Default Gateways(s) on Server1 and Server2 to the Core's ip address, to the respective ISP gateway addresses and tried local policies. None of it worked.
06-04-2014 07:44 AM
Hi Oliver ,
Have you got IP Address assigned to your server from the same segment ?? like for server 1
ip address PUBLIC_IP1 255.255.255.240
and for server 2
ip address PUBLIC_IP2 255.255.255.248
What is the gateway IP address assigned for both servers .
HTH
Sandy
06-04-2014 07:47 AM
Sandy, yes each server has an IP address assigned from the range from a respective ISP and that same ISP's gateway address is used as the Default Gateway.
06-04-2014 07:55 AM
Hi Oliver ,
Gateway IP address for server is your SVI VLAN of your Switch ??
06-04-2014 08:08 AM
No, I am using the ISP gateway addresses (I can ping them from the server).
06-04-2014 09:35 PM
Hi
can you do trace route from your server to some public IP address , similarly do a trace route from your VPN router , which is connected in same VLAN .
06-05-2014 02:39 AM
I have changed both routers to now point their gateways to the SVI VLAN of the core switch. It has actually improved the situation somewhat.
When I now do a test from an external PC and do a "telnet server_ip 80" then connection actually seems to connect instead of just timing out as it usually did. Also in a browser I go http://server_ip and something happens, although the page is empty, but no connection errors as before.
06-17-2014 12:53 AM
I eventually managed to resolve the issue with one of the servers (it turns out that server2's network card was bust, transmits but does not receive). I added a local policy to set the default gateways on the core. Then I added a route-map on the interfaces to set the next hops. I then also had to remove the default gateway as setup on the server and replace it with a few static permanent routes. Everything seemed fine after that.
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: