About SOCKMD_

SOCKMD_ · ‎04-14-2009

We recently performed an uprade similar to the one you are asking about, from 5.5 to 6.2. I studied the release notes and took a path that was recommended here. As a precaution, I also asked Juniper support what they recommended by opening a support case, and they said I was perfectly fine. However, we ran into som pretty serious bugs after the upgrade, the worst one being authentication servers disappearing when we would create new ones, due to an errornous database pointer after the upgrade. Took JTAC a few months to finally get it fixed, and we still can't update our ESAP files before we do yet another upgrade. What really got me going in all this, was that one of their engineers mentioned that it wasn't advisable to jump so many releases ahead, when we reported one of the bugs. After I explained to him how I had checked release notes AND opened a case before going ahead, he funnily didn't mention it again though. So in short, proceed with caution and better take a few extra steps. Just my 2 cents.

SOCKMD_ · ‎01-27-2009

I'm afraid the only lab box we have is a SA 700, and not much I can do with that on this particular issue. Breaking the cluster is also not an option, as this cluster is in production and out customers paid good money to get redundancy, so we can't just take that away and hope nothing goes wrong while we've done this. I actually tried making a new IVS on the production system, and choose to make it a copy of an existing one. The copy had the same error, so that doesn't solve anything, apparently. Seems the case has just been escalated, so I'm hoping Juniper will take a more serious look at the problem now... Thanks for your answers though guys.

SOCKMD_ · ‎01-22-2009

We have a clustered environment og two SA6000 boxes, in active/passive. Our own company uses it, as well as a number of customers, on overall 16 IVSes so far. We finally took the plunge and upgraded from 5.5R7 til 6.2R3.1. Release notes indicated this was an okay upgrade path to take, and I also called JTAC and had them confirm that this was the recommended release to upgrade to from ours. After the upgrade though, we are seeing quite a few bugs! The most serious one is regarding authentication server. If we try and make a new authentication server, of any kind, og any of teh IVSes, the system will automatically delete one of the older ones! On one of the IVSes it even deleted the authentication server called "Administrators", which normally can't be deleted. Realms and roles and so forth just map to the newly created one, if they mapped to the deleted one. Anyone else seen anything like this? The odd thing, it's only a problem on IVSes made before the upgrade. If we make an IVS and create new authentcation servers, it works as intended. Problem is, we have a lot of local authentication databases, and have no way of exporting and importing all the users in these. Have a JTAC case open on this, but so far they haven't come up with anything at all. So thought I'd post here too, in case anyone has seen anything similar. Thanks in advance for any feedback you can provide on this.

Re: How should I step from 5.5r5 to 6.2r5?

Re: Making a new authentication server deletes a r...

Making a new authentication server deletes a rando...