OpsCenter not connected to master server
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:
- installed OpsCenter, ViewBuilder, ICS and Agent on the Windows host
- checked host2host connectivity (bpclntcmd -ip/hn are OK, ping and telnet on port 1556 work fine)
- checked if the master has the windows host in the "Servers" list -> OK
- checked if /opt/VRTSpbx/bin/pbx-exchange is running on the master -> OK
- checked if nbsl daemon is running on the master -> OK
- "nbregopsc -add" isn't recognized on the master, I assume it only works in NBU 7.0 and above
- in terms of agent configuration, I've created one from the GUI (since the master is 6.5) yet since OC is not connected, nothing gets collected
- I've restarted the OC server multiple times
- checked nbproxy, which seems OK too:
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.
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...