Guest

Cisco Unified MeetingPlace

PCI Server to Cisco MeetingPlace 8100 Series Server Upgrade Procedure for Cisco MeetingPlace Audio Server Release 5.2 and 5.3

 Feedback

Table Of Contents

PCI Server to Cisco MeetingPlace 8100 Series Server Upgrade Procedure for Cisco MeetingPlace Audio Server

Naming Conventions

System Requirements

PCI Server

Cisco MeetingPlace 8100 Series Server

Network Requirements

How to Upgrade Your PCI Server to a Cisco MeetingPlace 8100 Series Server

Calculating the Time Required for the Upgrade

Initializing the Database

Completing Preupgrade Tasks for the PCI Server

Completing Preupgrade Tasks for the Cisco MeetingPlace 8100 Series Server

Upgrading the PCI Server to a Cisco MeetingPlace 8100 Series Server

Verifying Cisco MeetingPlace 8100 Series Server System Parameters

Performing Postupgrade Procedures

Verifying Cisco MeetingPlace System Functionality

Related Documentation

Obtaining Documentation

Cisco.com

Ordering Documentation

Documentation Feedback

Obtaining Technical Assistance

Cisco Technical Support Website

Submitting a Service Request

Definitions of Service Request Severity

Obtaining Additional Publications and Information


PCI Server to Cisco MeetingPlace 8100 Series Server Upgrade Procedure for Cisco MeetingPlace Audio Server


November 5, 2004


Note This document was previously titled Cisco MeetingPlace Audio Server Release 5.2 PCI to Cisco 8100 Series Upgrade Procedure.


This document provides procedures for upgrading by transferring Cisco MeetingPlace Audio Server Release 5.2 or Release 5.3 conference and voice data from an existing standalone or network configuration Peripheral Component Interconnect (PCI) server to a new or initialized database on a Cisco MeetingPlace 8100 series server. During the upgrade, the PCI system continues to operate as usual.

This procedure is intended for use with the Cisco MeetingPlace Audio Server Customer Engineering Guide or Cisco MeetingPlace Audio Server Installation and Configuration Guides for your Cisco MeetingPlace Audio Server Release 5.2 or Release 5.3 and Cisco MeetingPlace 8100 series server, which can be located at the following URL:

http://www.cisco.com/univercd/cc/td/doc/product/conf/mtgplace/audio/index.htm

This document contains the following sections:

Naming Conventions

System Requirements

How to Upgrade Your PCI Server to a Cisco MeetingPlace 8100 Series Server

Related Documentation

Obtaining Documentation

Documentation Feedback

Obtaining Technical Assistance

Obtaining Additional Publications and Information

Naming Conventions

The following product-naming conventions are used in this document:

Product
Convention

Cisco MeetingPlace Audio Server with any possible combinations of integration applications

Cisco MeetingPlace system

Cisco MeetingPlace Audio Sever Release 5.2 and Release 5.3

Release 5.2 and 5.3

Cisco MeetingPlace Audio Server Release 5.2 or Release 5.3 and the hardware on which the release is installed

Cisco MeetingPlace Audio Server system

Cisco MeetingPlace MeetingTime

MeetingTime


System Requirements

PCI Server

Cisco MeetingPlace Server Release 4.3 or a later release.

The PCI system must be up.

Cisco MeetingPlace 8100 Series Server

You must install and configure the Cisco MeetingPlace 8100 series server.

You must have all the appropriate licenses for the Cisco MeetingPlace 8100 series server before the upgrade.

The Cisco MeetingPlace 8100 series server must have an initialized or a new database.

During the upgrade, the Cisco MeetingPlace 8100 series server must be up.

You must disable disk backups.

You must disable Reservationless Meetings.

Network Requirements

The network, round-trip latency between the PCI server and the Cisco MeetingPlace 8100 series server must not exceed 250 ms with no more than 1% packet loss in a 30-second time period.

How to Upgrade Your PCI Server to a Cisco MeetingPlace 8100 Series Server


Note Do not perform this upgrade procedure when the system is busy.


To upgrade your PCI server to a Cisco MeetingPlace 8100 series server, perform the following tasks in this order:

(Optional) Calculating the Time Required for the Upgrade

Initializing the Database

Completing Preupgrade Tasks for the PCI Server

Completing Preupgrade Tasks for the Cisco MeetingPlace 8100 Series Server

Upgrading the PCI Server to a Cisco MeetingPlace 8100 Series Server

Verifying Cisco MeetingPlace 8100 Series Server System Parameters

