Worldwide [change] |Account |Register |About Cisco
Guest

Hierarchical Navigation

Cisco Unified MeetingPlace

MeetingPlace Server Merge Procedure

Downloads

Document ID: 51511


Contents

Introduction
Prerequisites
      Network Bandwidth Requirements
      Components Used
      Conventions
Background Information
      License Requirements
Checklist Before Merge
      Network System Checklist Before Merge
      Standalone Server Checklist Before Merge
Estimated Timing of Merge Process
      Brand New Server With Empty Database
      Existing Server With Valid Database
Merge Procedures
      Log into Network Server
      Log into Standalone Server
      Sample Remote Server Merge Output
Checklist After Merge
Related Information

Introduction

Network merge is the process in which a standalone Cisco MeetingPlace server is added (or merged) into a group of networked Cisco MeetingPlace servers (also known as a network system) so that it becomes a new member unit of that group. A networked Cisco MeetingPlace system consists of a network server, one to eight conference servers, and possibly a shadow server.

The merge process will merge the database of the standalone server into the database of the network server. The database contains profiles and meetings that existed on the standalone and will become part of the network server’s database.

Prerequisites

Network Bandwidth Requirements

Network System:

  • The network server, shadow server, and the conference server with the lowest number (typically, it is Conference Server 1) must be deployed on the same network segment. This network segment is always referred to as site 0 or home site in the Cisco MeetingPlace terminology.

Standalone Server:

Once merged into the network system, the communication between this unit and the network server must be:

  • 250 ms round trip latency, with no more than 1 percent packet loss in a 30-second period.

  • 384 Kb/s peak bandwidth per each fully loaded, 120-port remote conference server.

    Ports		Bandwidth (kbits/sec)
72 or less	256
96		320
120		384
240             384*2

Components Used

The information in this document is based on these software and hardware versions:

  • Network system and the standalone server must be running Cisco MeetingPlace Server Release 4.1.2 or later.

  • Network system and the standalone server must be running the same version. If they are running different versions of Cisco MeetingPlace server software, upgrade the one with the lower Cisco MeetingPlace server release to the higher version.

The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If your network is live, make sure that you understand the potential impact of any command.

Conventions

For more information on document conventions, refer to the Cisco Technical Tips Conventions.

Background Information

License Requirements

Prior to the actual merge, the total number of user licenses on the network system may need to be increased to accommodate the additional capacity from the standalone server once it is merged into the network system.

Additional telephony capacity from the standalone server directly affects these license options:

  • Access Ports

  • Conference Ports

The ability to support additional Cisco MeetingPlace users after the merge indirectly affects these license options, which may or may not need to be updated, depending on customer usage requirements:

  • Cisco MeetingNotes Voice Option

  • Cisco MeetingNotes Data Option

  • Notification Option

  • Data Conferencing Option

  • Workstation

Cisco MeetingPlace licenses are generated based on the Ethernet address of the network server. When requesting new licenses, be sure that you provide the correct Ethernet address of the network server.

Checklist Before Merge

In addition to verifying the requirements listed above, this section describes other preparatory steps that should be performed on the standalone server before it is merged.

Network System Checklist Before Merge

  • Conflict Meeting ID After Merge

    Run the Raw Meeting Detail Report and compare it with the same report from the standalone server. It is strongly recommended that you delete any meetings with a meeting ID conflict (same ID and schedule time overlaps) from either the network system or the standalone server.

