Welcome Serena Central users! CLICK HERE
The migration of the Serena Central community is currently underway. Be sure to read THIS MESSAGE to get your new login set up to access your account.
rogsa Absent Member.
Absent Member.
1305 views

Broker performance in large OES2 network

I have seen the Novell recommendation to use only one broker per network in OES2 (Considerations in deciding the number of iPrint Brokers/Driver Stores) and I was wondering if there are any performance issues with this in really large networks? We are planning to migrate to OES2 on a 380 server, 50000+ client network. Is there anyone out there who knows if this will choke a single broker?

CNE3,4,5,6, HP ASE Ask me about NetWare before V1.0 Advanced! I know HP, DELL, IBM and a few other languages 😄
0 Likes
4 Replies
Anonymous_User Absent Member.
Absent Member.

Re: Broker performance in large OES2 network

rogsa,

It appears that in the past few days you have not received a response to your
posting. That concerns us, and has triggered this automated reply.

Has your problem been resolved? If not, you might try one of the following options:

- Visit http://support.novell.com and search the knowledgebase and/or check all
the other self support options and support programs available.
- You could also try posting your message again. Make sure it is posted in the
correct newsgroup. (http://forums.novell.com)

Be sure to read the forum FAQ about what to expect in the way of responses:
http://forums.novell.com/faq.php

If this is a reply to a duplicate posting, please ignore and accept our apologies
and rest assured we will issue a stern reprimand to our posting bot.

Good luck!

Your Novell Product Support Forums Team
http://support.novell.com/forums/

0 Likes
Not applicable

Re: Broker performance in large OES2 network

rogsa;1718359 wrote:
I have seen the Novell recommendation to use only one broker per network in OES2 (Considerations in deciding the number of iPrint Brokers/Driver Stores) and I was wondering if there are any performance issues with this in really large networks? We are planning to migrate to OES2 on a 380 server, 50000+ client network. Is there anyone out there who knows if this will choke a single broker?


Would I be right in saying the main job of broker is driver delivery, which is only done at printer installation time, so unless all your clients are installing printers at the same time, surely broker performance is not that much of a worry? Or did you mean Manager rather than Broker?

Cheerz
IanB
0 Likes
Marcel_Cox Absent Member.
Absent Member.

Re: Broker performance in large OES2 network

ibelton wrote:

>Would I be right in saying the main job of broker is driver delivery,
>which is only done at printer installation time, so unless all your
>clients are installing printers at the same time, surely broker
>performance is not that much of a worry?


Actually, that is only the case for NDPS. For iPrint, the Broker does not
even need to be active at pritner installation time. In fact, the server
running the Manager will load a special ipp cache module which will cache
all used drivers locally. In other words, each manager just needs to
download each driver from the broker just once, even if 1000 users use
that driver. As such, the Broker (and the driver store on Linux) receive
very little traffic and all traffic just comes from the managers.

--
Marcel Cox
http://support.novell.com/forums
------------------------------------------------------------------------
Marcel Cox's Profile: http://forums.novell.com/member.php?userid=8
0 Likes
Highlighted
rogsa Absent Member.
Absent Member.

Re: Broker performance in large OES2 network

Should be okay with just the one broker then. We still plan to put it on a cluster for the sake of high availability.
We will now have to migrate our 220 current NDPS/iPrint brokers to a single iPrint broker, then to a single driver store in OES2.

Thanks guys

CNE3,4,5,6, HP ASE Ask me about NetWare before V1.0 Advanced! I know HP, DELL, IBM and a few other languages 😄
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.