Performing Postupgrade Procedures

Verifying Cisco MeetingPlace System Functionality

Calculating the Time Required for the Upgrade

To calculate the amount of time required to complete the PCI server to Cisco MeetingPlace 8100 series server upgrade, perform the following steps:


Step 1 From MeetingTime, run the View Disk Usage Statistics by performing the following steps:

a. Open the MeetingPlace Register Book and select the System tab.

b. Select View Disk Usage Statistics and click Execute.

Step 2 Obtain the number of minutes of voice and attachment data for all Cisco MeetingPlace Audio Server systems.

Step 3 On the PCI server, enter dbsize and obtain the following information:

Size of the database

Total number of user profiles, conferences, and conference participants

Step 4 To determine the approximate time that is required for the upgrade, perform the calculations in Table 1.

Table 1 Data Transfer Rate Calculations

 
Database Element
Result

a.

Minutes of voice and attachment data/4000

 

b.

Number of user profiles/9600

 

c.

Number of conferences/7200

 

d.

Number of conference participants/7200

 

e.

Sum of a through d = approximate upgrade time in hours

 

Step 5 If the database has not been initialized, add two hours to the upgrade time that you calculated in Step 4.


Note The following data transfer rates were used in Table 1.

Data Type
Transfer Rate

Voice data1

4000 minutes of data per hour

User profile data

9600 minutes of data per hour

Conference data

7200 minutes of data per hour

Conference participant data

7200 minutes of data per hour

1 Voice data transfers in a healthy switched 100 Mb/second network at approximately 300 KB per second, resulting in a voice data transfer rate of approximately 1 GB per hour. Therefore, the transfer rate calculates to 17 KB = 4 seconds of voice data = 4000 minutes of voice per hour. This equation is also used to calculate the user profile, conference, and conference participant data transfer rates.




Initializing the Database

Before upgrading, make sure that the Cisco MeetingPlace 8100 series server has either a new or initialized database. If the database is new and does not have any data except the default user profiles, go to the "Completing Preupgrade Tasks for the PCI Server" section.


Caution Initializing the database will delete all Cisco MeetingPlace Audio Server user profiles, meetings, and voice recordings. Do not use ^C or end this process until the initialization process is complete. Also, ensure that the save command has been active for at least a day and that the database is backed up.

To initialize the database, perform the following steps.


Step 1 Log in as a technician to the Cisco MeetingPlace 8100 series server.

The tech$ prompt appears.

Step 2 Enter mpconvert init.

Database initialization takes approximately two hours to finish.

All configurations are saved and restored when the initialization process is complete.

The server restarts automatically after the database initialization is complete.

If the backup is active message appears, follow the prompts to allow the server to restart.

After the server restarts, return to Step 2.

Step 3 When the server is back up, set the MeetingTime MaxRecordingSpace to a value that is sufficient for database conversion on your Cisco MeetingPlace Audio Server system.


Completing Preupgrade Tasks for the PCI Server

Before beginning the upgrade, complete the following tasks for the PCI server:

Task
Completed

Obtain the IP address of the PCI server.

 

Obtain the user ID and password for the PCI server.


Note You can use any existing user ID; however, the user ID must be one word without spaces.


 

Set up the following test meetings:

Normal meeting

Normal meeting with recording

Future meeting with attachment

Recurring meeting

Multiserver meeting

Continuous meeting

 

Run a Raw Meeting Detail report and save the output.

 

Enter the dbsize command and save the output.

 

Make sure that you copy the following system parameters:

User groups

Telephony access

System parameters

Network management information if you are using Simple Network Management Protocol (SNMP)

Network management communities if using SNMP

Usage parameters

Scheduling parameters

Teams

 


Completing Preupgrade Tasks for the Cisco MeetingPlace 8100 Series Server

Before you upgrade, complete the following tasks for the Cisco MeetingPlace 8100 series server:

Task
Completed

Verify LAN and analog modem connectivity to the Cisco MeetingPlace 8100 series server by performing the following steps:

1. Ensure that the modem is powered up and connected to the Cisco MeetingPlace 8100 series server before the server is powered up.

2. To verify the modem connection, dial in to the Cisco MeetingPlace Audio Server system.

 

Make sure that there is no planned network outage or scheduled maintenance during the upgrade.

 

Obtain a temporary IP address for data migration.

 

Ensure that the network latency between the PCI server and Cisco MeetingPlace 8100 series server does not exceed 250 ms with no more than 1% packet loss in a 30-second time period.

 

