3Com VCX V7000 Maintenance Manual
  1. Manuals
  2. Brands
  3. 3Com Manuals
  4. IP Phone
  5. VCX V7000
  6. Maintenance manual
3Com VCX V7000 Maintenance Manual

3Com VCX V7000 Maintenance Manual

Ip telephony solution
Hide thumbs Also See for VCX V7000:
Table of Contents

Advertisement

Quick Links

Download this manual See also: User Manual, Installation and Maintenance Manual
VCX
™
Maintenance Guide
™
VCX
V7000 IP Telephony Solution
Convergence Application Suite
System Release 7.1
Part Number 900-0382-01 Rev AF
Published November 2007
http://www.3com.com/

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the VCX V7000 and is the answer not in the manual?

Questions and answers

Subscribe to Our Youtube Channel

Related Manuals for 3Com VCX V7000

Summary of Contents for 3Com VCX V7000

  • Page 1 ™ Maintenance Guide ™ V7000 IP Telephony Solution Convergence Application Suite System Release 7.1 Part Number 900-0382-01 Rev AF Published November 2007 http://www.3com.com/...
  • Page 2 3Com Corporation reserves the right to revise this documentation and to make changes in content from 01752-3064 time to time without obligation on the part of 3Com Corporation to provide notification of such revision or change. 3Com Corporation provides this documentation without warranty of any kind, either implied or expressed, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose.

  • Page 3: Table Of Contents

    ONTENTS BOUT UIDE Conventions Related Documentation Comments VCX S YSTEM AINTENANCE VERVIEW Network-based Telephony VCX Software Components VCX Hardware Configurations Single-Site Configurations Multi-Site Configurations VCX Maintenance Tasks About VCX Passwords VCX File and Directory Name Guidelines ONFIGURING THE ECORDS ERVICE Call Records Service Overview CDR Collection Accounting Service Groups...
  • Page 4 Editing Accounting Service Information in a Group Deleting an Accounting Service from a Group Listing All Configured Accounting Services Viewing Accounting Service Details Managing CDRs and Super CDRs Understanding CDR Fields Viewing CDRs Viewing Super CDRs QoS Monitoring Statistics VCX S ANAGING ERVERS Managing the Tomcat Web Server...
  • Page 5 Enabling Message Tracing Enabling Server Logging SNMP Support Managing the SIP Phone Downloader Starting the SIP Phone Downloader Stopping the SIP Phone Downloader Restarting the SIP Phone Downloader Managing the IP Messaging Service Verifying IP Messaging Service Status Starting the IP Messaging Service Stopping the IP Messaging Service Restarting the IP Messaging Service Managing Authorized SNMP Station Access...
  • Page 6 Clearing the Configurable Tables ANUALLY ONFIGURING ULTI ASTER EPLICATION Multi-Master Replication Overview Replicated Table Location Manually Configuring Replication for an IP Telephony Server or IP Telephony and Messaging Server Manually Configuring Region to Region Replication Verifying Replication at a Branch Office Verifying the Number of VCX Data Schemas in a Region Deleting Replication Errors VCX S...
  • Page 7 Configuring Accounting and Directory Services Adding Primary and Secondary Accounting Servers Adding Primary and Secondary Authentication and Directory Servers ANAGING CCOUNTS SING THE OMMAND NTERFACE Command Overview Using Single User Mode Command Modes Single User Mode Command Syntax Single User Mode Examples Using Batch Mode Managing User Accounts with an XML File Adding User Accounts with a CSV File...
  • Page 8 Multi-Site VCX System Upgrade Order Upgrading the Regional Authentication and Directory Servers Upgrading the Regional IP Messaging Servers Upgrading the Regional Call Servers Upgrading the Regional Call Records Server Upgrading Branch Offices Configuring UPS Monitoring VCX S V7.1. V7.1. PGRADING ERVER OFTWARE X TO...
  • Page 9 Upgrading a Single-Site System With Two Servers Upgrading the Primary VCX Server Upgrading the Secondary VCX Server Set Up Database Replication Upgrading a Single-Site System With Four Servers Upgrading the Primary IP Telephony Server Upgrading the Primary IP Messaging Server Upgrading the Secondary IP Telephony Server Upgrading the Secondary IP Messaging Server Set Up Database Replication...
  • Page 10 ROCESSOR OMMAND NTERFACE OMMANDS Call Processor CLI Overview CLI Command Descriptions NDEX...
  • Page 11 BOUT UIDE ® This guide describes how to maintain 3Com VCX IP Telephony Solution software. VCX software runs on either the 3Com V6000 or 3Com V7000 server platforms. ™ This guide describes how to maintain VCX IP Telephony Solution components, which include the VCX software services running in standard VCX software configurations.

  • Page 12: Conventions

    BOUT UIDE Conventions Table 1 and Table 2 list conventions that are used throughout this guide. Table 1 Notice Icons Icon Notice Type Description Information note Information that describes important features or instructions Caution Information that alerts you to potential loss of data or potential damage to an application, system, or device Warning Information that alerts you to potential personal injury...

  • Page 13: Related Documentation

    Related These 3Com documents contain additional information about the Documentation products in this release that are a part of or support the 3Com Convergence Applications Suite. The following documents are a part of the VCX IP Telephony Solution: VCX Installation Guide ■...

  • Page 14: Comments

    Document part number (found on the front page) ■ Page number ■ Your name and organization (optional) ■ Example: VCX Maintenance Guide Part Number 900-0382-01 Rev AA Page 25 Please address all questions regarding the 3Com software to your authorized 3Com representative.
  • Page 15 YSTEM AINTENANCE VERVIEW The 3Com® VCX IP Telephony Solution delivers reliable, highly-scalable, comprehensive standards-based IP telephony for large enterprises. This chapter provides an overview of the VCX™ system and the steps required to maintain the servers and services in a VCX environment.

  • Page 16: Network-Based Telephony

    1: VCX S HAPTER YSTEM AINTENANCE VERVIEW Network-based The VCX IP Telephony Solution (referred to in this guide as the VCX Telephony system) merges telephony with networking by delivering business telephone service over a data network. The VCX architecture provides a distributed call processing system using the SIP signalling protocol to establish voice, video, and text sessions between SIP phones and other SIP-compatible devices.
  • Page 17 Accounting Service — Sends, exports, and manages CDRs. ■ SIP Phone Downloader — Loads an application image on to a 3Com ■ phone, which enables SIP support on the phone. Common Agent — Connects other software components and the ■...

  • Page 18: Vcx Hardware Configurations

    1: VCX S HAPTER YSTEM AINTENANCE VERVIEW Table 3 VCX Software Configuration Options Standard Software Configurations IP Telephony Authentication Global Call Software IP Messaging Call Telephony Messaging Directory Records Central Service Server Server Server Server Server Server Server Call Processor SIP Downloader Authentication and Directory...

  • Page 19: Single-Site Configurations

    VCX Hardware Configurations There are two basic configuration options, single-site and multi-site systems. The hardware servers in each option type run the VCX operating system. Currently supported hardware platforms include: V7000-series systems with IBM X306m or IBM X346 servers ■ V6000 Integrated Branch Communications servers ■...
  • Page 20 (local) IP Messaging service. The IP Telephony configuration requires that each branch office obtain IP Messaging services from the regional office (referred to as global messaging). The 3Com V6000-series Integrated Branch server runs the IP ■ Telephony and IP Messaging configuration which enables local IP Messaging service.

  • Page 21: Vcx Maintenance Tasks

    VCX Maintenance Tasks The version 7.1 upgrade procedure allows you to enable Global Voicemail Integration on servers running IP Messaging software. However, you must install IP Messaging software on a GVCS, and then set up the GVCS through the IP Messaging administrator configuration interface before enabling Global Voicemail Integration on regional and branch office IP Messaging servers.
  • Page 22 1: VCX S HAPTER YSTEM AINTENANCE VERVIEW Table 4 VCX Maintenance Tasks Task Purpose Reference Configure accounting groups on Identifies the Accounting services from Chapter 2 the Call Records service. which the Call Records service should collect Call Detail Records (CDRs). Maintain VCX system servers.

  • Page 23: About Vcx Passwords

    Default Password root pvadmin oracle oracle tomcat tomcat cworks cworks nice During the VCX installation procedure, the installer has the option to change the default password for each account. 3Com Corporation strongly recommends, for security reasons, that installers change the...

  • Page 24: Vcx File And Directory Name Guidelines

    1: VCX S HAPTER YSTEM AINTENANCE VERVIEW default passwords. Consult with your VCX installer for the current passwords. Note that these passwords can be changed after the initial installation by running the script. See Chapter vcx-reconfigure CAUTION: Do not use operating system commands or utilities to change these passwords.
  • Page 25 VCX File and Directory Name Guidelines Table 6 Characters to Avoid in File and Directory Names (continued) Character Description Dollar sign Exclamation mark < and > Left and right carets & Ampersand Semicolon ( and ) Left and right parentheses Pound or hash character At sign €...
  • Page 26 1: VCX S HAPTER YSTEM AINTENANCE VERVIEW...
  • Page 27 ONFIGURING THE ECORDS ERVICE This chapter describes how to configure accounting groups on the Call Records service. An accounting group identifies the Accounting services from which the Call Records service should collect Call Detail Records (CDRs). This includes the following topics: Call Records Service Overview ■...

  • Page 28: Call Records Service Overview

    2: C HAPTER ONFIGURING THE ECORDS ERVICE Call Records Service A Call Detail Record (CDR) contains information about a processed call. Overview This information can include the identity of the calling and called parties, the duration of the call, and the type of call. CDRs can be imported by third-party billing platforms to generate billing statements.
  • Page 29 Call Records service from needlessly checking for a new XML file. To adjust the Call Records service timer: 1 Access the server hosting the Call Records service using the root account. 2 Enter the following command: cd /opt/3com/VCX/bssxml/conf 3 Open the file and find the following entry: bssxmlconfig.xml...

  • Page 30: Accounting Service Groups

    2: C HAPTER ONFIGURING THE ECORDS ERVICE 4 Change the default value, 600 seconds (10 minutes), to suit your system requirements. 5 Save and close the file. Accounting Service The Call Records service organizes Accounting services into groups. Each Groups group can contain one or more Accounting services, but an Accounting service can belong to only one group.

  • Page 31: Adding An Accounting Group

    To add an accounting group: Accounting Group 1 Log on to the VCX server hosting the Call Records service as cworks and enter these commands: cd /opt/3com/VCX/bssxml/bin ./config.sh A menu of configuration options appears followed by the SELECT OPERATION prompt.

  • Page 32: Enabling And Disabling Groups

    To enable or disable an accounting group: 1 Log on to the VCX server hosting the Call Records service as cworks and enter these commands. cd /opt/3com/VCX/bssxml/bin ./config.sh A menu of configuration options appears followed by the SELECT OPERATION prompt.

  • Page 33: Adding Accounting Services To The Call Records Service

    To add Accounting services to the Call Records service: 1 Log on to the VCX server hosting the Call Records service as cworks and enter these commands; cd /opt/3com/VCX/bssxml/bin ./config.sh A menu of configuration options appears followed by the SELECT OPERATION prompt.
  • Page 34 ■ IP address assigned to eth0. The Do you want to use Default Accounting Server Source Configuration prompt appears. 3Com recommends using the default source configuration, which identifies where the CDRs are stored on the Accounting service. If you enter a At the Enter Source Path prompt, enter the path where you want the CDRs to be stored.

  • Page 35: Editing Accounting Service Information In A Group

    Group To edit Accounting service information: 1 Log on to the VCX server hosting the Call Records service as cworks and enter these commands: cd /opt/3com/VCX/bssxml/bin ./config.sh A menu of configuration options appears followed by the SELECT OPERATION prompt.

  • Page 36: Deleting An Accounting Service From A Group

    7 Enter the IP Address of the server you need to edit. The Update Source Path prompt appears. The default is /opt/3com/VCX/acctxml/db/export. This is the location where the CDRs are is stored on the Accounting service. The new configuration is applied and you are returned to the main menu.

  • Page 37: Listing All Configured Accounting Services

    Call Records service. To view all configured Accounting services: 1 Log on to the VCX server hosting the Call Records service as cworks and enter these commands: cd /opt/3com/VCX/bssxml/bin ./config.sh A menu of configuration options appears followed by the SELECT OPERATION prompt.

  • Page 38: Managing Cdrs And Super Cdrs

    2: C HAPTER ONFIGURING THE ECORDS ERVICE 3 The screen displays the number of configured Accounting services. Press Enter to view the Accounting services (clustered in their group) until you reach the Enter Source Name to View Details prompt. 4 Enter the name of the appropriate Accounting service. The Accounting service details are displayed and you are returned to the main menu.
  • Page 39 Managing CDRs and Super CDRs Table 7 CDR Field Descriptions and Values (continued) Variable Description and Values Example SESSIONSEQUENCEEND Indicates when a session sequence ends. For internal use only. ACCTAUTHENTICATIONFAILURECNT Account Auth Failure Count CALLINGPARTYE164ADDRESS An E.164 number from which the 304001 call is placed to the access gateway.
  • Page 40 2: C HAPTER ONFIGURING THE ECORDS ERVICE Table 7 CDR Field Descriptions and Values (continued) Variable Description and Values Example CALLTERMINATIONCAUSE Reason for call disconnect or not completed. Note that a value of zero indicates that the call has not been disconnected, or that no disconnect reason was given.
  • Page 41 Managing CDRs and Super CDRs Table 7 CDR Field Descriptions and Values (continued) Variable Description and Values Example CALLEEFORWARDNUMBER Call Forwarded Number by Called sip:5555000@10.10.10.10 Party. INBOUNDENDPOINTTYPE Indicates the type of inbound end point. 2 – Gateway 6 – Terminal 9 –...

  • Page 42: Viewing Cdrs

    To view a CDR stored on a server hosting the Accounting service: 1 Log on to server hosting the Accounting service as cworks. 2 The CDRs are stored in the /opt/3com/VCX/acctxml/db/export directory. The newest CDR is listed last and looks similar to the following: cdr200609111533531_c.xml...

  • Page 43: Qos Monitoring Statistics

    /opt/3com/VCX/acctxml/qos directory. You can use a third-party application to download the QDRs and create reports. QoS monitoring, as implemented on a VCX system, covers 3Com IP telephones (models 310x) as endpoints. The EMS administrator can: Configure one or more monitored endpoints or subnets.
  • Page 44 2: C HAPTER ONFIGURING THE ECORDS ERVICE Jitter ■ Packet Loss ■ Round Trip Delay ■ Call Start Time ■ Call End Time ■ Caller Extension and IP address ■ Called Party extension and IP address ■ In addition to call statistics, the following aggregate average statistics are available at the endpoint or subnet level, depending on how the statistics collection is configured.
  • Page 45 VCX S ANAGING ERVERS This chapter describes various maintenance tasks you may need to perform on the VCX services running on servers in your VCX system. Most maintenance tasks require logging in to a VCX server using one of the VCX system accounts. Each account has an associated password. See About VCX Passwords for more information.

  • Page 46: Managing The Tomcat Web Server

    -aux | grep tomcat If Tomcat is running, the operating system returns output similar to the following: tomcat 11619 3.7 496564 95892 ? Jun05 5:37 /opt/3com/VCX/j2sdk/bin/java -Xms32m -Xmx256m -Djava.util.logging.manager= org.apache.juli.ClassLoaderLogManager -Djava.endorsed.dirs= /opt/3com/VCX/tomcat/common/endorsed -classpath :/opt/3com/VCX/tomcat/bin/bootstrap.jar:/opt/3com/VCX/tomcat /bin/commons-log root 17471 3888 600 pts/0 S 06:57 0:00 grep tomcat...

  • Page 47: Clearing The Tomcat Cache

    Changing a Daylight Saving and Time Zone Configuration cd /opt/3com/VCX/scripts/rc3.d ./S70tomcat start exit Clearing the Tomcat If your browser generates page errors while accessing the VCX Central Cache Manager or any of the web-based management interfaces (VCX Administrator, VCX User, or IP Messaging) such as “page not found”, “page doesn't render”, “page doesn't render correctly”, or “exception...

  • Page 48: Managing Log And Cdr Files

    You should monitor the following applications and services: Tomcat and IP Messaging log files ■ Accounting service for CDR and QDR collection ■ Tomcat and IP Files in the tomcat directory (/opt/3com/VCX/tomcat/logs/) you should Messaging Log File monitor include: Maintenance catalina.out files, for example, catalina.2006-07-10.log ■...

  • Page 49: Cdr File Maintenance

    To modify the Accounting service configuration file: 1 Log in to the server running the Accounting service using the root account. 2 Enter the following command: cd /opt/3com/VCX/acctxml/conf/ 3 Use an editor to open the following file: acctxmlconfig.xml 4 In the section, locate the <CONFIGURATION_INFO>...

  • Page 50: Qdr File Maintenance

    To modify the Accounting service configuration file: 1 Log in to the server running the Accounting service using the root account. 2 Enter the following command: cd /opt/3com/VCX/acctxml/conf/ 3 Use an editor to open the following file: acctxmlconfig.xml 4 In the section, locate the <CONFIGURATION_INFO>...

  • Page 51: Verifying Service Operation

    Verifying Service Operation If you enable generation of QoS statistics and QDRs, change this setting to enable self-cleaning on AUTO_CLEAN_IF_NO_LATEST_UPDATE="Y" the Accounting service. The variable is set to 96 AUTO_CLEAN_IF_NO_LATEST_UPDATE_INTERVAL hours (four days) by default. A smaller value initiates the self-cleaning more often.

  • Page 52: Starting The Common Agent

    Using EMS Use EMS to stop the Common Agent immediately or gracefully. To stop the Common Agent immediately: 1 From the Explorer tab, right-click 3Com SNMP Agent. 2 From the pop-up menu, select Maintenance, then select Hard Shutdown. To stop the Common Agent gracefully: 1 From the Explorer tab, right-click 3Com SNMP Agent.

  • Page 53: Restarting The Common Agent

    Using EMS You can use EMS to restart the Common Agent immediately or gracefully. To restart the Common Agent immediately: 1 From the Explorer tab, right-click 3Com SNMP Agent. 2 From the pop-up menu, select Maintenance, then select Hard Shutdown.

  • Page 54: Managing The Call Processor Service

    The Call Processor service is not running if only the root ID is listed. ■ Starting the Call To start the Call Processor service: Processor 1 Log in into the server hosting the Call Processor service using the root account. 2 Enter the following commands: cd /opt/3com/VCX/scripts/rc3.d ./S80callp start...

  • Page 55: Stopping The Call Processor

    ./S80callp stop Using EMS To stop the Call Processor service from EMS: 1 From the Explorer tab, right-click the 3Com Call Processor service. 2 From the pop-up menu, select Maintenance, then select Hard Shutdown. A dialog box appears and displays the progress of the command. When the command has been completed, the Working icon changes to a Finished icon.

  • Page 56: Managing The Accounting Service And The Authentication And Directory Service

    Using EMS To restart the Call Processor service from EMS: 1 From the Explorer tab, right-click the 3Com Call Processor service. 2 From the pop-up menu, select Maintenance, then select Hard Restart to shutdown and restart the Call Processor service.

  • Page 57: Viewing Service Status

    Directory service: 1 Log in to the server hosting the service whose status you want to view using the root account. 2 Enter the following commands: cd /opt/3com/VCX/scripts/rc3.d ./<back-end server> status , enter one of the following identifiers: <back-end server>...

  • Page 58: Restarting A Service

    1 Log in to the server hosting the service you want to restart using the root account. 2 Enter the following commands: cd /opt/3com/VCX/scripts/rc3.d ./<back-end server> restart , enter one of the following identifiers: <back-end server> For an Accounting service enter ■...

  • Page 59: Enabling Server Logging

    1 Log in to the server hosting the service using the root account. 2 Stop the service (see Stopping a Service). 3 Enter the following command to change directories: cd /opt/3com/VCX/<schema>/conf , enter for the Accounting service or enter <schema> acctxml vcxdata for the Authentication and Directory service.
  • Page 60 (Authentication and Directory service) files are set up for the back-end server: 1 Log in to the server hosting the service using the root account. 2 Enter the following command: cd /opt/3com/VCX/<schema>/conf , enter for the Accounting service or enter <schema>...

  • Page 61: Managing The Sip Phone Downloader

    7 Start the service (see Starting a Service). Managing the SIP The SIP Phone Downloader loads an application image on to a 3Com Phone Downloader phone, which enables SIP support on the phone. Starting the SIP To start the SIP Phone Downloader:...

  • Page 62: Managing The Ip Messaging Service

    Messaging Service Status 1 Log in to the server hosting the IP Messaging service using the app account. 2 Enter the following commands: cd /opt/3com/VCX/scripts/rc3.d ./S60ums status Starting the IP To start the IP Messaging service: Messaging Service 1 Log in to the server hosting the IP Messaging service using the app account.

  • Page 63: Managing Authorized Snmp Station Access

    Managing Authorized SNMP Station Access Managing You can use an SNMP management station, such as 3Com Corporation’s Authorized SNMP Enterprise Management Suite, to manage a VCX server. You must, Station Access however, grant the management station explicit access to the VCX server to enable the exchange of SNMP management and monitoring messages.

  • Page 64: Changing Codecs

    3: M VCX S HAPTER ANAGING ERVERS delete :- Remove an authorized station entry quit:- exit this utility help:- show commands that are supported ***************************************************** supported commands are "show", "add", "delete", "quit", "help":: To add an SNMP management station, enter .

  • Page 65: How To Change Your Codec

    Changing Codecs If you want to enable a set of language prompts that are compatible with the currently operating codec, simply run the add_language utility as described in “Adding a Set of Language Prompts” in the IP Messaging Module Operations and System Administration Guide. IP Messaging supports only one codec at a time.

  • Page 66: Converting Prompts And Messages To A Different Codec

    7 Enter the following command to run the change_codec utility: ./change_codec g729a 8 Stop and restart IP Messaging by entering the following commands: cd /opt/3com/VCX/UMS/vcx-scripts/init.d ./S60ums stop ./S60ums start 9 Log in to the secondary IP Messaging server and repeat steps 2 through Note that steps 5 and 6 may be optional.
  • Page 67 Changing Codecs (US English). The steps in the example install the G.729a codec and convert any existing custom prompts and voice mail messages to the G.729a codec format. IP Messaging must not be actively processing calls while the codec_data_convert utility is running. 1 Log in to the primary IP Messaging server using the root account.
  • Page 68 3: M VCX S HAPTER ANAGING ERVERS...
  • Page 69 ACKING P AND ESTORING A VCX C ONFIGURATION This chapter describes how to back up and restore a VCX system configuration using the vcx-config-backup vcx-config-restore commands. This chapter includes the following topics: VCX Configuration Backup and Restore Overview ■ Backing Up a VCX Configuration ■...

  • Page 70: Vcx Configuration Backup And Restore Overview

    VCX system, you must perform a configuration backup operation on each machine in your VCX system. 3Com Corporation recommends that you back up configuration files on your VCX system once a week. However, you should back up a configuration whenever you make changes. A restored system will not include configuration changes made after the last backup was performed.

  • Page 71: Backup And Restore Considerations

    VCX Configuration Backup and Restore Overview Note that the command includes a parameter, vcx-config-restore , that excludes the operating system information from a exclude-os restore operation. If you select this option, the restore operation generates a warning if the system's current IP configuration does not match the configuration contained in the backup file.

  • Page 72: Backing Up A Vcx Configuration

    4: B VCX C HAPTER ACKING P AND ESTORING A ONFIGURATION apply the old configuration by restoring the backup file to the upgraded system. You can backup and restore the currently active version of VCX ■ software and the currently active version of the VCX operating system only.

  • Page 73: About The Backup File

    --test ■ create the backup file. The backup file is created in the /opt/3com/VCX/backup directory. The directory will be created if it does not already exist. Note that a VCX component may designate some configuration files and directories as optional. Optional files and directories are backed up if present but no error results if they are absent.
  • Page 74 To view the contents of a VCX configuration backup file: 1 Log in, using the root account, to the machine hosting the VCX configuration backup file you want to back view. 2 Enter the following commands: cd /opt/3com/VCX/backup vcx-backup-query [optional-arguments] <backup-filename>...

  • Page 75: Restoring A Vcx Configuration

    The new backup is created in the /opt/3com/VCX/backup/prerestore directory: You can prevent the restore operation from creating the new backup by...
  • Page 76 If you do not specify a path for the , the command <backup-filename> looks for the backup file in the current location and then in the /opt/3com/VCX/backup directory. The optional arguments include: — Displays information on command usage. --help ■...

  • Page 77: Backup And Restore Operation Logs

    Backup and Restore Operation Logs Note that, for security reasons the VCX firewall is not stopped. Furthermore, the Common Agent stops only briefly while its own restore is done. For EMS-based operations, this minimizes the time during which remote manageability is unavailable. Backup and Restore Each execution of the vcx-config-backup...
  • Page 78 4: B VCX C HAPTER ACKING P AND ESTORING A ONFIGURATION...

  • Page 79: D Atabases

    ANAGING UTHENTICATION IRECTORY ERVICE ATABASES This chapter describes how to manage the database associated with each Authentication and Directory service. This chapter includes the following topics: Backing Up and Restoring the Authentication and Directory Server ■ Database Exporting Table Data ■...

  • Page 80: Backing Up And Restoring The Authentication And Directory Server Database

    (refer to the VCX Administration Guide). Database 3Com recommends regular database backups. You should also back up this database before performing any upgrades. If the upgrade fails and you must downgrade, use the restore utility to repopulate the database.

  • Page 81: Restoring The Vcx Authentication And Directory Server Database

    6 Enter the site ID of the Master Definition site. A backup file named vcxdata<site ID>backup.<version number>.tgz is generated and saved in the /opt/3com/VCX/vcxdata/db/export/ directory. Unless you plan to use this backup file immediately to restore the database on another server, you should copy the file to an archive server.
  • Page 82 /opt/3com/VCX/vcxdata/db/export 3 Enter the following secure copy command, using the password cworks, to copy the vcxdata<site ID>backup.<version number>.tgz file generated by the backup utility to the /opt/3com/VCX/vcxdata/db/import directory. scp vcxdata<site ID>backup.*.tgz cworks@<IP address of primary Authentication and Directory server>:/opt/3com/VCX/vcxdata/db/import If you are prompted to verify the authenticity of the host, enter y.
  • Page 83 Telephony server, the IP Telephony and IP Messaging server, or the Call server. 2 Enter the following commands, on each server, to change the directory and stop Tomcat: cd /opt/3com/VCX/scripts/rc3.d ./S70tomcat stop 3 Log in to both the primary and secondary Authentication and Directory servers.as user cworks.
  • Page 84 8 Enter the site ID of the Master Definition site. The vcxdata<site ID>backup.<version number>.tgz back up file located at /opt/3com/VCX/auth/db/import/ is restored to the VCX Authentication and Directory server database. 9 Enter the following command on the primary VCX Authentication and Directory server to start replication: ./setupReplication...

  • Page 85: Exporting Table Data

    Exporting Table Data cd /opt/3com/VCX/scripts/rc3.d ./S20vcxdata start Exporting Table Use the CWDATA package to export tables into flat files. Export data as Data follows: For one table in a schema (except the runtime tables). See Exporting ■ Table Data for a Single Table.

  • Page 86: Importing Saved Table Data

    The following methods may overwrite existing files in the /opt/3com/VCX/<schema>/db/<schema>/bulkload directory. To prevent files from being overwritten, rename or move the current .txt files. If the data in the database and the data being importing have duplicated data, the duplicate data needs to be cleared before loading custom data.

  • Page 87: Clearing The Configurable Tables

    Once data is deleted it must be reloaded from the text files. To clear the configurable tables from the back-end server database: 1 Log on to the directory server as cworks. 2 Change to the /opt/3com/VCX/<schema>/bin directory: cd /opt/3com/VCX/<schema>/bin 3 Clear the data by entering the following command: ./besbulkload.pl -s <TNSname>...
  • Page 88 5: M HAPTER ANAGING UTHENTICATION AND IRECTORY ERVICE ATABASES...
  • Page 89 ANUALLY ONFIGURING ULTI ASTER EPLICATION This chapter describes Multi-Master Replication (MMR) and how to manually configure it in your VCX system. This chapter includes the following topics: Multi-Master Replication Overview ■ Replicated Table Location ■ Manually Configuring Replication for an IP Telephony Server or IP ■...

  • Page 90: Multi-Master Replication Overview

    Oracle replication is a fully integrated feature of the Oracle server; it is not a separate server. 3Com recommends and only supports MMR, which is comprised of multiple master sites equally participating in an update-anywhere model. Updates made to an individual master site are sent to all other participating master sites.

  • Page 91: Manually Configuring Replication For An Ip Telephony Server Or Ip Telephony And Messaging Server

    -p oracle allow <IP address of eth1 for the other server> c Stop the VCX Authentication and Directory server. cd /opt/3com/VCX/scripts/rc3.d ./S20vcxdata stop d Stop the Tomcat application. ./S70tomcat stop Remember to perform these steps on each server (primary and secondary).
  • Page 92 After 20 minutes, check the status of the replication. 9 To check replication, enter these commands while logged in as cworks: cd /opt/3com/VCX/vcxdata/bin ./checkReplication When the NORMAL Status returned, you know the replication is configured.

  • Page 93: Manually Configuring Region To Region Replication

    (R2DB’) on the VCX Authentication and Directory server for Region 1. a Log on as cworks on the primary Region 1 VCX Authentication and Directory server and enter these commands: cd /opt/3com/VCX/vcxdata/bin ./installVcxdata b Select option 2 to BACKUP ROCSA.
  • Page 94 On the Region 1 Call server, log in as root and enter these commands: cd /opt/3com/VCX/scripts/rc3.d ./S70tomcat stop b On the Region 2 Call server, log in as root and enter these commands: cd /opt/3com/VCX/scripts/rc3.d...
  • Page 95 Manually Configuring Region to Region Replication g Log in as cworks, and enter these commands: cd /opt/3com/VCX/vcxdata/bin ./restoreVcxdata h Enter the Site ID for Region 1. Enter these commands: ./backupVcxdata cd /opt/3com/VCX/vcxdata/db/export There should be a single file with this format: vcxdata<region 2 site ID>backup<vcx data version>.tgz...

  • Page 96: Verifying Replication At A Branch Office

    On each VCX Authentication and Directory server run checkReplication to verify replication is normal. Log in as cworks and enter these commands: cd /opt/3com/VCX/vcxdata/bin ./checkReplication m Restart Tomcat on each region’s Call serve. Log in as root and enter these commands: cd /opt/3com/VCX/scripts/rc3.d...

  • Page 97: Verifying The Number Of Vcx Data Schemas In A Region

    Verifying the Number of VCX Data Schemas in a Region The Enter the Number of MASTER SITEs other than the MASTER DEFINITION SITE [1]: prompt appears. To determine the number of Master Sites associated with this branch, use the listVcxdata command. See Manually Configuring Replication for an IP Telephony Server or IP Telephony and Messaging Server page 91...
  • Page 98 To list all of the VCX data schemas associated with the server you are logged on to: 1 Login on the office you want to verify the number of associated offices for as cworks and enter these commands: cd /opt/3com/VCX/vcxdata/bin ./listVcxdata The script lists all of the VCX data schemas found. 61REG1CHICAGO...

  • Page 99: Deleting Replication Errors

    Replication errors occasionally need to be deleted (for instance, before you perform an upgrade). To delete replication errors, log onto the server hosting the VCX Authentication and Directory server as cworks and enter these commands: cd /opt/3com/VCX/vcxdata/bin ./deleteReplicationErrors...
  • Page 100 6: M HAPTER ANUALLY ONFIGURING ULTI ASTER EPLICATION...
  • Page 101 VCX S ECONFIGURING A ERVER This chapter describes how to reconfigure a VCX server using the command. This chapter includes the following topics: vcx-reconfigure Reconfiguration Overview ■ Sample VCX Server Reconfiguration ■...

  • Page 102: Reconfiguration Overview

    7: R VCX S HAPTER ECONFIGURING A ERVER Reconfiguration Reconfiguring a VCX server enables you to modify its networking Overview parameters and the configuration of the services that run on the server. You may decide to reconfigure a VCX server if, for example, you are moving it to a new subnetwork or if you are expanding your VCX system to include additional servers and need all servers to work together in the new configuration.

  • Page 103: Sample Vcx Server Reconfiguration

    Sample VCX Server Reconfiguration Sample VCX Server The sample reconfiguration script in this section is based on a two-server Reconfiguration configuration. The changes made are described in Table 9. Any configuration parameters not listed in Table 9 remain unchanged. Table 9 Changes in Server Configuration Parameter Original Value New Value...
  • Page 104 7: R VCX S HAPTER ECONFIGURING A ERVER Sample VCX Reconfiguration Script --------------------------------------------------------------------------- --------------- Welcome to the VCX Reconfiguration Utility ---------------- --------------------------------------------------------------------------- This utility allows a previously configured VCX system to be reconfigured - for example, to change its IP address or the IP addresses of other VCX servers with which it communicates.
  • Page 105 Enter y to accept the information that you have entered, or enter n to change one or more of the items. If you enter n, the script prompts you with the current value for each item and allows you to change it. 3Com VCX Multi-Master Replication DROP ... continue with User Inputs...
  • Page 106 Sample VCX Reconfiguration Script (continued) VCXDATATESTONEX Database Multi-Master Replication DROP Process starting ... For Log Details Refer to ../log/replication_VCXDATATESTONEX_DROP200503300731.log Dec 14, 2005 9:05:25 AM com.coms.replication.run.Start dropReplication INFO: ----------------------------------------------- 3Com VCXDATATESTONEX Database ... Multi-Master Replication DROP: ************************************** ************** COMPLETE ************** ************************************** ----------------------------------------------- Dropping replication succeeded.
  • Page 107 Sample VCX Server Reconfiguration Sample VCX Reconfiguration Script (continued) -------------------------- Configuring Hostname --------------------------- Enter system hostname : test-three In this sample script, the host name is being changed from test-one to test-three. --------------------- Configuring IP Interface 'eth0' --------------------- IP Address : 10.230.64.40 Network Subnet Mask : 255.255.255.0...
  • Page 108 7: R VCX S HAPTER ECONFIGURING A ERVER Sample VCX Reconfiguration Script (continued) -------------------- Configuring Network Time Protocol -------------------- Enter NTP servers one at a time. When done, enter 0.0.0.0 to stop. Primary NTP Server : 10.35.10.51 Secondary NTP Server : 10.36.10.51 In this sample script, NTP server IP addresses remain unchanged.
  • Page 109 Sample VCX Server Reconfiguration Sample VCX Reconfiguration Script (continued) In this sample script, the country code remains unchanged. Please select a time zone from the following list: 1. Alaska Time 2. Alaska Time - Alaska panhandle 3. Alaska Time - Alaska panhandle neck 4.
  • Page 110 HAPTER ECONFIGURING A ERVER Sample VCX Reconfiguration Script (continued) DNS Servers: 10.25.10.31 10.26.10.31 10.27.10.31 Search Domains: ne.3com.com NTP Servers: 10.35.10.51 10.36.10.51 Time Zone: America/New_York --------------------------------------------------------------------------- Is all of the above information correct? [yes] : Press the Enter or Return key to accept the information. To change any of the parameters, enter no.
  • Page 111 : Site Three Enter the new site description for this server. The Customer Name identifies the company using this VCX system. Enter the customer name : 3Com Customer Some VCX applications can use European date ordering. Answer 'Y' here to enable this.
  • Page 112 7: R VCX S HAPTER ECONFIGURING A ERVER Sample VCX Reconfiguration Script (continued) The SIP default dialing domain is used to construct the SIP URI for outbound SIP requests. Enter the SIP default dialing domain : 1.1.1.1 In this sample script, the dialing domain remains unchanged. The secondary Call Processor acts as a backup if the primary is down or unreachable.
  • Page 113 The script displays a summary of the global parameters that you have accepted or changed. ----------------------- Summary of Global Parameters ----------------------- Site Name : Testthree Customer Name : 3Com Customer European Date Order : N Enable Adhoc Conference Service : Y SIP Default Dialing Domain : 1.1.1.1 Secondary Call Processor : 10.230.67.41...
  • Page 114 7: R VCX S HAPTER ECONFIGURING A ERVER Sample VCX Reconfiguration Script (continued) --------------- Configuring additional parameters for System --------------- This section allows you to change the password for each VCX system account. Press Enter to accept the current password. Root account password.
  • Page 115 Sample VCX Server Reconfiguration Sample VCX Reconfiguration Script (continued) ---------- Configuring additional parameters for UPS Monitoring ----------- An Uninterruptible Power Supply (UPS) can be used with VCX systems to avoid disruption due to a power outage. VCX provides a UPS monitoring service which tracks the UPS's status and performs a safe shutdown when the its battery is depleted during a long power outage.
  • Page 116 7: R VCX S HAPTER ECONFIGURING A ERVER Sample VCX Reconfiguration Script (continued) The SNMP 'write' community string configured in the UPS is required. (For security reasons, it is recommended that the default value provided by the UPS be changed.) UPS 'write' community string : private The string you enter here must match the SNMP write community string...
  • Page 117 Sample VCX Server Reconfiguration Sample VCX Reconfiguration Script (continued) -------- Configuring additional parameters for IP Messaging Service -------- The hostname of the other IP Messaging system is needed in order to set up Intelligent Mirroring redundancy with this system. Hostname of peer IP Messaging system : test-four Enter the host name of the Secondary VCX Server, as it will be defined after the reconfiguration.
  • Page 118 7: R VCX S HAPTER ECONFIGURING A ERVER Sample VCX Reconfiguration Script (continued) IP Messaging includes an optional ability to back up messages to an external server. Enable data backup server for IPMS? [N] Press the Enter or Return key to accept the default answer. In this sample script, the default answer (N) indicates that data backup was not originally enabled on this server.
  • Page 119 Sample VCX Server Reconfiguration Sample VCX Reconfiguration Script (continued) Do you wish to change any of the IP Messaging System parameters? [N] : Press the Enter or Return key to accept the data that you have accepted or changed. To review the data and make additional changes, enter Y. --------- Configuring additional parameters for Auth &...
  • Page 120 7: R VCX S HAPTER ECONFIGURING A ERVER Sample VCX Reconfiguration Script (continued) In some cases it may be desirable for SNMP Traps to be sent to multiple destinations. Additional Trap Destinations can be entered here. Enter a blank input to indicate that all destinations have been entered. IP Address of the first additional trap destination for this system.
  • Page 121 Y to this question, the script enters a mode in which you can review and modify low-level configuration parameters for each service. This is not needed for standard configurations and using it successfully requires substantial VCX configuration expertise. 3Com does not support this mode of making configuration changes. ----------------------------------------------------------------------------...
  • Page 122 7: R VCX S HAPTER ECONFIGURING A ERVER Sample VCX Reconfiguration Script (continued) ---------------------------- Applying Changes ----------------------------- The script displays several status messages. The last message reminds you to reboot all servers after they have all been reconfigured and to reboot them all at the same time.
  • Page 123 ANAGING NINTERRUPTIBLE OWER UPPLIES This chapter describes how to manage one or more Uninterruptible Power Supplies (UPS) in your VCX system. It describes how to add UPS support to an existing VCX system, and how to monitor UPS status. This chapter includes the following topics: UPS Overview ■...

  • Page 124: Ups Overview

    8: M HAPTER ANAGING NINTERRUPTIBLE OWER UPPLIES UPS Overview Critical network equipment is often connected to an Uninterruptible Power Supply (UPS) to ensure continued operation in the event of mains power loss. A server in a VCX system can be connected to, and can monitor, one or two (if the server has dual power supplies) UPS devices.

  • Page 125: Ups Configuration Options

    Adding UPS Support to an Existing VCX System UPS Configuration For the current VCX software release, 3Com Corporation supports UPS Options hardware from American Power Conversion (APC) Corporation. For a list of supported APC UPS devices and VCX hardware platforms, consult with your 3Com Service Representative or your 3Com Voice Authorized Reseller.
  • Page 126 As a general rule, the power requirements of devices serviced by a UPS should not exceed 80% of UPS load capacity. 3Com Corporation recommends that you consult with you UPS vendor or reseller for sizing assistance.

  • Page 127: Requirements

    Adding UPS Support to an Existing VCX System Requirements Setting up a VCX system to use UPS power and to monitor UPS status using the command requires the following configuration vcx-ups-setup information for each UPS in the VCX system: IP address of the UPS — You must know the pre-configured IP address ■...
  • Page 128 Enter the SNMP community string configured on the UPS to enable communication between the master VCX server and the UPS. Typically, the community string is private to allow Read or Write access (however, 3Com Corporation strongly recommends that you change the default community string). -- bcharge <UPS battery threshold charge>...
  • Page 129 Adding UPS Support to an Existing VCX System Note that you must include all the command parameters vcx-ups-setup even if you are only changing a single value. Single UPS System – Configuring a Slave VCX Server To enable and configure a VCX server as a slave in a single UPS system: 1 Log in, using the root account, to the VCX server you want to designate as a slave.

  • Page 130: Adding Multiple Ups Support

    8: M HAPTER ANAGING NINTERRUPTIBLE OWER UPPLIES After the initial slave VCX server configuration, you can change a parameter value by reentering the command. In the vcx-ups-setup following example, the IP address of the master VCX server is changed: vcx-ups-setup --master N --monitormultipleups N --upsserver 10.230.63.7 Note that you must include all the command parameters...
  • Page 131 Adding UPS Support to an Existing VCX System devices are used to provide power. For servers with redundant power supplies, ensure that each power supply is connected to a different UPS (and if possible, you should connect each UPS to different mains circuits).
  • Page 132 8: M HAPTER ANAGING NINTERRUPTIBLE OWER UPPLIES Figure 4 Two UPS Devices Powering Redundant VCX Servers Primary IPM Server VCX Server VCX Server Secondary IPM Server When you have multiple UPS devices, you should connect each UPS to different mains circuits if possible. Dual UPS System –...
  • Page 133 Adding UPS Support to an Existing VCX System Enter Y (you must uppercase) to indicate there are multiple UPS devices servicing the VCX system. -- upsipaddr <IP Address of the UPS> Enter the IP address of the first UPS. Use dotted decimal notation but do not enter leading zeros.
  • Page 134 8: M HAPTER ANAGING NINTERRUPTIBLE OWER UPPLIES The IP address of the second UPS is 10.230.63.4. ■ The community string the second UPS will use to communicate with ■ the master VCX server is private. The low battery threshold charge is 33%. ■...

  • Page 135: Disabling Ups Monitoring On A Vcx Server

    Adding UPS Support to an Existing VCX System The following example shows the syntax required to initially configure a slave VCX server in a system supported by multiple UPS devices: vcx-ups-setup --master N --monitormultipleups Y --upsserver 10.230.63.5 When this command is executed: UPS monitoring is enabled on the current VCX server.

  • Page 136: Monitoring Ups Status

    8: M HAPTER ANAGING NINTERRUPTIBLE OWER UPPLIES The optional argument specifies that the command should --fullauto run in automatic mode. In this mode, command execution does not provide any interactive prompts or queries. Note that you can enter the command with the optional vcx-ups-setup argument to display information on command usage.
  • Page 137 Monitoring UPS Status Table 10 vcx-ups-status Command Parameters (continued) Parameter Description --ismaster Indicates whether or not (Y or N) this VCX server is configured as the master. --listslaves Lists the IP addresses of all VCX servers configured as slaves. --all Displays values for the following parameters: upsstatus ■...

  • Page 138: Vcx Server Response To Power Events

    8: M HAPTER ANAGING NINTERRUPTIBLE OWER UPPLIES VCX Server This section describes how UPS-supported VCX systems respond to Response to Power various power events. Events Power events and VCX server responses are shown in Table Table 11 VCX Server Behavior for Power Events Event Response Power Loss...
  • Page 139 VCX Server Response to Power Events Table 11 VCX Server Behavior for Power Events (continued) Event Response Final Shutdown The UPS receives a signal to turn off after a time delay (the default is 270 seconds) to allow for the last shutdown steps to complete.
  • Page 140 8: M HAPTER ANAGING NINTERRUPTIBLE OWER UPPLIES...
  • Page 141 ONFIGURING THE ROCESSOR The VCX Call Processor provides call routing as well as other call services for the VCX IP Telephony Solution. This chapter includes the following topics: Call Processor Overview ■ Configuration Methods ■ Configuring Trusted Endpoints ■ Configuring Accounting and Directory Services ■...

  • Page 142: Call Processor Overview

    Call Processor configurable parameters. See the 3Com Enterprise Management Suite User Guide for basic EMS information and see the Enterprise Management Suite User Guide for VCX V7000 Components for VCX specific information. Using the vcx-reconfigure command ■...

  • Page 143: Configuring Trusted Endpoints

    -Index -RowStatus -TrustedAddress -Netmask 10.230.64.5 255.255.255.255 10.230.63.7 255.255.255.255 10.230.63.15 255.255.255.255 255.255.255.255 Adding Trusted To add a trusted endpoint to a Call Processor using the CLI: Endpoints 1 Log onto the server hosting the Call Processor. 2 Navigate to the /opt/3com/VCX/callprocessor/remoteCli/bin.
  • Page 144 9: C HAPTER ONFIGURING THE ROCESSOR 3 Start the remoteCLI interface: ./remoteCli -callprocessor 4 Add either a single or range of trusted endpoints: a To add a single trusted endpoint, from the prompt (>) enter: config CcTrusted rowStatus=4 index=<index ID> TrustedAddress=<IP address of endpoint>...

  • Page 145: Editing Trusted Endpoints

    To edit a trusted endpoint of a Call Processor using the CLI: Endpoints 1 Log onto the server hosting the Call Processor. 2 Navigate to the /opt/3com/VCX/callprocessor/remoteCli/bin. 3 Start the remoteCLI interface: ./remoteCli -callprocessor 4 At the remoteCLI prompt (>) enter: config CcTrusted RowStatus=<RowStatus variable>...

  • Page 146: Adding Primary And Secondary Accounting Servers

    You will have to manually reconfigure your system using remoteCli to match your previous configuration. Consult with your 3Com representative before using the remoteCli to configure Accounting services or Authentication and Directory services on your VCX system.

  • Page 147: Adding Primary And Secondary Authentication And Directory Servers

    Secondary remoteCLI interface: Authentication and Directory Servers 1 Log onto the server hosting the primary Call Processor. 2 Navigate to the /opt/3com/VCX/callprocessor/remoteCli/bin. 3 Start the remoteCLI interface: ./remoteCli -callprocessor 4 At the remoteCli prompt (>) enter: config authc use=false config auths pri=1 IpAddress=<IP address of primary Authentication and Directory server>...
  • Page 148 9: C HAPTER ONFIGURING THE ROCESSOR config authc use=false config auths pri=2 IpAddress=<IP address of secondary authentication server> config auths pri=2 LocalIpAddress=<IP address of call processor> config authc use=true 5 The interface lists the IP address of the new Authentication and Directory Server.

  • Page 149: I Nterface

    ANAGING CCOUNTS SING THE OMMAND NTERFACE This chapter describes how to add, modify, and delete user accounts using the command. user-MAC This chapter includes the following topics: Command Overview ■ Using Single User Mode ■ Using Batch Mode ■ Files and Directories ■...

  • Page 150: Command Overview

    10: M HAPTER ANAGING CCOUNTS SING THE OMMAND NTERFACE Command command enables the automated creation of VCX user user-MAC Overview accounts and phone extension assignments. You can run the command in two modes: Single user mode — In this mode, the command adds one user ■...
  • Page 151 Command Overview Table 13 User Account Attributes (continued) Attribute Description Phone Address Mandatory. Specifies the phone extension to be assigned to (extension) the user account. The specified number must be unique on the Call Processor. Site Id Optional. Specifies the site identifier assigned to the location hosting the account.

  • Page 152: Using Single User Mode

    1 Log into the primary VCX server using the cworks account. 2 Enter the following command: cd /opt/3com/VCX/vcxdata/bin You can now enter the command in either single user mode or user-MAC batch mode. See the sections in this chapter for a description of each mode, the required syntax, and examples.
  • Page 153 Using Single User Mode Table 14 user-MAC Command Parameters (continued) Parameter Takes Parameter (full name/abbreviation) Value? Mode Type Description --uname or --u Single String Mandatory. The value specifies the username associated with the account. The specified name must be unique. This value is also required to change account attributes or to delete the account --new-uname...
  • Page 154 10: M HAPTER ANAGING CCOUNTS SING THE OMMAND NTERFACE Table 14 user-MAC Command Parameters (continued) Parameter Takes Parameter (full name/abbreviation) Value? Mode Type Description --pprofile Single String The value specifies the phone profile to be used by the account. All phones must be assigned a phone profile. To create the account with the default phone profile, omit this field.

  • Page 155: Command Modes

    Using Single User Mode parameter sets the password the user enters to ■ --password access the VCX User Provisioning web interface. The user also must have a password to log in to the phone configured with the specified extension ( parameter value).
  • Page 156 10: M HAPTER ANAGING CCOUNTS SING THE OMMAND NTERFACE [--stateprov State Or Province] [--country Country Name] [--zip Zip Code] [--mac-addr xx:xx:xx:xx:xx:xx] [--mac-lock 1|0] [--site-id Site Id] [--remote Host IP Addr][--pprofile Phone Profile Name] Single user Delete mode uses the following command syntax: user-MAC --delete --uname User Name [--site-id Site Id] [--remote Host IP Addr] Single user Modify mode uses the following command syntax:...

  • Page 157: Using Batch Mode

    Using Batch Mode --mac-a 00:e0:bb:24:AE:56 -- mac-l 1 -–pp local --site-id Br3 The following simple command quickly adds a user account: user-MAC --u jjhonson --ph 2314323 The following command deletes the user account for jjohnson: user-MAC --delete --u jjhonson The following command changes the phone extension for the jjohnson user account: user-MAC --mod --u jjhonson --ph 5552121 --new-ph 5552222 Using Batch Mode...

  • Page 158: Managing User Accounts With An Xml File

    Transactions user-MAC Accounts with an in the file can add, modify, or delete user accounts. 3Com Corporation XML File recommends that an XML file contain no more than 5000 transactions. While this is not a hard limit, exceeding 5000 transactions may cause performance issues.
  • Page 159 Using Batch Mode site?, remote?, pprofile? macaddr? newmacaddr? maclock? )> <!ATTLIST transaction type (mod | delete) #IMPLIED > <!ELEMENT uname (#PCDATA) > <!ELEMENT phone (#PCDATA) > <!ELEMENT newPhone (#PCDATA) > <!ELEMENT newUname (#PCDATA) > <!ELEMENT password (#PCDATA) > <!ELEMENT title (#PCDATA) > <!ELEMENT first (#PCDATA) >...
  • Page 160 10: M HAPTER ANAGING CCOUNTS SING THE OMMAND NTERFACE <last>value</last> <email>value</email> <street1>value</street1> <street2>value</street2> <city>value</city> <state>value</state> <country>value</country> <zip>value</zip> <site>value</site> <remote>value</remote> <pprofile>value</pprofile> <macaddr>MACaddr</macaddr> <maclock>0</maclock> </transaction> <transaction type=”mod”> <uname>value</uname> <!--... whatever fields are to be changed ...--> <newUname>value</newUname> <newPhone>value</newPhone> </transaction> <transaction type=”delete”> <uname>value</uname> </transaction>...
  • Page 161 Using Batch Mode site, remote, pprofile )> <!ELEMENT password (#PCDATA) > <!ELEMENT phonepass (#PCDATA) > <!ELEMENT title (#PCDATA) > <!ELEMENT first (#PCDATA) > <!ELEMENT middle (#PCDATA) > <!ELEMENT last (#PCDATA) > <!ELEMENT email (#PCDATA) > <!ELEMENT street1 (#PCDATA) > <!ELEMENT street2 (#PCDATA) > <!ELEMENT city (#PCDATA) >...
  • Page 162 Transactions in the file can add user accounts, but not modify File or delete accounts. 3Com Corporation recommends that a CSV file contain no more than 5000 transactions. While this is not a hard limit, exceeding 5000 transactions may cause performance issues.

  • Page 163: Files And Directories

    Table 15 File Locations Directory File Description /opt/3com/VCX/vcxdata/bin/ user-MAC Runs the command line user account management script. /opt/3com/VCX/vcxdata/conf/ user-MAC-transactions.dtd This DTD file specifies the structure of XML input files required by the user-MAC command.
  • Page 164 File Description user_MAC_defaults.xsl This XSL file translates XML to HTML to improve readability of the default XML. /opt/3com/components/vcxdata.<version>/bin/log Contains various log files. The log files generated by execution of the user-MAC command include user-MAC and a timestamp in the filename, for example: user-MAC_Thu_May_4_ 08:45:20_2006.log...
  • Page 165 VCX S PGRADING ERVER V7.0 V7.1 OFTWARE This appendix describes the procedures required to upgrade a system running VCX server software version 7.0 to VCX server software version 7.1. This appendix includes the following topics: Verifying Software Versions ■ Overview of a 7.0 to 7.1 Upgrade ■...

  • Page 166: Verifying Software Versions

    VCX version. The running VCX version is preceded by a symbolic link icon ( -> lrwxrwxrwx 1 root root 21 Apr 26 09:13 VCX -> /opt/3com/VCX.7.0.7c drwxr-xr-x 10 root root 4096 Mar 10 07:13 VCX.7.0.6c In this example, the link points to version 7.0.7c. The other listed release, 7.0.6c, is installed, but not running.

  • Page 167: Overview Of A 7.0 To 7.1 Upgrade

    3Com Corporation’s Enterprise Management Suite (EMS). EMS is an SNMP-based client/server application. Refer to the Enterprise Management Suite User Guide for VCX V7000 Components for information. This section assumes the VCX system is successfully operating at version 7.0.7c before you perform the upgrade.

  • Page 168: Preliminary Steps

    To check replication status, execute the following steps on the server hosting the Authentication and Directory services database: Log in using the cworks account. Enter: cd /opt/3com/VCX/vcxdata/bin Enter: ./checkReplication The returned status should be NORMAL. If replication errors need to...

  • Page 169: Configuration Upgrade Options

    Overview of a 7.0 to 7.1 Upgrade The VCX v7.1 upgrade procedure creates one or more phone profiles based on data configured for phones in the VCX v7.0 system, and assigns each phone to the appropriate phone profile. However, the VCX administrator should be aware of upgrade implications on the following phone configuration settings: Registration Interval —...

  • Page 170: Configuring New Features

    A: U VCX S V7.0 V7.1 PPENDIX PGRADING ERVER OFTWARE Multi-site systems that include servers at regional offices and ■ servers at branch offices that use global or local IP Messaging A pair of Global Voicemail Central Servers (GVCS) to enable Global ■...

  • Page 171: Upgrading A Single-Site System With Two Servers

    1 Log in as root on the primary VCX server and on the secondary VCX server. 2 Stop the Tomcat process, first on the primary VCX server and then on the secondary VCX server by entering these commands: cd /opt/3com/VCX/scripts/rc3.d ./S70tomcat stop 3 Ensure that database replication has no errors (see Preliminary...
  • Page 172 5 Stop IP Messaging, first on the primary VCX server and then on the secondary VCX server by entering these commands: cd /opt/3com/VCX/scripts/rc3.d ./S60ums stop 6 Obtain a copy of the software upgrade file and vcx-all-7.1.xc.tar...

  • Page 173: Upgrading The Primary Vcx Server

    Upgrading a Single-Site System With Two Servers Upgrade the secondary VCX server. See Upgrading the Secondary VCX ■ Server. Set up database replication on the primary VCX server. See Set Up ■ Database Replication. Upgrading the Follow the steps in this section to upgrade the primary VCX server. Primary VCX Server 1 To start the upgrade process, enter these commands on the primary VCX server:...
  • Page 174 A: U VCX S V7.0 V7.1 PPENDIX PGRADING ERVER OFTWARE An Uninterruptible Power Supply (UPS) can be used with VCX systems to avoid disruption due to a power outage. provides a UPS monitoring service which tracks the UPS's status and performs a safe shutdown when the its battery is depleted during a long power outage.

  • Page 175: Upgrading The Secondary Vcx Server

    After the system has completed the restart process, verify that the upgrade has occurred by entering this command: ls -l /opt/3com/VCX The symbolic link (VCX) should point to the new version of the VCX software (7.1.xc). If the link does not point to the new version, wait a few minutes and reenter the command.
  • Page 176 After the system has completed the restart process, verify that the upgrade has occurred by entering this command: ls -l /opt/3com/VCX The symbolic link (VCX) should point to the new version of the VCX software (7.1.xc). If the link does not point to the new version, wait a few minutes and reenter the command.

  • Page 177: Set Up Database Replication

    Upgrading a Single-Site System With Two Servers 6 Stop the Authentication and Directory service by entering the following commands: cd /opt/3com/VCX/scripts/rc3.d ./S20vcxdata stop Set Up Database Follow the steps in this section to set up database replication. Replication 1 Stop the Tomcat process, first on the primary VCX server and then on the secondary VCX server by entering these commands: cd /opt/3com/VCX/scripts/rc3.d...

  • Page 178: Upgrading A Single-Site System With Four Servers

    4 Start the Authentication and Directory service on the primary VCX server and the secondary VCX server by entering the following commands: cd /opt/3com/VCX/scripts/rc3.d ./S20vcxdata start 5 Start the Tomcat process on the primary VCX server and the secondary VCX server by entering the following command: ./S70tomcat start...
  • Page 179 Telephony server. 2 Stop the Tomcat process, first on the primary IP Telephony server and then on the secondary IP Telephony server by entering these commands: cd /opt/3com/VCX/scripts/rc3.d ./S70tomcat stop 3 Ensure that database replication has no errors (see Preliminary...
  • Page 180 5 Stop IP Messaging, first on the primary IP Messaging server and then on the secondary IP Messaging server by entering these commands: cd /opt/3com/VCX/scripts/rc3.d ./S60ums stop 6 Obtain a copy of the software upgrade file vcx-softswitch-7.1.xc.tar...

  • Page 181: Upgrading The Primary Ip Telephony Server

    Upgrading a Single-Site System With Four Servers Upgrading the Follow the steps in this section to upgrade the primary IP Telephony Primary IP Telephony server. Server 1 To start the upgrade process, enter these commands on the primary IP Telephony server: cd /opt/installtemp tar xvf vcx-softswitch-7.1.xc.tar cd upgrade-7.1.xc...

  • Page 182: Upgrading The Primary Ip Messaging Server

    6 After the system has completed the restart process, verify that the upgrade has occurred by entering this command: ls -l /opt/3com/VCX The symbolic link (VCX) should point to the new version of the VCX software (7.1.xc). If the link does not point to the new version, wait a few minutes and reenter the command.
  • Page 183 Upgrading a Single-Site System With Four Servers ------------------- Installation Completed Successfully ------------------- ------------------- VCX version 7.1.xc is now available ------------------- 2 Switch to the new software version by entering the following command: vcx-switchversion 7.1.xc The system displays several status messages and provides prompts that allow you enable UPS Monitoring and Global Voicemail Integration.

  • Page 184: Upgrading The Secondary Ip Telephony Server

    6 After the system has completed the restart process, verify that the upgrade has occurred by entering this command: ls -l /opt/3com/VCX The symbolic link (VCX) should point to the new version of the VCX software (7.1.xc). If the link does not point to the new version, wait a few minutes and reenter the command.
  • Page 185 6 After the system has completed the restart process, verify that the upgrade has occurred by entering this command: ls -l /opt/3com/VCX The symbolic link (VCX) should point to the new version of the VCX software (7.1.xc). If the link does not point to the new version, wait a few...

  • Page 186: Upgrading The Secondary Ip Messaging Server

    This could take several minutes and it is important the link pointer is correct before proceeding. Example Output /opt/3com/VCX -> /opt/3com/VCX.7.1.xc 7 Stop the Authentication and Directory service by entering the following commands: cd /opt/3com/VCX/scripts/rc3.d ./S20vcxdata stop...

  • Page 187: Set Up Database Replication

    5 After the system has completed the restart process, verify that the upgrade has occurred by entering this command: ls -l /opt/3com/VCX The symbolic link (VCX) should point to the new version of the VCX software (7.1.xc). If the link does not point to the new version, wait a few minutes and reenter the command.
  • Page 188 A: U VCX S V7.0 V7.1 PPENDIX PGRADING ERVER OFTWARE b The Enter the Number of MASTER SITEs other than the MASTER [1]: prompt appears. DEFINITION SITE Press Enter to accept the default. c The Enter the MASTER DEFINITION SITE IP Address [IP prompt appears.

  • Page 189: Upgrading A Multi-Site System With No Branch Offices

    4 Start the Authentication and Directory service on the primary IP Telephony server and the secondary IP Telephony server by entering the following commands: cd /opt/3com/VCX/scripts/rc3.d ./S20vcxdata start 5 Start the Tomcat process on the primary IP Telephony server and the secondary IP Telephony server by entering the following command: ./S70tomcat start...
  • Page 190 A: U VCX S V7.0 V7.1 PPENDIX PGRADING ERVER OFTWARE The system displays several status messages. The last two messages are: ------------------- Installation Completed Successfully ------------------- ------------------- VCX version 7.1.xc is now available ------------------- 5 Change to the new software version by entering this command: vcx-switchversion 7.1.xc The system displays several status messages and provides prompts that allow you enable Adhoc Conferencing and UPS Monitoring.

  • Page 191: Upgrading A Multi-Site Vcx System With Branch Offices

    Upgrading a Multi-Site VCX System with Branch Offices ls -l /opt/3com/VCX The symbolic link (VCX) should point to the new version of the VCX software (7.1.xc). If the link does not point to the new version, wait a few minutes and reenter the command. This could take several minutes and it is important the link pointer is correct before proceeding.

  • Page 192: Multi-Site Vcx System Upgrade Order

    A: U VCX S V7.0 V7.1 PPENDIX PGRADING ERVER OFTWARE System Administration Guide for more information and for configuration options. The components in a multi-site VCX system can be set up in many possible configurations. The procedures in this section are based on a multi-site VCX system that includes two regions (Region 1 and Region 2) with multiple branch offices in each region.
  • Page 193 1 Log in, as root, to the Call server in Region 1. 2 Stop the Tomcat process by entering the following commands: cd /opt/3com/VCX/scripts/rc3.d ./S70tomcat stop 3 Log in, as root, to the Authentication and Directory server in Region 1.
  • Page 194 A: U VCX S V7.0 V7.1 PPENDIX PGRADING ERVER OFTWARE e The Do you want to continue with the above settings? [n/y]: prompt appears. Enter to continue. The script executes. 5 Enter the following command to exit the cworks account and return to the root account: exit 6 Obtain a copy of the...
  • Page 195 After the system has completed the restart process, verify that the upgrade has occurred by entering the following command: ls -l /opt/3com/VCX The symbolic link (VCX) should point to the new version of the VCX software (7.1.xc). If the link does not point to the new version, wait a few minutes and reenter the command.
  • Page 196 A: U VCX S V7.0 V7.1 PPENDIX PGRADING ERVER OFTWARE b The Enter the Number of MASTER SITEs other than the MASTER : prompt appears. DEFINITION SITE Enter the number of Master sites. To determine the number of Master sites associated with this server, use the listVcxdata command. See Manually Configuring Replication for an IP Telephony Server or IP Telephony and Messaging Server for more information.
  • Page 197 After the system has completed the restart process, verify that the upgrade has occurred by entering the following command: ls -l /opt/3com/VCX The symbolic link (VCX) should point to the new version of the VCX software (7.1.xc). If the link does not point to the new version, wait a few minutes and reenter the command.
  • Page 198 1 On the Authentication and Directory server in Region 1, upgrade the replica on the Region 2 database by entering the following commands: su - cworks cd /opt/3com/VCX/vcxdata/bin ./upgradeVcxdata prompt Enter the VCX Site Identification i.e. Site Id: appears.
  • Page 199 6 Set up database replication on Region 2 by entering the following commands (you should still be logged in to the Authentication and Directory server as cworks): cd /opt/3com/VCX/vcxdata/bin ./setupReplication The replication setup script starts. Follow these steps: a The prompt Enter the VCX Site Identification i.e.

  • Page 200: Upgrading The Regional Ip Messaging Servers

    7 Once replication is complete and status is NORMAL on Region 1 and Region 2, start the Authentication and Directory servers in each region by entering the following commands while logged in as root: cd /opt/3com/VCX/scripts/rc3.d ./S20vcxdata start 8 Start the Tomcat process on the primary Call server and the secondary Call server in each region by entering the following commands: cd /opt/3com/VCX/scripts/rc3.d...
  • Page 201 To upgrade IP Messaging servers running version 7.0 software: 1 Stop the primary IP Messaging server and a secondary IP Messaging server by entering the following commands, as root, on each server: cd /opt/3com/VCX/scripts/rc3.d ./S60ums stop 2 Obtain a copy of the software upgrade file and vcx-ipmsg-7.1.xc.tar...
  • Page 202 A: U VCX S V7.0 V7.1 PPENDIX PGRADING ERVER OFTWARE The system may prompt you to confirm that a new operating system version will be installed and indicates which disk partition will be used after the upgrade. If you see such a prompt, answer y. The system displays several status messages.

  • Page 203: Upgrading The Regional Call Servers

    After the system has completed the restart process, verify that the upgrade has occurred by entering this command: ls -l /opt/3com/VCX The symbolic link (VCX) should point to the new version of the VCX software (7.1.xc). If the link does not point to the new version, wait a few minutes and reenter the command.
  • Page 204 A: U VCX S V7.0 V7.1 PPENDIX PGRADING ERVER OFTWARE To upgrade the Call servers: 1 Log on, as root, to the primary Call server and the secondary Call server in a region. 2 Obtain a copy of the software upgrade file vcx-callserver-7.1.xc.tar and place it in the directory on the primary Call server...

  • Page 205: Upgrading The Regional Call Records Server

    After the system has completed the restart process, verify that the upgrade has occurred by entering this command: ls -l /opt/3com/VCX The symbolic link (VCX) should point to the new version of the VCX software (7.1.xc). If the link does not point to the new version, wait a few minutes and reenter the command.
  • Page 206 After the system has completed the restart process, verify that the upgrade has occurred by entering the following command: ls -l /opt/3com/VCX The symbolic link (VCX) should point to the new version of the VCX software (7.1.xc). If the link does not point to the new version, wait a few...

  • Page 207: Upgrading Branch Offices

    This could take several minutes and it is important the link pointer is correct before proceeding. Example Output: /opt/3com/VCX -> /opt/3com/VCX.7.1.xc Upgrading Branch This section describes how to upgrade branch offices. Each branch office Offices is associated with a regional office.
  • Page 208 A: U VCX S V7.0 V7.1 PPENDIX PGRADING ERVER OFTWARE that will replace the current version. The letter vcx-all-7.1.3c.tar) always appended to the version number. 3 To start the upgrade process, enter the following commands: cd /opt/installtemp tar xvf vcx-all-7.1.xc.tar cd upgrade-7.1.xc ./install-upgrade The system may prompt you to confirm that a new operating system...
  • Page 209 After the system has completed the restart process, verify that the upgrade has occurred by entering this command: ls -l /opt/3com/VCX The symbolic link (VCX) should point to the new version of the VCX software (7.1.xc). If the link does not point to the new version, wait a few...
  • Page 210 This could take several minutes and it is important the link pointer is correct before proceeding. Example Output /opt/3com/VCX -> /opt/3com/VCX.7.1.xc 9 Repeat steps 1 through 8 for all the other branch office servers in Region 1.

  • Page 211: Configuring Ups Monitoring

    8 After the system has completed the restart process, verify that the upgrade has occurred by entering this command: ls -l /opt/3com/VCX The symbolic link (VCX) should point to the new version of the VCX software (7.1.xc). If the link does not point to the new version, wait a few minutes and reenter the command.
  • Page 212 A: U VCX S V7.0 V7.1 PPENDIX PGRADING ERVER OFTWARE This section assumes you have answered to the following prompt during an upgrade to VCX version 7.1 software: An Uninterruptible Power Supply (UPS) can be used with VCX systems to avoid disruption due to a power outage. provides a UPS monitoring service which tracks the UPS's status and performs a safe shutdown when the its battery is depleted during a long power outage.
  • Page 213 Upgrading a Multi-Site VCX System with Branch Offices UPS Monitoring requires a network-enabled UPS. Enter the IP address assigned to the UPS's management card or Ethernet interface. Note: The UPS must already be configured with this address. UPS IP address : Enter the IP address assigned to the UPS.
  • Page 214 A: U VCX S V7.0 V7.1 PPENDIX PGRADING ERVER OFTWARE Enter the UPS battery threshold charge. The default is 25%. The range is from 25% to 75%. 8 The upgrade script gives you the opportunity to change your UPS monitoring configuration: Do you wish to change any of the UPS Monitoring parameters? [N] : Enter...
  • Page 215 VCX S PGRADING ERVER V7.1. OFTWARE X TO V7.1. This appendix describes the procedures required to upgrade a system running VCX server software version 7.1.x to VCX server software version 7.1.y. This appendix includes the following topics: Verifying Software Versions ■...

  • Page 216: Verifying Software Versions

    VCX version. The running VCX version is preceded by a symbolic link icon ( -> lrwxrwxrwx 1 root root 21 May 12 09:13 VCX -> /opt/3com/VCX.7.1.1c drwxr-xr-x 10 root root 4096 May 10 07:13 VCX.7.1.0c In this example, the link points to version 7.1.1c. The other listed release, 7.1.0c, is installed, but not running.

  • Page 217: Overview Of A 7.1.X To 7.1.Y Upgrade

    3Com Corporation’s Enterprise Management Suite (EMS). EMS is an SNMP-based client/server application. Refer to the Enterprise Management Suite User Guide for VCX V7000 Components for information. All components in a VCX system must run the same version of VCX software.

  • Page 218: Preliminary Steps

    To check replication status, execute the following steps on the server hosting the Authentication and Directory services database: Log in using the cworks account. Enter: cd /opt/3com/VCX/vcxdata/bin Enter: ./checkReplication The returned status should be NORMAL. If replication errors need to...

  • Page 219: Upgrading A Single-Site System With Two Servers

    Upgrading a Single-Site System With Two Servers Supported on: Single-site systems with four servers ■ Multi-site systems that include servers at regional offices and ■ servers at branch offices that use global or local IP Messaging A pair of Global Voicemail Central Servers (GVCS) to enable Global ■...
  • Page 220 1 Log in as root on the primary VCX server and on the secondary VCX server. 2 Stop the Tomcat process, first on the primary VCX server and then on the secondary VCX server by entering these commands: cd /opt/3com/VCX/scripts/rc3.d ./S70tomcat stop 3 Ensure that database replication has no errors (see Preliminary...

  • Page 221: Upgrading The Primary Vcx Server

    5 Stop IP Messaging, first on the primary VCX server and then on the secondary VCX server by entering these commands: cd /opt/3com/VCX/scripts/rc3.d ./S60ums stop 6 Obtain a copy of the software upgrade file and vcx-all-7.1.yc.tar...

  • Page 222: Upgrading The Secondary Vcx Server

    3 After the system has completed the restart process, verify that the upgrade has occurred by entering this command: ls -l /opt/3com/VCX The symbolic link (VCX) should point to the new version of the VCX software (7.1.yc). If the link does not point to the new version, wait a few minutes and reenter the command.

  • Page 223: Set Up Database Replication

    3 After the system has completed the restart process, verify that the upgrade has occurred by entering this command: ls -l /opt/3com/VCX The symbolic link (VCX) should point to the new version of the VCX software (7.1.yc). If the link does not point to the new version, wait a few minutes and reenter the command.
  • Page 224 B: U VCX S V7.1. V7.1. PPENDIX PGRADING ERVER OFTWARE X TO Enter site ID configured for this system. For single-site systems, the site ID is identical for both the primary VCX server and the secondary VCX server. b The Enter the Number of MASTER SITEs other than the MASTER [1]: prompt appears.

  • Page 225: Upgrading A Single-Site System With Four Servers

    Upgrading a Single-Site System With Four Servers 4 Start the Authentication and Directory service on the primary VCX server and the secondary VCX server by entering the following commands: cd /opt/3com/VCX/scripts/rc3.d ./S20vcxdata start 5 Start the Tomcat process on the primary VCX server and the secondary VCX server by entering the following command: ./S70tomcat start...
  • Page 226 5 Stop IP Messaging, first on the primary IP Messaging server and then on the secondary IP Messaging server by entering these commands: cd /opt/3com/VCX/scripts/rc3.d ./S60ums stop 6 Obtain a copy of the software upgrade file vcx-softswitch-7.1.yc.tar...

  • Page 227: Upgrading The Primary Ip Telephony Server

    Upgrading a Single-Site System With Four Servers 7 Obtain a copy of the software upgrade file and vcx-ipmsg-7.1.yc.tar place it in the directory on the primary IP Messaging /opt/installtemp server and on the secondary IP Messaging server. Next, execute the following steps in the order listed: Upgrade the primary IP Telephony server.

  • Page 228: Upgrading The Primary Ip Messaging Server

    3 After the system has completed the restart process, verify that the upgrade has occurred by entering this command: ls -l /opt/3com/VCX The symbolic link (VCX) should point to the new version of the VCX software (7.1.yc). If the link does not point to the new version, wait a few minutes and reenter the command.

  • Page 229: Upgrading The Secondary Ip Telephony Server

    Upgrading a Single-Site System With Four Servers ls -l /opt/3com/VCX The symbolic link (VCX) should point to the new version of the VCX software (7.1.yc). If the link does not point to the new version, wait a few minutes and reenter the command. This could take several minutes and it is important the link pointer is correct before proceeding.

  • Page 230: Upgrading The Secondary Ip Messaging Server

    PPENDIX PGRADING ERVER OFTWARE X TO Example Output /opt/3com/VCX -> /opt/3com/VCX.7.1.yc 4 Stop the Authentication and Directory service by entering the following commands: cd /opt/3com/VCX/scripts/rc3.d ./S20vcxdata stop Upgrading the Follow the steps in this section to upgrade the secondary IP Messaging Secondary IP server.

  • Page 231: Set Up Database Replication

    1 Stop the Tomcat process, first on the primary IP Telephony server and then on the secondary IP Telephony server by entering these commands (log in as root): cd /opt/3com/VCX/scripts/rc3.d ./S70tomcat stop 2 Set up replication on the primary IP Telephony server by entering these...

  • Page 232: Upgrading A Multi-Site System With No Branch Offices

    4 Start the Authentication and Directory service on the primary IP Telephony server and the secondary IP Telephony server by entering the following commands: cd /opt/3com/VCX/scripts/rc3.d ./S20vcxdata start 5 Start the Tomcat process on the primary IP Telephony server and the secondary IP Telephony server by entering the following command: ./S70tomcat start...

  • Page 233: Upgrading The Call Records Server

    6 After the system has completed the restart process, verify that the upgrade has occurred by entering the following command: ls -l /opt/3com/VCX The symbolic link (VCX) should point to the new version of the VCX software (7.1.yc). If the link does not point to the new version, wait a few minutes and reenter the command.

  • Page 234: Upgrading A Multi-Site Vcx System With Branch Offices

    B: U VCX S V7.1. V7.1. PPENDIX PGRADING ERVER OFTWARE X TO Upgrading a Some multi-site VCX systems have regional offices and branch offices. Multi-Site VCX Each branch office is associated with a regional office. System with Branch Multi-site VCX systems can be categorized by the method used to Offices implement messaging.

  • Page 235: Multi-Site Vcx System Upgrade Order

    Upgrading a Multi-Site VCX System with Branch Offices section are based on a multi-site VCX system that includes two regions (Region 1 and Region 2) with multiple branch offices in each region. All upgrade commands are executed locally at the console. When upgrading a region-to-region office configuration, you must drop replication between the Authentication and Directory server in each region.
  • Page 236 1 Log in, as root, to the Call server in Region 1. 2 Stop the Tomcat process by entering the following commands: cd /opt/3com/VCX/scripts/rc3.d ./S70tomcat stop 3 Log in, as root, to the Authentication and Directory server in Region 1.
  • Page 237 9 After the system has completed the restart process, verify that the upgrade has occurred by entering the following command: ls -l /opt/3com/VCX The symbolic link (VCX) should point to the new version of the VCX software (7.1.yc). If the link does not point to the new version, wait a few minutes and reenter the command.
  • Page 238 1 Log in, as root, to the Call server in Region 2. 2 Stop the Tomcat process by entering the following commands: cd /opt/3com/VCX/scripts/rc3.d ./S70tomcat stop 3 Log in, as root, to the Authentication and Directory server in Region 2.
  • Page 239 9 After the system has completed the restart process, verify that the upgrade has occurred by entering the following command: ls -l /opt/3com/VCX The symbolic link (VCX) should point to the new version of the VCX software (7.1.yc). If the link does not point to the new version, wait a few minutes and reenter the command.
  • Page 240 Directory server in each region. You should still be logged in, as root, in each region. 1 On the Authentication and Directory server in Region 1, upgrade the Region 2 database by entering the following commands: su - cworks cd /opt/3com/VCX/vcxdata/bin ./upgradeVcxdata prompt Enter the VCX Site Identification i.e. Site Id: appears.
  • Page 241 6 Set up database replication on Region 2 by entering the following commands (you should still be logged in to the Authentication and Directory server as cworks): cd /opt/3com/VCX/vcxdata/bin ./setupReplication The replication setup script starts. Follow these steps: a The prompt Enter the VCX Site Identification i.e.

  • Page 242: Upgrading The Regional Ip Messaging Servers

    7 Once replication is complete and status is NORMAL on Region 1 and Region 2, start the Authentication and Directory servers in each region by entering the following commands while logged in as root: cd /opt/3com/VCX/scripts/rc3.d ./S20vcxdata start 8 Start the Tomcat process on the primary Call server and the secondary Call server in each region by entering the following commands: cd /opt/3com/VCX/scripts/rc3.d...
  • Page 243 To upgrade the IP Messaging servers: 1 Stop the primary IP Messaging server and a secondary IP Messaging server by entering the following commands, as root, on each server: cd /opt/3com/VCX/scripts/rc3.d ./S60ums stop 2 Obtain a copy of the software upgrade file and vcx-ipmsg-7.1.yc.tar...

  • Page 244: Upgrading The Regional Call Servers

    After the system has completed the restart process, verify that the upgrade has occurred by entering this command: ls -l /opt/3com/VCX The symbolic link (VCX) should point to the new version of the VCX software (7.1.yc). If the link does not point to the new version, wait a few minutes and reenter the command.
  • Page 245 After the system has completed the restart process, verify that the upgrade has occurred by entering this command: ls -l /opt/3com/VCX The symbolic link (VCX) should point to the new version of the VCX software (7.1.yc). If the link does not point to the new version, wait a few minutes and reenter the command.

  • Page 246: Upgrading The Regional Call Records Server

    5 After the system has completed the restart process, verify that the upgrade has occurred by entering the following command: ls -l /opt/3com/VCX The symbolic link (VCX) should point to the new version of the VCX software (7.1.yc). If the link does not point to the new version, wait a few minutes and reenter the command.

  • Page 247: Upgrading The Branch Offices

    Upgrading a Multi-Site VCX System with Branch Offices Upgrading the Branch This section describes how to upgrade branch offices. Each branch office Offices is associated with a regional office. As noted in Upgrading a Multi-Site VCX System with Branch Offices, multi-site VCX systems can be categorized by the method used to implement messaging: global messaging, local messaging, or Global Voicemail Integration.
  • Page 248 5 After the system has completed the restart process, verify that the upgrade has occurred by entering this command: ls -l /opt/3com/VCX The symbolic link (VCX) should point to the new version of the VCX software (7.1.yc). If the link does not point to the new version, wait a few minutes and reenter the command.
  • Page 249 5 After the system has completed the restart process, verify that the upgrade has occurred by entering this command: ls -l /opt/3com/VCX The symbolic link (VCX) should point to the new version of the VCX software (7.1.yc). If the link does not point to the new version, wait a few minutes and reenter the command.
  • Page 250 B: U VCX S V7.1. V7.1. PPENDIX PGRADING ERVER OFTWARE X TO...
  • Page 251 VCX S PGRADING ERVER V6.0 V7.0 OFTWARE This appendix describes the procedures required to upgrade a system running VCX server software version 6.0 to VCX server software version 7.0. This appendix includes the following topics: Verifying Software Versions ■ Overview of a 6.0 to 7.0 Upgrade ■...

  • Page 252: Verifying Software Versions

    VCX version. The running VCX version is preceded by a symbolic link icon ( -> lrwxrwxrwx 1 root root 21 Oct 13 09:13 VCX -> /opt/3com/VCX.6.0.1c drwxr-xr-x 10 root root 4096 Oct 10 09:13 VCX.6.0.0c In this example, the link points to version 6.0.1c. The other listed release, 6.0.0c, is installed, but not running.
  • Page 253 Overview of a 6.0 to 7.0 Upgrade Enterprise Management Suite User Guide for VCX V7000 Components for information. All components in a VCX system must run the same version of VCX software. This requirement has the following implications: You cannot upgrade or downgrade one component in a VCX system ■...
  • Page 254 C: U VCX S V6.0 V7.0 PPENDIX PGRADING ERVER OFTWARE Enter: ./checkReplication The returned status should be NORMAL. If replication errors need to be cleared: Enter: ./deleteReplicationErrors CAUTION: Do not attempt an upgrade if there are replication errors that cannot be deleted. After the upgrade, you must restart database replication.
  • Page 255 Overview of a 6.0 to 7.0 Upgrade With version 7.0, you can set up IP Messaging in a client/server configuration. An IP Messaging server can support up to 20 IP Messaging clients. See the IP Messaging Operations and System Administration Guide for details. When you upgrade a primary IP Messaging server running version 6.0 IP Messaging software to version 7.0, the upgrade script asks if you want the system to support IP Messaging client systems.

  • Page 256: License Keys

    1 Log on the primary VCX server running the Call Processor service as the root user. 2 Run the password management script by entering these commands: cd /opt/3com/VCX/tomcat/scripts/ ./admincfg 3 Follow the script prompts to change the password. 4 When the script finishes, enter Y to ensure that the changes take effect.
  • Page 257 /opt/installtemp 3Com strongly recommends that you save copies of your license key files in a separate, safe location. If any VCX server experiences a disk or other failure that requires reinstallation of the VCX software, the license key file must be available for that process.

  • Page 258: Upgrading A Single-Site System With Two Servers

    1 Log in as root on the primary VCX server and on the secondary VCX server. 2 Stop the Tomcat process, first on the primary VCX server and then on the secondary VCX server by entering these commands: cd /opt/3com/VCX/scripts/rc3.d ./S70tomcat stop...
  • Page 259 Upgrading a Single-Site System With Two Servers 3 Drop database replication on the primary VCX server by entering these commands: cd /opt/3com/VCX/vcxdata/bin su cworks ./dropReplication The drop replication script starts. Follow these steps: a The prompt Enter the VCX Site Identification i.e. Site Id appears.

  • Page 260: Upgrading The Primary Vcx Server

    The system displays several status messages and then reboots. After the the reboot process has been completed, the system starts VCX 7.0.x services. 5 After the system has completed the restart process, verify that the upgrade has occurred by entering this command: ls -l /opt/3com/VCX...

  • Page 261: Upgrading The Secondary Vcx Server

    Upgrading a Single-Site System With Two Servers The symbolic link (VCX) should point to the new version of the VCX software (7.0.xc). Example Output /opt/3com/VCX -> /opt/3com/VCX.7.0.xc 6 Stop the Authentication and Directory service by entering the following commands: cd /opt/3com/VCX/scripts/rc3.d ./S20vcxdata stop...

  • Page 262: Set Up Database Replication

    5 After the system has completed the restart process, verify that the upgrade has occurred by entering this command: ls -l /opt/3com/VCX The symbolic link (VCX) should point to the new version of the VCX software (7.0.xc). Example Output /opt/3com/VCX ->...
  • Page 263 3 When the replication is complete, enter the following command to exit the cworks account and return to the root account: exit 4 Start the Authentication and Directory service on the primary VCX server and the secondary VCX server by entering the following commands: cd /opt/3com/VCX/scripts/rc3.d ./S20vcxdata start...

  • Page 264: Upgrading A Single-Site System With Four Servers

    2 Stop the Tomcat process, first on the primary IP Telephony server and then on the secondary IP Telephony server by entering these commands: cd /opt/3com/VCX/scripts/rc3.d ./S70tomcat stop 3 Drop database replication on the primary IP Telephony server by entering...
  • Page 265 5 Stop IP Messaging, first on the primary IP Messaging server and then on the secondary IP Messaging server by entering these commands: cd /opt/3com/VCX/scripts/rc3.d ./S60ums stop 6 Obtain a copy of the software upgrade file vcx-softswitch-7.0.xc.tar...

  • Page 266: Upgrading The Primary Ip Telephony Server

    C: U VCX S V6.0 V7.0 PPENDIX PGRADING ERVER OFTWARE Next, execute the following steps in the order listed: Upgrade the primary IP Telephony server. See Upgrading the Primary IP ■ Telephony Server. Upgrade the primary IP Messaging server. See Upgrading the Primary ■...

  • Page 267: Upgrading The Primary Ip Messaging Server

    Upgrading a Single-Site System With Four Servers 5 After the system has completed the restart process, verify that the upgrade has occurred by entering this command: ls -l /opt/3com/VCX The symbolic link (VCX) should point to the new version of the VCX software (7.0.xc).
  • Page 268 VCX 7.0.x IP Messaging services. 6 After the system has completed the restart process, verify that the upgrade has occurred by entering this command: ls -l /opt/3com/VCX The symbolic link (VCX) should point to the new version of the VCX software (7.0.xc).

  • Page 269: Upgrading The Secondary Ip Telephony Server

    Upgrading a Single-Site System With Four Servers Example Output /opt/3com/VCX -> /opt/3com/VCX.7.0.xc 7 Stop IP Messaging. When the primary IP Messaging reboots, IP Messaging restarts and must be stopped before you can upgrade the secondary IP Messaging server. However, you should ensure IP Messaging is fully active before stopping it.

  • Page 270: Upgrading The Secondary Ip Messaging Server

    Telephony services. 5 After the system has completed the restart process, verify that the upgrade has occurred by entering this command: ls -l /opt/3com/VCX The symbolic link (VCX) should point to the new version of the VCX software (7.0.xc). Example Output /opt/3com/VCX ->...

  • Page 271: Set Up Database Replication

    Messaging services. 5 After the system has completed the restart process, verify that the upgrade has occurred by entering this command: ls -l /opt/3com/VCX The symbolic link (VCX) should point to the new version of the VCX software (7.0.xc). Example Output /opt/3com/VCX ->...
  • Page 272 4 Start the Authentication and Directory service on the primary IP Telephony server and the secondary IP Telephony server by entering the following commands: cd /opt/3com/VCX/scripts/rc3.d ./S20vcxdata start 5 Start the Tomcat process on the primary IP Telephony server and the secondary IP Telephony server by entering the following command: ./S70tomcat start...

  • Page 273: Upgrading A Multi-Site System With No Branch Offices

    Upgrading a Multi-Site System With No Branch Offices 6 Start IP Messaging on the primary IP Messaging server by entering the following command: ./S60ums start Run the script on both the primary VCX server and the admincfg secondary VCX server. See Post-Upgrade Requirements.

  • Page 274: Upgrading A Multi-Site Vcx System With Branch Offices

    8 After the system has completed the restart process, verify that the upgrade has occurred by entering the following command: ls -l /opt/3com/VCX The symbolic link (VCX) should point to the new version of the VCX software (7.0.xc). Example Output: /opt/3com/VCX ->...

  • Page 275: Multi-Site Vcx System Upgrade Order

    2 Stop the Tomcat process, first on the primary Call server and then on the secondary Call server in each region by entering the following commands: cd /opt/3com/VCX/scripts/rc3.d ./S70tomcat stop 3 Log in, as root, to the Authentication and Directory server in Region 1.
  • Page 276 V6.0 V7.0 PPENDIX PGRADING ERVER OFTWARE 4 Stop database replication by entering the following commands: cd /opt/3com/VCX/vcxdata/bin su cworks ./dropReplication The drop replication script starts. Follow these steps: a The prompt Enter the VCX Site Identification i.e. Site Id appears.
  • Page 277 Authentication and Directory service. 11 After the system has completed the restart process, verify that the upgrade has occurred by entering the following command: ls -l /opt/3com/VCX The symbolic link (VCX) should point to the new version of the VCX software (7.1.xc).
  • Page 278 Authentication and Directory service. 21 After the system has completed the restart process, verify that the upgrade has occurred by entering the following command: ls -l /opt/3com/VCX The symbolic link (VCX) should point to the new version of the VCX software (7.0.xc).
  • Page 279 Directory server in each region. You should still be logged in, as root, in each region. 1 On the Authentication and Directory server in Region 1, upgrade the Region 2 database by entering the following commands: su - cworks cd /opt/3com/VCX/vcxdata/bin ./upgradeVcxdata prompt Enter the VCX Site Identification i.e. Site Id: appears.
  • Page 280 6 Set up database replication on Region 2 by entering the following commands (you should still be logged in to the Authentication and Directory server as cworks): cd /opt/3com/VCX/vcxdata/bin ./setupReplication The replication setup script starts. Follow the procedure described in step 5.

  • Page 281: Upgrading The Regional Ip Messaging Servers

    To upgrade the IP Messaging servers: 1 Stop the primary IP Messaging server and a secondary IP Messaging server by entering the following commands, as root, on each server: cd /opt/3com/VCX/scripts/rc3.d ./S60ums stop 2 Obtain a copy of the software upgrade file and vcx-ipmsg-7.0.xc.tar...
  • Page 282 C: U VCX S V6.0 V7.0 PPENDIX PGRADING ERVER OFTWARE d Switch to the new software version by entering the following command: vcx-switchversion 7.0.xc e Specify whether this IP Messaging system will support IP Messaging clients. The upgrade script displays the following prompt for the primary IP Messaging server only: Will this system support IPMSG client systems? [N]: IP Messaging can be deployed in a client/server configuration to...

  • Page 283: Upgrading The Regional Call Servers

    VCX 7.0.x IP Messaging services. After the system has completed the restart process, verify that the upgrade has occurred by entering this command: ls -l /opt/3com/VCX The symbolic link (VCX) should point to the new version of the VCX software (7.0.xc).

  • Page 284: Upgrading The Regional Call Records Server

    Call server. e After the system has completed the restart process, verify that the upgrade has occurred by entering this command: ls -l /opt/3com/VCX The symbolic link (VCX) should point to the new version of the VCX software (7.0.xc). Example Output /opt/3com/VCX ->...

  • Page 285: Upgrading The Branch Offices

    7 After the system has completed the restart process, verify that the upgrade has occurred by entering the following command: ls -l /opt/3com/VCX The symbolic link (VCX) should point to the new version of the VCX software (7.0.xc). Example Output: /opt/3com/VCX ->...
  • Page 286 1 Stop the Tomcat process on the Call servers in Region 1 by logging in to each server as root and executing the following commands: cd /opt/3com/VCX/scripts/rc3.d ./S70tomcat stop 2 Log in to the first branch office server as root.
  • Page 287 8 After the system has completed the restart process, verify that the upgrade has occurred by entering this command: ls -l /opt/3com/VCX The symbolic link (VCX) should point to the new version of the VCX software (7.0.xc). Example Output /opt/3com/VCX ->...
  • Page 288 8 After the system has completed the restart process, verify that the upgrade has occurred by entering this command: ls -l /opt/3com/VCX The symbolic link (VCX) should point to the new version of the VCX software (7.0.xc). Example Output /opt/3com/VCX ->...
  • Page 289 Upgrading a Multi-Site VCX System with Branch Offices server, IP Telephony server, and Call Processing server). See Post-Upgrade Requirements.
  • Page 290 C: U VCX S V6.0 V7.0 PPENDIX PGRADING ERVER OFTWARE...
  • Page 291 VCX S OWNGRADING ERVER OFTWARE This appendix describes the procedures you can perform to downgrade the VCX software running on your system to a previously installed version. This chapter includes the following topics: Verifying Software Versions ■ Downgrading from 7.1 to 7.0 ■...

  • Page 292: Verifying Software Versions

    VCX version. The running VCX version is preceded by a symbolic link icon ( -> lrwxrwxrwx 1 root root 21 Jan 13 09:13 VCX -> /opt/3com/VCX.7.0.1c drwxr-xr-x 10 root root 4096 Jan 10 07:13 VCX.7.0.0c In this example, the link points to version 7.0.1c. The other listed release, 7.0.0c, is installed, but not running.

  • Page 293: Downgrading From 7.1 To 7.0

    7.1. Following this procedure restores the VCX system to the operational state it was in prior to the upgrade occurring. If an upgrade at a regional office is unsuccessful, contact your 3Com ■ Support for assistance and downgrade the regional office servers. Do not upgrade any branch office servers that are associated with that regional office until the regional office upgrades are successful.
  • Page 294 CAUTION: Do not reboot the system or restart VCX services until databases have been restored. The VCX 7.0 version has been selected but the databases still contain 7.1 versioned data. This combination will not operate successfully. 2 Update the pointer to the configuration file using this command: SetConfigFile /opt/3com/VCX/conf/VCXConfiguration.xml...
  • Page 295 1 On the Master Definition Site (the primary server), log in as root and enter these commands: cd /opt/3com/VCX/scripts/rc3.d ./S70tomcat stop 2 On the Master Site (the secondary server) log in as root and enter these commands: cd /opt/3com/VCX/scripts/rc3.d...
  • Page 296 IP Telephony server software, establish database replication. 1 On the Master Definition Site (the primary server), log in as root and enter these commands: cd /opt/3com/VCX/scripts/rc3.d ./S20vcxdata stop ./S70tomcat stop 2 On the Master Site (the secondary server), log in as root and enter these commands: cd /opt/3com/VCX/scripts/rc3.d...
  • Page 297 Downgrading from 7.1 to 7.0 installed and if so, how to revert to the previous version. This operation must be performed on all VCX servers. The examples in this procedure use the assumption that upgrading from version 7.0 to 7.1 changed the operating system version from 4.2.1 to 5.1.3.
  • Page 298 CAUTION: Do not reboot the system or restart VCX services until databases have been restored. The VCX 7.0 version has been selected but the databases still contain 7.1 versioned data. This combination will not operate successfully. 2 Update the pointer to the configuration file using this command: SetConfigFile /opt/3com/VCX/conf/VCXConfiguration.xml...
  • Page 299 Downgrading from 7.1 to 7.0 3 Switch operating system version The upgrade from 7.0 to 7.1 may or may not have required the installation of a new VCX operating system version. This step describes how to determine if a new operating system version was installed and if so, how to revert to the previous version.
  • Page 300 2 Update the pointer to the configuration file using this command: SetConfigFile /opt/3com/VCX/conf/VCXConfiguration.xml 3 If necessary, switch to the previous version of the operating system. The upgrade from 7.0 to 7.1 may or may not have required the installation of a new VCX operating system version.
  • Page 301 When the system reboots, it starts VCX 7.0 services. Downgrading a Branch Office Server If you attempt to upgrade a branch office server but the upgrade is unsuccessful, you must downgrade and contact 3Com Support for assistance. Switch VCX Version...
  • Page 302 7.1 versioned data. This combination will not operate successfully. 2 Update the pointer to the configuration file using this command: SetConfigFile /opt/3com/VCX/conf/VCXConfiguration.xml Stop Database Replication 1 On the Master Definition Site (the primary server), log in as root and enter these commands: cd /opt/3com/VCX/scripts/rc3.d...
  • Page 303 On Master Definition Site, establish database replication. 1 On the Master Definition Site (the primary server), log in as root and enter these commands: cd /opt/3com/VCX/scripts/rc3.d ./S20vcxdata stop ./S70tomcat stop 2 On the Master Site (the secondary server), log in as root and enter these commands: cd /opt/3com/VCX/scripts/rc3.d...
  • Page 304 D: D VCX S PPENDIX OWNGRADING ERVER OFTWARE The examples in this procedure use the assumption that upgrading from version 7.0 to 7.1 changed the operating system version from 4.2.1 to 5.1.3. 1 Log in as root. 2 To determine which operating system versions are available, enter this command: vcx-os-query The output from this command appears:...

  • Page 305: Downgrading From 7.1.Y To 7.1.X

    7.1.y. Following this procedure restores the VCX system to the operational state it was in prior to the upgrade occurring. If an upgrade at a regional office is unsuccessful, contact your 3Com ■ Support for assistance and downgrade the regional office servers. Do not upgrade any branch office servers that are associated with that regional office until the regional office upgrades are successful.

  • Page 306: Downgrading A Single-Site System (7.1.Y To 7.1.X)

    7.1.y versioned data. This combination will not operate successfully. 2 Update the pointer to the configuration file using this command: SetConfigFile /opt/3com/VCX/conf/VCXConfiguration.xml Stop Database Replication If the server is running IP Telephony and IP Messaging server software or IP Telephony server software, you must stop database replication.
  • Page 307 Downgrading from 7.1.y to 7.1.x 1 On the Master Definition Site (the primary server), log in as root and enter these commands: cd /opt/3com/VCX/scripts/rc3.d ./S70tomcat stop 2 On the Master Site (the secondary server) log in as root and enter these commands: cd /opt/3com/VCX/scripts/rc3.d...
  • Page 308 IP Telephony server software, establish database replication. 1 On the Master Definition Site (the primary server), log in as root and enter these commands: cd /opt/3com/VCX/scripts/rc3.d ./S20vcxdata stop ./S70tomcat stop 2 On the Master Site (the secondary server), log in as root and enter these commands: cd /opt/3com/VCX/scripts/rc3.d...

  • Page 309: Downgrading A Multiple-Site System (7.1.Y To 7.1.X)

    Downgrading from 7.1.y to 7.1.x The examples in this procedure use the assumption that upgrading from version 7.1.x to 7.1.y changed the operating system version from 4.2.0 to 4.2.1. 1 Log in as root. 2 To determine which operating system versions are available, enter this command: vcx-os-query The output from this command appears:...
  • Page 310 7.1.y versioned data. This combination will not operate successfully. 2 Update the pointer to the configuration file using this command: SetConfigFile /opt/3com/VCX/conf/VCXConfiguration.xml 3 Switch operating system version The upgrade from 7.1.x to 7.1.y may or may not have required the...
  • Page 311 Downgrading from 7.1.y to 7.1.x how to determine if a new operating system version was installed and if so, how to revert to the previous version. The examples in this step use the assumption that upgrading from version 7.1.x to 7.1.y changed the operating system version from 4.2.0 to 4.2.1. a Log in as root.
  • Page 312 2 Update the pointer to the configuration file using this command: SetConfigFile /opt/3com/VCX/conf/VCXConfiguration.xml 3 If necessary, switch to the previous version of the operating system. The upgrade from 7.1.x to 7.1.y may or may not have required the installation of a new VCX operating system version.
  • Page 313 When the system reboots, it starts VCX 7.1.x services. Downgrading a Branch Office Server If you attempt to upgrade a branch office server but the upgrade is unsuccessful, you must downgrade and contact 3Com Support for assistance. Switch VCX Version...
  • Page 314 7.1.y versioned data. This combination will not operate successfully. 2 Update the pointer to the configuration file using this command: SetConfigFile /opt/3com/VCX/conf/VCXConfiguration.xml Stop Database Replication 1 On the Master Definition Site (the primary server), log in as root and enter these commands: cd /opt/3com/VCX/scripts/rc3.d...
  • Page 315 On Master Definition Site, establish database replication. 1 On the Master Definition Site (the primary server), log in as root and enter these commands: cd /opt/3com/VCX/scripts/rc3.d ./S20vcxdata stop ./S70tomcat stop 2 On the Master Site (the secondary server), log in as root and enter these commands: cd /opt/3com/VCX/scripts/rc3.d...
  • Page 316 D: D VCX S PPENDIX OWNGRADING ERVER OFTWARE The examples in this procedure use the assumption that upgrading from version 7.1.x to 7.1.y changed the operating system version from 4.2.0 to 4.2.1. 1 Log in as root. 2 To determine which operating system versions are available, enter this command: vcx-os-query The output from this command appears:...

  • Page 317: Downgrading From 7.0 To 6.0

    7.0. Following this procedure restores the VCX system to the operational state it was in prior to the upgrade occurring. If an upgrade at a regional office is unsuccessful, contact your 3Com ■ Support for assistance and downgrade the regional office servers. Do not upgrade any branch office servers that are associated with that regional office until the regional office upgrades are successful.

  • Page 318: Downgrading A Single-Site System

    RAID configuration. If a VCX server enabled for RAID operation must be downgraded to a software version prior to 7.0, the server must be rebuilt. Contact your 3Com representative. Downgrading a This procedure describes how to downgrade VCX single-site systems.
  • Page 319 Downgrading from 7.0 to 6.0 command: vcx-switchversion Stops VCX services ■ Changes the /opt/3com/VCX link to point to the requested VCX ■ version Issues a warning that databases must be restored ■ CAUTION: Do not reboot the system or restart VCX services until databases have been restored.
  • Page 320 1 Log in to the server as cworks user. 2 Enter the following commands: cd /opt/3com/VCX/vcxdata/bin ./dropVcxdata 3 When the script prompts you, enter the site name for the database.
  • Page 321 1 Log in to the Master Definition Site (the primary server) as cworks user. 2 Enter the following commands: cd /opt/3com/VCX/vcxdata/bin ./setupReplication 3 When the script prompts you, enter the site ID of the Master Site. 4 Wait at least 20 minutes to allow time for database replication to be completed.

  • Page 322: Downgrading A Multi-Site System

    D: D VCX S PPENDIX OWNGRADING ERVER OFTWARE The output from this command is similar to the following: Version Partition Label Status 3.4.0 /dev/hda2 4.2.1 /dev/hda3 active The operating system versions that you see may vary from the example shown. Also, the order of the A and B versions may be reversed depending on the upgrade history of the system.
  • Page 323 ■ If the upgrade process fails while upgrading any type of VCX server, consult with your 3Com representative before attempting to downgrade the server. Follow the downgrade procedures documented in this section only if you want to revert a successfully upgraded server from version 7.0 to version 6.0.
  • Page 324 A branch must be running the same version of VCX software as the regional servers hosting the branch. This section assumes that all of the regional servers and the branch have been upgraded successfully. If the branch upgrade failed, contact your 3Com representative before attempting to downgrade to the previous release.
  • Page 325 2 Stop the Tomcat process, first on the primary Call server, then on the secondary Call server, and then on the branch server by entering the following commands: cd /opt/3com/VCX/scripts/rc3.d ./S70tomcat stop 3 Log in as cworks on the regional Authentication and Directory server (the...
  • Page 326 Copy the backup data (tgz file) for branch schema to the following two locations: /opt/3com/VCX/vcxdata/db/import /opt/3com/VCX/vcxdata/db/export b Enter the following commands: cd /opt/3com/VCX.6.0.x/vcxdata/bin ./restoreVcxdata Enter the site ID for the branch. 8 Log in as cworks on the branch and delete the branch schema by entering the following commands: cd /opt/3com/VCX/vcxdata/bin ./dropVcxdata...
  • Page 327 14 Log in as root to the regional Authentication and Directory server associated with the branch and enter the following commands to start the globaldir service: cd /opt/3com/VCX/scripts/rc3.d ./S30vcxglobaldir start At this point, because there is a version mismatch between the branch database and the regional database, you cannot access branch data through provisioning at the region.
  • Page 328 D: D VCX S PPENDIX OWNGRADING ERVER OFTWARE...
  • Page 329 VCX C OMMANDS This appendix describes the VCX commands you can use to manage and view VCX components. This appendix includes the following topic: Command Descriptions ■...

  • Page 330: Command Descriptions

    E: VCX C PPENDIX OMMANDS Command This guide describes how to maintain your VCX system. Most Descriptions maintenance operations require entering commands to perform a particular task or to run a script. The tables in this appendix describe all available VCX commands. Many of these commands are used (and described) elsewhere in this guide to perform maintenance tasks.
  • Page 331 Command Descriptions Table 17 VCX Installation, Removal, and Switching Commands Command Description vcx-install Used to install VCX components. Typically invoked as part of a higher level script. However, you can use this command install a codec. See How to Change Your Codec.
  • Page 332 — Displays the currently ■ running version of VCX software. issuer-name — Displays the name of the company ■ issuing the license, in this case, 3Com Corporation. customer-name — Displays the name of the customer. ■ customer-address — Displays customer address ■...
  • Page 333 Command Descriptions Table 19 VCX Version Information Commands (continued) Command Description vcx-showphone Supports the following arguments: softwareversion devapp — Displays the version of application software ■ running on telephones connected to the system. devboot — Displays the version of boot software ■...
  • Page 334 E: VCX C PPENDIX OMMANDS Table 20 Miscellaneous System Commands Command Description vcx-sysinfo Displays system information, for example, host name, serial number, networking information, and disk information. vcx-ups-setup For VCX versions 7.1 and higher, configures UPS monitoring on the machine. See Adding UPS Support to an Existing VCX System.
  • Page 335 ROCESSOR OMMAND NTERFACE OMMANDS This chapter contains a complete listing of command line interface (CLI) commands available for managing the call processor. This chapter includes the following topics: Call Processor CLI Overview ■ CLI Command Descriptions ■...
  • Page 336 The call processor can be configured from the server where the call Overview processor was installed by using the remoteCLI application. CAUTION: Consult with your authorized 3Com technical support representative before using the remoteCLI application to reconfigure a call processor. Incorrect use of this application can render the call processor inoperable.
  • Page 337 Table 21 Remote CLI Command Descriptions Command Description exit Quits the Remote CLI application. shutdown Shuts down the Call Processor gracefully. version Shows the software version of the Call Processor and the version of the Distributed Message Routing (DMR) 3Com proprietary protocol.
  • Page 338 F: C PPENDIX ROCESSOR OMMAND NTERFACE OMMANDS Table 21 Remote CLI Command Descriptions (continued) Command Description show Lists all of the Call Processor tables that are used for configuration. Use the command with a table name as a parameter to view details of that table.
  • Page 339 CLI Command Descriptions...
  • Page 340 NDEX VCX configurations batch mode Accounting service user-MAC command adding to the Call Records service besbulkload.pl deleting from a group branch offices editing information in a group verifying replication listing logging maintenance starting cache stopping clearing for Tomcat view status Call Detail Record See CDR viewing details Call Processor service...
  • Page 341 vcx-licenseinstall single-site vcx-licensequery version 7.1.y to version 7.1.x vcx-listversions multi-site vcx-os-query single-site vcx-os-switch vcx-reconfigure vcx-showconfigtype vcx-showmachineid eml_client.out vcx-ups-setup monitoring vcx-ups-status enabling Common Agent service Accounting service groups restarting message tracing starting server logging stopping SNMP support configuration options exporting hardware all tables software single table...
  • Page 342 HAPTER NDEX stopping configuring for IP Telephony and IP Messaging IP Telephony and IP Messaging Server server configuring replication configuring for IP Telephony server IP Telephony Server configuring region to region configuring replication manually configuring region to region multi-master described verifying replication errors license keys...
  • Page 343 Authentication and Directory service multiple configuration Call Processor service master Common Agent service options IP Messaging service slave SIP Phone downloader service overview Super CDRs power event responses managing requirements viewing set up during upgrade setup guidelines setup options single configuration table data master exporting...
  • Page 344 HAPTER NDEX determining location (IP address) VCX system filename guidelines hardware components configuration options maintenance tasks overview software components configuration options vcx-assemble command vcx-config-backup command overview vcx-config-network command vcx-config-restore command overview vcx-config-services command vcx-install command to install a codec vcx-licenseinstall command vcx-licensequery command vcx-listversions command vcx-os-query command...

Table of Contents