MPLS Circuit. Problem with Routing through the cloud

Unanswered Question
May 15th, 2008

Hello,

I just had my first MPLS Circuit turned on. I can ping the other side (router) with no issues. But when I setup routing to go to a server on the other side I cannot get to it.

Here's what I have on my router:

show ip route:

10.0.0.0/8 is variably subnetted, 5 subnets, 2 masks

C 10.10.1.25/32 is directly connected, Serial0/1/0:0

C 10.10.1.24/30 is directly connected, Serial0/1/0:0

S 10.10.1.28/30 [1/0] via 10.10.1.25

S 10.30.10.55/32 [1/0] via 10.10.1.25

C 10.10.1.52/30 is directly connected, FastEthernet0/0

S* 0.0.0.0/0 [1/0] via 10.10.1.53

The 10.10.1.28 is the other side of the MPLS cloudl My side is 10.10.1.26.

I added a route for the a server on the other side of the cloud (10.30.10.55) to go through 10.10.1.25. But when I try to ping from the router to 10.30.10.55 I get the following:

ping 10.30.10.55

Type escape sequence to abort.

Sending 5, 100-byte ICMP Echos to 10.30.10.55, timeout is 2 seconds:

UUUUU

Success rate is 0 percent (0/5)

I know my routes are right, So I'm thinking there is something up with the MPLS Cloud.

Any ideas?

Thanks

Mike C.

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
Harold Ritter Thu, 05/15/2008 - 12:41

Mike,

It looks like the router on the other side doesn't have a route to this server (10.30.10.55). Is the server directly connected to this router? Who owns this router?

Regards,

MICHAEL CICCONE Thu, 05/15/2008 - 13:04

Hritter,

No, the server is connected to a switch which is connected to the router. The owner is the same company, But I don't admin the router.

What route should I have in there. Here's what I have in there now:

ip route 0.0.0.0 0.0.0.0 10.30.20.2

ip route 10.10.1.24 255.255.255.252 10.10.1.30

the second route is the route for the MPLS Circuit. Again this is the remote side, not my side.

Thanks

MIke C.

Actions

This Discussion