Subnet Configuration and system performance

I'm in the process of redesigning my SAP landscape. My predecessors (several) created 2 internal private subnets. The first (10.1.1.x) is only for server to server traffic between the Application Servers and the DB server. The 2nd (192.168.1.x) is for all user traffic. This includes users to App. Servers, as well as File Server, Exchange, DNS, etc.) I'm in teh process of upgrading all the SAP servers with new hardware. I'm at a cross roads where I'm trying to decide to maintain the existing seperate subnet for server SAP traffic. This is going to require additional switches and increase complecity somewhat. Does anyone know if seperate subnets for server traffic is really necessary? IS there any appreciable performance gain by keepingthe traffic seperate? Would you expect to see any appreciable performance decrease by going with a single subnet?

Answer Wiki

Thanks. We'll let you know when a new response is added.

Your predecessors must have had reasons to separate Server traffic and User traffic. If the network had been well documented, the reasons should be very clear. Keeping traffic separate not only enhances performance but provides security. However, you can minimise the hardware you need to purchase by implementing VLANS on switches that support them. You may not need to buy so much hardware and you could easily monitor the entire infrastructure if well designed.

Discuss This Question: 1  Reply

There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.
  • Carrie Higbie
    Separating traffic will show a performance gain especially for server to server traffic. It assures that server to server replication and mirroring happen without hinderance by user traffic on the network. VLANs are one way, but I would suggest keeping it on its own switch. I say this because you have less potential for errors and misconfigurations down the road. One option would be to look at the new resillient switches that can do load balancing and sharing along with hot failover. There are several on the market. In the event that your server to server switch fails, it could immediately fail over to your other switch. It is a bit more complex to set up, but I think you will be happy with the stability. Large database applications can be a hog of resources and this option, I think, will make you happier in the long run. Once it is set up, you can leave it alone and you won't slow down any network traffic with replication traffic. Look at the number of packets that move over your existing server to server switch compared to the network switches. You will see that there are a lot of packets in that communication. I would also suggest asking SAP what they think, but in my experience with setting up these networks with Oracle, SAP and others, it is recommended that the configuration is what you have now.
    660 pointsBadges:

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

Thanks! We'll email you when relevant content is added and updated.


Share this item with your network: