The SSR has 4 Traffic Profile or Traffic Class ( or queues )
Each service will be map to one of the Traffic Class ( by using a Service Class )
Session Type can be define ( mapped to Service Class ) but if Service exist will take priority ( and Service-policy which mapped to Service Class ) .
So Session Type will be for undefine traffic.
Traffic Profile: https://docs.128technology.com/docs/config_reference_guide/#traffic-profile
Service Classes:
Example: https://docs.128technology.com/docs/bcp_qos_msft_expressroute/
1- Create a new Session Type ( like Citrix )
2- Create a New Service Class ( for Citrix is needed: Aggr RL, Flow RL, DSCP Eg Marking, Queue/Traffic Class maping )
3- Create a New service ( for Citrix + Security policy and Service Policy ( select Service Class ))
| Mapping to a Traffic Class | Session Type will be for undefine traffic in Service |
|---|---|
1- Service Policy used and pointing to Service Class | Session > Service > Service Policy > Service Class |
| 2- or session-type use | Traffic matches a session-type ( destination port and protocol )
|
| 3- none of the above | it will be classified as best-effort treatment |
| Create Service Class | |
| Create Service Class |  |
Traffic Class DSCP ( for CoS in MPLS - no need for Broadband ) Aggregate Rate Limiting Flow Rate Limiting |
|
| Map a Service Policy to a Service Class | |
Mapping to a Traffic Class Session > Service > Service Policy > Service Class |
|
| |
| Traffic Profile ( for TE ) | 4x TE queues: high, medium, low, and best-effort. |
| |
High + Medium + Low + BE = 100% | |
| Apply Traffic Profile | |
| Apply to device-interface WAN device-interface | Enable TE and select the Traffic Profile Set Transmission capacity (specified in bps) to the upstream bandwidth (or possibly slightly below, say 95%)
|
