Inalp Networks SmartWare R2.00, Software Configuration Manual, Page: 127 / 321

Link Scheduler Configuration 127
Pool Codepoint Space Assignment Policy
1 xxxxx0 Standards Action
2 xxxx11 EXP/LU
3 xxxx01 EXP/LU (*)
Table 15-3: Codepoint Pools
(*) may be utilized for future Standards Action allocations as necessary
Service providers are not required to use the same node mechanisms or configurations to enable
service differentiation within their networks, and are free to configure the node parameters in
whatever way that is appropriate for their service offerings and traffic engineering objectives. Over
time certain common per-hop behaviors are likely to evolve (i.e. ones that are particularly useful for
implementing end-to-end services) and these may be associated with particular EXP/LU PHB
codepoints in the DS field, allowing use across domain boundaries. These PHBs are candidates for
future standardization.
Note: If you have to configure service differentiation on your SmartNode, ensure to that codepoint
settings are arranged with your service provider.
The command
set ip dscp sets the DS field applied to packets of the class name . Shaping may be
applied to make the class conformant. The no form of this command disables packet marking.
Procedure
Defining the codepoints in the DS field
Mode
Source
Command Purpose
node (src)[ name ]#set ip dscp value Defines the Differentiated Services Codepoint
value applied to packets of for the
selected
class or policy name . The range for value is from
0 to 63.
15.8.8 Specifying Layer 2 Marking
The IEEE ratified the 802.1p standard for traffic prioritization in response to the realization that
different traffic classes have different priority needs. This standard defines how network frames are
tagged with user priority levels ranging from 7 (highest priority) to 0 (lowest priority). 802.1p-
compliant network infrastructure devices, such as switches and routers, prioritize traffic delivery
according to the user priority tag, giving higher priority frames precedence over lower priority or
non-tagged frames. This means that time-critical data can receive preferential treatment over non-
time-critical data.
Under 802.1p, a 4-byte Tag Control Info (TCI) field is inserted in the Layer 2 header between the
Source Address and the MAC Client Type/Length field of an Ethernet Frame. Table 15-4 lists the tag
components.
Software Configuration Guide, Revision 1.03
Tag Control Field Description