cancel
Showing results for 
Search instead for 
Did you mean: 

Netbackup Appliance - Login Issue

Wangui
Level 4
Partner Accredited

Hi,

I'm setting up a new appliance...straight out of the box.

I put in IP address, DNS, gateway, SMTP and email address details...then my browser hang.

On restart, I can't log into the appliance at all.

I get the error 'Login failed. Please contact your System Administrator.'

 

My set up is that I've connected my laptop to the appliance.

I've tried using different browsers, cleared cache, etc....still giving me the same error.

Please help.

1 ACCEPTED SOLUTION

Accepted Solutions

Mark_Solutions
Level 6
Partner Accredited Certified

Have you worked down the list i provided - if you were in the middle of a config and it went wrong the domain etc may be all wrong .. work down the list:

 

4 Check the following log to determine if a service authentication has failed.
/opt/SYMCOpsCenterServer/logs/OpsCenterServer_out.log
5 If the log shows, Service user authentication failed, perform the following
steps:
■ Check the state of the VxAT service. If the service is down, bring it up.
■ You can check the state of the VxAT service from the root as,
/opt/VRTSat/bin/vxatd.
■ Enter AdminConsole Stop and then enter AdminConsole Start.
■ From the root, check for the VxAT domain, /opt/VRTSat/bin/vssat listpd
--pdrtype ab.
■ Check the host name in the domain and compare it with the host name of
the system:
■ If they are not the same, then your Initial configuration might have been
broken.
■ To resolve this issue, edit the vxss.hostname with the host name of the
system and restart the OpsCenter using the following command:
/opt/SYMCOpsCenterServer/bin/opsadmin.sh stop/start

View solution in original post

11 REPLIES 11

Mark_Solutions
Level 6
Partner Accredited Certified

It can take a while to reset after a re-start

I always configure mine using Putty and do it all from the CLISH - never has a problem that way!!

Take a look at my solution below - pretty easy to do - obviously the last part changes depending on if it is to be a master or a media

 

https://www-secure.symantec.com/connect/forums/appliance-5220-mastermedia-server-configuration-faile...

 

chashock
Level 6
Employee Accredited Certified

I'm assuming you can't connect a monitor/keyboard to see what's going on?

This might seem like a crazy question, but did you change the IP of the ethernet port you're plugged into when you were configuring the appliance?

You could try connecting directly to the IPMI port. The default IP is 192.168.0.10/24.  Plug into the port and point your browser to that IP, log into the IPMI session and fire up the remote console to see what's going on.

Sulivan77
Level 4

What happens when you hook up a console?  Does it let you log in?

 

 

Sully

Wangui
Level 4
Partner Accredited

Strange this is I can log in via CLISH and continue configuration. I can't do it via web console. I need to do it for demo purposes.

 

@chashock - havent' changed any IP addresses.

Mark_Solutions
Level 6
Partner Accredited Certified

If you cannot get in via the web gui it means that the webserver parts are not running for some reason.

Another reboot may help or you could cycle the netbackup services from the CLISH and see if it brings it all back to life.

Wangui
Level 4
Partner Accredited

Hi Mark. I tried the reboot, nothing.

How do I cycle back the Nbu services?

Wangui
Level 4
Partner Accredited

I can access the console but it won't let me log in any more. Message 'log in failed, contact administrator'.

See attached.

 

Edit: sorry...misunderstood your question. No it doesn't let me log in even with that. Can only log in via CLISH now.

chashock
Level 6
Employee Accredited Certified

Agree with Mark.  Take a look at whether the AdminConsole services are running via the CLISH.

Mark_Solutions
Level 6
Partner Accredited Certified

From the troubleshooting guide:

 

About a login error message that does not go away
You may encounter a login error message that states the following, "Please try after
5 minutes". If you receive this error message, and it does not disappear after five
minutes, then you can use the following procedure to diagnose the issue.
To determine why an error message does not go away after a period of time
1 Open the command-line shell on the appliance.
2 Use the following sequence of commands to navigate to the Processes view.
Main > Support > Processes
3 Enter the following command to review the status of the current processes.
AdminConsole Show
You can see that the Appliance Console Server service is down.
4 Check the following log to determine if a service authentication has failed.
/opt/SYMCOpsCenterServer/logs/OpsCenterServer_out.log
5 If the log shows, Service user authentication failed, perform the following
steps:
■ Check the state of the VxAT service. If the service is down, bring it up.
■ You can check the state of the VxAT service from the root as,
/opt/VRTSat/bin/vxatd.
■ Enter AdminConsole Stop and then enter AdminConsole Start.
■ From the root, check for the VxAT domain, /opt/VRTSat/bin/vssat listpd
--pdrtype ab.
■ Check the host name in the domain and compare it with the host name of
the system:
■ If they are not the same, then your Initial configuration might have been
broken.
■ To resolve this issue, edit the vxss.hostname with the host name of the
system and restart the OpsCenter using the following command:
/opt/SYMCOpsCenterServer/bin/opsadmin.sh stop/start

Wangui
Level 4
Partner Accredited

Thanks Mark. Everything is up though. (attached)

Mark_Solutions
Level 6
Partner Accredited Certified

Have you worked down the list i provided - if you were in the middle of a config and it went wrong the domain etc may be all wrong .. work down the list:

 

4 Check the following log to determine if a service authentication has failed.
/opt/SYMCOpsCenterServer/logs/OpsCenterServer_out.log
5 If the log shows, Service user authentication failed, perform the following
steps:
■ Check the state of the VxAT service. If the service is down, bring it up.
■ You can check the state of the VxAT service from the root as,
/opt/VRTSat/bin/vxatd.
■ Enter AdminConsole Stop and then enter AdminConsole Start.
■ From the root, check for the VxAT domain, /opt/VRTSat/bin/vssat listpd
--pdrtype ab.
■ Check the host name in the domain and compare it with the host name of
the system:
■ If they are not the same, then your Initial configuration might have been
broken.
■ To resolve this issue, edit the vxss.hostname with the host name of the
system and restart the OpsCenter using the following command:
/opt/SYMCOpsCenterServer/bin/opsadmin.sh stop/start