Arcsight Platform : "ArcSight ESM Web App (ESM Command Center)" Can't Open ?

Dear All

I faced this ERROR while Open arcSight Platform ESM App
--> Rules #OK 


--> Active Lists #OK
--> Session List #OK
-->
 Channels # nothing ,blank 
--> Command Center # nothing  ,blank
RedirectUrl -> 
fusion-vip-ip/.../




and  I direct click to ESM Command Center ,is OK!!

Parents Reply Children
  • 0 in reply to 

    Hello Daniel 

    "Thank you very much for your response and assistance. First off, I did follow your advice and went through the manual steps.

    I've previously run ArcsightPlatform version 23.3, and everything worked just fine. However, with this version 24.1, I'm encountering OSP connection failure messages despite setting it up the same way. This is really puzzling to me.

    The Arcsight Console also logs in via OSP and the connection is fine.

    I hope this helps clarify the situation. Thanks again for your help."

    Aaron

  • Verified Answer

    +1 in reply to 

    Hi  

    You will need to upgrade your ESM to 7.7. 

    Platform and ESM now need to be kept lock-step with versions. 

    E.g. if you have platform 24.1 you need ESM 24.1 (v7.7) 

    However, in the absence of ESM being upgraded, you can still navigate to your ESM hostname to get into the original command centre 

  • 0 in reply to 

    Hi LewisJ,

    Thank you for the update and clarification regarding the ESM upgrade. I appreciate the guidance on keeping the Platform and ESM versions aligned.

    I will ensure that we upgrade our ESM to version 7.7 to maintain compatibility with the Platform. In the meantime, it's good to know that we can still access the original command center on our ESM hostname.

    Thanks again for your assistance.

    Best regards,
    aaron_hsia

  • 0 in reply to 

    It also appears there's a bug in 24.1 where if your ESM usernames aren't in 'email' format, the fusion page won't redirect you properly and you'll get an error saying user not found. At least that is what is occurring in my environment. 

    I've logged a support ticket for this. 

  • 0 in reply to 

    Hello Lewis, 

    we are aware of this issue and we are working on fixing it.

    In the meantime, the only solution in order to use the fusion integration is to accommodate the ESM usernames in 'email' format.

    Best Regards, 

    Daniel