D-Link DES-3326SRM Product Manual - Page 95

CPU Interface Filtering, CPU Interface Filtering State Settings

Page 95 highlights

D-Link DES-3326S Layer 3 Switch CPU Interface Filtering There are specific circumstances under which the ACL cannot filter a packet even when there is a condition match that should deny forwarding. This is a limitation that may arise if: • the destination MAC is the same as the Switch (system) MAC • a packet is directed to the system IP interface such as multicast IP packets or if the hardware IP routing table is full and Switch software routes the packet according to routing protocol. In order to address this functional limitation of the chip set, an additional function, CPU Interface Filtering, has been added. CPU Filtering may be universally enabled or disabled. Setting up CPU Interface Filtering follows the same basic procedure as ACL configuration and requires some of the same input parameters. CPU Interface Filtering is configured in a manner similar to creating an Access Profiles. First a mask is created to specify which part or parts of a frame the Switch will examine, such as the MAC source address or the IP destination address. Then rules are used to define criteria the Switch will use to determine what to do with the frame. The entire process is described below. CPU Interface Filtering State Settings In the following window, the user may globally enable or disable the CPU Interface Filtering mechanism by using the pulldown menu to change the running state. To access this window, click CPU Interface Filtering State in the Advanced Setup directory folder. Choose Enabled to enable CPU packets to be scrutinized by the Switch and Disabled to disallow this scrutiny. Figure 14- 7. CPU Interface Filtering State Settings window 85

  • 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
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218
  • 219
  • 220
  • 221
  • 222
  • 223
  • 224
  • 225
  • 226
  • 227
  • 228
  • 229
  • 230
  • 231
  • 232
  • 233
  • 234
  • 235
  • 236
  • 237
  • 238
  • 239
  • 240
  • 241
  • 242

D-Link DES-3326S Layer 3 Switch
CPU Interface Filtering
There are specific circumstances under which the ACL cannot filter a packet even when there is a condition match that should
deny forwarding. This is a limitation that may arise if:
the destination MAC is the same as the Switch (system) MAC
a packet is directed to the system IP interface such as multicast IP packets or if the hardware IP routing table is full
and Switch software routes the packet according to routing protocol.
In order to address this functional limitation of the chip set, an additional function,
CPU Interface Filtering
, has been added.
CPU Filtering may be universally enabled or disabled. Setting up CPU Interface Filtering follows the same basic procedure as
ACL configuration and requires some of the same input parameters.
CPU Interface Filtering is configured in a manner similar to creating an Access Profiles. First a mask is created to specify
which part or parts of a frame the Switch will examine, such as the MAC source address or the IP destination address. Then
rules are used to define criteria the Switch will use to determine what to do with the frame. The entire process is described
below.
CPU Interface Filtering State Settings
In the following window, the user may globally enable or disable the CPU Interface Filtering mechanism by using the pull-
down menu to change the running state. To access this window, click
CPU Interface Filtering State
in the Advanced Setup
directory folder. Choose
Enabled
to enable CPU packets to be scrutinized by the Switch and
Disabled
to disallow this
scrutiny.
Figure 14- 7. CPU Interface Filtering State Settings window
85