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.

Article:TECH59148  |  Created: 2008-01-31  |  Updated: 2010-01-21  |  Article URL http://www.symantec.com/docs/TECH59148
Article Type
Technical Solution


Environment

Issue



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.

Error



cancelling job due to 811(failed to communicate with resource requester)

Solution



Symptoms:
Either a new or upgraded NetBackup 6.x media server experiences a problem where backups attempted to a tape storage unit will fail with status code 811 (failed to communicate with resource requester) reported.  However, backups to DSU (Disk Storage Unit) do run - and complete successfully.

This may indicate problems with Private Branch Exchange (PBX).

Troubleshooting:
Check the connection to the PBX port by running a telnet test locally on the media server.  

# telnet localhost 1556
Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.

Connection to localhost closed by foreign host.

Log Files:
Status 811 can be found in the nbjm (OID 117) logs.

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

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-...

Resolution:
Ensure the PBX process is running on the media server, and that it can listen on the defined PBX ports (1556/1557).  The problem may not be related to the installation of PBX (ICS), but a problem with PBX being started or listening correctly.

Things to check:
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

If the startup script fails, further troubleshooting of PBX is required.

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

3. 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

Confirm PBX has stopped by reissuing the bpps -x command.

If, after PBX is stopped, netstat output still appears for port 1556, another process is listening on the NetBackup registered port of 1556.  Either stop that other process, or change the PBX ports.  (It is not recommended that the PBX ports are changed as this will require a change on every NetBackup server involved in this NetBackup environment.)

Supplemental Materials

SourceError Code
Value811
Descriptionfailed to communicate with resource requester

Legacy ID



302182


Article URL http://www.symantec.com/docs/TECH59148


Terms of use for this information are found in Legal Notices