From: Dustin.Yates@xxxxxxxxxxxx
Date: Sun Mar 31 2002 - 21:48:07 GMT-3
Maybe the better question to ask is this task fishing for LAM or is it
fishing for Mobile IP? Guess that would be the point to bring to a proctor,
"if I configure it like this it's LAM, but if I do this it's Mobile IP...
and since the task didn't specify one or the other, can you clarify what is
needed for this." I've seen a couple of commercial lab products now with
this same type of question. Without asking the author, how would one know?
I did have one command that wasn't correct ... so instead of:
> Router 8:
> interface Ethernet0/0
> ip address 172.16.1.1 255.255.255.0
> ip mobile arp access-group 1
> !
I should have had:
> Router 8:
> interface Ethernet0/0
> ip address 172.16.1.1 255.255.255.0
>>>ip mobile foreign-service
> !
So, this is different from LAM from a configuration stand point. Mobile IP
was added to 12.0(1)T while LAM has been around since at least 11.3, which
leads me to presume Mobile IP became more of a standard after LAM was added
to the IOS. Just by looking at the documentation you can see that there are
more features with Mobile IP-- particularly security.
LAM:
http://www.cisco.com/warp/customer/cc/pd/iosw/ioft/lam/tech/lamso_wp.htm
Mobile IP:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios121/121cgcr/ip_c
/ipcprt1/1cdmobip.htm
-----Original Message-----
From: John Neiberger [mailto:neiby@ureach.com]
Sent: Saturday, March 30, 2002 10:59 AM
To: Dustin.Yates@ercgroup.com; ccielab@groupstudy.com
Subject: Re: Mobile IP Comprehension Check
I'm not sure about the differences between Mobile IP and Local
Area Mobility. Without the two commands "ip mobile home-agent"
and "ip mobile foreign-agent" this would be a working LAM
config.
What do those two commands add to this configuration? And, why
would we classify this as Mobile IP instead of LAM?
Back to your config, if this is working correctly you should
see /32 routes for users who have moved to R8. The tricky
thing I noticed is that you can't initiate communication with
them because this is ARP-based. The /32 routes won't be
entered into the config until one of those devices issues an
ARP request.
John
---- On Fri, 29 Mar 2002, Dustin.Yates@ercgroup.com
(Dustin.Yates@ercgroup.com) wrote:
> I'm trying to ensure I've got the basic understanding of
Mobile IP
> down...
> I've got a network that is running OSPF between all of the
routers,
> which
> I've verified end-to-end IP connectivity. Here's the highly
simplified
> network:
>
> E0/0 - Router1 ----- OSPF NETWORK ----- Router 8 - E0/0
>
> Now, here's the requirement:
>
> Task: Support users who relocate from Router 1 to Router 8
without
> requiring them to change their IP addresses. Ensure only the
users from
> E0/0 (network 10.1.1.0/24) are allowed to roam on Router 8's
E0/0
> interface.
>
> Assuming all routing is working correctly before making any
changes
> (e.g.,
> Router 1 can ping Router 8's E0/0 address and vice versa), I
believe the
> following provides the minimum mobile IP commands required to
meet this
> task.
>
> Router 1:
> interface Ethernet0/0
> ip address 10.1.1.1 255.255.255.0
> !
> router mobile
> !
> router ospf 1
> redistribute mobile metric 100 subnets
> !
> ip mobile home-agent
>
> Router 8:
> interface Ethernet0/0
> ip address 172.16.1.1 255.255.255.0
> ip mobile arp access-group 1
> !
> router mobile
> !
> router ospf 1
> redistribute mobile metric 100 subnets
> !
> ip mobile foreign-agent
> !
> access-list 1 permit 10.1.1.0 0.0.0.255
>
> So, would this be enough to meet the requirement as stated?
If I
> attached a
> PC to Router 8's Ethernet0/0 interface with IP address of
10.1.1.2,
> should I
> expect this PC to be able to ping 10.1.1.1? What changes in
the routing
> tables should one see if this is working correctly?
>
> TIA!!!
>
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:57:27 GMT-3