Replacing BR100 in a branch routing szenario

  • 1
  • Question
  • Updated 4 years ago
  • Answered
I got a question:
Branch routing policy with unique subnets at every site. Let's say a DHCP-pool of 20 IPs. Now: One of the routers goes defect. (Of course, I know Aerohive devices never break, working with pixie duste etc.)
I will have to replace it.

How do I ensure it gets the same addressspace as the one I replace?

Photo of Julian Frede

Julian Frede

  • 7 Posts
  • 5 Reply Likes
  • excited

Posted 5 years ago

  • 1
Photo of Julian Frede

Julian Frede

  • 7 Posts
  • 5 Reply Likes
One should think before asking a question: The solution is simple:

Allocate local subnetworks by specific IP addresses at site. Combined with Classifier Tags.
Photo of Amanda


  • 396 Posts
  • 25 Reply Likes
Thanks for the follow up!
Photo of Jornt Weyts

Jornt Weyts

  • 26 Posts
  • 3 Reply Likes
Can anyone point me to a how-to? I'm getting mixed results.

update: my test-procedure was flawed.

When changing subnetworks remember to delete the current allocated subnetwork:
'monitor' > 'Subnetwork Allocation'

Also combine Classifier Tags AND local subnetworks. Using just local subnetworks will only work if you have 1 subnetwork defined in the network-object. It will get you in trouble when you add a second subnetwork in the same network-object later on.