Hello All,

Is there a script that I can execute to determine the overall performance of the BES server as well as the health, on a daily basis?

Regards,

Unfortunately not; there is no silver bullet for this. There are monitoring / management products that will do log analysis along with WMI performance monitoring, but you've got to pay for it.

I think most importantly you should on a daily basis:

1) Review support cases logged regarding your BES / BlackBerry users
2) Review the ALRT log on the BES. A lot gets logged there that isn't critical / indicating a failure but its a good habit to get in to.

This'll let you know if your users are complaining and if your BES is complaining. Sure there is a lot you can do with perfmon counters and advanced log review and using the BRK tools ... but this is a quick way to see if there is something going on.

Are you seeing specific problems you're looking to pin down?

__________________
http://blog.port3101.org/hdawg/

Thanks for the feedback...actually I'm not looking at specific problems at all...I was just curious if there was a script...it would have been good to have that in hand in case I need it....

RIM has an excellent little too we call the Log Parser. It is web driven and automated - all you do is upload a single log or the entire days logs as a .zip and the parser will pull each entry that has a related KB, explain the log entry and link you to the appropriate knowledge base article - it takes all of 5 minutes to completely parse a days logs and the feedback is invaluable.

Is this strictly for RIM internal use?

__________________

Technically, it is a breach for me to mention it outside of RIM, but as a tool for administrators I feel it should be open - especially if you are paying for support.

I never understood why we give a 72 hour turn around time for a process that literally takes less than 10 minutes. I guess they assume that knowledge of the log parser would generate a flood of log review requests.

I guess this information is most useful to admins who are calling RIM and are ultimately asked to upload their logs for review - just mention you will be happy to wait while they run your zip through the log parser.

Oh, that is unless you don't pay for the "direct to analyst" support package - in that case you will be speaking with an employee of Sykes International, who will take a half an hour to collect your environment information and attempt to set up a 2 day call back

sweet tool!

I wish things like this were publicly available ... but then I guess if it were there would be less T-Support calls and less potential revenue from support / services.

__________________
http://blog.port3101.org/hdawg/

Nice, so just zip the log files, call T-Support, and ask them to run the files thru the Log Parser?

__________________
You may know me as Juwaack68

Does this mean we will no longer be friends Joolie?

__________________
http://blog.port3101.org/hdawg/

You can't get rid of me that easily

__________________
You may know me as Juwaack68

You will more than likely be told that the tool either does not exist or is otherwise not available and that an analyst will get back to you in a few days - this tool has been around since 2007 and its a very well kept secret - like hdawg said, this tool is only a revenue generator for RIM if the customer base is dependent on them for log review support.
They cut down on operational costs by providing an automated system to technicians - an actual "analyst" very rarely reviews logs unless an admin as really screwed the pooch.

This tool is neat but when I worked at RIM the use of that tool was taken away from the frontline reps as too many were not troubleshooting and just getting logs, which sometimes leads to looking for/at things that were not the issue.

I find that the tool was good for finding some things quickly but if you know what to look for you can find things just as quick with the right search strings.

The tool actually came out in 2006. When I started Server support in 06, my trainer was one of the head people working on the parser.

But it would be neat to have something similar. If you have any experience looking at logs you could create your own. all you need are search strings to look for.

Things have changed since I left in 2007 though. I'm not sure if they have given the use of the tool back to the reps but as long as it is used properly and not abused it can really help the troubleshooting process.

... any news if the parser became available to public? :P

probably around the time of never I think we can all safely assume.

__________________
http://blog.port3101.org/hdawg/