Can anyone ping sapserv?

[Former Member]

Hello all,

I have been following note 33135 Guidelines for OSS1.

In it, it mentions to use certain IP addresses:

sapserv1 (194.117.106.129) connection via Internet VPN

sapserv2 (194.39.131.34) connection via Internet SNC

sapserv3 (147.204.2.5) for customers with connection to Germany

sapserv4 (204.79.199.2) for customers in America

sapserv5 (194.39.138.2) for customers with connection to Japan

sapserv6 (194.39.139.16) for customers in Australia and New Zealand

sapserv7 (194.39.134.35) for customers in Asia

Can anyone ping these outside of the SAP Network? Do they actually work? Is there something special one must do in order for ping 194.39.134.35 to actually work?

TIA

Edited by: Casey Harris on Mar 6, 2009 7:38 AM

[Former Member]

Still need to try niping - hopefully, it will work 😐

[Former Member]

I am able to ping sapserv2 194.39.131.34 by my pc. it is pinging normally.

Ankit

[Former Member]

yes Harris,

that is the case

SAP will register you SAP Router and will provie you connection details

Then only you will be able to ping the router at SAP side.

so send a customer message to SAP detailing him about your connection details

Rohit

[Former Member]

hello Harris,

have you notified SAP that you have installed SAP router on your machine and got it registered

if not kindly send a message to SAP saying you have installed sap router giving the full ip and hostname details and ask them to register

Also you have to give your public ip of saprouter

Rohit

[Former Member]

Thanks for the information. Is this the reason why a regular "ping" does not work?

[Former Member]

Hi,

The ping does not work because it is filtered by SAP firewalls.

If you want to to test connectivity with sapservX servers , use the SAP utility niping.

Regards,

Olivier

[Former Member]

Hi Olivier,

I guess when the we get registered there only we will be able to ping as SAP will then allow us to ping their router

Rohit

[Former Member]

Hi Rohit,

The network connectivity is set by SAP, after registration but you will never be able (at least, we are not) to ping the SAP servers. But you will be able to niping them which gives you the same functionality.

Regards,

Olivier

[Former Member]

Thanks all again for the inputs.

Oliver, if one can niping, then can one do the "Test Connection" under the RFC SAPOSS?

Also, is Solution Manager useless without the connection OSS? The policy of the environment here is that it is not allowed - but - this system is for testing.

The idea was to download the patches to patch the Solution Manager. One can put them in the Download Basket on OSS but it looked as though the Approval had to go through the Maintenance Optimizer under the Solution Manager.

When entering the IP address mentioned by Ankit, yielded the following result.

Logon Connection Error

Error Details Error when opening an RFC connection

Error Details ERROR: sapserv2a: route permission denied (69.153.0.223 to oss001, sapmsOSS)

Error Details LOCATION: SAProuter 39.2 (SP4) on 'sapserv2a'

Error Details COMPONENT: NI (network interface)

Error Details COUNTER: 7

Error Details MODULE:

Error Details LINE:

Error Details RETURN CODE: -93

Error Details SUBRC: 0

Error Details RELEASE: 710

Error Details TIME: Sat Mar 7 10:36:17 2009

Error Details VERSION: 39

Edited by: Casey Harris on Mar 7, 2009 10:40 AM

[Former Member]

Hi Casey,

>Oliver, if one can niping, then can one do the "Test Connection" under the RFC SAPOSS?

Yes, it works for me. If the saprouters are well configured for the RFC destination, it should work.

Maybe the ping does not work for me because of my company's firewalls but I stuill think that niping or SM59 is a better test because it tests the real port and protocol.

Regards,

Olivier

[Former Member]

have you implemented saprouter?

Is sapserv2 is pingable from u?

by the error you are sending that it is permission denied means you are reaching at sapserv2 but permission is denied.

Ankit