MC / Service Guard 11.13 or 11.14

[Justin Willoughby]

Ok, first question 11.14 has been out for a bit now, would any one suggest not going to 11.14? (I am doing a rolling upgrade from 10.10).

Next question, I am doing a cold install during the rolling upgrade going from 10.20 to 11.00, should I wait until after I install MC / Service Guard before I apply the patch bundles from the support plus CD so that any patches for MC / Service Guard are applied?

Thanks,

- Justin

[A. Clay Stephenson]

I've had no problems with 11.14. Yes, you should install MS/SG fairly early in the process (and any other software suites for that matter, e.g. OnlineJFS, Mirror/UX, Glance, ... ) and then apply the patch bundles.

[Sebastian Galeski_1]

Hi
my friends installed last weekend MC/SG 11.14 anduring tests he has some problem with LAN card switching back after failure. He is not sure that this is a 11.14 problem but maybe. How it looks like:
He plug off network cable, so the IP moved to backup bridged lan card so then he plug in this cable again and ip didn't move back to primary card. Maybe there was a problem with switch to which one the lan card are connected, but there was no more time for tests. He is going to use hub and then he will be sure about this issue. I would install 11.13 because it is really tested in a lot of different configuration and work properly.
For your second question:
1. Install HPUX 11.00
2. Install all application
3. Install patch bundles

regards Seba

[Jeff Schussele]

Hi Justin/Sebastian,

MC/SG will not move the LAN from secondary to primary UNLESS the secondary fails, I believe.
If you want it back on primary and secondary is OK, you have to manually move it.
I don't believe this is a *problem* you're seeing in 11.14.

Rgds,
Jeff

[Stephen Doud · Accepted solution]

Hello Justin,

SG11.14 is yet another incremental release of ServiceGuard. Though we have not seen an unusual increase in call volume at the response center for version 11.14, it is our continuing recommendation to load the patch for whatever version of SG you are running. For 11.14 it is presently PHSS_26056 after loading ServiceGuard itself.

As for the sequence you follow when applying the patch bundle from the support-plus CD, it really doesn't matter since non-ServiceGuard patches are independent of SG, and I believe there is no SG patch in the bundle.

As for Jeff's statement... every NETWORK_POLLING_INTERVAL, ServiceGuard checks the tranmission ability of each card listed in
the current cluster ASCII configuration file. If any are found unable to transmit, that LAN is labeled "DOWN" (see syslog.log) until the next polling interval. When it is found to be "UP", it resumes it's duties.

Primary LAN outage
This means that if a primary LAN (LAN w/an IP) is found unable to
transmit, it is marked DOWN and if there is an UP standby LAN for it, it's traffic will be passed to the standby LAN. If no STBY
exists, it is marked DOWN until the next test decides it's status. When a primary LAN returns to UP state, ServiceGuard returns the NIC to activity by routing normal traffic through it - effectively putting the standby LAN back on standby (if one exists).


Standby LAN outage
Since the standby LAN has no IP assigned to it, it does not handle traffic. It is however tested at the same frequency as the primary
LAN and marked DOWN, or returned to UP state as it's status is discovered each test period. (see syslog.log)

-s.

[Jeff Schussele]

Hi (again) Justin,

I'm sorry, I don't know where my head was on that reply - a real brain-lock that was. I must have been thinking package & virtual-IP....
But Stephen is entirely correct the LAN IPs will come back to primary from alternate when they become available again.
Sheesh....I must have had too much sun over the weekend ;^)
N/A please...wish you could lower the earlier as well....

Rgds,
Jeff

[Justin Willoughby]

Hay Jeff,

No problem. It happens to us all. :-)

Not sure what they did with the N/A here, guess they got rid of it. Just put a 0. I think N/A sounds better then 0. Oh well.

- Justin