How does Prognosis (11.5) behaves when the server it's running gets renamed and its IP address ges changed?
Can this cause issues to Prognosis? It's collectors? It's components (PGSQL, RabbitMQ, etc...)?
Here, I'm voluntarily focusing on the Prognosis application and excluding any third party devices or applications like CUCM, Avaya CM, etc... These will obviously have to be reconfigured to send CDRs, RTCP streams, traps, syslogs, etc... to the new server IP.
Solved! Go to Solution.
Having looked at the planning phase in session one of this series, we will turn our focus to the readiness phase. The all important technical capabilities assessment, ensuring the network, endpoints and users are adequately prepared for the move.
Hear first hand from IR's Global Head of Information Systems and Technology, Jason Schwendinger, on how he has been tackling these issues.Join webinar