If the Cisco MeetingPlace 8100 series server and PCI server do not reside on the same subnet, make sure that the following ports are opened bidirectionally between the PCI server and the Cisco MeetingPlace 8100 series server:

5001

5005

5006

 

Log your HyperTerminal session during the upgrade.

 

Verify that the database is initialized by performing the following steps:

1. Enter dbsize on the Cisco MeetingPlace 8100 series server.

2. By viewing the dbsize output, make sure that only 4 user profiles and 0 conferences are listed, as shown in the following sample output:

servername:tech$ dbsize
User profiles:4
Groups: 1
Conferences: 0
Conference participants:0
Conference time records: 0
Conference notifications:0
Conference category records:0
Conference attachments:0
Team lists:1
Team list members:2
Meeting number reservations:0
Voice space reservations:0
servername:tech$

If the database is not initialized, see the "Initializing the Database" section.

 

Ensure that the system is configured with the necessary Smart Blades.

 

Make any necessary Cisco MeetingPlace 8100 series server configurations or modifications.

Telephony configuration—Before the upgrade, ensure that all appropriate telephony configurations are done.

LAN configuration— Before the upgrade, ensure that all proper network configurations, such as IP address, subnet mask, and so on, are made.

Cisco MeetingPlace MeetingTime telephony access parameters—These configurations are not transferred from the PCI server.

Max recording space—Make sure that the MaxRecordingSpace is set to an appropriate value for your system, a value that is sufficient for the database conversion.

Server configurations—Ensure that all port configurations, such as access ports, floating port, and so on, are set to the appropriate values for your system.

 

Copy the Translation Table from the PCI server to Cisco MeetingPlace 8100 series server and activate it.


Note The translation tables for the PCI server are not propagated during the database conversion process.


 

Verify VoIP connectivity to the Cisco MeetingPlace  8100 series server with a temporary IP gateway if necessary.


Note If you attach a temporary IP gateway, remove this gateway data from the Cisco MeetingPlace 8100 series server before you upgrade. Attach gateways after the upgrade.


 

Verify that the licenses are consistent between the Cisco MeetingPlace 8100 series server and the PCI server. At a minimum, the Cisco MeetingPlace 8100 series server must have all the licenses that the PCI server has.

 

Ensure that the Cisco MeetingPlace 8100 series server has all the languages that are installed on the PCI server.

 

Verify either the PSTN functionality on the Cisco MeetingPlace 8100 series server with a temporary T1 or E1 connection, and if necessary, verify VoIP functionality with a temporary Ethernet connection.

 

Verify that Reservationless Meetings is disabled by performing the following steps:

1. Go to the Meeting Time System Reservationless Mtgs dialog box.

2. Confirm that the Enable Reservationless attributes field is marked No.

 

Verify that the voice file system is correct by performing the following steps:

1. Log in as a superuser.

2. Enter the ls -l /lat/fs.? command.


Note For a sample voice file, see the "Voice File Example" section.


 


Voice File Example

The following sample output is a voice file listing that you can obtain by entering the ls -l /lat/fs.? command. The text in bold shows that the voice prompt files exist in the directory.


Note You may not find all files under /lat/fs.1 because some files refer to other language prompts.


servername:csc$ ls -l /lat/fs.?
/lat/fs.1:
total 366656
+rw-rw-rw-   1 csc      40960000 Mar  3 14:23 dir0blockrec.fs+
-rw-rw-rw-   1 csc       1280000 Mar  3 14:23 dir0headerrec.fs
-rw-rw-rw-   1 csc       1280000 Mar  3 14:23 dir0indexrec.fs
+rw-rw-rw-   1 csc      49152000 Oct 17  2002 dir3blockrec.fs+
-rw-rw-rw-   1 csc       2048000 Feb 25 17:28 dir3headerrec.fs
-rw-rw-rw-   1 csc       2048000 Oct 17  2002 dir3indexrec.fs
+rwxrwxrwx   1 root     49152000 Jul  2  2001 dir6blockrec.fs+
-rw-rw-rw-   1 root      1536000 Feb 25 17:28 dir6headerrec.fs
-rw-rw-rw-   1 root      1536000 Jul  2  2001 dir6indexrec.fs
+rw-rw-rw-   1 csc      32768000 Sep  4  2002 dir7blockrec.fs+
-rw-rw-rw-   1 csc       1280000 Feb 25 17:28 dir7headerrec.fs
-rw-rw-rw-   1 csc       1280000 Sep  4  2002 dir7indexrec.fs
-rw-rw-rw-   1 root       983040 Mar 17 11:00 dkdynamicconfig.fs
-rw-rw-rw-   1 root       983040 Mar 17 11:00 dkdynamicconfig.fs_orig
-rw-rw-rw-   1 root         1024 Mar 17 11:00 dkstaticconfig.fs
-rw-rw-rw-   1 root         1024 Mar 17 11:00 dkstaticconfig.fs_orig
-rw-rw-rw-   1 csc         43360 Mar  3 14:23 prompt_db_vfs_map_dir0
-rw-rw-rw-   1 csc         42968 Oct 17  2002 prompt_db_vfs_map_dir3
-rw-rw-rw-   1 root        41736 Jul  2  2001 prompt_db_vfs_map_dir6
-rw-rw-rw-   1 csc         42968 Sep  4  2002 prompt_db_vfs_map_dir7

