Troubleshooting Cisco Prime Collaboration

From DocWiki

(Difference between revisions)
Jump to: navigation, search
m (How to verify the Cisco Prime Collaboration Assurance installation?)
m (How to verify the Cisco Prime Collaboration Provisioning installation?)
Line 28: Line 28:
   If all the processes are running, see the "Getting Started" chapter, of the Cisco Prime Collaboration 9.0 Quick Start Guide to get started with the Prime Collaboration Assurance application.
   If all the processes are running, see the "Getting Started" chapter, of the Cisco Prime Collaboration 9.0 Quick Start Guide to get started with the Prime Collaboration Assurance application.
-
==== How to verify the Cisco Prime Collaboration Provisioning installation?<br>  ====
+
==== How to verify the Cisco Prime Collaboration Provisioning installation (for advanced/standard mode)?<br>  ====
After you install Prime Collaboration Provisioning, verify if it has been properly installed.  
After you install Prime Collaboration Provisioning, verify if it has been properly installed.  

Revision as of 16:03, 17 November 2013


Contents

Installation and Upgrade

How to verify the Cisco Prime Collaboration Assurance installation (for advanced and standard modes)?

If you are unable to launch Prime Collaboration Assurance, it could be because the required processes are not running on the Prime Collaboration Assurance server.

  1. Log in to the Assurance server using the SSH service and with the CLI admin that you created during OVA configuration. By default, this username is admin.
  2. Enter the following command to display the processes that are running:

           show application status cpcm
The following is sample output of the status command, for Prime Collaboration Assurance- Advanced server:        

STAT PID USER COMMAND ELAPSED
===============================================
S<l 4337 root Decap_main 03:54:04
SNl 15925 root emsam_cdc 03:46:05
SNl 8571 root emsam_fault 03:50:27
SNl 4576 root emsam_inventory 03:53:17
SNl 4458 root emsam_mq 03:53:56
SNl 7666 root emsam_poller 03:50:47
SNl 10000 root emsam_sessionmo 03:49:57
SNl 6050 root emsam_tomcat 03:51:27
SNl 10012 root emsam_troublesh 03:49:57
SN 4438 postgres postgres 03:53:59
Process State Pid
*******    *****   ***
ESS Program started - No mgt msgs received 7505
VHMIntegrator Program started - No mgt msgs received 7534
EssMonitor Running normally 7535
InventoryCollector Program started - No mgt msgs received 7816
GpfPurgeTask Administrator has shut down this server 0
SSHD Program started - No mgt msgs received 7818
QOVRMonitor Program started - No mgt msgs received 7819
QOVRMultiProcLogger Program started - No mgt msgs received 7820
IPSLAPurgeTask Administrator has shut down this server 0
FHPurgeTask Administrator has shut down this server 0
SEGPurgeTask Administrator has shut down this server 0
IPCDiscovery Administrator has shut down this server 0
SDRPurgeTask Administrator has shut down this server 0
IVR Program started - No mgt msgs received 7834
DiagPurgeTask Administrator has shut down this server 0
IPIUDbEngine Program started - No mgt msgs received 7873
IPIUDbMonitor Running normally 8105
FHDbEngine Program started - No mgt msgs received 8106
FHDbMonitor Running normally 8240
INVDbEngine Program started - No mgt msgs received 8241
ITMDiagServer Program started - No mgt msgs received 8361
INVDbMonitor Running normally 8362
EPMDbEngine Program started - No mgt msgs received 8363
EPMDbMonitor Running normally 8514
SIRServer Program started - No mgt msgs received 8515
ITMLogServer Program started - No mgt msgs received 8658
ITMCTMStartup Administrator has shut down this server 0
DfmBroker Running normally 8660
DfmServer Running normally 8843
CSDiscovery Never started 0
DCRDevicePoll Never started 0
CSRegistryServer Running normally 8844
TomcatMonitor Running normally 8845
LicenseServer Program started - No mgt msgs received 8846
FDRewinder Never started 0
NameServer Program started - No mgt msgs received 8847
NameServiceMonitor Program started - No mgt msgs received 9108
EDS Running normally 9234
CmfDbEngine Program started - No mgt msgs received 9474
CmfDbMonitor Running normally 9649
EDS-GCF Running normally 9678
DCRServer Running normally 9679
CMFOGSServer Program started - No mgt msgs received 9883
TISServer Program started - No mgt msgs received 9884
EPMServer Running normally 10181
STServer Program started - No mgt msgs received 10303
AdapterServer Program started - No mgt msgs received 10304
VHMServer Program started - No mgt msgs received 10393
PIFServer Program started - No mgt msgs received 10394
IPIUDataServer Running normally 10639
SRSTServer Running normally 10640
FHServer Program started - No mgt msgs received 10641
QoVMServer Program started - No mgt msgs received 10642
QOVR Running normally 10935
IPSLAServer Program started - No mgt msgs received 10936
SEGServer Running normally 10937
ITMOGSServer Program started - No mgt msgs received 10938
NOTSServer Running normally 11087
PTMServer Running normally 11088
GPF Running normally 11198
TopoServer Program started - No mgt msgs received 11200
SMDBMonitor Program started - No mgt msgs received 11201
jrm Program started - No mgt msgs received 11202
DataPurge Administrator has shut down this server 0
diskWatcher Running normally 11349


