ComWin (connection rejected by transportservice, check transpoirt service name)

[OKACHA]

hi ;

we have a hipath 4000 (duplex / DSCXL2) that was working correctly, we had only the problem of SLES Linux blocked until today we can't access to the comwin as you could notice in the joined photo in the assistant page we have the message "unbale to connect to RMX ".
any help, please. may I reboot the system without problems.

best regards
Okacha

 

[Moriendi]

Does it work if you open through Expert Mode, Hipath 4000 Expert Access. It should do. Then close everything and try again, direct from Comwin.

 

[OKACHA]

no, it doesn't work if I open through Expert Mode, Hipath 4000 Expert Access

 

[Moriendi]

Looks like a problem with ADP then, as the Assistant homepage is not showing any license info and also needs an upload, looks like it can't run any AMOs, it can't connect either.

I would reboot the Assistant from Base Admin/Webmin, and restart the ADP (from Portal, System, Front Panel). That's from memory, it's there somewhere so have a look around.

 

[george_a]

You should be able to connect to the ADP via telnet on the Atlantic LAN.
Connect via ssh (using PuTTY for example) to the OS4k Assistant, and run from there
telnet 192.0.2.3
After inputting the credentials, run
TSN;
You'll get a list of active connections, if you see 12 connections for logical device FBT, it means the FAMOS connection limit was reached. You can either stop them (but then you have to find the applications that opened the connections in the first place - like ComWin, Concierge) or you restart the ADP:
exe-rest:unit,a1,soft;

If there are not so many connections open, then it could be that FAMOS got deactivated, so just run
act-famos:famos;

 

[OKACHA]

thanks george
yes i could connect to ADP via telnet
<TSN;
TSN | NOUN | LOG DEV | TIME | USER
------+-------+---------+----------+----------
5596 STTAB TASK 13 53 28
4808 USER * 11 23 47 ROOT
if I execute exe-rest:unit,a1,soft; does telephony still working or it willbe shutdown

 

[george_a]

Try first act-famos:famos;
If after this you still cannot connect with ComWin, then restart the ADP.
You have a dual system (ADP and SWU running in separate machines), so an ADP restart doesn't impact telephony, but CSTA applications (like OSCC, UC, DTB, BLF) will be (shortly) disconnected.

 

[OKACHA]

thanks george

I had execute act-famos:famos; and it work ; then I had execute an uploud ( Click CM, Network, System, Search, then Action, Upload )and its synchronous, I have only the problem of logical backup

thanks again
best regards

 

[george_a]

Ok, this means that FAMOS was locked - if it was done by the system, then you should see in the Hista a related advisory. Also, there is a V6 R2 patch that prevents the automatic blocking of FAMOS, included in RMX-HF11 for V6 R2.17.