If you have an existing connection that is manually summarising a network block as 10.90.0.0/18 subnet, is it possible to use one of the subnets within that block for another remote site even though it is being advertised in the summary route or would it be easier to not summarise and increase the size if the routing table?
Its not a good design to have a discontiguous network. Accurate summarization is the key to a good network.
However it is still possible to advertise another network if you have to. If for example you have a network 10.90.10.0/24 elsewhere in the network, if you advertise it out so all other routers see it then you won't have a problem as the first routing decision is to choose the most specific route. a /24 address is more specific than a /18.
We could give better answers if we had more details about your environment and what you plan to do.
But lacking that detail I would comment that my colleagues in their answers have not taken recognition that in routing decisions the longest prefix is always chosen.
So if I understand your question correctly you are planning to summarize a group of subnets. But there is a subnet that is part of that block and is not reached out the interface where the summary will be configured. In general this will work ok.
Assuming that the routing table of the routers in the network contain both the summary route to the block of addresses and contain the route to the more specific subnet then everything should work ok.
I would agree that it is not optimum design. But when the question is will this work or not, then the answer is that it will work.
I already have 2 sites connected in a cloud. Manual summarisation is being used on the main interface to advertise the /18 routes. Unfortunately, I have to use the subnet inside this block for another site which will be connected to the 2 sites. I was wondering if I didnt use summarisation at all and had a larger routing table - would this be better than have a subnet summarised in more than one location. Which would you think would give a better design under the circumstances ?
Personally i would keep the summarised routes and advertise out your more specific one as well rather than remove all summarisation.
There are some specific advantages to summarisation, one of the key ones being that a route change in one location does not necessarily have to be propogated throughout the network with the obvious savings in bandwidth, CPU and memory usage on your routers.
You can certainly use the subnet within 10.90.0.0/18 in antoher lcoation as long as it is not present in anywhere else. As the routing table lookup is always based on longest prefix match and hence the subnet route will take preference over the summarized route.
This is neither optimul routing design, nor recommended setup.
However, its possible, the impact would be the longest prefix will always be preferred over the summarized route. Another impact would be if this Network (most specific route) always reachable, No traffic destined for the Network part of the summarized route is going to reach its destination due to the longest match preference.
Could you provide more details about the reason of having 2 Networks spilitted at different sites. I mean why you had to?
Question We run asr9001 with XR 6.1.3, and we have a very long delay to
login w/ SSH 1 or 2 to the device compare to IOS device. After
investigation, the there is 1s delay between the client KEXDH_INIT and
the server (XR) KEXDH_REPLY. After debug ssh serv...
Introduction The purpose of this document is to demonstrate the Open
Shortest Path First (OSPF) behavior when the V-bit (Virtual-link bit) is
present in a non-backbone area. The V-bit is signaled in Type-1 LSA only
if the router is the endpoint of one or ...
Hi, I am seeing quite a few issues with patch install and wanted to
share my experience and workaround to this. Login to admin via CLI, then
access root with the “shell” command Issue “df –h” and you’ll probably
see the following directory full or nearly ...