Migrate to 11.2.1

After I finish upgrading the standby unit, it comes up as Standalone (standby). How can I do a config sync and make this node Active? have you seen this?

 

 

Manual Chapter: Upgrading BIG-IP ActiveStandby Systems to Version 11X

 

http://support.f5.com/kb/en-us/products/big-ip_ltm/manuals/product/tmos-active-standby-upgrade-11-1-0/1.html

Hi Nitass,

 

I went through the manual but 2 things:

 

1. There is a point in the manual where both the nodes go offline. We cannot affort to bring our network down.

 

2. After the nodes come up, in the Config sync status, I see changes Pending, even though the logs say Sync complete

 

Dec 4 15:25:34 elkmdr02ltm02 notice mcpd[6152]: 01071431:5: Attempting to connect to CMI peer 192.168.2.101 port 6699

 

Dec 4 15:25:34 elkmdr02ltm02 err mcpd[6152]: 0107142f:3: Can't connect to CMI peer 192.168.2.101, port:6699, Transport endpoint is not connected

 

Dec 4 15:25:34 elkmdr02ltm02 notice mcpd[6152]: 0107143a:5: CMI reconnect timer: enabled

 

Dec 4 15:25:34 elkmdr02ltm02 notice mcpd[6152]: 01071431:5: Attempting to connect to CMI peer 192.168.2.101 port 6699

 

Dec 4 15:25:34 elkmdr02ltm02 notice mcpd[6152]: 01071432:5: CMI peer connection established to 192.168.2.101 port 6699

 

Dec 4 15:25:35 elkmdr02ltm02 info devmgmtd[4906]: com.f5.devmgmt.certmgmt.TrustConfigUpdateForHAPairTask.run(TrustConfigUpdateForHAPairTask.java:447): Trust configuration upgrade for HA Pair is completed.

 

Dec 4 15:25:36 elkmdr02ltm02 notice mcpd[6152]: 01071451:5: Received CMI hello from /Common/elkmdr02ltm01.elkmdr02.snptt.spcsdns.net

 

Dec 4 15:25:39 elkmdr02ltm02 notice mcpd[6152]: 0107143a:5: CMI reconnect timer: disabled, all peers are connected

 

Dec 4 15:35:35 elkmdr02ltm02 notice mcpd[6152]: 01071038:5: aa:39:7a:c2:10:d7:62:e5:78:9f:02:72:52:48:1b:d3:8a:65:66:26

 

Dec 4 15:35:36 elkmdr02ltm02 notice mcpd[6152]: 01071038:5: aa:39:7a:c2:10:d7:62:e5:78:9f:02:72:52:48:1b:d3:8a:65:66:26

 

Dec 4 15:35:36 elkmdr02ltm02 notice mcpd[6152]: 01071038:5: Unit key read from the hardware.

 

Dec 4 15:35:38 elkmdr02ltm02 notice mcpd[6152]: 010714a0:5: Sync of device group /Common/device-group-failover-f14c8472a99d to commit id 244 5818192888493070010 /Common/elkmdr02ltm01.elkmdr02.snptt.spcsdns.net from device /Common/elkmdr02ltm01.elkmdr02.snptt.spcsdns.net complete.

 

Dec 4 15:37:41 elkmdr02ltm02 notice mcpd[6152]: 01071038:5: aa:39:7a:c2:10:d7:62:e5:78:9f:02:72:52:48:1b:d3:8a:65:66:26

 

Dec 4 15:37:41 elkmdr02ltm02 notice mcpd[6152]: 01071038:5: aa:39:7a:c2:10:d7:62:e5:78:9f:02:72:52:48:1b:d3:8a:65:66:26

 

Dec 4 15:37:41 elkmdr02ltm02 notice mcpd[6152]: 01071038:5: Unit key read from the hardware.

 

Dec 4 15:37:43 elkmdr02ltm02 notice mcpd[6152]: 010714a0:5: Sync of device group /Common/device-group-failover-f14c8472a99d to commit id 245 5818193429260659912 /Common/elkmdr02ltm01.elkmdr02.snptt.spcsdns.net from device /Common/elkmdr02ltm01.elkmdr02.snptt.spcsdns.net complete.

 

 

1. There is a point in the manual where both the nodes go offline. We cannot affort to bring our network down.i never tested but thinking serial failover may be helpful.

 

 

Note: You can use serial failover only when the device group contains a maximum of two devices.

 

For a group with more than two devices, network failover is required. Also, if the hardware platform

 

is a VIPRION® platform, you must use network failover.Serial and network failover

 

http://support.f5.com/content/kb/en-us/products/big-ip_ltm/manuals/product/tmos-redundant-systems-config-11-1-0/_jcr_content/pdfAttach/download/file.res/tmos-redundant-systems-config-11-1-0.pdf

 

 

2. After the nodes come up, in the Config sync status, I see changes Pending, even though the logs say Sync completewhat is "tmsh show cm sync-status" output?

Ameya

 

 

I don't think you can avoid downtime when migrating from v10 to v11 due to the changes in the failover topology from one version to the next. Even with serial failover I still think because v11 now has traffic groups it'll come up as Active by default and the v10 will also be Active. When I recently did this upgrade that was my understanding anyway.

 

 

I'd always plan for and schedule downtime anyway just in case.

 

 

As for your issue re the Config Sync - I had a similar issue and the resolution was to remove the one device reporting changes pending from the device group and then re-add it.

 

 

Hope this helps,

 

N

Ameya

 

 

When I perform upgrading 10.2.4 to 11.2.1 After I finish upgrading the standby unit, it comes up as Standalone (standby) too

 

 

Is this happen because you forget to clear Network failover address or unplug Hardwire failover ?

 

 

Thank you

Ameya

 

 

When I perform upgrading 10.2.4 to 11.2.1 After I finish upgrading the standby unit, it comes up as Standalone (standby) too

 

 

Is this happen because you forget to clear Network failover address or unplug Hardwire failover ?

 

 

Thank you