UNP vs. Port-Mobility when Client IP changes

[Favorite]

Hi Guys,
thanks for that great forum. I always read here if I got problems but I wasn't able to create an account here for a while due Forum problems or so . Now I did and I can describe a problem we have in our environment.

The environment:
We're doing most "Client"-Vlans via UNP / Port-Mobility based on their IP-addresss. Most Switches are 6860 now, some still are 6850.

# OS6850
vlan 32 enable name "Network 192.168.32.0"
vlan 33 enable name "Network 192.168.33.0"

vlan 32 ip 192.168.32.0 255.255.255.0
vlan 33 ip 192.168.33.0 255.255.255.0
vlan port mobile 1/5-48

Works fine on 6850:
If I have a Client IP 192.168.32.x it will stay in VLAN 32. If I change the Clients IP to 192.168.33.x it will move to VLAN 33 immediately. That's how I expect it.


# OS6860
vlan 31-32 admin-state enable
vlan 32 name "Network 192.168.32.0"
vlan 33 name "Network 192.168.33.0"

unp edge-profile vlan-32
unp edge-profile vlan-33
unp vlan-mapping edge-profile vlan-32 vlan 32
unp vlan-mapping edge-profile vlan-33 vlan 33
unp classification ip-address 192.168.32.0 mask 255.255.255.0 edge-profile "vlan-32"
unp classification ip-address 192.168.33.0 mask 255.255.255.0 edge-profile "vlan-33"
unp edge-template TEMPLATE_1
unp edge-template TEMPLATE_1 classification enable
unp edge-template TEMPLATE_1 default-edge-profile DHCP
unp port 1/1/5-48 port-type edge
unp port 1/1/5-48 edge-template TEMPLATE_1

Problem on 6860:
If I have a Client IP 192.168.32.x it will stay in VLAN 32. But if I change the Clients IP to 192.168.33.x it will not move to VLAN 33 immediately.

The only thing I could do would be unplug the Clients Network Cable for 5 minutes or use "mac-learning flush dynamic mac-address" or any other unp resetting command. Is there any way to speed this up? As network admin it's easy for me to use the workaround but my administrator colleagues who aren't very familiar with networking are confused and frustrated because they either loose time or need to contact me.
Does anyone have the same problems and a solution? I would really appreciate!

Best wishes,
Favorite




SELFEDIT:
For some reason I checked a dokuwiki today (german language) and have seen that there is the option unp force-l3-learning which would fix the issue. It is not available in official AOS yet. I'll let you know if this fixes our problems:

http://dokuwiki.alu4u.com/doku.php?id=o ... np_forcel3
unp force-l3-learning enable
http://dokuwiki.alu4u.com/doku.php?id=o ... np_forcel3

[silvio]

Hi,
thanks for sharing your knowledge. But in your R8 config the classification rules are missing.
looks like:
unp classification ip-address 192.168.32.0 mask 255.255.255.0 edge-profile vlan-32
unp classification ip-address 192.168.33.0 mask 255.255.255.0 edge-profile vlan-33

But you are correct. Option "force-l3" is necessary maybe. But it should be possible in actual releases.
regards
Silvio

[Favorite]

Hi Silvio,
thanks for your reply and ups.. yes you are right, I just forgot to add that config lines to this topic. On our Switches it's already implemented. I edited my first post and wait for approval.
I will update the topic if I updated our switches to the current release and tested out the "force-l3" option.
Thanks and best regards,
Favorite