LSP upgrade to version 4 access problem

[Pauly55]

I have recently installed an LSP onto a G700
The install went well.
I added local accounts and loaded the licesne file and authentication file with no problems.

However as soon as the LSP syncronized with the main 8720 server.
I am no longer able to login to the lsp by the browser or ASA, its says invalid user name or password.

I have added more accounts on the central 8720 and syncronized successfully but I still cannot get access.
Any Idea's anyone ?

 

[Voicedataman]

What ver of CM are you using. Did you do a reset sys 4 on the LSP, is it a G350? You should not be able to add local accounts on the LSP, when it registers with the Main G700 you should use the same username and password as you use on the G700 Main site, as it syncs with the main site.

 

[Pauly55]

Its a version 4 running on a G700
The main site is also a version 4

It works perfectly until its syncronizes then the account a dadmin account no longer works
I used the same password on the central server as on the local lsp

I have even added new users accounts onto the central server and syncronized, they also dont let me log into the LSP
:-(

 

[caspian11]

This is a known problem at Avaya. I called in and they were able to fix it, but they didn't tell me what the fix was.

 

[Pauly55]

Thanks for lettig me know
I will open a case and see what happens

 

[Ronster]

dadmin needs to be added to susers in linux.

Ronster

Science is the rehab of the masses.

 

[Pauly55]

I added dadmin and a super user account
using the web admin tool "accounts" etc
I was able to log in with the account and finish the install.
Until it syncronised with the main server, now i cant login

if i added the account using the web tool, do you know if it makes a difference then using the command line in Linux

Thanks
Paul

 

[big70]

Before you sync make a new user with only prof 18

You can use this login to get in after its syncronized.

So add first a user dadmin prof2,prof 18 then a user xxxx prof 18.


Greets Peter

 

[g3rguy]

Because of changes to CM login administration in CM4, the SAT
list logins command no longer exists, and the Maintenance Web
Interface offers no way to view the already-administered customer
logins. System administrators are reduced to grepping through
/etc/passwd and /etc/group using the BASH CLI to attempt to
discover what logins they already have, and what profiles are
associated with those logins. This EI customer, XXXX
considers this deficiency to be unacceptable and informed the Product
Introduction engineers that it is inconceivable that Avaya would
roll-out a new GA release with such a deficiency. Other
customers and business partners as well as internal services
associates concur in this assessment.

This particular customer and others want badly for the SAT login
administration conventions to remain exactly the same as in CM3,
but that is unlikely due to the incompatibility of such a scheme
with industry imperatives for Authentication, Authorization, and
Accounting (AAA) architecture and design. Applications like CM no
longer drive AAA: they are now clients of centralized server-based
implementations in which all applications look to a single central <<<<<
authentication source for login administration.

CM4 design complies with the new AAA concept by moving local host
account login administration out of CM4 and into the Linux platform
and offers login administration tools via Linux Command Line Interface
and via Maintenance Web Interface Options. Web Pages are the preferred
login administration method, but the CM4.0 release offers no web option
to view the customer's previously-administered local host account logins
and their related profiles on the same page. (Local host accounts are
those accounts whose AAA database information is stored entirely locally,
on the Linux server).

 

[Pauly55]

Thanks everyone for your answers
I will try the prof 18 on the lsp and see what happens
I think I will have to reininstall as I have no method of access at the moment.

Paul