Avaya Site Admin Acccess to S8300D Survivable Remote Embedded

[wallot]

Folks,

It seems I should be able to access and S8300D via site admin even though it's configured as a survivable remote. I think I used to be able to do this. But since making changes in a survivable anything aren't saved, I usually just test for failover and it always works.

It works in this case as well. However, I'm not sure if I should be able to access it with site admin or not. When I attempt to login in, it takes the initial login and password but then prompts for another login. As soon as I add the login again, it drops the connection. I can replicate this on site and in the lab.

Thanks for any thoughts.

 

[kyle555]

What account are you using for that?

Yes, you should be able to access it with site admin - but you should only do so if you needed to make a change during failover. The changes you make there get overwritten every night by what the main server pushes over, and the changes you make would only be used if the site were in failover.

Nonetheless, you should be able to login, see "LSP - translations cannot be saved" and see a copy of your main system with no gateways registered and nothing online.

Maybe the account you're logging in with is Linux only and not cm enabled? Check the profile of that account in the webpage and try to emulate something that works on your main server to see.

 

[wpetilli]

If you've done a save trans all you should be able to access that 8300 w/your production credentials. Using ASA or by SSH'ng to the box.

 

[wallot]

Thank you, yes, I know abut the save trans all and the transfer of logins and permissions. All of these work fine and do show in the login report with the proper permissions, until I try to access the SAT - either straight via command line or by using site admin.

The SMI is showing a failed login with every attempt to access the SAT. This is with CM 6.3.111. I may delete the template and load the CM 6.3.11 and see whats up.

Thanks again

 

[wpetilli]

That sounds a bit extreme.. the only difference in the .xxx vs .xx was something related to SNMP from what I understand. It shouldn't matter, but have you tried making that 8300 go active and see if it that makes a difference?

 

[kyle555]

I would argue that credentials aren't pushed in a save trans all. I haven't actually checked, but I always thought it was call processing stuff and not admin accounts that were involved in that.

 

[wallot]

Yes, I have made it go active - no difference. Also, I added in a new admin account and waited - didn't show in the LSP until a save trans all was ran.

Thanks folks. I KNOW this worked at one point on past releases - and I think it may be a bug. Just updated to CM SP 115 and no difference either. Probably going to have to open a ticket with Avaya.

 

[wallot]

To kyle555's response that said you would argue that login credentials are pushed from CM core to the LSPs/ESS servers. So, I just did it to prove that doing a save trans all does in fact push the credentials to the LSPs and ESS servers. I also know the syslog IP and the web access configurations are pushed to the LSPs and ESS during a save trans all.

I decided to try the new login I created to access CM on the S8300D, and I was able to access the S8300. The new login was indentical to the other super user in the server.

So, I wanted to prove that the dadmin and siteadmin that are in the core as well as in the S8300D, still didn’t work (which would have pointed to, something anyway). Well, to my surprise, the siteadmin and dadmin logins work now.

It doesn't explain why this happened, as I’ve done quite a few save trans during the day today, but in the end, it seems to be fully resolved.

Since I have CM SP 115 in the server, I can't say if it was the SP that helped or not. As time permits, may go ahead and reload the template and install back to SP111 and retest.

Thanks kyle555 for the mental nudge to trying a new login. Thanks wpetilli as well for your thoughts!

 

[wpetilli]

I know when installing that template it asks you to create a login, which I just use dadmin. I do login with that account to set the SID/MID and the file sync information before running the save trans all. I have my own login that I use to access all my systems (not dadmin)and that begins allowing me access as soon as the translations are pushed. Anyhow, glad you got passed it.

 

[montyzummer]

Good to see you have it sorted , have a look at this thread BSH details some really useful commands on user , this is all done from the CLI of the shell of CM , i guess its a habit but this is how i admin the users on my systems , my reasoning for doing it this way is you are adding direct onto the platform and not with the web interface ,

http://www.tek-tips.com/viewthread.cfm?qid=1602247

ACSS (UC/SBCE/SM/SME)

Not that they mean a thing anymore , get a brain dump pass the test crash the system.