Why VMware’s Network Insight is showing a large amount of 240.240.240.240 entities

While testing out VMware’s Network Insight I noticed a large amount of source IPs showing up as 240.240.240.240. At first I didn’t recognize that address, especially since it’s a class E range.

According to VMware’s KB it’s a placeholder IP for sets of IP > 5000 addresses in order to prevent system load from becoming too high.

Further details are listed below in the article.

VMware KB: vRNI flows show IP address 240.240.240.240 (2150713)

Network Insight Networking
Tags

Fun with vSphere Tags, PowerCLI, and vRealize Operations – Part 1

One of the more powerful features that VMware has added to several product lines lately has been vSphere tags. As time has gone on support for these tags has been added to other products beyond just vSphere vCenter such as vRealize Operations and PowerCLI cmdlets. I still see engineers ask why someone would use tags instead of the older school custom attributes, so I figured I’d show how we use them in my job.

We utilize tags in two specific ways. The first is to use the tags to filter groups of VMs for PowerCLI reporting. In our case we have tags created for each Engineering team so we can customize these reports only for the virtual guests that they have access to.

The second use for these vSphere tags is to filter objects in vRealize Operations for dashboards, policies, alerts, etc. Eventually reports from vRealize Operations may even replace the PowerCLI reports since most of the properties and metrics are already collected from vCenter.

Management Operations PowerCLI vCenter

Welcome to definebroken.com

Many of us in the IT field have had the experience of customers complaining to us that this “technical thing” is broken. In turn we then usually try to narrow down the issue by replying, “Define … broken?” This site is an effort to provide some of the lessons learned, code I’ve written to solve some of these issues, and other IT related posts to share with others.

Website