BIG-IP® Systems: Upgrading Active-Standby

Systems from Version 10.x to Version 11.x

Version 11.3
 Table of Contents

Table of Contents
Legal Notices.....................................................................................................................................5
Acknowledgments............................................................................................................................7

Chapter 1:  Upgrading BIG-IP Active-Standby Systems to Version 11.x

...............................................................................................................................1 7
Overview: Upgrading BIG-IP active-standby systems............................................................18
DSC components........................................................................................................20
About traffic groups.....................................................................................................21
Task summary........................................................................................................................22
Preparing BIG-IP modules for an upgrade from version 10.x to version 11.x..............22
Preparing BIG-IP active-standby systems for an upgrade...........................................26
Upgrading the standby BIG-IP 2 system.....................................................................27
Upgrading the active BIG-IP 1 system.........................................................................28
Verifying a BIG-IP active-standby upgrade..................................................................29
Implementation result.............................................................................................................30

3
Table of Contents

4
Legal Notices

Publication Date
This document was published on March 22, 2013.

Publication Number
MAN-0374-03

Copyright
Copyright © 2012-2013, F5 Networks, Inc. All rights reserved.
F5 Networks, Inc. (F5) believes the information it furnishes to be accurate and reliable. However, F5 assumes
no responsibility for the use of this information, nor any infringement of patents or other rights of third
parties which may result from its use. No license is granted by implication or otherwise under any patent,
copyright, or other intellectual property right of F5 except as specifically described by applicable user
licenses. F5 reserves the right to change specifications at any time without notice.

Trademarks
Access Policy Manager, Advanced Client Authentication, Advanced Routing, APM, Application Security
Manager, ARX, AskF5, ASM, BIG-IP, BIG-IQ, Cloud Extender, CloudFucious, Cloud Manager, Clustered
Multiprocessing, CMP, COHESION, Data Manager, DevCentral, DevCentral [DESIGN], DNS Express,
DSC, DSI, Edge Client, Edge Gateway, Edge Portal, ELEVATE, EM, Enterprise Manager, ENGAGE, F5,
F5 [DESIGN], F5 Management Pack, F5 Networks, F5 World, Fast Application Proxy, Fast Cache, FirePass,
Global Traffic Manager, GTM, GUARDIAN, IBR, Intelligent Browser Referencing, Intelligent Compression,
IPv6 Gateway, iApps, iControl, iHealth, iQuery, iRules, iRules OnDemand, iSession, L7 Rate Shaping,
LC, Link Controller, Local Traffic Manager, LTM, Message Security Manager, MSM, OneConnect,
OpenBloX, OpenBloX [DESIGN], Packet Velocity, Policy Enforcement Manager, PEM, Protocol Security
Manager, PSM, Real Traffic Policy Builder, Rosetta Diameter Gateway, ScaleN, Signaling Delivery
Controller, SDC, SSL Acceleration, StrongBox, SuperVIP, SYN Check, TCP Express, TDR, TMOS, Traffic
Management Operating System, Traffix Diameter Load Balancer, Traffix Systems, Traffix Systems
(DESIGN), Transparent Data Reduction, UNITY, VAULT, VIPRION, vCMP, virtual Clustered
Multiprocessing, WA, WAN Optimization Manager, WebAccelerator, WOM, and ZoneRunner, are
trademarks or service marks of F5 Networks, Inc., in the U.S. and other countries, and may not be used
without F5's express written consent.
All other product and company names herein may be trademarks of their respective owners.

Export Regulation Notice

This product may include cryptographic software. Under the Export Administration Act, the United States
government may consider it a criminal offense to export this product from the United States.

RF Interference Warning
This is a Class A product. In a domestic environment this product may cause radio interference, in which
case the user may be required to take adequate measures.
Legal Notices

FCC Compliance
This equipment has been tested and found to comply with the limits for a Class A digital device pursuant
to Part 15 of FCC rules. These limits are designed to provide reasonable protection against harmful
interference when the equipment is operated in a commercial environment. This unit generates, uses, and
can radiate radio frequency energy and, if not installed and used in accordance with the instruction manual,
may cause harmful interference to radio communications. Operation of this equipment in a residential area
is likely to cause harmful interference, in which case the user, at his own expense, will be required to take
whatever measures may be required to correct the interference.
Any modifications to this device, unless expressly approved by the manufacturer, can void the user's authority
to operate this equipment under part 15 of the FCC rules.

Canadian Regulatory Compliance

This Class A digital apparatus complies with Canadian ICES-003.

Standards Compliance
This product conforms to the IEC, European Union, ANSI/UL and Canadian CSA standards applicable to
Information Technology products at the time of manufacture.

6
Acknowledgments

This product includes software developed by Bill Paul.

This product includes software developed by Jonathan Stone.
This product includes software developed by Manuel Bouyer.
This product includes software developed by Paul Richards.
This product includes software developed by the NetBSD Foundation, Inc. and its contributors.
This product includes software developed by the Politecnico di Torino, and its contributors.
This product includes software developed by the Swedish Institute of Computer Science and its contributors.
This product includes software developed by the University of California, Berkeley and its contributors.
This product includes software developed by the Computer Systems Engineering Group at the Lawrence
Berkeley Laboratory.
This product includes software developed by Christopher G. Demetriou for the NetBSD Project.
This product includes software developed by Adam Glass.
This product includes software developed by Christian E. Hopps.
This product includes software developed by Dean Huxley.
This product includes software developed by John Kohl.
This product includes software developed by Paul Kranenburg.
This product includes software developed by Terrence R. Lambert.
This product includes software developed by Philip A. Nelson.
This product includes software developed by Herb Peyerl.
This product includes software developed by Jochen Pohl for the NetBSD Project.
This product includes software developed by Chris Provenzano.
This product includes software developed by Theo de Raadt.
This product includes software developed by David Muir Sharnoff.
This product includes software developed by SigmaSoft, Th. Lockert.
This product includes software developed for the NetBSD Project by Jason R. Thorpe.
This product includes software developed by Jason R. Thorpe for And Communications, http://www.and.com.
This product includes software developed for the NetBSD Project by Frank Van der Linden.
This product includes software developed for the NetBSD Project by John M. Vinopal.
This product includes software developed by Christos Zoulas.
This product includes software developed by the University of Vermont and State Agricultural College and
Garrett A. Wollman.
This product includes software developed by Balazs Scheidler ([email protected]), which is protected under
the GNU Public License.
Acknowledgments