The following is the output of status command for Prime Collaboration Assurance- Standard server:
STAT PID USER COMMAND ELAPSED
===============================================
S<l 4271 root Decap_main 1-23:28:00
SNl 7622 root emsam_fault 1-23:24:15
SNl 4499 root emsam_inventory 1-23:27:14
SNl 4400 root emsam_mq 1-23:27:53
SNl 6687 root emsam_poller 1-23:24:35
SNl 9444 root emsam_sessionmo 1-23:23:44
SNl 5350 root emsam_tomcat 1-23:25:17
SNl 9532 root emsam_troublesh 1-23:23:43
SN 4363 postgres postgres 1-23:27:55

The parameters in the COMMAND column are the processes that are running on the Prime Collaboration Assurance server (standard/advanced). If you do not
see all of these processes running, enter the following commands to restart the Prime Collaboration Assurance services:
<hostname>/admin#application stop cpcm
<hostname>/admin#application start cpcm

The application start cpcm/cpcmcontrol.sh start takes 10 to15 minutes for execution and

application stop cpcm/cpcmcontrol.sh stop takes 10 minutes.

3. Repeat Step 2 and check whether all of the processes are running.

    If all of the required processes are still not running on the Prime Collaboration Assurance server or if you are unable to access the Prime Collaboration Assurance URL, contact the Cisco support team.

   If all the processes are running, see the "Getting Started" chapter, of the Cisco Prime Collaboration 9.0 Quick Start Guide to get started with the Prime Collaboration Assurance application.

How to verify the Cisco Prime Collaboration Provisioning installation (for advanced/standard mode)?

After you install Prime Collaboration Provisioning, verify if it has been properly installed.

  1. In a browser, specify the IP address of the server on which Prime Collaboration Provisioning (standard/advanced) has been installed.
    The login page is displayed. Log in with globaladmin credentials.
  2. Log in to the Provisioning server using the SSH service and with the CLI admin that you created during OVA configuration. By default, this username is admin.
  3. Enter the following command to display the processes that are running:
    show application status cpcm

    bash: no job control in this shell
    httpd denotes httpd service.
    nice.sh denotes Nice service.
    startcupm.sh denotes Jboss service.
    postmaster/su denotes Postgres service.
    STAT PID USER COMMAND ELAPSED
    ===============================================
    Ss 629 root httpd 02:11:38
    S 613 root nice.sh 02:11:38
    S 610 root startcupm.sh 02:11:38
    S 608 root su 02:11:38

    The parameters in the COMMAND column are the processes that are running on the Prime Collaboration Provisioning server (standard/advanced). If you do not see the processes running, enter the following commands to restart the Prime Collaboration Provisioning services:
    admin#application stop cpcm
    admin#application start cpcm
    The above commands take one or two minutes to stop or start the Prime Collaboration Provisioning services.