Standalone Server Checklist Before Merge

  • Telephony Configuration information

    Record the configurations of dcard, span, and port. You will need to re-configure these parameters after the merge. Keep in mind that the port group setting is a system-wide setting. Make sure there is no port group conflict with the network server.

  • LAN Configuration Information

    Record the network and site configurations, such as server IP, subnet mask IP, broadcast IP, default gateway IP, etc. (use command: net).

  • Conflict Meeting ID After Merge

    Run the Raw Meeting Detail Report and compare it with the same report from the network system. It is strongly recommended that you delete any meetings with a meeting ID conflict (same ID and schedule time overlaps) from either the network system or the standalone server.

    If meeting ID conflicts exists before the merge, they will continue to exist after the merge. If single number access is implemented on the network system, then it is possible that a user who calls into the Cisco MeetingPlace system will be directed to the wrong conference server, since the same meeting ID exists on more than one of the conference servers. In this situation, the user will be directed to the first conference server that returned a valid response to the network server, and the user may end up joining the wrong meeting.

    It is important to communicate this design to the customer before the merge takes place.

  • Profiles Replication/Duplication

    • If there are same profiles that exist in both the network server and the standalone server (same profile means exactly the same user ID and profile number), then after the merge, the system will default these profiles to the existing profile settings on the network server. The most significant impact in such matters will be their scheduling home server. It is recommended that you run the Raw Profile Report after the merge, update the changes, then import them back to the system.

    • If there are partial-same profiles that exist in both the network server and the merging standalone server (partial-same means either the same user ID or the same profile number), then after the merge, the system will create a new user profile with either a different user ID or a different profile number by appending the conference server number to it. For example, you are merging the standalone server into the network system as Conference Server 5, then the duplicate ID of latitude on the standalone will become latitude5 in the merged database.

  • Teams

    Teams information on the standalone server will not be merged into the network server database. It is recommended that you save the teams information (for instance run the Team Info Report) before the merge, then recreate them after the merge.

  • Cisco MeetingTime Telephony Access Parameters

    In Cisco MeetingPlace Release 4.2 or earlier, the Telephony Access parameter settings (such as server phone number, Direct Inward Dialing [DID] range number settings, etc.) for the standalone server will not be propagated to the network server during the merge process.

    It is recommended that you save those settings before the merge, then re-enter them into the corresponding conference server settings after the merge.

  • Translation Tables

    The translation tables for the standalone server will not be propagated to the network server during the merge process. After the merge, only the translation tables on the network server will be used. You must understand the customer’s translation table requirements for the standalone server before proceeding with the merge.

Estimated Timing of Merge Process

Brand New Server With Empty Database

The time required to merge a new standalone server with a blank database will be no more than 30 minutes.

Existing Server With Valid Database

Time required to merge a standalone server that has been in operation will depend on two factors:

  1. The size of the database on both the standalone server and the network server.

  2. The LAN/WAN latency between the standalone server and the network server.

The estimate is as follows:

  • It is based on the network round trip latency of 40-50 ms or less.

  • There are two merging phases during the process.

    • Phase 1—The standalone server’s database files are copied to the network server then merged. This will take approximately 60 minutes.

    • Phase 2—The standalone server’s database files are merged into network server’s database. This will take approximately 10 minutes per every 1000 conference records in the standalone server.

      For example, if the network round trip latency is less than 50 ms, and the standalone conference records total 6000, then you will be looking at about 60 + 10*(6000/1000) = 120 minutes.

Merge Procedures

Log into Network Server

Complete these steps:

  1. Run the net command to select the unit number that will eventually represent the to-be-merged server.

  2. Select 2 to modify the server configuration

  3. Enter y when prompted “Would you like to activate this server and site (y/[n])?”

  4. If the server will be a remote conference server, then select 2 to “Select a different site for this server” and enter a new site number.

    This is a very important step. You must select the remote site number before you can enter the IP information.

    If the standalone server is to be added as a local conference server, skip to step 5.

  5. Enter the IP, broadcast IP, subnet mask, Ethernet Address, and default gateway IP.

Log into Standalone Server

Complete these steps:

  1. Run the net command to display the server configuration. Make sure the server configurations match the network information you entered into the network server. In most cases, the site is 0. You need to change it if this server is going to be a remote site after the merge.

  2. 2. Run the setup command to set its unit type. The five choices are:

    1. Standalone.

    2. Networked, home site (VP/LOCAL).

    3. Networked, remote site (VP/REMOTE).

    4. Network server.

    5. Shadow network server.

    Specific to the merge, you will select either option 2 or option 3, depending on whether the standalone server is to become a local or remote conference server, relative to the home site.

  3. If you choose option 2, networked, home site (VP/LOCAL), then go to step 4.

    If you choose option 3, networked, home site (VP/REMOTE), you will be prompted to enter the network parameters, such as the IP address for the unit, IP for the network server.

  4. You will be asked as to how database should be merged. You have three choices on how to treat the current database on this server:

    1. It is new from the factory or contains no useful data. Wipe it clean.

    2. It is a valid standalone server database that needs to be merged with the network server database.

    3. It is a valid database, already merged. Leave it alone.

  5. Follow the instructions to select the server region and set server time zone.

  6. 6. Enter restart enable.

    The server will go through three reboots, then begin to copy and merge files into the network system.