This product includes software developed by Niels Mueller ([email protected]), which is protected under
the GNU Public License.
In the following statement, This software refers to the Mitsumi CD-ROM driver: This software was developed
by Holger Veit and Brian Moore for use with 386BSD and similar operating systems. Similar operating
systems includes mainly non-profit oriented systems for research and education, including but not restricted
to NetBSD, FreeBSD, Mach (by CMU).
This product includes software developed by the Apache Group for use in the Apache HTTP server project
(http://www.apache.org/).
This product includes software licensed from Richard H. Porter under the GNU Library General Public
License (© 1998, Red Hat Software), www.gnu.org/copyleft/lgpl.html.
This product includes the standard version of Perl software licensed under the Perl Artistic License (© 1997,
1998 Tom Christiansen and Nathan Torkington). All rights reserved. You may find the most current standard
version of Perl at http://www.perl.com.
This product includes software developed by Jared Minch.
This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit
(http://www.openssl.org/).
This product includes cryptographic software written by Eric Young ([email protected]).
This product contains software based on oprofile, which is protected under the GNU Public License.
This product includes software with glib library utility functions, which is protected under the GNU Public
License.
This product includes software with grub2 bootloader functions, which is protected under the GNU Public
License.
This product includes software with the Intel Gigabit Linux driver, which is protected under the GNU Public
License. Copyright ©1999 - 2012 Intel Corporation.
This product includes software with the Intel 10 Gigabit PCI Express Linux driver, which is protected under
the GNU Public License. Copyright ©1999 - 2012 Intel Corporation.
This product includes RRDtool software developed by Tobi Oetiker (http://www.rrdtool.com/index.html)
and licensed under the GNU General Public License.
This product contains software licensed from Dr. Brian Gladman under the GNU General Public License
(GPL).
This product includes software developed by the Apache Software Foundation (http://www.apache.org/).
This product includes Hypersonic SQL.
This product contains software developed by the Regents of the University of California, Sun Microsystems,
Inc., Scriptics Corporation, and others.
This product includes software developed by the Internet Software Consortium.
This product includes software developed by Nominum, Inc. (http://www.nominum.com).
This product contains software developed by Broadcom Corporation, which is protected under the GNU
Public License.
This product contains software developed by MaxMind LLC, and is protected under the GNU Lesser General
Public License, as published by the Free Software Foundation.
This product includes software developed by Andrew Tridgell, which is protected under the GNU Public
License, copyright ©1992-2000.

8
 BIG-IP® Systems: Upgrading Active-Standby Systems

This product includes software developed by Jeremy Allison, which is protected under the GNU Public
License, copyright ©1998.
This product includes software developed by Guenther Deschner, which is protected under the GNU Public
License, copyright ©2008.
This product includes software developed by www.samba.org, which is protected under the GNU Public
License, copyright ©2007.
This product includes software from Allan Jardine, distributed under the MIT License.
This product includes software from Trent Richardson, distributed under the MIT License.
This product includes vmbus drivers distributed by Microsoft Corporation.
This product includes software from Cavium.
This product includes software from Webroot, Inc.
This product includes software from Maxmind, Inc.
This product includes software licensed from www.samba.org under the GNU Library General Public
License.
This product includes software from OpenVision Technologies, Inc. Copyright ©1993-1996, OpenVision
Technologies, Inc. All Rights Reserved.
This product includes software developed by Matt Johnson, distributed under the MIT License. Copyright
©2012.

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated
documentation files (the "Software"), to deal in the Software without restriction, including without limitation
the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software,
and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions
of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
THE SOFTWARE.
This product includes software from NLnetLabs. Copyright ©2005, 2006. All Rights Reserved.
Redistribution and use in source and binary forms, with or without modification, are permitted provided
that the following conditions are met:
• Redistributions of source code must retain the above copyright notice, this list of conditions and the
following disclaimer.
• Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the
following disclaimer in the documentation and/or other materials provided with the distribution.
• Neither the name of NLnetLabs nor the names of its contributors may be used to endorse or promote
products derived from this software without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS"
AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE
LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR

9
Acknowledgments

CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF

SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY
OF SUCH DAMAGE.
This product includes GRand Unified Bootloader (GRUB) software developed under the GNU Public
License, copyright ©2007.
This product includes Intel QuickAssist kernel module, library, and headers software licensed under the
GNU General Public License (GPL).
This product includes gd-libgd library software developed by the following in accordance with the following
copyrights:
• Portions copyright ©1994, 1995, 1996, 1997, 1998, 2000, 2001, 2002 by Cold Spring Harbor Laboratory.
Funded under Grant P41-RR02188 by the National Institutes of Health.
• Portions copyright ©1996, 1997, 1998, 1999, 2000, 2001, 2002 by Boutell.Com, Inc.
• Portions relating to GD2 format copyright ©1999, 2000, 2001, 2002 Philip Warner.
• Portions relating to PNG copyright ©1999, 2000, 2001, 2002 Greg Roelofs.
• Portions relating to gdttf.c copyright ©1999, 2000, 2001, 2002 John Ellson ([email protected]).
• Portions relating to gdft.c copyright ©2001, 2002 John Ellson ([email protected]).
• Portions copyright ©2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007 2008 Pierre-Alain Joye
([email protected]).
• Portions relating to JPEG and to color quantization copyright ©2000, 2001, 2002, Doug Becker and
copyright ©1994, 1995, 1996, 1997, 1998, 1999, 2000, 2001, 2002, Thomas G. Lane. This software is
based in part on the work of the Independent JPEG Group.
• Portions relating to WBMP copyright 2000, 2001, 2002 Maurice Szmurlo and Johan Van den Brande.
Permission has been granted to copy, distribute and modify gd in any context without fee, including a
commercial application, provided that this notice is present in user-accessible supporting documentation.
This product includes software developed by Oracle America, Inc. Copyright ©2012.
1. Java Technology Restrictions. Licensee shall not create, modify, change the behavior of, or authorize
licensees of ;icensee to create, modify, or change the behavior of, classes, interfaces, or subpackages
that are in any way identified as "java", "javax”, "sun" or similar convention as specified by Oracle in
any naming convention designation. In the event that Licensee creates an additional API(s) which: (a)
extends the functionality of a Java Environment; and (b) is exposed to third party software developers
for the purpose of developing additional software which invokes such additional API, Licensee must
promptly publish broadly an accurate specification for such API for free use by all developer.
2. Trademarks and Logos. This License does not authorize an end user licensee to use any Oracle America,
Inc. name, trademark, service mark, logo or icon. The end user licensee acknowledges that Oracle owns
the Java trademark and all Java-related trademarks, logos and icon including the Coffee Cup and Duke
("Java Marks") and agrees to: (a) comply with the Java Trademark Guidelines at
http://www.oraclc.com/html/3party.html; (b) not do anything harmful to or inconsistent with Oracle's
rights in the Java Marks; and (c) assist Oracle in protecting those rights, including assigning to Oracle
any rights acquired by Licensee in any Java Mark.
3. Source Code. Software may contain source code that, unless expressly licensed for other purposes, is
provided solely for reference purposes pursuant to the terms of your license. Source code may not be
redistributed unless expressly provided for in the terms of your license.
4. Third Party Code. Additional copyright notices and license terms applicable to portion of the Software
are set forth in the THIRDPARTYLICENSEREADME.txt file.
5. Commercial Features. Use of the Commercial Features for any commercial or production purpose
requires a separate license from Oracle. "Commercial Features" means those features identified in Table

10
 BIG-IP® Systems: Upgrading Active-Standby Systems

I-I (Commercial Features In Java SE Product Editions) of tile Software documentation accessible at
http://www.oracle.com/technetwork/java/javase/documentation/index.html.
This product includes utilities developed by Linus Torvalds for inspecting devices connected to a USB bus.
This product includes perl-PHP-Serialization software, developed by Jesse Brown, copyright ©2003, and
distributed under the Perl Development Artistic License (http://dev.perl.org/licenses/artistic.html).
This product includes software licensed from Gerald Combs ([email protected]) under the GNU General
Public License as published by the Free Software Foundation; either version 2 of the License, or any later
version. Copyright ©1998 Gerald Combs.
This product includes software licensed from Rémi Denis-Courmont under the GNU Library General Public
License. Copyright ©2006 - 2011.
This product includes software developed by jQuery Foundation and other contributors, distributed under
the MIT License. Copyright ©2012 jQuery Foundation and other contributors (http://jquery.com/).
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated
documentation files (the "Software"), to deal in the Software without restriction, including without limitation
the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software,
and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions
of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
THE SOFTWARE.
This product includes software developed by Trent Richardson, distributed under the MIT License. Copyright
©2012 jQuery Foundation and other contributors (http://jquery.com/).

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated
documentation files (the "Software"), to deal in the Software without restriction, including without limitation
the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software,
and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions
of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
THE SOFTWARE.
This product includes software developed by Allan Jardine, distributed under the MIT License. Copyright
©2008 - 2012, Allan Jardine, all rights reserved, jQuery Foundation and other contributors
(http://jquery.com/).
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated
documentation files (the "Software"), to deal in the Software without restriction, including without limitation
the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software,
and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

11
Acknowledgments

The above copyright notice and this permission notice shall be included in all copies or substantial portions
of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
THE SOFTWARE.
This product includes software developed by Douglas Gilbert. Copyright ©1992 - 2012 The FreeBSD
Project. All rights reserved.
Redistribution and use in source and binary forms, with or without modification, are permitted provided
that the following conditions are met:
1. Redistributions of source code must retain the above copyright notice, this list of conditions and the
following disclaimer.
2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the
following disclaimer in the documentation and/or other materials provided with the distribution.
THIS SOFTWARE IS PROVIDED BY THE FREEBSD PROJECT ``AS IS'' AND ANY EXPRESS OR
IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO
EVENT SHALL THE FREEBSD PROJECT OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT,
INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING,
BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY
OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING
NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE,
EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
The views and conclusions contained in the software and documentation are those of the authors and should
not be interpreted as representing official policies, either expressed or implied, of the FreeBSD Project.
This product includes software developed as open source software. Copyright ©1994 - 2012 The FreeBSD
Project. All rights reserved.
Redistribution and use in source and binary forms, with or without modification, are permitted provided
that the following conditions are met:
1. Redistributions of source code must retain the above copyright notice, this list of conditions and the
following disclaimer.
2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the
following disclaimer in the documentation and/or other materials provided with the distribution.
3. The names of the authors may not be used to endorse or promote products derived from this software
without specific prior written permission.
THIS SOFTWARE IS PROVIDED ``AS IS'' AND WITHOUT ANY EXPRESS OR IMPLIED
WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.
This product includes cryptographic software written by Eric Young ([email protected]). Copyright ©1998
- 2011 The OpenSSL Project. All rights reserved.
Redistribution and use in source and binary forms, with or without modification, are permitted provided
that the following conditions are met:

12
 BIG-IP® Systems: Upgrading Active-Standby Systems

1. Redistributions of source code must retain the above copyright notice, this list of conditions and the
following disclaimer.
2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the
following disclaimer in the documentation and/or other materials provided with the distribution.
3. All advertising materials mentioning features or use of this software must display the following
acknowledgment: "This product includes software developed by the OpenSSL Project for use in the
OpenSSL Toolkit. (http://www.openssl.org/)"
4. The names "OpenSSL Toolkit" and "OpenSSL Project" must not be used to endorse or promote products
derived from this software without prior written permission. For written permission, please contact
[email protected].
5. Products derived from this software may not be called "OpenSSL" nor may "OpenSSL" appear in their
names without prior written permission of the OpenSSL Project.
6. Redistributions of any form whatsoever must retain the following acknowledgment: "This product
includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit
(http://www.openssl.org/)"
THIS SOFTWARE IS PROVIDED BY THE OpenSSL PROJECT ``AS IS'' AND ANY EXPRESSED OR
IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO
EVENT SHALL THE OpenSSL PROJECT OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT,
INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING,
BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY
OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING
NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE,
EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
This product includes software licensed from William Ferrell, Selene Scriven and many other contributors
under the GNU General Public License, copyright ©1998 - 2006.
This product includes software developed by Thomas Williams and Colin Kelley. Copyright ©1986 - 1993,
1998, 2004, 2007
Permission to use, copy, and distribute this software and its documentation for any purpose with or without
fee is hereby granted, provided that the above copyright notice appear in all copies and that both that
copyright notice and this permission notice appear in supporting documentation. Permission to modify the
software is granted, but not the right to distribute the complete modified source code. Modifications are to
be distributed as patches to the released version. Permission to distribute binaries produced by compiling
modified sources is granted, provided you
1. distribute the corresponding source modifications from the released version in the form of a patch file
along with the binaries,
2. add special version identification to distinguish your version in addition to the base release version
number,
3. provide your name and address as the primary contact for the support of your modified version, and
4. retain our contact information in regard to use of the base software.
Permission to distribute the released version of the source code along with corresponding source modifications
in the form of a patch file is granted with same provisions 2 through 4 for binary distributions. This software
is provided "as is" without express or implied warranty to the extent permitted by applicable law.
This product includes software developed by the Computer Systems Engineering Group at Lawrence
Berkeley Laboratory. Copyright ©1990-1994 Regents of the University of California. All rights reserved.
Redistribution and use in source and binary forms, with or without modification, are permitted provided
that the following conditions are met:

13
Acknowledgments

1. Redistributions of source code must retain the above copyright notice, this list of conditions and the
following disclaimer.
2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the
following disclaimer in the documentation and/or other materials provided with the distribution.
3. All advertising materials mentioning features or use of this software must display the following
acknowledgment: This product includes software developed by the Computer Systems Engineering
Group at Lawrence Berkeley Laboratory.
4. Neither the name of the University nor of the Laboratory may be used to endorse or promote products
derived from this software without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS "AS IS" AND ANY
EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE FOR ANY
DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND
ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
This product includes software developed by Sony Computer Science Laboratories Inc. Copyright ©
1997-2003 Sony Computer Science Laboratories Inc. All rights reserved. Redistribution and use in source
and binary forms, with or without modification, are permitted provided that the following conditions are
met:
1. Redistributions of source code must retain the above copyright notice, this list of conditions and the
following disclaimer.
2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the
following disclaimer in the documentation and/or other materials provided with the distribution.
THIS SOFTWARE IS PROVIDED BY SONY CSL AND CONTRIBUTORS "AS IS" AND ANY EXPRESS
OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN
NO EVENT SHALL SONY CSL OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT,
INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY
OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING
NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE,
EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
This product contains software developed by Google, Inc. Copyright ©2011 Google, Inc.
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated
documentation files (the "Software"), to deal in the Software without restriction, including without limitation
the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software,
and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions
of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,

14
 BIG-IP® Systems: Upgrading Active-Standby Systems

OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN

THE SOFTWARE.

15
Acknowledgments

16
Chapter
1
Upgrading BIG-IP Active-Standby Systems to Version 11.x
Topics:

• Overview: Upgrading BIG-IP active-standby

systems
• Task summary
• Implementation result
Upgrading BIG-IP Active-Standby Systems to Version 11.x

Overview: Upgrading BIG-IP active-standby systems

A BIG-IP® system active-standby pair for version 10.x includes one BIG-IP system operating in active
mode (Device A) and one BIG-IP system operating in standby mode (Device B).

Figure 1: A version 10.x active-standby pair

After preparing the devices for an upgrade to version 11.x, you install version 11.x onto Device B (the
standby device). When you finish the installation of version 11.x onto Device B, it creates a traffic group
called traffic-group-1. The version 11.x traffic group is in standby state on Device B, and Device A (the
version 10.x device) is in active mode. Note that the Unit ID that was used in version 10.x becomes obsolete
in version 11.x.

18
 BIG-IP® Systems: Upgrading Active-Standby Systems

Figure 2: A version 10.x device in active mode and a version 11.x traffic group in standby
state

With version 11.x installed on Device B and traffic-group-1 in standby state, you can install version 11.x
onto Device A, force Device A to standby mode, which changes Device B to active state so that it can pass
traffic, and reboot Device A to the location of the 11.x software image. When you complete upgrading both
devices to version 11.x, the BIG-IP configuration includes a traffic group in active state on Device B, a
traffic group in standby state on Device A, and a device group that includes both devices.

19
Upgrading BIG-IP Active-Standby Systems to Version 11.x

Figure 3: A version 11.x traffic group in active and standby states

An upgrade of BIG-IP active-standby systems to version 11.x involves the following tasks.

Task Description
Preparing Device A (the active mode BIG-IP 1 In preparing to upgrade the active-standby BIG-IP
system) and Device B (the standby mode BIG-IP 2 systems to version 11.x, you need to understand any
system) specific configuration or functional changes from
the previous version, and prepare the systems. You
also download the new version of software from the
AskF5 web site (www.askf5.com) and import the
files onto each device.
Upgrading Device B (the standby mode BIG-IP 2 When you complete preparation of Device B, you
system) can upgrade the software on that device.
Upgrading Device A (the standby mode BIG-IP 1 When you complete upgrading Device B, you can
system) prepare Device A and upgrade the software on
Device A.
Verifying the upgrade Finally, you should verify that your active and
standby BIG-IP systems are functioning properly.
Configuring module-specific settings According to your understanding of the configuration
and functional changes from the previous version,
you can reconfigure any customized module settings.

DSC components
Device service clustering (DSC™) is based on a few key components.

20
 BIG-IP® Systems: Upgrading Active-Standby Systems

Devices
A device is a physical or virtual BIG-IP system, as well as a member of a local trust domain and a device
group. Each device member has a set of unique identification properties that the BIG-IP® system
generates.
Device groups
A device group is a collection of BIG-IP® devices that trust each other and can synchronize, and
sometimes fail over, their BIG-IP configuration data. You can create two types of devices groups: A
Sync-Failover device group contains devices that synchronize configuration data and support traffic
groups for failover purposes when a device becomes unavailable. A Sync-Only device group contains
devices that synchronize configuration data, such as policy data, but do not synchronize failover objects.
Traffic groups
A traffic group is a collection of related configuration objects (such as a virtual IP address and a self IP
address) that run on a BIG-IP device and process a particular type of application traffic. When a BIG-IP
device becomes unavailable, a traffic group can float to another device in a device group to ensure that
application traffic continues to be processed with little to no interruption in service.
Device trust and trust domains
Underlying the success of device groups and traffic groups is a feature known as device trust. Device
trust establishes trust relationships between BIG-IP devices on the network, through mutual
certificate-based authentication. A trust domain is a collection of BIG-IP devices that trust one another
and can therefore synchronize and fail over their BIG-IP configuration data, as well as exchange status
and failover messages on a regular basis. A local trust domain is a trust domain that includes the local
device, that is, the device you are currently logged in to.
Folders and sub folders
Folders and sub-folders are containers for the configuration objects on a BIG-IP device. For every
administrative partition on the BIG-IP system, there is a high-level folder. At the highest level of the
folder hierarchy is a folder named root. The BIG-IP system uses folders to affect the level of granularity
to which it synchronizes configuration data to other devices in the device group.

About traffic groups

A traffic group is a collection of related configuration objects that run on a BIG-IP® device. Together, these
objects process a particular type of traffic on that device. When a BIG-IP device becomes unavailable, a
traffic group floats (that is, fails over) to another device in a device group to ensure that application traffic
continues to be processed with little to no interruption in service. In general, a traffic group ensures that
when a device becomes unavailable, all of the failover objects in the traffic group fail over to any one of
the devices in the device group.
A traffic group is initially active on the device on which you create it, until the traffic group fails over to
another device. For example, if you initially create three traffic groups on Device A, these traffic groups
remain active on Device A until one or more traffic groups fail over to another device. If you want to balance
the traffic group load among the devices in the device group, you can intentionally cause a traffic group to
fail over to another device. You do this using the Force to Standby option of the Configuration utility.

Important: Although a specific traffic group can be active on only one device in a device group,
the traffic group actually resides and is in a standby state on all other device group members, due
to configuration synchronization.

Only certain types of configuration objects can belong to a traffic group. Examples of traffic group objects
are floating self IP addresses and floating virtual IP addresses.

21
Upgrading BIG-IP Active-Standby Systems to Version 11.x

An example of a set of objects in a traffic group is an iApps™ application service. If a device with this traffic
group is a member of a device group, and the device becomes unavailable, the traffic group floats to another
member of the device group, and that member becomes the device that processes the application traffic.

Note: A Sync-Failover device group can support a maximum of 15 traffic groups.

Task summary
The upgrade process involves preparation of the two BIG-IP® devices (Device A and Device B) configured
in an active-standby implementation, followed by the installation and verification of version 11.x on each
device. When you upgrade each device, you perform several tasks. Completing these tasks results in a
successful upgrade to version 11.x on both BIG-IP devices, with a traffic group configured properly for an
active-standby implementation.
Preparing BIG-IP modules for an upgrade from version 10.x to version 11.x
Preparing BIG-IP active-standby systems for an upgrade
Upgrading the standby BIG-IP 2 system
Upgrading the active BIG-IP 1 system
Verifying a BIG-IP active-standby upgrade

Preparing BIG-IP modules for an upgrade from version 10.x to version 11.x
Before you upgrade the BIG-IP® system from version 10.x to version 11.x, you might need to manually
prepare settings or configurations for specific modules.

Access Policy Manager system preparation

The Access Policy Manager® system does not require specific preparation when upgrading from version
10.x to version 11.x. However, additional configuration might be required after completing the upgrade to
version 11.x.

Post-upgrade activities
When you complete upgrading to version 11.x, you should consider the following feature or functionality
changes that occur for the Access Policy Manager systems. Depending on your configuration, you might
need to perform these changes after you upgrade your systems.

Feature or Functionality Description

Sessions All users currently logged in while the upgrade
occurs will need to log in again.
Authentication agents and SSO methods If you have deployments using ActiveSync or
Outlook Anywhere, where the domain name is part
of the user name, you should enable the Split
domain from username option in the login page
agent if the authentication method used in the access
policy requires only the user name for authentication.
In BIG-IP® APM™ 11.x.x, authentication agents and

22
 BIG-IP® Systems: Upgrading Active-Standby Systems

Feature or Functionality Description

SSO methods no longer separates the domain name
from the user name internally.
iRule for processing URI If you have deployments where an iRule is used to
perform processing on internal access control URI,
for example, /my.policy, /myvpn or other URIs
suc as APM system's login page request, you need
to enable the iRule events for internal access control
URIs because by default, BIG-IP APM 11.x.x does
not raise iRule events for internal access control
URIs. However, this can be achieved by adding the
following code to the iRule:
when CLIENT_ACCEPTED {

ACCESS::restrict_irule_events
disable
}

OAM support Manually remove all the OAM server-related

configurations and reconfigure OAM on BIG-IP
APM 11.x.x. OAM configuration has been modified
to support various OAM 11G related use cases.
Citrix support functionality The Citrix iRule is no longer visible to the
administrator because it is integrated natively in
BIG-IP APM 11.x.x. If you have not modified the
iRule, then you must enable the Citrix Support
setting on the virtual server to use Citrix. If you
modified the F5-provided Citrix support iRule and
want to use the modified iRule, you need to contact
F5 support and work with them to replace natively
integrated iRules® with your own version of
Citrix-supported iRules®.
Reporting functionality If you used the adminreports.pl script for your
logging or reporting purposes, this script is no longer
available in BIG-IP APM 11.x.x. You need to
migrate to the new and enhanced reporting and
logging functionality available as a built-in
functionality on version 11.x.x.

Application Security Manager system preparation

The BIG-IP® Application Security Manager™ (ASM™) system does not require specific preparation when
upgrading from version 10.x to version 11.x. No additional configuration is required after completing the
upgrade to version 11.x.

What to expect after upgrading a redundant system

If you update two redundant systems that are running as an active-standby pair with BIG-IP Application
Security Manager (ASM) and BIG-IP® Local Traffic Manager™ (LTM®) provisioned, the system maintains

23
Upgrading BIG-IP Active-Standby Systems to Version 11.x

the active-standby status and automatically creates a Sync-Failover device group and a traffic group containing
both systems. The device group is enabled for BIG-IP ASM (because both systems have ASM provisioned).
You can manually push or pull the updates (including BIG-IP LTM and ASM configurations and policies)
from one system to the other (Device Management > Device Groups, then click Config Sync and choose
Synchronize TO/FROM Group).

Global Traffic Manager system preparation and configuration

BIG-IP® Global Traffic Manager™ (GTM™) systems do not require any preparation to upgrade from version
10.x to version 11.x.

Post-upgrade changes
The following feature or functionality changes occur after you complete the upgrade process to version
11.x.

Feature or Functionality Description

Assigning a BIG-IP system to probe a server to Assigning a single BIG-IP system to probe a server
gather health and performance data to gather health and performance data, in version
10.x, is replaced by a Prober pool in version 11.x.

Link Controller system preparation

The BIG-IP® Link Controller™ (LC™) system does not require specific preparation when upgrading from
version 10.x to version 11.x. No additional configuration is required after completing the upgrade to version
11.x.

Local Traffic Manager system preparation

The BIG-IP® Local Traffic Manager™ (LTM®) system does not require specific preparation when upgrading
from version 10.x to version 11.x. No additional configuration is required after completing the upgrade to
version 11.x.

MAC masquerade addresses for VLANs

Note: If you configured MAC Masquerade addresses for VLANs on the version 10.x devices, one
of the addresses will be included automatically in the MAC Masquerade Address field for
traffic-group-1 during the upgrade.

Protocol Security Module preparation

The BIG-IP® Protocol Security Manager™ (PSM™) does not require specific preparation when upgrading
from version 10.x to version 11.x. No additional configuration is required after completing the upgrade to
version 11.x.

WebAccelerator module preparation and configuration

BIG-IP® WebAccelerator modules require specific preparation tasks and changes to upgrade from version
10.x to version 11.x.

24
 BIG-IP® Systems: Upgrading Active-Standby Systems

Preparation activities
Before you upgrade the BIG-IP® WebAccelerator™ modules from version 10.x to version 11.x, you need
to prepare the systems, based on your configuration. The following table summarizes the applicable tasks
that you need to complete.

Feature or Functionality Preparation Task

Symmetric deployment You must reconfigure symmetric WebAccelerator
modules as asymmetric systems before you upgrade
them from version 10.x to version 11.x.

Important: Version 11.x does not support

symmetric WebAccelerator modules.

Unpublished policies You must publish any policies that you want to
migrate to version 11.x. Only published policies are
migrated into version 11.x.
Signed policies Signed policies are not supported in version 11.x. If
you use signed policies, you must replace them with
predefined or user-defined policies before upgrading.
Configuration files Upgrading from version 10.x to version 11.x does
not include custom changes to configuration files.
After upgrading to version 11.x, you need to
manually restore any customizations made to your
configuration files by using the Configuration utility
or Traffic Management Shell (tmsh). The following
list includes examples of configuration files that
might have been customized:
• /config/wa/globalfragment.xml.10.x.0;
in version 11.x, all objtype entries are provided
in tmsh.
• /config/wa/pvsystem.conf.10.x.0
• /config/wa/pvsystem.dtd.10.x.0
• /config/wa/transforms/common.zip.10.x.0;
version 11.x does not include transforms.

Debug Options X-PV-Info response headers in version 10.x are

changed to X-WA-Info response headers in version
11.x. The default setting for X-WA-Info Headers
is None (disabled). To use X-WA-Info response
headers, you will need to change this setting, and
update any associated iRules® or scripts, accordingly.

Post-upgrade activities
When you complete upgrading to version 11.x, you should consider the following feature or functionality
changes that occur for the WebAccelerator modules. Depending upon your configuration, you might need
to perform these changes after you upgrade the systems.

25
Upgrading BIG-IP Active-Standby Systems to Version 11.x

Feature or Functionality Description

Web acceleration Web acceleration functionality requires configuration
of the Web Acceleration profile.

Important: You must enable an

WebAccelerator module application in the
Web Acceleration profile to enable the
WebAccelerator module.

Compression Compression functionality requires configuration of

the HTTP Compression profile in version 11.x.
Request logging Request logging does not migrate to version 11.x.
You must recreate the configuration after upgrading
by using the Request Logging profile.
Policy logging Policy logging does not migrate to version 11.x. You
must recreate the configuration after upgrading by
using the Request Logging profile.
URL normalization URL normalization is not supported in version 11.x.
ESI functionality Edge Side Include (ESI) functionality in the
WebAccelerator module is not supported in version
11.x, with the exception of ESI invalidations.
iControl® backward compatibility Backward compatibility for iControl Compression
and RAM Cache API settings in the HTTP profile
is not supported in version 11.x. These settings
appear in the HTTP Compression and Web
Acceleration profiles in version 11.x.

WAN Optimization Manager preparation

BIG-IP® WAN Optimization Manager™ (WOM®) systems do not require specific preparation when upgrading
from version 10.x to version 11.x. However, in a redundant system configuration, you must upgrade the
standby system first (to avoid interrupting traffic on the active system), and then upgrade the other system.
No additional configuration is required after completing the upgrade to version 11.x.

Preparing BIG-IP active-standby systems for an upgrade

The following prerequisites apply when you upgrade BIG-IP® active and standby devices from version 10.x
to 11.x.
• The BIG-IP systems (Device A and Device B) are configured as an active-standby pair.
• Each BIG-IP device is running the same version of 10.x software.
• The BIG-IP active-standby devices are the same model of hardware.
When you upgrade a BIG-IP active-standby pair from version 10.x to 11.x, you begin by preparing the
devices.

Note: If you prefer to closely observe the upgrade of each device, you can optionally connect to
the serial console port of the device that you are upgrading.

26
 BIG-IP® Systems: Upgrading Active-Standby Systems

1. For each device, complete the following steps to prepare the configuration and settings.
a) Examine the Release Notes for specific configuration requirements, and reconfigure the systems, as
necessary.
For example, you must reconfigure version 10.x symmetric WebAccelerator modules as asymmetric
systems before upgrading to version 11.x.
b) Examine the Release Notes for specific changes to settings that occur when upgrading from version
10.x to 11.x, and complete any in-process settings.
For example, you must publish any unpublished BIG-IP® WebAccelerator™ module policies in order
for them to migrate to version 11.x.

2. From the device that is running the latest configuration, synchronize the configuration to the peer unit.
a) On the Main menu, click System > High Availability > ConfigSync.
A message appears for the Status Message.
b) Click Synchronize TO Peer.
3. For each device, reactivate the license.
a) On the Main menu, click System > License.
b) Click Re-activate.
c) In the Activation Method area, select the Automatic (requires outbound connectivity) option.
d) Click Next.
The BIG-IP software license renews automatically.

4. For each device, click System > High Availability > Redundancy, and, from the Redundancy State
Preference list, select None.
5. For each device, create a backup file.
a) Access the tmsh command line utility.
b) At the prompt, type save /sys ucs /shared/filename.ucs.
c) Copy the backup file to a safe location on your network.
6. Download the BIG-IP version 11.x .iso file from the AskF5 downloads web site
(https://www.downloads.f5.com) to a preferred location.
7. Using a tool or utility that computes an md5 checksum, verify the integrity of the BIG-IP version 11.x
.iso file.
8. Import the version 11.x software image file to each device.
a) On the Main menu, click System > Software Management > Image List > Import.
b) Click Choose File, locate and click the image file, click Open, and click Import.
c) When the software image file completes uploading to the BIG-IP device, click OK.
A link to the image file, but not to the .md5 file, appears in the Software Image list.