You can verify if the installation is complete and successful, by checking if the JBoss service is running.
In the SSH terminal, run the following command as a root user to know if the JBoss service is running:
ps - aef|grep startcupm
You can also check at what time the JBoss service was started, in the following location (in the last line of the log file):
/opt/cupm/sep/logs/jboss.log
If the JBoss service is running, see the "Getting Started" chapter, of the Cisco Prime Collaboration 9.0 Quick Start Guide to get started with the Prime Collaboration Provisioning application.

How to upgrade Cisco Prime Collaboration Assurance deployment model?

If you need to upgrade Cisco Prime Collaboration Assurance deployment model, you must first upgrade your hardware resources, such as, vRAM, vCPU, and vDisk.

Also, you must increase the virtual disk size by adding a new vDisk. (Refer to VMware documentation to upgrade the hardware resources. Contact Cisco TAC for further assistance.)

You must login as root user and upgrade the Cisco Prime Collaboration Assurance deployment model to medium, large, or very large using the following tuning script.


# /opt/emms/emsam/bin/cpcmtuning.sh

From the options displayed, choose the deployment model (excluding option 1) that you wish to upgrade to, and then select Y to proceed with upgrading or N to reselect the deployment model.

Note:

You can upgrade Cisco Prime Collaboration Assurance server (thick provisioned format) from small to medium, large, or very large 
deployment model, using the Cisco Prime Assurance tuning script.

You can upgrade Cisco Prime Collaboration Provisioning server (thick provisioned format) from small to medium deployment model, 
using the Cisco Prime Provisioning tuning script.

However, you must manually upgrade Cisco Prime Collaboration Provisioning server medium deployment model to large deployment model. 
The procedure to upgrade Provisioning small and medium deployment models are listed in the following sections. 

For information on installing Prime Collaboration Assurance, Prime Collaboration Provisioning, and system requirements, 
see Cisco Prime Collaboration Quick Start Guide: 
http://www.cisco.com/en/US/docs/net_mgmt/prime/collaboration/9.0/quick/start/guide/Cisco_Prime_Collaboration_9.html

How to upgrade Cisco Prime Collaboration Provisioning from small to medium deployment model?

After you manually upgrade the system requirements (vRAM, vCPU, vDISK and such), you must run the following scripts as a root user:

  1. Execute the memorymodel.sh file under /opt/cupm:
    ./memorymodel.sh medium "-Xms512m -Xmx1024m -XX:MaxPermSize=256m -server" "-Xms512m -Xmx1024m -XX:MaxPermSize=256m" simple all
  2. Execute cpcmdiskutil.sh under /opt/cupm:
    . cpcmdiskutil.sh /dev/sda
  3. Restart the server(vmware instance)

How to upgrade Cisco Prime Collaboration Provisioning application server from medium to large deployment model?

After you upgrade the system requirements (vRAM, vCPU, vDISK and such), perform the following steps as a root user:

  1. Stop jboss and nice services in the application server.
  2. Go to /opt/cupm/sep/build/bin and execute vi nice.sh
  3. Modify the following line-
    JAVA_OPTS="-Xms512m -Xmx1024m -XX:MaxPermSize=256m"
    a<span id="fck_dom_range_temp_1357198455032_401" /><span id="fck_dom_range_temp_1357198455033_200" />s 
    JAVA_OPTS="-Xms512m -Xmx4096m -XX:MaxPermSize=512m"
  4. Save nice.sh file.
  5. Execute vi run.conf
  6. Modify the following line:
    JAVA_OPTS="-Xms512m -Xmx1024m -XX:MaxPermSize=256m -server"
    as 
    JAVA_OPTS="-Xms512m -Xmx4096m -XX:MaxPermSize=512m -server"
  7. Save run.conf file.
  8. Execute cpcmdiskutil.sh under /opt/cupm (This step is to allocate extra disk space for /opt volume):
    . cpcmdiskutil.sh /dev/sda
  9. Restart Provisioning services:
    /etc/init.d/pmservers start
  10. Restart the server (vmware instance)