Sample Remote Server Merge Output

ftwr-conf-1:tech$ net
 1) View the server & site configuration
 2) Modify the server configuration
 3) Select another server (current unit = #0)
99) Quit
Select: 1
Current server configuration:
    Unit:                 #0 (ftwr-conf-1)
    Active:               YES
    Description:          FTWR LATITUDE CONF SERVER
    Kind:                 Conference server
    IP Address:           38.246.125.252
    Ethernet address:     0000c0db95e1
    NTP servers:          none
    Site:                 #0 (FTWR)
    Site subnet mask:     255.255.254.0
    Site broadcast addr:  38.246.125.255
    Site default gateway: 38.246.124.1
    Route daemon:         disabled
 1) View the server & site configuration
 2) Modify the server configuration
 3) Select another server (current unit = #0)
99) Quit
Select: 99
Unit class = SINGLE/LOCAL
ftwr-conf-1:tech$ swstatus 
Conference server 4.X.X   S/N: 100357    Union Pacific Railroad
System status: Operating
System mode: Up
Temperature: Unknown
Power supply: OK

MODULE NAME          STATUS     VERSION
SIM                  UP         "02/11/99 12:05 MPBUILD-rel400n"
LSH                  UP         "02/11/99 09:47 MPBUILD-rel400n"
SNMPD                UP         "02/11/99 13:18 MPBUILD-rel400n"
DBSERVER             UP         "02/16/99 15:18 UPDATE-rel400n"
DBQSERVER            UP         "02/16/99 15:18 UPDATE-rel400n"
POSERVER             UP         "02/11/99 11:06 MPBUILD-rel400n"
CPSERVER             UP         "02/11/99 11:01 MPBUILD-rel400n"
CONFSCHED            UP         "03/02/99 13:39 UPDATE-rel400n"
WSSERVER             UP         "02/11/99 12:09 MPBUILD-rel400n"
VOICESERVER          UP         "02/17/99 16:14 UPDATE-rel400n"
GWSIMMGR             UP         "03/02/99 13:37 UPDATE-rel400n"

UNIT SITE  STATUS    RUN LEVEL  UNIT KIND   LAST ATTACH

ftwr-conf-1:tech$ down
Are you sure (y/n)? y
Checking to see if the system is loaded...OK
System DOWN procedure has been initiated.
The MeetingPlace software is DOWN
The system is DOWN.
ftwr-conf-1:tech$ setup
This program determines the basic personality of this unit.
Current unit class = SINGLE
Current site class = LOCAL

Select the unit class:
 1) MeetingPlace -- Standalone (SINGLE).
 2) MeetingPlace -- Networked, home site (VP/LOCAL).
 3) MeetingPlace -- Networked, remote site (VP/REMOTE).
 4) Network Server (DB).
 5) Shadow Network Server (SHADOW).
99) Quit.
Select: 3

!--- For remote units it is necessary to manually enter various network
!--- parameters.  These will be used to establish the initial communication
!--- with the network server for this system.


Host name for this unit [ftwr-conf-1]: uprrfwt1
IP address for this unit [38.246.125.252]: 
Subnet mask [255.255.254.0]: 
Broadcast address [38.246.125.255]: 
Default gateway IP address [38.246.124.1]: 
Host name of the network server []: pyramid
IP address of the network server []: 172.20.5.0
IP address of shadow network server, if any []: 171.68.222.57
Current database label information:
  Revision:     4.0.0
  Kind:         standalone conference server
  DB serial #:  922837649

