|
Home > Archive > WebSphere Edge Server > January 2004 > ND 4.0.3 in KCBR configuration
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
ND 4.0.3 in KCBR configuration
|
|
| zoubir 2004-01-19, 3:02 pm |
| Hi,
I'd installed ND 4.0.3.9 in KCBR configuration on Aix 5.1 ML 02 box in
collocation with IHS server. The problem is when i start ND the server
freezes. It was no core and no error message in system log.
Any idea
Thanks
Zoubir
| |
|
| Zoubir,
Freezes as in complete machine hang (seen from local console) or as in
unreachable on network? If the network problem, then it's probably just
the route issue on AIX 5.1 (alias an address and you will get a new
route that often needs to be deleted).
If console hang, then is there an HA partner? If HA partner, then make
sure your startup scripts is defining HA prior to load the
cluster/port/servers. There is a potential network adapter lockup
problem when having HA partners will collocated servers on each --
avoided by setting up HA first.
Jeff
| |
| zoubir 2004-01-19, 3:02 pm |
| Jeff,
It's console hang (panic kernel). If you mean by HA High Availability, i'd
installed ND on one server only (there is no HA )
JLee wrote:
quote:
> Zoubir,
>
> Freezes as in complete machine hang (seen from local console) or as in
> unreachable on network? If the network problem, then it's probably just
> the route issue on AIX 5.1 (alias an address and you will get a new
> route that often needs to be deleted).
>
> If console hang, then is there an HA partner? If HA partner, then make
> sure your startup scripts is defining HA prior to load the
> cluster/port/servers. There is a potential network adapter lockup
> problem when having HA partners will collocated servers on each --
> avoided by setting up HA first.
>
> Jeff
| |
|
| Zoubir,
I'm not aware of any system panic problems in that version of the code.
If you can set the machine up to save a system dump, I'd recommend
having either the Edge L2 Support team or perhaps AIX L2 support team
analyze the dump to determine why this is occurring.
Jeff
|
|
|
|
|