How to upgrade Cisco Prime Collaboration Provisioning database server from medium to large deployment model?

After you upgrade the system requirements (vRAM, vCPU, vDISK and such), perform the following steps as a root user:

  1. Stop the database service:
    /etc/init.d/pmservers stop
  2. Copy the configuration file:
    cp "/opt/cupm/postgres/9.0/postgresql.conf.large" "/opt/postgres/9.0/data/postgresql.conf.large"
  3. Rename the file as postgresql.conf:
    mv "/opt/postgres/9.0/data/postgresql.conf.large" "/opt/postgres/9.0/data/postgresql.conf"
  4. Update the file - /opt/postgres/9.0/data/postgresql.conf:
    In the above file, search for the word "@PORT@" and change it as - 5432
  5. Restart Provisioning services:
    /etc/init.d/pmservers start
  6. Execute cpcmdiskutil.sh under /opt/cupm (this step is to allocate the extra disk space to /opt volume):
    . cpcmdiskutil.sh /dev/sda
  7. Restart the server (vmware instance)

How to configure a second NIC for Prime Collaboration?

A second NIC can be added to the Prime Collaboration as follows:

  • Use vSphere Client (Edit virtual machine settings option) to add a second virtual Network Adapter to the virtual machine
  • Login to the Prime Collaboration admin CLI to configure the IP address for the second interface
  • Configure the ip route gateways for the two interfaces (with the same CLI access)

Login as admin user and execute the following CLI commands:

admin# configure
admin (config)# interface GigabitEthernet 1 (Note that the first interface is GigabitEthernet 0)
admin (config-GigabitEthernet)# ip address <ip address> <net mask>
admin (config-GigabitEthernet)# exit

To configure the ip routes to the two different gateways:

admin (config)# ip route <network addr> <net mask> <route-specific gateway1>
admin (config)# ip route <network addr> <net mask> <route-specific gateway2>
……

Change the default route (0.0.0.0 0.0.0.0) to the appropriate gateway if needed.

How to change the IP Address on the Provisioning Database Server (for a Distributed Setup)?

To change the IP address:

1. Login to the server as root through SSH.

2. Edit the file network-scripts using the vi editor:

3. Go to /etc/sysconfig/network-scripts/

    a. Open the file ifcfg-eth0

    b. Modify the value for IPADDR; for example, if the database IPADDR=10.77.154.246, you must change it to a suitable database IP address.

    C. Save and close the file

4. Modify the /etc/hosts file by replacing the old database IP address entry with your new database IP address and save the file.

5. Nice system record must be updated in postgres:

    a. Login to postgres

    b. cd /opt/postgres/9.0/bin

    c. ./psql -Upmadmin -d cupm

    d. Select * from nicesyseng;

6. Find the entry which has the 'host' column as your old IP address. If there are any entries delete them by executing the following query.

delete from nicesyseng where host='<Old IP address>';

7. Restart the network:

/etc/init.d/network restart

After the network restarts, you might be logged out of server. You'd need to re-login through SSH.

In the /opt/postgres/9.0/data/pg_hba.conf file, replace the line:  host all all <ip>/32 trust with host all all <changed db-server ip>/32 trust and restart the Provisioning services.

How to change the IP Address on the Provisioning Application Server (for a Distributed Setup)?

To change the IP address:

1. Login to the server as root through SSH.

2. Edit the file network-scripts using the vi editor:

3. Go to /etc/sysconfig/network-scripts/

    a. Open the file ifcfg-eth0

    b. Modify the value for IPADDR; for example, if the application IPADDR=10.77.154.246, you must change it to a suitable application IP address.

    C. Save and close the file

4. Modify the /etc/hosts file by replacing the old application server IP address entry with your new application server IP address and save the file.