The BIG-IP devices are prepared to install the version 11.x software onto Device B (the standby BIG-IP 2
device).

Upgrading the standby BIG-IP 2 system

The following prerequisites apply for this task.
• Device A (the active BIG-IP® 1 system) and Device B (the standby BIG-IP 2 system) must be prepared
to upgrade Device B with version 11.x software.
• The version 11.x software image file is downloaded and available.

27
Upgrading BIG-IP Active-Standby Systems to Version 11.x

After you prepare Device A (the active BIG-IP 1 system) and Device B (the standby BIG-IP 2 system) for
upgrading the software, you can perform these steps to install the version 11.x software onto Device B.

1. On the Main menu, click System > Software Management > Image List.
2. In the Available Images area, select the check box for the version 11.x software image.
3. Select a location to install the image, and click Install.

Important: In the Install Status list for the specified location, a progress bar indicates the
status of the installation. Ensure that installation successfully completes, as indicated by the
progress bar, before proceeding.

4. Reboot the device to the location of the installed version 11.x software image.
a) On the Main menu, click System > Software Management > Boot Locations.
b) In the Boot Location list, click the boot location of the installed version 11.x software image.
c) Click Activate.
The BIG-IP device reboots to the version 11.x boot location with traffic-group-1 in standby state.

Note: If the device appears to be taking a long time to reboot, do not cycle the power off
and on. Instead, verify the status of the device by connecting to its serial console port. The
device might be performing firmware upgrades.

