AskF5 - Manual Chapter - Upgrading Version 11

2/15/2016
AskF5 | Manual Chapter: Upgrading Version 11.x BIG-IP Software
Print
Manual Chapter: Upgrading Version 11.x BIG-IP

Software
AppliesTo: Hide Versions

BIG-IP LTM
11.6.0, 11.5.4, 11.5.3, 11.5.2,
11.5.1, 11.5.0
BIG-IP AAM
11.6.0, 11.5.4, 11.5.3, 11.5.2,
11.5.1, 11.5.0
Introductiontoupgradingversion11.xBIGIPsoftware
Version11.xBIGIPsystemsaretypicallyconfiguredtoemploythe
functionalityofadevicegroup.Whenyouupgradeversion11.xBIGIP
softwareforaBIGIPsystemdevicegroup,tothenewversionsoftware,you
canuseasimplesequenceofstepstosuccessfullyupgradeeachdevice
withinthedevicegroup.Thefollowingstepsenableyoutopreparefora
softwareupgrade,performtheupgrade,andthenverifythattheupgrade
successfullycompleted.
1.PreparingBIGIPmodulesforanupgrade
2.PreparingBIGIPdevicegroupsforanupgrade
3.Upgradingeachdevicewithinthedevicegroup
4.Changingstatesofthetrafficgroups
5.ConfiguringHAgroups(ifapplicable)
6.Configuringmodulespecificsettings
7.Verifyingthesoftwareupgradeforthedevicegroup
BIG-IP AFM
11.6.0, 11.5.4, 11.5.3, 11.5.2,
11.5.1, 11.5.0
BIG-IP Analytics
11.6.0, 11.5.4, 11.5.3, 11.5.2,
11.5.1, 11.5.0
BIG-IP APM
11.6.0, 11.5.4, 11.5.3, 11.5.2,
11.5.1, 11.5.0
BIG-IP ASM
11.6.0, 11.5.4, 11.5.3, 11.5.2,
11.5.1, 11.5.0
BIG-IP GTM
11.6.0, 11.5.4, 11.5.3, 11.5.2,
11.5.1, 11.5.0
BIG-IP Link Controller

