Cisco Cisco IPCC Web Option Release Note

o 

Admin UI: under Collaboration Server\Server Setup\Connections\Monitor – all services 
will have an UP status 

o 

Media Blender: 

o 

Admin UI: under Media Blender\Server\Startup Shutdown – media blender has been 
running for <time> 

o 

Admin UI: under Media Blender\Services\Firewall Gateway\Monitor – all gateway stubs 
will have a RUN status 

With the full ICM system in the staging environment, you can test fault tolerance prior to shipping the 
system to the production environment. Refer to the section in the document on 

 in the 

Staging Environment.  

Validate the following settings from the system diagram for the Production Environment and make the 
required changes prior to shipping systems. If you used “dummy” IP addresses during the staging process, 
you need to load the actual Host Names/IP Addresses for the system onto the DNS Server (Logger/DNS 
Server) and the actual/production IP addresses set: 

o 

IPAddresses (visible and private, high and low) 

o 

Default Gateways 

o 

Masks 

o 

DNS preferred and alternate servers on visible cards 

o 

Static Routes 

o 

Active Directory WAN Sites and Subnets 

o 

DNS Forward and Reverse Lookup Zone Records 

o 

Label each Network Card and Port - Label the machine on the front and back with the host name 

o 

Create Emergency Repair Disk 

o 

Clear Event Logs 

o 

Clear any Dr. Watson Application Errors 

o 

Remove any diskettes, CD’s or media from drives 

o 

Make sure that all ICM Services are set to Manual Start – Services are not set to AUTOSTART until 
after the implementation testing in the production environment. 

Assure that the 

 has been filled out as and accurate record of the Staging 

event. Test Detail and note the test cases you run as pass/fail/exceptions. Any outstanding action items 
from the Staging event should be documented and shared with the team and project manager(s) associated 
with this project