TSE 4.1 sp5 Lim 1 repair - MP issue.

[safron]

Hi All,

Since making a repair of lim1 (due to faulty ASU - drive) I am now unable to use MP.

Each time I try to intergote the system, eg: view extns. I receive 'Authentication error'.

I think this is due to conflict in MTS username/password. On Lim1 rebuild Aastra/Aastra was used which differs from the previous MTS credentials.

Note: MP is installed on lim2.

Does anybody know how I overcome this, do I need to re-install MTS?

Thanks!
Saf.

 

[whosrdaddy]

straight from the manual:

 MP Login: Manager Provisioning on Another Server
When Manager Provisioni
ng is on another server
, either a stand alone
server or a Telephony Server other
than server 1 (for example with ip
address: xx.xx.xx.xx)
, the part tagged
<application-policy
name="WBMLogin">
in the
login-config.xml
file on the Manager Tele-
phony System server, shall
be changed to the following:
If the Manager Provisioning
server is running http:
<application-policy
name="WBMLogin">
<authentication>
<login-module code="se.ericsson.ebc.em.secu-
rity.SoapLoginModule" flag="required">
<module-option name="java.naming.provider.url">
[URL unfurl="true"]http://xx.xx.xx.xx:80</module-option>[/URL]
</login-module> </authentication> </applica-
tion-policy>
If the Manager Provisioning
server is running https:
<application-policy
name="WBMLogin">
<authentication>
<login-module code="se.ericsson.ebc.em.secu-
rity.SoapLoginModule" flag="required">
<module-option name="java.naming.provider.url">
[URL unfurl="true"]https://xx.xx.xx.xx:443</module-option>[/URL]
</login-module> </authentication> </applica-
tion-policy>
After modifying the configurati
on, restart the Manager Telephony
System server with command:
/etc/init.d/eri_om restart

-----------------------------------------------------
Helping people is my job...

 

[whosrdaddy]

Better formatting:

[tt]MP Login: Manager Provisioning on Another Server
When Manager Provisioning is on another server, either a stand alone
server or a Telephony Server other than server 1 (for example with ip address: xx.xx.xx.xx), the part tagged <application-policy name="WBMLogin"> in the login-config.xml file on the Manager Telephony System server, shall be changed to the following:

If the Manager Provisioning
server is running http:
<application-policy
name="WBMLogin">
<authentication>
<login-module code="se.ericsson.ebc.em.secu-
rity.SoapLoginModule" flag="required">
<module-option name="java.naming.provider.url">

http://xx.xx.xx.xx:80</module-option>

</login-module> </authentication> </applica-
tion-policy>

After modifying the configuration, restart the Manager Telephony
System server with command:
/etc/init.d/eri_om restart
[/tt]

-----------------------------------------------------
Helping people is my job...

 

[safron]

Hi,

Thanks for the info and sorry for the delay in reposnding.

I did not edit the login-config xml file, instead I have un-intalled MP and re-installed on Lim1. After recreating the subsystem I was able to click the subsystem and be connected straight through to MTS (Proving this account). Before I would receive (at the bottom in red) incorrect username or password but on typing manually it would connect??

Anyway, the issue I now have is that when I try to 'Remove' an extn in lim1 using MP. This fails..."Feature Not Initiated". The MP/server logs dont tell me much and the 'local message logs' show a transaction which is same as a remove made on an extn in lim2 which works fine.

Note: Same extn can be removed ok using command line.

The documentation talks about using a linux account auhentication as apposed to MP authentication. I dont beleive this is my problem as authentication is now ok, this issue now is deleting extns on lim1 from MP. Note: I tried to set a CDINI on an extn in lim 1, this works ok?

Looks like a lim1 repair causes issues with MP or at least it did with me Anybody else had to repair lim1 experienced issues with MP?

Trying to avoid a total rebuild but looks like the only way forward now to SP6.
___________________________________________

MP Login: Manager Provisioning and Manager Telephony
System on the same Server
__________________________

In a coexistence system the <application-policy name="WBMLogin">
part looks like this:
<application-policy name="WBMLogin"> <authentication>
<login-module code="se.ericsson.ebc.em.security.
SoapLoginModule" flag="required">
<module-option name="java.naming.provider.url">

http://localhost:8080</module-option>

</login-module> </authentication> </application-
policy>
INSTALLING MANAGER PROVISIONING
30 9/1531-ANF 901 15 Uen C7 2011-09-27
This means that Manager Telephony System will login using Manager
Provisioning authentication.
This is set up automatically when Manager Provisioning and Manager
Telephony System are on the same server. There is no need to change
this, unless Manager Telephony System shall login using a Linux user
account authentication.