topic RE: Duplicate system on Dragon system dashboard in Security

Duplicate system on Dragon system dashboard

ESI_SEG — Tue, 29 Oct 2013 22:52:00 GMT

On the dragon system dashboard, I see two systems with the same name but one is unavailable. How can I delete the unavailable system that is duplicated and doesn't make sense? Thanks

RE: Duplicate system on Dragon system dashboard

Doug — Tue, 29 Oct 2013 23:27:00 GMT

Hello, You can right-mouse on the icon in the dashboard view and select 'delete' To prevent it from coming back, ensure the /etc/hosts has only one ip-to-hostname entry that represents the correct ip/hostname of this system. Regards, Doug Hyde Sr Support Engineer Enterasys Networks

RE: Duplicate system on Dragon system dashboard

ESI_SEG — Tue, 29 Oct 2013 23:36:00 GMT

Hi I don't have that option when I select the sensor with status unavailable. The only option is export to .csv. I ensure that our /etc/hosts doesn't have any entry regarding this sensor. Thanks in advance Best regards

RE: Duplicate system on Dragon system dashboard

Doug — Wed, 30 Oct 2013 03:25:00 GMT

Hello, If you can send me your contact details I will have one of our GTAC Dragon Support Engineers reach out to you directly. We should be able to setup a remote screen sharing session via LogMeIn and correct the issue. My direct email: dhyde@enterasys.com Regards, Doug Hyde Sr Support Engineer Enterasys Networks

RE: Duplicate system on Dragon system dashboard

Doug — Thu, 31 Oct 2013 20:52:00 GMT

Hello, A GTAC case ticket has been opened to track this issue. One of our Dragon Support Engineers will reach out to you directly. Once we find a resolution, we will post that resolution here on The Hub. Doug Hyde Sr Support Engineer Enterasys Networks

RE: Duplicate system on Dragon system dashboard

Mullins__Keith — Thu, 07 Nov 2013 23:50:00 GMT

summary of resolution --------------------------- we removed the duplicate system directly from the mysql db, and reassigned all interfaces and virtualsensors pointing to the deleted duplicate system to the active system. restarted jboss and dragon2mysql, and the nodes are now all green with the correct event/heartbeat timestamps.