5. Nice system record must be updated in postgres:

    a. Login to postgres

    b. cd /opt/postgres/9.0/bin

    c. ./psql -Upmadmin -d cupm

    d. Select * from nicesyseng;

6. Find the entry which has the 'host' column as your old IP address. If there are any entries delete them by executing the following query.

delete from nicesyseng where host='<Old IP address>';

7. Restart the network:

/etc/init.d/network restart

After the network restarts, you might be logged out of server. You'd need to re-login through SSH.

In the /opt/postgres/9.0/data/pg_hba.conf file, replace the line:  host all all <app-server ip>/32 trust with host all all <changed app-server ip>/32 trust and restart the Provisioning services.

  • Restart the cupm-full services:
a. Log into the server using SSH. 
b. Go to /opt/cupm folder. 
c. Execute the ./cupm-full-service.sh stop command. 
d. Check whether the services are down by running the following commands: 
       ps -aef | grep startcupm
   If there are any processes running, kill those services by using the following command:
       kill -9 <processID1> <processId2> 
       ps -aef | grep nice 
   If there are any processes running, kill those services by using the following command:
       kill -9 <processID1> <processId2>
e. Check if the port 46009 is free (used by JBoss):
       netstat -a | grep 46009 
   If this port is in use, wait till it gets free. 
  • Start the application services:
*execute ./cupm-full-service.sh start
The services may take some time to start.


  • On the system where Provisioning is running, update the following files:
• /opt/cupm/sep/dfc.properties—Update the following line with the new IP address: 
   dfc.postgres.host=<DB_SERVER_ADDR> 
• /opt/cupm/jboss/server/cupm/deploy/dfc-ds.xml —Update the following line with the new IP address:
   <connection-url>jdbc:postgresql://<DB_SERVER_ADDR>:5432/cupm</connection-url>


Restart the Provisioning services.

How to change IP address on the Provisioning Server (Single Setup)?

1. Login to the server as root through SSH.

2. Edit the file network-scripts using the vi editor:

3. Go to /etc/sysconfig/network-scripts/

    a. Open the file ifcfg-eth0

    b. Modify the value for IPADDR

    C. Save and close the file

4.Modify the /etc/hosts file by replacing the old IP address entry with your new IP address and save the file. 
5. Nice system record must be updated in postgres:

    a. Login to postgres

    b. cd /opt/postgres/9.0/bin

    c. ./psql -Upmadmin -d cupm

    d. Select * from nicesyseng;

6. Find the entry which has the 'host' column as your old IP address. If there are any entries, delete them by executing the following query.

delete from nicesyseng where host='<Old IP address>';

7. Restart the network using the following

/etc/init.d/network restart

After the network restarts, you might be logged out of server. You'd need to re-login through SSH.
NOTE: You must restart the system after changing the IP address of the server.

How to change IP Address on the Prime Collaboration Assurance Server?

  1. Login to CLI as admin and execute the following command:
    IPAddress-Change/admin# conf t
  2. Execute the following configuration commands, one per line, and end each of them with "control Z".
    • IPAddress-Change/admin(config)# interface GigabitEthernet 0
    • IPAddress-Change/admin(config-GigabitEthernet)# ip
    • IPAddress-Change/admin(config-GigabitEthernet)# ip address 10.64.91.177 255.255.255.0
  3. Specify "y" when the following message is displayed: Changing the IP may result in undesired side effects on any installed application(s). Are you sure you want to proceed? [y/n] y
  4. IPAddress-Change/admin(config-GigabitEthernet)# exit
  5. IPAddress-Change/admin(config)# exit
  6. IPAddress-Change/admin# wr mem

Restart VM after IP address change and execute the script EMSAM_HOME/bin/updateJmsProps.sh

NOTE: Before you change the IP address in converged mode, the Provisioning server must be detached and browser cache must be cleared. You can then launch the server.

User Interface

