DSML Provider, Status - Failed.

[element4749]

Was hoping someone could help me out. I had some bugs with One-X Portal, I decided to reinstall.

Prior to reinstall, I had no issues synchronizing the directories, the two IPO's that I have were communicating just fine with the DSML Provider.

After I reinstalled, now the provider can only see one of my IPO's. The IPO that the DSML provider cant communicate with is reachable through the diagnostics > IPO Connections.

I have left the default passwords on everything.

Any ideas?

 

[element4749]

Wanted to bump this as this issue is driving me nuts. After some searching I found a really old post regarding a very similar issue:

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

However, in the link - the poster stated that it was fixed with the latest version of One-X at the time. I am running the very latest OneX software available from support.avaya.com

I have tried all of the following:

Reinstallation

Checked firewalls - none on

Removed the DSML provider from the problem unit and readd but not restarting services.

Checked the default EnhTcpaService user password on my IPO and made sure that it was default. - I even defaulted all of my security settings.

Heres the interesting thing, if I remove the DSML proider from OneX for the specific trouble unit, then readd, but restart services, it tends to initially communicate. But after a short while, it fails again, and remains in a failed state.

Since my other IPO is always fine and can communicate with it's DSML provider. I am leaning towards it having something to do with the other IPO itself.

Is there something not documented in the knowledgebase? I am trying to figure out what other type of communication exists between One-X and the IPO.

I did an Apache Chainsaw capture as I was removing and readding the provider and really did not see much...

Any ideas? Is there a new One-X version not listed on support.avaya?

 

[hairlessupportmonkey]

does your version of one-x portal match the version of software for your switch?

I generally only see this if say, you install 6.1 one-x app and try to connect it to a 6.0 or lower switch.

ACSS - SME

 

[element4749]

God I wish that was the case, but both of my IPO's are on 6.1(5) and One X is 6.1.17

 

[hairlessupportmonkey]

have you tried installing one-x onto a temp machine to replicate the issue?

ACSS - SME

 

[tlpeter]

Is there anything else installed on the server besides 1XP ????

When you pay peanuts, you get monkeys!

I'm not insane, my mother had me tested!

 

[element4749]

I did Haireless, I tried a much beefer server than what it is currently installed on.. it was doing the same thing. I had since rolled back to the other.

And very minimal applications installed tlpeter; adobe air, adobe reader, ccleaner, I let One-X install the Java platform as I thought my previous version was causing the issue. Visual C++ 2005, my audio driver, Ie 8 and Server 2003 sp2.

 

[tlpeter]

Did you try a dedicated server?
Try a virtual machine and also try the linux version.
See what happens then.

When you pay peanuts, you get monkeys!

I'm not insane, my mother had me tested!

 

[NYSTECH]

I has seen something similar. database at remote site would not sysnc.. the site was reachable through the IPO connections diagnostics.. Can you web to the remote IPO from one X server and get the Avaya splash screen? I found out after I could not that an update had been done to firewall and a port was blocked... It isn't just 8080 that needs to be open..

 

[element4749]

I did try this on a completely seperate dedicated server. I have not tested a VM yet or on linux. I guess I could try that.

Actually NYSTECH, in this case my remote IPO and DSML provider is perfect. It's the local IPO which is on the same subnet as the OneX Server. Which is reachable through the diagnostics of OneX / and is completely routeable.

What do you mean web to the IPO? If I throw

http://IPOAddress

in my web browser it just shows "Maximum number of Post Requests Exceeded
"

 

[NYSTECH]

You can enter the IP address of the IP office in browser and if it is communicating properly you should get Avaya splash screen.

 

[element4749]

Do I need to specifiy and ports on the address? or just

http://192.168.1.10

as an example?

or something like

http://192.168.1.10:80

etc.

And what if I dont see the avaya spash screen =P

 

[NYSTECH]

http://192.168.1.10

If you don't see it then something is blocking it...
Also, if you have "Avaya HTTP Clients Only" setting in the config you will not be able to access this page.

 

[hairlessupportmonkey]

back up the config, default the switch, restore.

will that be possible onsite?

ACSS - SME

 

[element4749]

Hairless,

Not really - I mean I'd have to do it off hours. I am trying to save that as a last resort so to speak.

Also, when I browse to the URL of the IPO, I see "Maximum number of Post Requests Exceeded" - I am not only verifying port 80 anyway though?... so I am not sure what this would verify.

 

[element4749]

So just an update to this. After I reboot the IPO, the DSML Provider shows available pretty much right away. Then it eventually fails again. So its certainly something with the IPO itself. Any other ideas before I need to resort to blowing the config?

My concern is that whatever is causing this to happen in my current config, will just be replaced when I import the same backed up config... any other ideas?

Thanks in advance.

 

[NYSTECH]

Has this ever worked? You said you had bugs before that is why you reinstalled..Did you follow the DOCS when you installed/ What were the bugs.. Avaya support told me to try the URL thing when they were troubleshooting my issue,, and since I could not get the avaya spalsh they figured something was blocking it, Eventhough it showed connected in DSLM provided on 1x portal.. and the diagnostic could connect to IPO.They were correct. Customer upgraded firewall and did not tell me.. Had them open ports and it worked.
Have you opened a case with Avaya?

 

[element4749]

Did not open a case with them just yet.... about to though. It has worked for me just fine on older software rev's. This is really the only issue that I have had with 6.1. Just so happens to be the first oneX install specifically on 6.1 that I have done. As far as following the docs..I will make sure there is nothing different for 6.1, but its normally pretty straightforward.

I am pretty sure that the bugs that I was referring to before was basically the same issue, just wanted to skip the long explination beforehand.

What rev were you on with that customer?

There is no firewall turned on at all on the One-X server. Its perfectly routeable to the IPO, same subnet, same vlan, off the same switch etc.

 

[NYSTECH]

6.0.18 IPo and the corresponding 1x portal version

 

[tlpeter]

Still sounds like the "http clients only" for me.
Is it turned on or off?


When you pay peanuts, you get monkeys!

I'm not insane, my mother had me tested!