Cisco Unified MeetingPlace, Release 7.0 -- Command Reference
From DocWiki
m (→Table: Command Reference: Database Replication Commands) |
|||
| Line 1: | Line 1: | ||
| - | {{Template:Required Metadata}} | + | {{Template:Required Metadata}} '''Main page:''' [[Cisco Unified MeetingPlace, Release 7.0]] |
| - | '''Main page:''' | + | |
| - | '''Up one level:''' | + | '''Up one level:''' [[Cisco Unified MeetingPlace, Release 7.0 -- Reference Information|Reference Information]] |
| + | <br> | ||
| + | <br> | ||
| + | == Command Syntax Conventions == | ||
| + | '''CAUTION : The CLI is a diagnostic interface designed to perform diagnostic and operational tasks and functions, and is not designed for use as a persistent operating environment monitoring tool. If you need to perform persistent continuous monitoring please consult Cisco TAC or your Cisco Professional Services partners for further guidance. '''<br> | ||
| - | + | This document uses these command syntax conventions. | |
| + | <br> | ||
| - | + | {| border="1" | |
| - | + | ||
| - | + | ||
| - | {| border = 1 | + | |
|- | |- | ||
| - | !Convention | + | ! Convention |
| - | !Description | + | ! Description |
|- | |- | ||
| - | | | + | | |
| - | + | ||
'''bold''' | '''bold''' | ||
| - | |||
| + | | | ||
Bold text indicates commands and parameters that you enter as shown. | Bold text indicates commands and parameters that you enter as shown. | ||
| + | |||
|- | |- | ||
| - | | | + | | |
| - | + | ||
''italic'' | ''italic'' | ||
| - | |||
| + | | | ||
Italic text indicates parameters for which you supply values. | Italic text indicates parameters for which you supply values. | ||
| + | |||
|- | |- | ||
| - | | | + | | |
| + | <x> | ||
| - | + | | | |
| - | | | + | Angle brackets enclose a parameter for which you supply values. This is typically used instead of italic text when there is no space between adjacent parameters. |
| - | |||
|- | |- | ||
| - | | | + | | |
| - | + | [x] | |
| - | [x] | + | |
| - | + | ||
| + | | | ||
Square brackets enclose an optional parameter. | Square brackets enclose an optional parameter. | ||
| + | |||
|- | |- | ||
| - | | | + | | |
| - | <nowiki> | </nowiki> | + | <nowiki> | </nowiki> |
| - | + | ||
| + | | | ||
A vertical line, called a pipe, indicates a choice within a set of parameters. | A vertical line, called a pipe, indicates a choice within a set of parameters. | ||
| + | |||
|- | |- | ||
| - | | | + | | |
| - | + | [x | y] | |
| - | [x | + | |
| - | + | ||
| + | | | ||
Square brackets enclosing parameters separated by a pipe indicate an optional choice. | Square brackets enclosing parameters separated by a pipe indicate an optional choice. | ||
| + | |||
|- | |- | ||
| - | | | + | | |
| - | + | {x | y} | |
| - | {x | + | |
| - | + | ||
| + | | | ||
Braces enclosing parameters separated by a pipe indicate a required choice. | Braces enclosing parameters separated by a pipe indicate a required choice. | ||
| + | |||
|- | |- | ||
| - | | | + | | |
| - | + | [x {y | z}] | |
| - | [x {y | + | |
| - | + | ||
| + | | | ||
Braces and a pipe within square brackets indicate a required choice within an optional element. | Braces and a pipe within square brackets indicate a required choice within an optional element. | ||
| + | |||
|} | |} | ||
| + | <br> | ||
| + | <br> | ||
| + | == Application Commands == | ||
| + | ===== Table: Command Reference: Application Commands ===== | ||
| - | + | {| border="1" | |
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | {| border = 1 | + | |
|- | |- | ||
| - | !Command | + | ! Command |
| - | !Description | + | ! Description |
|- | |- | ||
| - | | | + | | |
| - | + | activity | |
| - | activity | + | |
| - | + | ||
| - | Displays a quick, verbose, or complete status of all ports or a range of ports. Allows you to make a test call and show all meetings. | + | | |
| + | Displays a quick, verbose, or complete status of all ports or a range of ports. Allows you to make a test call and show all meetings. | ||
| + | <br> Syntax: '''activity''' | ||
| - | |||
|- | |- | ||
| - | | | + | | |
| + | alarm | ||
| - | + | | | |
| - | | | + | Displays the [[Cisco Unified MeetingPlace, Release 7.0 -- About Alarms#Alarm_Table|Alarm Table]]: |
| - | + | *REFNO -- Reference number used with the [[Cisco Unified MeetingPlace, Release 7.0 -- Command Reference#clearalarm|clearalarm]] command to clear a specific alarm table entry. | |
| - | * REFNO -- Reference number used with the [[Cisco Unified MeetingPlace, Release 7.0 -- Command Reference#clearalarm|clearalarm]] command to clear a specific alarm table entry. | + | *SEV -- Severity, either major (MAJ) or minor (MIN). See [[Cisco Unified MeetingPlace, Release 7.0 -- About Alarms#Alarm_Severity_Levels|Alarm Severity Levels]] in the [[Cisco Unified MeetingPlace, Release 7.0 -- Using Alarms and Logs on Cisco Unified MeetingPlace#Using_Alarms_and_Logs_on_Cisco_Unified_MeetingPlace|Using Alarms and Logs on Cisco Unified MeetingPlace]] module. |
| - | * SEV -- Severity, either major (MAJ) or minor (MIN). See [[Cisco Unified MeetingPlace, Release 7.0 -- About Alarms# | + | *CODE -- See [[Cisco Unified MeetingPlace, Release 7.0 -- Alarms Page#Code|Code]]. |
| - | * CODE -- See [[Cisco Unified MeetingPlace, Release 7.0 -- Alarms Page#Code|Code]]. | + | *COUNT -- See [[Cisco Unified MeetingPlace, Release 7.0 -- Alarms Page#Count|Count]]. |
| - | * COUNT -- See [[Cisco Unified MeetingPlace, Release 7.0 -- Alarms Page#Count|Count]]. | + | *FIRST -- See [[Cisco Unified MeetingPlace, Release 7.0 -- Alarms Page#First_Time|First Time]]. |
| - | * FIRST -- See [[Cisco Unified MeetingPlace, Release 7.0 -- Alarms Page# | + | *LAST -- See [[Cisco Unified MeetingPlace, Release 7.0 -- Alarms Page#Last_Time|Last Time]]. |
| - | * LAST -- See [[Cisco Unified MeetingPlace, Release 7.0 -- Alarms Page# | + | *UNIT -- See [[Cisco Unified MeetingPlace, Release 7.0 -- Alarms Page#Unit|Unit]]. |
| - | * UNIT -- See [[Cisco Unified MeetingPlace, Release 7.0 -- Alarms Page#Unit|Unit]]. | + | *SW MODULE -- See [[Cisco Unified MeetingPlace, Release 7.0 -- Alarms Page#Software_Module|Software Module]]. |
| - | * SW MODULE -- See [[Cisco Unified MeetingPlace, Release 7.0 -- Alarms Page# | + | |
| - | '''Note: ''' The brief description in the alarm table entry may contain values that are specific to one alarm occurrence, such as an IP address. These values may differ in all alarms that are combined into one table entry, but only the values for the ''first'' alarm are displayed. To see the individual alarms, use the [[Cisco Unified MeetingPlace, Release 7.0 -- Command Reference#errorlog|errorlog]] command or the [[Cisco Unified MeetingPlace, Release 7.0 -- Command Reference#viewexlog|viewexlog]] command. | + | '''Note: ''' The brief description in the alarm table entry may contain values that are specific to one alarm occurrence, such as an IP address. These values may differ in all alarms that are combined into one table entry, but only the values for the ''first'' alarm are displayed. To see the individual alarms, use the [[Cisco Unified MeetingPlace, Release 7.0 -- Command Reference#errorlog|errorlog]] command or the [[Cisco Unified MeetingPlace, Release 7.0 -- Command Reference#viewexlog|viewexlog]] command. |
| + | <br> Syntax: '''alarm''' | ||
| - | |||
|- | |- | ||
| - | | | + | | |
| + | checklic | ||
| - | + | | | |
| - | | | + | Shows the type and number of licenses installed. |
| - | + | '''Note: ''' The system may take up to 15 seconds to process this information. | |
| - | ''' | + | <br> Syntax: '''checklic''' |
| - | |||
| - | |||
|- | |- | ||
| - | | | + | | |
| + | clearalarm | ||
| - | + | | | |
| - | | | + | Clears either all the alarms in the alarm table or just the alarm specified. |
| - | + | <br> If there are any major alarms in the alarm table, the system can be configured to call the system administrator after every restart until all major alarms are deleted from the alarm table. See [[Cisco Unified MeetingPlace, Release 7.0 -- Configuring the System to Call You if There is a Major Alarm#Configuring_the_System_to_Call_You_if_There_is_a_Major_Alarm|Configuring the System to Call You if There is a Major Alarm]]. | |
| + | <br> Running this command stops the system from calling the system administrator (if it has been configured to do so). | ||
| - | + | <br> Syntax: '''clearalarm''' {''reference-number'' | '''all'''} | |
| - | |||
| - | |||
| - | |||
| - | |||
| - | |||
|- | |- | ||
| + | | | ||
| + | cleardb | ||
| + | | | ||
| + | Clears the following Application Server data: | ||
| - | |||
| - | |||
| - | |||
| - | |||
| - | |||
| - | |||
*All user profiles except the admin and guest user profiles | *All user profiles except the admin and guest user profiles | ||
*All user groups except the System group | *All user groups except the System group | ||
*All user recordings | *All user recordings | ||
| - | *All conference recordings | + | *All conference recordings |
You must be signed in to the Application Server CLI as the root user to enter this command. | You must be signed in to the Application Server CLI as the root user to enter this command. | ||
| - | Use this command for specific situations; as instructed in the documentation or as recommended by Cisco TAC. It first clears the database, then restarts all Cisco Unified MeetingPlace services. | + | Use this command for specific situations; as instructed in the documentation or as recommended by Cisco TAC. It first clears the database, then restarts all Cisco Unified MeetingPlace services. Upon restarting, ConfSchd service executes a ConfSchd db table rebuild to clean up other dependent tables. When the ConfSchd db table rebuild is completed and all other MeetingPlace services are up, then the prompt returns. |
| - | '''Note:''' If the Application Server is in a failover or in a RSNA deployment, then turn off replication before running this command. Be sure that the Application Server is in active mode before running this command. | + | '''Note:''' If the Application Server is in a failover or in a RSNA deployment, then turn off replication before running this command. Be sure that the Application Server is in active mode before running this command. |
| - | Syntax: '''cleardb''' | + | Syntax: '''cleardb''' |
|- | |- | ||
| + | | | ||
| + | cpstatus | ||
| + | | | ||
| + | Displays information about each active call, including the associated meeting ID, whether the system dialed out to the endpoint, and whether the call uses video. | ||
| + | <br> Syntax: '''cpstatus''' | ||
| - | |||
| - | |||
| - | |||
| - | |||
| - | |||
| - | |||
| - | |||
| - | |||
| - | |||
|- | |- | ||
| - | | | + | | |
| + | cptrace | ||
| - | + | | | |
| - | | | + | Lists selected portions of the call processing trace log. |
| - | + | <br> Syntax: '''cptrace''' | |
| - | |||
| - | |||
|- | |- | ||
| - | | | + | | |
| + | date | ||
| - | + | | | |
| - | | | + | Displays the time and date for the Application Server. |
| - | + | <br> If you are logged in as a root user, then you can also set the date and time based on the local time zone. | |
| + | <br> Syntax: '''date''' [''MMDDhhmm''[''YYYY'']['''.'''''ss'']] | ||
| - | + | <br> Parameters (available only to root users): | |
| + | *''MM'' -- month, specified by two digits | ||
| + | *''DD'' -- day, specified by two digits | ||
| + | *''hh'' -- hour, specified by two digits in 24-hour format | ||
| + | *''mm'' -- minute, specified by two digits | ||
| + | *''YYYY'' -- calendar year, specified by four digits | ||
| + | *'''.'''''ss'' -- second, specified by two digits and a preceding period (.) | ||
| - | + | |- | |
| + | | | ||
| + | dbupdate | ||
| + | | | ||
| + | Deletes all entries in the Cisco Unified MeetingPlace database, so that the database is the equivalent of that in a newly installed Cisco Unified MeetingPlace system. This means that all user groups, user profiles, video terminal profiles, remote servers, meeting categories, and all meeting records are deleted from the system except the standard, preconfigured items, such as the System user group. | ||
| - | + | '''Caution! ''' Deleting all database entries is an irreversible operation. Before you run the [[Cisco Unified MeetingPlace, Release 7.0 -- Command Reference#dbupdate|dbupdate]] command, consider backing up and archiving the database. See [[Cisco Unified MeetingPlace, Release 7.0 -- Backing Up, Archiving, and Restoring Data on the Cisco Unified MeetingPlace Application Server|Backing Up, Archiving, and Restoring Data on the Cisco Unified MeetingPlace Application Server]]. | |
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | <br> Use this command only in the following situations: | |
| - | + | ||
| - | + | *Cisco TAC instructs you to do so. | |
| + | *You configured Directory Service on your system, and you need to change the LDAP directory with which Cisco Unified Communications Manager is integrated. If you do not clear the database before switching from one LDAP directory to another, then all the user profiles from the first LDAP directory will remain in the Cisco Unified MeetingPlace database until you manually delete them. | ||
| - | + | :The automatic Directory Service deletion of user profiles does not apply when you change the LDAP directory. For details about when and how the system automatically deletes Directory Service user profiles, see [[Cisco Unified MeetingPlace, Release 7.0 -- About Directory Service#Directory_Service_User_Profile_Deletion|Directory Service User Profile Deletion]]. | |
| - | |||
| - | |||
| - | |||
| - | |||
| - | |||
|- | |- | ||
| - | | | + | | |
| + | errorlog | ||
| - | + | | | |
| - | | | + | Displays the [[Cisco Unified MeetingPlace, Release 7.0 -- About Alarms#Exception_Log|Exception Log]] output one screen at a time: |
| - | + | *Date of the event | |
| - | * Date of the event | + | *Time of the event |
| - | * Time of the event | + | *Severity (major, minor, informational, or warning) |
| - | * Severity (major, minor, informational, or warning) | + | *Exception code |
| - | * Exception code | + | *Brief description |
| - | * Brief description | + | |
| + | <br> In contrast, the [[Cisco Unified MeetingPlace, Release 7.0 -- Command Reference#viewexlog|viewexlog]] command provides the entire [[Cisco Unified MeetingPlace, Release 7.0 -- About Alarms#Exception_Log|Exception Log]] output all at once. | ||
| - | + | <br> Syntax: '''errorlog''' | |
| - | |||
| - | |||
|- | |- | ||
| - | | | + | | |
| + | eventlog | ||
| - | + | | | |
| - | | | + | Displays the system event log. |
| - | + | '''Note: ''' This command has many parameter options; only the most commonly used parameters are listed below. | |
| - | ''' | + | <br> Syntax: '''eventlog''' ['''-b''' [''YY''][''MMDD'']''hhmm''] ['''-e''' [''YY''][''MMDD'']''hhmm''] ['''-G''' | '''-C'''] ['''-t'''] ['''| more'''] |
| + | <br> Parameters: | ||
| - | + | *'''-b''' -- Specifies a start time for the log events to include in the output. | |
| + | *'''-e''' -- Specifies an end time for the log events to include in the output. | ||
| + | '''Note: ''' To show events for the current day, you may omit the ''YY'', ''MM'', and ''DD'' parameters from the start and end times. | ||
| - | + | *''YY'' -- Calendar year, specified by two digits. Typically, this parameter is included only when troubleshooting issues around the start of a new calendar year. | |
| - | * '''- | + | *''MM'' -- month, specified by two digits |
| - | * '''- | + | *''DD'' -- day, specified by two digits |
| + | *''hh'' -- hour, specified by two digits in 24-hour format | ||
| + | *''mm'' -- minute, specified by two digits | ||
| + | *'''-G''' -- Shows the telephony and conference events and control messages from the Call Processing-Media Control Protocol (CPMCP) component, which is a proxy for the Media Server. | ||
| + | *'''-C''' -- Limits log output to events for the conference scheduler (ConfSchd) component. | ||
| + | *'''-t''' -- Displays the log output in real time. This option is useful for troubleshooting issues in real time. For example, you can enter '''eventlog -G -t''' and then place a test call to the system to see how the system responds to the incoming call and to any subsequent user input. | ||
| + | *'''| more''' -- Displays the log output one screen at a time. | ||
| - | |||
| - | |||
| - | |||
| - | |||
| - | |||
| - | |||
| - | |||
| - | |||
| - | |||
| - | |||
|- | |- | ||
| - | | | + | | |
| + | exc | ||
| - | + | | | |
| - | | | + | Displays the meaning of an exception code that was listed in the [[Cisco Unified MeetingPlace, Release 7.0 -- Command Reference#errorlog|errorlog]] or [[Cisco Unified MeetingPlace, Release 7.0 -- Command Reference#viewexlog|viewexlog]] command output. |
| - | + | <br> Syntax: '''exc''' ['''-v'''] ''exception-code'' | |
| - | |||
| - | |||
|- | |- | ||
| - | | | + | | |
| - | + | hostname | |
| - | hostname | + | |
| - | + | ||
| + | | | ||
Displays the hostname of the Application Server. | Displays the hostname of the Application Server. | ||
| + | <br> Syntax: '''hostname''' | ||
| - | |||
|- | |- | ||
| - | | | + | | |
| + | infocap | ||
| - | + | | | |
| - | | | + | Captures configuration details and logs from the system for a particular time period. The output file is a zip file that is stored in the /tmp directory. The system gives the exact location after compiling the information. |
| - | + | <br> Restrictions: | |
| + | *You must be logged in as the root user to run this command. | ||
| + | *You can also get this information by completing [[Cisco Unified MeetingPlace, Release 7.0 -- Obtaining and Viewing the System Information Capture (Infocap) Log#Obtaining_and_Viewing_the_System_Information_Capture_.28Infocap.29_Log|Obtaining and Viewing the System Information Capture (Infocap) Log]]. Use this command only if you are unable to get the information from the Cisco Unified MeetingPlace Administration Center. | ||
| + | *The begin and end dates and times must be in the format [YY]MMDDhhmm. The YY is optional and if not specified, the system uses the current year. For format details, see the parameters for the [[Cisco Unified MeetingPlace, Release 7.0 -- Command Reference#date|date]] command. | ||
| - | + | <br> Syntax: '''infocap -b''' ''begin-date-and-time'' '''-e''' ''end-date-and-time'' | |
| - | + | ||
| - | + | ||
| - | + | ||
| - | |||
| - | |||
|- | |- | ||
| - | | | + | | |
| + | langinfo | ||
| - | + | | | |
| - | | | + | Displays information about all installed locales including the following: |
| - | + | *Locale ID | |
| - | * Locale ID | + | *Language code |
| - | * Language code | + | *Locale order |
| - | * Locale order | + | *Locale name |
| - | * Locale name | + | *Country code |
| - | * Country code | + | *Locale version number |
| - | * Locale version number | + | |
| + | <br> Syntax: '''langinfo''' | ||
| - | |||
|- | |- | ||
| - | | | + | | |
| - | + | ||
mtginfo | mtginfo | ||
| - | |||
| - | Displays information about a specific meeting. Searches for a meeting based on any of these: | + | | |
| - | + | Displays information about a specific meeting. Searches for a meeting based on any of these: | |
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| + | *Unique conference ID (such as 125). (This number is output by certain commands such as '''cptrace -C''' and '''errorlog'''. It uniquely identifies a meeting.) | ||
| + | *Meeting ID (such as 1278). Can optionally use any of the time arguments. | ||
| + | *Unique user ID (such as 0x65). (This number is output by certain commands such as [[Cisco Unified MeetingPlace, Release 7.0 -- Command Reference#userinfo|userinfo]]. It uniquely identifies a user.) Searches for all meetings that a user has attended or been invited to. | ||
| + | *Activity. Searches only for active meetings. | ||
| + | *Time. Searches for all meetings valid at a certain time with the -t argument or between two times when the -s and -e arguments are used together. | ||
| - | Syntax: '''mtginfo''' '''-a''' | + | <br> Syntax: '''mtginfo''' '''-a''' ''time'' '''-c''' ''unique-conf-id'' '''-e''' ''end-time'' '''-m''' ''meeting-id'' '''-s''' ''start-time'' '''-t''' ''time'' '''-u''' ''unique-user-id'' |
| - | '''Note: ''' The start and end times must be in the format YYMMDDhhmm. All parameters are optional. If they are not all present, the system starts processing from the right. For format details, see the parameters for the [[Cisco Unified MeetingPlace, Release 7.0 -- Command Reference#date|date]] command. | + | '''Note: ''' The start and end times must be in the format YYMMDDhhmm. All parameters are optional. If they are not all present, the system starts processing from the right. For format details, see the parameters for the [[Cisco Unified MeetingPlace, Release 7.0 -- Command Reference#date|date]] command. |
| - | '''Note: ''' Start and end times in the command output are adjusted for the [[Cisco Unified MeetingPlace, Release 7.0 -- Meeting Configuration Page# | + | '''Note: ''' Start and end times in the command output are adjusted for the [[Cisco Unified MeetingPlace, Release 7.0 -- Meeting Configuration Page#Meeting_ID_start_guard_time_.28minutes.29|Meeting ID start guard time (minutes)]] and [[Cisco Unified MeetingPlace, Release 7.0 -- Meeting Configuration Page#Meeting_ID_end_guard_time_.28minutes.29|Meeting ID end guard time (minutes)]] fields on the [[Cisco Unified MeetingPlace, Release 7.0 -- Meeting Configuration Page#Meeting_Configuration_Page|Meeting Configuration Page]]. |
| + | <br> Examples: | ||
| - | + | <br> '''mtginfo -m 1234 '''Looks for the meeting with the ID of 1234 at the current time | |
| + | <br> '''mtginfo -m 1234 -t 11 '''Looks for meeting with the ID of 1234 at 11 minutes after the current hour | ||
| - | '''mtginfo -m 1234 '''Looks for | + | <br> '''mtginfo -m 1234 -t 1111111111 '''Looks for meeting with the ID of 1234 at 11:11am on Nov 11, 2011 |
| + | <br> '''mtginfo -a 1430 '''Looks for meetings that are active at 2:30pm today | ||
| - | '''mtginfo - | + | <br> '''mtginfo -s 1430 -e 1530 '''Looks for meetings that started or ended between 2:30 and 3:30pm today |
| + | <br> '''mtginfo -c 123 '''Looks for meeting with the unique conference ID of 123 | ||
| - | '''mtginfo - | + | <br> '''mtginfo -u 123 -t 1111 -e 1211 '''Looks for meetings that the user with the unique user ID of 123 is invited to between 11:11 and 12:11 today |
| - | |||
| - | |||
| - | |||
| - | |||
| - | |||
| - | |||
| - | |||
| - | |||
| - | |||
| - | |||
| - | |||
|- | |- | ||
| - | | | + | | |
| + | net | ||
| - | + | | | |
| - | | | + | Lists the current network configuration settings and allows you to change them after the system has been installed. Most changes take affect after restarting the system. |
| - | + | '''Caution! ''' A system restart terminates all existing call connections. Proceed only during a scheduled maintenance period or during a period of extremely low usage. '''NOTE:''' When you restart the Web Server, all manual changes made to the registry are lost. | |
| - | + | <br> | |
| - | + | ||
| + | Use the '''net''' command to set the following: | ||
| + | *Port configuration parameters, including: | ||
| + | **Application Server (eth0) hostname, IP address, subnet mask, and default gateway | ||
| + | **Virtual (eth0:0) hostname, IP address, subnet mask, and default gateway-the eth0:0 virtual interface is used in [[Cisco Unified MeetingPlace, Release 7.0 -- Application Server Failover#Application_Server_Failover|Application Server Failover]] deployments | ||
| + | **MTU and link parameters (auto-negotiation, speed, duplex). | ||
| - | + | *Domain name | |
| - | * | + | *DNS servers |
| - | + | ||
| - | + | ||
| - | + | ||
| - | * | + | *NTP servers |
| + | *:'''Note: ''' If you change the Application Server hostname (for eth0), then you must also perform the following actions: | ||
| + | **Configure the DNS server to point the old hostname to the new hostname. | ||
| + | **Restart the application by entering either the [[Cisco Unified MeetingPlace, Release 7.0 -- Command Reference#mpx_sys|mpx_sys]] '''restart''' operating system command or the '''reboot''' Linux command. '''NOTE:''' When you restart the Web Server, all manual changes made to the registry are lost. | ||
| + | **If you enabled SSL for the Application Server, complete [[Cisco Unified MeetingPlace, Release 7.0 -- Generating a Certificate Signing Request and Obtaining the Certificate|Generating a Certificate Signing Request and Obtaining the Certificate]] and [[Cisco Unified MeetingPlace, Release 7.0 -- Uploading the Certificate File and Enabling SSL|Uploading the Certificate File and Enabling SSL]]. | ||
| + | **If you installed MeetingPlace Conference Manager, complete [[Cisco Unified MeetingPlace, Release 7.0 -- How to Add, Edit, or Remove a Server#Editing_an_Existing_Server|Editing an Existing Server]]. | ||
| + | **If your system includes a Web Server, complete [[Cisco Unified MeetingPlace, Release 7.0 -- Changing the Cisco Unified MeetingPlace Application Server Connection Configured in the Gateway SIM|Changing the Cisco Unified MeetingPlace Application Server Connection Configured in the Gateway SIM]] . | ||
| + | **If you integrated the system with Cisco WebEx, notify the Cisco WebEx administrator to update the Cisco Unified MeetingPlace hostname that is configured in the Cisco WebEx license manager. | ||
| - | + | <br> Syntax: '''net''' | |
| - | |||
| - | |||
| - | |||
| - | |||
| - | |||
| - | |||
| - | |||
| - | |||
| - | |||
| - | |||
| - | |||
|- | |- | ||
| - | | | + | | |
| - | + | ntpdate | |
| - | ntpdate | + | |
| - | + | ||
| + | | | ||
Sets the Application Server date and time to match the time obtained by polling an NTP server. | Sets the Application Server date and time to match the time obtained by polling an NTP server. | ||
| + | <br> Syntax: '''ntpdate''' ['''-u'''] ''ntp-server'' | ||
| - | + | <br> Parameters: | |
| + | *'''-u''' -- Specifies to send packets through an unprivileged port to communicate with the NTP server. Use this option when you want to reach an NTP server that is beyond a firewall. | ||
| + | *''ntp-server'' -- Hostname or IP address of the NTP server. | ||
| - | |||
| - | |||
| - | |||
|- | |- | ||
| - | | | + | | |
| + | swstatus | ||
| - | + | | | |
| - | | | + | Displays information about Cisco Unified MeetingPlace, including the following: |
| - | + | *Version number | |
| - | * Version number | + | *System mode |
| - | * System mode | + | *Status of the power supplies |
| - | * Status of the power supplies | + | *List of software modules loaded in to memory, their version number, and their status |
| - | * List of software modules loaded in to memory, their version number, and their status | + | |
| + | <br> Syntax: '''swstatus''' | ||
| - | |||
|- | |- | ||
| - | | | + | | |
| - | + | techui | |
| - | techui | + | |
| - | + | ||
| + | | | ||
Displays statistics for the Media Server, ports, and conferences. | Displays statistics for the Media Server, ports, and conferences. | ||
| + | <br> This technician user interface helps to diagnose and troubleshoot media and voice quality issues of active calls. | ||
| - | + | <br> Syntax: '''techui''' | |
| - | |||
| - | |||
|- | |- | ||
| - | | | + | | |
| + | userinfo | ||
| - | + | | | |
| - | | | + | Displays information about a specific user. Searches for a user based on any of these: |
| - | + | *[[Cisco Unified MeetingPlace, Release 7.0 -- Add User Profile Page#User_ID|User ID]] | |
| - | * [[Cisco Unified MeetingPlace, Release 7.0 -- Add User Profile Page# | + | *[[Cisco Unified MeetingPlace, Release 7.0 -- Add User Profile Page#Profile_number|Profile number]] |
| - | * [[Cisco Unified MeetingPlace, Release 7.0 -- Add User Profile Page# | + | *Unique user ID (such as 0x65). The unique user ID is output by certain commands. It uniquely identifies a user but does not display the name of the user. |
| - | * Unique user ID (such as 0x65). The unique user ID is output by certain commands. It uniquely identifies a user but does not display the name of the user. | + | |
| + | <br> Syntax: '''userinfo''' {''user-id'' | ''profile-number'' | ''unique-user-id''} | ||
| - | |||
|- | |- | ||
| - | | | + | | |
| - | + | userutil | |
| - | userutil | + | |
| - | + | ||
| - | + | ||
| - | + | ||
| + | | | ||
| + | Performs administrative functions for any user profile. | ||
| - | Restriction: You cannot set the admin user to inactive, locked, or the group default. | + | <br> Restriction: You cannot set the admin user to inactive, locked, or the group default. |
| + | <br> Syntax: '''userutil''' {'''-q''' | ['''-p''' | '''-P] '''['''-n''' | '''-N] '''['''-a''' | '''-i''' | '''-l''' | '''-g]'''} ''userid'' [''password''] | ||
| - | + | <br> Parameters: | |
| + | *'''-q''' -- Displays user profile information and status. | ||
| + | *'''-p''' -- Reset the [[Cisco Unified MeetingPlace, Release 7.0 -- Add User Profile Page#User_password|User password]]. Requires a ''password'' entry. | ||
| + | *'''-P''' -- Reset the [[Cisco Unified MeetingPlace, Release 7.0 -- Add User Profile Page#User_password|User password]] and force it to expire. Requires a ''password'' entry. | ||
| + | *'''-n''' -- Reset the [[Cisco Unified MeetingPlace, Release 7.0 -- Billing Report Page#Profile_password|Profile password]] (PIN for authentication over the phone). Requires a ''password'' entry. | ||
| + | *'''-N''' -- Reset the [[Cisco Unified MeetingPlace, Release 7.0 -- Billing Report Page#Profile_password|Profile password]] and force it to expire. Requires a ''password'' entry. | ||
| + | *'''-a''' -- Set [[Cisco Unified MeetingPlace, Release 7.0 -- Add User Profile Page#User_status|User status]] to active. | ||
| + | *'''-i''' -- Set [[Cisco Unified MeetingPlace, Release 7.0 -- Add User Profile Page#User_status|User status]] to inactive. | ||
| + | *'''-l''' -- Set [[Cisco Unified MeetingPlace, Release 7.0 -- Add User Profile Page#User_status|User status]] to locked. | ||
| + | *'''-g''' -- Set [[Cisco Unified MeetingPlace, Release 7.0 -- Add User Profile Page#User_status|User status]] to group default setting. | ||
| + | *''userid'' -- [[Cisco Unified MeetingPlace, Release 7.0 -- Add User Profile Page#User_ID|User ID]]. | ||
| + | *''pasword'' -- New [[Cisco Unified MeetingPlace, Release 7.0 -- Add User Profile Page#User_password|User password]] or [[Cisco Unified MeetingPlace, Release 7.0 -- Billing Report Page#Profile_password|Profile password]]. Required if you enter '''-p''', '''-P''', '''-n''', or '''-N'''. | ||
| - | |||
| - | |||
| - | |||
| - | |||
| - | |||
| - | |||
| - | |||
| - | |||
| - | |||
| - | |||
| - | |||
| - | |||
|- | |- | ||
| - | | | + | | |
| + | viewexlog | ||
| - | + | | | |
| - | | | + | Provides the entire [[Cisco Unified MeetingPlace, Release 7.0 -- About Alarms#Exception_Log|Exception Log]] output all at once: |
| - | + | *Date of the event | |
| - | * Date of the event | + | *Time of the event |
| - | * Time of the event | + | *Severity (major, minor, informational, or warning) |
| - | * Severity (major, minor, informational, or warning) | + | *Exception code |
| - | * Exception code | + | *Brief description |
| - | * Brief description | + | |
| + | <br> In contrast, the [[Cisco Unified MeetingPlace, Release 7.0 -- Command Reference#errorlog|errorlog]] command displays the [[Cisco Unified MeetingPlace, Release 7.0 -- About Alarms#Exception_Log|Exception Log]] output one screen at a time: | ||
| - | + | <br> Syntax: '''viewexlog''' | |
| - | |||
| - | |||
|} | |} | ||
| - | ===== Related Topics ===== | + | ===== Related Topics ===== |
| - | * [[Cisco Unified MeetingPlace, Release 7.0 -- Using Alarms and Logs on Cisco Unified MeetingPlace|Using Alarms and Logs on Cisco Unified MeetingPlace]] | + | *[[Cisco Unified MeetingPlace, Release 7.0 -- Using Alarms and Logs on Cisco Unified MeetingPlace|Using Alarms and Logs on Cisco Unified MeetingPlace]] |
| + | <br> | ||
| + | == Operating System Commands == | ||
| - | + | In addition to the Cisco Unified MeetingPlace commands listed in [[Cisco Unified MeetingPlace, Release 7.0 -- Command Reference#Table:_Command_Reference:_Operating_System_Commands|Table: Command Reference: Operating System Commands]], the CLI supports the standard Linux operating system commands. You can use the '''vim''' command to view or modify text files if necessary. | |
| - | + | <br> Note the following requirements and restrictions for operating system commands: | |
| + | *With the exception of the [[Cisco Unified MeetingPlace, Release 7.0 -- Command Reference#mpx_sys|mpx_sys]] command, use the operating system commands to start or stop services only when you have been explicitly told to do so by Cisco TAC. Use of these commands may cause unpredictable results. | ||
| - | + | *If you are not logged in as the [[Cisco Unified MeetingPlace, Release 7.0 -- CLI User Level Options#root|root]] user, you must enter '''sudo''' before you can run any of these commands. For example, to stop all application services, go to the command line and enter the following: | |
| - | + | :'''sudo ./mpx_app stop''' | |
| + | :The preceding example assumes that you are already in the /etc/init.d directory. If you are not in that directory, you instead enter the following: | ||
| + | :'''sudo /etc/init.d/mpx_app stop''' | ||
| - | * | + | *Existing call connections will not be terminated by stopping services on the Application Server. However, starting or restarting services will terminate those calls. This behavior applies: |
| - | + | **To the [[Cisco Unified MeetingPlace, Release 7.0 -- Command Reference#mpx_app|mpx_app]], [[Cisco Unified MeetingPlace, Release 7.0 -- Command Reference#mpx_sys|mpx_sys]], and [[Cisco Unified MeetingPlace, Release 7.0 -- Command Reference#mpx_va|mpx_va]] commands. | |
| - | + | **If the Application Server crashes and is reloaded. | |
| - | + | **If you enter the '''shutdown''' or '''reboot''' Linux command on the Application Server. | |
| - | + | <br> | |
| - | + | ||
| - | + | ||
| - | + | ||
| + | ===== Table: Command Reference: Operating System Commands ===== | ||
| - | + | {| border="1" | |
| - | + | ||
| - | {| border = 1 | + | |
|- | |- | ||
| - | !Command | + | ! Command |
| - | !Description | + | ! Description |
|- | |- | ||
| - | | | + | | |
| - | + | mpx_app | |
| - | mpx_app | + | |
| - | + | ||
| + | | | ||
Starts, stops, or restarts all Cisco Unified MeetingPlace application services. | Starts, stops, or restarts all Cisco Unified MeetingPlace application services. | ||
| - | '''NOTE:''' When you restart the Web Server, all manual changes made to the registry are lost. | + | '''NOTE:''' When you restart the Web Server, all manual changes made to the registry are lost. |
| + | <br> Syntax: '''mpx_app''' {'''start''' | '''stop''' | '''restart''' | '''status'''} ['''-v'''] | ||
| - | |||
|- | |- | ||
| - | | | + | | |
| + | mpx_axlds | ||
| - | + | | | |
| - | | | + | Starts, stops, or restarts Directory Service and external AXL authentication through Cisco Unified Communications Manager. |
| - | + | <br> Syntax: '''mpx_axlds''' {'''start''' | '''stop''' | '''restart''' | '''status'''} ['''-v'''] | |
| - | |||
| - | |||
|- | |- | ||
| - | | | + | | |
| + | mpx_db | ||
| - | + | | | |
| - | | | + | Starts, stops, or restarts Cisco Unified MeetingPlace database services. |
| - | + | <br> Syntax: '''mpx_db''' {'''start''' | '''stop''' | '''restart''' | '''status'''} ['''-v'''] | |
| - | |||
| - | |||
|- | |- | ||
| - | | | + | | |
| - | + | mpx_lm | |
| - | mpx_lm | + | |
| - | + | ||
| - | Starts, stops, or restarts Cisco Unified MeetingPlace license manager services. | + | | |
| + | Starts, stops, or restarts Cisco Unified MeetingPlace license manager services. | ||
| + | <br> Syntax: '''mpx_lm''' {'''start''' | '''stop''' | '''restart''' | '''status'''} ['''-v'''] | ||
| - | |||
|- | |- | ||
| - | | | + | | |
| + | mpx_rmi | ||
| - | + | | | |
| - | | | + | Starts, stops, or restarts messaging integration services for Cisco Unified MeetingPlace Click-to-Conference for IBM Lotus Sametime Instant Messaging. |
| - | + | <br> Syntax: '''mpx_rmi''' {'''start''' | '''stop''' | '''restart''' | '''status'''} ['''-v'''] | |
| - | |||
| - | |||
|- | |- | ||
| - | | | + | | |
| - | + | mpx_rssctrl | |
| - | mpx_rssctrl | + | |
| - | + | ||
| - | Starts, stops, or restarts the Cisco Unified MeetingPlace recording and streaming service. | + | | |
| + | Starts, stops, or restarts the Cisco Unified MeetingPlace recording and streaming service. | ||
| + | <br> Syntax: '''mpx_rssctrl''' {'''start''' | '''stop''' | '''restart''' | '''status'''} ['''-v'''] | ||
| - | |||
|- | |- | ||
| - | | | + | | |
| + | mpx_snmp | ||
| - | + | | | |
| - | | | + | Starts, stops, or restarts SNMP services. |
| - | + | <br> Syntax: '''mpx_snmp''' {'''start''' | '''stop''' | '''restart''' | '''status'''} ['''-v'''] | |
| - | |||
| - | |||
|- | |- | ||
| - | | | + | | |
| - | + | mpx_sys | |
| - | mpx_sys | + | |
| - | + | ||
| + | | | ||
Starts, stops, or restarts ''all'' Cisco Unified MeetingPlace services. | Starts, stops, or restarts ''all'' Cisco Unified MeetingPlace services. | ||
| - | '''Caution! ''' A system restart terminates all existing call connections. Proceed only during a scheduled maintenance period or during a period of extremely low usage. | + | '''Caution! ''' A system restart terminates all existing call connections. Proceed only during a scheduled maintenance period or during a period of extremely low usage. |
| - | '''NOTE:''' When you restart the Web Server, all manual changes made to the registry are lost. | + | '''NOTE:''' When you restart the Web Server, all manual changes made to the registry are lost. |
| + | <br> '''Note: ''' If the restart process is interrupted, you will have to reenter the '''mpx_sys restart''' command. For example, the restart process may be interrupted by a power outage, by closing the SSH connection, or by another restart process that is initiated from a different terminal. | ||
| - | ''' | + | <br> Syntax: '''mpx_sys''' {'''stop''' | '''restart''' | '''status'''} ['''-v'''] |
| - | |||
| - | |||
|- | |- | ||
| - | | | + | | |
| + | mpx_tomcat | ||
| - | + | | | |
| - | | | + | Starts, stops, or restarts Apache Tomcat services. |
| - | + | <br> Syntax: '''mpx_tomcat''' {'''start''' | '''stop''' | '''restart''' | '''status'''} ['''-v'''] | |
| - | |||
| - | |||
|- | |- | ||
| - | | | + | | |
| + | mpx_tomcatmon | ||
| - | + | | | |
| - | | | + | Starts, stops, or restarts Apache Tomcat monitoring services. |
| - | + | <br> Syntax: '''mpx_tomcatmon''' {'''start''' | '''stop''' | '''restart''' | '''status'''} ['''-v'''] | |
| - | |||
| - | |||
|- | |- | ||
| - | | | + | | |
| + | mpx_va | ||
| - | + | | | |
| - | | | + | Starts, stops, or restarts Media Server services on the Application Server. |
| - | + | <br> If all other Cisco Unified MeetingPlace services continue running, entering this command does ''not'' interrupt meetings that are in session. | |
| + | <br> Syntax: '''mpx_va''' {'''start''' | '''stop''' | '''restart''' | '''status'''} ['''-v'''] | ||
| - | |||
| - | |||
| - | |||
| - | |||
|- | |- | ||
| - | | | + | | |
| - | + | ||
mpx_version | mpx_version | ||
| - | |||
| + | | | ||
Lists all installed versions of Cisco Unified MeetingPlace. | Lists all installed versions of Cisco Unified MeetingPlace. | ||
| + | <br> Syntax: '''mpx_version ''' | ||
| - | |||
|- | |- | ||
| - | | | + | | |
| + | mpx_webx | ||
| - | + | | | |
| - | | | + | Starts, stops, or restarts all Cisco WebEx integration services on the Application Server. |
| - | + | <br> Syntax: '''mpx_webx''' {'''start''' | '''stop''' | '''restart''' | '''status'''} ['''-v'''] | |
| - | |||
| - | |||
|- | |- | ||
| - | | | + | | |
| + | resetmsapassword | ||
| - | + | | | |
| - | | | + | Resets the Media Server Administration password to "cisco". |
| - | + | <br> Syntax: '''resetmsapassword''' | |
| - | |||
| - | |||
|- | |- | ||
| - | | | + | | |
| - | + | shutdown | |
| - | shutdown | + | |
| - | + | ||
| - | + | ||
| - | + | ||
| + | | | ||
| + | Shuts down the Application Server. | ||
| - | For a graceful shutdown, we recommend that you enter the command using the syntax below. You can see which other options are available by entering '''shutdown''' without any parameters. | + | <br> For a graceful shutdown, we recommend that you enter the command using the syntax below. You can see which other options are available by entering '''shutdown''' without any parameters. |
| + | <br> Syntax: '''shutdown -h now''' | ||
| - | |||
|} | |} | ||
| - | ===== Related Topics ===== | + | ===== Related Topics ===== |
| - | * [[Cisco Unified MeetingPlace, Release 7.0 -- Configuring Application Server Failover for Cisco Unified MeetingPlace|Configuring Application Server Failover for Cisco Unified MeetingPlace]] | + | *[[Cisco Unified MeetingPlace, Release 7.0 -- Configuring Application Server Failover for Cisco Unified MeetingPlace|Configuring Application Server Failover for Cisco Unified MeetingPlace]] |
| - | * [[Cisco Unified MeetingPlace, Release 7.0 -- Changing the Media Server Administration Password|Changing the Media Server Administration Password]] | + | *[[Cisco Unified MeetingPlace, Release 7.0 -- Changing the Media Server Administration Password|Changing the Media Server Administration Password]] |
| + | <br> | ||
| + | == Database Replication Commands == | ||
| - | + | '''Note: ''' To enter the database replication commands in [[Cisco Unified MeetingPlace, Release 7.0 -- Command Reference#Table:_Command_Reference:_Database_Replication_Commands|Table: Command Reference: Database Replication Commands]]: | |
| - | + | *The MeetingPlace Database services must be running on the Application Server. | |
| - | * | + | *You must be logged in to the CLI as the [[Cisco Unified MeetingPlace, Release 7.0 -- CLI User Level Options#root|root]] user. |
| - | + | <br> The output messages from each command execution are displayed on the screen and stored in a log file under the directory $MP_LOGDIR/database/replication/logs. The log file names have the format mp_replication_log.<YYYY-MM-DD_hh-mm-ss>. | |
| + | <br> | ||
| - | + | ===== Table: Command Reference: Database Replication Commands ===== | |
| - | + | {| border="1" | |
| - | + | ||
| - | + | ||
| - | {| border = 1 | + | |
|- | |- | ||
| - | !Command | + | ! Command |
| - | !Description | + | ! Description |
|- | |- | ||
| - | | | + | | |
| + | mp_replication init | ||
| - | + | | | |
| - | | | + | Makes necessary changes in configuration files and database to enable the Application Server to use database replication. Run this command on each node involved in replication. |
| - | + | <br> Syntax: '''mp_replication init -s''' ''site'' '''-n''' ''node'' ['''-l''' ''local-server''] '''-r''' ''remote-server'' {'''-h''' | '''-m'''} ['''-v'''] | |
| + | <br> Parameters: | ||
| - | + | *'''-s''' ''site'' -- Specifies the site of the node on which you run this command. Valid values for ''site'' are 1 and 2. | |
| + | *'''-n''' ''node'' -- Specifies the node (within the specified site) on which you run the command. Valid values for ''node'' are 1 and 2. | ||
| + | *'''-l''' ''local-server'' -- (Optional) Specifies the hostname or IP address of the Application Server on which you run this command. | ||
| + | :For intra-site replication, which is used for [[Cisco Unified MeetingPlace, Release 7.0 -- Application Server Failover#Application_Server_Failover|Application Server Failover]], specify the hostname or IP address of the virtual network interface eth0:0. | ||
| + | :By default, the (eth0 hostname) value returned by the [[Cisco Unified MeetingPlace, Release 7.0 -- Command Reference#hostname|hostname]] command is used. | ||
| + | |||
| + | *'''-r''' ''remote-server'' -- Specifies the hostname or IP address of the other Application Server with which to establish replication. | ||
| + | *'''-h''' -- Specifies intra-site replication, which is used for replication between the active and standby Application Server in a single-site active/standby failover deployment. | ||
| + | *'''-m''' -- Specifies inter-site replication, which is used for replication between two singleServer mode Application Servers (i.e, site 1 and site 2) in Reservationless Single Number Access (RSNA) deployment. | ||
| + | *'''-v''' -- Specifies verbose output. | ||
| - | |||
| - | |||
| - | |||
| - | |||
| - | |||
| - | |||
| - | |||
| - | |||
| - | |||
| - | |||
|- | |- | ||
| - | | | + | | |
| - | + | mp_replication switchON | |
| - | mp_replication switchON | + | |
| - | + | ||
| + | | | ||
Starts replication between two Application Servers. | Starts replication between two Application Servers. | ||
| - | |||
| - | |||
| + | *Run this command on node 1 only. | ||
| + | *Run this command only after running the [[Cisco Unified MeetingPlace, Release 7.0 -- Command Reference#mp_replication_init|mp_replication init]] command on each node involved in replication. | ||
| - | Syntax: '''mp_replication switchON''' '''-r''' ''remote-server'' ['''-S''' '''-F''' ''data-source-server''] ['''-v'''] | + | <br> Syntax: '''mp_replication switchON''' '''-r''' ''remote-server'' ['''-S''' '''-F''' ''data-source-server''] ['''-v'''] |
| + | <br> Parameters: | ||
| - | + | *'''-r''' ''remote-server'' -- Specifies the hostname or IP address of the other Application Server with which to establish replication. | |
| - | * '''-r''' ''remote-server'' -- Specifies the hostname or IP address of the other Application Server with which to establish replication. | + | |
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | :For intra-site replication, which is used for Application Server failover, specify the hostname or IP address of the virtual network interface eth0:0. | |
| - | + | ||
| - | + | *'''-S''' '''-F''' ''data-source-server'' -- Indicates data synchronization between the two Application Servers. | |
| + | :'''NOTE:''' Both Application Servers must be in standby mode when the '''-S''' '''-F''' options are used. | ||
| + | :For intra-site replication, which is used for [[Cisco Unified MeetingPlace, Release 7.0 -- Application Server Failover#Application_Server_Failover|Application Server Failover]], specify the hostname or IP address of the virtual network interface eth0:0. | ||
| - | + | *'''-v''' -- Specifies verbose output. | |
| + | |- | ||
| + | | | ||
| + | mp_replication status | ||
| + | |||
| + | | | ||
| + | Displays the status of replication between the specified servers. | ||
| + | |||
| + | <br> Syntax: '''mp_replication status''' ['''-v'''] | ||
| + | |||
| + | <br> Parameter: '''-v'''-Specifies verbose output. | ||
| - | |||
|- | |- | ||
| - | | | + | | |
| + | mp_replication switchOFF | ||
| - | + | | | |
| - | | | + | Stops replication, but does not restore configuration changes. |
| - | + | *Run this command on node 1 only. | |
| - | * Run this command on node 1 only. | + | *To restart replication, use the [[Cisco Unified MeetingPlace, Release 7.0 -- Command Reference#mp_replication_switchON|mp_replication switchON]] command. |
| - | * To restart replication, use the [[Cisco Unified MeetingPlace, Release 7.0 -- Command Reference# | + | *To restore the configuration changes done by the [[Cisco Unified MeetingPlace, Release 7.0 -- Command Reference#mp_replication_init|mp_replication init]] command, use the [[Cisco Unified MeetingPlace, Release 7.0 -- Command Reference#mp_replication_teardown|mp_replication teardown]] command. |
| - | * To restore the configuration changes done by the [[Cisco Unified MeetingPlace, Release 7.0 -- Command Reference# | + | |
| + | <br> Syntax: '''mp_replication switchOFF''' ['''-l''' ''local-server''] '''-r''' ''remote-server'' ['''-v'''] ['''-f'''] | ||
| - | + | <br> Parameters: See the [[Cisco Unified MeetingPlace, Release 7.0 -- Command Reference#mp_replication_init|mp_replication init]] command. Exception: | |
| + | *'''-f''' -- Specifies to remove the local server from replication even in the following cases: | ||
| + | **Specified remote server is not part of replication. | ||
| + | **Local server is not in replication with any other servers. | ||
| - | |||
| - | |||
| - | |||
| - | |||
|- | |- | ||
| - | | | + | | |
| - | + | mp_replication teardown | |
| - | mp_replication teardown | + | |
| - | + | ||
| + | | | ||
Removes configuration changes made on the local server for replication with the specified remote server. Run this command on each node involved in replication to undo the configuration changes. | Removes configuration changes made on the local server for replication with the specified remote server. Run this command on each node involved in replication to undo the configuration changes. | ||
| + | <br> Syntax: '''mp_replication teardown''' ['''-l''' ''local-server''] '''-r''' ''remote-server'' ['''-v'''] ['''-f'''] | ||
| - | + | <br> Parameters: See the [[Cisco Unified MeetingPlace, Release 7.0 -- Command Reference#mp_replication_init|mp_replication init]] command. | |
| - | + | ||
| - | |||
|} | |} | ||
| - | ===== Related Topics ===== | + | ===== Related Topics ===== |
| - | * [[Cisco Unified MeetingPlace, Release 7.0 -- Configuring Cisco Unified MeetingPlace Directory Service|Configuring Cisco Unified MeetingPlace Directory Service]] | + | *[[Cisco Unified MeetingPlace, Release 7.0 -- Configuring Cisco Unified MeetingPlace Directory Service|Configuring Cisco Unified MeetingPlace Directory Service]] |
| - | * [[Cisco Unified MeetingPlace, Release 7.0 -- Configuring Application Server Failover for Cisco Unified MeetingPlace|Configuring Application Server Failover for Cisco Unified MeetingPlace]] | + | *[[Cisco Unified MeetingPlace, Release 7.0 -- Configuring Application Server Failover for Cisco Unified MeetingPlace|Configuring Application Server Failover for Cisco Unified MeetingPlace]] |
| + | <br> | ||
| + | == Failover Commands == | ||
| - | + | '''Note: ''' You must be logged in to the CLI as the [[Cisco Unified MeetingPlace, Release 7.0 -- CLI User Level Options#root|root]] user to enter the failover commands in [[Cisco Unified MeetingPlace, Release 7.0 -- Command Reference#Table:_Command_Reference:_Failover_Commands|Table: Command Reference: Failover Commands]]. | |
| - | + | <br> | |
| + | ===== Table: Command Reference: Failover Commands ===== | ||
| - | + | {| border="1" | |
| - | + | ||
| - | {| border = 1 | + | |
|- | |- | ||
| - | !Command | + | ! Command |
| - | !Description | + | ! Description |
|- | |- | ||
| - | | | + | | |
| + | failoverUtil copyConfigFiles | ||
| - | + | | | |
| - | | | + | Transfers configuration files from one Application Server to the other, specifically: |
| - | + | #Compresses the configuration files and user prompts on the local server. | |
| - | # Compresses the configuration files and user prompts on the local server. | + | #Transfers the compressed files to the remote server. |
| - | # Transfers the compressed files to the remote server. | + | |
| + | <br> After you enter this command on the local server, you need to enter the [[Cisco Unified MeetingPlace, Release 7.0 -- Command Reference#failoverUtil_restoreConfigFiles|failoverUtil restoreConfigFiles]] on the remote server. | ||
| - | + | <br> The following files and directories are transferred by this command: | |
| + | *Directory Service: | ||
| + | **/opt/cisco/meetingplace/axlds/current/etc/config.properties | ||
| + | *Recorded user names and custom voice prompts: | ||
| + | **Everything under /opt/cisco/meetingplace/afs/custom | ||
| + | *Microsoft Outlook integration files: | ||
| + | **Everything under /opt/cisco/meetingplace/var/outlook | ||
| + | **/opt/cisco/meetingplace/var/admin/outlook.config | ||
| + | **Everything under /opt/cisco/meetingplace/var/mail | ||
| + | *Cisco WebEx integration files: | ||
| + | **/opt/cisco/meetingplace/web/current/etc/conf/keyinfo.properties | ||
| + | **/opt/cisco/meetingplace/web/current/etc/conf/keystore.jks | ||
| + | **/opt/cisco/meetingplace/web/current/etc/conf/cert.cer | ||
| - | The following | + | <br> The script pauses to request your credentials. You must provide the following: |
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| + | *The remote machine's hostname or IP address | ||
| + | *The administrator’s username on the remote machine (the mpxadmin username) | ||
| + | *The mpxadmin password | ||
| - | + | <br> Syntax: '''failoverUtil copyConfigFiles''' | |
| - | + | ||
| - | + | ||
| - | + | ||
| - | |||
| - | |||
|- | |- | ||
| - | | | + | | |
| + | failoverUtil restoreConfigFiles | ||
| - | + | | | |
| - | | | + | Completes the transfer of configuration files from one Application Server to the other, specifically: |
| - | + | #Decompresses the configuration files and user prompts that were transferred from the remote server. | |
| - | # Decompresses the configuration files and user prompts that were transferred from the remote server. | + | #Places the transferred files into the correct directories, overwriting any existing local files with those from the remote server. |
| - | # Places the transferred files into the correct directories, overwriting any existing local files with those from the remote server. | + | |
| - | '''Note: ''' The [[Cisco Unified MeetingPlace, Release 7.0 -- Command Reference# | + | '''Note: ''' The [[Cisco Unified MeetingPlace, Release 7.0 -- Command Reference#failoverUtil_copyConfigFiles|failoverUtil copyConfigFiles]] and [[Cisco Unified MeetingPlace, Release 7.0 -- Command Reference#failoverUtil_restoreConfigFiles|failoverUtil restoreConfigFiles]] commands are entered on separate Application Servers. |
| + | <br> Syntax: '''failoverUtil restoreConfigFiles''' | ||
| - | |||
|- | |- | ||
| - | | | + | | |
| + | failoverUtil setDeployment failover | ||
| - | + | | | |
| - | | | + | Sets up an Application Server for failover deployment, including the configuration of the virtual network interface (eth0:0) hostname, IP address, subnet mask, and default gateway. |
| - | + | <br> Syntax: '''failoverUtil setDeployment failover''' | |
| - | |||
| - | |||
|- | |- | ||
| - | | | + | | |
| - | + | ||
failoverUtil setDeployment singleServer | failoverUtil setDeployment singleServer | ||
| - | |||
| - | Restores a failover-deployed Application Server to a single-server deployment. | + | | |
| + | Restores a failover-deployed Application Server to a single-server deployment. | ||
| + | <br> Syntax: '''failoverUtil setDeployment singleServer''' | ||
| - | |||
|- | |- | ||
| - | | | + | | |
| - | + | failoverUtil setServer | |
| - | failoverUtil setServer | + | |
| - | + | ||
| + | | | ||
Sets a failover-deployed Application Server to either active or standby mode. | Sets a failover-deployed Application Server to either active or standby mode. | ||
| + | <br> Enter this command only after running the [[Cisco Unified MeetingPlace, Release 7.0 -- Command Reference#failoverUtil_setDeployment_failover|failoverUtil setDeployment failover]] command on the server. | ||
| - | + | '''Note: ''' The mode setting may not be successful if this process is interrupted, for example, by a power outage, by closing the SSH connection, or by a system restart. To view the failover mode, log in to the Administration Center. If the wrong failover deployment mode appears at the top of the page, enter the [[Cisco Unified MeetingPlace, Release 7.0 -- Command Reference#mpx_sys|mpx_sys]] '''restart''' command, followed by the [[Cisco Unified MeetingPlace, Release 7.0 -- Command Reference#failoverUtil_setServer|failoverUtil setServer]] command. | |
| - | ''' | + | '''NOTE:''' When you restart the Web Server, all manual changes made to the registry are lost. |
| - | + | <br> | |
| + | Syntax: '''failoverUtil setServer''' {'''active''' | '''standby'''} | ||
| - | |||
| - | |||
|- | |- | ||
| - | | | + | | |
| - | + | ||
failoverUtil status | failoverUtil status | ||
| - | |||
| - | Displays the current modes of the Application Server, specifically: | + | | |
| - | + | Displays the current modes of the Application Server, specifically: | |
| - | + | ||
| + | *Whether the server is deployed for failover or as a single server. | ||
| + | *If deployed for failover, then whether the server is in active or standby mode. | ||
| + | |||
| + | <br> Syntax: '''failoverUtil status''' | ||
| - | |||
|} | |} | ||
| + | <br> | ||
| + | <br> | ||
| + | ===== Related Topics ===== | ||
| - | + | *[[Cisco Unified MeetingPlace, Release 7.0 -- Configuring Application Server Failover for Cisco Unified MeetingPlace|Configuring Application Server Failover for Cisco Unified MeetingPlace]] | |
| - | + | ||
| - | * [[Cisco Unified MeetingPlace, Release 7.0 -- Configuring Application Server Failover for Cisco Unified MeetingPlace|Configuring Application Server Failover for Cisco Unified MeetingPlace]] | + | |
| - | + | ||
| - | + | ||
| - | + | ||
| - | [[Category: | + | [[Category:Reference_Information_for_Cisco_Unified_MeetingPlace,_Release_7.0]] |
Latest revision as of 23:26, 10 April 2012
Main page: Cisco Unified MeetingPlace, Release 7.0
Up one level: Reference Information
Contents |
Command Syntax Conventions
CAUTION : The CLI is a diagnostic interface designed to perform diagnostic and operational tasks and functions, and is not designed for use as a persistent operating environment monitoring tool. If you need to perform persistent continuous monitoring please consult Cisco TAC or your Cisco Professional Services partners for further guidance.
This document uses these command syntax conventions.
| Convention | Description |
|---|---|
|
bold |
Bold text indicates commands and parameters that you enter as shown. |
|
italic |
Italic text indicates parameters for which you supply values. |
|
<x> |
Angle brackets enclose a parameter for which you supply values. This is typically used instead of italic text when there is no space between adjacent parameters. |
|
[x] |
Square brackets enclose an optional parameter. |
|
| |
A vertical line, called a pipe, indicates a choice within a set of parameters. |
|
[x | y] |
Square brackets enclosing parameters separated by a pipe indicate an optional choice. |
|
{x | y} |
Braces enclosing parameters separated by a pipe indicate a required choice. |
|
[x {y | z}] |
Braces and a pipe within square brackets indicate a required choice within an optional element. |
Application Commands
Table: Command Reference: Application Commands
| Command | Description |
|---|---|
|
activity |
Displays a quick, verbose, or complete status of all ports or a range of ports. Allows you to make a test call and show all meetings.
|
|
alarm |
Displays the Alarm Table:
Note: The brief description in the alarm table entry may contain values that are specific to one alarm occurrence, such as an IP address. These values may differ in all alarms that are combined into one table entry, but only the values for the first alarm are displayed. To see the individual alarms, use the errorlog command or the viewexlog command.
|
|
checklic |
Shows the type and number of licenses installed. Note: The system may take up to 15 seconds to process this information.
|
|
clearalarm |
Clears either all the alarms in the alarm table or just the alarm specified.
|
|
cleardb |
Clears the following Application Server data:
You must be signed in to the Application Server CLI as the root user to enter this command. Use this command for specific situations; as instructed in the documentation or as recommended by Cisco TAC. It first clears the database, then restarts all Cisco Unified MeetingPlace services. Upon restarting, ConfSchd service executes a ConfSchd db table rebuild to clean up other dependent tables. When the ConfSchd db table rebuild is completed and all other MeetingPlace services are up, then the prompt returns. Note: If the Application Server is in a failover or in a RSNA deployment, then turn off replication before running this command. Be sure that the Application Server is in active mode before running this command. Syntax: cleardb |
|
cpstatus |
Displays information about each active call, including the associated meeting ID, whether the system dialed out to the endpoint, and whether the call uses video.
|
|
cptrace |
Lists selected portions of the call processing trace log.
|
|
date |
Displays the time and date for the Application Server.
|
|
dbupdate |
Deletes all entries in the Cisco Unified MeetingPlace database, so that the database is the equivalent of that in a newly installed Cisco Unified MeetingPlace system. This means that all user groups, user profiles, video terminal profiles, remote servers, meeting categories, and all meeting records are deleted from the system except the standard, preconfigured items, such as the System user group. Caution! Deleting all database entries is an irreversible operation. Before you run the dbupdate command, consider backing up and archiving the database. See Backing Up, Archiving, and Restoring Data on the Cisco Unified MeetingPlace Application Server.
|
|
errorlog |
Displays the Exception Log output one screen at a time:
|
|
eventlog |
Displays the system event log. Note: This command has many parameter options; only the most commonly used parameters are listed below.
Note: To show events for the current day, you may omit the YY, MM, and DD parameters from the start and end times.
|
|
exc |
Displays the meaning of an exception code that was listed in the errorlog or viewexlog command output.
|
|
hostname |
Displays the hostname of the Application Server.
|
|
infocap |
Captures configuration details and logs from the system for a particular time period. The output file is a zip file that is stored in the /tmp directory. The system gives the exact location after compiling the information.
|
|
langinfo |
Displays information about all installed locales including the following:
|
|
mtginfo |
Displays information about a specific meeting. Searches for a meeting based on any of these:
Note: The start and end times must be in the format YYMMDDhhmm. All parameters are optional. If they are not all present, the system starts processing from the right. For format details, see the parameters for the date command. Note: Start and end times in the command output are adjusted for the Meeting ID start guard time (minutes) and Meeting ID end guard time (minutes) fields on the Meeting Configuration Page.
|
|
net |
Lists the current network configuration settings and allows you to change them after the system has been installed. Most changes take affect after restarting the system. Caution! A system restart terminates all existing call connections. Proceed only during a scheduled maintenance period or during a period of extremely low usage. NOTE: When you restart the Web Server, all manual changes made to the registry are lost.
Use the net command to set the following:
|
|
ntpdate |
Sets the Application Server date and time to match the time obtained by polling an NTP server.
|
|
swstatus |
Displays information about Cisco Unified MeetingPlace, including the following:
|
|
techui |
Displays statistics for the Media Server, ports, and conferences.
|
|
userinfo |
Displays information about a specific user. Searches for a user based on any of these:
|
|
userutil |
Performs administrative functions for any user profile.
|
|
viewexlog |
Provides the entire Exception Log output all at once:
|
Related Topics
Operating System Commands
In addition to the Cisco Unified MeetingPlace commands listed in Table: Command Reference: Operating System Commands, the CLI supports the standard Linux operating system commands. You can use the vim command to view or modify text files if necessary.
Note the following requirements and restrictions for operating system commands:
- With the exception of the mpx_sys command, use the operating system commands to start or stop services only when you have been explicitly told to do so by Cisco TAC. Use of these commands may cause unpredictable results.
- If you are not logged in as the root user, you must enter sudo before you can run any of these commands. For example, to stop all application services, go to the command line and enter the following:
- sudo ./mpx_app stop
- The preceding example assumes that you are already in the /etc/init.d directory. If you are not in that directory, you instead enter the following:
- sudo /etc/init.d/mpx_app stop
- Existing call connections will not be terminated by stopping services on the Application Server. However, starting or restarting services will terminate those calls. This behavior applies:
Table: Command Reference: Operating System Commands
| Command | Description |
|---|---|
|
mpx_app |
Starts, stops, or restarts all Cisco Unified MeetingPlace application services. NOTE: When you restart the Web Server, all manual changes made to the registry are lost.
|
|
mpx_axlds |
Starts, stops, or restarts Directory Service and external AXL authentication through Cisco Unified Communications Manager.
|
|
mpx_db |
Starts, stops, or restarts Cisco Unified MeetingPlace database services.
|
|
mpx_lm |
Starts, stops, or restarts Cisco Unified MeetingPlace license manager services.
|
|
mpx_rmi |
Starts, stops, or restarts messaging integration services for Cisco Unified MeetingPlace Click-to-Conference for IBM Lotus Sametime Instant Messaging.
|
|
mpx_rssctrl |
Starts, stops, or restarts the Cisco Unified MeetingPlace recording and streaming service.
|
|
mpx_snmp |
Starts, stops, or restarts SNMP services.
|
|
mpx_sys |
Starts, stops, or restarts all Cisco Unified MeetingPlace services. Caution! A system restart terminates all existing call connections. Proceed only during a scheduled maintenance period or during a period of extremely low usage. NOTE: When you restart the Web Server, all manual changes made to the registry are lost.
|
|
mpx_tomcat |
Starts, stops, or restarts Apache Tomcat services.
|
|
mpx_tomcatmon |
Starts, stops, or restarts Apache Tomcat monitoring services.
|
|
mpx_va |
Starts, stops, or restarts Media Server services on the Application Server.
|
|
mpx_version |
Lists all installed versions of Cisco Unified MeetingPlace.
|
|
mpx_webx |
Starts, stops, or restarts all Cisco WebEx integration services on the Application Server.
|
|
resetmsapassword |
Resets the Media Server Administration password to "cisco".
|
|
shutdown |
Shuts down the Application Server.
|
Related Topics
Database Replication Commands
Note: To enter the database replication commands in Table: Command Reference: Database Replication Commands:
- The MeetingPlace Database services must be running on the Application Server.
- You must be logged in to the CLI as the root user.
The output messages from each command execution are displayed on the screen and stored in a log file under the directory $MP_LOGDIR/database/replication/logs. The log file names have the format mp_replication_log.<YYYY-MM-DD_hh-mm-ss>.
Table: Command Reference: Database Replication Commands
| Command | Description |
|---|---|
|
mp_replication init |
Makes necessary changes in configuration files and database to enable the Application Server to use database replication. Run this command on each node involved in replication.
|
|
mp_replication switchON |
Starts replication between two Application Servers.
|
|
mp_replication status |
Displays the status of replication between the specified servers.
|
|
mp_replication switchOFF |
Stops replication, but does not restore configuration changes.
|
|
mp_replication teardown |
Removes configuration changes made on the local server for replication with the specified remote server. Run this command on each node involved in replication to undo the configuration changes.
|
Related Topics
Failover Commands
Note: You must be logged in to the CLI as the root user to enter the failover commands in Table: Command Reference: Failover Commands.
Table: Command Reference: Failover Commands
| Command | Description |
|---|---|
|
failoverUtil copyConfigFiles |
Transfers configuration files from one Application Server to the other, specifically:
|
|
failoverUtil restoreConfigFiles |
Completes the transfer of configuration files from one Application Server to the other, specifically:
Note: The failoverUtil copyConfigFiles and failoverUtil restoreConfigFiles commands are entered on separate Application Servers.
|
|
failoverUtil setDeployment failover |
Sets up an Application Server for failover deployment, including the configuration of the virtual network interface (eth0:0) hostname, IP address, subnet mask, and default gateway.
|
|
failoverUtil setDeployment singleServer |
Restores a failover-deployed Application Server to a single-server deployment.
|
|
failoverUtil setServer |
Sets a failover-deployed Application Server to either active or standby mode.
Note: The mode setting may not be successful if this process is interrupted, for example, by a power outage, by closing the SSH connection, or by a system restart. To view the failover mode, log in to the Administration Center. If the wrong failover deployment mode appears at the top of the page, enter the mpx_sys restart command, followed by the failoverUtil setServer command. NOTE: When you restart the Web Server, all manual changes made to the registry are lost.
Syntax: failoverUtil setServer {active | standby} |
|
failoverUtil status |
Displays the current modes of the Application Server, specifically:
|