Cisco Unified MeetingPlace Release 8.0 -- Upgrading to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0 - Revision history

MeetingPlace Moderator: /* Related Topics */

2012-10-31T20:47:43Z

MeetingPlace Moderator: /* Troubleshooting */

2012-10-31T20:45:27Z

Troubleshooting

← Older revision		Revision as of 20:45, 31 October 2012
Line 322:		Line 322:
	# Synchronize the Hardware Media Server and meeting types.		# Synchronize the Hardware Media Server and meeting types.
	# Put the Audio Blade back online.		# Put the Audio Blade back online.
		+
		+
		+	===== What To Do Next =====
		+
		+	If you have already applied the Cisco WebEx Security Certification patch to your Cisco Unified MeetingPlace system and then upgraded to an 8.0 release, then you must reapply this patch following your upgrade.
		+
		+	For more information on this Cisco WebEx Security Certification Patch, see:
		+	* http://customercare.corp.webex.com/commcal/archives/type_informational/006535.php
		+	* http://docwiki.cisco.com/wiki/Cisco_Unified_MeetingPlace_-_WebEx_Certificate_Upgrade

MeetingPlace Moderator: /* Troubleshooting Tips */

2012-10-31T20:45:04Z

Troubleshooting Tips

← Older revision		Revision as of 20:45, 31 October 2012
Line 262:		Line 262:
	#Synchronize the Hardware Media Server and meeting types.		#Synchronize the Hardware Media Server and meeting types.
	#Put the Audio Blade back online.		#Put the Audio Blade back online.
		+
		+	===== What To Do Next =====
		+
		+	If you have already applied the Cisco WebEx Security Certification patch to your Cisco Unified MeetingPlace system and then upgraded to an 8.0 release, then you must reapply this patch following your upgrade.
		+
		+	For more information on this Cisco WebEx Security Certification Patch, see:
		+	* http://customercare.corp.webex.com/commcal/archives/type_informational/006535.php
		+	*http://docwiki.cisco.com/wiki/Cisco_Unified_MeetingPlace_-_WebEx_Certificate_Upgrade

	===== Troubleshooting Tips =====		===== Troubleshooting Tips =====
	* See [[Cisco Unified MeetingPlace Release 8.0 -- Upgrading to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0#Troubleshooting the Application Server Software Upgrade\|Troubleshooting the Application Server Software Upgrade]].		* See [[Cisco Unified MeetingPlace Release 8.0 -- Upgrading to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0#Troubleshooting the Application Server Software Upgrade\|Troubleshooting the Application Server Software Upgrade]].
-

	===== Related Topics =====		===== Related Topics =====

Dunn at 00:26, 9 February 2012

2012-02-09T00:26:04Z

← Older revision		Revision as of 00:26, 9 February 2012
Line 238:		Line 238:


-	===== Procedure =====	+	===== Procedure =====
-		+
-		+
-	~~# Go to Cisco.com and find the upgrade file. The naming convention will be similar to upgrade_mp_''<version_number''>.bin, where <''version_number> ''is the version number to which you are upgrading.~~	+
-	~~#: '''Note: ''' The file is located near http://tools.cisco.com/support/downloads/go/Redirect.x?mdfid=278875240~~	+
-	~~# Save the file to a convenient location.~~	+
-	# Enter '''md5sum upgrade_mp_<''''''version_number>''''''.bin''' to determine the checksum of the file that you downloaded. Compare this value to the checksum value of the file that is posted on the download page on Cisco.com.	+
-	~~# From the console, go to the Cisco Unified MeetingPlace operating system sign-in page and sign in as the user called root.~~	+
-	~~# Right-click on the desktop and select '''New Terminal'''.~~	+
-	~~#: The upgrade program displays the command line.~~	+
-	~~# Navigate to the directory where you saved the upgrade file.~~	+
-	~~# Enter''' sh''' '''upgrade_mp_<'''''version_number'''''>''''''.bin'''<span style="font-weight: bold"> </span>'''&''' to execute the upgrade program.~~	+
-	~~#: The upgrade program displays the Introduction page.~~	+
-	~~# Select '''Next'''.~~	+
-	#: The upgrade program checks to see if there are any previous versions of the Application Server software installed. If there is at least one previous version, the upgrade program displays a message listing the previous versions found on the system.	+
-	~~#: '''Note: ''' If the upgrade program does not find any previous versions of the Application Server software, the upgrade program displays an error message and you must quit the upgrade.~~	+
-	~~# Select '''Next''' to begin the upgrade.~~	+
-	~~#: The upgrade program displays a pre-installation summary.~~	+
-	~~# Review the pre-installation summary. Values include the product name, install folder, and the amount of disk space required and available for the installation target.~~	+
-	~~# Select '''Install''' if all the values are correct.~~	+
-	~~#: The upgrade program upgrades all the required components associated with the Application Server software.~~	+
-	~~#: The upgrade program displays a message stating that the upgrade is complete.~~	+
-	~~# Select '''Done''' to restart the system.~~	+
-	~~# Synchronize the Hardware Media Server and meeting types.~~	+
-	~~# Put the Audio Blade back online.~~	+

		+	#Go to Cisco.com and find the upgrade file. The naming convention will be similar to upgrade_mp_''<version_number''>.bin, where <''version_number> ''is the version number to which you are upgrading.
		+	#:'''Note: ''' The file is located near http://tools.cisco.com/support/downloads/go/Redirect.x?mdfid=278875240
		+	#Save the file to a convenient location.
		+	#Enter '''md5sum upgrade_mp_<''''''version_number>''''''.bin''' to determine the checksum of the file that you downloaded. Compare this value to the checksum value of the file that is posted on the download page on Cisco.com.
		+	#From the console, go to the Cisco Unified MeetingPlace operating system sign-in page and sign in as the user called root.
		+	#Right-click on the desktop and select '''New Terminal'''.
		+	#:The upgrade program displays the command line.
		+	#Navigate to the directory where you saved the upgrade file.
		+	#Enter '''sh upgrade_mp_<version_number>.bin<span style="font-weight: bold"> </span>&''' to execute the upgrade program.
		+	#:The upgrade program displays the Introduction page.
		+	#Select '''Next'''.
		+	#:The upgrade program checks to see if there are any previous versions of the Application Server software installed. If there is at least one previous version, the upgrade program displays a message listing the previous versions found on the system.
		+	#:'''Note: ''' If the upgrade program does not find any previous versions of the Application Server software, the upgrade program displays an error message and you must quit the upgrade.
		+	#Select '''Next''' to begin the upgrade.
		+	#:The upgrade program displays a pre-installation summary.
		+	#Review the pre-installation summary. Values include the product name, install folder, and the amount of disk space required and available for the installation target.
		+	#Select '''Install''' if all the values are correct.
		+	#:The upgrade program upgrades all the required components associated with the Application Server software.
		+	#:The upgrade program displays a message stating that the upgrade is complete.
		+	#Select '''Done''' to restart the system.
		+	#Synchronize the Hardware Media Server and meeting types.
		+	#Put the Audio Blade back online.

	===== Troubleshooting Tips =====		===== Troubleshooting Tips =====

Dunn: /* Procedure */ edit text bold/italics

2012-02-09T00:24:22Z

Procedure: edit text bold/italics

← Older revision		Revision as of 00:24, 9 February 2012
Line 341:		Line 341:


-	===== Procedure =====	+	===== Procedure =====

		+	#Sign in to the CLI of node 1. If you are signing in remotely, use the eth0:0 IP address or hostname.
		+	#Enter '''su - '''to switch to the root user.
		+	#Enter '''mp_replication status''' on node 1 to ensure that all database changes have been synchronized.
		+	#:The system displays the queue column as zeroes.
		+	#Enter '''mp_replication switchOFF -r'''''node_2_eth0:0 ''on node 1, to switch off replication between the two Application Servers, where ''node_2_eth0:0''is the eth0:0 address for node 2.
		+	#Enter '''mp_replication teardown -r '''''node_2_eth0:0 ''on node 1, to tear down the replication setup with the remote Application Server, where ''node_2_eth0:0''is the eth0:0 address for node 2.
		+	#Archive and save the configuration data on node 1.
		+	#Enter '''failoverUtil setDeployment singleServer '''to change the mode of node 1 to SingleServer.
		+	#Upgrade node 1. See the [[Cisco Unified MeetingPlace Release 8.0 -- Upgrading to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0#Upgrading_the_Application_Server_by_Using_the_Console\|Upgrading the Application Server by Using the Console]].
		+	#Enter '''failoverUtil setDeployment failover '''on node 1 to change the mode of node 1 to failover.
		+	#:'''Note: ''' This disables the eth0 interface of node 1, so that node 2 can become active.
		+	#Sign in to the CLI of node 2. If you are signing in remotely, use the eth0:0 IP address or hostname.
		+	#Enter '''su - '''to switch to the root user.
		+	#Enter '''failoverUtil setServer active''' on node 2 to change its mode from standby to active.
		+	#Enter '''mp_replication teardown -r '''''node_1_eth0:0 ''on node 2, to tear down the replication setup with the remote Application Server, where ''node_1_eth0:0''is the eth0:0 address for node 1.
		+	#Enter '''failoverUtil setDeployment singleServer''' on node 2 to change its mode to SingleServer.
		+	#Upgrade node 2. See the [[Cisco Unified MeetingPlace Release 8.0 -- Upgrading to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0#Upgrading_the_Application_Server_by_Using_the_Console\|Upgrading the Application Server by Using the Console]].
		+	#Enter '''failoverUtil setDeployment failover''' on node 2 to change its mode to failover.

-	~~# Sign in to the CLI of node 1. If you are signing in remotely~~, ~~use the eth0:0 IP address or hostname.~~	+	<br> At this point, both Application Servers are in standby mode.
-	~~# Enter '''su - '''to switch to the root user.~~	+
-	~~# Enter '''mp_replication status''' on node 1 to ensure that all database changes have been synchronized.~~	+
-	~~#: The system displays the queue column as zeroes.~~	+
-	~~# Enter '''mp_replication switchOFF -r ''''''node_2_eth0:0''' on node 1, to switch off replication between the two~~ Application Servers~~, where ''node_2_eth0:0''''' '''is the eth0:0 address for node 2.~~	+
-	# Enter '''mp_replication teardown -r ''''''node_2_eth0:0 '''on node 1, to tear down the replication setup with the remote Application Server, where ''node_2_eth0:0''''' '''is the eth0:0 address for node 2.	+
-	~~# Archive and save the configuration data on node 1.~~	+
-	~~# Enter '''failoverUtil setDeployment singleServer '''to change the mode of node 1 to SingleServer.~~	+
-	# Upgrade node 1. See the [[Cisco Unified MeetingPlace Release 8.0 -- Upgrading to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0#Upgrading the Application Server by Using the Console\|Upgrading the Application Server by Using the Console]].	+
-	~~# Enter '''failoverUtil setDeployment failover '''on node 1 to change the mode of node 1 to failover.~~	+
-	~~#: '''Note: ''' This disables the eth0 interface of node 1, so that node 2 can become active.~~	+
-	~~# Sign in to the CLI of node 2. If you~~ are ~~signing~~ in ~~remotely, use the eth0:0 IP address or hostname.~~	+
-	~~# Enter '''su - '''to switch to the root user.~~	+
-	~~# Enter '''failoverUtil setServer active''' on node 2 to change its mode from~~ standby ~~to active.~~	+
-	# Enter '''mp_replication teardown -r ''''''node_1_eth0:0 '''on node 2, to tear down the replication setup with the remote Application Server, where ''node_1_eth0:0''''' '''is the eth0:0 address for node 1.	+
-	~~# Enter '''failoverUtil setDeployment singleServer''' on node 2 to change its mode to SingleServer.~~	+
-	# Upgrade node 2. See the [[Cisco Unified MeetingPlace Release 8.0 -- Upgrading to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0#Upgrading the Application Server by Using the Console\|Upgrading the Application Server by Using the Console]].	+
-	~~# Enter '''failoverUtil setDeployment failover''' on node 2 to change its~~ mode ~~to failover~~.	+

-		+	#Sign in to the CLI of node 2. If you are signing in remotely, use the eth0:0 IP address or hostname.
-	~~At this point, both Application Servers are in standby mode.~~	+	#Initialize database replication:
-	# Sign in to the CLI of node 2. If you are signing in remotely, use the eth0:0 IP address or hostname.	+	#*Release 8.0 MR1--Enter '''mp_replication init -n 2 -r <''node1-eth0:0-hostname''> [-v]'''
-	# Initialize database replication:	+	#*Release 8.0 FCS-- Enter'''mp_replication init -s 1 -n 2 -l node2-eth0:0 -r node1-eth0:0 -h'''
-	#* Release 8.0 MR1--Enter '''mp_replication init -n 2 -r <''node1-eth0:0-hostname''> [-v]'''	+	#Sign in to the CLI of Node 1. If you are signing in remotely, use the Node 1 eth0:0 IP address or hostname.
-	#* Release 8.0 FCS-- Enter'''mp_replication init -s 1 -n 2 -l node2-eth0:0 -r node1-eth0:0 -h'''	+	#Enter the following to initialize and start database replication:
-	# Sign in to the CLI of Node 1. If you are signing in remotely, use the Node 1 eth0:0 IP address or hostname.	+	#*Release 8.0 MR1
-	# Enter the following to initialize and start database replication:	+	#::'''mp_replication init -n 1 -r <''node2-eth0:0-hostname''> [-v]'''
-	#* Release 8.0 MR1	+	#::'''mp_replication switchON '''
-	#:: '''mp_replication init -n 1 -r <''node2-eth0:0-hostname''> [-v]'''	+	#*Release 8.0 FCS
-	#:: '''mp_replication switchON '''	+	#::'''mp_replication init -s 1 -n 1 -l node1-eth0:0 -r node2-eth0:0 -h'''
-	#* Release 8.0 FCS	+	#::'''mp_replication switchON -r node2-eth0:0'''
-	#:: '''mp_replication init -s 1 -n 1 -l node1-eth0:0 -r node2-eth0:0 -h'''	+	#Sign in to the CLI of node 1. If you are signing in remotely, use the eth0:0 IP address or hostname.
-	#:: '''mp_replication switchON -r node2-eth0:0'''	+	#Enter '''failoverUtil setServer active''' on node 1 to change its mode to active.
-	# Sign in to the CLI of node 1. If you are signing in remotely, use the eth0:0 IP address or hostname.	+	#:Node 1 is the active Application Server and node 2 is the standby Application Server.
-	# Enter '''failoverUtil setServer active''' on node 1 to change its mode to active.	+
-	#: Node 1 is the active Application Server and node 2 is the standby Application Server.	+

	===== Related Topics =====		===== Related Topics =====

MeetingPlace Moderator: /* Procedure */

2011-12-01T22:14:16Z

Procedure

← Older revision		Revision as of 22:14, 1 December 2011
Line 442:		Line 442:
	# Enter '''su - '''to switch to the root user.		# Enter '''su - '''to switch to the root user.
	# Enter the following command using the hostname of node 1:		# Enter the following command using the hostname of node 1:
		+	#* Release 8.0 MR1
		+	#: '''mp_replication init -n 2 -r''' <''node1-eth0:0-hostname''> '''[-v]'''
		+	#* Release 8.0 FCS
	#: '''mp_replication init -s 2 -n 1 -r ''''''hostname_of_node_1'''''' -m '''		#: '''mp_replication init -s 2 -n 1 -r ''''''hostname_of_node_1'''''' -m '''
	# Sign in to the CLI of node 1.		# Sign in to the CLI of node 1.
	# Enter '''su - '''to switch to the root user.		# Enter '''su - '''to switch to the root user.
	# Enter the following commands using the hostname of node 2:		# Enter the following commands using the hostname of node 2:
-	#: '''mp_replication init -s 1 -n 1 -r ''''''hostname_of_node_2'''''' -m '''	+	#* Release 8.0 MR1
-	#: '''mp_replication switchON -r '''''hostname_of_node_2''	+	#:: '''mp_replication init -n 1 -r''' <''node2-eth0:0-hostname''> '''[-v]'''
-		+	#:: '''mp_replication switchON '''
		+	#* Release 8.0 FCS
		+	#:: '''mp_replication init -s 1 -n 1 -r ''''''hostname_of_node_2'''''' -m '''
		+	#:: '''mp_replication switchON -r '''''hostname_of_node_2''

	===== Related Topics =====		===== Related Topics =====

MeetingPlace Moderator: /* Procedure */

2011-12-01T22:10:15Z

Procedure

← Older revision		Revision as of 22:10, 1 December 2011
Line 366:		Line 366:
	At this point, both Application Servers are in standby mode.		At this point, both Application Servers are in standby mode.
	# Sign in to the CLI of node 2. If you are signing in remotely, use the eth0:0 IP address or hostname.		# Sign in to the CLI of node 2. If you are signing in remotely, use the eth0:0 IP address or hostname.
-	# Enter '''mp_replication init -s 1 -n 2 -l node2-eth0:0 -r node1-eth0:0 -h''' ~~to initialize database replication.~~	+	# Initialize database replication:
		+	#* Release 8.0 MR1--Enter '''mp_replication init -n 2 -r <''node1-eth0:0-hostname''> [-v]'''
		+	#* Release 8.0 FCS-- Enter'''mp_replication init -s 1 -n 2 -l node2-eth0:0 -r node1-eth0:0 -h'''
	# Sign in to the CLI of Node 1. If you are signing in remotely, use the Node 1 eth0:0 IP address or hostname.		# Sign in to the CLI of Node 1. If you are signing in remotely, use the Node 1 eth0:0 IP address or hostname.
	# Enter the following to initialize and start database replication:		# Enter the following to initialize and start database replication:
-	#: '''mp_replication init -s 1 -n 1 -l node1-eth0:0 -r node2-eth0:0 -h'''	+	#* Release 8.0 MR1
-	#: '''mp_replication switchON -r node2-eth0:0'''	+	#:: '''mp_replication init -n 1 -r <''node2-eth0:0-hostname''> [-v]'''
		+	#:: '''mp_replication switchON '''
		+	#* Release 8.0 FCS
		+	#:: '''mp_replication init -s 1 -n 1 -l node1-eth0:0 -r node2-eth0:0 -h'''
		+	#:: '''mp_replication switchON -r node2-eth0:0'''
	# Sign in to the CLI of node 1. If you are signing in remotely, use the eth0:0 IP address or hostname.		# Sign in to the CLI of node 1. If you are signing in remotely, use the eth0:0 IP address or hostname.
	# Enter '''failoverUtil setServer active''' on node 1 to change its mode to active.		# Enter '''failoverUtil setServer active''' on node 1 to change its mode to active.
	#: Node 1 is the active Application Server and node 2 is the standby Application Server.		#: Node 1 is the active Application Server and node 2 is the standby Application Server.
-

	===== Related Topics =====		===== Related Topics =====

MeetingPlace Moderator: /* Related Topics */

2011-10-21T20:29:26Z

MeetingPlace Moderator: /* About Upgrading the Application Server Software */

2011-10-21T20:26:19Z

About Upgrading the Application Server Software

← Older revision		Revision as of 20:26, 21 October 2011
Line 199:		Line 199:
	=== About Upgrading the Application Server Software ===		=== About Upgrading the Application Server Software ===
	* To upgrade the Application Server software, you must already have an existing version of the Application Server software installed on your server.		* To upgrade the Application Server software, you must already have an existing version of the Application Server software installed on your server.
-	* When you upgrade the Application Server software, the upgrade program moves the existing files to a backup directory and installs the new files in the current directory~~. This allows you to uninstall the upgrade if you need to~~.	+	* When you upgrade the Application Server software, the upgrade program moves the existing files to a backup directory and installs the new files in the current directory.
	* A fresh installation of the Application Server software erases the database that holds the Hardware Media Server configuration information; however, ''upgrading'' the Application Server software does not erase the database.		* A fresh installation of the Application Server software erases the database that holds the Hardware Media Server configuration information; however, ''upgrading'' the Application Server software does not erase the database.
	* The upgrade program backs up any Microsoft Outlook notification templates and copies them to /opt/cisco/meetingplace/var.		* The upgrade program backs up any Microsoft Outlook notification templates and copies them to /opt/cisco/meetingplace/var.
	* We support using Integrated Lights-Out (iLO) to install and upgrade the Application Server software. This standard only applies to the Cisco MCS 7835-H2 and Cisco MCS 7845-H2. For information about installing, configuring, and using iLO, see http://h18000.www1.hp.com/products/servers/management/ilo/.		* We support using Integrated Lights-Out (iLO) to install and upgrade the Application Server software. This standard only applies to the Cisco MCS 7835-H2 and Cisco MCS 7845-H2. For information about installing, configuring, and using iLO, see http://h18000.www1.hp.com/products/servers/management/ilo/.
-

	=== Preparing to Upgrade the Application Server Software ===		=== Preparing to Upgrade the Application Server Software ===

MeetingPlace Moderator at 18:12, 18 October 2011

2011-10-18T18:12:31Z

← Older revision		Revision as of 18:12, 18 October 2011
Line 12:		Line 12:
	:* Release 8.0.1.3 (the FCS version)		:* Release 8.0.1.3 (the FCS version)
	:* Release 8.0.1.229 (the Patch 1 version)		:* Release 8.0.1.229 (the Patch 1 version)
		+
		+	'''Note:''' If you are upgrading from Release 8.0 FCS or Release 8.0 Patch 1 to Release 8.0 MR 1, then complete the upgrade procedure in this module.

	* You can upgrade to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace:		* You can upgrade to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace:

← Older revision		Revision as of 20:47, 31 October 2012
Line 746:		Line 746:
	#: The upgrade finishes with a single system reboot.		#: The upgrade finishes with a single system reboot.
	# Ensure that the Windows Time Service is up and running.		# Ensure that the Windows Time Service is up and running.
		+
		+
		+	===== What To Do Next =====
		+
		+	If you have already applied the Cisco WebEx Security Certification patch to your Cisco Unified MeetingPlace system and then upgraded to an 8.0 release, then you must reapply this patch following your upgrade.
		+
		+	For more information on this Cisco WebEx Security Certification Patch, see:
		+	* http://customercare.corp.webex.com/commcal/archives/type_informational/006535.php
		+	* http://docwiki.cisco.com/wiki/Cisco_Unified_MeetingPlace_-_WebEx_Certificate_Upgrade


	===== Related Topics =====		===== Related Topics =====
	* For information about configuring the Web Server to synchronize with an NTP server, see [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Time and Time Zones for Cisco Unified MeetingPlace#Configuring the Time for the Web Server\|Configuring the Time for the Web Server]] in the'' ''[[Cisco Unified MeetingPlace Release 8.0 -- Configuring Time and Time Zones for Cisco Unified MeetingPlace#Configuring Time and Time Zones for Cisco Unified MeetingPlace\|Configuring Time and Time Zones for Cisco Unified MeetingPlace]] module.		* For information about configuring the Web Server to synchronize with an NTP server, see [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Time and Time Zones for Cisco Unified MeetingPlace#Configuring the Time for the Web Server\|Configuring the Time for the Web Server]] in the'' ''[[Cisco Unified MeetingPlace Release 8.0 -- Configuring Time and Time Zones for Cisco Unified MeetingPlace#Configuring Time and Time Zones for Cisco Unified MeetingPlace\|Configuring Time and Time Zones for Cisco Unified MeetingPlace]] module.
-

	=== Allowing Guest Users to Dial Out ===		=== Allowing Guest Users to Dial Out ===

← Older revision		Revision as of 20:29, 21 October 2011
Line 615:		Line 615:
	'''Error Message: ''' Warning - Not enough memory. If you continue, system performance may be impacted. It is highly recommended that you exit the installation and install more memory.		'''Error Message: ''' Warning - Not enough memory. If you continue, system performance may be impacted. It is highly recommended that you exit the installation and install more memory.

-	'''Explanation: ''' We recommend that the server that you upgrade have 4 ~~Gig~~ of memory. However, you can still upgrade a server with only 2 ~~Gig~~ of memory.	+	'''Explanation: ''' We recommend that the server that you upgrade have 4 GB of memory. However, you can still upgrade a server with only 2 GB of memory.

	'''Recommended Action: ''' Install more memory.		'''Recommended Action: ''' Install more memory.
-

	===== Related Topics =====		===== Related Topics =====