[c-nsp] Cisco Local Area Mobility - (LAM)

[Tassos Chatzithomaoglou]

Do you have the global "router mobile" configured?

--
Tassos

Bogdan Radulescu wrote on 03/07/2009 12:08:
> Hello all,
> 
> I'm trying to use LAM on the following topology without much luck...
> 
> V100left---|3560G|---p-t-pL3link--|6500|---l2link--|7600|--V100right
> 
> V100left = SVI = 172.16.224.0/19
> V100right = SVI = 192.168.224.0/19
> V100right just random subnet, no clients
> 7600#interface Vlan100
>         ip address 192.168.224.1 255.255.0.0
>         ip mobile arp timers 1 1
>        end
> 
> Between 6500 and 7600 i have a dynamic routing protocol and 6500 
> announces V100left into BGP.
> 6500 has a static route for V100left to 3560G.
> Connected to 7600 there is a server on V150 that needs to "talk" with 
> these "clients"
> Clients don't need to talk to each other.
> 
> I would like to move clients from V100 left to V100 right. I don't want 
> to change ip addresses.
> V100left will be moved when all clients move to the right.
> 
> It looks like 7600 detects the foreign ip on it's interface V100right, 
> but doesn't put a "mobile" route for it.
> All i can see is this:
> --------------------------------
> Local MobileIP: aging arp mobility cache entries
> Local MobileIP: aging arp entry 172.16.225.153 60028 60000 60000
> Local MobileIP: Vlan100 add 172.16.225.153 accepted
> Local MobileIP: Vlan100 add 172.16.225.153 accepted
> Local MobileIP: Vlan100 add 172.16.225.153 accepted
> ----------------------------------
> 7600#sh arp vlan 100 detail
> ARP entry for 172.16.225.153, link type IP.
>  Simple Application, via Vlan100, last updated 0 minute ago.
>  Created by "IP Mobility".
>  Encap type is ARPA, hardware address is 0006.1901.2925, 6 bytes long.
>  ARP subblocks:
>  * Application Simple ARP Subblock
>    Entry is complete.
>  * IP ARP Adjacency
>    Adjacency (for 172.16.225.153 on Vlan100) was installed.
>  * IP Mobility
>    ARP Application entry for application IP Mobility.
>  * IP ARP VLAN ID
>    Subblock data size is 4 bytes.
>    VLAN IN ID: 100
>    VLAN OUT ID: 100
> ------------------------------------------
> 7600#sh ip route | i 172.16.225.153
> *?        172.16.225.153/32 [0/1] via 172.16.225.153*
> ------------------------------------------
> sh ip route 172.16.225.153
> Routing entry for 172.16.225.153/32
>  Known via "connected", distance 0, metric 1
>  Last update from 172.16.225.153 00:41:57 ago
>  Routing Descriptor Blocks:
>  * 172.16.225.153
>      Route metric is 1, traffic share count is 1
> ------------------------------------------
> 
> debug ip packet detail gives me this
> 
> Jul  2 23:32:19: FIBipv4-packet-proc: route packet from (local) src 
> 172.16.0.1 dst 172.16.225.153
> Jul  2 23:32:19: FIBfwd-proc: Default:172.16.225.153/32 proces level 
> forwarding
> Jul  2 23:32:19: FIBfwd-proc: depth 0 first_idx 0 paths 1 long 0(0)
> Jul  2 23:32:19: FIBfwd-proc: try path 0 (of 1) v4-rcrsv-172.16.225.153 
> first short ext 0(-1)
> Jul  2 23:32:19: FIBfwd-proc: v4-rcrsv-172.16.225.153 valid
> Jul  2 23:32:19: FIBfwd-proc: ip_pak_table 0 ip_nh_table 0 if none nh 
> 172.16.225.153 deag 0 via fib 0 path type recursive
> Jul  2 23:32:19: FIBfwd-proc: Default:172.16.225.153/32 not enough info 
> to forward via fib (none 172.16.225.153)
> Jul  2 23:32:19: FIBipv4-packet-proc: packet routing failed
> Jul  2 23:32:19: IP: s=172.16.0.1 (local), d=172.16.225.153, len 100, 
> unroutable
> Jul  2 23:32:19:     ICMP type=8, code=0
> 
> On the same 7600 i have several other VLANs with subnets from  
> 172.16.0.0/16 and some
> L3 interfaces part of other VRFs
> 
> 
> Is what i want possible or i\m wasting my time and yours? :)
> 
> Thank you
> 
> 
> 
> 
> 
> 
> 
> 
>