You have three choices on how to treat the current database on this server:
1)  It is new from the factory or contains no useful data.  Wipe it clean.
2)  It is a valid standalone server database that needs to be merged with
    the network server database.
3)  It is a valid database, already merged.  Leave it alone.
99) Cancel setup.
Select:2


!--- This selection will cause the database on this server to be merged with
!--- the database on the network server.  This is appropriate if this server
!--- was operating in a standalone mode and you are now attaching it to a
!--- network server.

Proceed (y/[n])? y
Please select the region where this server is installed:
  1) Europe
  2) Far East
  3) North America
 99) quit
Select: 3
Please select the time zone for this server.

The following time zones are available:
  1) America/Anchorage
  2) America/Chicago
  3) America/Denver
  4) America/Edmonton
5) America/Halifax
  6) America/Indianapolis
  7) America/Los_Angeles
  8) America/Montreal
  9) America/New_York
 10) America/Phoenix
 11) America/Vancouver
 12) America/Winnipeg
 13) Pacific/Honolulu
 99) no action
Select: 7

The local time zone (PST) is 480 minutes west of GMT
Daylight savings time policy: US/Canada

Please confirm (y/n): y
DONE
You have selected a new configuration for this unit.
Unit class = VP
Site class = REMOTE
Update the initialization file (y/[n])? y
DONE
NOTE: Changes take effect with the next restart of the unit.
Unit class = VP/REMOTE
ftwr-conf-1:tech$ 
ftwr-conf-1:tech$ restart
Are you sure (y/n)? y
Checking to see if the system is loaded...
The System Integrity Manager is not running.
Restarting the system... 
**** LynxOS is down **** 
LynxOS 386/486/Pentium PC-AT Version 2.4.0
Copyright 1987-1996 Lynx Real-Time Systems Inc.
All rights reserved.

LynxOS (x86) created Mon Dec  7 13:58:43 1998

             MeetingPlace by Latitude Communications

Fri Apr 23 10:34:49 PDT 1999
Startup flags = a
SCSI adapter is Adaptec 2740 (EISA).
Disk 1 is mounted.
Disk 2 is mounted.
Unit class is networked conference server (VP/REMOTE).
Bus architecture is EISA.
Ethernet device is "wd3e0".
Resetting system file ownerships:
Removing set-uid permissions:
Updating files and setting permissions:
Replacing /lat/bin/viewexlog with /lat/etc/viewexlog.vp
Replacing /lat/techbin/alarm with /lat/etc/alarm.vp
Replacing /lat/techbin/clearalarm with /lat/etc/clearalarm.vp
Replacing /lat/techbin/exc with /lat/etc/exc.vp
Replacing /lat/techbin/help with /lat/etc/help.vp
Replacing /lat/techbin/diskoptions with /lat/etc/diskoptions.vp
Replacing /lat/techbin/setsn with /lat/etc/setsn.vp
Removing junk files:
./tmp/gwsimgr/core
lat/db/vista.taf
/usr/users/csc/lynx.os.ns
/usr/users/csc/lynx.os.vp
/usr/users/csc/nodetab.ns
/usr/users/csc/nodetab.vp
/usr/users/csc/om-kiran
/usr/users/csc/gen.os
/usr/users/csc/logit
/usr/users/csc/syslogd
/tmp/dbtasklocks/SETSN
Links:
Recreating the file system table:
Network setup:
Unit class = VP/REMOTE
Done.
Restarting...
 
**** LynxOS is down **** 
LynxOS 386/486/Pentium PC-AT Version 2.4.0
Copyright 1987-1996 Lynx Real-Time Systems Inc.
All rights reserved.

LynxOS (x86) created Mon Dec  7 13:58:43 1998

             MeetingPlace by Latitude Communications

