"Pending" licenses

Answered Question
Mar 20th, 2009
User Badges:

Hi there,


A prospect customer of ours is having some issues with Auto registering phones, and it means that they now can't add new phones. The symptoms that they've put across to me are a little on the woolly side and we can't get remote access either!


Basically in CUCM 5.x they have the license report that tells them:


Total DLUs:

1260


Used:

1124


Units Remaining:

136


Units Pending:

185


I havent got the exact wording, but the error the customer receives is along the lines that number of unused / pending licenses is preventing them from adding new phones.


Anyone care to explain what the "pending" field does? And why they might have ended up with pending licenses?


Thanks!


Mike.

Correct Answer by Rob Huffman about 8 years 4 months ago

Hi Mike,


You are most welcome! There is no more DBLHelper for 5.x and beyond but there are some good methods to repair replication problems. This answer was recently provided by our good friend Java;


1) Run stop on all nodes that will be reset. Stop CLI will stop any currently running processes and give us a clean slate to restart replication.


2) Go to each server (that will be reset), get on the CLI, and run. "utils dbreplication stop"


3) On pub, run the "utils dbreplication stop" as well.


4) Then, (also on the pub) run "utils dbreplication reset all" command (to reset replication on the pub and ALL Subs.



The commands are described in this doc;


http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/cucos/6_0_1/cucos/iptpappa.html



Hope this helps!

Rob

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (1 ratings)
Loading.
Rob Huffman Mon, 03/16/2009 - 03:37
User Badges:
  • Super Red, 40000 points or more
  • Hall of Fame,

    Founding Member

  • Cisco Designated VIP,

    2017 IP Telephony, Unified Communications

Hi Mike,


I believe the licenses will stay in a "pending" state until the auto-registered phone pulls down a profile after going through the Taps process.



Hope this helps!

Rob

nowcommsupport Fri, 03/20/2009 - 06:07
User Badges:

Cool thanks Rob. I don't believe they're using TAPS, they're just doing it manually!


Any idea on the DBLHelper.exe question?


Thanks!

Correct Answer
Rob Huffman Fri, 03/20/2009 - 06:37
User Badges:
  • Super Red, 40000 points or more
  • Hall of Fame,

    Founding Member

  • Cisco Designated VIP,

    2017 IP Telephony, Unified Communications

Hi Mike,


You are most welcome! There is no more DBLHelper for 5.x and beyond but there are some good methods to repair replication problems. This answer was recently provided by our good friend Java;


1) Run stop on all nodes that will be reset. Stop CLI will stop any currently running processes and give us a clean slate to restart replication.


2) Go to each server (that will be reset), get on the CLI, and run. "utils dbreplication stop"


3) On pub, run the "utils dbreplication stop" as well.


4) Then, (also on the pub) run "utils dbreplication reset all" command (to reset replication on the pub and ALL Subs.



The commands are described in this doc;


http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/cucos/6_0_1/cucos/iptpappa.html



Hope this helps!

Rob

nowcommsupport Fri, 03/20/2009 - 05:44
User Badges:

Ok it turns out that the customer's Subscriber had gone a bit mad, and wasn't getting replication traffic. They plan to reboot later, but is there an equivalant of DBHelper.exe in CUCM 5/6/7?


I don't think they were using BAT, just Auto-register and Super-copy. It was certainly strange behaviour but it was alleviated by deleting devices that werent required.


I'm just curious now as to what the Pending field actually means...

Actions

This Discussion