Video Screencast Help
Search Video Help Close Back
to help
Not able to make it to Vision this year? Get a sampling in the Best of Vision on Demand group.

Opcenter not locating master server

Created: 15 Jun 2011 | 7 comments
jmorehea's picture
0 0 Votes
Login to vote

I am running Netbackup 7.1 and Opcenter 7.1.  When Opcenter was initially installed everything seemed to connect and data transfered over from NOM.  However, now enabling and disabling the data collection results in a non-connection.  I recently deleted the Master so that I may add it back and the error is stating:  Server "  IP    " could not be located. Please confirm that the server is configured for access from OpsCenter and also check if the NetBackup services are running.  BNWsesraser

There have been no major changes to our Master Server that would have prevented further access.  Please advise.

Comments

jmorehea's picture
15
Jun
2011
0 Votes 0
Login to vote

Ok...for some reason, maybe

Ok...for some reason, maybe load on the Master, the server is now partially connected.  Still not where I want to be! 

AudienceofOne's picture
15
Jun
2011
0 Votes 0
Login to vote

it certainly could be load on

it certainly could be load on the master.  Any issues with pbx on the OpsCenter box?  I had an issue with connectivity, and it turns out it was related to a host file that someone had put in place, that had the wrong IP for that master.  Removed host entries and it worked fine.

RonCaplinger's picture
16
Jun
2011
0 Votes 0
Login to vote

Still running OCA 7.0.1, but similar problem

We have a problem with some of the data collection types failing, and the status of the agent then shows "partially connected".  You might want to check your data collection when the status is "partically connected" and see if any of them have failed.

If I disable data collection (takes about 20 seconds for it to take effect and for the screen to update), then enable data collection (again, another 20 seconds), we seem to get data collected for at least a little while, but it eventually fails again.

jmorehea's picture
16
Jun
2011
0 Votes 0
Login to vote

I manually restarted all

I manually restarted all Opcenter services, deleted the master, and readded.  After about 30 mins of readding, it finally partially connected. Completed a dfrag on the Opcenter DB, seeing that when it migrated from NOM, it most likely was only a copy.  24 hours later did a disable -> enable and now fully connected.  I think it was a few things, such as load and initial configuration contributed to issues.  However, can anyone explain the amount of times or the time frame that Opcenter makes contact with the master?  Connection status is solid but is it constantly syncing with the master?  Thanks to all who did and are replying. Hope this helps others.

Edwork's picture
17
Aug
2011
0 Votes 0
Login to vote

Similar issue I met

I got simialr issue. Does anyone could help ?

MikeM11's picture
23
Sep
2011
0 Votes 0
Login to vote

Initial data collection...

Hi, i'm not sure if this is correct in your case but could be worth investigating...

I found that the initial data collection from OCA 7.1 and our BE agent would fail if the initial data collection was over 6000 entries (for us about 2 months job history).  I cannot find a limit in any config files but this may be a hard coded limit?  I am open to correction but this may also be the case with data collection from NBU.

Our environment is brand new so have not experienced this issue with NBU.

Mike

speedfreak's picture
06
Nov
2011
1 Vote +1
Login to vote

Hi   Try below one and let us

Hi

 

Try below one and let us know if it helps

 

Add OpsCenter Server entry to NetBackup master server host properties

Under servers tab

 and then check from opscenter if it is able to locate master server

 Cheers !!!