11.6.0, 11.5.4, 11.5.3, 11.5.2,
11.5.1, 11.5.0
BIG-IP PEM
11.6.0, 11.5.4, 11.5.3, 11.5.2,
11.5.1, 11.5.0
Overview:Upgradingaversion11.xBIGIPdevicegroup
ABIGIPsystemdevicegroupforversion11.xincludestwoormoreBIGIPsystems,withoneormoretraffic
groupsoperatinginactivestate.Inthisexample,aversion11.xdevicegroupincludesoneBIGIPsystemwith
trafficgroup1operatinginactivestate(DeviceA),oneBIGIPsystemwithtrafficgroup2operatinginactive
state(DeviceB),andoneBIGIPsystemwithtrafficgroup3operatinginactivestate(DeviceC).
Important: If your version 11.x device group includes HA groups, note that an HA group applies to the respective
device in version 11.0 through 11.4.x, whereas an HA group applies to a traffic group on the device in version
11.5, and later.
https://support.f5.com/kb/en-us/products/big-ip_ltm/manuals/product/bigip-11x-software-upgrade-11-5-0/1.print.html
1/21
2/15/2016
Aversion11.xdevicegroup
Whenupgradingan11.xdevicegrouptothenewversionsoftware,youfirstneedtoprepareyourdevices.After
preparingthedevices,youforceDeviceAtoofflinestate,andinstallthenewversionsoftwareontoDeviceA.
WhenyoufinishtheinstallationofthenewversionsoftwareontoDeviceA,thetrafficgroupsremaininstandby
stateonDeviceA,andinactivestateonDeviceBandDeviceC.
Important: Once Device A reboots, if the BIG-IP system is configured to use a network hardware security module
(HSM), you must reinstall network HSM client software on Device A before upgrading Device B, to ensure that
traffic groups using the network HSM function properly.
2/21
2/15/2016
AdevicegroupwithDeviceAupgradedtothenewversionsoftware,andtrafficgroupsinstandbystate
WiththenewversionsoftwareinstalledonDeviceAandalltrafficgroupsinstandbystate,youforceDeviceBto
offlinestate,changingthetrafficgroupsonDeviceAtoactivestatesothattheycanpasstraffic.Youcanthen
installthenewversionsoftwareontoDeviceB,andrebootDeviceBtothelocationofthenewversionsoftware
image.
Important: Once Device B reboots, if the BIG-IP system is configured to use a network HSM, you must reinstall
network HSM client software on Device B before upgrading Device C, to ensure that traffic groups using the
network HSM function properly.
3/21
2/15/2016
AdevicegroupwithDeviceBupgradedtothenewversionsoftware,andtrafficgroupsinstandbystate
OnceDeviceBreboots,youcanforceDeviceCtoofflinestate,makingtrafficgroup3activeonDeviceB.When
youcompleteupgradingDeviceCtothenewversionsoftwareandrebootDeviceC,theBIGIPconfiguration
includestrafficgroup1andtrafficgroup2inactivestateonDeviceA,trafficgroup3inactivestateonDeviceB,
andadevicegroupthatincludesalldevices.IfyouuseHAgroups,observethattheHAgrouponDeviceA,
DeviceB,andDeviceCappliestoeachtrafficgroup.
Important: Once Device C reboots, if the BIG-IP system is configured to use a network HSM, you must reinstall
network HSM client software on Device C, to ensure that traffic groups using the network HSM function properly.
4/21
2/15/2016
Adevicegroupwithalldevicesupgradedtothenewversionsoftware
Onceeachdeviceisupgradedtothenewversionsoftware,youcanreconfigurethetrafficgroupstobecome
activeonthedevicesthatyouwantbyforcingtheactivetrafficgrouponadevicetostandbystate.Whenforcing
thetrafficgrouptostandbystate,youcantargetthedeviceuponwhichyouwantthattrafficgrouptoruninactive
state.Forexample,youcanforcetrafficgroup2onDeviceAintostandbystate,andintoactivestateonDevice
B,andthenforcetrafficgroup3onDeviceBintostandbystate,andintoactivestateonDeviceC.Additionally,if
youuseHAgroups,youcancreateauniqueHAgroupforeachtrafficgrouponeachdevice.
5/21
2/15/2016
Adevicegroupwithanactivetrafficgrouponeachdevice
Summaryoftasks
TASK
DESCRIPTION
Preparingthe
InpreparingtoupgradetheBIGIPsystemstothenewversionsoftware,youneed
devicesinthedevice tounderstandanyspecificconfigurationorfunctionalchangesfromtheprevious
group
version,andpreparethesystems.Youalsodownloadthenewversionofsoftware
fromtheAskF5website(http://support.f5.com/kb/en-us.html)andimportthe
filesontoeachdevice.
UpgradingDeviceA WhenyoucompletepreparationofDeviceA,youcanforcethatdevicetooffline
state,changingthosetrafficgroupstoactivestateonanotherdeviceinthetraffic
group,andthenupgradethesoftwareonDeviceA.
Important: Once Device A reboots, if the BIG-IP system is configured to use a network
HSM, you must reinstall network HSM client software on Device A before upgrading
Device B, to ensure that traffic groups using the network HSM function properly.
UpgradingDeviceB WhenyoucompletepreparationofDeviceB,youcanforcethatdevicetooffline
group,andthenupgradethesoftwareonDeviceB.
Important: Once Device B reboots, if the BIG-IP system is configured to use a network
HSM, you must reinstall network HSM client software on Device B before upgrading
Device C, to ensure that traffic groups using the network HSM function properly.
UpgradingDeviceC WhenyoucompletepreparationofDeviceC,youcanforcethatdevicetooffline
group,andthenupgradethesoftwareonDeviceC.
Important: Once Device C reboots, if the BIG-IP system is configured to use a network
HSM, you must reinstall network HSM client software on Device C to ensure that traffic
groups using the network HSM function properly.
6/21
2/15/2016
Changingstatesof Whenyoufinishupgradingallofthedevices,youcanrestoretheconfigurationof
trafficgroups
activetrafficgroupsoneachdevice.
Verifyingtheupgrade Finally,youshouldverifythattheBIGIPdevicegroupisfunctioningproperly.
ConfiguringHA
Whenyoufinishupgradingadevice,theHAgrouponthedevice(inversion11.5,
groups
andlater)appliestoatrafficgroup,asopposedtothedevice.Youcancreatea
uniqueHAgroupforeachtrafficgrouponeachdevice,asnecessary.
Configuringmodule Accordingtoyourunderstandingoftheconfigurationandfunctionalchangesfrom
specificsettings
thepreviousversion,youcanreconfigureanycustomizedmodulesettings.
DSCcomponents
Deviceserviceclustering(DSC)isbasedonafewkeycomponents.
Devices
AdeviceisaphysicalorvirtualBIGIPsystem,aswellasamemberofalocaltrustdomainandadevice
group.EachdevicememberhasasetofuniqueidentificationpropertiesthattheBIGIPsystemgenerates.
Fordevicegroupsconfiguredforfailover,itisimportantthatthedevicewiththesmallestcapacityhasthe
capacitytoprocessalltrafficgroups.Thisensuresapplicationavailabilityintheeventthatallbutone
deviceinthedevicegroupbecomeunavailableforanyreason.
Devicegroups
AdevicegroupisacollectionofBIGIPdevicesthattrusteachotherandcansynchronize,and
sometimesfailover,theirBIGIPconfigurationdata.Youcancreatetwotypesofdevicesgroups:ASync
Failoverdevicegroupcontainsdevicesthatsynchronizeconfigurationdataandsupporttrafficgroupsfor
failoverpurposeswhenadevicebecomesunavailable.ASyncOnlydevicegroupcontainsdevicesthat
synchronizeconfigurationdata,suchaspolicydata,butdonotsynchronizefailoverobjects.TheBIGIP
systemsupportseitherhomogeneousorheterogeneoushardwareplatformswithinadevicegroup.
Important: BIG-IP module provisioning must be equivalent on all devices within a device group. For
example, module provisioning is equivalent when all device group members are provisioned to run BIG-IP
Local Traffic Manager (LTM) and BIG-IP Application Security Manager (ASM) only. Maintaining equivalent
module provisioning on all devices ensures that any device in the device group can process modulespecific application traffic in the event of failover from another device.
Trafficgroups
Atrafficgroupisacollectionofrelatedconfigurationobjects(suchasavirtualIPaddressandaselfIP
address)thatrunonaBIGIPdeviceandprocessaparticulartypeofapplicationtraffic.WhenaBIGIP
devicebecomesunavailable,atrafficgroupcanfloattoanotherdeviceinadevicegrouptoensurethat
applicationtrafficcontinuestobeprocessedwithlittletonointerruptioninservice.
Devicetrustandtrustdomains
Underlyingthesuccessofdevicegroupsandtrafficgroupsisafeatureknownasdevicetrust.Device
trustestablishestrustrelationshipsbetweenBIGIPdevicesonthenetwork,throughmutualcertificate
basedauthentication.AtrustdomainisacollectionofBIGIPdevicesthattrustoneanotherandcan
thereforesynchronizeandfailovertheirBIGIPconfigurationdata,aswellasexchangestatusandfailover
messagesonaregularbasis.Alocaltrustdomainisatrustdomainthatincludesthelocaldevice,thatis,
thedeviceyouarecurrentlyloggedinto.
Folders
FoldersarecontainersfortheconfigurationobjectsonaBIGIPdevice.Foreveryadministrativepartition
ontheBIGIPsystem,thereisahighlevelfolder.Atthehighestlevelofthefolderhierarchyisafolder
namedroot.TheBIGIPsystemusesfolderstoaffectthelevelofgranularitytowhichitsynchronizes
configurationdatatootherdevicesinthedevicegroup.
Abouttrafficgroups
Atrafficgroupisacollectionofrelatedconfigurationobjects,suchasafloatingselfIPaddress,avirtualIP
address,andaSNATtranslationaddress,thatrunonaBIGIPdevice.Together,theseobjectsprocessa
particulartypeofapplicationtrafficonthatdevice.WhenaBIGIPdevicebecomesunavailable,atrafficgroup
floats(thatis,failsover)toanotherdeviceinadevicegrouptoensurethatapplicationtrafficcontinuestobe
processedwithlittletonointerruptioninservice.Ingeneral,atrafficgroupensuresthatwhenadevicebecomes
unavailable,allofthefailoverobjectsinthetrafficgroupfailovertoanyoneoftheavailabledevicesinthedevice
group.
7/21
2/15/2016
Atrafficgroupisinitiallyactiveonthedeviceonwhichyoucreateit,untilthetrafficgroupfailsovertoanother
device.Forexample,ifyouinitiallycreatethreetrafficgroupsonDeviceA,thesetrafficgroupsremainactiveon
DeviceAuntiloneormoretrafficgroupsfailovertoanotherdevice.Ifyouwantanactivetrafficgrouptobecome
activeonadifferentdeviceinthedevicegroupwhenfailoverhasnotoccurred,youcanintentionallyforcethe
trafficgrouptoswitchtoastandbystate,therebycausingfailovertoanotherdevice.
OnlyobjectswithfloatingIPaddressescanbemembersofafloatingtrafficgroup.
AnexampleofasetofobjectsinatrafficgroupisaniAppsapplicationservice.Ifadevicewiththistrafficgroupis
amemberofadevicegroup,andthedevicebecomesunavailable,thetrafficgroupfloatstoanothermemberof
thedevicegroup,andthatmemberbecomesthedevicethatprocessestheapplicationtraffic.
Note: A Sync-Failover device group can support a maximum of 15 floating traffic groups.
Aboutforcingadeviceoffline
YoucanforceaBIGIPdeviceintoanofflinestate,whichstopsthatdevicefromprocessingorrespondingtolocal
trafficconnections.Whenthedeviceisinofflinestate,youcanupgradethesoftwareonthatdeviceorperform
maintenanceonthatdevice.
WhentheBIGIPsystemisforcedoffline,itterminatesexistingconnectionstolocaltrafficobjects,suchasvirtual
servers,SNATs,andsoon.Intheforcedofflinestate,theBIGIPsystemdoesnotallownewconnections.
ForBIGIPsystemsrunningsoftwareversion11.1.0andlater,theForceOfflinestatuspersiststhroughsystem
rebootsandupgrades.ForBIGIPsystemsrunningsoftwareversionsearlierthan11.1.0,theForceOfflinestatus
doesnotpersistthroughsystemreboots.
TheBIGIPsystemallowsadministrativeconnectionstothemanagementaddresstocontinue,buthandles
administrativeconnectionstoselfIPaddressesdifferently,dependingontheplatform:
Onappliancesystems,thesystemmaintainsconnectionstoselfIPaddresses.
OnVIPRIONsystems,thesystemterminatesconnectionstoselfIPaddresses,anddoesnotallownew
connections.
Note: When you force a chassis system offline, the Traffic Management Microkernel (TMM) interfaces remain
configured until the unit is rebooted. If the chassis is rebooted while Force Offline is enabled, the system marks all
TMM interfaces as Uninitializedor Missing. This behavior is by design. The system will not attempt to
initialize and bring up TMM interfaces while the system is in the offline state.
WhenyouforceVIPRIONplatformsoffline,makesuretomanagethesystembyusingthemanagementportor
console.ThesystemterminatesconnectionstoselfIPaddresseswhenyouforcetheplatformoffline.
Youwillwanttoforcethestandbydevicesofflinebeforeyouchangetheredundancystate(suchasresettingthe
devicetrustforadevicegroup).Forcingstandbydevicesintoofflinestatepreventsastandbydevicefrom
unexpectedlybecomingactive.
Tasksummary
TheupgradeprocessinvolvespreparationoftheBIGIPdevices(DeviceA,DeviceB,andDeviceC)configured
indevicegroup,followedbytheinstallationandverificationofthenewversionsoftwareoneachdevice.When
youupgradeeachdevice,youperformseveraltasks.Completingthesetasksresultsinasuccessfulupgradeto
thenewversionsoftwareonallBIGIPdevices,withthedevicegroupconfiguredproperly.
PreparingBIGIPmodulesforanupgradefromversion11.x
BeforeyouupgradetheBIGIPsystemfromversion11.xtothenewversion,youmightneedtomanuallyprepare
settingsorconfigurationsforspecificmodules.
ApplicationAccelerationManagerpreparation
8/21
2/15/2016
BIGIPApplicationAccelerationManager(AAM)modulesrequirespecificpreparationtasksandchangesto
upgradefromversion11.xtothenewversionsoftware.Noadditionalconfigurationisrequiredaftercompleting
theupgradetothenewversionsoftware.
Preparationactivities
BeforeyouupgradetheBIGIPApplicationAccelerationManager(AAM)modulesfromversion11.xtothenew
versionsoftware,youneedtopreparethesystems,basedonyourconfiguration.Thefollowingtablesummarizes
theapplicabletasksthatyouneedtocomplete.
FEATUREOR
FUNCTIONALITY
PREPARATIONTASK
Unpublishedpolicies Youmustpublishanypoliciesthatyouwanttomigratetothenewversionsoftware.
Onlypublishedpoliciesaremigratedintothenewversionsoftware.
AdvancedFirewallManagersystempreparation
TheBIGIPAdvancedFirewallManager(AFM)systemdoesnotrequirespecificpreparationwhenupgrading
fromversion11.xtothenewversionsoftware.Noadditionalconfigurationisrequiredaftercompletingthe
upgradetothenewversionsoftware.
AccessPolicyManagersystempreparation
TheAccessPolicyManagersystemdoesnotrequirespecificpreparationwhenupgradingfromversion11.xto
thenewversionsoftware.However,additionalconfigurationmightberequiredaftercompletingtheupgradetothe
newversionsoftware.
SupportedhighavailabilityconfigurationforAccessPolicyManager
AccessPolicyManagerissupportedinanactivestandbyconfigurationwithtwoBIGIPsystemsonly.
Important: Access Policy Manager is not supported in an active-active configuration.
Postupgradeactivities
Whenyoufinishupgradingtothenewversionsoftware,youshouldconsiderthefollowingfeatureorfunctionality
changesthatoccurfortheAccessPolicyManagersystems.Dependingonyourconfiguration,youmightneedto
performthesechangesafteryouupgradeyoursystems.
FEATUREOR
FUNCTIONALITY
Sessions
Authentication
agentsandSSO
methods
DESCRIPTION
Alluserscurrentlyloggedinwhiletheupgradeoccurswillneedtologinagain.
IfyouhavedeploymentsusingActiveSyncorOutlookAnywhere,wherethedomain
nameispartoftheusername,youshouldenabletheSplitdomainfrom
usernameoptionintheloginpageagentiftheauthenticationmethodusedinthe
accesspolicyrequiresonlytheusernameforauthentication.
ApplicationSecurityManagersystempreparation
TheBIGIPApplicationSecurityManager(ASM)systemdoesnotrequirespecificpreparationwhenupgrading
Whattoexpectafterupgradingaredundantsystem
IfyouupdatetworedundantsystemsthatarerunningasanactivestandbypairwithBIGIPApplicationSecurity
Manager(ASM)andBIGIPLocalTrafficManager(LTM)provisioned,thesystemmaintainstheactivestandby
statusandautomaticallycreatesaSyncFailoverdevicegroupandatrafficgroupcontainingbothsystems.The
devicegroupisenabledforBIGIPASM(becausebothsystemshaveASMprovisioned).
Youcanmanuallypushorpulltheupdates(includingBIGIPLTMandASMconfigurationsandpolicies)fromone
systemtotheother(DeviceManagement>Overview,clickthenameofadevice,andthenchooseSync
DevicetoGrouporSyncGrouptoDevice).
9/21
2/15/2016
GlobalTrafficManagersystempreparationandconfiguration
BIGIPGlobalTrafficManagersystemsrequirespecificpreparationandconfigurationwhenupgradingfrom
version11.xtothenewversionsoftware.
Preparationactivities
YoushouldcompletetheseactivitiesbeforeupgradingGlobalTrafficManagersystemsfromversion11.xtothe
newversionsoftware(BIGIPDNS).
ACTIVITY
INSTRUCTIONS
Verifythatthedevicecertificatesarecurrent,and
thatexpirationdoesnotoccuruntilafterupgrading. 1.OntheMainmenu,clickSystem>Device
Certificates>DeviceCertificate.
2.VerifytheExpiresdate.
DisableconfigurationsynchronizationandDNS
zonefilessynchronization.
1.OntheMainmenu,clickDNS>Settings>
GSLB>General.
Note: To use a backup UCS file without synchronizing

2.CleartheSynchronizecheckbox.
the GTM configuration, disable synchronization. If
synchronization is enabled, restoring the UCS backup
file loads the configuration and initiates synchronization. 3.CleartheSynchronizeDNSZoneFilescheck
box.
Postupgradeactivities
YoushouldcompletethesetasksafterupgradingBIGIPDNSsystemsfrom11.xtothenewversionsoftware.
Fromthecommandline,runthebig3d_installscriptonthefirstBIGIPDNSsystemthatyouupgraded,so
thatyoucanmonitorotherBIGIPDNSsystems.
Important: Run this script only once, only from the first BIG-IP DNS system that you upgraded. This step
momentary degrades monitoring performance as new big3d agents start.
Oneachdevice,verifytheconfiguration.
Oneachdevice,testqueriesagainstlisteners.
Oneachdevice,verifyiQueryconnectionsbyusingthetmshcommandtmsh show /gtm iquery all.
Enablesynchronizationoneachdevice.
Verifyconfigurationsynchronizationbyusingadummytestobjectforexample,byusinganobjectthatcanbe
deletedaftertheconfigurationsynchronizationisverifiedasoperational.
LinkControllersystempreparation
TheBIGIPLinkController(LC)systemdoesnotrequirespecificpreparationwhenupgradingfromversion11.x
tothenewversionsoftware.Noadditionalconfigurationisrequiredaftercompletingtheupgradetothenew
versionsoftware.
LocalTrafficManagersystempreparation
TheBIGIPLocalTrafficManager(LTM)systemdoesnotrequirespecificpreparationwhenupgradingfrom
version11.xtothenewversionsoftware.Noadditionalconfigurationisrequiredaftercompletingtheupgradeto
thenewversionsoftware.
HTTPClassprofiles
F5NetworksreplacedtheHTTPClassprofileinBIGIPversion11.4.0,andlater,withtheintroductionofthe
LocalTrafficPoliciesfeature.DuringanupgradetoBIGIPversion11.4.0,ifyourconfigurationcontainsanHTTP
Classprofile,theBIGIPsystemattemptstomigratetheHTTPClassprofiletoanequivalentlocaltrafficpolicy.
ForadditionalsupportinformationregardingthechangeofHTTPClassprofilestoLocalTrafficPolicies,referto
SOL14409onwww.askf5.com.
10/21
2/15/2016
PolicyEnforcementManagersystempreparation
TheBIGIPPolicyEnforcementManager(PEM)systemdoesnotrequirespecificpreparationwhenupgrading
PreparingBIGIPdevicegroupsforanupgrade
ThefollowingprerequisitesapplywhenyouupgradeBIGIPdevicegroupsfromversion11.xtothenewversion.
TheBIGIPsystems(DeviceA,DeviceB,andDeviceC)areconfiguredasadevicegroup.
EachBIGIPdeviceisrunningthesameversionof11.xsoftware.
TheBIGIPversion11.xdevicesarethesamemodelofhardware.
WhenyouupgradeaBIGIPdevicegroupfromversion11.xtothenewversion,youbeginbypreparingthe
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.
1.Foreachdevice,completethefollowingstepstopreparetheconfigurationandsettings.
a.ExaminetheReleaseNotesforspecificconfigurationrequirements,andreconfigurethesystems,as
necessary.
b.ExaminetheReleaseNotesforspecificchangestosettingsthatoccurwhenupgradingfromversion11.xto
thenewversion,andcompleteanyinprocesssettings.
2.Fromthedevicethatisrunningthelatestconfiguration,synchronizetheconfigurationtothedevicesinthe
devicegroup.
OPTION
DESCRIPTION
Forversion11.2,and a.OntheMainmenu,clickDeviceManagement>DeviceGroups.Alistof
earlier.
devicegroupsappears.
b.IntheGroupNamecolumn,clickthenameofadevicegroup.
c.Onthemenubar,clickConfigSync.
d.ClickSynchronizeToGroup.
Forversion11.3,and a.OntheMainmenu,clickDeviceManagement>Overview.Amessage
later.
appearsfortheStatusMessage.
b.IntheDevicesareaofthescreen,intheSyncStatuscolumn,clickthe
devicethatshowsasyncstatusofChanges Pending.
c.ClickSynchronizeDevicetoGroup.
3.Foreachdevice,createaQKViewfile,anduploadittoiHealth.
a.OntheMainmenu,clickSystem>Support.TheSupportscreenopens.
b.SelecttheQKViewcheckbox.
c.ClickStart.TheBIGIPsystemcreatesaQKViewfile.
d.ClickDownloadSnapshotFile,andclickSave.TheBIGIPsystemdownloadstheQKViewfile,named
case_number_###_support_file.qkview,intothebrowser'sdownloadfolder.
11/21
2/15/2016
e.RenametheQKViewfiletoincludeacasenumberandanidentifier.Anexampleofarenamedfileis:
c123456_A_support_file.qkview.
f.Gotohttps://ihealth.f5.com,andloginusingyourF5WebSupportcredentials.
g.ClickUpload.
h.ClickBrowse,navigatetotheQKViewfileinthedownloadfolder,andthenclickOpen.
i.ClickUploadQKView(s).
4.Foreachdevice,createabackupfile.
a.Accessthetmshcommandlineutility.
b.Attheprompt,typesave /sys ucs /shared/filename.ucs.
c.Copythebackupfiletoasafelocationonyournetwork.
Note: For additional support information about backing up and restoring BIG-IP system configuration files,
refer to SOL11318 on www.askf5.com.
5.DownloadeitherthelatestBIGIPsystemhotfiximagefile,ifavailable,orthenewversionsoftwareimagefile
fromtheAskF5downloadswebsite(http://support.f5.com/kb/en-us.htm)toapreferredlocation.
Note: Using a tool or utility that computes an md5 checksum, you can verify the integrity of the BIG-IP system
latest hotfix .isofile or new version .isofile in the preferred location.
6.ImporteitherthelatestBIGIPsystemhotfiximagefile,ifavailable,orthenewversionsoftwareimagefileto
eachdevice.
OPTION
DESCRIPTION
ImportthelatestBIGIP a.OntheMainmenu,clickSystem>SoftwareManagement>Hotfix
systemhotfiximagefile
List>Import.
b.ClickBrowse,locateandclicktheimagefile,clickOpen,andclick
Import.
c.WhenthehotfiximagefilecompletesuploadingtotheBIGIPdevice,
clickOK.AlinktotheimagefileappearsintheSoftwareImagelist.
Importthenewversion
softwareimagefile
a.OntheMainmenu,clickSystem>SoftwareManagement>Image
List>Import.
b.ClickBrowse,locateandclicktheimagefile,clickOpen,andclick
Import.
c.WhenthesoftwareimagefilecompletesuploadingtotheBIGIPdevice,
clickOK.AlinktotheimagefileappearsintheSoftwareImagelist.
7.IftheBIGIPsystemisconfiguredtouseanetworkhardwaresecuritymodule(HSM),theHSMclientsoftware
mustbeavailableforreinstallation.
Important: Make sure that the available version of HSM client software supports the new version of BIG-IP
software.
12/21
2/15/2016
TheBIGIPdevicesarepreparedtoinstallthelatesthotfixornewversionsoftware.
UpgradingtheDeviceAsystem
Thefollowingprerequisitesapplyforthistask.
EachdevicemustbepreparedtoupgradeDeviceAwiththenewversionsoftware.
Eitherthelatesthotfiximagefile,ifavailable,orthenewversionsoftwareimagefileisdownloadedand
accessible.
Afteryouprepareeachdeviceforupgradingthesoftware,youforcethedeviceoffline,reactivatethesoftware
license,andinstallthenewversionsoftwareontoDeviceA.
1.ForceDeviceAtoofflinestate.
a.OntheMainmenu,clickDeviceManagement>Devices.
b.ClickthenameofDeviceA.Thedevicepropertiesscreenopens.
c.ClickForceOffline.DeviceAchangestoofflinestate.
Important: Once Device A changes to offline state, ensure that traffic passes normally for all active traffic
groups on the other devices.
Note: When Force Offline is enabled, make sure to manage the system using the management port or
console. Connections to self IP addresses are terminated when Force Offline is enabled.
2.Reactivatethesoftwarelicense.
a.OntheMainmenu,clickSystem>License.
b.ClickReactivate.
c.FortheActivationMethodsetting,selecttheAutomatic(requiresoutboundconnectivity)option.
d.ClickNext.TheBIGIPsoftwarelicenserenewsautomatically.
e.ClickContinue.
3.Installeitherthelatesthotfiximage,ifavailable,orthenewversionsoftware.
OPTION
DESCRIPTION
Installthelatest a.OntheMainmenu,clickSystem>SoftwareManagement>HotfixList.
hotfiximage
b.IntheAvailableImagesarea,selectthecheckboxforthehotfiximage,andclick
Install.TheInstallSoftwareHotfixpopupscreenopens.
c.FromtheVolumesetnamelist,selectthelocationofthenewversionsoftware
volumetoinstallthehotfiximage,andclickInstall.
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.
Installthenew
a.OntheMainmenu,clickSystem>SoftwareManagement>ImageList.
13/21
2/15/2016
versionsoftware
b.IntheAvailableImagesarea,selectthecheckboxforthenewversionsoftware
image,andclickInstall.TheInstallSoftwareImagepopupscreenopens.
c.FromtheVolumesetnamelist,selectalocationtoinstalltheimage,andclick
Install.
4.Rebootthedevicetothelocationoftheinstallednewsoftwareimage.
OPTION
Reboot
from
version
11.3.0,or
earlier
DESCRIPTION
a.OntheMainmenu,clickSystem>SoftwareManagement>BootLocations.
b.IntheBootLocationlist,clickthebootlocationoftheinstallednewsoftwareimage.
Note: Upgrading from version 11.3.0, or earlier, automatically installs the configuration of that
version to the new boot location.
c.ClickActivate.DeviceArebootstothenewsoftwareimagebootlocationinoffline
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.
Reboot
from
version
11.4.0,or
later
c.FromtheInstallConfigurationlist,selectYes.TheSourceVolumelistappears.
d.FromtheSourceVolumelist,selectthelocationoftheconfigurationtoinstallwhen
activatingthebootlocationofthenewsoftwareimage.Forexample,foraninstallation
ofanewsoftwareimageonHD1.3,selectingHD1.2:11.6.0installstheversion11.6.0
configuration.
e.ClickActivate.DeviceArebootstothenewsoftwareimagebootlocationinoffline
state.
5.IftheBIGIPsystemisconfiguredtouseanetworkhardwaresecuritymodule(HSM),reinstallandconfigure
theHSMclientsoftware.
Important: You must reinstall network HSM client software on this device before upgrading another device in
the device group, to ensure that traffic groups using the network HSM function properly.
6.ReleaseDeviceAfromofflinestate.
14/21
2/15/2016
b.ClickthenameofDeviceA.Thedevicepropertiesscreenopens.
c.ClickReleaseOffline.DeviceAchangestostandbystate.
ThenewversionofBIGIPsoftwareisinstalledonDeviceA,withalltrafficgroupsinstandbystate.
UpgradingtheDeviceBsystem
ThefollowingprerequisitesapplyinupgradingDeviceB.
DeviceBmustbepreparedtoupgradethesoftwaretonewversionsoftware.
accessible.
IftheBIGIPsystemisconfiguredtouseanetworkhardwaresecuritymodule(HSM),youmustreinstall
networkHSMclientsoftwareonDeviceAbeforeupgradingDeviceB,toensurethattrafficgroupsusingthe
networkHSMfunctionproperly.
DeviceA(thenewversionBIGIPdevice)isinstandbystate.
AfteryouprepareDeviceBforupgradingthesoftware,youforcethedeviceoffline,reactivatethesoftware
license,andinstallthenewversionsoftware.
1.ForceDeviceBtoofflinestate.
b.ClickthenameofDeviceB.Thedevicepropertiesscreenopens.
c.ClickForceOffline.DeviceBchangestoofflinestate.
Important: Once Device B changes to offline state, ensure that Device A passes traffic normally for all
active traffic groups.
b.ClickReactivate.
e.ClickContinue.
OPTION
DESCRIPTION
hotfiximage
15/21
2/15/2016
Installthenew a.OntheMainmenu,clickSystem>SoftwareManagement>ImageList.
versionsoftware
Install.
4.ReboottheDeviceBtothelocationoftheinstallednewsoftwareimage.
OPTION
Reboot
from
version
11.3.0,or
earlier
DESCRIPTION
c.ClickActivate.DeviceBrebootstothenewsoftwareimagebootlocationinoffline
state.
Reboot
from
version
11.4.0,or
later
ofanewsoftwareimageonHD1.3,selectingHD1.2:11.6.0installsaversion11.6.0
configuration.
e.ClickActivate.DeviceBrebootstothenewsoftwareimagebootlocationinoffline
state.
16/21
2/15/2016
5.IftheBIGIPsystemisconfiguredtouseanetworkHSM,reinstallandconfiguretheHSMclientsoftware.
Important: You must reinstall network HSM client software on this device before upgrading another device in
the device group, to ensure that traffic groups using the network HSM function properly.
6.ReleaseDeviceBfromofflinestate.
b.ClickthenameofDeviceB.Thedevicepropertiesscreenopens.
c.ClickReleaseOffline.DeviceBchangestostandbystate.
ThenewversionofBIGIPsoftwareisinstalledonDeviceBwithconfiguredtrafficgroupsinstandbystate.
UpgradingtheDeviceCsystem
ThefollowingprerequisitesapplyinupgradingDeviceC.
DeviceCmustbepreparedtoupgradethesoftwaretonewversionsoftware.
accessible.
IftheBIGIPsystemisconfiguredtouseanetworkhardwaresecuritymodule(HSM),youmustreinstall
networkHSMclientsoftwareonDeviceBbeforeupgradingDeviceC,toensurethattrafficgroupsusingthe
networkHSMfunctionproperly.
DeviceCisinactivestate.
AfteryouprepareDeviceCforupgradingthesoftware,youforcethedeviceoffline,reactivatethesoftware
license,andinstallthenewversionsoftware.
1.ForceDeviceCtoofflinestate.
b.ClickthenameofDeviceC.Thedevicepropertiesscreenopens.
c.ClickForceOffline.DeviceCchangestoofflinestate.
Important: Once Device C changes to offline state, ensure that the other devices pass traffic normally for
all active traffic groups.
b.ClickReactivate.
17/21
2/15/2016
e.ClickContinue.
OPTION
DESCRIPTION
hotfiximage
Installthenew a.OntheMainmenu,clickSystem>SoftwareManagement>ImageList.
versionsoftware
Install.
4.RebootDeviceCtothelocationoftheinstallednewsoftwareimage.
OPTION
Reboot
from
version
11.3.0,or
earlier
DESCRIPTION
c.ClickActivate.DeviceCrebootstothenewsoftwareimagebootlocationinoffline
state.
Reboot
from
version
11.4.0,or
later
ofanewsoftwareimageonHD1.3,selectingHD1.2:11.6.0installsaversion11.6.0
configuration.
18/21
2/15/2016
e.ClickActivate.DeviceCrebootstothenewsoftwareimagebootlocationinoffline
state.
5.IftheBIGIPsystemisconfiguredtouseanetworkhardwaresecuritymodule(HSM),reinstallandconfigure
theHSMclientsoftware.
Important: You must reinstall network HSM client software on this device, to ensure that traffic groups using
the network HSM function properly.
6.ReleaseDeviceCfromofflinestate.
b.ClickthenameofDeviceC.Thedevicepropertiesscreenopens.
c.ClickReleaseOffline.DeviceCchangestostandbystate.
7.OntheMaintab,clickDeviceManagement>Overview.
8.IntheDevicesareaofthescreen,intheSyncStatuscolumn,selectthedevicethatshowsasyncstatusof
Changes Pending.
9.IntheSyncOptionsareaofthescreen,selectSyncDevicetoGroup.
10.ClickSync.
ThenewversionofBIGIPsoftwareisinstalledonDeviceCwithconfiguredtrafficgroupsinstandbystate.
Changingstatesofthetrafficgroups
Manuallyconfiguringactivestatetrafficgroupsacrossdeviceswithinadevicegroupinvolvesforcinganactive
statetrafficgrouponadevicetostandbystate,andretargetingthatactivestatetrafficgrouptoadifferentdevice.
Completingthesetasksresultsinactivestatetrafficgroupsontheappropriatedevicesinadevicegroup.
Viewingalistoftrafficgroupsforadevice
Youcanviewalistoftrafficgroupsforthedevicegroup.Usingthislist,youcanaddfloatingIPaddressestoa
trafficgroup,forceatrafficgroupintoaStandbystate,andviewinformationsuchasthecurrentandnextactive
devicesforatrafficgroupanditsHAloadfactor.
1.OntheMaintab,clickDeviceManagement>TrafficGroups.
2.IntheNamecolumn,viewthenamesofthetrafficgroupsonthelocaldevice.
Forcingatrafficgrouptoastandbystate
Youperformthistaskwhenyouwanttheselectedtrafficgrouponthelocaldevicetofailovertoanotherdevice
(thatis,switchtoaStandbystate).Userstypicallyperformthistaskwhennoautomatedmethodisconfiguredfor
atrafficgroup,suchasautofailbackoranHAgroup.ByforcingthetrafficgroupintoaStandbystate,thetraffic
groupbecomesactiveonanotherdeviceinthedevicegroup.Fordevicegroupswithmorethantwomembers,
youcanchoosethespecificdevicetowhichthetrafficgroupfailsover.
19/21
2/15/2016
1.Logintothedeviceonwhichthetrafficgroupiscurrentlyactive.
2.OntheMaintab,clickDeviceManagement>TrafficGroups.
3.IntheNamecolumn,locatethenameofthetrafficgroupthatyouwanttorunonthepeerdevice.
4.Selectthecheckboxtotheleftofthetrafficgroupname.Ifthecheckboxisunavailable,thetrafficgroupisnot
activeonthedevicetowhichyouarecurrentlyloggedin.Performthistaskonthedeviceonwhichthetraffic
groupisactive.
5.ClickForcetoStandby.Thisdisplaystargetdeviceoptions.
6.Chooseoneoftheseactions:
Ifthedevicegrouphastwomembersonly,clickForcetoStandby.Thisdisplaysthelistoftrafficgroups
forthedevicegroupandcausesthelocaldevicetoappearintheNextActiveDevicecolumn.
Ifthedevicegrouphasmorethantwomembers,thenfromtheTargetDevicelist,selectavalueandclick
ForcetoStandby.
Theselectedtrafficgroupisnowinastandbystateonthelocaldeviceandactiveonanotherdeviceinthedevice
group.
VerifyingaBIGIPdevicegroupupgrade
WhenyouhavecompletedupgradingtheBIGIPdevicegroupfromversion11.xtothenewversion,youshould
verifythattheupgradedconfigurationisworkingproperly.
1.VerifythePlatformconfigurationforeachdevice.
a.OntheMainmenu,clickSystem>Platform.
b.FortheRootFolderDeviceGroupsetting,verifythatthedevicegroupisidenticaloneachdevice.
c.FromtheRootFolderTrafficGrouplist,verifythatthecorrecttrafficgroup(trafficgroup1)isselected.
2.Verifytheconfigurationforeachdevice.
b.Verifythefollowinginformationforthedeviceandthepeerdevices.
activestandbystatus
devicename
managementIPaddress
hostname
TMOSversion
c.OntheMainmenu,clickDeviceManagement>DeviceTrust>PeerList.
d.VerifythatthepeerdevicesarespecifiedasPeerAuthorityDevices.
Note: Ensure that all information for each peer device appears correctly and completely.
3.Verifythetrafficgroupsforeachdevice.
a.OntheMainmenu,clickDeviceManagement>TrafficGroups.
b.FromtheNamelist,clickatrafficgroup.
20/21
2/15/2016
c.IfyouconfiguredMACMasqueradeaddressesforVLANsonthedevices,verifythatthetrafficgroup1
includesanaddressintheMACMasqueradeAddressfield.
d.Verifythatthefloatingtrafficgroupiscorrect.
e.Verifythatthefailoverobjectsarecorrect.
4.VerifytheCurrentConfigSyncStateforeachdevice.
a.OntheMainmenu,clickDeviceManagement>Overview.
b.IntheDevicesareaofthescreen,intheSyncStatuscolumn,verifythateachdeviceshowsasyncstatus
ofgreen.
Implementationresult
YourupgradeoftheBIGIPdevicegroupfromversion11.xtothenewversionsoftwareisnowcomplete.The
newversionsoftwareconfigurationincludesadevicegroupwiththreedevices(DeviceA,DeviceB,andDevice
C)andthreetrafficgroups(traffic-group-1,traffic-group-2,andtraffic-group-3),withatraffic
grouponeachdeviceinactivestate.
Anupgradeddevicegroup
21/21

AskF5 - Manual Chapter - Upgrading Version 11

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

AskF5 - Manual Chapter - Upgrading Version 11

Uploaded by

Copyright:

Available Formats

2/15/2016

AskF5 | Manual Chapter: Upgrading Version 11.x BIG-IP Software

Manual Chapter: Upgrading Version 11.x BIG-IP

AppliesTo: Hide Versions

BIG-IP Link Controller

AskF5 | Manual Chapter: Upgrading Version 11.x BIG-IP Software

AskF5 | Manual Chapter: Upgrading Version 11.x BIG-IP Software

AskF5 | Manual Chapter: Upgrading Version 11.x BIG-IP Software

AskF5 | Manual Chapter: Upgrading Version 11.x BIG-IP Software

AskF5 | Manual Chapter: Upgrading Version 11.x BIG-IP Software

AskF5 | Manual Chapter: Upgrading Version 11.x BIG-IP Software

AskF5 | Manual Chapter: Upgrading Version 11.x BIG-IP Software

AskF5 | Manual Chapter: Upgrading Version 11.x BIG-IP Software

AskF5 | Manual Chapter: Upgrading Version 11.x BIG-IP Software

Note: To use a backup UCS file without synchronizing

AskF5 | Manual Chapter: Upgrading Version 11.x BIG-IP Software

AskF5 | Manual Chapter: Upgrading Version 11.x BIG-IP Software

AskF5 | Manual Chapter: Upgrading Version 11.x BIG-IP Software

AskF5 | Manual Chapter: Upgrading Version 11.x BIG-IP Software

AskF5 | Manual Chapter: Upgrading Version 11.x BIG-IP Software

AskF5 | Manual Chapter: Upgrading Version 11.x BIG-IP Software

AskF5 | Manual Chapter: Upgrading Version 11.x BIG-IP Software

AskF5 | Manual Chapter: Upgrading Version 11.x BIG-IP Software

AskF5 | Manual Chapter: Upgrading Version 11.x BIG-IP Software

AskF5 | Manual Chapter: Upgrading Version 11.x BIG-IP Software

AskF5 | Manual Chapter: Upgrading Version 11.x BIG-IP Software

You might also like