Questions about GSS software upgrade

[wilson_1234_2]

I am in the process of staging an upgrade for a GSS cluster, we currently have three devices that need a software upgrade.

The current version is gss-3.0.2.0.0-k9upg, upgrading to gss-3.2.0.0.15-k9.upg.

According to TAC, nothing needs to be done other than copy the file and issue the begin upgrade process.

Currently the directory in the GSS devices loook like the following:

drwxrwxrwx   3 root root       4096 Jul 29 10:57 .

drwxrwxrwx  21 root root       4096 Jul 29 10:57 ..

-rw-r--r--   1 root users       304 Jul 29 11:05 .bash_logout

-rw-r--r--   1 root users       191 Jul 29 11:05 .bash_profile

-rw-r--r--   1 root users       124 Jul 29 11:05 .bashrc

drwxr-xr-x   2 root root       4096 Apr  3  2007 .ssh

-rw-r--r--   1 root users 187760681 Jan  9  2009 gss-2.0.2.0.0-k9.upg

-rw-r--r--   1 root users 188784681 Jan  9  2009 gss-2.0.3.0.0-k9.upg

-rw-r--r--   1 root root       3634 May 11  2010 proximitySchema.xsd

-rw-r--r--   1 root users      1301 Jan  9  2009 startup-config-01-09-2009

-rw-r--r--   1 root root       3523 May 11  2010 stickySchema.xsd

I do not know how the other images were loaded onto the GSS, but the only way I could do it was enable FTP on the GSS and push the file up with and FTP client, the directory now looks like:

drwxrwxrwx   3 root root       4096 Jul 29 10:57 .

drwxrwxrwx  21 root root       4096 Jul 29 10:57 ..

-rw-r--r--   1 root users       304 Jul 29 11:05 .bash_logout

-rw-r--r--   1 root users       191 Jul 29 11:05 .bash_profile

-rw-r--r--   1 root users       124 Jul 29 11:05 .bashrc

drwxr-xr-x   2 root root       4096 Apr  3  2007 .ssh

-rw-r--r--   1 root users 187760681 Jan  9  2009 gss-2.0.2.0.0-k9.upg

-rw-r--r--   1 root users 188784681 Jan  9  2009 gss-2.0.3.0.0-k9.upg

-rw-r--r--   1 root root  194426922 Jul 29 10:36 gss-3.2.0.0.15-k9.upg

-rw-r--r--   1 root root       3634 May 11  2010 proximitySchema.xsd

-rw-r--r--   1 root users      1301 Jan  9  2009 startup-config-01-09-2009

-rw-r--r--   1 root root       3523 May 11  2010 stickySchema.xsd

Why does my file show up as "root root" and the others are "root users"

Does it matter this file is not the same as the others?

Is it possible to change the file to "root users"?

[Daniel Arrondo Ostiz]

Hi Wilson,

I'm afraid I'm not sure on the reasons why the previous images were showing under the "users" group. My guess is that the behavior of the FTP process was slightly different in earlier releases.

What I can say for sure is that it's currently expected to see any files copied through FTP as "root root" and that anyway, since the installation commands are executed with root priviledges anyway, it makes no difference.

Regards

Daniel

[wilson_1234_2]

Thanks for the reply, I have a couple more question regarding the upgrade process:

I have three GSS devices, my understanding is that I do nothing to the secondary devices and launch the upgrade process on the primary, is this correct?

If so, do the backup devices take over the DNS functions of the primary, while primary is rebooting?

Once the primary is back on line, my undestanding is the backup devices will no longer communicate with the primary du to different software releases, is this correct, or are they all off line?

When the primary is back up and active (relating to above question), will it immidiately begin to answer DNS requests?

[Daniel Arrondo Ostiz · Accepted solution]

Hi Wilson,

See my answers inline

I have three GSS devices, my understanding is that I do nothing to the secondary devices and launch the upgrade process on the primary, is this correct?

You should always upgrade the primary GSSM first, but doing this upgrade will not automatically trigger upgrades on all the other devices, you will have to upgrade each device manually.

If so, do the backup devices take over the DNS functions of the primary, while primary is rebooting?

Not exactly because the GSS has no real redundancy. As far as DNS answering is concerned, each device is independent. Therefore, requests sent to each device while it's rebooting will fail. However, this should not be a problem in most setups because either all the GSS are configured on the clients or some load-balancing is in place to avoid any outage due to a possible failure of one of the devices

Once the primary is back on line, my undestanding is the backup devices will no longer communicate with the primary du to different software releases, is this correct, or are they all off line?

They secondary devices should still be able to talk to the primary GSSM even after the upgrade

When the primary is back up and active (relating to above question), will it immidiately begin to answer DNS requests?

Yes, it will start answering immediately

[wilson_1234_2]

Thanks for the prompt replies,

Are you up for some more questions about GSS operation kal keepalives?

[Daniel Arrondo Ostiz]

Hi Wilson,

I'm happy to help out with those new questions, but, it's better if you open a separate thread for them. This way the answer will be easier to find by other people in the future.

Daniel

[wilson_1234_2]

Will do, starting a new post.

Last couple of questions on this:

We have three devices

GSS Primary

GSS registered to primary

GSS Secondary

When launching the upgade process on the Primary (first one to upgrade), does anything need to be done to the other devices?

How long before the Secondary unit promotes itself to the Primary?

Will it automatically resume as Secondary once Primary is back on line?

Updated questions:

When the primary device is off line, then the configureation, then the gslb-config would have to be on all devices, is this correct?

This would allow the remaining devices to answer DNS requests when the primary is unavailable. is this correct?

[wilson_1234_2]

Daniel,

Please see new questions