I am having trouble with Celerra Manager response times, any settings I can do to help?

I am having the same issue w/ IE8 and Firefox...just slow when clicking on any item in Celerra Manager...takes like 10 seconds ++ to load anything up..I don't think its a network issue, just maybe something to tweek on the browser side to help? thanks,

Tags (2)
0 Kudos
7 Replies
SAMEERK1
3 Argentium

Re: I am having trouble with Celerra Manager response times, any settings I can do to help?

As per the release notes, the IE8 is still not supported by Celerra manager hence I suggest you to try it by using the IE6 and test the same,

check also if you have too many old alerts showing up in the Celerra manager and if you can clean up few of old alerts.

0 Kudos
Rainer_EMC
5 Osmium

Re: I am having trouble with Celerra Manager response times, any settings I can do to help?

what Celerra model?

0 Kudos

Re: I am having trouble with Celerra Manager response times, any settings I can do to help?

NS-120’s running Celerra Manager Advanced Edition v. 5.6

0 Kudos
Rainer_EMC
5 Osmium

Re: I am having trouble with Celerra Manager response times, any settings I can do to help?

ok - no gateway - there was a bug delaying startup with NS-G2/8 recently

0 Kudos
dynamox
6 Thallium

Re: I am having trouble with Celerra Manager response times, any settings I can do to help?

reboot the control station, see if it helps. Celerra Manager is notoriously slow and the more objects it manages the slower it gets.

0 Kudos
Rich_Bai
2 Bronze

Re: I am having trouble with Celerra Manager response times, any settings I can do to help?

It appears that some suggestions have been given for the question you asked. Are they helpful? If so, please mark the question as "Answered".

Your feedback and response is appreciated.

Thanks!

0 Kudos
ScottHolmanBG
1 Copper

Re: I am having trouble with Celerra Manager response times, any settings I can do to help?

we've a pair of NS-G8's that have always had problems with delayed response times. one more that the other actaully. we're currently on 5.6.47-11. In which code level is this resolved?

cheers

0 Kudos