Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Web client Real Time Reporting problem.

Status
Not open for further replies.

MrvNDMrtN

ISP
Nov 4, 2001
34
AU
Hi,

This is regarding SWC 4.5 SU06 V1.

I suddenly got an error when loading up a skillset display in the web client.

Apparently i've reached a unicast session limit on the server.

I can see the number is 30 sessions and i am thinking that is a bit low. But it also says before changing these settings that i should consult my design guidelines to make sure its within range.

Can i just up to figure to an arbitrary number?

Thanks,

What the?!?!
 
Why are you using UNICAST, should really be MUTICAST.

Unicast places large loadings on the server CPU and increases significantly the amount of data on the LAN.

That's why there is a unicast limit, unwise to proceed without specialist analysis.
 
Captain (as usual) is right, Mulitcast is preferred. However, it is usually not configured (by default) on switches and getting IT people to change the programming can be futile.

These days the load on the CPU is probably not a factor. The increased unicast traffic on the LAN, though, may get you in trouble with your IT people. I would increase the value slightly to see if any issues arise. I would also encourage users not to leave RTDs up if they are not actively using them.
 
The guys are right...multicast is the way to go provided you can talk your network types into allowing multicast traffic...if not, you're stuck with unicast.

One thing you might try if you don't want to bump the sessions up is restart the RTR service by ticking the "restart real time reporting service" box in the RTR setup page and click OK. That will reset all the sessions. Of course you'd need to do this during a quiet time.
 
When looking at the number of sessions to set, you need to realise that one user doesn't necessarily equal one unicast session.

Without referring back to the NTP, I think that you use one unicast session for every type of stat (agent, skillset, application, ivr, route, nodal) and also if it's moving window or interval to date.

So, in theory a particularly zealous individual (with a plasma screen for a monitor!) could be using 12 unicast sessions!!

(Anybody correct me if this isn't right)

DD
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top