top of page

Mane Mob Group

Public·38 members
Peter Gavrilov
Peter Gavrilov

Cisco CUCM 9.1 ISO 133: Best Practices for Licensing and Monitoring


Introduction




Cisco Unified Communications Manager (CUCM) is an enterprise call and session management platform that streamlines team communication and collaboration for today's hybrid workforce. It supports a wide range of features such as IP telephony, high-definition video, unified messaging, instant messaging and presence, and mobility on Cisco as well as third-party devices.




cisco cucm 9.1 iso 133


Download Zip: https://www.google.com/url?q=https%3A%2F%2Fgohhs.com%2F2ulwBS&sa=D&sntz=1&usg=AOvVaw2J_thFrmPQiiUnFE2kmKdd



The IM and Presence Service is an integrated component of CUCM that provides rich presence capabilities, enterprise instant messaging, network-based call hold and resume, and integration with Cisco Jabber clients.


Cisco CUCM 9.1 ISO 133 is a software image that contains both CUCM and IM and Presence Service in one package. It is designed for easy installation and upgrade on Cisco Unified Computing System (UCS) servers or compatible third-party servers.


In this article, we will explore the benefits of using Cisco CUCM 9.1 ISO 133, how to install it on your servers, some common issues that you may encounter with it, and some best practices for managing and monitoring it.


Benefits of Cisco CUCM 9.1 ISO 133




Why upgrade to Cisco CUCM 9.1 ISO 133?




There are many reasons why you may want to upgrade your existing CUCM system to Cisco CUCM 9.1 ISO 133. Here are some of the main benefits that you can expect from this software image:


  • Enhanced mobility: You can transform your workspaces by enabling your employees to work from anywhere, anytime, and on any device. Cisco CUCM 9.1 ISO 133 supports extensive features for mobile and remote workers, such as Extend & Connect, which allows you to use any phone as a remote line for your Cisco IP phone, Mobile Voice Access, which allows you to access your enterprise voice system from any phone, and Single Number Reach, which allows you to receive calls on multiple devices with one number.



  • Enhanced video: You can improve your collaboration and productivity by enabling high-quality video communication across your organization. Cisco CUCM 9.1 ISO 133 supports advanced video features such as video conferencing, video transcoding, video recording, and video on hold. You can also integrate your CUCM system with Cisco TelePresence solutions for immersive and lifelike video experiences.



  • Enhanced cloud: You can leverage the power and flexibility of the cloud by integrating your CUCM system with Cisco Webex Cloud services. Cisco CUCM 9.1 ISO 133 supports seamless integration with Cisco Webex Calling, which allows you to use the cloud as an extension of your on-premises CUCM system. You can also integrate your CUCM system with Cisco Webex Meetings, which allows you to schedule and join online meetings from your CUCM devices.



  • Enhanced licensing: You can simplify and optimize your licensing management by using the Cisco Prime License Manager (PLM) tool. Cisco CUCM 9.1 ISO 133 supports the PLM tool, which allows you to centrally manage and monitor the licenses for CUCM and IM and Presence Service across multiple clusters. You can also use the PLM tool to migrate your licenses from the traditional Device License Unit (DLU) model to the new User Connect License (UCL) or Cisco Unified Workspace License (CUWL) model.



These are just some of the benefits that you can enjoy by upgrading to Cisco CUCM 9.1 ISO 133. Of course, there are many more features and enhancements that this software image offers, such as improved security, scalability, reliability, interoperability, and administration. You can find more details about these features in the official documentation.


How to install Cisco CUCM 9.1 ISO 133




Basic install of cluster




If you want to install a new CUCM and IM and Presence Service cluster using Cisco CUCM 9.1 ISO 133, you need to follow these basic steps:


  • Download the Cisco CUCM 9.1 ISO 133 image from the Cisco Software Download Center. You need a valid Cisco account and a service contract to access this site.



  • Burn the ISO image to a DVD or mount it to a virtual drive.



  • Insert the DVD or mount the virtual drive to the server that you want to use as the first node of the cluster. This node will act as the publisher server for both CUCM and IM and Presence Service.



  • Boot the server from the DVD or virtual drive.



  • Follow the prompts on the screen to configure the basic settings for the server, such as hostname, IP address, DNS, NTP, security password, application username and password, etc.



  • Select the option to install both CUCM and IM and Presence Service on this node.



  • Wait for the installation process to complete. This may take several hours depending on the hardware specifications of your server.



  • Reboot the server when prompted.



  • Login to the web administration interface of CUCM using the application username and password that you configured during installation.



  • Login to the web administration interface of IM and Presence Service using the same credentials.



  • Verify that both applications are running properly and that they are synchronized with each other.



Congratulations! You have successfully installed the first node of your cluster using Cisco CUCM 9.1 ISO 133. You can now proceed to add more nodes to your cluster if needed.


Touchless install of cluster




If you want to automate the installation process of a new CUCM and IM and Presence Service cluster using Cisco CUCM 9.1 ISO 133, you can use the touchless installation feature. This feature allows you to pre-configure all the settings for each node in a cluster using an answer file, which is a text file that contains all the parameters for installation. You can then use a bootable USB drive or a network share to install all the nodes in a cluster without any user intervention.


