Veritas-bu

[Veritas-bu] [DC-3.41] Why does it use low ports

2002-10-10 19:15:31
Subject: [Veritas-bu] [DC-3.41] Why does it use low ports
From: keri.sprinkle AT veritas DOT com (Keri Sprinkle)
Date: Thu, 10 Oct 2002 19:15:31 -0400
These ports are defined in your /etc/services file and are reserved for
specific NetBackup processes.  It is possible to change them but is not
recommended unless absolutely necessary.  If you do have to change the ports
you will need to change them for EVERY NetBackup machine in your
environment, all servers and clients.  The port numbers must match across
the board.

-----Original Message-----
From: Arne Kloecker [mailto:arne AT topnet DOT de]
Sent: Thursday, October 10, 2002 10:33 AM
To: veritas-bu AT mailman.eng.auburn DOT edu
Subject: [Veritas-bu] [DC-3.41] Why does it use low ports


Hi,

i have this strange issue with Netbackup DataCenter 3.41.

bp.conf on Master:
[...]
ALLOW_NON_RESERVED_PORTS
CLIENT_PORT_WINDOW = 14000 14100
SERVER_PORT_WINDOW = 14000 14100
[...]

bp.conf on client:
[...]
ALLOW_NON_RESERVED_PORTS
CLIENT_PORT_WINDOW = 14000 14100
[...]

Client does a restore, this are some portions of bprd log:

16:22:10 [11031] <2> getsockconnected: host=MASTERSERVER service=bpdbm 
address=MASTERSERVER-IP protocol=tcp non-reserved port=13721
16:22:10 [11031] <2> getsockconnected: host=CLIENT service=bpcd 
address=CLIENT-IP protocol=tcp reserved port=13782
16:22:10 [11031] <2> getsockconnected: Connect to CLIENT on port 635
16:23:10 [11031] <16> bpcr_connect: bpcr_connect timeout during select after

60 seconds on port 639
16:23:10 [11031] <16> add_msgs_to_progress_file: timed out connecting to 
CLIENT
16:23:10 [11031] <2> getsockconnected: host=CLIENT service=bpcd 
address=CLIENT-IP protocol=tcp reserved port=13782
16:23:10 [11031] <2> getsockconnected: Connect to CLIENT on port 525
16:24:10 [11031] <16> bpcr_connect: bpcr_connect timeout during select after

60 seconds on port 632
16:24:10 [11031] <16> add_msgs_to_progress_file: timed out connecting to 
CLIENT
16:24:10 [11031] <2> getsockconnected: host=CLIENT service=bpcd 
address=CLIENT-IP protocol=tcp reserved port=13782
16:24:10 [11031] <2> getsockconnected: Connect to CLIENT on port 790
16:25:10 [11031] <16> bpcr_connect: bpcr_connect timeout during select after

60 seconds on port 660
16:25:10 [11031] <16> add_msgs_to_progress_file: timed out connecting to 
CLIENT
16:25:10 [11031] <2> getsockconnected: host=MASTERSERVER service=bpdbm 
address=MASTERSERVER-IP protocol=tcp non-reserved port=13721
16:25:10 [11031] <2> getsockconnected: host=CLIENT service=bpcd 
address=CLIENT-IP protocol=tcp reserved port=13782
16:25:10 [11031] <2> getsockconnected: Connect to CLIENT on port 551
16:26:10 [11031] <16> bpcr_connect: bpcr_connect timeout during select after

60 seconds on port 653
16:26:10 [11031] <16> add_msgs_to_progress_file: timed out connecting to 
CLIENT
16:26:10 [11031] <2> getsockconnected: host=MASTERSERVER service=bpdbm 
address=MASTERSERVER-IP protocol=tcp non-reserved port=13721
16:26:10 [11031] <2> start_mpx_main_bprd: server = MASTERSERVER
16:26:10 [11031] <2> getsockconnected: host=MASTERSERVER service=bpcd 
address=MASTERSERVER-IP protocol=tcp reserved port=13782
16:26:10 [11031] <2> getsockconnected: Connect to MASTERSERVER on port 949

Why the heck do they try low ports ? They can't work due to a paketfilter.

TIA
Arne
_______________________________________________
Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

<Prev in Thread] Current Thread [Next in Thread>