Was it an “in place” upgrade? If not check if anything changed with the CM Groups during the upgrade. Sometimes people just upgrade the publisher, and build in new subscribers (if this happened, I’d also make sure any custom MoH files are on all nodes and not just the publisher). When you do that, it will remove everything from the CM groups and the nodes have to be manually added back and in the correct order.
Did anything change with the UC Services? Thanks, Ryan Sent from my iPhone On Jul 17, 2018, at 20:47, Lelio Fulgenzi <[email protected]<mailto:[email protected]>> wrote: shot in the dark here - we're working with a partner who has upgraded our cluster from v9 to v11.5. we noticed that MRA (first time) logins are taking significantly longer. some captures show that MRA clients are being served up the ip address of the publisher for tftp services as well as the primary (only) tftp server. we use _cisco-uds SRV records for on-prem so the deployment document confirms no settings of tftp server as i recollected. the MRA deployment guide talks about refreshing the nodes - but that's been done a few times. we'll be opening a case in the morrow but just wondering if anyone has run into this? --- Lelio Fulgenzi, B.A. Senior Analyst, Network Infrastructure Computing and Communications Services (CCS) University of Guelph 519-824-4120 Ext 56354 [email protected]<mailto:[email protected]> www.uoguelph.ca/ccs<http://www.uoguelph.ca/ccs> Room 037, Animal Science and Nutrition Building Guelph, Ontario, N1G 2W1 _______________________________________________ cisco-voip mailing list [email protected]<mailto:[email protected]> https://puck.nether.net/mailman/listinfo/cisco-voip
_______________________________________________ cisco-voip mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-voip
