Forum Discussion
Copy over self IPs from several partitions
- Nov 16, 2023
I wonder if this is as simple as not setting a default route domain for your other partitions? Try to set that before the import, rather than modifying the IPs to put the route domain in with the %xxx syntax. You have to first define the route domain object (net route-domain), then set the partition to it.
admin@(west)(cfg-sync Standalone)(ModuleNotLicensed::Active)(/Common)(tmos)# create net route-domain rd_foo id 1234 vlans replace-all-with { con1 }
admin@(west)(cfg-sync Standalone)(ModuleNotLicensed::Active)(/Common)(tmos)# list auth partition foo all-properties
auth partition foo {
default-route-domain 0
description none
}
admin@(west)(cfg-sync Standalone)(ModuleNotLicensed::Active)(/Common)(tmos)# modify auth partition foo default-route-domain 1234
admin@(west)(cfg-sync Standalone)(ModuleNotLicensed::Active)(/Common)(tmos)# list auth partition foo all-properties
auth partition foo {
default-route-domain 1234
description none
}
During Ericsson POC in 2011 with F5 presales, I was able to pair Viprion with VE.
Even persistence records were synchronized.
So, I suggest you to try:
1. break current pairing then shutdown the standby unit.
2. pair the active unit with one of the new HW.
3. switchover the new HW to active node
4. break pairing then shutdown the standbay unit (old HW)
5. pair with second new HW
Thanks for your reply ! The steps you listed are actually my plan 🙂 but before to do that I have to configure the network objects on the new servers. Given the large amount of objects I tried to automate that as much as I could but I'm facing some issues.
- zamroni777Nov 17, 2023Nacreous
because old standby HW is shutted down, you can use the old standby's physical links and self & mgmt IP configuration on the new HW.
After that, pair this new HW as standby of old active HW.
Recent Discussions
Related Content
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com