Version 11.x software is installed on Device B, with traffic-group-1 in standby state.

Upgrading the active BIG-IP 1 system

The following prerequisites apply in upgrading Device A (the BIG-IP® 1 system).
• Device A (the version 10.x BIG-IP 1 system) must be prepared to upgrade the software to version 11.x.
• Device A is in active mode.
• Device B (the version 11.x BIG-IP device with traffic-group-1) is in standby state.
After you prepare Device A (the standby BIG-IP 1 system) for upgrading the software, you can perform
these steps to upgrade the software to version 11.x.

1. On the Main menu, click System > Software Management > Image List.
2. In the Available Images area, select the check box for the version 11.x software image.
3. Select a location to install the image, and click Install.

Important: In the Install Status list for the specified location, a progress bar indicates the
status of the installation. Ensure that installation successfully completes, as indicated by the
progress bar, before proceding.

4. Force the BIG-IP device (Device A) to standby mode.

a) On the Main menu, click System > High Availability > Redundancy.
b) Click Force to Standby.
The BIG-IP device (Device A) changes to standby mode and the peer BIG-IP device (Device B)
changes to active state.

Important: Once the peer BIG-IP device (Device B) changes to active state, ensure that it
passes traffic normally.

28
 BIG-IP® Systems: Upgrading Active-Standby Systems

