HP StorageWorks 8/80 Brocade Converged Enhanced Ethernet Administrator's Guide - Page 124

Traffic class mapping, Unicast traffic

Page 124 highlights

9 Queueing Traffic class mapping The Brocade 8000 supports eight unicast traffic classes for isolation and to control servicing for different priorities of application data. Traffic classes are numbered from 0 through 7, with higher values designating higher priority. The traffic class mapping stage provides some flexibility in queue selection: • The mapping may be many-to-one, such as mapping one byte user priority (256 values) to eight traffic classes. • There may be a non-linear ordering between the user priorities and traffic classes. Unicast traffic Table 17 presents the Layer 2 default traffic class mapping supported for a COS-based user priority to conform to 802.1Q default mapping. TABLE 17 Default user priority for unicast traffic class mapping User priority Traffic class 0 1 1 0 2 2 3 3 4 4 5 5 6 6 7 7 You are allowed to override these default traffic class mappings per port. Once the traffic class mapping has been resolved it is applied consistently across any queueing incurred on the ingress and the egress ports. Multicast traffic The Brocade 8000 supports four multicast traffic classes for isolation and to control servicing for different priorities of application data. Traffic classes are numbered from 0 through 3, with higher values designating higher priority. The traffic class mapping stage provides some flexibility in queue selection. Table 18 presents the Layer 2 default traffic class mapping supported for a COS-based user priority to conform to 802.1Q default mapping. TABLE 18 Default user priority for multicast traffic class mapping User Priority Traffic class 0 0 1 0 2 1 3 1 4 2 104 Converged Enhanced Ethernet Administrator's Guide 53-1001346-01

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162

104
Converged Enhanced Ethernet Administrator’s Guide
53-1001346-01
Queueing
9
Traffic class mapping
The Brocade 8000 supports eight unicast traffic classes for isolation and to control servicing for
different priorities of application data. Traffic classes are numbered from 0 through 7, with higher
values designating higher priority.
The traffic class mapping stage provides some flexibility in queue selection:
The mapping may be many-to-one, such as mapping one byte user priority (256 values) to eight
traffic classes.
There may be a non-linear ordering between the user priorities and traffic classes.
Unicast traffic
Table 17
presents the Layer 2 default traffic class mapping supported for a COS-based user priority
to conform to 802.1Q default mapping.
You are allowed to override these default traffic class mappings per port. Once the traffic class
mapping has been resolved it is applied consistently across any queueing incurred on the ingress
and the egress ports.
Multicast traffic
The Brocade 8000 supports four multicast traffic classes for isolation and to control servicing for
different priorities of application data. Traffic classes are numbered from 0 through 3, with higher
values designating higher priority. The traffic class mapping stage provides some flexibility in queue
selection.
Table 18
presents the Layer 2 default traffic class mapping supported for a COS-based user priority
to conform to 802.1Q default mapping.
TABLE 17
Default user priority for unicast traffic class mapping
User priority
Traffic class
0
1
1
0
2
2
3
3
4
4
5
5
6
6
7
7
TABLE 18
Default user priority for multicast traffic class mapping
User Priority
Traffic class
0
0
1
0
2
1
3
1
4
2