Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
EC392 - L3 Roaming
EC392 looks like it should be The client database on the original controller is updated with the anchor entry, and the new controller database is updated with the foreign entry.

See (Intercontroller Layer 3 Roaming)

"Layer 3 roaming is similar to Layer 2 roaming in that the controllers exchange mobility messages on the client roam. However, instead of moving the client database entry to the new controller, the original controller marks the client with an “Anchor” entry in its own client database. The database entry is copied to the new controller client database and marked with a “Foreign” entry in the new controller. The roam remains transparent to the wireless client, and the client maintains its original IP address."
Was this ever resolved?
Resolved - thank you for your constructive feedback.

Forum Jump:

Users browsing this thread: 1 Guest(s)