لطفا منتظر باشید ...
Identify the Implementation Tools
All the CallManager servers in a cluster must have the same CallManager OS version, CallManager application version, and SQL server version for successful operation. In a large network deployment, in the initial stages of implementation or during major upgrades, you could miss upgrading one server or applying a hot fix on one or more servers. This section discusses how to check the CallManager OS, CallManager, operating system, and SQL server versions and identify inconsistencies in software versions.
Checking the CallManager OS Version
To check the CallManager OS that is running on the CallManager servers, choose Start > Cisco OS Version. The MCS Version Utility displays the CallManager OS version, as shown in Figure 8-18. Notice that the base OS version is 2000.2.4 and that it has been upgraded to 2000.2.6.
Figure 8-18. Checking the Cisco CallManager OS Version
Checking the CallManager Version
To check the CallManager version that you are running in the cluster, on the CallManager Administration page, click the Details button. Figure 8-19 shows the dialog box displaying the CallManager version, 4.0(1), and the active CallManager database name in use, which is CCM0300. You need to provide this information to Cisco personnel when you report problems with CallManager.
Figure 8-19. Checking the Cisco CallManager Version
[View full size image]
Checking the SQL Version
To check the SQL version that is running on the CallManager servers, choose Start > Programs > Microsoft SQL Server > Query Analyzer and enter the query statement select @@version, as shown in Figure 8-20. SQL Query Analyzer displays the SQL version in the result window. In Figure 8-20, the SQL version is 8.00.760.
Figure 8-20. Checking the Cisco CallManager SQL Version
[View full size image]
Database Layer Tool to Check SQL Subscriptions
The DBL Helper tool diagnoses problems and restores replication in the CallManager database. To run the DBL Helper tool, run the DBLhelper.exe file located in the C:\Program Files\Cisco\Bin directory on the publisher server.NoteIf you do not have this tool installed on the publisher server, contact Cisco TAC to obtain this tool and copy it into the previously mentioned folder.Figure 8-21 shows the interface for the DBL Helper tool. The tool has four tabs:SQLReplicationNameResolutionCompare DBExport/Import Data
Figure 8-21. DBL Helper Tool
[View full size image]
Checking Inconsistencies in the Software Versions Within the Cluster
To check for inconsistent versions of different components within a CallManager cluster, on the CallManager Administration page, choose Help > Component Versions and click the Out of Sync link. If you see inconsistencies, you should examine the files that are not consistent and resolve the issue.
Multi-Level Administration Tool
The CallManager Multi-Level Administration (MLA) tool provides different levels of permission and access privileges to CallManager Administration and Serviceability pages. Prior to the release of the MLA tool, access to the CallManager Administration and Serviceability interfaces was global in nature and used basic Windows NT authentication. With this authentication method, all pages were available to anyone who logged in. There was no way of providing the granular access to these pages to classify administrators based on their responsibilities.In large-scale IPT deployments, companies typically subcontract the deployment of IP Phones to other vendors. Using the MLA tool, the CallManager administrator can create different users and assign privileges to those users that limit them to just configuring and managing the IP Phones. The CallManager administrator can also use the MLA tool to track the changes made by the implementation team.The MLA tool offers the following benefits:Keeps a log of changes made by different administratorsMaintains audit logs and login attempt logs:The audit logs keep track of the configuration changes to the CallManager Administration page and Serviceability page.The login attempt logs keep track of authentication attempts.
For CallManager versions prior to 4.0, MLA was available in a separate software package. Starting with CallManager 4.0, MLA is included in the CallManager software, and no separate installation is required.To enable the MLA feature in CallManager 4.0, on the CallManager Administration page on the publisher server, choose User > Access Rights > Configure MLA Parameters and set the Enable MultiLevelAdmin parameter to True. When you set the parameter to True, the web page prompts you to set the CCMAdministrator password. After you enable the MLA feature, use the user ID CCMAdministrator and the password you have entered to access the CallManager Administration pages.You have to restart the web service on all the servers in the cluster after enabling the MLA feature. Use the CCMPwdChanger.exe tool discussed in Chapter 9 to reset the password for the CCMAdministrator user.
Functional Groups
The functional groups in MLA comprise different CallManager administration functions. The standard functional groups predefined are as follows:Standard Plug-InStandard User Privilege ManagementStandard User ManagementStandard FeatureStandard Service ManagementStandard ServiceStandard ServiceabilityStandard GatewayStandard Route PlanStandard Phone
These standard functional groups contain predefined menu pages that users can access. For example, users who have full access to the Standard Plug-In group have permissions to access the CallManager Install Plugins pages; users who have full access to the Standard Phone functional group have access to all the pages in CallManager Administration that allow them to modify, create, and add phones.You can create new functional groups based on the predefined functional groups. However, you cannot modify the predefined functional groups.
User Groups
User groups define the access privileges to various functional groups and users who have access to the functional groups. The following user groups are predefined:Gateway AdministrationPhone AdministrationRead OnlyServer MaintenanceServer MonitoringSuper User Group
You can assign a user to multiple user groups; the users in the Super User Group have full access. You cannot delete the Super User Group.
Access Levels
By using the MLA authentication method, any user who attempts to access a CallManager menu or web page will be allowed one of three access levels:Full Access Can perform all functionsRead Only Access Cannot make any changesNo Access Cannot even view the page
You can assign these access privileges to the functional groups.The View Privileges Report prints all the user groups that are defined with their associated functional groups and privileges. This report will assist in troubleshooting problems with access privileges to different functional groups.
MLA Logs
By default, the debug level in MLA is set to None. To enable full logging so that you can see the changes that the other administrators are making to the system, change the debug level to Debug. To access the debug level parameter, on the CallManager Administration page, choose User > Access Rights > Configure MLA Parameters.MLA stores the log files in the C:\Program Files\Cisco\Trace\MLA directory. The PermissionsXXXXXX.txt file contains debug information. The AccessXX.log file contains login attempts of users and changes made by these users while they are logged in to CallManager web pages.