5. Reboot the BIG-IP device (Device A) to the location of the installed version 11.x software image.
a) On the Main menu, click System > Software Management > Boot Locations.
b) In the Boot Location list, click the boot location of the installed version 11.x software image.
c) Click Activate.
The BIG-IP device (Device A) reboots to the version 11.x boot location with traffic-group-1 in
standby state.

Note: If the device appears to be taking a long time to reboot, do not cycle the power off
and on. Instead, verify the status of the device by connecting to its serial console port. The
device might be performing firmware upgrades.

6. On the Main tab, click Device Management > Overview.

7. In the Devices area of the screen, in the Sync Status column, select the device that shows a sync status
of Changes Pending.
8. In the Sync Options area of the screen, select Sync Device to Group.
9. Click Sync.

Version 11.x software is installed on Device A (the BIG-IP system with traffic-group-1 in standby state).

Verifying a BIG-IP active-standby upgrade

When you have completed upgrading the BIG-IP active-standby pair from version 10.x to version 11.x,
you should verify that the upgraded configuration is working properly. Perform the following steps to verify
the version 11.x upgrade.

1. Verify the Platform configuration for each device.

a) On the Main menu, click System > Platform.
b) For the Root Folder Device Group setting, verify that the device group is identical on the pair of
devices.
c) From the Default Traffic Group list, verify that the correct traffic group (traffic-group-1) is selected.
2. Verify the configuration for each device.
a) On the Main menu, click Device Management > Devices.
b) Verify the following information for the device and the peer device.
• active-standby status
• device name
• management IP address
• hostname
• TMOS version

