01-28-2012 10:24 AM
Hi all,
I'm new to OpsCenter and I'm having difficulties making it communicate with my master server. Current setup:
- master is 6.5.3.1, running on Solaris 9, 32-bit; no media servers in my config
- I've installed OpsCenter 7.0 on a Windows 2003 machine, 32-bit
All went fine with the installation, I had some trouble starting Tomcat but I managed to bypass those and now I have a fully functional server and a nice, clean GUI up and running. What I don't have is a functional connection between OpsCenter and the master. Here's what I did, chronologically:
bpps -x | grep nbproxy
root 4387 26800 0 Jan 20 ? 0:00 sh -c "/usr/openv/netbackup/bin/nbproxy" dblib nbpem_cleanup
root 4388 4387 0 Jan 20 ? 0:01 /usr/openv/netbackup/bin/nbproxy dblib nbpem_cleanup
root 3920 3918 0 Jan 20 ? 0:08 /usr/openv/netbackup/bin/nbproxy dblib nbpem_email
root 26806 26800 0 Jan 20 ? 0:00 sh -c "/usr/openv/netbackup/bin/nbproxy" dblib nbpem
root 26792 26791 0 Jan 20 ? 0:11 /usr/openv/netbackup/bin/nbproxy dblib nbjm
root 3918 26800 0 Jan 20 ? 0:00 sh -c "/usr/openv/netbackup/bin/nbproxy" dblib nbpem_email
root 14478 14477 0 18:27:42 ? 0:01 /usr/openv/netbackup/bin/nbproxy libminlic -mgrIORFile -LicenseManager-3.ior.mg
root 26791 26787 0 Jan 20 ? 0:00 sh -c "/usr/openv/netbackup/bin/nbproxy" dblib nbjm
root 14477 26862 0 18:27:42 ? 0:00 sh -c "/usr/openv/netbackup/bin/nbproxy" libminlic -mgrIORFile -LicenseManager-
root 26807 26806 0 Jan 20 ? 4:36 /usr/openv/netbackup/bin/nbproxy dblib nbpem
I'm guessing I'm doing something wrong here, and I suspect the fact that the agent needs to be installed actually on the master server, NOT on the OC host. If so, please confirm, this particularly important aspect is not clearly stated in the OC admin guide (but I've pretty much given up hopes of seeing proper English and a decent logical flow of ideas in Symantec's documentation, after stumbling upon this: "Either delete the user backup schedule that is a copy from a full or incremental schedule that has the calendar base schedule and recreate the user backup schedule or modify the existing user backup schedule by changing the backup type to full backup and then de-select the calendar base and change it back to user backup type schedule." If someone can translate that, I'd be really grateful...).
If my master is running on Solaris I suppose I'd need the Solaris agent? Is there any patch I need to apply to my version of OC (7.0)? Any authentication issues between the two servers I should be aware of ? Below is the security.conf file from the Windows OC host:
#Last Updated on
#Fri Aug 14 15:58:26 IST 2009
vxss.portnumber=2821
vxss.pbxportnumber=1556
vxss.hostname=localhost
vxss.password=EQWWPZUwh5o=
vxss.username=admin
vxss.domainName=broker
I've already executed on the OC host the following command, with it being the resource broker, to no avail:
./vssat setuptrust --broker <RootBrokerMachine>:<port> --securitylevel high
Thank you for whatever useful advice you can give me.
Solved! Go to Solution.
02-08-2012 02:49 AM
I really am both pissed off and flabbergasted... who would've thought that the culprit for this whole mess is actually ... Symantec? After two agonizing weeks of searching and digging through documentation, knowing that I had done everything by the boook, it turns out that the Agent executable file was blocked by Symantec's own AV!
This is what I saw in my windows host, this time after doing an install in the production environment and actually getting about 10 m of connectivity (the same setup there too- windows agent host+solaris master):
SYMANTEC TAMPER PROTECTION ALERT
Target: C:\Program Files\Symantec\OpsCenter\Agent\bin\OpsCenterAgentService.exe
Event Info: Suspend Thread
Action Taken: Blocked
Actor Process: C:\WINDOWS\System32\svchost.exe (PID 1572)
Time: 07 February 2012 21:35:31
You might wonder if the AV itself is up to date... it is. You guys might wanna look into this, it's completely and utterly retarded to spend so much time on a simple task that would've taken just half an hour to complete...
01-30-2012 08:01 AM
Hello Chronos,
I've read your chronological list. Sorry for the question maybe you only forgot this point:
Did you add the masterserver in OPScenter? (OPScenter > Settings > Configuration > NetBackup > Add)
Regards,
Alex
01-30-2012 08:09 AM
Obivously I forgot to mention that, sorry. The master is still shown as "Not connected" no matter if I delete it/re-add it from the console.
02-02-2012 06:59 AM
1) The Windows Host (OpsCenter) can be the agent host for the Solaris Master
2) Ensure that OpsCenter / Agent / Java ViewBuilder are all running the same version. (Assume 7.0 or 7.0.1)
3) Ensure that the OpsCenter host is listed in the bp.conf file on the master as a SERVER = opscenter_hostname
It should be listed as SERVER = and not MEDIA_SERVER =
4) Configure the agent in OpsCenter first
5) Now configure the Master in OpsCenter
The master should now connect and show online or partially connected.
Please let me know your results, if you still cannot connect, please check your Network route between both hosts, ensure port connectivity (1556), and name resolution for both hosts.
If this resolves you issue, please mark this as a solution
-------------------------------------------------------------------------------------------------------------------------------------------------------
Secondary Issue (Translation)
"Either delete the user backup schedule that is a copy from a full or incremental schedule that has the calendar base schedule and recreate the user backup schedule or modify the existing user backup schedule by changing the backup type to full backup and then de-select the calendar base and change it back to user backup type schedule."
What it should reflect:
Delete the user backup schedule and recreate it manually.
Although it maybe possible to modify and correct the copied User Backup Schedule, it is not recommended.
Technote: TECH154514 has been updated and should be published shortly --- Thank you!
02-06-2012 05:04 AM
Hi Tom,
Thanks for your efforts, but I think I had done all this the first time... just to follow your steps, I've deleted both the master and the agent to re-create them in the order you mentioned.
1. agent, OpsCenter and JavaBuilder are all 7.0.0.0
2. bp.conf is fine:
2. agent is configured as in the attached screenshot (dwinipsngn is the windows host where I've installed OC):
4. below you have the master server's configuration:
5. and yet it's still showing not connected, after multiple restarts of the server:
6. The weird thing is that it seems to connect for a very short period of time (you can see "Last contact") and then it seems to disconnect...
7. connectivity on port 1556 is fine between both hosts:
02-06-2012 05:35 AM
I can see the images have been trunkated, you can just copy the image URL and see the whole thing.
02-06-2012 06:23 AM
I telnet-ed from my windows host to the solaris master on 1556 and it's OK:
root@tbackupngn:/ # netstat -an | grep 10.123.3.16
02-06-2012 03:50 PM
I am not sure if this helps, but this is same thing what you did, but you can try it as option.
delete your master server from opscenter web console;
from master server run this command:
bin\admincmd directory nbregopsc -add opscenter server name.
not sure if this helps you.
also you can try to disable and enable the data collection.
02-08-2012 02:49 AM
I really am both pissed off and flabbergasted... who would've thought that the culprit for this whole mess is actually ... Symantec? After two agonizing weeks of searching and digging through documentation, knowing that I had done everything by the boook, it turns out that the Agent executable file was blocked by Symantec's own AV!
This is what I saw in my windows host, this time after doing an install in the production environment and actually getting about 10 m of connectivity (the same setup there too- windows agent host+solaris master):
SYMANTEC TAMPER PROTECTION ALERT
Target: C:\Program Files\Symantec\OpsCenter\Agent\bin\OpsCenterAgentService.exe
Event Info: Suspend Thread
Action Taken: Blocked
Actor Process: C:\WINDOWS\System32\svchost.exe (PID 1572)
Time: 07 February 2012 21:35:31
You might wonder if the AV itself is up to date... it is. You guys might wanna look into this, it's completely and utterly retarded to spend so much time on a simple task that would've taken just half an hour to complete...