IP address in SAPNote for Solution Manager 7.0 RFC SAPOSS not working

[Former Member]

Hello,

I am attempting to set up the SAPOSS RFC user so that it can be used for the Solution Manager. I have been following note: 33135 to set up the process (as it says to set up saprouter). Used IP addresses set up in note 33135 Guidelines for OSS1 but they dont seem to work. Did items below.

question: Why does one get the error? What more steps can be done to troubleshoot it?

TIA

_________________________________________________________________________________

-> When going to SM59 and doing the test, get the following error in the RFC developer trace

Trace file opened at 20090305 023020 CST SAP-REL 700,0,144 RFC-VER U 3 957098

Error RFCIO_ERROR_SYSERROR in abrfcpic.c : 2513

LB: Hostname or service of the message server unknown

DEST =SAPOSS

MSHOST =/H/69.153.0.223/S/sapdp99/H/204.79.199.2/S/sapdp99/H/oss001

R3NAME =OSS

GROUP =EWA

ABAP Programm: RSRFCPIN (Transaction: SM59)

User: TEST (Client: 001)

Destination: SAPOSS (handle: 2, , )

testbox:xdsadm 170> ping 204.79.199.2

PING 204.79.199.2 (204.79.199.2) 56(84) bytes of data.

204.79.199.2 ping statistics ---

5 packets transmitted, 0 received, 100% packet loss, time 3999ms

testbox:xdsadm 171> ping 69.153.0.223

PING 69.153.0.223 (69.153.0.223) 56(84) bytes of data.

64 bytes from 69.153.0.223: icmp_seq=1 ttl=255 time=1.50 ms

64 bytes from 69.153.0.223: icmp_seq=2 ttl=255 time=0.543 ms

69.153.0.223 ping statistics ---

2 packets transmitted, 2 received, 0% packet loss, time 1002ms

rtt min/avg/max/mdev = 0.543/1.025/1.507/0.482 ms

testbox:xdsadm 187> cat saprouttab

P * * *

testbox:xdsadm 188> saprouter -n

Thu Mar 5 02:47:54 2009

SAP Network Interface Router, Version 38.10

Thu Mar 5 02:47:55 2009

peer SAProuter with NI version 38 ...

send new-routtab-request to running SAProuter ...

WARNING: wildcard character used in route target

request successfully completed.

testbox:xdsadm 190> saprouter -l

Thu Mar 5 02:48:48 2009

SAP Network Interface Router, Version 38.10

peer SAProuter with NI version 38 ...

send info-request to running SAProuter ...

SAP Network Interface Router running on port 3299 (PID = 14638)

Started on: Thu Mar 5 02:15:48 2009

ID CLIENT | PARTNER service

-

---

+----

---

1 localhost | (no partner)

Total no. of clients: 1

Working directory : /sapmnt/xds/exe

Routtab : ./saprouttab

testbox:xdsadm 197> niping -s

Thu Mar 5 02:57:19 2009

ready for connect from client ...

testbox:xdsadm 199> niping -c

Thu Mar 5 02:57:28 2009

connect from host 'localhost', client hdl 1 o.k.

Thu Mar 5 02:57:28 2009

connect to server o.k.

send and receive 10 messages (len 1000)

-

---

times -

---

avg 0.022 ms

max 0.076 ms

min 0.016 ms

tr 86805.556 kB/s

excluding max and min:

av2 0.017 ms

tr2 117481.203 kB/s

client hdl 1 disconnected ...

[Former Member]

Hi,

Follow the bellow steps and make sure you are entering the correct SAP end's router IP. Like when you raise the req. with SAP they will assign you to sapserv1,2,..... with IP's.

If any error occurs as per 24177 run the commands as per the note.

In the router system etc/services

sapdp99 3299/tcp added

Snote is not working after this?

Follow the note 797001

Regards,

Hari.

[Former Member]

Hello all,

Thanks for the responses.

Also saw: http://help.sap.com/saphelp_nw04/helpdata/en/4f/992dd7446d11d189700000e8322d00/content.htm

Question: does saprouter require *three* hosts in order to work properly? According to the link above, that seems to be the case.

Also, I have the following:

>netstat -a | grep sap (y|n|e|a)? yes

tcp 0 0 *:sapdp00 : LISTEN

tcp 0 0 *:sapdp01 : LISTEN

tcp 0 0 *:sapdp99 : LISTEN

tcp 0 0 *:sapgw00 : LISTEN

tcp 0 0 *:sapmsKDS : LISTEN

tcp 0 0 simba:sapdp01 simba:37877 ESTABLISHED

tcp 0 0 simba:sapdp01 simba:37879 ESTABLISHED

testbox:xdsadm 166> saprouter -r &

[1] 22197

testbox:xdsadm 167>

trcfile dev_rout

no logging active

WARNING: wildcard character used in route target

testbox:xdsadm 167> niping -s &

[2] 22200

testbox:xdsadm 168>

Thu Mar 5 09:53:10 2009

ready for connect from client ...

testbox:xdsadm 168> niping -c -H testbox

Thu Mar 5 09:53:31 2009

connect from host 'localhost', client hdl 1 o.k.

Thu Mar 5 09:53:31 2009

connect to server o.k.

send and receive 10 messages (len 1000)

times -

---

avg 0.022 ms

max 0.077 ms

min 0.016 ms

tr 86805.556 kB/s

excluding max and min:

av2 0.017 ms

tr2 118371.212 kB/s

client hdl 1 disconnected ...

testbox:xdsadm 169>

BUT -

---

For sapserv4

testbox:xdsadm 168> niping -c -H /H/testbox/H/204.79.199.2

It just stalls ...

Is thre some kind of way to see why that is the case? Some kind of trace file?

TIA

[allaine_tabilin]

Hi,

Seems to be a firewall (or network) issue. Is it possible for you to execute "ftp sapserv4" on the command line to verify if all kinds of network packets are being dropped? If this timeout, then you need to verify if the network VPN from your server to OSS1 is working.

Thanks,

Allaine

[Former Member]

Also check that port 99 is open or closed as this might cause an issue

Also get the entry of saprouter at SAP side in hosts file

Hope it helps

Rohit

[Former Member]

Hai,

Goto ST11 and check the trace file dev_lg for more details.

Did you have the entry for sapdp99 in the /etc/services file?

Regards,

Yoganand.V