To use this feature, you need to follow these steps:


  • Create an answer file for each node in your cluster using the template provided by Cisco. You can find the template and the instructions on how to create the answer file in the official documentation.



  • Save the answer file for each node in a USB drive or a network share that is accessible by all the servers in your cluster.



  • Download the Cisco CUCM 9.1 ISO 133 image from the Cisco Software Download Center. You need a valid Cisco account and a service contract to access this site.



  • Burn the ISO image to a DVD or mount it to a virtual drive.



  • Insert the DVD or mount the virtual drive to the server that you want to use as the first node of the cluster. This node will act as the publisher server for both CUCM and IM and Presence Service.



  • Boot the server from the DVD or virtual drive.



  • Select the option to perform a touchless installation.



  • Specify the location of the answer file for this node, either on the USB drive or on the network share.



  • Wait for the installation process to complete. This may take several hours depending on the hardware specifications of your server.



  • Reboot the server when prompted.



  • Login to the web administration interface of CUCM using the application username and password that you configured in the answer file.



  • Login to the web administration interface of IM and Presence Service using the same credentials.



  • Verify that both applications are running properly and that they are synchronized with each other.



  • Repeat steps 5 to 13 for each additional node in your cluster using their respective answer files.



Congratulations! You have successfully installed your cluster using Cisco CUCM 9.1 ISO 133 with touchless installation. You can now proceed to configure and customize your cluster according to your needs.


Add a node to a cluster




If you want to add a new node to an existing CUCM and IM and Presence Service cluster using Cisco CUCM 9.1 ISO 133, you need to follow these steps:


  • Download the Cisco CUCM 9.1 ISO 133 image from the Cisco Software Download Center. You need a valid Cisco account and a service contract to access this site.



  • Burn the ISO image to a DVD or mount it to a virtual drive.



  • Insert the DVD or mount the virtual drive to the server that you want to use as the new node of the cluster. This node will act as a subscriber server for both CUCM and IM and Presence Service.



  • Boot the server from the DVD or virtual drive.



  • Follow the prompts on the screen to configure the basic settings for the server, such as hostname, IP address, DNS, NTP, security password, application username and password, etc.



  • Select the option to install both CUCM and IM and Presence Service on this node.



  • Select the option to join an existing cluster and specify the IP address of the publisher server of the cluster.



  • Wait for the installation process to complete. This may take several hours depending on the hardware specifications of your server.



  • Reboot the server when prompted.



  • Login to the web administration interface of CUCM using the application username and password that you configured during installation.



  • Login to the web administration interface of IM and Presence Service using the same credentials.



  • Verify that both applications are running properly and that they are synchronized with the publisher server and the other subscriber servers in the cluster.



Congratulations! You have successfully added a new node to your cluster using Cisco CUCM 9.1 ISO 133. You can now proceed to configure and customize your node according to your needs.


Common issues with Cisco CUCM 9.1 ISO 133




High CPU utilization due to I/O wait issue




One of the common issues that you may encounter with Cisco CUCM 9.1 ISO 133 is high CPU utilization due to I/O wait issue. This issue occurs when the CPU is waiting for disk input or output operations to complete, which causes a slowdown in the system performance and responsiveness.


The symptoms of this issue are:


  • The CPU utilization on the affected node is consistently above 90%.



  • The I/O wait percentage on the affected node is consistently above 10%.



  • The system logs on the affected node show messages such as "I/O error", "disk full", "disk timeout", or "disk failure".



  • The users on the affected node experience delays or failures in call processing, messaging, or presence services.



To verify this issue, you can use the following commands on the CLI of the affected node:


  • show process load: This command shows the CPU utilization and I/O wait percentage for each process on the node.



  • show perf query class "Cisco System Performance": This command shows the CPU utilization and I/O wait percentage for the whole system on the node.



  • show diskusage active: This command shows the disk usage and availability for each partition on the node.



  • show status: This command shows the system status and health for the node.



To solve this issue, you can try the following steps:


  • Check if there are any disk errors or failures on the node. If there are, replace or repair the faulty disk as soon as possible.



  • Check if there are any disk space issues on the node. If there are, free up some disk space by deleting unnecessary files or moving them to another location.



  • Check if there are any network issues on the node. If there are, troubleshoot and resolve them as soon as possible.



  • Check if there are any application issues on the node. If there are, restart or upgrade the affected application as soon as possible.



  • If none of the above steps resolve the issue, contact Cisco Technical Support for further assistance.



CUCM reboots periodically




Another common issue that you may encounter with Cisco CUCM 9.1 ISO 133 is CUCM reboots periodically. This issue occurs when the CUCM service crashes or encounters a critical error that requires a reboot to recover. This issue can affect the availability and reliability of the CUCM system and cause service disruptions for the users.


The symptoms of this issue are:


  • The CUCM node reboots unexpectedly and frequently, usually every few days or weeks.



  • The system logs on the affected node show messages such as "CUCM service crashed", "CUCM service terminated abnormally", "CUCM service encountered a fatal error", or "CUCM service requested a reboot".



  • The users on the affected node experience call drops, call failures, or registration failures during or after the reboot.



