Re: Agent Builder SNMP Get Agent

Until ITM 623 FP2, keep far far away from the limit. When you exceed it 
the TEMS involved will crash - kaboom!! APAR IV16083 resolves issue,

http://www-01.ibm.com/support/docview.wss?uid=swg1IV16083

The limit  involves how many bytes to store the list of all subnodes in a 
string. Before that fix I you are limited to 32767 bytes. Often that meant 
a limit of 600-800 subnode agents depending on the size of the managed 
system name. Sometimes customers would methodically reduce the name size 
to squeeze in more nodes.

>From ITM 623 FP2 onward - go for it.

The APAR fix is not available in the ITM 622 maintenance level.

Regards, 

  



John Alvord - Ph: 1-720-396-2788    Cell: none 
Customer Support - Tivoli Software - jalvord-r/[email protected]
Advisory Engineer - Tivoli Monitoring - ITM infrastructure
Developer Blog - Wonderful World of Situations
Follow us on Twitter! @Tivolisupport and Facebook
Personalize your support needs with the IBM Support Portal
Use Service Request to get assistance!
For emails regarding a PMR, copy [email protected]
For secure browser uploads: https://www.ecurep.ibm.com/app/upload
For Customer Support guidance: IBM Software Support Handbook









From:   Gregory Mendes <[email protected]>
To:     <[email protected]>, 
Date:   03/25/2013 09:55 AM
Subject:        [TME10] Agent Builder SNMP Get Agent
Sent by:        [email protected]



Hello All,
 
Looking for best practices/white papers when configuring the SNMP Get 
Agent.
 
Is there a subnode limitation to the agent?  I'm looking at more than 1000 
subnodes pr more on one agent. 
 
Why not multiple agents?
 
Regards,


Gregory R. Mendes
770-317-8593
_______________________________________________
TME10 mailing list
[email protected]
Unsubscribe:[email protected]

_______________________________________________
TME10 mailing list
[email protected]
Unsubscribe:[email protected]