This discussion has been locked.

You can no longer post new replies to this discussion. If you have a question you can start a new discussion

DON'T update to 6.300

Hi,
6.300 ist a buggy Update (at least with ASG220HA Systems), do not apply it! It seems to have problems with socket handling, SSH, Webadmin will break after some seconds. HA systems will not work any longer after update (they don't see each other)
-Peter

Update:
We went back to 6.203 and updated each HA member for itself. Now one ASG220 is running OK and we will establish HA this night again.

This thread was automatically locked due to age.

Parents

0 pineiro over 19 years ago

Hi,

do you have more informations? I think the Problem that HA dont see the other one is fixed in 6.300. Do you have opened a call at Astaro?
Cancel
Vote Up 0 Vote Down

Cancel
0 ylb over 19 years ago in reply to pineiro

I don't see that should be a problem. I run a HA environment. In earlier relaeses prior 6.202/6.203 I had the problem with the HA not seeing each other - so that's an old Issue. My HA's see's each other just fine on 6.300. :-)
Cancel
Vote Up 0 Vote Down

Cancel
0 pineiro over 19 years ago in reply to ylb

@ylb do you have an ASG320 or 220 or your own Hardware?
Cancel
Vote Up 0 Vote Down

Cancel
0 ylb over 19 years ago in reply to pineiro

Running on Sun hardware, 2 x Sun Fire V20z Opteron based servers. - But I have had the problem with the HA's not seeing each other. What I saw, was that the hot-standby server somehow died, there was no connection to the console directly either.
Cancel
Vote Up 0 Vote Down

Cancel

Reply

0 ylb over 19 years ago in reply to pineiro

Running on Sun hardware, 2 x Sun Fire V20z Opteron based servers. - But I have had the problem with the HA's not seeing each other. What I saw, was that the hot-standby server somehow died, there was no connection to the console directly either.
Cancel
Vote Up 0 Vote Down

Cancel

Children

0 pineiro over 19 years ago in reply to ylb

tnx

Is it Possible that the "dying" Error only on Own Hardware occure or anyone with an ASG have this Problem?
Cancel
Vote Up 0 Vote Down

Cancel
0 NimmdirKeks over 19 years ago in reply to pineiro

Hardlock on the slaves occures on both ASG and "own" hardware. Haven't got any information, if they found what is causing the hardlock.

But it seems to be a software problem.
Cancel
Vote Up 0 Vote Down

Cancel
0 Godsbrother over 19 years ago in reply to NimmdirKeks

Well our HA on ASG320 is now working fine... however the AD auth on the proxy is now broken!! back to transparent mode at present!
Cancel
Vote Up 0 Vote Down

Cancel
0 BrucekConvergent over 19 years ago in reply to Godsbrother

Well our HA on ASG320 is now working fine... however the AD auth on the proxy is now broken!! back to transparent mode at present!

I've noticed after every up2date that we have one customer who uses AD authentication who can't access the proxy service afterwards. We simply go in and "rejoin" the domain, that fixes it up.

CTO, Convergent Information Security Solutions, LLC

https://www.convergesecurity.com

Advice given as posted on this forum does not construe a support relationship or other relationship with Convergent Information Security Solutions, LLC or its subsidiaries. Use the advice given at your own risk.
Cancel
Vote Up 0 Vote Down

Cancel