Upgrade Procedure

HA Enabled

• Open console making sure that console version is up to date.
• ssh as root to both nodes
  • Ensure that time and date are within 10sec between nodes
  • Make note of which node is active/passive by:

    # tail /var/log/ha-log

  • Make note of current version by issuing:

    cat /etc/issue

• Check out HA cluster
• Go to Tools, Check For Updates
• Both nodes should authenticate, if one of them fails to authenticate, the wrong password is being used. The HA password should be used during check out.
• Once both nodes authenticate, continue through steps of downloading and sending updates.
• Before starting reboot process start a tail on the active node by issuing:

  # tail -f /var/log/ha-log

• If reboot on passive node does not start automatically, reboot passive node manually. Server will reboot as many times as there are upgrades, i.e. if there are 3 upgrades, the server will reboot three times.
• Once passive node is upgraded, it will become the active node and the upgrade process should start on the remaining node. Again if reboot does not happen automatically, manually reboot to initiate upgrade process.
• Once both nodes have been upgraded, ensure new version by issuing:

  # cat /etc/issue

• Check /etc/ntp.conf file and ensure it has not changed, check peer status with ntpq to be sure and start ntp if necessary:

  Config as of 16-JUL-2008

  #--------------------------------------------------------------
  # /etc/ntp.conf, configuration for ntp
  # ntpd will use syslog() if logfile is not defined
  #--------------------------------------------------------------
  #
  logfile /var/log/ntpd
  driftfile /var/lib/ntp/ntp.drift
  #
  server 141.210.8.1
  server 127.127.1.0
  fudge 127.127.1.0 stratum 13

  Command to start NTPd

  # /usr/local/bluecat/ntp.sh start

No HA Enabled

*Open console making sure that console version is up to date.

• ssh as root to both nodes
  • Make note of current version by issuing:

    cat /etc/issue

• Check out standalone node
• Go to Tools, Check For Updates
• Continue through steps of downloading and sending updates
• Node will reboot, once rebooted
• Once both nodes have been upgraded, ensure new version by issuing:

  cat /etc/issue

• Check /etc/ntp.conf file and ensure it has not changed, check peer status with ntpq to be sure and start ntp if necessary:

  Config as of 16-JUL-2008

  #--------------------------------------------------------------
  # /etc/ntp.conf, configuration for ntp
  # ntpd will use syslog() if logfile is not defined
  #--------------------------------------------------------------
  #
  logfile /var/log/ntpd
  driftfile /var/lib/ntp/ntp.drift
  #
  server 141.210.8.1
  server 127.127.1.0
  fudge 127.127.1.0 stratum 13

  Command to start NTPd

  # /usr/local/bluecat/ntp.sh start