Troubleshooting Cisco Prime Collaboration - Revision history

Chetrao at 10:09, 8 January 2013

2013-01-08T10:09:29Z

Chetrao at 10:07, 8 January 2013

2013-01-08T10:07:15Z

← Older revision		Revision as of 10:07, 8 January 2013
Line 63:		Line 63:
	see Cisco Prime Collaboration Quick Start Guide:		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</pre>		http://www.cisco.com/en/US/docs/net_mgmt/prime/collaboration/9.0/quick/start/guide/Cisco_Prime_Collaboration_9.html</pre>
-
	==== How to upgrade Cisco Prime Collaboration Provisioning from small to medium deployment model? ====		==== How to upgrade Cisco Prime Collaboration Provisioning from small to medium deployment model? ====

Line 85:		Line 84:
	#Execute cpcmdiskutil.sh under /opt/cupm (This step is to allocate extra disk space for /opt volume):<br>. cpcmdiskutil.sh /dev/sda		#Execute cpcmdiskutil.sh under /opt/cupm (This step is to allocate extra disk space for /opt volume):<br>. cpcmdiskutil.sh /dev/sda
	#Restart Provisioning services:<br>/etc/init.d/pmservers start		#Restart Provisioning services:<br>/etc/init.d/pmservers start
-	#Restart the server (vmware instance)~~<br>~~	+	#Restart the server (vmware instance)

-	==== How to upgrade Cisco Prime Collaboration Provisioning database server from medium to large deployment model? ====	+	==== 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:	+	After you upgrade the system requirements (vRAM, vCPU, vDISK and such), perform the following steps as a root user:

	#Stop the database service:<br>/etc/init.d/pmservers stop		#Stop the database service:<br>/etc/init.d/pmservers stop
