cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1768
Views
0
Helpful
10
Replies

7.3.3 Provisioning Error

mfisher
Level 1
Level 1

I have recently been upgrading codecs for three different customers.  Once upgraded to 7.3.3 i get a provisioning error.  All three of these systems (MX700, mx200, and a c20) all have received the error.  I have removed all the provisioning info and readded and still seem to get this error is this a bug? Cant seem to locate anything for TMS/ VCS environment just CUCM stuff. 

10 Replies 10

Jens Didriksen
Level 9
Level 9

I gather you have TMS? If so, go to the end-point details in TMS and uncheck the "provisioned" box found under "Edit Settings/General". Hit "Save"and "Force Refresh".

/jens

Please rate replies and mark question(s) as "answered" if applicable.

Please rate replies and mark question(s) as "answered" if applicable.

under general i only see the following:

name

system type

status

system usage type

system connectivity

network address

system contact

alrt system contact

description

mac address

manufactuer

ip zone

tiem zone and password.  i do not see a provisioned check box.  using 14.1.1

On the Edit Settings screen in TMS, try just clicking the "Enforce Management Settings" button.

Failing that, check the setting on the endpoint itself.  If you're using TMS, set the Provisioning Mode to TMS either via the Web Interface, or via the CLI with the "xconfiguration Provisioning Mode: TMS" command.

If that doesn't work, can you provide the actual error you are receiving?

Wayne
--
Please remember to rate responses and to mark your question as answer if appropriate.

Wayne

Please remember to mark helpful responses and to set your question as answered if appropriate.

Little more information.  So these were existing systems already configured for tms and working correctly.  It wasnt until upgrading to 7.3.3 i received the error Provisioning status- provisioning failed. couldnt connect to server.  All the details are the same as before. So i went in deleted all the provisioning info and reconfigured no luck.  Since then i have enforced management settings, purged and re added the device, confirmed settings to be valid for tms.  

sadly tms upgrade is not in the cards at the moment. 

Yes, I got exactly the same errors after upgrading to TC7.3.3, particularly with our SX10 endpoints.

Since upgrading TMS is not an option, then I guess your only options are either just ignore these errors or roll the systems back to TC7.2.x.

/jens

Please rate replies and mark question(s) as "answered" if applicable.

Please rate replies and mark question(s) as "answered" if applicable.

"i do not see a provisioned check box.  using 14.1.1"

Guess you might have to upgrade TMS as this is available in 14.4.1 and it fixed these provisioning errors for me.

/jens

Please rate replies and mark question(s) as "answered" if applicable.

Please rate replies and mark question(s) as "answered" if applicable.

If you're using MX700s and/or TC7.3.x, you should really upgrade to at least TMS 14.4 which was the first version that properly supports the MX700 and endpoint software versions TC7.3 and newer.

Note: TMS 14.x has also just been announced as going End-of Sale: End-of-Sale and End-of-Life Announcement for the Cisco TelePresence Management Suite (TMS) Version 14.x and it's recommended that you upgrade to TMS 15.x

Wayne
--
Please remember to rate responses and to mark your question as answered if appropriate.

Wayne

Please remember to mark helpful responses and to set your question as answered if appropriate.

Patrick Sparkman
VIP Alumni
VIP Alumni

Using the endpoints web interface, Configuration > System Status > Provisioning, what appears on the provisioning status page?

Are these endpoints be provisioned using TMSPE via your VCS, or just directly managed by TMS?

Also, as Wayne suggestions, you should consider upgrading to TMS 14.4 where the MX200/700 is officially supported.

they are set for tms pe is nto being used just managed by tms. i cannot upgrade. 

What is the provisioning status shown on some of the endpoints through their web interface, see my previous reply.