IP prefix length warning
See original GitHub issueHi,
The docs mention this, and logs contain WARNING: IP prefix length of 'x.x.x.x/32' (vNIC 1 (x_NFW_3814) (vm)) does not match network prefix length 'x.x.x.x/24'
But the reported IP’s for VMWare virtual machines do not include a subnet, so IP’s collected from VMWare sources will always be /32, right? I don’t think there is a way for pyvmomi to retrieve the subnet for the IP’s of the vm’s, or am I wrong?
And as such, that warning will always be displayed.
Issue Analytics
- State:
- Created 3 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
Automatic prefix length for individual IP addresses #800
3.5" and gets told it's an error. So they enter either "1.2.3.5/32" (because it's a single IP) or a made-up prefix which does...
Read more >How can I turn off "Network netmask (prefix length) is not ...
I'm tired of getting this warning multiple times a day. ... DHCP and NAT -> Manual IP section of your router configuration in...
Read more >Wildcard Entry and Prefix Length
A wildcard IP address is the IP address of a subnetwork. ... The prefix length determines the size of the subnet and is...
Read more >Visibility of Prefix Lengths in IPv4 and IPv6
A prefix's visibility is determined by dividing the number of full peers announcing the prefix to us by the total number of full...
Read more >IPv6 prefix length of <Value1> does not match the globally ...
<Value-2> is the IPv6 prefix length configured on the BIG-IP system DB ... a related warning message is logged to the /var/log/ltm log...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Looks like this is already fixed in a more recent version. Tested on 11.1.5 and works fine there.
Great to hear.