jeschaff
New Member.
788 views

Have you seen these symptoms on your LAGs....


Just curious if anyone has run into this scenario and if so what they
did to fix it.

Running NAM appliance on sles 11 or sles 9 we find that after any
policy push, a reboot of a server, or a core... the ESP throws 403
errors and thus the LAG is useless. This can be traced down in the
browser's http headers or by simply hitting the LAGs health check. We
found that functionally is easily restored by going into the admin
console's audit task and repushing the current config to the offending
box. One of my colleagues also mentioned that he got around it once by
repushing the certs but isn't 100 percent sure on that solution.
Thankfully to date we've only seen this in our pre-production
environment, despite the fact that it is nearly identical to our
production environment (patch versions, hardware, number of servers,
config, etc...).

Anyhow as previously mentioned I was curious if anyone else had run
into this. We are currently in the process of escalating to Novell
support but aren't sure what they will do for us as we are still running
on the sp2 ir patches and hesitant to upgrade due to the stable
environment we've been running for the last year in production.

Thanks,
-Jeff


--
jeschaff
------------------------------------------------------------------------
jeschaff's Profile: http://forums.novell.com/member.php?userid=8222
View this thread: http://forums.novell.com/showthread.php?t=447967

0 Likes
5 Replies
Knowledge Partner Knowledge Partner
Knowledge Partner

Re: Have you seen these symptoms on your LAGs....

jeschaff wrote:


> Anyhow as previously mentioned I was curious if anyone else had run
> into this. We are currently in the process of escalating to Novell
> support but aren't sure what they will do for us as we are still
> running on the sp2 ir patches and hesitant to upgrade due to the
> stable environment we've been running for the last year in production.


I've seen it but it was due to the fact it was still processing
policies, have you tried giving it some time?

--
Cheers,
Edward
0 Likes
jeschaff
New Member.

Re: Have you seen these symptoms on your LAGs....


edmaa;2152331 Wrote:
>
>
> I've seen it but it was due to the fact it was still processing
> policies, have you tried giving it some time?
>
> --
> Cheers,
> Edward
>
>


Unfortunately yes, we have given it as much as 30 mins or more, and
looking at the admin console the health of the LAG is reported back as
green. With no pending policy activity under the server health tab, or
pending actions under the server's command status tab, or for that
matter nothing under the alerts tab. But as soon as a request is
redirected from the application URL to the ESP the browser encounters
the 403 error until we repush the current config to the LAG.

Thanks for the reply,
Jeff


--
jeschaff
------------------------------------------------------------------------
jeschaff's Profile: http://forums.novell.com/member.php?userid=8222
View this thread: http://forums.novell.com/showthread.php?t=447967

0 Likes
Knowledge Partner Knowledge Partner
Knowledge Partner

Re: Have you seen these symptoms on your LAGs....

jeschaff wrote:

>
> edmaa;2152331 Wrote:
> >
> >
> > I've seen it but it was due to the fact it was still processing
> > policies, have you tried giving it some time?
> >
> > --
> > Cheers,
> > Edward
> >
> >

>
> Unfortunately yes, we have given it as much as 30 mins or more, and
> looking at the admin console the health of the LAG is reported back as
> green. With no pending policy activity under the server health tab,
> or pending actions under the server's command status tab, or for that
> matter nothing under the alerts tab. But as soon as a request is
> redirected from the application URL to the ESP the browser encounters
> the 403 error until we repush the current config to the LAG.
>
> Thanks for the reply,
> Jeff


Any chance you can enable debug logging on the ESP and ics_dyn and
provide the log files with a 403 error?

--
Cheers,
Edward
0 Likes
Knowledge Partner
Knowledge Partner

Re: Have you seen these symptoms on your LAGs....


Yeah, I've gotten this before and I think Samantha has seen it as well.
I was never able to duplicate it with enough consistency though to get
Novell the information they needed.


--
The opinions expressed are my own.
Check out my OES2 Guides:
Installing OES2 SP2:
http://www.novell.com/communities/node/11600/oes2-sp2-installation-guide
Upgrading to OES2 with ID Transfer:
http://www.novell.com/communities/node/11601/oes2-sp2-migration-guide-transfer-id-scenarios
GroupWise Migration with OES2 ID Transfer:
http://www.novell.com/communities/node/11602/groupwise-migration-netware-oes2-sp2-transfer-id
------------------------------------------------------------------------
kjhurni's Profile: http://forums.novell.com/member.php?userid=734
View this thread: http://forums.novell.com/showthread.php?t=447967

0 Likes
jeschaff
New Member.

Re: Have you seen these symptoms on your LAGs....


Well our issue was consistent enough. But we were on a very old version
of NAM. So we upgraded from sp2ir1 to sp3 and the symptoms went away.
After that we took a leap of faith and jumped to sp4 since this was in
our pre-production environment.

So far so good with our regression testing.

Jeff


--
jeschaff
------------------------------------------------------------------------
jeschaff's Profile: http://forums.novell.com/member.php?userid=8222
View this thread: http://forums.novell.com/showthread.php?t=447967

0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.