07-29-2012 11:30 AM - edited 03-07-2019 08:02 AM
Hi Experts
Pls find attached diagram
have vlan streching betwwen sw1 (site1) and sw2 (site2) away from each other 5km, telco authority gives me 16 Mbps between these 2 sites,srv1 has private L2 vlan for database syncronaziation with srv2 at site 2 along with a public ip ,when the thes 2 servers replicate the database(mssql) with each other over the trunk(16mbps) the trunk link becomes congested then end up having latency with main service of the servers , now how to configure L2 QOS betwwen these 2 switches(3750) and only reserver bandwith for the sql database 10Mbps while the remaing 6Mbps keep it for the services offered by these servers when the congestion happend....pls advise
thanks in the advance
thanks
jamil
08-07-2012 10:58 AM
Disclaimer
The Author of this posting offers the information contained within this posting without consideration and with the reader's understanding that there's no implied or expressed suitability or fitness for any purpose. Information provided is for informational purposes only and should not be construed as rendering professional advice of any kind. Usage of this posting's information is solely at reader's own risk.
Liability Disclaimer
In no event shall Author be liable for any damages whatsoever (including, without limitation, damages for loss of use, data or profit) arising out of the use or inability to use the posting's information even if Author has been advised of the possibility of such damage.
Posting
There are several ways to accomplish this on a 3750. Best approach depends on how you really want to manage your bandwidth.
You need to get SQL replication into a dedicated egress queue, and all other traffic into its own queue.
Do you always want to cap the SQL replication at 10 Mbps? (Vs. allowing it to use otherwise unused bandwidth.
Do you always want to cap the non-SQL data at 6 Mbps?
If both SQL replication and non-SQL want more bandwidth, you want to maintain the 5:3 bandwidth sharing ratio?
PS:
What I would suggest, "shape" egress bandwidth at 16 Mbps, and set a bandwidth sharing ratio of 1:255. Effectively, this would only provide the SQL replication available bandwidth, although it won't be starved.
This should be find unless you find SQL replication can't get enough bandwidth to meet its service requirements, if not, then modify the ratio so it does.
08-08-2012 11:46 AM
Hi Joseph
Thanks for ur reply
Pls sample configuration for the below as Yessssssssss
Do you always want to cap the SQL replication at 10 Mbps? (Vs. allowing it to use otherwise unused bandwidth.
Do you always want to cap the non-SQL data at 6 Mbps?
jamil
08-08-2012 12:14 PM
Disclaimer
The Author of this posting offers the information contained within this posting without consideration and with the reader's understanding that there's no implied or expressed suitability or fitness for any purpose. Information provided is for informational purposes only and should not be construed as rendering professional advice of any kind. Usage of this posting's information is solely at reader's own risk.
Liability Disclaimer
In no event shall Author be liable for any damages whatsoever (including, without limitation, damages for loss of use, data or profit) arising out of the use or inability to use the posting's information even if Author has been advised of the possibility of such damage.
Posting
interface x
!assuing interface is running at 100 Mbps
!and non-SQL traffic is directed to Q1
!and SQL traffic is directed to Q2
srr-queue bandwidth shape 17 10 0 0
08-08-2012 12:51 PM
H Joseph
what are the below value in the shape?
17 10 0 0
08-08-2012 05:18 PM
Disclaimer
The Author of this posting offers the information contained within this posting without consideration and with the reader's understanding that there's no implied or expressed suitability or fitness for any purpose. Information provided is for informational purposes only and should not be construed as rendering professional advice of any kind. Usage of this posting's information is solely at reader's own risk.
Liability Disclaimer
In no event shall Author be liable for any damages whatsoever (including, without limitation, damages for loss of use, data or profit) arising out of the use or inability to use the posting's information even if Author has been advised of the possibility of such damage.
Posting
Ibrahim Jamil wrote:
H Joseph
what are the below value in the shape?
17 10 0 0
On a 100 Mbps port, 1/17 (5.88 Mbps) and 1/10 (10 Mbps).
08-09-2012 11:29 AM
thanks jospeh for ur reply. i realy appreciate
08-09-2012 11:54 AM
Just a side note - I always run L3 over MetroE circuits and would recommend that to anyone....
08-09-2012 12:41 PM
Hi Robert
the business require L2 Extension so we hqad to go with L2 to acomplish the VLAN Steching
jamil
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide