The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
The system creates a First Administrator account. This administrator must sign into the system, create a password, and add other administrators. Until then, no other administrator can have access to the system. As part of the process, the First Administrator (and only the First Administrator) can create an Auditor account, separating the administrator and auditor. This can be done as part of the deployment process or the First Administrator can create an Auditor by using (Auditor Role for more information.) ) to modify the role. (See
A mail server for the system to use to send emails to administrators must be configured. See Configuring an Email (SMTP) Server for instructions.
The Auditor role is added by using Adding Users.
The Auditor role is a special role created for environments that need to audit sign-ins and configuration changes made by administrators. An auditor can configure log settings and generate Application Audit logs to meet company security and JITC-compliance requirements.
The First Administrator has Auditor privileges by default, and is the only one who can activate the Auditor role for another user. When doing so, the Auditor privileges are taken away from the First Administrator. If an Auditor is also a System Administrator, that person has a System Auditing role.
The Auditor role separates administrative actions from system monitoring as follows:
Turn auditing on or off.
Configure CWMS to synchronize with the remote syslog servers.
Perform log purging.
Configure alarms for the log partition.
Generate log captures.
An Auditor does not have Host privileges and cannot schedule meetings by using the Auditor account. An Auditor can attend meetings as a participant.
If the Administrator and Auditor roles are not separated, only the Administrator role exists.
If the Administrator and Auditor roles are separated when the system is deployed, a First Administrator role is created (described as the emergency account). After system deployment, only the First Administrator emergency account can create an Auditor. The First Administrator can create as many auditors as desired after the system has been deployed by using the Adding Users procedure..
The Auditor is local only; it cannot come from synchronization with any external user base.
Auditor parameters (such as the name) can be modified, but once created the Auditor role cannot be deactivated or reassigned to another user ID.
An Auditor cannot modify user parameters. An Auditor can only see and configure settings on the Auditor tab.
The Auditor role is a unique role with the following aspects:
Note | If an Auditor is not configured, all administrators have access to and can configure the Application Audit Log settings on the page and the Log Memory Usage alarm on the page. If an Auditor is configured, administrators can view these pages, but they cannot modify them. |
Configure your system properties by selecting
in the System section.Use this feature to change virtual machine settings. Do not use VMware vCenter to change virtual machine settings.
During deployment, you can only configure IPv4 settings. After deployment, you can configure IPv6 settings if you have an IPv6 connection between your Internet Reverse Proxy in the DMZ network and your internal virtual machines.
Step 1 | Sign in to Site Administration.
In a Multidata Center system, the DNS determines which data center Dashboard appears. Use this Dashboard to manage all the data centers in this system. |
Step 2 | Turn on Maintenance Mode. See Turning Maintenance Mode On or Off.
If the data center is part of a Multidata Center (MDC) system, in-progress meetings fail over to an active data center. The failover can cause a brief interruption in active meetings. See About Maintenance Mode for information. Turning on Maintenance Mode for all active data centers shuts down all conference functionality. No one can sign in to the WebEx site, schedule meetings, join meetings, or play meeting recordings. |
Step 3 | (Optional) Take a snapshot of each virtual machine. (See Taking a Snapshot by using VMware vCenter.) |
Step 4 | Select . |
Step 5 | Select the virtual machine name in the Primary System or High Availability System section.
You can modify the following virtual machine settings:
The Virtual Machine field is grayed out. The system automatically retrieves the IP address by resolving the host name to the IP address of a virtual machine in the DNS server. See Changing the IP Address of a Virtual Machine while Retaining the Hostname for more information about changing an IP address of a virtual machine. |
Step 6 | Select
Save.
Your changes are saved and the virtual machine is re-booted. |
Step 7 | Turn off Maintenance Mode.
When you turn off Maintenance Mode, the system determines whether a restart or a reboot is required, and displays the appropriate message. A restart takes approximated 3 to 5 minutes and a reboot takes approximately 30 minutes. If the data center is part of a Multidata Center (MDC) system, you are redirected to the global admin URL. The DNS resolution policy determines which data center you see. If Key Regeneration is enabled, taking one data center out of Maintenance Mode automatically takes all data centers in the system out of Maintenance Mode. Meeting service on the data center is restored. |
If you make changes to any of your virtual machines, you must deploy a new certificate on all virtual machines in each data center unless you are using wildcard certificates for systems in the same domain. For more information see Managing Certificates.
If you change the hostname of a virtual machine that is part of your deployment, the corresponding IP address is picked up automatically from the DNS. This procedure explains how to change the IP address of a virtual machine and keep the same hostname.
Step 1 | Configure a temporary hostname in the DNS server. |
Step 2 | Complete the Changing Virtual Machine Settings procedure to change the hostname of the virtual machine to the temporary hostname you entered in the DNS server. When you take the system out of maintenance mode, the new temporary hostname takes effect. The original hostname is no longer part of the deployment after making this change. |
Step 3 | Change the IP address of the original hostname in the DNS to the new IP address. |
Step 4 | Using the Changing Virtual Machine Settings procedure, change the temporary hostname of the virtual machine to the original hostname. When you take the system out of maintenance mode, the original hostname takes effect. Your original hostname with the new IP address is configured. |
Step 1 | Sign in to Site Administration.
In a Multidata Center system, the DNS determines which data center Dashboard appears. Use this Dashboard to manage all the data centers in this system. |
Step 2 | Turn on Maintenance Mode. See Turning Maintenance Mode On or Off.
If the data center is part of a Multidata Center (MDC) system, in-progress meetings fail over to an active data center. The failover can cause a brief interruption in active meetings. See About Maintenance Mode for information. Turning on Maintenance Mode for all active data centers shuts down all conference functionality. No one can sign in to the WebEx site, schedule meetings, join meetings, or play meeting recordings. |
Step 3 | Select System, select the data center, and select View Details in the System section. The Properties page appears. |
Step 4 | To modify the IP addresses, in the Virtual IP Address section select a link in the Type column. |
Step 5 | Enter the virtual IP addresses. |
Step 6 | Enter the virtual IP address, subnet mask, and gateway in the IPv6 Address column if you have enabled IPv6 for client connections. The public and private virtual IP addresses must be on separate IPv6 subnets. |
Step 7 | Select Save. |
Step 8 | Turn off Maintenance Mode.
When you turn off Maintenance Mode, the system determines whether a restart or a reboot is required, and displays the appropriate message. A restart takes approximated 3 to 5 minutes and a reboot takes approximately 30 minutes. If the data center is part of a Multidata Center (MDC) system, you are redirected to the global admin URL. The DNS resolution policy determines which data center you see. If Key Regeneration is enabled, taking one data center out of Maintenance Mode automatically takes all data centers in the system out of Maintenance Mode. Meeting service on the data center is restored. |
Public access enables people external to your network to host or attend online meetings through the Internet or mobile devices. Removing public access will remove public virtual IP address settings for your WebEx site URLs and terminate external access to your site.
The requirements for Internet Reverse Proxy (IRP) in an MDC environment are:
The process for adding or removing IRP is the same for a Single-data Center system as they are for a MDC system.
When adding a data center to a MDC system, all data centers or none of the data centers should be configured to use IRP.
One IRP node is used per data center.
Modifying IRP requires that the system be place in Maintenance Mode. In a MDC system, IRP can be added or removed one system at a time to avoid a service interruption.
In a MDC environment, adding or removing a local public VIP on one data center does not affect the other data centers.
For a description of internal Internet Reverse Proxy topology, see the Cisco WebEx Meetings Server Planning Guide.
To enable public access you must first configure an Internet Reverse Proxy virtual machine to serve as your public access system. Start VMware vCenter and perform the following:
Back up your virtual machines using VMware Data Recovery (vSphere 5.0) or VMware vSphere Data Protection (vSphere 5.1). This enables you to revert the changes if necessary. See Creating a Backup by Using VMware vCenter for more information.
Deploy an Internet Reverse Proxy virtual machine using the same OVA file that you used to deploy your administrator virtual machine. Your Internet Reverse Proxy virtual machine must be on the same subnet as the public virtual IP address.
Note | If you have a High Availability system, you must also deploy an Internet Reverse Proxy virtual machine for your High Availability system. Deploy an Internet Reverse Proxy virtual machine by using the same OVA file that you used to deploy your administrator virtual machine. |
Step 1 | Sign in to Site Administration.
In a Multidata Center system, the DNS determines which data center Dashboard appears. Use this Dashboard to manage all the data centers in this system. |
Step 2 | Turn on Maintenance Mode. See Turning Maintenance Mode On or Off.
If the data center is part of a Multidata Center (MDC) system, in-progress meetings fail over to an active data center. The failover can cause a brief interruption in active meetings. See About Maintenance Mode for information. Turning on Maintenance Mode for all active data centers shuts down all conference functionality. No one can sign in to the WebEx site, schedule meetings, join meetings, or play meeting recordings. |
Step 3 | Select . |
Step 4 | Select Add Public Access. |
Step 5 | Enter your
Internet Reverse Proxy virtual machine in the
FQDN field.
There are two fully qualified domain name (FQDN) fields if your system is configured for high availability. Enter your high availability FQDN in the second field. |
Step 6 | Select
Detect
virtual machines.
If your system is not configured for High Availability, a table appears displaying the Internet Reverse Proxy virtual machine. If your system is configured for High Availability, a table appears displaying the primary system Internet Reverse Proxy virtual machine and the high availability Internet Reverse Proxy virtual machine. If your system has any updates that are incompatible with the OVA version you used to create the Internet Reverse proxy virtual machine, you receive an error message and cannot proceed until you redeploy the Internet Reverse Proxy virtual machine by using an appropriate OVA file. |
Step 7 | Select Continue. |
Step 8 | Enter the IP
address from the same subnet that you used to configure your Internet Reverse
Proxy virtual machine in the
Public
(VIP) Virtual IPv4 Address field and select
Save.
Your system is updated and public access is configured. Keep your browser window open for the entire process. If your system requires minor updates compatible with the OVA version you used for creating the Internet Reverse Proxy virtual machine, they are automatically applied to your Internet Reverse Proxy virtual machine. |
Step 9 | If your system
requires minor updates, you are prompted to select
Restart after the updates are complete.
After the system restarts, you receive a confirmation message indicating that you have added public access. |
Step 10 | Verify your configuration. If you are satisfied, you can delete the virtual machine backup that you configured before performing this procedure. |
Step 11 | Select Done. |
Step 12 | Verify that
your security certificates are still valid.
Because this procedure changes your virtual machines, it might affect your certificates. If necessary, your system provides a self-signed certificate to keep your system functioning until you can reconfigure your certificates. See Managing Certificates for more information. |
Step 13 | Make any necessary changes to your DNS servers. |
Step 14 | Turn off Maintenance Mode.
When you turn off Maintenance Mode, the system determines whether a restart or a reboot is required, and displays the appropriate message. A restart takes approximated 3 to 5 minutes and a reboot takes approximately 30 minutes. If the data center is part of a Multidata Center (MDC) system, you are redirected to the global admin URL. The DNS resolution policy determines which data center you see. If Key Regeneration is enabled, taking one data center out of Maintenance Mode automatically takes all data centers in the system out of Maintenance Mode. Meeting service on the data center is restored. |
Back up your virtual machines using VMware Data Recovery or VMware vSphere Data Protection. See Creating a Backup by Using VMware vCenter for more information. Make sure you power on your virtual machines after your backup is complete.
Step 1 | Sign in to Site Administration.
In a Multidata Center system, the DNS determines which data center Dashboard appears. Use this Dashboard to manage all the data centers in this system. |
Step 2 | Turn on Maintenance Mode. See Turning Maintenance Mode On or Off.
If the data center is part of a Multidata Center (MDC) system, in-progress meetings fail over to an active data center. The failover can cause a brief interruption in active meetings. See About Maintenance Mode for information. Turning on Maintenance Mode for all active data centers shuts down all conference functionality. No one can sign in to the WebEx site, schedule meetings, join meetings, or play meeting recordings. |
Step 3 | Select System and then select the View More link in the System section. The Properties page appears. |
Step 4 | Select the
desired site, select
Remove
Public Access, and select
Continue.
After you remove public access from your site, you cannot add the same Internet proxy virtual machine to that site. To reconfigure public access, you must start over by redeploying an Internet reverse proxy virtual machine from the OVA file. See Adding Public Access to Your System by using IRP for more information. Public access is removed from the site. |
Step 5 | Select Done. |
Step 6 | Open VMware vCenter. Power off, and delete the Internet Reverse Proxy machine (and high-availability Internet reverse proxy machine, if deployed) from your system. |
Step 7 | Turn off Maintenance Mode.
When you turn off Maintenance Mode, the system determines whether a restart or a reboot is required, and displays the appropriate message. A restart takes approximated 3 to 5 minutes and a reboot takes approximately 30 minutes. If the data center is part of a Multidata Center (MDC) system, you are redirected to the global admin URL. The DNS resolution policy determines which data center you see. If Key Regeneration is enabled, taking one data center out of Maintenance Mode automatically takes all data centers in the system out of Maintenance Mode. Meeting service on the data center is restored. |
When you have a non-split-horizon network topology, all users (internal and external) with an IPv6 client connection can access the WebEx site URL using the public VIP address to host and access online meetings. When the private IPv6 virtual IP address information is configured, administrators with an IPv6 client connection can sign in to the Administration site.
Consider the following when configuring an IPv6 client connection:
Configure the DNS servers so your Administration site URL points to the private IPv6 and the private IPv4 virtual IP addresses.
Configure the DNS servers so your WebEx site URL points to the public IPv6 and the public IPv4 virtual IP addresses.
Step 1 | Sign in to Site Administration.
In a Multidata Center system, the DNS determines which data center Dashboard appears. Use this Dashboard to manage all the data centers in this system. |
Step 2 | Turn on Maintenance Mode. See Turning Maintenance Mode On or Off.
If the data center is part of a Multidata Center (MDC) system, in-progress meetings fail over to an active data center. The failover can cause a brief interruption in active meetings. See About Maintenance Mode for information. Turning on Maintenance Mode for all active data centers shuts down all conference functionality. No one can sign in to the WebEx site, schedule meetings, join meetings, or play meeting recordings. |
Step 3 | Select System and then select the View More link in the System section. |
Step 4 | In the Virtual IP Address section, select a link in the Type column. The Private or Public Virtual IP Address page displays the previously entered IPv4 IP address, subnet mask, and gateway IP address of the WebEx Site URL and Administration URL. |
Step 5 | In the IPv6 Address column, enter the IPv6 IP address, subnet mask, and gateway IP address of the WebEx Site URL and Administration URL. |
Step 6 | Select Save. |
Step 7 | Turn off Maintenance Mode.
When you turn off Maintenance Mode, the system determines whether a restart or a reboot is required, and displays the appropriate message. A restart takes approximated 3 to 5 minutes and a reboot takes approximately 30 minutes. If the data center is part of a Multidata Center (MDC) system, you are redirected to the global admin URL. The DNS resolution policy determines which data center you see. If Key Regeneration is enabled, taking one data center out of Maintenance Mode automatically takes all data centers in the system out of Maintenance Mode. Meeting service on the data center is restored. |
Perform this procedure from a computer that belongs to the same subnet as the CWMS. Site Administration is accessible from either the original or the new subnet for the CWMS.
If you plan to keep the same DNS servers, keep the old DNS entries until the change is complete. If you are changing DNS servers, configure the servers, turn off Maintenance Mode, and then change the subnet.
To keep the same fully qualified domain names (FQDNs) and change only the IP addresses, you must do this in two stages by using temporary names. Typically you can change the IP address of a server only if you also change its name. This is to avoid a change simply by changing a DNS entry. However, Admin and Site URLs do not fall into this category. Sometimes that the computer making all the administrative changes appears to be unable to browse to the Admin URL pages. If that happens, make sure that you can ping nslookup and if necessary, flush the local PC DNS cache after any changes.
We recommend for all versions of CWMS:
Create a Remote Support Account before beginning any maintenance work.
Apply for new certificates to be used when the IP address change is completed. In the interim, the system can use a self-signed certificate.
Verify that the DNS entries are prepared and ready. If the virtual machines do not restart, restart only the Admin virtual machine and change the Network Adapter #2 assignment. The IRP can remain up, and you can change the assignment for Network Adapter #2 when you see the Admin virtual machine rebooting.
Note | During the subnet change, you must edit the virtual machine settings to move the virtual NICs to another VLAN. You cannot simply power off, change the system, and power it back on. Turn off Maintenance Mode to apply the changes and cause all the virtual machines to reboot. If you fail to change the VLANs after the virtual machines reboot, the network interfaces appear, but they cannot communicate. |
If you used temporary names, Replace the Temporary Names.
Complete this procedure to replace the temporary names with the original fully qualified domain names (FQDN).
Step 1 | In the DNS, connect the permanent names to the new IP addresses.
To change the FQDN for the new IP addresses, use Site Administration. Open the servers one-by-one to enter permanent names. |
Step 2 | Optionally edit the URLs. |
Step 3 | Turn off Maintenance Mode. |
Step 4 | After the system reboots, delete the unused entries from DNS. |
Step 5 | Verify that the system works correctly by accessing the Admin URL. We also recommend that you test access to meeting recordings on the NFS and test the system by creating a new recording. |
Step 6 | Double check the CUCM trunks and modify IP addresses as necessary. |
General settings include the following parameters:
Site Settings—Manages the site URL.
Administration Site Settings—Manages the administration site URL.
Virtual IP addresses are shown in the information block and can be managed on the
.Use this procedure to change the original WebEx site URL to a new URL. You configured your original WebEx site URLs during deployment. In an MDC system, the WebEx site URL is configured during the process of joining data centers. For more information about site URL configuration and naming conventions, see WebEx Site and WebEx Administration URLs.
After this change is made, system traffic coming from hostnames, other than the ones currently configured, is dropped.
We recommend that you notify users of the pending change and suggest that before the change is made that they download any recordings they want to retain.
If users attempt to use the original URL, those users cannot:
Step 1 | Sign in to Site Administration.
In a Multidata Center system, the DNS determines which data center Dashboard appears. Use this Dashboard to manage all the data centers in this system. |
Step 2 | Turn on Maintenance Mode. See Turning Maintenance Mode On or Off.
If the data center is part of a Multidata Center (MDC) system, in-progress meetings fail over to an active data center. The failover can cause a brief interruption in active meetings. See About Maintenance Mode for information. Turning on Maintenance Mode for all active data centers shuts down all conference functionality. No one can sign in to the WebEx site, schedule meetings, join meetings, or play meeting recordings. |
Step 3 | Select The General Settings window displays. . |
Step 4 | If this is an MDC system, select the data center. |
Step 5 | In the Site Settings section to be modified, select Edit. |
Step 6 | Enter the URLs and select Save. |
Step 7 | Turn off Maintenance Mode.
When you turn off Maintenance Mode, the system determines whether a restart or a reboot is required, and displays the appropriate message. A restart takes approximated 3 to 5 minutes and a reboot takes approximately 30 minutes. If the data center is part of a Multidata Center (MDC) system, you are redirected to the global admin URL. The DNS resolution policy determines which data center you see. If Key Regeneration is enabled, taking one data center out of Maintenance Mode automatically takes all data centers in the system out of Maintenance Mode. Meeting service on the data center is restored. |
Update your site certificate to ensure secure access. See Managing Certificates for more information.
Notify hosts that they should reschedule all meetings.
Use this procedure to change the original administration site URL to a new URL. You configured your original administration site URL setting during deployment. In an MDC system, your administration site URL is configured during the process of joining data-centers. For more information about site URL configuration and naming conventions, see WebEx Site and WebEx Administration URLs.
We recommend that you notify users of the pending change and suggest that before the change is made that they download any recordings they want to retain.
If users attempt to use the original URL, those users cannot:
Step 1 | Sign in to the Administration site. |
Step 2 | Turn on Maintenance Mode. See Turning Maintenance Mode On or Off.
If the data center is part of a Multidata Center (MDC) system, in-progress meetings fail over to an active data center. The failover can cause a brief interruption in active meetings. See About Maintenance Mode for information. Turning on Maintenance Mode for all active data centers shuts down all conference functionality. No one can sign in to the WebEx site, schedule meetings, join meetings, or play meeting recordings. |
Step 3 | Select System. |
Step 4 | In the Configuration section, select View More. |
Step 5 | In the Administration Settings section, select Edit. |
Step 6 | Enter your new Administration site URLs in the dialog box and select Save. |
Step 7 | Turn off Maintenance Mode.
When you turn off Maintenance Mode, the system determines whether a restart or a reboot is required, and displays the appropriate message. A restart takes approximated 3 to 5 minutes and a reboot takes approximately 30 minutes. If the data center is part of a Multidata Center (MDC) system, you are redirected to the global admin URL. The DNS resolution policy determines which data center you see. If Key Regeneration is enabled, taking one data center out of Maintenance Mode automatically takes all data centers in the system out of Maintenance Mode. Meeting service on the data center is restored. |
Update your site certificate to ensure secure access. See Managing Certificates for more information.
Notify hosts that they should reschedule all meetings.
Use these features to configure your servers:
Configure an Email server to enable your system to send meeting invitations and other communications to users.
It is important that the Email server is always operational. Email is the primary method of communication with your users including recording notifications, meeting information changes, account status, and many other important announcements. (See also Adding Users.)
Turning on Maintenance Mode is not required to change these properties.
Users are identified to the system by Email address. If a user Email address is changed and the user remains active, the Email address on CWMS must also be changed or that user will not receive notifications.
CWMS cannot establish a connection with Exchange if the password contains special character, such as ^, &, *, (), _, +, or /\.
See Activating or Deactivating Users or Administrators, Adding Users, and Editing Users.
A list of email templates:
All Admins - Welcome Email
Forgot Password - Reset Password-Admin
Forgot Password - Password Changed-Admin
Import finished
Import aborted
Export finished
Export aborted
Orion Site URL changed-Admin
Orion Admin URL changed-Admin
Primary admin - License-free Trial Started
1st alarm: Buy license
2nd alarm: Buy license
Free license expired
Licenses added successfully
License converted successfully
1st alarm: Convert license
180 day expiration
Alarm: SSL Certificate expiring
SSL Certificate expired
Alarm: SSO IdP Certificate expiring
SSO IdP Certificate expired
Alarm: Secure TC Certificate expiring
Sec TC Certificate expired
Monthly Report ready
Customized Report ready
Customized Log ready
Alarm: Meeting Errors
Alarm: Meeting participants
Alarm: CPU usage
Alarm: Memory usage
Alarm: Network bandwidth usage
Alarm: Storage usage
Account Deactivated
Send Email to All Users
Account Reactivated-Admin
Clear Alarm: CPU usage
Clear Alarm: Meeting Errors
Clear Alarm: Meeting participants
Clear Alarm: Memory usage
Clear Alarm: Network bandwidth usage
Clear Alarm: Storage usage
HA system present
No HA system
Back In Compliance
AD-Sync Success
AD-Sync Failed
Account Locked
Account Locked-Unlock
Alarm License - user grace license allocated
Alarm License - warn admin of user grace license allocation
Alarm License - warn admin of grace license expiration
Alarm License - warn admin when all grace licenses are used up
Alarm License - warn admin when license usage over threshold
Alarm audit logs
Alarm MDC - DB Replication
Clear Alarm MDC - DB Replication
Alarm HA System - DB Replication Status
Clear Alarm HA System - DB Replication Status
Alarm MDC - Datacenter Status
Alarm MDC - Datacenter Unreachable
Alarm MDC - Datacenter Blocked
Clear Alarm MDC - Datacenter Status
Clear Alarm MDC - Datacenter Unreachable
Conflict in user profiles auto-corrected
Email when clocks are back to normal
Email when clocks drift
Meeting Summary report for Host
Alarm: Meeting Issues
Configurable percent: n%
Subject: Alert: Meetings experiencing issues has reached %n% of %MaxData%
On your Cisco WebEx site n% meetings in progress are experiencing issues.
Alarm: Meeting participants
Configurable percent: n%
Subject: Alert: Online meeting participants has reached n% of %Total%
Number of online meeting participants has reached n% of system capacity.
Alarm: CPU usage
Alert: CPU usage has reached %X% MHz of %Y% MHz (75%)
CPU usage has reached 75%
Alarm: Memory usage
Alert: Memory usage has reached %X% GB of %Y% GB (75%)
Memory usage has reached 75%
Alarm: Network bandwidth usage
Subject: Alert: Network bandwidth usage has reached %X% Mbps of %Y% Mbps (75%)
Network bandwidth usage has reached 75%
Alarm: Storage usage
Subject: Alert: Storage usage has reached %X% GB of %Y% GB (75%)
Because your storage usage has reached 75%, meeting recording is disabled for all users to ensure optimal performance for WebEx meetings.
Users will not be able to record meeting until storage is available on the Network File Server storage system.
Alarm License - user grace license allocated
Subject: Alert: Your temporary host license expires in 180 days
Your temporary host license expires in 180 days.
Contact your administrator to install permanent licenses.
Alarm License - warn admin of user grace license allocation
Subject: Alert: Temporary host licenses expire in 180 days
%NumberofLicenses% temporary licenses expire in 180 days.
Install additional permanent licenses to enable these users to host meetings.
Alarm License - warn admin of grace license expiration
Subject: Alert: Temporary host licenses expired
%NumberofLicenses% temporary licenses expired.
Install additional permanent licenses to enable these users to host meetings.
Alarm License - warn admin when all grace licenses are used up
Subject: Alert: All licenses assigned
All licenses are assigned and new users cannot host meetings.
Install additional permanent licenses to enable users to host meetings.
Alarm License - warn admin when license usage over threshold
Configurable threshold : $n
Subject: Alert: Licenses usage over threshold
$n of all permanent licenses are assigned. Install additional permanent licenses to allow more users to host meetings.
Alarm audit logs
Configurable percent = n%
Subject: Alert: Audit logs are nearing capacity
The log partition is n% of full capacity.
Increase free disk space.
Or you can navigate to Log Purging Settings.
on CWMS system sectionSelect date before all log archives are to be deleted and click Purge Log Archive.
Alarm MDC - DB Replication
%ReplicationStatus% = Inactive, Limited
Subject: Alert: Data synchronization between datacenters has been %ReplicationStatus%
Data synchronization from DC-1 to DC-2 has been %ReplicationStatus%. Verify that the state of the network link between the data centers is good and meets Multi-datacenter requirements.
Alarm HA System - DB Replication Status
Subject: Alert: Data synchronization has been Inactive
Data synchronization in the data center has been Inactive. Verify that the network connection between the virtual machines meets the High Availability requirements.
Alarm MDC - Datacenter Status
%DatacenterStatus% = Partial Service, Down
Subject: Alert: Datacenter is %DatacenterStatus%
The MyDatacenter1 data center is in a %DatacenterStatus% state and the system is attempting to fix the problem.
System is operating normally, but a data center has an issue that should be addressed as soon as possible. If this is intentional, then ignore this message.
Alarm MDC - Datacenter Unreachable
Subject: Alert: The MyDatacenter2 datacenter is unreachable
The MyDatacenter2 datacenter is not reachable from the MyDatacenter1 datacenter. It is not operational or is disconnected from the network.
If you are working with the data center and it was brought down intentionally, you can ignore this message.
Alarm MDC - Datacenter Blocked
Subject: Alert: Datacenter is Blocked
The MyDatacenter1 datacenter is blocked. The system is redirecting end user traffic to the other data center and is attempting to self-correct the problem.
The <site name> system continues to operate normally and this data center problem is transparent to users, but the issue should be addressed as soon as possible. If you are working with the datacenter and it was put into this state intentionally, you can ignore this message.
Email when clocks drift
Subject: Customized log file is ready
A clock drift between the Admin virtual machines of data centers DC-1 and DC-2 was detected. Synchronization of the clocks is critical to maintaining consistency of data shared by these data centers.
This problem is transparent to the end users, but the issue should be addressed as soon as possible.
Verify that the correct NTP servers are configured on the virtual machine hosts on both data centers and that the NTP servers are reachable from those hosts.
NTP is mandatory in a Multi-data Center (MDC) environment.
Step 1 | Sign in to Site Administration.
In a Multidata Center system, the DNS determines which data center Dashboard appears. Use this Dashboard to manage all the data centers in this system. |
Step 2 | Select System. |
Step 3 | Under Servers, select the View More link. |
Step 4 | Turn on Maintenance Mode. See Turning Maintenance Mode On or Off.
If the data center is part of a Multidata Center (MDC) system, in-progress meetings fail over to an active data center. The failover can cause a brief interruption in active meetings. See About Maintenance Mode for information. Turning on Maintenance Mode for all active data centers shuts down all conference functionality. No one can sign in to the WebEx site, schedule meetings, join meetings, or play meeting recordings. |
Step 5 | Under NTP Server, select the Edit link. |
Step 6 | Specify the NTP
server or select the local server.
If you select Use NTP server to update time, you must also enter the IP address of the NTP server. |
Step 7 | Select Save. |
Step 8 | Turn off Maintenance Mode.
When you turn off Maintenance Mode, the system determines whether a restart or a reboot is required, and displays the appropriate message. A restart takes approximated 3 to 5 minutes and a reboot takes approximately 30 minutes. If the data center is part of a Multidata Center (MDC) system, you are redirected to the global admin URL. The DNS resolution policy determines which data center you see. If Key Regeneration is enabled, taking one data center out of Maintenance Mode automatically takes all data centers in the system out of Maintenance Mode. Meeting service on the data center is restored. |
Use a storage server to back up your system for disaster recovery (see Disaster Recovery by Using the Storage Server) and to store meeting recordings. The supported storage methods are Network File System (NFS) and Secure Storage (SSHFS). Verify that your storage server is accessible from all internal virtual machines. There is also a VMware-provided VMware Data Recovery feature to backup the virtual machines.
You do not need to connect your storage server to external virtual machines such as external Internet Reverse Proxy (IRP) servers.
Your storage server backs up the following data daily:
Certain system settings
User information
Meeting information
SSL certificates uploaded into the system
The site URL
Backups are performed daily and are initially set for 4:20 a.m. local time. Cisco WebEx Meetings Server runs during the backup process without any interruption to meetings, recordings, or other functions. The system does not remove the previous backup until the following daily backup is complete to ensure that a backup is available.
Your system takes approximately five minutes to back up 500 MB. The time it takes to back up your system depends on storage speed, NFS speed, and other factors. A 70-GB database takes approximately 1 hour to back up and 10 minutes to transfer it to the NFS. Transfer time is 12 MB/sec to allow other network communication and to ensure the continuous operation of the system.
Secure Storage includes the following features:
Encrypted communication.
Limit storage server access to authorized accounts.
Permissions are mapped to a defined user; 777 permissions on storage are no longer required.
Cisco WebEx Meetings Server must have exclusive use of the NFS share, because the system runs various scripts on NFS files and directories. Do not manually create files or directories in the NFS share used by Cisco WebEx Meetings Server
Configure your system to use the storage server for meeting recordings and disaster recovery. Your choice of storage server depends on the configuration of your system.
Port 22 is used for Secure Storage.
Ports 111, 1110, 2049, 4045 are standard ports for various NFS services and NFS configurations of NFS server implementations.
NFS traffic requires ports 111 (TCP and UDP) and 2049 (TCP and UDP).
Cluster status requires port 1110 (TCP) and client status requires port 1110 (UDP).
NFS lock manager requires port 4045 (TCP and UDP).
Make sure that you configure your Unix access privileges so that your system can store user-generated content and system backups. (Applies to NFS storage.)
On Linux-based storage systems, configure the read and write permissions for anonymous users for the directory to be used for your Network File System (NFS). See Connect a Linux Client to the NFS Share.
On Windows-based storage systems, enable the Network Access: Let Everyone permissions apply to anonymous users setting. In addition, you must provide the Everyone user group read and write permissions for the NFS. See Configure an NFS Share.
We recommend using openSSH server for secure storage. However, this feature is independent of the make of the SFTP server and the feature should work with every server supporting this protocol.
Step 1 | Sign in to Site Administration.
In a Multidata Center system, the DNS determines which data center Dashboard appears. Use this Dashboard to manage all the data centers in this system. |
Step 2 | Turn on Maintenance Mode. See Turning Maintenance Mode On or Off.
If the data center is part of a Multidata Center (MDC) system, in-progress meetings fail over to an active data center. The failover can cause a brief interruption in active meetings. See About Maintenance Mode for information. Turning on Maintenance Mode for all active data centers shuts down all conference functionality. No one can sign in to the WebEx site, schedule meetings, join meetings, or play meeting recordings. |
Step 3 | On the System tab, in the Servers section, select
.
If a storage server is present on your system, it is displayed on this page. If there is no storage server present on your system, you are given the option to add one. |
Step 4 | In the Storage Server section, select Add a Storage Server now or Edit. |
Step 5 | Select NFS or Secure Storage. |
Step 6 | (Optional)
If you selected NFS: and . Otherwise, go to the next step. |
Step 7 | (Optional)
If you chose Secure Storage. The system confirms your mount point. You are sent a confirmation message that your storage server has been added. |
Step 8 | Select Done. |
Step 9 | (Optional) Click the System Backup Schedule (time) to display the System Backup Schedule pop-up window, select a time from the drop-down menu, and then select Save. A daily backup occurs at the time you selected. |
Step 10 | Turn off Maintenance Mode.
When you turn off Maintenance Mode, the system determines whether a restart or a reboot is required, and displays the appropriate message. A restart takes approximated 3 to 5 minutes and a reboot takes approximately 30 minutes. If the data center is part of a Multidata Center (MDC) system, you are redirected to the global admin URL. The DNS resolution policy determines which data center you see. If Key Regeneration is enabled, taking one data center out of Maintenance Mode automatically takes all data centers in the system out of Maintenance Mode. Meeting service on the data center is restored. |
Make sure that:
Your storage server is accessible from outside of Cisco WebEx
Meetings Server.
Your storage server is powered on.
There is network connectivity to your storage server.
Mount/access is possible from a non-Cisco WebEx Meetings Server
machine.
Your storage server is not full.
Note
If a user inadvertently deletes a
recording from the
Cisco WebEx Meeting Recordings page and the
recording is saved on the Network File System (NFS) storage server, you can contact the
Cisco Technical Assistance Center (TAC) for assistance in recovering the
recording.
Step 1 | Launch Server Manager. |
Step 2 | On the top menu, select Manage. |
Step 3 | Select Add Roles and Features. The Before you begin window appears. |
Step 4 | Select Next. The Select installation type window appears. |
Step 5 | Verify that Role-based or feature-based installation is selected and select Next. The Server selection window appears. |
Step 6 | Select Next. The Select server roles window appears. |
Step 7 | Expand Server for NFS. , and then check |
Step 8 | Select Next. The Select feature window appears. |
Step 9 | Select Next. |
Step 10 | Confirm the installation details, and then select Install. |
Configure an NFS share:
Install NFS file services. (See Install NFS File Services.)
Step 1 | Launch File Explorer. |
Step 2 | Create a new directory for your NFS share. |
Step 3 | Right-click the directory and select Properties. |
Step 4 | Select the NFS Sharing tab. |
Step 5 | Select Manage NFS Sharing…. |
Step 6 | Check
Share this folder and enter
in
Anonymous UID and
Anonymous GID.
Anonymous UID defaults to –2. On 16-bit machines, this value can fail because anonymous (nfsnobody) UID –2 is equivalent to 65534 in 16-bit numbers. (See www.troubleshooters.com/linux/nfs.htm). |
Step 7 | Enter a
Share name.
This is the name used when a user connects to this NFS share. |
Step 8 | Select Permissions. |
Step 9 | Select Add and enter the IP address or hostname of the client connections. |
Step 10 | Choose Read–Write access or Read-Only access and select OK. |
Step 11 | Select An NFS share is hosted on a Windows Server 2012 R2. |
Connect a Linux Client to the NFS share. (See Connect a Linux Client to the NFS Share.)
Step 1 | Log on to a
Linux server or desktop.
Open a terminal window, if you are in a Desktop version of the operating system. |
Step 2 | Create a new directory on which to mount the Windows NFS share. For example, mkdir/postprod. |
Step 3 | Mount the NFS share to the new directory. For example, mount.nfs slfileserver01:/postprod /postprod |
Step 4 | If the client has Read–Write access, test the share by creating a new file. For example, touch file01.txt. |
When you switch your storage server from the current NFS or SSH NFS to a replacement, the stored files become inaccessible. To restore access, transfer all meeting recordings, and backups to the new storage server.
Step 1 | Sign in to Site Administration.
In a Multidata Center system, the DNS determines which data center Dashboard appears. Use this Dashboard to manage all the data centers in this system. |
Step 2 | Turn on Maintenance Mode. See Turning Maintenance Mode On or Off.
If the data center is part of a Multidata Center (MDC) system, in-progress meetings fail over to an active data center. The failover can cause a brief interruption in active meetings. See About Maintenance Mode for information. Turning on Maintenance Mode for all active data centers shuts down all conference functionality. No one can sign in to the WebEx site, schedule meetings, join meetings, or play meeting recordings. |
Step 3 | Select . |
Step 4 | Manually transfer recording and backup files from the old storage server to the new storage server.
We cannot provide specific instructions for transferring these files, because each system is unique. |
Step 5 | In the Storage Server section, select Add a Storage Server now. |
Step 6 | Enter the
replacement NFS mount point or the replacement Secure Storage username.
Usernames must begin with a lowercase letter. Ending a username with a dollar sign ($) is allowed. Allowed characters: Lowercase letters, numbers, underscore, and dollar sign. All other characters are forbidden. Example: user1 |
Step 7 | Enter the
replacement NFS mount point or the replacement Secure Storage password.
Example: ******* |
Step 8 | Enter the
replacement NFS mount point or the replacement Secure Storage mount point.
Example: 192.168.10.10:/CWMS/backup |
Step 9 | Select
Save.
The system confirms your replacement NFS mount point or Secure Storage mount point. |
Step 10 | (Optional)
Select
Yes to perform the disaster recovery procedure or
select
No to skip this step.
If there are no system backup files on the replacement storage server, this step is automatically skipped. For additional information about disaster recovery, see Disaster Recovery by Using the Storage Server. |
Step 11 | Select
Continue.
You receive a confirmation message that your storage server has been added. |
Step 12 | Select Done. |
Step 13 | (Optional) You can change the default time for the daily backup. In the Storage Server section, click the System Backup Schedule time and select another time from the drop-down list. Then select Save. A daily backup occurs at the time you selected. |
Step 14 | Turn off Maintenance Mode.
When you turn off Maintenance Mode, the system determines whether a restart or a reboot is required, and displays the appropriate message. A restart takes approximated 3 to 5 minutes and a reboot takes approximately 30 minutes. If the data center is part of a Multidata Center (MDC) system, you are redirected to the global admin URL. The DNS resolution policy determines which data center you see. If Key Regeneration is enabled, taking one data center out of Maintenance Mode automatically takes all data centers in the system out of Maintenance Mode. Meeting service on the data center is restored. |
A disaster could be a network crash, server failure, data center outage, or other event that makes your system unusable. There are two types of disaster recovery:
Single-data Center (SDC) disaster recovery—You can reinstall your SDC system in the same data center and restore it to the same state by using storage server backups.
Multi-data Center (MDC) disaster recovery—If one data center fails, you can access the MDC system through the second data center, restore the damaged data center, and join the data centers to restore the MDC system. If the failed data center hosts the License Manager, it might be necessary to reinstall the License Manger, as it can run on only one system at a time.
After you configure a storage server, your system is backed up on a daily basis. A system backup notice appears on your dashboard that includes information about the latest backup. Only one backup system is kept in storage at a time. After you perform an upgrade or update, the backup from your previous Cisco WebEx Meetings Server version is retained. We recommend that you do not use the same storage directory for different Cisco WebEx Meetings Server installations.
Note that disaster recovery:
Takes more than 30 minutes
Overwrites your settings with the settings on the latest backup
Requires you to perform additional steps to restore service to your users (detailed in What To Do Next in this section)
This procedure backs up certain system settings, user information, meeting information, SSL certificates uploaded into the system, and the site URL. The backup process does not store VMware credentials or IP address information for individual virtual machines. (There is also a VMware-provided VMware Data Recovery feature to back up the virtual machines. See http://www.vmware.com/pdf/vdr_11_admin.pdf for more information.) When you perform a disaster recovery, you must manually reapply certain settings including the following:
Connections to certain external components, for example Cisco Unified Communications Manager (CUCM).
SSL certificates (in case the hostnames of the disaster recovery system differ from those in the original system).
On SDC systems, you can optionally use the same IP address or hostname. On multi-data centers systems, you can optionally use the original IP addresses or hostnames for your primary system.
Perform this procedure after a disaster has occurred and you have lost the ability to use your system.
To perform disaster recovery procedures:
A storage server must have been configured. If you do not have a storage server configured, the Disaster Recovery option is not available and backups are not created. See Adding an NFS or SSH Storage Server for more information.
Your recovery system must be the same deployment size and software version as your original system.
For a high-availability (HA) system, you must first configure disaster recovery and then configure HA on that system. If you have a HA system that requires recovery from a disaster, you must first restore your system and then configure HA on the restored system. For more information on HA, see Adding a High Availability System.
A backup OVA stored on NFS is not sufficient to rebuild a system. We recommend that you have the current OVA file stored outside the system for disaster recovery. In this context, disaster recovery includes the need to recover from a failed update. The OVA file must be ordered by using a product upgrade tool or through customer service. Sometimes this can be a lengthy process, hence our recommendation to have access to the OVA file for the current system prior to making a system altering procedure.
If you have software subscription, you can order an OVA file through the product upgrade tool (PUT) at http://tools.cisco.com/gct/Upgrade/jsp/productUpgrade.jsp by using your contract number. If you choose edelivery, you can download it from the site. If you need assistance with this process or do not have access to PUT, contact your account team or customer service. Your Cisco Customer Service Contacts can be found here at http://www.cisco.com/cisco/web/siteassets/contacts/index.html#~tab-b
Step 1 | Sign in to the Administration site on a system from where you can restore your deployment. |
Step 2 | Turn on Maintenance Mode. See Turning Maintenance Mode On or Off.
If the data center is part of a Multidata Center (MDC) system, in-progress meetings fail over to an active data center. The failover can cause a brief interruption in active meetings. See About Maintenance Mode for information. Turning on Maintenance Mode for all active data centers shuts down all conference functionality. No one can sign in to the WebEx site, schedule meetings, join meetings, or play meeting recordings. |
Step 3 | Select . |
Step 4 | Select Secure Storage. |
Step 5 | Enter the name and password for
your storage server in the
NFS Mount
Point field and select
Save.
Example:192.168.10.10:/CWMS/backup. |
Step 6 | Select
Continue to proceed with disaster recovery.
If the recovery system deployment size and software version matches your original system, you can proceed with disaster recovery. If the system has a different deployment size or software version, you cannot proceed until you redeploy the application on your recovery system so that the deployment size and software version match the original deployment. The IP address or hostname does not have to match your original deployment. |
Step 7 | Select one of the
following actions to continue:
The disaster recovery process begins. If you close your browser, you cannot sign back into the system until the process is completed. |
Step 8 | Turn off Maintenance Mode.
When you turn off Maintenance Mode, the system determines whether a restart or a reboot is required, and displays the appropriate message. A restart takes approximated 3 to 5 minutes and a reboot takes approximately 30 minutes. If the data center is part of a Multidata Center (MDC) system, you are redirected to the global admin URL. The DNS resolution policy determines which data center you see. If Key Regeneration is enabled, taking one data center out of Maintenance Mode automatically takes all data centers in the system out of Maintenance Mode. Meeting service on the data center is restored. |
You must perform the following procedures to restore service to your users:
Reconfigure your teleconferencing settings. Refer to Configuring CUCM in the Planning Guide for more information.
Reconfigure your SSO settings. See Configuring Federated Single Sign-On (SSO) Settings for more information.
Reconfigure your SNMP settings. See Configuring Your SNMP Settings for more information.
Reconfigure your certificates. You might have to reload your SSL certificates if they do not match the SSL certificates that are configured on the recovery system. See Restoring an SSL Certificate for more information.
The recovered system is initially configured for License Free Mode that expires in 180 days. Re-host your previous system licenses on the recovered system. See Re-hosting Licenses after a Major System Modification and About Host Licenses for more information.
Configure your DNS settings so that your site URL points to the current VIP. Your VIP on the restored system might be different from what you had on your original system. You must complete your DNS configuration for end users to use their original links to sign into or join meetings on the restored system. See Changing the Private and Public Virtual IP Addresses for more information.
If you have configured your system for Directory Integration and enabled LDAP authentication, verify that your CUCM credentials work. After you take your system out of maintenance mode and your system reboot is complete, sign in to the Administration site, select Save. If your CUCM credentials are incorrect, you receive an Invalid Credentials error message. If you receive this error message, enter the correct credentials and select Save again. (See "Configuring Directory Information.")
, and then selectYou can configure the following SNMP settings:
Community strings—SNMP community strings authenticate access to MIB objects and function as an embedded password.
USM users—Configure user-based security (USM) to provide additional message-level security. Select an existing USM configuration to edit it or add additional USM configurations. Other than the default USM user, serveradmin, which has read and write privileges to MIB information, all new USM users that you configure only have read-only privileges to MIB information.
Notification destinations—Use this feature to configure the trap/inform receiver.
You can add and edit community strings and community string access privileges.
Step 1 | Sign in to Site Administration.
In a Multidata Center system, the DNS determines which data center Dashboard appears. Use this Dashboard to manage all the data centers in this system. | ||||||||
Step 2 | Turn on Maintenance Mode. See Turning Maintenance Mode On or Off.
If the data center is part of a Multidata Center (MDC) system, in-progress meetings fail over to an active data center. The failover can cause a brief interruption in active meetings. See About Maintenance Mode for information. Turning on Maintenance Mode for all active data centers shuts down all conference functionality. No one can sign in to the WebEx site, schedule meetings, join meetings, or play meeting recordings. | ||||||||
Step 3 | Select System and select the View More link in the SNMP section. | ||||||||
Step 4 | Select Add in the Community Strings section. | ||||||||
Step 5 | Complete the fields on the
Add
Community String page.
Select Add. The community string is added to your system. | ||||||||
Step 6 | Turn off Maintenance Mode.
When you turn off Maintenance Mode, the system determines whether a restart or a reboot is required, and displays the appropriate message. A restart takes approximated 3 to 5 minutes and a reboot takes approximately 30 minutes. If the data center is part of a Multidata Center (MDC) system, you are redirected to the global admin URL. The DNS resolution policy determines which data center you see. If Key Regeneration is enabled, taking one data center out of Maintenance Mode automatically takes all data centers in the system out of Maintenance Mode. Meeting service on the data center is restored. |
Step 1 | Sign in to Site Administration.
In a Multidata Center system, the DNS determines which data center Dashboard appears. Use this Dashboard to manage all the data centers in this system. | ||||||||
Step 2 | Turn on Maintenance Mode. See Turning Maintenance Mode On or Off.
If the data center is part of a Multidata Center (MDC) system, in-progress meetings fail over to an active data center. The failover can cause a brief interruption in active meetings. See About Maintenance Mode for information. Turning on Maintenance Mode for all active data centers shuts down all conference functionality. No one can sign in to the WebEx site, schedule meetings, join meetings, or play meeting recordings. | ||||||||
Step 3 | Select System and select the View More link in the SNMP section. | ||||||||
Step 4 | Select a community string name link in the Community Strings section. | ||||||||
Step 5 | Change the
desired fields on the
Edit
Community String page.
Select Edit. Your community string information is changed. | ||||||||
Step 6 | Turn off Maintenance Mode.
When you turn off Maintenance Mode, the system determines whether a restart or a reboot is required, and displays the appropriate message. A restart takes approximated 3 to 5 minutes and a reboot takes approximately 30 minutes. If the data center is part of a Multidata Center (MDC) system, you are redirected to the global admin URL. The DNS resolution policy determines which data center you see. If Key Regeneration is enabled, taking one data center out of Maintenance Mode automatically takes all data centers in the system out of Maintenance Mode. Meeting service on the data center is restored. |
You can add and edit your USM users.
Step 1 | Sign in to Site Administration.
In a Multidata Center system, the DNS determines which data center Dashboard appears. Use this Dashboard to manage all the data centers in this system. | ||||||||||||||||||||||
Step 2 | Turn on Maintenance Mode. See Turning Maintenance Mode On or Off.
If the data center is part of a Multidata Center (MDC) system, in-progress meetings fail over to an active data center. The failover can cause a brief interruption in active meetings. See About Maintenance Mode for information. Turning on Maintenance Mode for all active data centers shuts down all conference functionality. No one can sign in to the WebEx site, schedule meetings, join meetings, or play meeting recordings. | ||||||||||||||||||||||
Step 3 | Select System and then select View More in the SNMP section. | ||||||||||||||||||||||
Step 4 | Select Add in the USM Users section. | ||||||||||||||||||||||
Step 5 | Complete the
fields on the
Add USM
User page.
| ||||||||||||||||||||||
Step 6 | Select
Add.
The USM user is added to your system. | ||||||||||||||||||||||
Step 7 | Turn off Maintenance Mode.
When you turn off Maintenance Mode, the system determines whether a restart or a reboot is required, and displays the appropriate message. A restart takes approximated 3 to 5 minutes and a reboot takes approximately 30 minutes. If the data center is part of a Multidata Center (MDC) system, you are redirected to the global admin URL. The DNS resolution policy determines which data center you see. If Key Regeneration is enabled, taking one data center out of Maintenance Mode automatically takes all data centers in the system out of Maintenance Mode. Meeting service on the data center is restored. |
Note | The default USM user, serveradmin, is used internally. An administrator can change the USM user name and privacy password for the serveradmin user, but cannot change the security level, authentication algorithm, or privacy algorithm for this user. |
Step 1 | Sign in to Site Administration.
In a Multidata Center system, the DNS determines which data center Dashboard appears. Use this Dashboard to manage all the data centers in this system. | ||||||||||||||||||||||
Step 2 | Turn on Maintenance Mode. See Turning Maintenance Mode On or Off.
If the data center is part of a Multidata Center (MDC) system, in-progress meetings fail over to an active data center. The failover can cause a brief interruption in active meetings. See About Maintenance Mode for information. Turning on Maintenance Mode for all active data centers shuts down all conference functionality. No one can sign in to the WebEx site, schedule meetings, join meetings, or play meeting recordings. | ||||||||||||||||||||||
Step 3 | Select System and then select View More in the SNMP section. | ||||||||||||||||||||||
Step 4 | Select a USM user in the USM Users section. | ||||||||||||||||||||||
Step 5 | Change the
desired fields on the
Edit USM
User page.
| ||||||||||||||||||||||
Step 6 | Select
Edit.
The USM user information is changed. | ||||||||||||||||||||||
Step 7 | Turn off Maintenance Mode.
When you turn off Maintenance Mode, the system determines whether a restart or a reboot is required, and displays the appropriate message. A restart takes approximated 3 to 5 minutes and a reboot takes approximately 30 minutes. If the data center is part of a Multidata Center (MDC) system, you are redirected to the global admin URL. The DNS resolution policy determines which data center you see. If Key Regeneration is enabled, taking one data center out of Maintenance Mode automatically takes all data centers in the system out of Maintenance Mode. Meeting service on the data center is restored. |
Step 1 | Sign in to Site Administration.
In a Multidata Center system, the DNS determines which data center Dashboard appears. Use this Dashboard to manage all the data centers in this system. | ||||||||||||||||||
Step 2 | Turn on Maintenance Mode. See Turning Maintenance Mode On or Off.
If the data center is part of a Multidata Center (MDC) system, in-progress meetings fail over to an active data center. The failover can cause a brief interruption in active meetings. See About Maintenance Mode for information. Turning on Maintenance Mode for all active data centers shuts down all conference functionality. No one can sign in to the WebEx site, schedule meetings, join meetings, or play meeting recordings. | ||||||||||||||||||
Step 3 | Select System and select the View More link in the SNMP section. | ||||||||||||||||||
Step 4 | Select a notification destination link from the Notification Destinations list. | ||||||||||||||||||
Step 5 | You can edit the following fields for your notification destination:
| ||||||||||||||||||
Step 6 | Select Save.
Your notification destination changes are saved. | ||||||||||||||||||
Step 7 | Turn off Maintenance Mode.
When you turn off Maintenance Mode, the system determines whether a restart or a reboot is required, and displays the appropriate message. A restart takes approximated 3 to 5 minutes and a reboot takes approximately 30 minutes. If the data center is part of a Multidata Center (MDC) system, you are redirected to the global admin URL. The DNS resolution policy determines which data center you see. If Key Regeneration is enabled, taking one data center out of Maintenance Mode automatically takes all data centers in the system out of Maintenance Mode. Meeting service on the data center is restored. |
Step 1 | Sign in to Site Administration.
In a Multidata Center system, the DNS determines which data center Dashboard appears. Use this Dashboard to manage all the data centers in this system. | ||||||||||||||||||
Step 2 | Turn on Maintenance Mode. See Turning Maintenance Mode On or Off.
If the data center is part of a Multidata Center (MDC) system, in-progress meetings fail over to an active data center. The failover can cause a brief interruption in active meetings. See About Maintenance Mode for information. Turning on Maintenance Mode for all active data centers shuts down all conference functionality. No one can sign in to the WebEx site, schedule meetings, join meetings, or play meeting recordings. | ||||||||||||||||||
Step 3 | Select System and select the View More link in the SNMP section. | ||||||||||||||||||
Step 4 | Select a notification destination link from the Notification Destinations list. | ||||||||||||||||||
Step 5 | You can edit the following fields for your notification destination:
| ||||||||||||||||||
Step 6 | Select Save.
Your notification destination changes are saved. | ||||||||||||||||||
Step 7 | Turn off Maintenance Mode.
When you turn off Maintenance Mode, the system determines whether a restart or a reboot is required, and displays the appropriate message. A restart takes approximated 3 to 5 minutes and a reboot takes approximately 30 minutes. If the data center is part of a Multidata Center (MDC) system, you are redirected to the global admin URL. The DNS resolution policy determines which data center you see. If Key Regeneration is enabled, taking one data center out of Maintenance Mode automatically takes all data centers in the system out of Maintenance Mode. Meeting service on the data center is restored. |
The list of recordings can be searched by title, creation date, or owner ID (meeting host).
The list of recordings can be sorted by file name, date, size, or owner.
An administrator can list, filter, or delete meeting recordings.
An auditor can list or filter meeting recordings.
An administrator or auditor cannot playback or download meeting recordings.
When a recording is marked for deletion, the recording status is updated in the database and the recording is no longer listed in the recordings list on the screen. After 6 months the recording is deleted from the file storage (NFS).
The owner of the recording is not notified that the recording has been deleted.
Step 1 | Select to access the Manage Recordings screen. |
Step 2 | Check the box to select the recordings to be deleted. |
Step 3 | Select Delete. |
Backups are performed daily, initially set for 4:20 a.m. local time. Cisco WebEx Meetings Server runs during the backup process without any interruption to meetings, recordings, or other functions. The system does not remove the previous backup until the following daily backup is complete to ensure that a backup is available.
Your system takes approximately five minutes to back up 500 MB. The time it takes to back up your system is dependent on storage speed, NFS speed, and other factors. A 70 GB database takes approximately one hour to back up and 10 minutes to transfer to the NFS. Transfer time is 12 MB/sec to allow other network communication and to ensure the continuous operation of the system.