Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials

Standardize MAC address notation, or at least cross check variants prior to generating alerts.

In this day and age IT admins get bombarded with alerts and we are always looking for ways to filter out the noise. It looks like there is some further error checking that could be done before IPAM sends out the IP address conflict alerts. We frequently get alerted on the same MAC address conflicting with... itself.

The IP address 10.27.1.201 is in conflict. <br />The following devices were detected on network with same IP address:<br /> <br />- IPAM Reservation vs Neighbor data MAC: F0-92-1C-DF-34-81, MAC: F0:92:1C:DF:34:81

Find more posts tagged with

Status: None

Comments

nichols.356

I would definitely vote for standardizing MAC address. This also applies to other tools such as UDT. It seems that every Orion product decides how it wants to format the MAC address, and this gets rather annoying. Please, use ONE standard format. Or, maybe give us the capability to change how that standard is. Maybe I want to see MAC adddresses without any notation, maybe I want it in the format of Cisco ARP tables. Give us choices, and make it standard all across the board:

aabb.ccdd.eeff

aa-bb-cc-dd-ee-ff

aa:bb:cc:dd:ee:ff

aabbccddeeff