11-26-2015 06:47 PM
Hi All,
Observed Java login issue in one of our master server post upgrade from 6.5.6 to 7.5.0.7. Both Java GUI login and jnbSA reporting same error. For some reason it is resulting the configured port is 0. Attached the error screen shot.
# cat /etc/services | egrep "pbx|vnetd|bpjava"
pbx 1556/tcp # AshWin CI Tecnologies
pbx 1556/udp # AshWin CI Tecnologies
vnetd 13724/tcp vnetd
bpjava-msvc 13722/tcp bpjava-msvc
nbj.conf
#***************************************************************************
#* $VRTScprght: Copyright 2013 Symantec Corporation, All Rights Reserved $ *
#***************************************************************************
#BPJAVA_PORT=13722
VNETD_PORT=13724
PBX_PORT=1556
NBJAVA_CLIENT_PORT_WINDOW=0 0
INSTALL_PATH=/usr/openv/java
INITIAL_MEMORY=36M
MAX_MEMORY=256M
MEM_USE_WARNING=80
FORCE_IPADDR_LOOKUP=0
USE_NBJAUTH_WITH_ENHAUTH=0
NBJAVA_CORBA_DEFAULT_TIMEOUT=60
NBJAVA_CORBA_LONG_TIMEOUT=1800
FORCE_RESET=1
VNETD_CONNECT_RETRY_TIMEOUT=60
USE_OS_DATETIME_FORMAT=0
NBCSSC_PORT=5637
Solved! Go to Solution.
11-26-2015 11:19 PM
You got a port clash. Its seems both AshWin CI Tecnologies and Veritas both uses port 1556 (google)
Netbackup used 13724 in 6.5 but switched to 1556 in 7.x
My /etc/services look like this:
veritas_pbx 1556/tcp # VERITAS Private Branch Exchange
veritas_pbx 1556/udp # VERITAS Private Branch Exchange
You should ask the application responsbile for Ahwin software to use another port than 1556 becuase 1556 is official assigned to Veritas according to IANA
http://www.iana.org/assignments/service-names-port-numbers/service-names-port-numbers.xhtml?search=1556
11-26-2015 11:19 PM
You got a port clash. Its seems both AshWin CI Tecnologies and Veritas both uses port 1556 (google)
Netbackup used 13724 in 6.5 but switched to 1556 in 7.x
My /etc/services look like this:
veritas_pbx 1556/tcp # VERITAS Private Branch Exchange
veritas_pbx 1556/udp # VERITAS Private Branch Exchange
You should ask the application responsbile for Ahwin software to use another port than 1556 becuase 1556 is official assigned to Veritas according to IANA
http://www.iana.org/assignments/service-names-port-numbers/service-names-port-numbers.xhtml?search=1556
11-26-2015 11:27 PM
According to this comment from a Veritas employee the /etc/service registration is OK
https://www-secure.symantec.com/connect/forums/backups-failing-robotic-issue#comment-9447371
But worth while investigating anyway
11-29-2015 07:18 PM
Hi Nicolai,
Checked replacing the service entry but that did not work as well. for 1556 port do we need to allow both tcp and udp ports in firewall? I suspect something is blocking as it is showing the error as configured port as 0.
Thanks
11-29-2015 10:58 PM
Correct, tell them to go get their own port ....
11-30-2015 12:40 AM
Replacing the text in /etc/services will not fix the port issues. If you already have a application that uses port 1556, Netbackup will not be able to use the same port. You need to stop the previous application so Netbackup can use 1556.
The following command work in Linux to list what command listen at IP port - now you are on AIX, so It require some tweaking
# netstat -tulpn | grep 1556
This should provide a line like this
tcp 0 0 0.0.0.0:1556 0.0.0.0:* LISTEN 2375/pbx_exchange
If you get anything else than pbx_exchange, you got a issue.
Think IP as a street with house numbers, SSH living at 22, HTTP at port 80. Now Netbackup drive down to 1556 just to discover someone is already living at that street address. Now Netbackup get very sorry and drives away. To remedy the issue you need to expel the application using 1556 and call Netbackup to get back and live at 1556.
If you have firewall in place, you need to open port 1556 in both directions.
12-02-2015 09:54 PM
Hi Nicolai, Checked and pbx is the only service using 1556.
# netstat -a | grep pbx
tcp4 0 0 *.pbx *.* LISTEN
tcp6 0 0 *.pbx *.* LISTEN
12-07-2015 07:27 AM
can you do a bpps -a and provide the output ?
Please verify that nbatd is running.
http://www.veritas.com/docs/000023495
12-07-2015 10:46 AM