PA4000HighAvailabilityTestPlan

ThisplancoverstestingoftheHighAvailabilityfunctionofthePA4000.Itisapplicabletoall modesofoperationLayer1(virtualwire),Layer2andLayer3andcoversthefollowing: HAEstablishment HAFailover HASynchronization Preemption SoftwareUpgrade.

HAEstablishment ThissectiontestsestablishmentofHAActive/Passivestatus.
Test Description First active device in group Procedure Config only one PAN to be in HA mode Config the second PAN in HA mode Pass Criteria Should attempt to form adjacency but data and sessions keep going. HA exchanges happen and active/passive states established. Active should stay Active

Second device in group

Second device in group with lower priority value and pre-emption off

Config only one PAN to be in HA mode. Config the second PAN in HA mode. Second device should have better priority but preemption off. Config only one PAN to be in HA mode. Config the second one in HA mode. Check using show command and WebUI.

Second device in group with lower priority value and pre-emption on Check peer states. Active and Passive

Second device should become active. Reflect appropriate state. Display it correctly. Passive device should have all links down.

HAFailover Thissectiontestsfailoverforthevariousconditions.Performfollowingtestswithtraffic flowingthroughactive.Forallteststhatcauseafailover,verifythattrafficresumesthrough thenewlyactivedevice.

Test Description Power down Active and check Standby Procedure Shutdown Active HA device after states are established; check using show command on Standby Shutdown Standby HA device after states are established; check using show command on Active After HA states are established disconnect Active's control and data links; check Standby's states and information While sessions are being created unplug control link to cause failover While sessions are being created unplug data link to cause failover Pass Criteria Standby takes over and state is reflected correctly.

Power down Standby and check Standby

Standby resumes state.

Disconnect Active from Passive (HA control/data)

Failover should happen.

Unplug HA control link on Active

Failover should happen.

Unplug HA data link on Active

Failover should happen.

Restart Active

When all states are established and sessions table gets populated, restart active device When all states are established and sessions table gets populated, restart standby device Config link failure monitoring, cause link failure and check for failover Config path monitoring. Make the remote device unreachable Save config and reboot. On the active device issue "request restart data plane" On the standby device issue "request restart data plane" Reboot switch/router connected to HA devices

Standby takes over and state is reflected correctly. Standby resumes state.

Restart Standby

Config link/interface sync and shutdown interface on active Config path monitoring and make IP unreachable Reboot both peers and check states Issue request restart data plane on Active peer Issue request restart data plane on Standby peer Create link failure using connected Switch/Router

Failover should happen when links are down Failover should happen when ICMP failures s happen Should not run into any race condition. This is a failover scenario. Expect standby to takeover. Standby resumes state. PAN devices should detect network failures and perform HA operation

Create path failure with Router/Switch Suspended state on Active Suspended state on Standby

Create an access list on router switch and deny icmp packets Put Active in suspended state. Put Standby in suspended state.

Failover should cause standby to takeover Failover should cause standby to takeover Make sure in suspended state it does not get affected by any HA events

HASynchronization Thissectiontestscontrol(configuration)anddata(session)planesynchronization.
Test Description Per device config Procedure Config device specific parameters, for e.g. IP, syslog server, time zone Make sure time values are in sync. Change time, manually and check if they get synced Make sure mgmt. objects get synced Pass Criteria This should not be synced to standby Should get synced to Standby and commit should reflect it in config Should get synced to Standby and commit should reflect it in config Should get synced to Standby and commit should reflect it in config Should get synced to Standby and commit should reflect it in config Should get synced to Standby and commit should reflect it in config Should get synced to Active and commit should reflect it in config Configs should match. Commit should transfer config

Sync time and date

Sync admin and management options Sync security profile

Create a security profile on Active PAN In PAN HA env create some objects on Active PAN In PAN HA env create some interfaces on Active PAN

Sync objects (services, addresses, schedules, etc) Sync interfaces

Configuration sync from Standby

Perform above tests on Standby

Download and load a config that was saved

Setup PAN devices in HA mode. Download a saved config to Active. Do a load config and commit. Check standby config and do a commit PAN devices in HA mode. Start sessions.

Session state

Check session info on Standby. Should be same as Active

Preemption Thissectiontestspreemptionwherethehigherprioritydevicewillalwaysbecomeactiveif capable.

Test Description Config preemption and check functionality

Procedure Config preemption on both devices. After Active/Standby states are established, restart active peer.

Pass Criteria Check preemption behavior and the device with better priority should preempt active state after it comes back up

SoftwareUpgrade ThissectionteststhesoftwareupgradeprocedureforanHApair.
Test Description Upgrade PANOS - load new image on B. No preemption and upgrade A Upgrade content Procedure Follow upgrade procedure first on B and then A. Upgrade both devices Pass Criteria Upgrade should ensure no disruption with only one failover Upgrade should ensure no disruption