Guest

Preview Tool

Cisco Bug: CSCup50058 - Migration issues from CUCM 6.x to 10.x due to timezones changes

Last Modified

Jan 23, 2019

Products (3)

  • Cisco Unified Communications Manager (CallManager)
  • Cisco Intercompany Media Engine
  • Cisco Unified Communications Manager Version 10.0

Known Affected Releases

10.0(1)

Description (partial)

Symptom:
Migration from CUCM 6.x to CUCM 10.x  fails using PCD showing an error regarding timezone

"invalid Timezone US pacific"

Conditions:
CUCM 6.x to CUCM 10.x migration

Any servers in the CUCM 6.x cluster is using one of the following timezones:

5 - Africa/Asmera  
49 - Africa/Timbuktu
 60 - America/Argentina/ComodRivadavia
 73 - America/Atka
82 - America/Buenos_Aires
 87 - America/Catamarca
  92 - America/Coral_Harbour
 93 - America/Cordoba
106 - America/Ensenada
 108 - America/Fort_Wayne
125 - America/Indianapolis
133 - America/Jujuy
137 - America/Knox_IN
141 - America/Louisville
 148 - America/Mendoza
170 - America/Porto_Acre
 180 - America/Rosario
 200 - America/Virgin
 223 - Asia/Ashkhabad
 231 - Asia/Calcutta
 234 - Asia/Chungking
 236 - Asia/Dacca
 262 - Asia/Macao
 282 - Asia/Saigon
292 - Asia/Tel_Aviv
 293 - Asia/Thimbu
296 - Asia/Ujung_Pandang
298 - Asia/Ulan_Bator
 309 - Atlantic/Faeroe
 311 - Atlantic/Jan_Mayen
 317 - Australia/ACT
 321 - Australia/Canberra
  326 - Australia/LHI
 330 - Australia/North
 331 - Australia/NSW
 333 - Australia/Queensland
 334 - Australia/South
336 - Australia/Tasmania
 337 - Australia/Victoria
 338 - Australia/West
 339 - Australia/Yancowinna
 340 - Brazil/Acre
 341 - Brazil/DeNoronha
 342 - Brazil/East
 343 - Brazil/West
 344 - Canada/Atlantic
 345 - Canada/Central
 346 - Canada/Eastern
 347 - Canada/East-Saskatchewan
 348 - Canada/Mountain
 349 - Canada/Newfoundland
 350 - Canada/Pacific
 351 - Canada/Saskatchewan
 352 - Canada/Yukon
 354 - Chile/Continental
 355 - Chile/EasterIsland
 357 - Cuba
359 - Egypt
 360 - Eire
401 - Europe/Belfast
445 - Europe/Tiraspol
 456 - Factory
 457 - GB-Eire
 458 - GB
 459 - GMT-0
 460 - GMT+0
 461 - GMT0
 462 - GMT
 463 - Greenwich
 464 - Hongkong
 466 - Iceland
 478 - Iran
 479 - Israel
 480 - Jamaica
 481 - Japan
 482 - Kwajalein
 483 - Libya
 485 - Mexico/BajaNorte
 486 - Mexico/BajaSur
 487 - Mexico/General
 493 - Navajo
 494 - NZ-CHAT
 495 - NZ
 535 - Pacific/Yap
 536 - Poland
 537 - Portugal
 538 - PRC
 540 - ROC
 541 - ROK
 542 - Singapore
 543 - Turkey
 544 - UCT
 545 - Universal
 546 - US/Alaska
 547 - US/Aleutian
 548 - US/Arizona
 549 - US/Central
 550 - US/Eastern
 551 - US/East-Indiana
 552 - US/Hawaii
 553 - US/Indiana-Starke
 554 - US/Michigan
 555 - US/Mountain
 556 - US/Pacific
 557 - US/Samoa
 558 - UTC
 560 - W-SU
 561 - Zulu

Related Community Discussions

Cisco BUG <key>CSCup50058</key>
I am facing a problem with 4 nodes CUCM upgrade using PCD from 6.1(5) to 10.5.2.10000-5 all nodes migrated except one &quot;Invalid timezone&quot;. Based on BUG <key>CSCup50058</key> the target version is under the known fixed releases, and why only one node they all have the same timezone? Do I have to set timezone on all production nodes or only the faulty one and will it only need a single node restart or system restart. Another issue the ESXI hosting this node is using another NTP other than all other CUCM and ESXi ...
Latest activity: Nov 25, 2015
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.

Bug Details Include

  • Full Description (including symptoms, conditions and workarounds)
  • Status
  • Severity
  • Known Fixed Releases
  • Related Community Discussions
  • Number of Related Support Cases
Bug information is viewable for customers and partners who have a service contract. Registered users can view up to 200 bugs per month without a service contract.