How to remove the SSL certificate warning?

  • Windows Internet Explorer—You can permanently remove the SSL certificate warning by installing the Prime Collaboration self-signed certificate.
  • Mozilla Firefox—You can remove the SSL certificate warning only by adding an exception.

In Windows Internet Explorer, to remove the SSL certificate warning:

  1. Choose Continue to this website (not recommended).
  2. Choose Tools > Internet Options.
  3. In the Internet Options dialog box, click the Security tab, choose Trusted sites, and then click Sites.
  4. Confirm that the URL that appears in the field and matches the application URL, and then click Add.
  5. Close all dialog boxes and refresh the browser.
  6. Choose Certificate Error to the right of the address bar, and then click View certificates.
  7. In the Certificate dialog box, click Install Certificate.
  8. In the Certificate Import Wizard dialog box, click Next.
  9. Click the Place all certificates in the following store radio button, and then click Browse.
  10. In the Select Certificate Store dialog box, choose Trusted Root Certification Authorities, and then click OK.
  11. Click Next > Finish.
  12. In the Security Warning message box, click Yes.
  13. In the Certificate Import Wizard message box, click OK.
  14. In the Certificate dialog box, click OK.
  15. Repeat Step 2 and Step 3.
  16. Select the URL in the Websites section, and then click Remove.
  17. Close all dialog boxes, restart the browser, and invoke Prime Collaboration. See the "Getting Started" chapter of Prime Collaboration 9.0 Administration Guide for information about invoking Prime Collaboration.

If you have a safe URL implemented, do the following:

  1. Choose Tools > Internet Options.
  2. In the Internet Options dialog box, click the Advanced tab.
  3. In the Security section, uncheck the Warn about certificate address mismatch check box.

In Mozilla Firefox, to remove the SSL certificate warning:

  1. ClickI Understand the Risks >Add Exception.
  2. In the the Add Security Exception dialog box, click Confirm Security Exception.

How to configure Prime Collaboration Provisioning to synchronize a subset of subscribers from Cisco Unified Communications Manager?

The option to synchronize a subset of subscribers from Cisco Unified Communications Manager is disabled by default. To enable this feature, add the properties mentioned below in $CUPM\sep\ipt.properties file.

  • dfc.ipt.sync.users.filter.attribute.name: department
  • dfc.ipt.sync.users.filter.attribute.value: _*

Names and Values to be set in the ipt.properties file:
1. Specify the following parameters for the property dfc.ipt.sync.users.filter.attribute.name:

          a. department
         b. userid
         c. firstname
         d. lastname

2. Specify the following values for the property dfc.ipt.sync.users.filter.attribute.value:

          a. _* (this will sync only those users that have the above specified property (ex: department) value as not empty)
         b. test* (this will sync those users that have the above specified property (ex: department) value that starts with 'test')
         c. *test* (this will sync those users that have the above specified property (ex: department) value that contains 'test') 

Troubleshooting

While performing the troubleshooting workflow between endpoints, I am seeing these issues:

  • Troubleshooting status shows Errored and log tab shows Pathtrace Discovery could not be completed because of an internal error.
  • Some network nodes are missing in the path topology

If you are seeing any one of the above issues, you can check whether:

  • "utils network mtr" runs successfully between the source endpoint and destination device; where the source endpoint is a Cisco TelePresence System (CTS 500, 1000 and or 3000).
  • "systemtools network traceroute" runs successfully between the source endpoint and destination device; where the source endpoint is a Cisco C and/or EX series system.
    traceroute runs successfully between the first hop router or layer 3 switch and destination device. The first hop router or layer 3 switch is connected to either a Cisco Video Phone (89xx/99xx) Cisco Cius, Cisco Jabber video, Polycom, and/or E20.
    In addition, you must ensure that traceroute command from Prime Collaboration server to the source device works successfully where the source device is Cisco Jabber Video, Polycom, E20.
  • "systemtools network traceroute" runs successfully between the source endpoint and destination device; where the source endpoint is a Cisco MXP.

The first hop router or layer 3 switch must have the CLI Access Level RW (Prime Collaboration server > Operate > Device Work Center > Current Inventory table).

