Learn How We Can Help You Keep Teleworkers Protected During the COVID-19 Crisis

Network Change & Configuration Management

Reply
Highlighted
Accepted Solution

Discovery Status Precedence

Authority
Posts: 21
2595     1

Hello,

In documentation is information:

"An advanced setting, Discovery Status Precedence (Settings icon –> Network Automation Settings –> Advanced Settings –> Discovery group –> Discovery Status Precedence), governs the global setting for exclusion ranges. Changing this Advanced setting to Longest Prefix Match enables an exclusion range to contain smaller IP ranges that can be matched against to allow discovery—for example, you can Exclude a /23 network, but Include a /24 prefix within the EXCLUDE range, because the /24 is a longer prefix."

 

When Longest Prefix Match is choosen and in discovery ranges only CIDR are configured everything is clear but I don't know how system behave when in Discovery Range is configured also range not only CIDR, i.e.:

A: 10.0.0.0/24 INCLUDE

B: 10.0.0.2-10.0.1.0 EXCLUDE FROM DISCOVERY

 

Range B is taken into account (this is not CIDR notation)?

Less adresses than network A  - Exclude will be used?

When range B will be biger than 256 adresses than Include will be used?

 

Does anybody know how it works?

Thanks

Darek

 

Highlighted

Re: Discovery Status Precedence

Techie
Posts: 12
2595     1

Behind the scenes, everything is converted into CIDR ranges.

The option to specificy an IP range is provided for the convinience of data entry.

 

10.0.0.2-10.0.1.0 is converted into the minimal number of cidrs needed to cover that range. For example...

 

10.0.0.2/31
10.0.0.4/30
10.0.0.8/29
10.0.0.16/28
10.0.0.32/27
10.0.0.64/26
10.0.0.128/25
10.0.1.0/32

 

The above 8 cidrs are used internally to represent the range 10.0.0.2-10.0.1.0.

These are all longer prefixes than a /24, so they take precedence over 10.0.0.0/24 when the "Longest Prefix" mode is selected.

Showing results for 
Search instead for 
Do you mean 

Recommended for You