By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
440,686 Members | 1,510 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 440,686 IT Pros & Developers. It's quick & easy.

Use of port 523 from Control Center

P: n/a
We are just starting to use DB2. I have a question about Control Center and
port 523. Our DBA set up a database that listens on port 30280 (I have no
idea where that port number came from...). Our security guy opened that
port so I can access it from my workstation. It seems to work, but Control
Center seems to also want to connect to port 523 first. Since port 523 it
being blocked by the firewall it takes a while to timeout before it connects
to the database at 30280. After this it seems to work fine.

The DBA, who is also new to DB2 (he's an Oracle guy) doesn't see why I
should need access to port 523. Do I? And if I don't, is there any way to
tell Control Center to not even try it? What features am I giving up by not
having access to port 523?

Here's my client info:

================================================== ==========
About DB2 Administration Tools Environment
================================================== ==========
DB2 administration tools level:
Product identifier SQL09050
Level identifier 03010107
Level DB2 v9.5.0.808
Build level s071001
PTF NT3295
================================================== ==========
Java development kit (JDK):
Level IBM Corporation 1.5.0
================================================== ==========

The server is running DB2 9.5 also, on Linux on zSeries.

Thanks,
Frank

Dec 31 '07 #1
Share this Question
Share on Google+
3 Replies


P: n/a
On 31 dez, 14:42, "Frank Swarbrick" <Frank.Swarbr...@efirstbank.com>
wrote:
We are just starting to use DB2. I have a question about Control Center and
port 523. Our DBA set up a database that listens on port 30280 (I have no
idea where that port number came from...). Our security guy opened that
port so I can access it from my workstation. It seems to work, but Control
Center seems to also want to connect to port 523 first. Since port 523 it
being blocked by the firewall it takes a while to timeout before it connects
to the database at 30280. After this it seems to work fine.

The DBA, who is also new to DB2 (he's an Oracle guy) doesn't see why I
should need access to port 523. Do I? And if I don't, is there any way to
tell Control Center to not even try it? What features am I giving up by not
having access to port 523?

Here's my client info:

================================================== ==========
About DB2 Administration Tools Environment
================================================== ==========
DB2 administration tools level:
Product identifier SQL09050
Level identifier 03010107
Level DB2 v9.5.0.808
Build level s071001
PTF NT3295
================================================== ==========
Java development kit (JDK):
Level IBM Corporation 1.5.0
================================================== ==========

The server is running DB2 9.5 also, on Linux on zSeries.

Thanks,
Frank
Hello

port 523 is used to carry db2 administrative instance data streams
(ex: when doing a load through db2 control center, when choosing the
path on the server where thefile is , the server directory list data
go through port 523)
Some admin tools / functionalities wont work fine without it
(specially db2 control center)
Dec 31 '07 #2

P: n/a
Ian
Frank Swarbrick wrote:
We are just starting to use DB2. I have a question about Control Center and
port 523. Our DBA set up a database that listens on port 30280 (I have no
idea where that port number came from...). Our security guy opened that
port so I can access it from my workstation. It seems to work, but Control
Center seems to also want to connect to port 523 first. Since port 523 it
being blocked by the firewall it takes a while to timeout before it connects
to the database at 30280. After this it seems to work fine.

The DBA, who is also new to DB2 (he's an Oracle guy) doesn't see why I
should need access to port 523. Do I? And if I don't, is there any way to
tell Control Center to not even try it? What features am I giving up by not
having access to port 523?
Frank,

The DB2 Administration Server (DAS) listens on port 523 (and this is not
configurable). It provides Control Center with the ability to do
administrative "meta" tasks - like starting/stopping DB2 instances,
executing server-based commands (like db2look) and also provides job
scheduling functionality. It is also tightly integrated into the health
monitor.

The admin server is not *required* -- but if you want to use the GUI
tools you'll find that there a number of things you can't do without it.
If you do most work at the command line, you probably won't miss it.

Dec 31 '07 #3

P: n/a
On Mon, 31 Dec 2007 17:05:57 -0000, Ian <ia*****@mobileaudio.comwrote:
Frank Swarbrick wrote:
>We are just starting to use DB2. I have a question about Control
Center and
port 523. Our DBA set up a database that listens on port 30280 (I have
no
idea where that port number came from...). Our security guy opened that
port so I can access it from my workstation. It seems to work, but
Control
Center seems to also want to connect to port 523 first. Since port 523
it
being blocked by the firewall it takes a while to timeout before it
connects
to the database at 30280. After this it seems to work fine.
The DBA, who is also new to DB2 (he's an Oracle guy) doesn't see why I
should need access to port 523. Do I? And if I don't, is there any
way to
tell Control Center to not even try it? What features am I giving up
by not
having access to port 523?

Frank,

The DB2 Administration Server (DAS) listens on port 523 (and this is not
configurable). It provides Control Center with the ability to do
administrative "meta" tasks - like starting/stopping DB2 instances,
executing server-based commands (like db2look) and also provides job
scheduling functionality. It is also tightly integrated into the health
monitor.

The admin server is not *required* -- but if you want to use the GUI
tools you'll find that there a number of things you can't do without it.
If you do most work at the command line, you probably won't miss it.
Just to expand briefly on this:

* A DB2 server can have multiple database instances which listen on a
configurable TCP port (default 60000)
* A DB2 server can have an optional administration instance which listens
on TCP _and_ UDP port 523 (this is not configurable)
* Databases belong to database instances; the administration instance does
not contain any databases - it only exists to support additional
functionality (as detailed by Ian above)

In other words, if you need the GUI tools, you'll need to open TCP and UDP
ports 523 on the firewall (not sure what it uses UDP for, but it listens
on it).

Cheers,

Dave.
Dec 31 '07 #4

This discussion thread is closed

Replies have been disabled for this discussion.