The troubleshooting status shows No CLI Access and does not allow to troubleshoot.

Check whether the source device has CLI Access Level as RW (Prime Collaboration server > Operate > Device Work Center > Current Inventory table).

Why the mediatrace or IP SLA statistics is not displayed in the troubleshooting result page?

In the troubleshooting workflow, if both the endpoints do not support five-tuple configuration, the mediatrace statistics is not displayed. In the troubleshooting workflow, if one of the endpoints support five-tuple, the mediatrace statistics is displayed.

The E20, MXP, Cisco Jabber Video, and Polycom devices does not support five-tuple configuration.

For running IPSLA VO diagnostics, you must ensure that traceroute command from source switch or router to destination switch or router runs successfully.


What happens when  Prime Collaboration Assurance server and NTP server are not synchronized?

(Applicable for Prime Collaboration 9.5)

The Oracle service fails to execute after you start the Assurance server. To resolve this issue, you must synchronize the NTP server time with the Prime Collaboration Assurance server time.

Login as root user and check for this message in the  /var/log/start_emsam.log file: "Oracle failed to start. Check your system time and NTP server configuration". Synchronize the NTP server time with the PC Assurance server time. Restart the Assurance server (using start application cpcm).


Some of the hostnames are not resolved in Prime Collaboration Assurance server, Why?

(Applicable for Prime Collaboration 9.5)

The /etc/hosts file changes after the restart. After the Prime Collaboration Assurance server restarts, the file from the storedconfig folder is synchronized with (copied to) the /etc/hosts file.

To avoid this issue and for the changes to occur immediately after restart,  whenever you add a new entry in /etc/host, you must also add the entry in /storedconfig/startup-config-xxx/etc/hosts file, so that the entry is retained and is not deleted if the PC server is rebooted. 

This issue is also applicable if the Unified CM publisher is configured using name in the CUCM section/System Server section of Prime Collaboration Administration and the name is not resolved through DNS from the Prime Collaboration Assurance server.

How to set Throttling Values for Cisco Unified Communications Managers?

The throttling values set in Provisioning must be equal to or less than the values set in Cisco Unified Communications Manager. If you change the throttling settings in Cisco Unified Communications Manager, you must also change the same settings in Provisioning.

The throttling settings in Provisioning are set in the ipt.properties file (located at /opt/cupm/sep folder).

Note: The default location for the installation directory is /opt/cupm.

The following properties (in the ipt.properties file) are used to control the write request sent to Cisco Unified Communications Manager:

   •dfc.ipt.axl.soap.MaxAXLWritesPerMinute: 20

This property specifies the default number of write requests per minute. Its value is used if there is no version or device specific value specified.

   •dfc.ipt.axl.soap.MaxAXLWritesPerMinute.ccm501: 50

This property specifies the number of write requests per minute for Cisco Unified Communications Manager version 5.0(1). Its value is used if there is no device specific value specified.

   •dfc.ipt.axl.soap.MaxAXLWritesPerMinute.<IP address>: 20

This property specifies the number of write requests per minute for a specific Cisco Unified Communications Manager indicated by the IP address.

For example, dfc.ipt.axl.soap.MaxAXLWritesPerMinute.1.2.3.4: 20 sets the value to 20 for Cisco Unified Communications Manager with the IP address of 1.2.3.4.

Describe Provisioning architecture.

Provisioning is a web-based application based on the J2EE architecture. It uses various interfaces to connect with Cisco Unified Communications applications. It does not need to deploy any agent software onto those applications’ platforms.

Provisioning uses open interfaces such as HTTP, HTTPS, AVVID XML Layer (AXL)–Simple Object Access Protocol (SOAP), SSH, and Telnet to remotely configure or query the applications being managed. Different levels of user access can be configured by the administrator.

Provisioning Interfaces:
Prime collaboration provides a graphical user interface for administration and configuration.


Rating: 0.0/5 (0 votes cast)

Personal tools