Introducing SOC Insights for BloxOne Threat Defense: Boost your SOC efficiency with AI-driven insights to eliminate manual work and accelerate investigation and response times. Read the blog announcement here.

Azure

Reply

vDiscovery on Azure in error state with overlapping VNETs error

New Member
Posts: 2
4674     1

Hi,

 

I have a question regarding a recent problem we found on our infoblox grid manager. We usually use a vDiscovery Job on our Azure Subscription to discover the network information and DNS.

 

Since we updated in a recent version of infoblox (v. 8.5.4-419474), the Azure vDiscovery job is in error state, with the following messages in the "show log debug" command:

 

[2021/09/29 15:45:57.262] (21605 <py>/infoblox/dns/bin/cdiscovery_aggregator) cdiscovery_data_aggregation.py:2013 add_message(): Overlapped VNETs encountered with direct network view mapping option, entire discovered dataset discarded. (Overlapping with existing NIOS objects)
[2021/09/29 15:45:57.263] (21605 <py>/infoblox/dns/bin/cdiscovery_aggregator) cdiscovery_data_aggregation.py:2575 _on_message(): Error during message callback : Overlapping with existing NIOS objects
[2021/09/29 15:45:57.263] (21605 <py>/infoblox/dns/bin/cdiscovery_aggregator) cdiscovery_data_aggregation.py:2576 _on_message(): CDiscoveryVpcOverlappedDataError: Overlapping with existing NIOS objects
[2021/09/29 15:45:57.264] (21605 <py>/infoblox/dns/bin/cdiscovery_aggregator) cdiscovery_data_aggregation.py:2576 _on_message(): File "cdiscovery_data_aggregation.py", line 2526, in _on_message
[2021/09/29 15:45:57.264] (21605 <py>/infoblox/dns/bin/cdiscovery_aggregator) cdiscovery_data_aggregation.py:2576 _on_message():
[2021/09/29 15:45:57.264] (21605 <py>/infoblox/dns/bin/cdiscovery_aggregator) cdiscovery_data_aggregation.py:2576 _on_message(): File "cdiscovery_data_aggregation.py", line 2000, in add_message
[2021/09/29 15:45:57.264] (21605 <py>/infoblox/dns/bin/cdiscovery_aggregator) cdiscovery_data_aggregation.py:2576 _on_message():
[2021/09/29 15:45:57.264] (21605 <py>/infoblox/dns/bin/cdiscovery_aggregator) cdiscovery_data_aggregation.py:2576 _on_message(): File "cdiscovery_data_aggregation.py", line 732, in _retrieve_missing_ipam_nviews
[2021/09/29 15:45:57.264] (21605 <py>/infoblox/dns/bin/cdiscovery_aggregator) cdiscovery_data_aggregation.py:2576 _on_message():
[2021/09/29 15:45:57.264] (21605 <py>/infoblox/dns/bin/cdiscovery_aggregator) cdiscovery_data_aggregation.py:2576 _on_message(): File "cdiscovery_data_aggregation.py", line 557, in _ensure_network_view
[2021/09/29 15:45:57.264] (21605 <py>/infoblox/dns/bin/cdiscovery_aggregator) cdiscovery_data_aggregation.py:2576 _on_message():
[2021/09/29 15:45:57.264] (21605 <py>/infoblox/dns/bin/cdiscovery_aggregator) cdiscovery_data_aggregation.py:2576 _on_message(): File "cdiscovery_data_aggregation.py", line 517, in _validate_direct_network_view_vpc_overlapped

 

It seems that we have some overlapping vnets but we cannot find which ones in the logs.

 

Could you please help us with this problem?

 

Thank you! =)

Re: vDiscovery on Azure in error state with overlapping VNETs error

New Member
Posts: 2
4675     1

Moreoever, we don't want to create a new network view.

Re: vDiscovery on Azure in error state with overlapping VNETs error

Authority
Posts: 33
4675     1

We just came across the same error today and was hoping there was an answer out there somewhere. Smiley Happy However, we're still on 8.4.7...

Re: vDiscovery on Azure in error state with overlapping VNETs error

[ Edited ]
New Member
Posts: 1
4675     1

I ran into this error today.  I imported our azure subscription into a new view and found that there were 2 subnets that existed in different azure regions in the same subscription.  My Azure guys tell me that to add a subnet to a route table, they have to add it to the vnet.  So, overlapping subnets in 3 different azure regions.  They were all subnets we had put in for Prisma when we were testing last year.  I have put in a request to have our Azure team remove the subnets from all 3 regions' vnets and I will try the discovery again tomorrow trying to pull it into our default view.  

Also, the logs wouldn't tell me which subnets were overlapping which is why I pulled it into a new view to find them manually.  

Showing results for 
Search instead for 
Did you mean: 

Recommended for You