ArcSight Ideas - TEMPORARILY CLOSED
cancel

Individual Connector Management inside a Container

Hi Friends,

Raising this issue as a feature request based on the below issue recently brought up faced by many of us. We know the Container is the logical grouping of Connectors.

Issues:

Any changes to individual connector-> requires the container restart

Any issues with a single connector degrades the container.

If a single connector is down, it requires the entire container to restart.

Being the Single point of failure the Connectors inside the container requires container restart is not a good thing.

Need more Connector commands than container commands.

Request:

Individual Connector Management for all the Connectors inside the Containers.

Open for more Suggestions

Cheers,

Bala

2 Comments
Contributor.

Yup !

this is the one actually messing around for so many days!!

Hope - Hp will look into it !

regards,

Super Contributor..

We thought of differentiating 32 and 64 bits connectors so we placed each connector in one container and we overruled above situation (connector management), we have added 20 containers containing each connector in it so that its manageable individually.

However i have noticed if we scan the complete remote mgmt range at one stretch, connector inside the container will jump to other preceding container if the container is empty and ticket is raised with support, it’s been long time!!!

One more thing i have noticed, not able to add more than 20 containers in a single connector server,  sometimes its unpredictable, ticket is raised with support, it’s been long time again!!!

Regards, Ismail