Line 98:		Line 97:
	#Execute cpcmdiskutil.sh under /opt/cupm (this step is to allocate the extra disk space to /opt volume):<br>. cpcmdiskutil.sh /dev/sda		#Execute cpcmdiskutil.sh under /opt/cupm (this step is to allocate the extra disk space to /opt volume):<br>. cpcmdiskutil.sh /dev/sda
	#Restart the server (vmware instance)<br>		#Restart the server (vmware instance)<br>
		+
		+	'''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:
		+	<pre>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</pre>
		+	To configure the ip routes to the two different gateways:
		+	<pre>admin (config)# ip route <network addr> <net mask> <route-specific gateway1>
		+	admin (config)# ip route <network addr> <net mask> <route-specific gateway2>
		+	……</pre>
		+	Change the default route (0.0.0.0 0.0.0.0) to the appropriate gateway if needed.

	= User Interface =		= User Interface =

Chetrao: /* How to upgrade Cisco Prime Collaboration Provisioning database server from medium to large deployment model? */

2013-01-04T09:44:12Z

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

← Older revision		Revision as of 09:44, 4 January 2013
Line 87:		Line 87:
	#Restart the server (vmware instance)<br>		#Restart the server (vmware instance)<br>

-	==== How to upgrade Cisco Prime Collaboration Provisioning database server from medium to large deployment model? ====	+	==== 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:

	#Stop the database service:<br>/etc/init.d/pmservers stop		#Stop the database service:<br>/etc/init.d/pmservers stop
Line 93:		Line 95:
	#Rename the file as postgresql.conf:<br>mv "/opt/postgres/9.0/data/postgresql.conf.large" "/opt/postgres/9.0/data/postgresql.conf"		#Rename the file as postgresql.conf:<br>mv "/opt/postgres/9.0/data/postgresql.conf.large" "/opt/postgres/9.0/data/postgresql.conf"
	#Update the file - /opt/postgres/9.0/data/postgresql.conf:<br>In the above file, search for the word "@PORT@" and change it as - 5432		#Update the file - /opt/postgres/9.0/data/postgresql.conf:<br>In the above file, search for the word "@PORT@" and change it as - 5432
-	#Restart Provisioning services:<br>/etc/init.d/pmservers start	+	#Restart Provisioning services:<br>/etc/init.d/pmservers start
	#Execute cpcmdiskutil.sh under /opt/cupm (this step is to allocate the extra disk space to /opt volume):<br>. cpcmdiskutil.sh /dev/sda		#Execute cpcmdiskutil.sh under /opt/cupm (this step is to allocate the extra disk space to /opt volume):<br>. cpcmdiskutil.sh /dev/sda
	#Restart the server (vmware instance)<br>		#Restart the server (vmware instance)<br>

Chetrao: /* How to upgrade Cisco Prime Collaboration Provisioning database server from medium to large deployment model? */

2013-01-04T09:43:01Z

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

← Older revision		Revision as of 09:43, 4 January 2013
Line 93:		Line 93:
	#Rename the file as postgresql.conf:<br>mv "/opt/postgres/9.0/data/postgresql.conf.large" "/opt/postgres/9.0/data/postgresql.conf"		#Rename the file as postgresql.conf:<br>mv "/opt/postgres/9.0/data/postgresql.conf.large" "/opt/postgres/9.0/data/postgresql.conf"
	#Update the file - /opt/postgres/9.0/data/postgresql.conf:<br>In the above file, search for the word "@PORT@" and change it as - 5432		#Update the file - /opt/postgres/9.0/data/postgresql.conf:<br>In the above file, search for the word "@PORT@" and change it as - 5432
-	#Restart Provisioning services:<br>/etc/init.d/pmservers ~~stop~~	+	#Restart Provisioning services:<br>/etc/init.d/pmservers start
	#Execute cpcmdiskutil.sh under /opt/cupm (this step is to allocate the extra disk space to /opt volume):<br>. cpcmdiskutil.sh /dev/sda		#Execute cpcmdiskutil.sh under /opt/cupm (this step is to allocate the extra disk space to /opt volume):<br>. cpcmdiskutil.sh /dev/sda
	#Restart the server (vmware instance)<br>		#Restart the server (vmware instance)<br>

Chetrao: /* How to upgrade Cisco Prime Collaboration Provisioning application server from medium to large deployment model? */

2013-01-04T09:42:22Z

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

← Older revision		Revision as of 09:42, 4 January 2013
Line 74:		Line 74:
	==== How to upgrade Cisco Prime Collaboration Provisioning application server from medium to large deployment model? ====		==== 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:	+	After you upgrade the system requirements (vRAM, vCPU, vDISK and such), perform the following steps as a root user:

	#Stop jboss and nice services in the application server.		#Stop jboss and nice services in the application server.

Chetrao: /* How to upgrade Cisco Prime Collaboration Provisioning from small to medium deployment model? */

2013-01-04T09:41:57Z

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

← Older revision		Revision as of 09:41, 4 January 2013
Line 66:		Line 66:
	==== How to upgrade Cisco Prime Collaboration Provisioning from small to medium deployment model? ====		==== 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 ~~listed in the procedure~~:	+	After you manually upgrade the system requirements (vRAM, vCPU, vDISK and such), you must run the following scripts as a root user:

	#Execute the memorymodel.sh file under /opt/cupm:<br>./memorymodel.sh medium "-Xms512m -Xmx1024m -XX:MaxPermSize=256m -server" "-Xms512m -Xmx1024m -XX:MaxPermSize=256m" simple all		#Execute the memorymodel.sh file under /opt/cupm:<br>./memorymodel.sh medium "-Xms512m -Xmx1024m -XX:MaxPermSize=256m -server" "-Xms512m -Xmx1024m -XX:MaxPermSize=256m" simple all

Chetrao: /* How to upgrade Cisco Prime Collaboration Assurance deployment model? */

2013-01-04T09:40:20Z

How to upgrade Cisco Prime Collaboration Assurance deployment model?

← Older revision		Revision as of 09:40, 4 January 2013
Line 44:		Line 44:
	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.)		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 ~~can~~ upgrade the Cisco Prime Collaboration Assurance deployment model to medium, large, or very large using the following tuning script.	+	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.

	<br>		<br>

Chetrao: /* How to upgrade Cisco Prime Collaboration Assurance deployment model? */

2013-01-03T09:43:55Z

How to upgrade Cisco Prime Collaboration Assurance deployment model?

← Older revision		Revision as of 09:43, 3 January 2013
Line 61:		Line 61:

	For information on installing Prime Collaboration Assurance, Prime Collaboration Provisioning, and system requirements,		For information on installing Prime Collaboration Assurance, Prime Collaboration Provisioning, and system requirements,
-	see [Cisco Prime Collaboration Quick Start Guide].</pre>	+	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</pre>

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

Chetrao at 09:42, 3 January 2013

2013-01-03T09:42:16Z

← Older revision		Revision as of 09:42, 3 January 2013
Line 61:		Line 61:

	For information on installing Prime Collaboration Assurance, Prime Collaboration Provisioning, and system requirements,		For information on installing Prime Collaboration Assurance, Prime Collaboration Provisioning, and system requirements,
-	see [~~http://www.cisco.com/en/US/docs/net_mgmt/prime/collaboration/9.0/quick/start/guide/Cisco_Prime_Collaboration_9.html~~ Cisco Prime Collaboration Quick Start Guide].</pre>	+	see [Cisco Prime Collaboration Quick Start Guide].</pre>
		+
	==== How to upgrade Cisco Prime Collaboration Provisioning from small to medium deployment model? ====		==== How to upgrade Cisco Prime Collaboration Provisioning from small to medium deployment model? ====

Chetrao at 09:40, 3 January 2013

2013-01-03T09:40:14Z

← Older revision		Revision as of 09:40, 3 January 2013
Line 61:		Line 61:

	For information on installing Prime Collaboration Assurance, Prime Collaboration Provisioning, and system requirements,		For information on installing Prime Collaboration Assurance, Prime Collaboration Provisioning, and system requirements,
-	see [http://www.cisco.com/en/US/docs/net_mgmt/prime/collaboration/9.0/quick/start/guide/Cisco_Prime_Collaboration_9.html ~~www.cisco.com/en/US/docs/net_mgmt/prime/collaboration/9.0/quick/start/guide/Cisco_Prime_Collaboration_9.html~~].</pre>	+	see [http://www.cisco.com/en/US/docs/net_mgmt/prime/collaboration/9.0/quick/start/guide/Cisco_Prime_Collaboration_9.html Cisco Prime Collaboration Quick Start Guide].</pre>
	==== How to upgrade Cisco Prime Collaboration Provisioning from small to medium deployment model? ====		==== How to upgrade Cisco Prime Collaboration Provisioning from small to medium deployment model? ====

← Older revision		Revision as of 10:09, 8 January 2013
Line 98:		Line 98:
	#Restart the server (vmware instance)<br>		#Restart the server (vmware instance)<br>

-	~~'''~~How to configure a second NIC for Prime Collaboration?~~'''~~	+	==== How to configure a second NIC for Prime Collaboration? ====

-	A second NIC can be added to the Prime Collaboration as follows:	+	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	+	*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	+	*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)		*Configure the ip route gateways for the two interfaces (with the same CLI access)

-	Login as admin user and execute the following CLI commands:	+	Login as admin user and execute the following CLI commands:
	<pre>admin# configure		<pre>admin# configure
	admin (config)# interface GigabitEthernet 1 (Note that the first interface is GigabitEthernet 0)		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)# ip address <ip address> <net mask>
	admin (config-GigabitEthernet)# exit</pre>		admin (config-GigabitEthernet)# exit</pre>
-	To configure the ip routes to the two different gateways:	+	To configure the ip routes to the two different gateways:
	<pre>admin (config)# ip route <network addr> <net mask> <route-specific gateway1>		<pre>admin (config)# ip route <network addr> <net mask> <route-specific gateway1>
	admin (config)# ip route <network addr> <net mask> <route-specific gateway2>		admin (config)# ip route <network addr> <net mask> <route-specific gateway2>
	……</pre>		……</pre>
-	Change the default route (0.0.0.0 0.0.0.0) to the appropriate gateway if needed.	+	Change the default route (0.0.0.0 0.0.0.0) to the appropriate gateway if needed.

	= User Interface =		= User Interface =