- Blue, 1500 points or more
I have a two cluster server running CCM 184.108.40.2062-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).
This is a Cosmetic bug;
CSCsl61950 Bug Details
Cisco Unified Reporting does not handle upper case /etc/hosts correctly
reporting app is not handling the case correctly. I changed the /etc/hosts file
to have lower case and the report is generated correctly.
mixed case chars in /etc/hosts
Further Problem Description:
3 - moderate
In Last Year
Cisco Unified Communications Manager (CallManager)
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!