NBU Appliance Admin access via putty ssh is denied

[Yet]

I've been loggin in remotely to NBU appliance via putty ssh until I configured SRM (IPMI) and practically click Console Redirection button. After that I cannot log in anymore to appliance via putty (access denied), though login directly to appliance via KVM is fine.

How can I bring the access back? Any idea?

Appliance 5230, Media server role, ver 2.6.0.3.

[DPO]

Try reconfiguring your network (IP address ) of the appliance from IPMI and then login using putty

[Yet]

I configured ip address thru web console and putty (before it went out), but not sure how i can use IPMI on configuring ip address & bonding? I used IPMI thru java and it does not seemed to giv eme any clish access.

[Veerendra]

Check this below link for how to configure the IPMI from the BIOS. You can also configure the IPMI from Appliance CLISH also.

http://www.symantec.com/business/support/index?page=content&id=HOWTO94363

check this  below Technote for  to how to access the Appliance IPMI. it should be java enabled web browser not the putty as its a http and https service. you cannot use bonding for the IPMI ethernet port.

http://www.symantec.com/business/support/index?page=content&id=HOWTO94393#v87211141

[Veerendra]

its look like your keyboard might be in caps lock or anyother keyboard layout is configured. can you confirm once you are password is correct by typing on a text notepad and once its confirmed try to login again .

[Yet]

Thanks for the reply. Keyboard is just fine.

I lost the access on production network (bonded) not on IPMI.

Any idea? 

[SYMAJ]

I have seen something similar when the customer set the IPMI address to the same as the appliance address - this gave rise to a message when we logged on stating that USER NOT AUTHORIZED.  This message was issued when they logged in via Putty or via a direct console onto the appliance.  Once the IPMI address was corrected (to something other than the actual appliance IP address) all was OK.

I reconfigured the IPMI address via the BIOS screen (F2 at boot time from a directly attached monitor and keyboard).

As above - watch for keyboard mapping - I see the @ symbol being a shift+2 as opposed to the @ key itself when using direct attach keyboard/monitor or IPMI.  Can be sorted by correctly mapping the keyboard.

AJ

[Yet]

Thanks, but production network has different segment that management (IPMI) network. It's only via putty or remote access SSH that is not allowed, loggin in from KVM is OK.

Any idea is much welcome.

[Veerendra]

We can suspect some of these reasons , We all know these all are silly but sometime  they effect a lot.

1).Are you connecting the Appliance using FQDN or ip ? if it is FQDN try to ping it before you connect so that you can confirm there is no problem with FQDN as some time due to hosts file entries it might redirect to some other server.

2). Can you check the status of the bonding by login into the appliance directly? check the status of bonded ethernet connection status.

3). if you installed Netbackup admin or Java console then try to connect to the Netbackup and see what is happening so that you can confirm the connectivity between the system and Appliance.

4).Check with Unix Os support team whether they have configured any ip allow subnetting access  restriction on the Appliance.

5).If you fail all of the above try to connect to the eth0 management port and try to access it from there.