Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. If you'd prefer to explore, try our test area to get started. And see here for current known issues.

New Member

Cisco Unity 7 port usage report errors

We're planning a migration from Call manager and Unity 7 to CUCM and Unity Connection 9.

I wanted to baseline the current voicemail port utilization on our Unity 7 systems to validate the port requirements for Connection.

However the Unity Toolkit Port Usage tool won't run properly on our systems.

We have Unity 7.0(2) mix of ES 35 and ES44

Most of the systems have an older version of the port usage tool installed. (2.0.0.2)

They return an endless set of popup warnings regarding a parsing error:

PortUsageAnalyzer "Error in ParseLogFile Routine: Subscript out of range Number =9"

One of the systems has a newer version of the port usage tool installed (2.0.0.5)

It tells me that there are no calls present in the log data. 

What irks me is that I swear that I successfully ran the port tool on this system a few months ago for another project.

So either it got upgraded to a newer version that's incompatible, or something else is wrong.

In both cases I cannot get the data I am looking for.

Any suggestions on how to get the port usage tool working with my Unity 7 system?

Can I get a copy of version 2.0.0.3 or 2.0.0.4 if they would work better?

I don't see a way to download prior versions online.

Thanks,

Vivien

1 ACCEPTED SOLUTION

Accepted Solutions
Cisco Employee

Re: Cisco Unity 7 port usage report errors

couple things I can fill in at any rate...

1. the Unity version of the port Usage Analyzer tool hasn't been touched in over 4 years (September of 2009) so it wasn't updated out from under you, I assure you!  That was when 2.0.0.5 was put out - 2.0.0.3 and 4 were only out shortly and were mostly about moving the max ports suport up to 144 and then again to 256 - no other parsing changes were made in there.

2. the reason 2.0.0.2 had to be updated along the way was because the logging format changed a couple times and parsing out the port data had to be updated to match it (this is very likely the subscript out of range error you see on 2.0.0.2).

3. One possibility - if you're running a cluster (failover) scenario the logging data does not replicate between the systems - it's worth checking both pri/sub servers.

it's possible your log files really don't contain port usage data for the timeframe you're looking for (i.e. logs get purged) - I know the first instinct is when you run a tool and it doesn't work it must be the tool that's broken but in this case the parsing is pretty straight forward.

4 REPLIES
Hall of Fame Super Silver

Re: Cisco Unity 7 port usage report errors

Unity connection ports are free so install ova template that supports as many or more ports as your current system.

Chris

Sent from Cisco Technical Support iPhone App

New Member

Cisco Unity 7 port usage report errors

That's good to know, but I was trying to model the WAN bandwidth requirement if I have my primary and secondary servers in two different sites.  The guidlelines say that you need to model that based on the number of ports configured.

I do have a clarifying question about that - will the BW need scale with the number of ports configured or the number of ports USED?  If it's the latter then I can still take your advice and just configure Maxports without worrying about blowing up the WAN link.

-Vivien

Cisco Employee

Re: Cisco Unity 7 port usage report errors

couple things I can fill in at any rate...

1. the Unity version of the port Usage Analyzer tool hasn't been touched in over 4 years (September of 2009) so it wasn't updated out from under you, I assure you!  That was when 2.0.0.5 was put out - 2.0.0.3 and 4 were only out shortly and were mostly about moving the max ports suport up to 144 and then again to 256 - no other parsing changes were made in there.

2. the reason 2.0.0.2 had to be updated along the way was because the logging format changed a couple times and parsing out the port data had to be updated to match it (this is very likely the subscript out of range error you see on 2.0.0.2).

3. One possibility - if you're running a cluster (failover) scenario the logging data does not replicate between the systems - it's worth checking both pri/sub servers.

it's possible your log files really don't contain port usage data for the timeframe you're looking for (i.e. logs get purged) - I know the first instinct is when you run a tool and it doesn't work it must be the tool that's broken but in this case the parsing is pretty straight forward.

New Member

Cisco Unity 7 port usage report errors

Thanks - I'll get the newer version on the servers with 2.0.0.2.

And your suspicion about the server with missing data was right on target -

it was in failover and I didn't think to check that beforehand.

Thanks,

Vivien

248
Views
0
Helpful
4
Replies