Log Change Messages - Advanced VLAN's on NIC (Trunking) to Monitor Multiple Subnets

[Daweeze]

Hello,

I am using the Trial of the UltraMon3 Plug-In for the first time and this Plug-In is fantastic! That said, I have run into something. It appears the discovery process is constantly running as part of the PI functionality. I have a unique configuration that I suppose is not typical. I am using the VLAN Functionality of the Network Adapter to monitor multiple subnets without adding a secondary NIC (Trunking). The trouble is that this creates a duplicate MAC Address for both Subnets for both the Router as well as the NIC on my HS3 Server. This is typical if the Physical Source Port and the Destination Port are the same (one wire between hardware). Hence, my logs are filled with this:

Sep-16 5:51:08 AM Informational Host 44-D9-E7-07-DE-3E changed from 192.168.5.1 to 192.168.3.1
Sep-16 5:51:08 AM Informational Host 00-23-24-41-FB-D7 changed from 192.168.5.3 to 192.168.3.3
Sep-16 5:50:31 AM Informational Host 44-D9-E7-07-DE-3E changed from 192.168.3.1 to 192.168.5.1
Sep-16 5:50:26 AM Informational Host 00-23-24-41-FB-D7 changed from 192.168.3.3 to 192.168.5.3
Sep-16 5:48:36 AM Informational Host 44-D9-E7-07-DE-3E changed from 192.168.5.1 to 192.168.3.1
Sep-16 5:48:36 AM Informational Host 00-23-24-41-FB-D7 changed from 192.168.5.3 to 192.168.3.3
Sep-16 5:47:59 AM Informational Host 44-D9-E7-07-DE-3E changed from 192.168.3.1 to 192.168.5.1
Sep-16 5:47:54 AM Informational Host 00-23-24-41-FB-D7 changed from 192.168.3.3 to 192.168.5.3
Sep-16 5:46:05 AM Informational Host 44-D9-E7-07-DE-3E changed from 192.168.5.1 to 192.168.3.1
Sep-16 5:46:05 AM Informational Host 00-23-24-41-FB-D7 changed from 192.168.5.3 to 192.168.3.3
Sep-16 5:45:28 AM Informational Host 44-D9-E7-07-DE-3E changed from 192.168.3.1 to 192.168.5.1
Sep-16 5:45:23 AM Informational Host 00-23-24-41-FB-D7 changed from 192.168.3.3 to 192.168.5.3
Sep-16 5:43:33 AM Informational Host 44-D9-E7-07-DE-3E changed from 192.168.5.1 to 192.168.3.1
Sep-16 5:43:33 AM Informational Host 00-23-24-41-FB-D7 changed from 192.168.5.3 to 192.168.3.3
Sep-16 5:42:56 AM Informational Host 44-D9-E7-07-DE-3E changed from 192.168.3.1 to 192.168.5.1
Sep-16 5:42:51 AM Informational Host 00-23-24-41-FB-D7 changed from 192.168.3.3 to 192.168.5.3
Sep-16 5:41:02 AM Informational Host 44-D9-E7-07-DE-3E changed from 192.168.5.1 to 192.168.3.1
Sep-16 5:41:02 AM Informational Host 00-23-24-41-FB-D7 changed from 192.168.5.3 to 192.168.3.3
Sep-16 5:40:25 AM Informational Host 44-D9-E7-07-DE-3E changed from 192.168.3.1 to 192.168.5.1
Sep-16 5:40:20 AM Informational Host 00-23-24-41-FB-D7 changed from 192.168.3.3 to 192.168.5.3
Sep-16 5:38:30 AM Informational Host 44-D9-E7-07-DE-3E changed from 192.168.5.1 to 192.168.3.1
Sep-16 5:38:30 AM Informational Host 00-23-24-41-FB-D7 changed from 192.168.5.3 to 192.168.3.3
Sep-16 5:37:53 AM Informational Host 44-D9-E7-07-DE-3E changed from 192.168.3.1 to 192.168.5.1
Sep-16 5:37:49 AM Informational Host 00-23-24-41-FB-D7 changed from 192.168.3.3 to 192.168.5.3

Is there any way to stop the reporting of this and also keep the PI Device association set to a specific IP address? Black List? I really don't want to add another NIC to the HS3 PC just to get a new set of MAC Addresses to eliminate this.

Thanks for your help!

-Travis

[jrv]

Maybe IP aliases would be easier here.

Is every hardware ethernet port VLAN capable and aware? Is VLAN support enabled on the system hosting HS?

I think either the HS3 server's NIC doesn't do VLANs, or the operating system on the HS3 server isn't properly configured.