Siemens EF 711 Series Betriebsanweisung PDF herunterladen (Seite 318)

Configuring Classes of Service

Rate Limiting

SCALANCE WLC711

8-6 C79000-G8976-C260-03, 07/2012, User Guide, V8.11

Note:

Select either Type of Service (ToS) or Diffserv Codepoint (DSCP) from this dialog. You cannot configure both

types.

3. Click Type of Service (ToS):

• Select a Precedence value from the drop-down list,

• Select a specific ToS from the following list:

- Delay Sensitive

- High Throughput

- High Reliability

- Explicit Congestion Notification

4. Click Diffserv Codepoint (DSCP):

• Select a Well-known Value or

• Enter a Raw Binary Value.

5. Close the Configuration dialog.

The logic used to find the final User Priority (UP) depends on the CoS, the received UP, or the final

ToS/DSCP value. Here are the steps followed to determine the final UP:

1. Use UP markings defined in CoS (directly or via Legacy UP override).

2. If still no UP, use UP from the received packet.

3. If still no UP, use DSCP marking defined in CoS and map to UP with WLANs DSCP-to-UP

mapping table.

4. If still no UP, use received DSCP value and map to UP with WLANs DSCP-to-UP mapping

table.

Rate Limiting

The Inbound and Outbound Rate Limit is enforced on a per-station basis whether the rate limit is

assigned to a rule, policy or WLAN. Each station has its own set of counters that are used to

monitor its wireless network utilization. Traffic from other stations never count against a station's

rate limits.

• Controllers support up to 128 system wide rate profiles when managed from the controller.

• Each policy can use a maximum of 9 inbound rate profiles and 9 outbound rate profiles. For

each direction there can be one rate profile assigned by the policy's default CoS and 8 other

rate profiles assigned by the policy's rules.

• There is no limit to how many rules allow CoS assignments as long as there are never more

than 8 + 8 rate profiles assigned by Classes of Service.

If two or more rules in the same policy assign the same named rate profile to a station's packets,

then those rules "share" the rate profile. In Figure 8-1, a policy's rules assign both HTTP and FTP

traffic to the same rate limiter. The sum of the amounts of HTTP and FTP traffic determine

whether the rate limit is being exceeded. Each station gets its own set of rate limiters. So the HTTP

and FTP traffic of other stations never gets counted against a station's own rate profile limits.

1 2 ... 313 314 315 316 317 318 319 320 321 322 323 ... 491 492

Keine Kommentare

Siemens EF 711 Series Betriebsanweisung Seite 318