Upgrading the PCI Server to a Cisco MeetingPlace 8100 Series Server


Note You must apply any change to the scheduling and usage parameters after the upgrade is completed.


We recommended that you use the -usp option, which imports all Scheduling and Usage Parameters from the PCI server to the Cisco MeetingPlace 8100 series server.

If you are upgrading from a Release 4.2 PCI system, extra fields that exist in Release 4.3 and Release 5.0 or a later release take the default values from the Cisco MeetingPlace 8100 series server.

To upgrade the PCI to Cisco MeetingPlace 8100 series, perform the following steps:


Step 1 Log in as a technician to the Cisco MeetingPlace 8100 series server.


Note If the database is not initialized before you enter the mpconvert start command, you are prompted to enter mpconvert init. Complete the tasks in "Initializing the Database" section before you upgrade.


Step 2 Enter mpconvert start -c option where option is one of the following selections:

-usp—Uses PCI system scheduling and usage parameters

-ip—Ignores past meetings

-iv—Ignores voice data

-q—Uses quiet mode


Note If you choose the -ds option, the PCI server will not be able to schedule any meetings during the upgrade.


-ds—Disables scheduling on the PCI server

Step 3 Enter y at the WARNING: all data in this directory will be deleted. Continue? (y/n) message.

Step 4 Enter your user ID and password.

Step 5 Enter the IP address of the PCI server.

The upgrade begins and runs in the background.


Tip During the upgrade, you are in trace mode and can exit by pressing ^C at any time. You can rejoin the trace session by entering the mpconvert trace command at the command line.


Step 6 If the upgrade fails, review the log and look for the following error:

Warning: failed to get remote checksum (0)

This error indicates that an interruption in network connectivity occurred.


Note You must stabilize the network and begin the upgrade procedure again.


Step 7 When the upgrade finishes, restart the server.

Step 8 Complete the "Verifying Cisco MeetingPlace 8100 Series Server System Parameters" section.

Step 9 Complete the "Performing Postupgrade Procedures" section.

Step 10 After the postupgrade procedures are complete, enter save.

Step 11 If necessary, enable Reservationless Meetings.


Verifying Cisco MeetingPlace 8100 Series Server System Parameters

After the upgrade process, the following notable system behaviors can occur. Verify your Cisco MeetingPlace 8100 series server system parameters and reconfigure any parameters that did not transfer properly. Unless noted in Table 2, the system parameters and information that are imported from the PCI server remain unchanged on the Cisco MeetingPlace 8100 series server.

Table 2 Notable System Behaviors

System Parameter
System Behavior

Conference records

If you use an option other than -usp during the upgrade, the following notable system behaviors may occur:

Without using -usp—Scheduling and Usage Parameters do not change in the Cisco MeetingPlace 8100 series server.

Using option -ip—Past meetings from the PCI do not propagate the Cisco MeetingPlace 8100 series server.

Using option -iv—PCI voice data does not exist on the Cisco MeetingPlace 8100 series server.

Using an option other than option -usp—Scheduling and Usage Parameters are not imported from the PCI server.

Profile updates

Profile conflicts may occur; therefore, you must resolve the conflicting profiles, which are modified to complete the upgrade process.

Teams update

Verify that the teams on the PCI server are also on the Cisco MeetingPlace 8100 series server; if not, recreate the teams.



Performing Postupgrade Procedures

Perform the following steps to complete the PCI server to Cisco MeetingPlace 8100 series server upgrade:


Step 1 Verify that the voice file is correct.

Step 2 Redirect all T1s from the PCI server to the Cisco MeetingPlace 8100 series server if needed.

Step 3 Verify the meetings that were scheduled during preupgrade tasks by performing the following tasks:

