Monday, July 31, 2017

Coming back from vacation and Cisco's Collaboration Solutions Analyzer

I spent the last week on vacation in Birch Bay, Washington. It's a little town just 5 miles south of the US/Canada border. We had very little to no cell phone service and no internet so this was a great vacation. The sunsets were fabulous!

I wanted to read up on Expressways and all sorts of other things but I skipped all of that hub-bub and just enjoyed the slow pace of doing nothing. I avoided tech except to play SimCity Build-It in offline mode :)   All of that to say that the fam did not want to kill me as I was previously worried about.

So what happens at work when you are the only one minding the shop and you are gone for a week? Thankfully not too much. So today being my first day back at work I had a few emails to parse but moved through them quickly. Now I'm looking for things to work on.

Collaboration Solutions Analyzer - the greatest thing ever?

Has anyone ever seen this? Collaboration Solutions Analyzer (Cisco how to use) is something I found before I left and took a cursory look at today. The doc I liked explains it pretty well, but of course I'm going to add my bits here.

Take a diagnostics log from your your Expressway, VCS-C, Conductor or even most endpoints and this puppy will parse out all the goodies that you probably need to know. The keen folks at Cisco TAC built this and must have had it in their secret weapon toolbox

I decided to make a few calls, gathers a couple of logs and see what it tells me. The first thing that popped up from a log captured on my VCS-c is this: POTENTIAL PROBLEMS!

Right there, the CSA tool tells me there might be some problem I didn't even know about. This is very cool. By following the link right there I was able to see what it was and in this case completely did not apply, but I like knowing that CSA can identify something I might not otherwise be looking for.

There is so much more to like in the CSA that I'm going to have to use it more and include it in the troubleshooting processes we use.
I will probably even write about it more later.

No comments:

Post a Comment

Note: Only a member of this blog may post a comment.