Browsed by
Category: Howto

CUCM Common Partition – How to Clean?

CUCM Common Partition – How to Clean?

Sometimes when you go through RTMT logs on a Cisco Unified Communicatios Manager (CUCM), you can see a critical warning of “LogPartitionLowWaterMarkExceeded“. This happens when free space in CUCM common partition becomes low.

In most cases this problem doesn’t affect the whole system to function, but the low space on disk may cause problems if you want to do some installation (eg. device pack) or upgrades.

CUCM common partition is also called as log partition and is mostly filled with CDRs, CUCM traces and phone firmware files from TFTP server. LogPartitionLowWaterMarkExceeded alarm is occured when the log partition disk space percentage reaches the “Low WaterMark” treshold. You can take this alarm as an early notification to clean up the disk space. CUCM doesn’t have such kind of automated cleanup process until the “High WaterMark” value is reached.

What Should I Do To Clean CUCM Common Partition?

To clean up and free some space in the common partition, you can do the following:

  • Change the threshold values of LogPartitionLowWaterMarkExceeded to 50% and LogPartitionHighWaterMarkExceeded to 60%, and then restart “Cisco Log Partition Monitoring Tool” service and after couple of hours you should see that the used space is decreased.
  • Delete unused log by using RTMT Trace/Log Central to collect logs/traces with “Delete Collected Log Files from Server” option.(this is for both active and inactive partitions). Select relateive range as 8-9 years to delete all unused logs.
  • Delete the old unused phone firmware files from the TFTP server.
  • Use CUCM script called ciscocm.free_common_space_v1.1.cop.sgn (you can find & download it in cisco.com) that deletes all files from the inactive common partition. But please be informed that after using this script, you won’t be able to switch to previous CUCM version.

If you want to reduce the CUCM common partition usage, you can do the following:

  • Deactivate Detail/Debug trace level.
  • Reduce the number of trace files to be stored.
  • For CDR: reduce the High Water Mark, reduce the occupied disk space, and reduce the number of days to store CDRs.

Taking a Screenshot of a Cisco IP Phone

Taking a Screenshot of a Cisco IP Phone

The screen capture function which is available on Cisco IP Phone models can be very useful, especially in some situations that require remote support. In the following article, you can find the procedure for taking screenshots for Cisco 7800 and 8800 series IP phones.

First, let’s verify some settings on Cisco Unified Communications Manager (CUCM).

CUCM Settings

In order to take a screenshot of a Cisco IP phone, the phone first must be paired with a CUCM user (End User) and web access must be enabled in the phone settings page. You can make these settings from the CUCM Administration page using the Device -> Phone menu and selecting the corresponding phone.

First you need to open the web interface of the phone. To do so, enable Web Access in the Product Specific Configuration Layout section.

Cisco IP Phone Web Access Settings

Then we need to pair the IP phone with an end user. Select the end user in Owner User ID section on the same settings page.

Pairing End User With Cisco IP Phone

After selecting the end user, select the relevant user from the User Management -> End User menu and ensure that the corresponding phone is added in the Controlled Devices field of Device Information section.

User – IP Phone Matching under End User Settings

After applying these settings, go to System -> Enterprise Parameters menu and check the user authentication URLs that the phone will use when accessing the web interface. Related settings can be found in the Phone URL Parameters and Secure Phone URL Parameters.

Service Authentication URL Settings in Enterprise Parameters

Authentication on IP phones uses the URL format below:

http(s)://cucmcip/authenticate.jsp?UserID=<id>&Password=<password>&devicename=<nameofthedevice>

If the information entered is appropriate, browser displays a simple AUTHORIZED message, and if there is inconsistency in the information, UN-AUTHORIZED message is displayed. Below is a sample URL and its output:

You Can Check Your CUCM End User & Password This Way

Tip: If you want to by-pass authentication on IP phones, you can redirect the Authentication URLs under Enterprise Parameters to a webpage that will always respond as “AUTHORIZED” 🙂

Taking a Screenshot of a Cisco IP Phone From a Web Browser

If you have done all of the above steps properly, you can now take a screenshot of your IP phone. To do so, you can use the following URL:

 http://cucmip/CGI/Screenshot 

After entering the username and password, you will see an image like the following:

Cisco 7821 IP Phone Screenshot Tkane From a Web Browser

Troubleshooting

If you get an error message like this in your web browser:

 <CiscoIPPhoneError Number=”4” /> 

This problem is probably related to authentication. Verify that the IP phone is in control of an end user and that the user’s credentials are correct. To see this easily, you can test and adapt the above authentication URL format to your phone. If the URL works but the phone’s web page still shows the same error, reset the phone and try again.

 <CiscoIPPhoneError Number=”0” /> 

This error indicates that the phone cannot connect to the URL provided in CUCM for authentication. There can be many things that can cause this issue, and almost all of them are about the accessibility. Please check the settings like routing from IP telephones to CUCM (or authentication server), DNS etc.

Cisco Serial Number Analyis in Detail

Cisco Serial Number Analyis in Detail

In this article you will find a detailed analysis of the serial numbers of your Cisco devices. This allows you to learn where and when your device was manufactured with the Cisco serial number.

Cisco Serial Number Format

The common serial number format in Cisco is:

LLLYYHHXXX

Now let’s explain these letters one by one:

LLL: Company and Country (Location) Codes:

Indicates which company produced the device and where. Below you will find the relevant companies and locations:

CTH – Celestica – Thailand
FOC – Foxconn – Shenzhen, China
JAB – Jabil – Florida, United States
JPE – Jabil – Malaysia
JSH – Jabil in Shanghai, China
TAU – Solectron – Texas, United States
PEN – Solectron – Malaysia

YY: Year Codes

This two-digit code indicates the year of manufacture. There is a nuance that needs attention. To find the year of manufacture, you must add 1996 to the specified number. For example, if it says 20, the device was manufactured in 20 + 1996 = 2016.

Below you will find code and year information for your convenience:

01 = 1997
02 = 1998
03 = 1999
04 = 2000
05 = 2001
06 = 2002
07 = 2003
08 = 2004
09 = 2005
10 = 2006
11 = 2007
12 = 2008
13 = 2009
14 = 2010
15 = 2011
16 = 2012
17 = 2013
18 = 2014
19 = 2015
20 = 2016
21 = 2017
22 = 2018
23 = 2019

HH: Week Codes

This section indicates which week of the year the device was manufactured. For convenience, you can find the week-to-month matching below:

1-5: January
6-9: February
10-14: March
15-18: April
19-22: May
23-27: June
28-31: July
32-35: August
36-40: September
41-44: October
45-48: November
49-52: December

XXXX: Serial Number

The last 4 digits are the device-specific serial number. 0-9 and A-Z (except for I and O). With these 4 digits, approximately 1.3 million combinations can be produced.

An Example: FOC18240VLV

Company and Place Foxconn – Shenzhen, China
Year of Production 18 + 1996 = 2014
Production Week 24 (June)
Serial No 0VLV
Changing IP Address & Hostname CUCM

Changing IP Address & Hostname CUCM

Hello, in this article you can find the configuration steps to change the CUCM IP address and hostname.

CUCM Changing IP Address & Hostname

Note 1: Before you start, if you plan to change the hostname, make sure that the corresponding DNS records are also updated. Otherwise you may experience communication problems.

Note 2: If you are going to change the IP addresses or hostnames of all nodes on a CUCM cluster, start from Publisher first. And then change the Subscribers individually.

After these warnings, now we can start:

1. Connect to CUCM OS Admin CLI via SSH and use the following command to change the hostname:

admin:set network hostname 
  
ctrl-c: To quit the input.
  
          ***   W A R N I N G   ***
 Do not close this window without first canceling the command.
  
 This command will automatically restart system services.
 The command should not be issued during normal operating 
 hours.
  
 =======================================================
  Note: Please verify that the new hostname is a unique 
        name across the cluster and, if DNS services are 
        utilized, any DNS configuration is completed 
        before proceeding.
 =======================================================
  
 Security Warning : This operation will regenerate
        all CUCM Certificates including any third party
        signed Certificates that have been uploaded.   

Note: For hostname changes, if your CUCM or cluster uses certificates that are signed by a CA, you will need to sign these certificates again according to the new hostname and upload them to the CUCM. If self-signed certificates are used, this process will be renewed automatically and your endpoints will be reset to receive the new ITL file.

2. Enter the hostname after reading the warnings:

Enter the hostname:: cucm 

3. If you want to change the IP address, subnet mask and default gateway, enter the relevant information followed by yes:

 Would you like to change the network ip address at this time [yes]:: yes
    
 Warning: Do not close this window until command finishes.
    
  ctrl-c: To quit the input.
    
            ***   W A R N I N G   ***
 =======================================================
  Note: Please verify that the new ip address is unique 
        across the cluster.
 =======================================================
     
 Enter the ip address:: 192.168.0.137
 Enter the ip subnet mask:: 255.255.255.0
 Enter the ip address of the gateway:: 192.168.0.1 