Fri Apr 23 10:36:43 PDT 1999
Startup flags = a
SCSI adapter is Adaptec 2740 (EISA).
Disk 1 is mounted.
Disk 2 is mounted.
Unit class is networked conference server (VP/REMOTE).
Bus architecture is EISA.
Ethernet device is "wd3e0".
IP forwarding DISABLED (0).
Initializing the back panel serial port...done
Initializing the modem.../lat/bin/initmodem ... 
/lat/bin/initmodem: type is `USR Sportster 28.8' 
/lat/bin/initmodem: modem initialized 
Installing Latitude drivers... 
MSC #0 (Rev B4) in slot 4
PRC #0 (Rev B2) in slot 5
PRC #1 (Rev B2) in slot 6
PRC #2 (Rev B2) in slot 7
Making nodes...done.
Kernel WDT autostrobe disabled
add net default: gateway 38.246.124.1
23 Apr 10:39:02 ntpdate[25]: step time server 172.20.5.0 offset 121.527054
/bin/mv: rename: File or directory doesn't exist
Waiting for network server "pyramid" to be ready...OK
Checking for software updates.
           6 files differ.
Downloading updated files from pyramid.
Updating /lat/bin/cs-db...OK
Updating /lat/bin/ConfSchd...OK
Updating /lat/bin/db...OK
Updating /lat/techbin/release...OK
Updating /lat/etc/db.tar.Z...OK
Updating /lat/man/gwsim.l...OK
The MeetingPlace software now is up to date (updated).
The system will now reboot.
 
**** LynxOS is down **** 
LynxOS 386/486/Pentium PC-AT Version 2.4.0
Copyright 1987-1996 Lynx Real-Time Systems Inc.
All rights reserved.

LynxOS (x86) created Mon Dec  7 13:58:43 1998

             MeetingPlace by Latitude Communications

Fri Apr 23 10:41:57 PDT 1999
Startup flags = a
SCSI adapter is Adaptec 2740 (EISA).
Disk 1 is mounted.
Disk 2 is mounted.
Unit class is networked conference server (VP/REMOTE).
Bus architecture is EISA.
Ethernet device is "wd3e0".
Resetting system file ownerships:
Removing set-uid permissions:
Updating files and setting permissions:
Removing junk files:
Links:
Recreating the file system table:
Network setup:
Unit class = VP/REMOTE
Done.
Restarting...
 
**** LynxOS is down **** 
LynxOS 386/486/Pentium PC-AT Version 2.4.0
Copyright 1987-1996 Lynx Real-Time Systems Inc.
All rights reserved.

LynxOS (x86) created Mon Dec  7 13:58:43 1998

             MeetingPlace by Latitude Communications

Fri Apr 23 10:43:46 PDT 1999
Startup flags = a
SCSI adapter is Adaptec 2740 (EISA).
Disk 1 is mounted.
Disk 2 is mounted.
Unit class is networked conference server (VP/REMOTE).
Bus architecture is EISA.
Ethernet device is "wd3e0".
IP forwarding DISABLED (0).
Initializing the back panel serial port...done
Initializing the modem.../lat/bin/initmodem ... 
/lat/bin/initmodem: type is `USR Sportster 28.8' 
/lat/bin/initmodem: modem initialized 
Installing Latitude drivers... 
MSC #0 (Rev B4) in slot 4
PRC #0 (Rev B2) in slot 5
PRC #1 (Rev B2) in slot 6
PRC #2 (Rev B2) in slot 7
Making nodes...done.
Kernel WDT autostrobe disabled
add net default: gateway 38.246.124.1
23 Apr 10:44:04 ntpdate[25]: step time server 172.20.5.0 offset 0.559013
Waiting for network server "pyramid" to be ready...OK
Checking for software updates.
The MeetingPlace software is up to date (time stamp match).

Ready to load the MeetingPlace application software modules.
Hit ^C now to interrupt system activation...54321...activating

Loading the System Integrity Manager...OK
Checking for out of date database files
Setting the database serial number
Starting the database merge for unit 6
Copying database files to the network server: 
    user	(this will take approximately 20-30 minutes)
    group
    gentmp1
    gentmp2
    gentmp3
    flexfield
    gen.dbd
    billinginfo
    companyinfo
    filestats
    hwconfig
    hwstats
    option
    outdialtrans
    netmgtinfo
    netmgtcomm
    unit
    site
    promptstats
    scsi
    swconfig
    swstats
    systemconfig
    timezone
    mtgcategory
    remoteserver
    didcnfgconfig
    schedparamsconfig
    config.dbd
    analogcard
    masterswcard
    portrescard
    t1card
    t1span
    trunk
    trunkgroup
    e1card
    e1span
    tcnfg.dbd
    userlist	