a. Run a raw data meeting detail report.

b. Compare the PCI server dbsize output to the Cisco MeetingPlace 8100 series server dbsize output.

Step 4 Verify that recordings and attachments were converted.

Step 5 Delete each gateway pointing to the PCI server at the gateway.

Step 6 Disconnect the LAN from the current PCI.

Step 7 Change the Domain Name System (DNS) to point to the new IP address of Cisco MeetingPlace 8100 series server.

Step 8 Install the Cisco MeetingPlace for Outlook if necessary.

Step 9 Add all gateways and ensure that the gateways point to the Cisco MeetingPlace 8100 series server.


Note Once you attach Cisco MeetingPlace Web Conferencing gateway, the Cisco MeetingPlace Web Conferencing database will be updated with the data from the Cisco MeetingPlace Audio Server system.


Step 10 Connect the T1 to the Cisco MeetingPlace 8100 series server.


Verifying Cisco MeetingPlace System Functionality

To verify Cisco MeetingPlace system functionality, complete the following tasks in this order:

Task
Yes
No

Check for alarms and conflicts.

Did you note any alarms?

Were there any errors or conflicts reported in the conversion trace?

   

In the MeetingTime Configuration tab, verify that the following system parameters were transferred:

System and Usage parameters

Other Cisco MeetingPlace servers

All users, groups, and teams

All meeting categories

Flex fields

Ports and port groups

System options

System parameters

Network management information and community

Server configuration

NS site configuration

Company information

   

Check the system's date and time.

   

From the Cisco MeetingPlace 8100 series server, ping the IP address of the Cisco MeetingPlace 8100 series server and the default gateway to verify LAN connectivity.

   

Enter swstatus and verify that all software have been updated with the correct releases and have a status of up.

   

Check the server telephony and Cisco MeetingPlace Audio Server by completing the following tasks:

1. From the CLI prompt, enter spanstat -s to verify the T1s are up.

2. To verify that all ports are idle, enter spanstat -all.

3. To place a test call, enter activity and select option 4.

4. Call in to the Cisco MeetingPlace Audio Server system.

5. Verify that you can schedule and attend a meeting.

6. Verify that you hear the Welcome to MeetingPlace greeting in the correct language.

7. Verify that you can log in as a profiled user.

8. Verify that you can schedule and attend an immediate meeting.

9. Verify that you can access all in-session features, such as break-out session and outdial.

   

Verify MeetingTime functionality by completing the following tasks:

1. Start MeetingTime on one or more computers.

2. Verify that the correct number of licenses has been entered by choosing Configure > System Options > Workstation Connections.

3. Log in as a technician.

4. To create a profiled user, choose Configure > User Profiles.

5. Log in as the profiled user that you just created.

6. Log in as a profiled user that you imported from the PCI server.

   

By using MeetingTime, verify that you can schedule meetings.

Can you successfully schedule a meeting?

Did the system generate a meeting ID?

Can you invite participants (profile, guest, and other server) and use the MeetingTime page function to notify one of the participants.

Does the page work?

If applicable, does the multiserver meeting connect?

Can you successfully schedule a continuous meeting?

   

Double-click the meeting on the whiteboard to verify that you can call in to the meeting that you just scheduled.

Can the system dial out?

Can you dial in to the Cisco MeetingPlace Audio Server system?

As a guest and as a profiled user, can you join one of the meetings that you just scheduled?

Can you find the meeting that you just joined in the In Session tab?

Can you record the meeting?

Can you listen to the recording through the voice user interface?

   

Terminate the meeting and verify that it shows up in the Review Tab.

   

Verify that you can run reports.

Can you run a Raw Meeting Details Info report and save it to a file?

Can you run the Conferencing Use report?

   

If necessary, schedule a meeting from Cisco MeetingPlace Web Conferencing and ensure that you perform the following tasks:

1. Set Recording to Yes.

2. Add a sample file as attachment.

3. Enter text for the Meeting Description.

   

Verify Cisco MeetingPlace Web Conferencing functionality.

Is the e-mail notification sent out?

Is the format of the notification correct?

Is the click-to-attend link correct?

Can you join the meeting and start recording?

   

Join a web conference from two PCs and verify Cisco MeetingPlace Web Conferencing functionality by sharing and collaborating.

   

Hang up and by using MeetingTime, terminate the meeting.

   

Log in to Cisco MeetingPlace Web Conferencing as a profiled user and review the meeting through the web to make sure that the recordings and attachments are posted.

   

Verify that you can still see the links to meetings and can download attachments from past meetings.

   

If necessary, schedule a Cisco MeetingPlace meeting from Outlook and ensure that you perform the following tasks:

1. Invite a few users.

2. Specify a meeting ID.

   

Verify Cisco MeetingPlace for Outlook functionality.

Is the e-mail notification sent out?

Is the format of the notification correct?

Can you attend the meeting by using the click-to-attend link?

   

Upgrading the PCI Server to Cisco MeetingPlace 8100 Series Server Example

disk backups have been disabled.
reenable with "save" after conversion is complete.
work area mounted on /dev/disk2e
WARNING: all data in this directory will be deleted. continue? (y/n)
y
Enter User Id: user
Enter Password: 
Enter PCI System IP Address (*not* the hostname!): 38.246.124.20
38.246.124.20
checking network connectivity with primary
port 5006 OK
port 5001 OK
conversion started!
work area mounted on /dev/disk2e
conversion starting at Wed Nov 21 19:25:13 PST 2001
no completed units found; conversion starting with primary
copying /lat/db/conf_att.dbd
copying /lat/db/pegs.dbd
copying /lat/db/config.dbd
copying /lat/db/podata.dbd
copying /lat/db/conflite.dbd
copying /lat/db/prompt.dbd
copying /lat/db/db.dbd
copying /lat/db/res.dbd
copying /lat/db/db_query.dbd
copying /lat/db/reslite.dbd
copying /lat/db/deletedrec.dbd
copying /lat/db/status.dbd
copying /lat/db/flexmenu.dbd
copying /lat/db/tcnfg.dbd
copying /lat/db/gen.dbd
copying /lat/db/userlist.dbd
copying /lat/db/genlite.dbd
copying /lat/db/unit
unit
TIMESTAMP Wed Nov 21 19:25:17 2001  (300)
TIMESTAMP Wed Nov 21 19:25:17 2001  (301)
merging from 38.246.124.20 (goldengate-ns), version 4.3.0
options:
ignore past = FALSE
ignore voice = FALSE
use sched params = FALSE
disable sched = FALSE
commit = TRUE
checking network connectivity: VP 2
connection OK
hashtab initialized; sz=250000, capacity=750000, keysz=12, memused=24000000
starting database copy from NS at Wed Nov 21 19:25:18 2001
copying /lat/db/billinginfo
copying /lat/db/companyinfo
copying /lat/db/filestats
copying /lat/db/hwconfig
copying /lat/db/hwstats
copying /lat/db/option
copying /lat/db/outdialtrans
copying /lat/db/netmgtinfo
copying /lat/db/netmgtcomm
copying /lat/db/unit
copying /lat/db/site
copying /lat/db/scsi
copying /lat/db/swconfig
copying /lat/db/swstats
copying /lat/db/systemconfig
copying /lat/db/timezone
copying /lat/db/mtgcategory
copying /lat/db/remoteserver
copying /lat/db/didcnfgconfig
copying /lat/db/schedparamsconfig
copying /lat/db/FMAppRec
copying /lat/db/FMStateTable
copying /lat/db/CustAppPrompt
copying /lat/db/FMPlayPrompt
copying /lat/db/FMGotoApp
copying /lat/db/FMOptionMenu
copying /lat/db/FMHangUp
copying /lat/db/FMFindMtg
copying /lat/db/FMReviewMtgMat
copying /lat/db/FMGetProfile
copying /lat/db/user
read  (10000000)
read  (20000000)
read  (30000000)
read  (40000000)
read  (50000000)
read  (60000000)
read  (70000000)
read  (80000000)
read  (90000000)
read  (100000000)
read  (110000000)
read  (120000000)
read  (130000000)
read  (140000000)
read  (150000000)
read  (160000000)
read  (170000000)
read  (180000000)
read  (190000000)
read  (200000000)
copying /lat/db/group
copying /lat/db/flexfield
copying /lat/db/pomailbox
copying /lat/db/pomsgdata
read  (10000000)
read  (20000000)
read  (30000000)
read  (40000000)
copying /lat/db/prompt
copying /lat/db/outdial
copying /lat/db/notification
copying /lat/db/userlist
read  (10000000)
read  (20000000)
read  (30000000)
copying /lat/db/userlistmem
read  (10000000)
database copy complete at Wed Nov 21 19:30:25 2001
starting NS merge at Wed Nov 21 19:30:25 2001
converting 4.3 system
option
TIMESTAMP Wed Nov 21 19:30:25 2001  (300)
Have 168 of option Access Ports
Have 120 of option Conference Ports
Have 200 of option Workstation Connections
Have 120 of option MeetingNotes Voice Option
Have 2 of option Flex Menu Option
Have 1 of option MeetingPlace for Notes
Have 0 of option Reserved for future use
Have 4 of option SNMP Option
Have 3 of option Languages
Have 120 of option Notification Option
Have 1 of option Fax Gateway
Have 120 of option MeetingNotes Data
Have 0 of option Exchange Dataconferencing
Have 1 of option SameTime Interface
Have 1 of option MeetingPlace for Outlook
Have 0 of option E-mail Gateway (MAPI)
Have 1 of option MeetingPlace WebPublisher
Have 1 of option Network Server
Have 1 of option Shadow Network Server
Have 120 of option Data Conferencing Option
Have 1 of option Directory Integration Option
Have 1 of option E-mail Gateway (SMTP)
TIMESTAMP Wed Nov 21 19:30:25 2001  (301)
companyinfo
TIMESTAMP Wed Nov 21 19:30:25 2001  (300)
TIMESTAMP Wed Nov 21 19:30:25 2001  (301)
swconfig
TIMESTAMP Wed Nov 21 19:30:25 2001  (300)
TIMESTAMP Wed Nov 21 19:30:25 2001  (301)
Systemconfig
.....
.....
.....
Mtg ID Conflict: Date:  Mon Jul 16 12:45:00 2001  MtgID: 7248
Mtg ID Conflict: Date:  Wed Nov 14 07:03:06 2001  MtgID: 847282
Mtg ID Conflict: Date:  Wed Nov 14 11:47:56 2001  MtgID: 47472
Mtg ID Conflict: Date:  Mon Nov 19 11:47:28 2001  MtgID: 742773
Mtg ID Conflict: Date:  Tue Oct  9 09:46:25 2001  MtgID: 7464835
Mtg ID Conflict: Date:  Wed Sep  5 08:57:01 2001  MtgID: 28846780
 Found 13 conflicts ...