To verify this issue, you can use the following commands on the CLI of the affected node:


  • show version active: This command shows the software version and build number of the active partition on the node.



  • show version inactive: This command shows the software version and build number of the inactive partition on the node.



  • show network ipprefs all: This command shows the IP preferences and settings for all network interfaces on the node.



  • show status: This command shows the system status and health for the node.



  • show tech notify: This command shows the technical notifications and alerts for the node.



  • file list activelog /cm/trace/ccm/sdl/*: This command shows the list of SDL trace files for the CUCM service on the node.



To solve this issue, you can try the following steps:


  • Check if there are any software bugs or defects that affect your CUCM version and build number. If there are, apply the latest patches or updates from Cisco as soon as possible.



  • Check if there are any hardware issues or failures on your node. If there are, replace or repair the faulty hardware as soon as possible.



  • Check if there are any configuration issues or conflicts on your node. If there are, correct or resolve them as soon as possible.



  • Check if there are any network issues or disruptions on your node. If there are, troubleshoot and resolve them as soon as possible.



  • If none of the above steps resolve the issue, contact Cisco Technical Support for further assistance.



CUCM crashes




A more severe issue that you may encounter with Cisco CUCM 9.1 ISO 133 is CUCM crashes. This issue occurs when the CUCM service stops working completely and does not recover by itself. This issue can cause a total outage of the CUCM system and affect all the users and devices that rely on it.


The symptoms of this issue are:


  • The CUCM node does not respond to any requests or commands from the web administration interface, the CLI, or the network.



  • The system logs on the affected node show messages such as "CUCM service crashed", "CUCM service terminated abnormally", "CUCM service encountered a fatal error", or "CUCM service requested a reboot".



  • The users and devices on the affected node lose all connectivity and functionality with the CUCM system.



To verify this issue, you can use the following commands on the CLI of the affected node:


  • show version active: This command shows the software version and build number of the active partition on the node.



  • show version inactive: This command shows the software version and build number of the inactive partition on the node.



  • show network ipprefs all: This command shows the IP preferences and settings for all network interfaces on the node.



  • show status: This command shows the system status and health for the node.



  • show tech notify: This command shows the technical notifications and alerts for the node.



  • file list activelog /cm/trace/ccm/sdl/*: This command shows the list of SDL trace files for the CUCM service on the node.



To solve this issue, you can try the following steps:


  • Reboot the affected node manually by using the utils system restart command on the CLI or by pressing the power button on the server.



  • Check if the CUCM service is running normally after the reboot. If not, proceed to the next step.



  • Switch to the inactive partition on the affected node by using the utils system switch-version command on the CLI. This will activate the backup software image on the node and reboot it automatically.



  • Check if the CUCM service is running normally after switching to the inactive partition. If not, proceed to the next step.



  • Contact Cisco Technical Support for further assistance. You may need to reinstall or upgrade your CUCM software image or replace your hardware.



CUCM hangs




A less severe but still annoying issue that you may encounter with Cisco CUCM 9.1 ISO 133 is CUCM hangs. This issue occurs when the CUCM service becomes unresponsive or sluggish and does not process requests or commands in a timely manner. This issue can affect the user experience and satisfaction with the CUCM system and cause frustration and confusion.


The symptoms of this issue are:


  • The CUCM node responds slowly or intermittently to requests or commands from the web administration interface, the CLI, or the network.



  • The system logs on the affected node show messages such as "CUCM service is busy", "CUCM service is waiting for resources", "CUCM service is experiencing high load", or "CUCM service is not responding".



  • The users and devices on the affected node experience delays or errors in call processing, messaging, or presence services.



To verify this issue, you can use the following commands on the CLI of the affected node:


  • show process load: This command shows the CPU utilization and I/O wait percentage for each process on the node.



  • show perf query class "Cisco System Performance": This command shows the CPU utilization and I/O wait percentage for the whole system on the node.



  • show diskusage active: This command shows the disk usage and availability for each partition on the node.



  • show status: This command shows the system status and health for the node.



  • show tech notify: This command shows the technical notifications and alerts for the node.



  • file list activelog /cm/trace/ccm/sdl/*: This command shows the list of SDL trace files for the CUCM service on the node.



To solve this issue, you can try the following steps:


  • Check if there are any software bugs or defects that affect your CUCM version and build number. If there are, apply the latest patches or updates from Cisco as soon as possible.



  • Check if there are any hardware issues or failures on your node. If there are, replace or repair the faulty hardware as soon as possible.



  • Check if there are any configuration issues or conflicts on your node. If there are, correct or resolve them as soon as possible.



  • Check if there are any network issues or disruptions on your node. If there are, troubleshoot and resolve them as soon as possible.



  • If none of the above steps resolve the issue, restart the CUCM service on the affected node by using the utils service restart Cisco CallManager command on the CLI. This will stop and start the CUCM service without rebooting the node.



If restarting the CUCM service does not resolve the issue, contact Cisco Technical Support


About

Welcome to the group! You can connect with other members, ge...

Members

  • White Facebook Icon
  • White Instagram Icon
bottom of page