Foreign and Anchor with different Virtual IP

[tomas.jacobsson]

I am planning to replace the Virtual IP 1.1.1.1 on most controllers with 192.0.2.x. I will not be able to change all at the same time, so I will have different IP between Foreign and Anchor controllers on some sites for a while (and possibly indefinitely since I have no access to some Foreign controllers).

I have tested with Foreign and Anchor in the Mobility Group and different Virtual IP, and DHCP relay seems to be working and also Web Auth. We have single foreign controllers so client roaming is not an issue.

Can anyone think of any other problem that could occur between foreign and anchor if they have different Virtual IPs? Does the EoIP tunnel use the Virtual IP at all? Should I risk it?

/Tomas

[Rasika Nayanajith · Accepted solution]

As long as it works you can give it a go

Rasika

[tomas.jacobsson]

Well, nobody is contradicting so I'll give it a go.