×
INTELLIGENT WORK FORUMS
FOR COMPUTER PROFESSIONALS

Log In

Come Join Us!

Are you a
Computer / IT professional?
Join Tek-Tips Forums!
  • Talk With Other Members
  • Be Notified Of Responses
    To Your Posts
  • Keyword Search
  • One-Click Access To Your
    Favorite Forums
  • Automated Signatures
    On Your Posts
  • Best Of All, It's Free!
  • Students Click Here

*Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

Posting Guidelines

Promoting, selling, recruiting, coursework and thesis posting is forbidden.

Students Click Here

Jobs

Network dispatcher

Network dispatcher

Network dispatcher

(OP)
Hi,

I'm using Network Dispatcher on AIX 5.2 with high availability and load balancing options.

The issue here is that, when I stop ND (ndserver stop) the script "goInOp" is not use whereas GoActive and GoStanby are used. goInOp is suppose to delete the aliase of the cluster on the interface (en1 or lo0 in my case) when ND stops or start for the first time:

ifconfig en1 delete cluster_ip
ifconfig lo0 delete cluster_ip

Any idea of what wrong in my configuration?

Thanx in advance.

Barn.
IBM Certified -- lsuser command user

RE: Network dispatcher

Did you create teh GoInOp script yourself? Does it have execute permission? Also: must be placed in the bin directory where ND is installed...

perhaps ndcontrol executor stop instead of ndserver stop?

Note I do not use ND, I just googled for a user's guide and this is what I came up with:

Quote (ndugv3_us.pdf p. 178):


Problem: Dispatcher high-availability function is not working
This problem appears when a Dispatcher high-availability environment is
configured and connections from the client machines are not being served or
are timing out. Check the following to correct or diagnose the problem:
- Make sure you have created the goActive, goStandby, and goInOp scripts,
and place them in the bin directory where Dispatcher is installed.
- For AIX, Red Hat Linux, and Solaris, make sure the goActive, goStandby,
and goInOp scripts have execute permission set.

also:

Quote (same book p.159):


Stopping the Dispatcher
Stop all functions of the Dispatcher by:
- Entering ndcontrol executor stop (AIX, Red Hat Linux, and Solaris)

HTH,

p5wizard

RE: Network dispatcher

(OP)

Indeed I created it myself.
The three scripts have the mode 755 and are placed in the directory : /opt/ibm/edge/lb/servers/bin

When I use "ndserver executor stop" instead of "ndserver stop" ND doesn't stop any more, plus I've got and error:
"
can not create registry on port 10,099.
java.lang.NullPointerException
blablabla
"

Barn.
IBM Certified -- lsuser command user

RE: Network dispatcher

(OP)
I'm sorry, I used "ndserver executor stop" instead of "dscontrol executor stop".

AND NOW IT WORKS!

goInOp is used. I'll use the both:

dscontrol executor stop
ndserver stop

in a stop_nd.ksh script.

Thank you!

Barn.
IBM Certified -- lsuser command user

RE: Network dispatcher

Good thing you caught it yourself - I would have probably read over it a couple of times until it would have caught my eye...

Allthough I'm a bit curious - manual says "ndcontrol executor stop" - not "dscontrol executor stop" Or is that just another name for the same command?

ndcontrol - Network Dispatcher CONTROL
dscontrol - DiSpatcher CONTROL

HTH,

p5wizard

RE: Network dispatcher

(OP)
/distrib/scripts/nd # ls -l /usr/bin|grep control
-rwx------   1 root     system          526 Oct  6 2003  cbrcontrol
-rwx------   1 root     system          520 Oct  6 2003  ccocontrol
-rwx------   1 root     system          523 Oct  6 2003  dscontrol
-rwx------   1 root     system          520 Oct  6 2003  nalcontrol
-rwx------   1 root     system          523 Oct  6 2003  ndcontrol
-rwx------   1 root     system          525 Oct  6 2003  sscontrol


Same size, I think they are the same command.

I have an other problem now. I can't restart ND properly.

#ndserver start

ends with no error but the executor is not started. When I try to start it:
#ndcontrol executor start

Error : kernel was not loaded.


Is that because I'm in a 64 bits kernel mode? I'm not sure because when I restart the system, "ndserver start" works well. I don't need to start the executor manualy and every think is configure.

Any ideas?

Barn.
IBM Certified -- ls command user

RE: Network dispatcher

Check out if there is something configured in /etc/inittab or /etc/rc.local or... that starts some extra daemon or loads a kernel extension at boot time.

HTH,

p5wizard

Red Flag This Post

Please let us know here why this post is inappropriate. Reasons such as off-topic, duplicates, flames, illegal, vulgar, or students posting their homework.

Red Flag Submitted

Thank you for helping keep Tek-Tips Forums free from inappropriate posts.
The Tek-Tips staff will check this out and take appropriate action.

Reply To This Thread

Posting in the Tek-Tips forums is a member-only feature.

Click Here to join Tek-Tips and talk with other members!

Close Box

Join Tek-Tips® Today!

Join your peers on the Internet's largest technical computer professional community.
It's easy to join and it's free.

Here's Why Members Love Tek-Tips Forums:

Register now while it's still free!

Already a member? Close this window and log in.

Join Us             Close