!--- This will take approximately 10 minutes.

    userlistmem
    userlist.dbd
    prompt
    prompt.dbd
    FMAppRec
    FMStateTable
    CustAppPrompt
    FMPlayPrompt
    FMGotoApp
    FMOptionMenu
    FMHangUp
    FMFindMtg
    FMReviewMtgMat
    FMGetProfile
    flexmenu.dbd
    alarmentry
    exlogentry
    hwstatus
    swstatus
    exlogformat
    apps
    outdial
    notification	
!--- This will take approximately three minutes.

    schedfail
    gwstatus
    status.dbd
Starting the database merge on the network server (phase 1)
Copying the map file from the network server
Starting the local merge (phase 2)	
!--- Timing for this depends on the size of conference records. ~10 minutes / 1000 records.

Merge is complete!
The log file is /usr/adm/nsmerge.log
Restarting the server.
Checking to see if the system is loaded...OK
System DOWN procedure has been initiated.
MeetingPlace 4.0.0, Apr 23, 1999
user name: The MeetingPlace software is DOWN
---> Restarting the system
 
**** LynxOS is down **** 
LynxOS 386/486/Pentium PC-AT Version 2.4.0
Copyright 1987-1996 Lynx Real-Time Systems Inc.
All rights reserved.

LynxOS (x86) created Mon Dec  7 13:58:43 1998

             MeetingPlace by Latitude Communications

Fri Apr 23 11:29:51 PDT 1999
Startup flags = a
SCSI adapter is Adaptec 2740 (EISA).
Disk 1 is mounted.
Disk 2 is mounted.
Unit class is networked conference server (VP/REMOTE).
Bus architecture is EISA.
Ethernet device is "wd3e0".
IP forwarding DISABLED (0).
Initializing the back panel serial port...done
Initializing the modem.../lat/bin/initmodem ... 
/lat/bin/initmodem: type is `USR Sportster 28.8' 
/lat/bin/initmodem: modem initialized 
Installing Latitude drivers... 
MSC #0 (Rev B4) in slot 4
PRC #0 (Rev B2) in slot 5
PRC #1 (Rev B2) in slot 6
PRC #2 (Rev B2) in slot 7
Making nodes...done.
Kernel WDT autostrobe disabled
add net default: gateway 38.246.124.1
23 Apr 11:30:08 ntpdate[29]: adjust time server 172.20.5.0 offset -0.391368
Waiting for network server "pyramid" to be ready...OK
Checking for software updates.
The MeetingPlace software is up to date (time stamp match).

Ready to load the MeetingPlace application software modules.
Hit ^C now to interrupt system activation...54321...activating

Loading the System Integrity Manager...OK
*** Running the Voice File System rebuild.
Copying SCSI database down from network server...
/lat/db/scsi
/lat/db/scsi.unitid

Running vfptrfix on unit 6...
Establishing communication with the SIM...
Initializing the file system...
Getting the disk configuration status...
FSGetDiskConfigStatus failed, ret = a005e
Disk configuration inconsistency!
Disk 3 configured but no directories configured
Disk 4 configured but no directories configured
*** Restarting system after Voice File System rebuild.
Checking to see if the system is loaded...OK
System DOWN procedure has been initiated.
MeetingPlace 4.0.0, Apr 23, 1999
user name: The MeetingPlace software is DOWN
---> Restarting the system
 
**** LynxOS is down **** 
LynxOS 386/486/Pentium PC-AT Version 2.4.0
Copyright 1987-1996 Lynx Real-Time Systems Inc.
All rights reserved.

LynxOS (x86) created Mon Dec  7 13:58:43 1998

             MeetingPlace by Latitude Communications

Fri Apr 23 11:31:29 PDT 1999
Startup flags = a
SCSI adapter is Adaptec 2740 (EISA).
Disk 1 is mounted.
Disk 2 is mounted.
Unit class is networked conference server (VP/REMOTE).
Bus architecture is EISA.
Ethernet device is "wd3e0".
IP forwarding DISABLED (0).
Initializing the back panel serial port...done
Initializing the modem.../lat/bin/initmodem ... 
/lat/bin/initmodem: type is `USR Sportster 28.8' 
/lat/bin/initmodem: modem initialized 
Installing Latitude drivers... 
MSC #0 (Rev B4) in slot 4
PRC #0 (Rev B2) in slot 5
PRC #1 (Rev B2) in slot 6
PRC #2 (Rev B2) in slot 7
Making nodes...done.
Kernel WDT autostrobe disabled
add net default: gateway 38.246.124.1
23 Apr 11:31:46 ntpdate[29]: adjust time server 172.20.5.0 offset -0.397139
Waiting for network server "pyramid" to be ready...OK
Checking for software updates.
The MeetingPlace software is up to date (time stamp match).