4. The information you entered will be displayed on the screen. If all are true, you can start the change process by typing yes:

 Hostname:       cucm                                                   
 IP Address:     192.168.0.137
 IP Subnet Mask: 255.255.255.0
 Gateway:        192.168.0.1
  
 Do you want to continue [yes/no]? yes 
    
 calling 1 of 5 component notification script: ahostname_callback.sh                      
 Info(0): Processnode query returned =
 name       
 ========== 
 bldr-vcm18 
 updating server table from:'oldHostname', to: 'newHostname'
 Rows: 1
 updating database, please wait 90 seconds
 updating database, please wait 60 seconds
 updating database, please wait 30 seconds
 Going to trigger /usr/local/cm/bin/dbl updatefiles --remote=newHostname,oldHostname 
 calling 2 of 5 component notification script: clm_notify_hostname.sh                   notification
 Verifying update across cluster nodes...
 platformConfig.xml is up-to-date: bldr-vcm21
  
 cluster update successfull
 calling 3 of 5 component notification script: drf_notify_hostname_change.py    
 calling 4 of 5 component notification script: regenerate_all_certs.sh                      
 calling 5 of 5 component notification script: update_idsenv.sh                  
 calling 1 of 2 component notification script: ahostname_callback.sh                       
 Info(0): Processnode query returned =
 name 
 ==== 
 Going to trigger /usr/local/cm/bin/dbl updatefiles --remote=10.10.10.28,10.67.142.24
 calling 2 of 2 component notification script: clm_notify_hostname.sh                    
 Verifying update across cluster nodes...
 Shutting down interface eth0:  

If your CUCM or cluster is in mixed-mode, and you have done this with the CTL Client, run the CTL client again and update the CTL file. If you used tokenless CTL, run utils ctl update CTLFile from CLI to update the CTL file.

Cisco Meeting Server (CMS): Basic Configuration

Cisco Meeting Server (CMS): Basic Configuration

Hello, in this article you can find the basic configuration steps and how to enable web interface of Cisco Meeting Server (CMS).

There are 3 different interfaces for configuring Cisco Meeting Server: command line (CLI), GUI and API. The first CLI interface can be accessed via the server’s console or SSH (after the IP address is given). Now let’s start with the basic configuration steps, starting with the CLI interface and continue with switching to the GUI interface:

Cisco Meeting Server CLI Basic Configuration

When you connect to CMS via console, a login screen is displayed. You can log into CMS with default user admin and admin as password. After you log in, it asks you to change the password.

After passing this step, we can proceed to IP settings. By default, the CMS uses the IP which is received via DHCP, and if you want to configure CMS with a static IP address, you can use the following CLI command according to your own settings:

ipv4 a add 192.168.0.133/24 192.168.0.1 

In this command, a is the name of a interface, 192.168.0.133is the IP address /24 is subnet mask and as you would expect 192.168.0.1 is default gateway.

Once you set the IP address, you can now connect to the CMS over SSH.

You can change the hostname which is defined as acano by default by issuing this command:

hostname cms1

After this command, the CMS will ask you to reboot CMS in order to activate new hostname. You can reboot the CMS with the reboot command.

You need DNS and NTP servers for CMS to work properly. Considering that they are already up and running, enter the following DNS (.100) and NTP (.101) IP configurations:

ntp server add 192.168.0.101
dns add forwardzone. 192.168.0.100

You can noe continue with the configuration to activate the GUI.

WEB GUI Configuration

In order to use the web GUI, first you need a certificate for HTTPS connections. This certificate can be either a self-signed or a CA-signed certificate. For ease of operation, you can use the self-signed certificate by issuing this command:

pki selfsigned cms1

After that, specify the interface and HTTPS port for the web interface:

webadmin listen a 445

For the certificate (s) to be used, we specify the self-signed certificate created in the upper section and with the relevant key:

webadmin certs cms1.key cms1.crt

You can use the following command to route HTTP requests to HTTPS:

webadmin http-redirect enable

Then finally activate the web admin module:

webadmin enable

Now you can use the web interface with same CLI user.

You can also find these procedures in the video below:

Cisco Meeting Server (CMS) Basic Configuration

At this point, I must point out that you need to use either CLI, GUI and API interfaces to configure the different services of CMS. So this means that you can’t do everything from GUI or CLI only. I hope this situation will change with next releases.