Avaya IP Office Web Manager

[Abdul manaf]

Hello everyone,

I recently migrated our Avaya recording server from one Hyper-V host to another. After the migration, the Avaya IP Web Manager username shows as "root," and I am unable to log in with my credentials.

Has anyone encountered this issue before or have any suggestions on how to resolve it?

Thanks in advance!

 

[lleeNC]

Have you tried using "Administrator" without quotes as the password?

 

[derfloh]

Looks like if the system is not ignited.

IP Office remote service
IP Office certificate check
CLI based call blocking
SCN fallback over PSTN

 

[Travis Harper]

Hello everyone,

I recently migrated our Avaya recording server from one Hyper-V host to another. After the migration, the Avaya IP Web Manager username shows as "root," and I am unable to log in with my credentials.

Has anyone encountered this issue before or have any suggestions on how to resolve it?

Thanks in advance!

Sounds like something was lost in the migration. What you are experiencing is what it looks like when doing a brand new install of IP Office, prior to Igniting it. The default password for root is/was Administrator .Here is a link that explains how to Ignite the server. https://documentation.avaya.com/bun...TheComponentsofMEusingtheIgnitionProcess.html

 

[Menniss]

I am not surprised you have had this issue. I don't use or have many customers that use Hyper-V so can't comment on that.

However I have experience with the same issue on VMWare, a customer recently migrated (without saying anything first) from one host to a new one using a 3rd party management tool and it broken the instance in the same way you describe. Every other VM on host moved without issues it was just the IPO that spat the dummy. If I understand correctly Avaya only supports vMotion to do this in VMware.

We attempted a number of things to correct the access issues but in my experience once this typer of thing has happed it's not worth the grief especially the possibility of future grief in trying to resolve it. You are better to roll back and follow a supportted process.

The customer rolled back and we used the backup and restore process to do this. https://documentation.avaya.com/bun...formWebManagerR11_1/page/Backup_overview.html

Its infuriating that the IPO instance is this fickle but there is nothing we can do about that we just need to work within the constraints that exist.

 

[Travis Harper]

I am not surprised you have had this issue. I don't use or have many customers that use Hyper-V so can't comment on that.

However I have experience with the same issue on VMWare, a customer recently migrated (without saying anything first) from one host to a new one using a 3rd party management tool and it broken the instance in the same way you describe. Every other VM on host moved without issues it was just the IPO that spat the dummy. If I understand correctly Avaya only supports vMotion to do this in VMware.

We attempted a number of things to correct the access issues but in my experience once this typer of thing has happed it's not worth the grief especially the possibility of future grief in trying to resolve it. You are better to roll back and follow a supportted process.

The customer rolled back and we used the backup and restore process to do this. https://documentation.avaya.com/bun...formWebManagerR11_1/page/Backup_overview.html

Its infuriating that the IPO instance is this fickle but there is nothing we can do about that we just need to work within the constraints that exist.

It's bizarre. I have moved my entire instance of IP Office from bare metal, to VirtualBox ( yes it works ), and back to bare metal, using ssh and RSYNC with only minor issues related to the primary NIC MAC Address and WebLM. ..but never has this dumped my entire config and put the platform be back at Ignite stage. Even more bizarre, in this case all that was migrated was the recording server.. assuming ACR/Xima. I have no idea how this would/could hose the entire platform. I agree...its better to roll back , take a backup, build new and restore from the backup.

 

[Menniss]

@ Travis

Bizarre is right, in my case and I suspect from what Abdual is saying it's the same it didn't drop the config the system was running you just couldn't access Web Manger it was behaving like it needed to be ignited.

Actually I missed the comment "Avaya recording server" and honed in on "Avaya IP Web Manager username shows as "root,""

Perhaps the application server with a 500? or server edition. My ESP is broken so can't be sure. Either way the advice is the same.

 

[Michel$]

hi guys,

Lost administrator password, how to reset administrator password through RS 232 port in CLI

please help me

chakibBRAIKI

 

[TouchToneTommy]

chakib - start a new thread for a new question that doesn't pertain to the current thread.
And use Google, here's your answer

Reset all passwords

Passwords can be reset to default values via the RS232 (DTE) Maintenance port

pbxbook.com