Does Prognosis read the version of cucm software or is it what we put in? Reason. I have a screenshot of a CUCM showing in the thick client as CUCM 7. I assume that means version 7. when I check the version directly from the cli it says it is CUCM version 10.5. The Unity is version 11.5. Are the software version for the CUCM and the other Cisco devices supposed to be the same version? in other words CUCM version 11.x Unity version 11.x
thanks for the post but I think these are 2 different questions so maybe you could delete the second post and put this as a seperate topic, please?
If you could send the screenshot it would be easier to see what you mean. What I think is that the name of you cluster is CUCM 7 and that it does not say something about the version, but with the screenshot it will be easier.
Is there any way it could grab the wrong version? How can I trace from the Prognosis to the IP of the Callmanager....all of our checks show the version of the call manger to be 10.5 also reports dont populate and the error tells me that it is pointing to the wrong node...how can I find out what node it is pointing to. If it is pointing to the wrong node that means it is pointing to the wrong "services" correct
or could it be that the services are pointing to the wrong node. You know where you can in services go to file/action/connect to another computer...could that be pointing to the wrong place...where should it be pointing?
Can you post a screen capture or some additional information to help clarify your questions? You can determine the IP address used by selecting a cluster and then clicking on any node (pub or sub) in the cluster. The corresponding CUCM Server Summary screen will show you the IP address.
thanks for the screen capture Tonia, that helps greatly. From your screen capture, it appears your publisher is offline in Prognosis and we are not capturing its details. Perhaps the best thing to do at this point is to log a support case with an IRFAX from your environment to better allow us to investigate the reasons why it is offline. there are some settings in Prognosis as well in which we can define the cluster version but the connectivity should be addressed first.