Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

How to Verify that Symantec Private Branch Exchange (VxPBX) processes new requests

Created: 11 Nov 2013 | 8 comments

Dear all,

We have communications issues with VxPBX process that ultimately causes PBX becomes inoperative. I´m trying to monitor and verify that Symantec Private Branch Exchange (PBX) processes new requests from/to MasterServer/MediaServer.

Anyone can help me on how to monitor if PBX processes new requests please? Any documentation about this critical process (Symantec Private Branch Exchange)?

 

Thanks in advance.

Regards

Operating Systems:

Comments 8 CommentsJump to latest comment

Stumpr2's picture

most people simply do a telnet test to the port to check for connectivity (pbx uses port 1556)

telnet $CLIENT 1556

There are some tips in this old technote that still apply.

GENERAL ERROR: An incorrect or incomplete installation of Private Branch Exchange (PBX) may cause CORBA issues and status code 811 failures on a media server upgraded from NetBackup 5.x to NetBackup 6.x.
http://www.symantec.com/docs/TECH59148

 

VERITAS ain't it the truth?

Marianne's picture

Curious to know what kind of 'communications issues'? 

What are the errors/symptoms?

PBX on master or other servers and/or clients?

Which NBU patch level? Which Linux version?

You should be able to check pbx logs with vxlogview command. Originator id is 103.

You can check pbx connections with 'netstat -a'.

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links

Ah45's picture

Also,

try /usr/openv/netbackup/bin/admincmd/bptestbpcd -client <client name> -verbose -debug

in that you can see pbx connections

ashish.patil01's picture

Just to get a better clarity could you please elaborate more and let us know if the backup jobs are running for your clients or else the netbackup services are not running in this case.

mph999's picture

Don't suppose anyone has actually suggested to look in the PBX log have they .... ;0)

vxlogview -p 50936 -i 103 -S

telnet to PBX port is good, and shows it 'can' accept requests, but doesn't mean it 'is' receiving requests - perhaps nothing is getting sent when it should ...

 

Regards,  Martin
 
Setting Logs in NetBackup:
http://www.symantec.com/docs/TECH75805
 
Marianne's picture

Don't suppose anyone has actually suggested to look in the PBX log have they .... ;0)

I have! See my post above wink

We now need Victor to tell us more about actual issues experienced....

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links

mph999's picture

... don't supose I read all the posts properly .... sorry Marianne ...

 

Regards,  Martin
 
Setting Logs in NetBackup:
http://www.symantec.com/docs/TECH75805
 
Stumpr2's picture

I dont think anyone read the technote I posted as it does say...

TELNET
When performing the telnet test, several lines should be logged during the connection attempt in the PBX (OID 103) log.

CHECK LOGS
Note: PBX has a different product ID (50936) than NetBackup (51216). It also logs to a different place than NetBackup. Its default log location is /opt/VRTSpbx/log/50936-103-...
 

SEE IF IT IS RUNNING
1. To check for a running PBX process, use the bpps -x command:
# /usr/openv/netbackup/bin/bpps -x
...
Shared Symantec Processes
-------------------------
root 563 1 1 Dec 19 ? 201:55 /opt/VRTSpbx/bin/pbx_exchange
If the pbx_exchange process is not displayed, it is not running
To start it, run:
# /opt/VRTSpbx/bin/vxpbx_exchanged start

LISTEN
2. After determining the PBX process is running, its port can be checked with a netstat command:
# netstat -an | grep 1556 | grep -i listen
*.1556 *.* 0 0 49152 0 LISTEN

VERIFY
To verify that the netstat output is displaying information for PBX, the pbx_exchange can be stopped and the netstat command rerun to see if the information for port 1556 is no longer displayed
To stop PBX, use the following command:
# /opt/VRTSpbx/bin/vxpbx_exchanged stop
# /usr/openv/netbackup/bin/bpps -x
# /opt/VRTSpbx/bin/vxpbx_exchanged start
# /usr/openv/netbackup/bin/bpps -x
 

VERITAS ain't it the truth?