Any suggestions on how to limit the neigbors on an Ethernet OSPF session? I have a router that I not only want to act as DR, but I want all other routers on that Ethernet to connect to it and it alone...not each other.

_________________
Find networking-forum.com on Facebook, LinkedIn, Twitter, Google+,or subscribe to the site's RSS feeds.

There are a few ways to go about doing this.

Cant remember off the top of my head 100% on this for a broadcast network type. However set all the other Routers OSPF to priority 0 is one possible way. I will have to check this one out later to be sure.

Another would be to set up an access list to accept 224.0.0.6 sourced from DR router only.

Also you could go about using a non broadcast network type and staticly setting the DR router with priority under the OSPF config. This would be quite a bit of admin overhead.


DP

_________________
"Knowledge is contagious, infect"

Well ... I'm sure you know to set the priority up on the desired DR router and then cycle the OSPF processes. That will get your DR elected.

May I ask why you don't want neighbor relationships with the other routers on the segment?

mr

_________________
*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*
Mark Alan Rohlf, MIT, CCNA, CCAI
Network Administrator - Memorial Health Systems
"Batches? We don' need no steenking batches!"

This would work ... but wouldn't it chew up CPU utilization?

_________________
*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*
Mark Alan Rohlf, MIT, CCNA, CCAI
Network Administrator - Memorial Health Systems
"Batches? We don' need no steenking batches!"

All depends on what the router is and what the router is doing.


DP

_________________
"Knowledge is contagious, infect"

I'm sure you have your reasons for doing thins, but you're killing the redundancy by doing it you realize? If your DR fails and things move to the BDR the other rouers on the segment aren't going to be able to talk to it.

My $0.02

It's a hard scenario to explain...it's Ethernet over wireless and each OSPF neighbor except the DR should act like a stub. We can't use static routes because the Ethernet of the customer router does not go down when the wireless link goes down.

_________________
Find networking-forum.com on Facebook, LinkedIn, Twitter, Google+,or subscribe to the site's RSS feeds.

is this in a multi-vendor environment?

I just wonder if EIGRP might provide more efficient use of bandwidth.

mr

_________________
*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*
Mark Alan Rohlf, MIT, CCNA, CCAI
Network Administrator - Memorial Health Systems
"Batches? We don' need no steenking batches!"

A thought....

Now this isn't the cleanest way, or most efficient approach to this issue, but if your DR has some resources to spare, then this could be a solution.

Run seperate OSPF processes for each neighbour, and the redistribute as needed

Yeh, I know, ugly ugly ugly. It would work though




Then do just that... Make them stub areas. Grantd your gonna chew up a couple of subnets... And from the sounds of things you'll have to use subinterfaces on a single ethernet interface... But I can't thin of any reason wy it shouldn't work.

Again I don't think this is a very clean way of doing things, but it could be hacked together to work.