Skip to content
This repository has been archived by the owner on Oct 26, 2022. It is now read-only.

QFX3500 QoS provisioning breaks connectivity in TOR configuration #60

Open
ibaldin opened this issue Jun 15, 2016 · 2 comments
Open

QFX3500 QoS provisioning breaks connectivity in TOR configuration #60

ibaldin opened this issue Jun 15, 2016 · 2 comments
Assignees
Labels

Comments

@ibaldin
Copy link
Contributor

ibaldin commented Jun 15, 2016

When used in mishmash rack the QFX3500 in TOR configuration does not properly pass TCP and UDP packets (ICMP is fine). Possibly a rate configuration on the policer, as removing the filter off the VLAN fixes the problem.

@ibaldin ibaldin added the bug label Jun 15, 2016
@ibaldin ibaldin self-assigned this Jun 15, 2016
@mcevik0
Copy link
Contributor

mcevik0 commented Jun 17, 2016

  • On QFX3500 switch, the policer is configured with minimum values (8k for bandwidth limit and 512 bytes for burst-size-limit).

policer orca_policy_2201-policer { if-exceeding { bandwidth-limit 8k; burst-size-limit 512; } then discard; }

  • When bandwidth is changed on Flukes to 100Mbps, the same values were applied on the switch.
  • On the logs the values are seen as below. QUANTUM_MAX_RATE changes according to the selection on Flukes. (And I think QUANTUM_BURST_SIZE also changes according to the bandwidth selected.)
    The first line -bw=0 burst=0- is the same on RCI rack as well (no matter what bandwidth value is selected).

INFO | jvm 1 | 2016/06/16 18:33:42 | [echo] enabling vlan 2201 on router 192.168.201.249 bw=0 burst=0
. . .
INFO | jvm 1 | 2016/06/16 18:33:54 | [echo] QUANTUM_MAX_RATE= 10000000
INFO | jvm 1 | 2016/06/16 18:33:54 | [echo] QUANTUM_BURST_RATE= 1250000

  • CreateQoSVLAN.txt is identical to QFX hierarch as well.

@ibaldin
Copy link
Contributor Author

ibaldin commented Dec 2, 2016

Should fix this in mishmash first, then re-test DD performance.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

2 participants