Done!!!
merge for VP 2 complete at Wed Nov 21 22:25:13 2001

conversion completed at Wed Nov 21 22:25:17 2001

Related Documentation

For additional Cisco MeetingPlace information, see the following documentation:

Guide to Cisco MeetingPlace Conferencing Documentation and Support

http://www.cisco.com/univercd/cc/td/doc/product/conf/mtgplace/roadmap.htm

Cisco MeetingPlace Audio Server documentation for your release

http://www.cisco.com/univercd/cc/td/doc/product/conf/mtgplace/audio/index.htm

Obtaining Documentation

Cisco documentation and additional literature are available on Cisco.com. Cisco also provides several ways to obtain technical assistance and other technical resources. These sections explain how to obtain technical information from Cisco Systems.

Cisco.com

You can access the most current Cisco documentation at this URL:

http://www.cisco.com/univercd/home/home.htm

You can access the Cisco website at this URL:

http://www.cisco.com

You can access international Cisco websites at this URL:

http://www.cisco.com/public/countries_languages.shtml

Ordering Documentation

You can find instructions for ordering documentation at this URL:

http://www.cisco.com/univercd/cc/td/doc/es_inpck/pdi.htm

You can order Cisco documentation in these ways:

Registered Cisco.com users (Cisco direct customers) can order Cisco product documentation from the Ordering tool:

http://www.cisco.com/en/US/partner/ordering/index.shtml

Nonregistered Cisco.com users can order documentation through a local account representative by calling Cisco Systems Corporate Headquarters (California, USA) at 408 526-7208 or, elsewhere in North America, by calling 1 800 553-NETS (6387).

Documentation Feedback

You can send comments about technical documentation to bug-doc@cisco.com.

You can submit comments by using the response card (if present) behind the front cover of your document or by writing to the following address:

Cisco Systems
Attn: Customer Document Ordering
170 West Tasman Drive
San Jose, CA 95134-9883

We appreciate your comments.

Obtaining Technical Assistance

For all customers, partners, resellers, and distributors who hold valid Cisco service contracts, Cisco Technical Support provides 24-hour-a-day, award-winning technical assistance. The Cisco Technical Support Website on Cisco.com features extensive online support resources. In addition, Cisco Technical Assistance Center (TAC) engineers provide telephone support. If you do not hold a valid Cisco service contract, contact your reseller.

Cisco Technical Support Website

The Cisco Technical Support Website provides online documents and tools for troubleshooting and resolving technical issues with Cisco products and technologies. The website is available 24 hours a day, 365 days a year, at this URL:

