Cisco Cisco Administrative Workstation Release Note
Hosted NAM/CICM Model
Step 71.
Change Domain Controllers to Native Mode
Cisco ICM functions with Active Directory in both “Mixed” and “Native” modes. Microsoft recommends
that you change an AD domain to native mode if an implementation does not and will not have any future
NT domain controllers. You can only change the mode from mixed to native. Once the domain is running
in native mode, you cannot change it back to mixed mode.
that you change an AD domain to native mode if an implementation does not and will not have any future
NT domain controllers. You can only change the mode from mixed to native. Once the domain is running
in native mode, you cannot change it back to mixed mode.
On NAM, CICM and Customer AW Domains Controllers:
1. Open Active Directory Domains and Trusts.
2. Right-click the domain node for the domain you want to administer and then click Properties.
3. In the General Tab, click Change Mode and then click Yes.
Step 72.
Install Listeners, LGMappers and LGArchiver
Refer to the Remote Monitoring Suite Administration Guide for instructions on installing and configuring
Listeners, LGMappers and LGArchivers. The NAM and CICM Loggers are configured in setup to “Phone
Home” events to the Listeners over the NAM/CICM network. Service providers install Alarm Tracker
Clients to monitor and manage the event stream from the LGMappers.
Listeners, LGMappers and LGArchivers. The NAM and CICM Loggers are configured in setup to “Phone
Home” events to the Listeners over the NAM/CICM network. Service providers install Alarm Tracker
Clients to monitor and manage the event stream from the LGMappers.
Step 73.
Complete Staging Tests
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
system to the production environment. Refer to the section in the document on
in the
Staging Environment.
Step 74.
Complete Settings for Production Environments
Validate the following settings from the system diagram for Production Environment and make the
required changes prior to shipping systems. If you used a “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 set the actual/production IP addresses:
required changes prior to shipping systems. If you used a “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 set the actual/production IP addresses:
IPAddresses (visible and private, high and low)
Default Gateways
Masks
DNS preferred and alternate servers on visible cards
Static Routes
Active Directory WAN Sites and Subnets
DNS Forward and Reverse Lookup Zone Records
Label each Network Card and Port - Label the machine on the front and back with the host name
Create Emergency Repair Disk
Clear Event Logs
Clear any Dr. Watson Application Errors
Remove any diskettes, CD’s or media from drives
Make sure that all ICM Services are set to Manual Start. Do not set Services to AUTOSTART
Default Gateways
Masks
DNS preferred and alternate servers on visible cards
Static Routes
Active Directory WAN Sites and Subnets
DNS Forward and Reverse Lookup Zone Records
Label each Network Card and Port - Label the machine on the front and back with the host name
Create Emergency Repair Disk
Clear Event Logs
Clear any Dr. Watson Application Errors
Remove any diskettes, CD’s or media from drives
Make sure that all ICM Services are set to Manual Start. Do not set Services to AUTOSTART
until after Implementation Testing in the Production environment.
Release 6.0(0) Staging on Windows 2000
102
102