Cisco Cisco Administrative Workstation Nota De Lançamento

Although PGs are supported back two previous versions, to eliminate defects and add feature enhancements, the PGs should be 
upgraded to the same version as the Central Controller.  In addition, to minimize upgrade complications Cisco recommends all 
components are at the same version prior to performing the upgrade. 

HOSTED NOTE: assure Central Site PGs are the first PGs to be upgraded. All other sites can be subsequently upgraded due to the 
sheer volume of PGs that are involved. 

An equally important consideration for hardware compatibility requirements are those derived from the Microsoft operating system 
and system software (most notably SQL Server 2000).  Note that the ICM/IPCC solution requirements outlined in this document 
match and in some cases exceed like requirements from Microsoft.  For example, while Microsoft SQL Server 2000 Enterprise 
Edition is not technically required (over SQL Server Standard Edition) with a total of 4GB of physical memory and four or fewer 
processors, there are mission critical, high database load scenarios where Enterprise Edition is suitable with the ICM/IPCC 
application.  (Because Cisco performs all SQL Server Enterprise Edition qualification on Windows Server 2003 Enterprise Edition, 
the latter is likewise required whenever SQL Server Enterprise Edition is itself deployed.)  Details are covered in 

all cases, the Microsoft operating system and SQL Server software Service Pack (SP) updates must be applied to meet the levels 
specified herein.  This is important for operational integrity as well as for security.  Cisco tests extensively against published Service 
Pack support levels, and each new Service Release is tested against all relevant security updates. 

Additional important upgrade information follows: 

Š  An ICM/IPCC system is always upgraded from a prior release starting with the central controller (CallRouter and Logger) 

servers.   

Š  Upgrades of duplexed systems are typically done one “side” at a time.   

Š  As with any major release upgrade, release 7.0(0) requires that the HDS systems be themselves upgraded to coincide with 

the Logger to which they communicate.  

Š  Peripheral Gateway (PG) nodes are typically the last servers to be upgraded; the 7.0(0) upgrade will support 4.6.2 PGs 

through the upgrade transition, but all PGs must be running a minimum of release 5.0(0) for a fully supported system 
configuration.  (Release 7.0(0) PGs are strongly recommended to take advantage of several key PG enhancements made in 
the area of supportability, scalability, and feature support.) 

Š  ICM Hosted Edition and IPCC Hosted Edition customers may, as with prior major releases, upgrade their NAM and CICM 

servers in either order to best suit their operational requirements.  Also like prior releases, however, the NAM-to-CICM 
protocol support inherent in the Hosted Edition software supports only a single major back-level (Hosted Edition) release.  
For ICM/IPCC Hosted Edition 7.0(0), this means the interface opposite that being upgraded must itself be at release 5.0(0) 
(or later). 

Š  The documented procedures for upgrading to ICM/IPCC Release 7.0(0) require a starting baseline of ICM/IPCC 5.0(0) or 

6.0(0), running on the Microsoft Windows 2000 Server operating system (SP4) with Microsoft SQL Server 2000 (SP3a or 
SP4).  Upgrade customers currently deploying releases earlier than release 5.0(0) will need to provide a transitional upgrade 
to 5.0(0) or 6.0(0) as a staging release.  This step will require database migration from the earlier release to 5.0(0)/6.0(0), 
and for that reason the upgrade requires stabilization on the transitional release and is thus not a multi-step process 
accomplished in a single maintenance window.   

Š  Microsoft’s Windows 2000 Update Rollup 1 for Service Pack 4 is supported by the various components of Cisco 

ICM/IPCC 7.0(0) SR1 or later during the upgrade period.  Update Rollup 1 is an elective add-on to SP4 that is supported 
where Windows 2000 itself is supported. 

Caution: If the computer has certain earlier non-Plug and Play ISA, EISA, or MCA SCSI controllers installed, when you 
restart a computer after you install Update Rollup 1 for Microsoft Windows 2000 Service Pack 4 (SP4), you may receive 
something similar to the following Stop error message:  
***Stop 0x0000001e {0xc0000005,0x804a1a51,0x00000000,0x000000b0} KMODE_EXCEPTION_NOT_HANDLED 
This problem results from a problem in the Scsiport.sys driver that is included in Update Rollup 1 for Windows 2000 SP4.