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

Component Version Mismatch on CCM6.1

Hi,

I have a two cluster server running CCM 6.1.2.1122-1 (an engineering special).

The Unified CM Cluster Report generated using the Cisco Unified Reporting function reports numerous discrepancies between components running on the Publisher and Subscriber servers within the cluster.

The are over a hundred mismatches such as those shown below:

The version of hpdiags on 192.168.1.11 is 1.6.0(1) and not 7.7.0(142)

The version of hponcfg on 192.168.1.11 is 7.8.1(custom) and not 1.6.0(1)

The version of hprsm on 192.168.1.11 is 2.1.8(177) and not 7.8.1(custom)

The version of hpsmh on 192.168.1.11 is 0.101.27(1) and not 2.1.8(177)

The version of hwdata on 192.168.1.11 is 4.5(3) and not 0.101.27(1)

If you examine the reports in detail it seems that the first version entry in the first line matches the second in the second line and so on.

This leads me to conclude that this is a problem with the report rather than the cluster itself - i.e. a cosmetic bug rather than a serious problem.

Has anyone else seen this? If it is a known bug and there is a bug ID I would be grateful to know (I did search bug toolkit without success).

1 ACCEPTED SOLUTION

Accepted Solutions
Hall of Fame Super Red

Re: Component Version Mismatch on CCM6.1

Hi James,

This is a Cosmetic bug;

CSCsl71686 has been superseded by CSCsl61950 displayed below.

CSCsl61950 Bug Details

Cisco Unified Reporting does not handle upper case /etc/hosts correctly

Symptom:

reporting app is not handling the case correctly. I changed the /etc/hosts file

to have lower case and the report is generated correctly.

Conditions:

reporting app

mixed case chars in /etc/hosts

Workaround:

Further Problem Description:

Status

Fixed

Severity

3 - moderate

Last Modified

In Last Year

Product

Cisco Unified Communications Manager (CallManager)

Technology

1st Found-In

5.1(3)

6.1(1)

7.0(0.9821.2)

Fixed-In

7.0(0.39000.14)

6.1(1.9901.32)

5.1(3.9901.89)

5.1(3.2102.1)

6.1(1.2105.1)

6.1(2.1000.13)

7.0(0.66666.1)

7.0(0.66666.2)

7.0(1.11000.2)

6.1(3.9999.1)

Related Bug Information CU Reporting CM Cluster Overview component versions are out of sync

Symptom: When using Cisco Unified Reporting, after you run CM Cluster Overview report the Component versions are always out of sync. Conditions: The component versions shows which version of software components are installed on each node and this report indicates all components on all nodes are out of sync incorrectly. Inspecting via CU OS Admin CLI "show packages" indicates all components are infact in sync.

Workaround: No workaround to get this report to reliably compare all components on all nodes. This section of the report can be ignored since it is not reliably showing which components are in fact out of sync.

Hope this helps!

Rob

3 REPLIES
Hall of Fame Super Red

Re: Component Version Mismatch on CCM6.1

Hi James,

This is a Cosmetic bug;

CSCsl71686 has been superseded by CSCsl61950 displayed below.

CSCsl61950 Bug Details

Cisco Unified Reporting does not handle upper case /etc/hosts correctly

Symptom:

reporting app is not handling the case correctly. I changed the /etc/hosts file

to have lower case and the report is generated correctly.

Conditions:

reporting app

mixed case chars in /etc/hosts

Workaround:

Further Problem Description:

Status

Fixed

Severity

3 - moderate

Last Modified

In Last Year

Product

Cisco Unified Communications Manager (CallManager)

Technology

1st Found-In

5.1(3)

6.1(1)

7.0(0.9821.2)

Fixed-In

7.0(0.39000.14)

6.1(1.9901.32)

5.1(3.9901.89)

5.1(3.2102.1)

6.1(1.2105.1)

6.1(2.1000.13)

7.0(0.66666.1)

7.0(0.66666.2)

7.0(1.11000.2)

6.1(3.9999.1)

Related Bug Information CU Reporting CM Cluster Overview component versions are out of sync

Symptom: When using Cisco Unified Reporting, after you run CM Cluster Overview report the Component versions are always out of sync. Conditions: The component versions shows which version of software components are installed on each node and this report indicates all components on all nodes are out of sync incorrectly. Inspecting via CU OS Admin CLI "show packages" indicates all components are infact in sync.

Workaround: No workaround to get this report to reliably compare all components on all nodes. This section of the report can be ignored since it is not reliably showing which components are in fact out of sync.

Hope this helps!

Rob

Re: Component Version Mismatch on CCM6.1

Rob,

It has been said many times before but you are a star!

+5 and my heartfelt thanks.

Hall of Fame Super Red

Re: Component Version Mismatch on CCM6.1

Hey James,

You are most welcome my friend! It's always a pleasure to help out someone so nice, even in a very small way such as this.

Cheers!

Rob

PS: Keep up the great work!

180
Views
0
Helpful
3
Replies
CreatePlease to create content