Learn about inactive and active nodes when upgrading the Vocera Voice Server in a
clustered environment.
When you perform this upgrade, the first Vocera Voice Server you
configure becomes the initial active node in the 5.3.3 cluster. You
should upgrade an inactive cluster node to 5.3.3 (leaving Vocera Voice Server running
on the active node), move the badges over to this new 5.3.3 server, and
then upgrade the remaining cluster node(s).
Consider the following:
- If you are setting up a cluster as you upgrade, the first machine that you configure
becomes the initial active node.
- If your Vocera system has Vocera Messaging Interface ( VMI) applications that connect to it, you need to coordinate with the integration developer
to schedule updates to those applications before Vocera badge users can begin using the
new system. VMI applications integrate the Vocera system with external systems (such as a nurse call
system).
Important: This upgrade affects Vocera badges in the following
ways:
- Users will experience a short outage (several minutes) while their badges connect
to the upgraded 5.3.3 server for the first time and download new firmware.