Appendix B. F5 Licensing For Arx Use Case - F5 ARX 2000 Replacement Script

supARX4000# config
% WARNING: CHASSIS_NOT_READY_REASON (38010969):
The switch is not ready for the operation: Insufficient ACM NVR Battery.
supARX4000> en
supARX4000# term debug
supARX4000# ignore battery
The NVRAM battery charge is not sufficient to preserve data for 72 hours.
Are you sure? [yes/no] yes ("yes", not just "y")

Appendix B. F5 Licensing for ARX Use Case

Purpose:
Starting with the ARX Virtual Edition (ARX VE) version 5.3.0, the ARX adopts and integrates the
licensing used by other F5 products. In the 6.0.0 release, this licensing is extended to the ARX
hardware platforms. Each ARX device is assigned a unique base registration key (BRK). This BRK
is used to create a license dossier that is delivered to the F5 license server. The license server
returns a license that can only be applied to that device. This license sets the feature limits of the
box. The limits that are enforced by licensing are designed to be greater than or equal to any limits
that were hard coded in the ARX software prior to licensing. This should prevent licensing from
breaking any existing configuration that was allowed by earlier releases of the software. Once a
license is applied to a box, you should not need to apply it to that box again. This use case is
designed to walk through the scenarios where customers need to apply a license in order to use
license aware ARX releases. The scenarios that are covered are as follows:
Upgrade to license aware software from non-license aware software
New ARX hardware with a pre-programmed base registration key.
Running through initial interview wizard on license aware code without a pre-programmed base
registration key. [ARX VE and RMA Scenarios]
- 11 –
Copyright © 2010, F5 Networks, Inc. All rights reserved.