Ready to load the MeetingPlace application software modules.
Hit ^C now to interrupt system activation...54321...activating

Loading the System Integrity Manager...OK
Loading the Command Shell...OK
Loading the Network Management Server...OK
Loading the Database Server...OK
Loading the Call Processing Module...OK
Loading the Conference Scheduler...OK
Loading the Voice User Interface ...OK
MeetingPlace 4.0.0, Apr 23, 1999
user name: 
Downloading to MSC.....OK
Downloading to PRC 0...OK
Downloading to PRC 1...OK
Downloading to PRC 2...OK
The MeetingPlace software is UP

user name: tech
Password:
Last login: Fri Apr 23 11:47:21 from pyramid
*************************************************************************
*			      MeetingPlace(tm)			 	*
*			by Latitude Communications			*
*									*
*	    Copyright (c) 1993-1998 Latitude Communications, Inc.	*
*			    All rights reserved.			*
*************************************************************************
Networked conference server 4.0.0
Fri Apr 23 12:20:30 PDT 1999
uprrfwt1:tech$ swstatus 
Networked conference server 4.0.0
System status: Operating
System mode: Up
Temperature: 33
Power supply: OK

MODULE NAME          STATUS     VERSION
SIM                  UP         "02/11/99 12:05 MPBUILD-rel400n"
LSH                  UP         "02/11/99 09:47 MPBUILD-rel400n"
SNMPD                UP         "02/11/99 13:18 MPBUILD-rel400n"
DBQSERVER            UP         "03/16/99 00:19 MPBUILD-HEAD"
CPSERVER             UP         "02/11/99 11:01 MPBUILD-rel400n"
CONFSCHED            UP         "02/16/99 15:20 UPDATE-rel400n"
VOICESERVER          UP         "02/17/99 16:14 UPDATE-rel400n"

UNIT SITE  STATUS    RUN LEVEL  UNIT KIND   LAST ATTACH
   0    0  OK        UP         NETSERV     04/23/99 11:32:00

uprrfwt1:tech$

Checklist After Merge

After the merge, some parameters may need to be reconfigured because the settings were lost during the merge process. Notable system behaviors are also described below.

  • Existing Conference Records Remain Intact

    Conference records — past or future — will continue to exist in those conference servers on which they were scheduled, and can be retrieved via various reports or trace utilities.

  • Profile Updates

    If profile conflicts occurred during the merge process, you need to resolve the conflicting (and hence, modified) profiles.

  • Translation Table Update

    If the newly merged conference server requires digit translation patterns that do not already exist in the translation table of the network system, you need to add those patterns into the translation table on network server.

  • Teams Update

    If there are teams that existed on the standalone server but is now missing on the network system, you need to re-create the teams.

  • Telephony Access Parameters Update

    Using Cisco MeetingTime, configure the telephony access information for the newly merged conference server.

  • Run the diskoptions command to install the system disk

    This information is wiped out during the merge process. You will need to restart the conference server.

  • Reconfigure Telephony Settings for the Conference Server

    After the merge, the telephony configurations of the newly merged conference server such as dcard, span, port will all be wiped out. You need to manually reconfigure those settings.

Related Information

Updated: Jan 31, 2006 Document ID: 51511