Switch and router

Sven Olaf Kamphuis sven at cb3rob.net
Tue Feb 7 18:04:52 UTC 2012


"increase pipe" = port trunking/etherchannel/port bonding whatever your 
supplier calls it. just use 2 or 4 ports instead of just one.

ieee 802.3ad/lacp/link aggregation, etc.... all the same stuff. ;)

provided you have another interface on/for your router ofcourse (your 
switch probably has plenty ;)

also an option (for cisco)...

int gix/x/x
max-reserved-bandwidth 1

(i'd say, 1% of 10ge should about cover all the needs for inband layer-2 
related stuff as a few kbit/s already should suffice ;)

1% being the minimum you can set this to.

-- 
Greetings,

Sven Olaf Kamphuis,
CB3ROB Ltd. & Co. KG
=========================================================================
Address: Koloniestrasse 34         VAT Tax ID:      DE267268209
          D-13359                   Registration:    HRA 42834 B
          BERLIN                    Phone:           +31/(0)87-8747479
          Germany                   GSM:             +49/(0)152-26410799
RIPE:    CBSK1-RIPE                e-Mail:          sven at cb3rob.net
=========================================================================
<penpen> C3P0, der elektrische Westerwelle
http://www.facebook.com/cb3rob
=========================================================================

Confidential: Please be advised that the information contained in this
email message, including all attached documents or files, is privileged
and confidential and is intended only for the use of the individual or
individuals addressed. Any other use, dissemination, distribution or
copying of this communication is strictly prohibited.


On Tue, 7 Feb 2012, Randy McAnally wrote:

> On Tue, 7 Feb 2012 08:32:21 -0500, Ann Kwok wrote
>> Hello
>>
>> Thank you for your help
>>
>> But we can't increase the pipe as we are using 10G switch.
>>
>> The congestion happens when the traffic is using 7G
>
> If you cannot increase bandwidth, then you must increase the TX queue (in QOS
> and/or port buffer).
>
> ~Randy
>
>




More information about the NANOG mailing list