D-Link DWS-3024 Product Manual - Page 223

L3 Tunnel Status Values, Con d, Routing Disabled, Routing Interface, Table 83., L3 Tunnel Status

Page 223 highlights

L3 Roaming Example possible values and explains what they mean. Table 83. L3 Tunnel Status Values L3 Tunnel Status None Configured Not Configured Routing Disabled Not Configured - No Routing Interface Description The status might be None for one of the following reasons: • The WLAN Operational Status is disabled • L3 Tunnel is Disabled • The network is not associated with any AP profiles. If you create or edit a network and configure L3 Tunneling, but there are no VAPs on any AP Profiles that use the network, the status is None. The L3 Tunnel is configured and ready to be applied to the APs that use this profile. Routing is disabled on the routing interface. The status might show this value for one of the following reasons: • The routing interface for the L3 Tunnel network does not exist. • IPv6 is enabled on the routing interface. • IP Multicast is enabled on the routing interface. • The Tunnel subnet address does not match a routing interface. In the example in this appendix, the VLAN routing interface has an IP address of 192.168.60.15/24, and the L3 Tunnel Subnet is 192.168.60.0/24, so the tunnel subnet matches a routing interface. 11. From Privileged EXEC mode, apply the modified default profile to the APs that use the default profile (Profile 1). (switch-prompt)#wireless ap profile apply 1 After the managed AP updates complete, the L3 Tunnel network is available on all APs that use the default profile. Users who connect to an AP by using the L3 Tunnel SSID can roam among all APs without traffic interruption. To test connectivity, make sure you can ping from each AP to the switch loopback IP address and the IP address used by the routing interface for L3 tunnels. From Privileged EXEC mode, you can enable debugging on the AP with the wireless ap debug command, which allows you to Telnet to the AP. Once a wireless client associates with the tunneled subnet, use the ping command and set a large packet size to make sure you can send the desired MTU size through the tunnel. From a Windows client, use -l to set the packet size and -f to prohibit packet fragmentation, for example: ping -l 1542 -f 192.168.60.15 From a Unix system, use -s to set the packet size and -M do to prohibit packet fragmentation, for example: ping -s 1542 -M do 192.168.60.15 Configuring the L3 Tunnel Network 223

  • 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
  • 243
  • 244
  • 245
  • 246
  • 247
  • 248
  • 249
  • 250
  • 251
  • 252
  • 253
  • 254
  • 255
  • 256
  • 257
  • 258
  • 259
  • 260
  • 261
  • 262
  • 263
  • 264
  • 265
  • 266
  • 267
  • 268
  • 269
  • 270

Configuring the L3 Tunnel Network
223
L3 Roaming Example
possible values and explains what they mean.
11.
From Privileged EXEC mode, apply the modified default profile to the APs that use the
default profile (Profile 1).
(switch-prompt)#
wireless ap profile apply 1
After the managed AP updates complete, the L3 Tunnel network is available on all APs that
use the default profile. Users who connect to an AP by using the L3 Tunnel SSID can roam
among all APs without traffic interruption.
To test connectivity, make sure you can ping from each AP to the switch loopback IP address
and the IP address used by the routing interface for L3 tunnels. From Privileged EXEC mode,
you can enable debugging on the AP with the
wireless ap debug
<macaddr>
command,
which allows you to Telnet to the AP.
Once a wireless client associates with the tunneled subnet, use the ping command and set a
large packet size to make sure you can send the desired MTU size through the tunnel.
From a Windows client, use
-l
<size>
to set the packet size and
-f
to prohibit packet
fragmentation, for example:
ping -l 1542 -f 192.168.60.15
From a Unix system, use
-s
<size>
to set the packet size and
-M do
to prohibit packet
fragmentation, for example:
ping -s 1542 -M do 192.168.60.15
Table 83.
L3 Tunnel Status Values
L3 Tunnel Status
Description
None
The status might be None for one of the following reasons:
The WLAN Operational Status is disabled
L3 Tunnel is Disabled
The network is not associated with any AP profiles. If you create
or edit a network and configure L3 Tunneling, but there are no
VAPs on any AP Profiles that use the network, the status is None.
Configured
The L3 Tunnel is configured and ready to be applied to the APs that
use this profile.
Not Configured -
Routing Disabled
Routing is disabled on the routing interface.
Not Configured - No
Routing Interface
The status might show this value for one of the following reasons:
The routing interface for the L3 Tunnel network does not exist.
IPv6 is enabled on the routing interface.
IP Multicast is enabled on the routing interface.
The Tunnel subnet address does not match a routing interface.
In the example in this appendix, the VLAN routing interface has an IP
address of 192.168.60.15/24, and the L3 Tunnel Subnet is
192.168.60.0/24, so the tunnel subnet matches a routing interface.