Advertising loopback address via static routes

[wgranada1]

I have a quick question here, I have a edge router that I managed but to get to it I have to go through my corporate network. I want to add a loopback address to it so that the corporate folks can add it to their monitoring service. Once I add this loopback address to it how do I advertise it to the corporate network via static routes?

Do I just add the following

ip route 172.19.103.80 255.255.255.255 168.162.50.90

the 168 address is the default gateway

[Richard Burts]

Warren

You do not mention in your post whether this edge router runs any dynamic routing protocol with other devices in your network. If so, then it would probably be easy and appropriate to advertise the loopback via the dynamic routing protocol.

If you do not run a dynamic routing protocol then are other networks being accessed by static route? If so, what do those static routes look like?

The static route as you have it here looks fine: you have an address, and the /32 mask is appropriate for a loopback.

[edit] as I re-read your post and my response I wonder if I have misunderstood something. I am assuming that the static route would be configured on the device in the corporate network that connects to the edge router. But I wonder if you are thinking of this static route on the edge router?

There is no need for a static route on the edge router for its own loopback interface. The static route, if needed, is configured on some device that connects to the edge router. Then the static would usually be redistributed into the enterprise routing protocol so the entire enterprise would know how to reach that loopback interface.

HTH

Rick

[yagnesh_tel]

Warren,

There is nothing special about loopback interface. Just treat it like any other interface(serial/ethernet. So depending on how network prefixes for these interfaces are being advertised in your setup, you can use same method to advertise loopback interface.

Let us know if this does not answer your question.

[wgranada1]

Yes I'm not running any sort of routing protocal with my corporate network just doing static routes. Here is the current statics:

ip route 10.255.180.0 255.255.255.0 168.162.50.90

ip route 147.249.41.0 255.255.255.240 168.162.50.90

ip route 147.249.42.0 255.255.255.240 168.162.50.90

ip route 147.249.152.128 255.255.255.240 168.162.50.90

ip route 147.249.154.128 255.255.255.240 168.162.50.90

ip route 168.162.55.88 255.255.255.248 168.162.50.90

ip route 170.132.128.64 255.255.255.192 168.162.50.90

ip route 170.132.137.0 255.255.255.248 168.162.50.90

ip route 172.19.201.51 255.255.255.255 168.162.50.90

ip route 172.19.207.204 255.255.255.255 168.162.50.90

ip route 172.19.207.205 255.255.255.255 168.162.50.90

ip route 205.248.197.0 255.255.255.0 168.162.50.90

So what I put previous should work then correct?

[Richard Burts · Accepted solution]

Warren

Based on this I believe that the static route in your original post is fine and should work.

HTH

Rick

[wgranada1]

Thanks guys for your help!!! Much appreciated!!!!