c) On the Main menu, click Device Management > Device Trust > Peer List.
d) Verify that the peer device is specified as a Peer Authority Device.

Note: Ensure that all information for the peer device appears correctly and complete.

3. Verify the traffic groups for each device.

a) On the Main menu, click Device Management > Traffic Groups.
b) Click traffic-group-1.

29
Upgrading BIG-IP Active-Standby Systems to Version 11.x

c) If you configured MAC Masquerade addresses for VLANs on the version 10.x devices, verify that
the traffic-group-1 includes an address in the MAC Masquerade Address field.
d) Verify that the floating traffic group is correct.
e) Verify that the failover objects are correct.
4. Verify the Current ConfigSync State for each device.
a) On the Main menu, click Device Management > Overview.
b) In the Devices area of the screen, in the Sync Status column, verify that each device shows a sync
status of green.

Implementation result
Your upgrade of the BIG-IP® active-standby pair from version 10.x to version 11.x is now complete. The
version 11.x configuration includes a device group with two devices (Device A and Device B) and a traffic
group (traffic-group-1), with the traffic group on one device (Device B) in active state and the traffic
group on the other device (Device A) in standby state.

Figure 4: A version 11.x device group and traffic group

30
 Index

Index
A F
active-standby software upgrade failover
overview 18 and traffic groups 21
results 30 folders
task summary 22 defined 20
active-standby systems
upgrading 17
availability
M
during failover 21 migration
preparation 24
B preparation for APM 22
WA preparation 24
BIG-IP system WOM preparation 26
preparing for upgrade 26
upgrading to version 11.x 27, 28
BIG-IP system version 11.x upgrade
T
verifying 29 traffic groups
defined 20, 21
D maximum number supported 21

device availability
defined 21
U
device groups upgrading
defined 20 and ASM 23
device objects and PSM 24
defined 20 and two redundant ASM systems 23
devices preparation 24
defined 20 preparation for APM 22
selecting for failover 21 WA preparation 24
device trust WOM preparation 26
defined 20

V
version 11.x upgrade
preparing BIG-IP modules 22

31
Index

32