http://www.cisco.com/techsupport

Access to all tools on the Cisco Technical Support Website requires a Cisco.com user ID and password. If you have a valid service contract but do not have a user ID or password, you can register at this URL:

http://tools.cisco.com/RPF/register/register.do


Note Use the Cisco Product Identification (CPI) tool to locate your product serial number before submitting a web or phone request for service. You can access the CPI tool from the Cisco Technical Support Website by clicking the Tools & Resources link under Documentation & Tools. Choose Cisco Product Identification Tool from the Alphabetical Index drop-down list, or click the Cisco Product Identification Tool link under Alerts & RMAs. The CPI tool offers three search options: by product ID or model name; by tree view; or for certain products, by copying and pasting show command output. Search results show an illustration of your product with the serial number label location highlighted. Locate the serial number label on your product and record the information before placing a service call.


Submitting a Service Request

Using the online TAC Service Request Tool is the fastest way to open S3 and S4 service requests. (S3 and S4 service requests are those in which your network is minimally impaired or for which you require product information.) After you describe your situation, the TAC Service Request Tool provides recommended solutions. If your issue is not resolved using the recommended resources, your service request is assigned to a Cisco TAC engineer. The TAC Service Request Tool is located at this URL:

http://www.cisco.com/techsupport/servicerequest

For S1 or S2 service requests or if you do not have Internet access, contact the Cisco TAC by telephone. (S1 or S2 service requests are those in which your production network is down or severely degraded.) Cisco TAC engineers are assigned immediately to S1 and S2 service requests to help keep your business operations running smoothly.

To open a service request by telephone, use one of the following numbers:

Asia-Pacific: +61 2 8446 7411 (Australia: 1 800 805 227)
EMEA: +32 2 704 55 55
USA: 1 800 553-2447

For a complete list of Cisco TAC contacts, go to this URL:

http://www.cisco.com/techsupport/contacts

Definitions of Service Request Severity

To ensure that all service requests are reported in a standard format, Cisco has established severity definitions.

Severity 1 (S1)—Your network is "down," or there is a critical impact to your business operations. You and Cisco will commit all necessary resources around the clock to resolve the situation.

Severity 2 (S2)—Operation of an existing network is severely degraded, or significant aspects of your business operation are negatively affected by inadequate performance of Cisco products. You and Cisco will commit full-time resources during normal business hours to resolve the situation.

Severity 3 (S3)—Operational performance of your network is impaired, but most business operations remain functional. You and Cisco will commit resources during normal business hours to restore service to satisfactory levels.

Severity 4 (S4)—You require information or assistance with Cisco product capabilities, installation, or configuration. There is little or no effect on your business operations.

Obtaining Additional Publications and Information

Information about Cisco products, technologies, and network solutions is available from various online and printed sources.

Cisco Marketplace provides a variety of Cisco books, reference guides, and logo merchandise. Visit Cisco Marketplace, the company store, at this URL:

http://www.cisco.com/go/marketplace/

The Cisco Product Catalog describes the networking products offered by Cisco Systems, as well as ordering and customer support services. Access the Cisco Product Catalog at this URL:

http://cisco.com/univercd/cc/td/doc/pcat/

Cisco Press publishes a wide range of general networking, training and certification titles. Both new and experienced users will benefit from these publications. For current Cisco Press titles and other information, go to Cisco Press at this URL:

http://www.ciscopress.com

Packet magazine is the Cisco Systems technical user magazine for maximizing Internet and networking investments. Each quarter, Packet delivers coverage of the latest industry trends, technology breakthroughs, and Cisco products and solutions, as well as network deployment and troubleshooting tips, configuration examples, customer case studies, certification and training information, and links to scores of in-depth online resources. You can access Packet magazine at this URL:

http://www.cisco.com/packet

iQ Magazine is the quarterly publication from Cisco Systems designed to help growing companies learn how they can use technology to increase revenue, streamline their business, and expand services. The publication identifies the challenges facing these companies and the technologies to help solve them, using real-world case studies and business strategies to help readers make sound technology investment decisions. You can access iQ Magazine at this URL:

http://www.cisco.com/go/iqmagazine

Internet Protocol Journal is a quarterly journal published by Cisco Systems for engineering professionals involved in designing, developing, and operating public and private internets and intranets. You can access the Internet Protocol Journal at this URL:

http://www.cisco.com/ipj

World-class networking training is available from Cisco. You can view current offerings at this URL:

http://www.cisco.com/en/US/learning/index.html