(it doesn't let me stop or restart the server) (so, basically I can do nothing) When my server is down ping doesn't respond either and I can't access either via ENJOY VPS console. My question is almost all the hops goes to the same ip, that is my provider ip (but not my server ip) ¿is that ok? I config my own DNS server (bind9) might that be the problem? I'm having some problems with a vps I rent ( ENJOY VPS: Unmanaged VPS - Medium VPS) and they insist that their server is running ok, but I keep having this problem, My server keeps getting down everyday, It's less than 15 minutes, but it's everyday (sometime twice a day) and I think that's not acceptable. L 10.0.2.1/32 is directly connected, FastEthernet1/0Ĭ 10.0.3.0/24 is directly connected, FastEthernet1/1 L 10.0.1.1/32 is directly connected, FastEthernet0/1Ĭ 10.0.2.0/24 is directly connected, FastEthernet1/0 L 10.0.0.1/32 is directly connected, FastEthernet0/0Ĭ 10.0.1.0/24 is directly connected, FastEthernet0/1 + - replicated route, % - next hop overrideġ0.0.0.0/8 is variably subnetted, 13 subnets, 3 masksĬ 10.0.0.0/24 is directly connected, FastEthernet0/0 O - ODR, P - periodic downloaded static route, H - NHRP, l - LISP Ia - IS-IS inter area, * - candidate default, U - per-user static route I - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2 N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2Į1 - OSPF external type 1, E2 - OSPF external type 2 The loopback interfaces are not in the routing tables because they are in the 192.168.0.0/24 range which has not been included in the routing protocol.Ĭodes: L - local, C - connected, S - static, R - RIP, M - mobile, B - BGPĭ - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area There is no connectivity from the PCs to the loopback interfaces because they are not in the routing tables of the routers (apart from the local loopback interface on each router).

Is there connectivity to the loopback interfaces from the PCs? Why or why not? We can get to our routers no matter what path we've got available and still using the same IP address.Ģ. I can still ping 192.168.1.1and if I traceroute to it, I'm going to see it going down the bottom path via R5. However, it failed over to the other path, so it uses the FastEthernet 2/0. If I do a show ip route now, I can see the 192.168.1.1 in the routing table from EIGRP. The first path is not going to be available anymore. On R4, I’ll go to interface FastEthernet 0/0 then I'm going to shut down that interface. Let's check that I can failover and could use the loopback. I can ping 192.168.1.1and if I enter the command trace 192.168.1.1, I can see that it's passing along the top path with the next hop of 10.1.1.2 which was out interface FastEthernet 0/0. That's why only the FastEthernet 0/0 path is in the routing table right now. There are two paths, but one of them has got a better cost. Let's see if the route is there using the show ip route command.

Going back to R4, EIGRP converges pretty quickly. The 0.0.0.0 is the wildcard mask which is the inverse of the subnet mask.

Loop address ip