Purpose	Namespace software and networking software record important log information, called metalog data, to be used by a redundant peer in the event of a failover. The ARX-1500 and ARX-2500 store their metalog data on internal disk partitions. You can use the show metalog usage command to view the usage of these metalog partitions over time. Use this command to clear the metalog-usage statistics for the current ARX.
Mode	priv-exec
Security Role(s)	network-technician, network-engineer, storage-engineer, or crypto-officer
Syntax	clear metalog usage
Default(s)	None
Valid Platforms	ARX-1500 and ARX-2500
Guidelines	The show metalog usage command shows up-to-date usage statistics for all metalog partitions in the ARX. Use this command to clear those usage statistics for the entire system. The CLI prompts for confirmation before clearing any statistics; enter yes to continue. The show metalog usage command is unavailable for a minute after you issue this command.
Sample	stoweA# clear metalog usage Clear metalog statistics? [yes/no] yes Metalog driver usage statistics will not be available for a minute. clears the metalog-usage statistics for the ARX named stoweA.
Related Commands	show metalog usage

Purpose	The Non-Volatile RAM (NVRAM) is battery-backed memory on the ACM. The NVRAM stores all database transactions for the namespace processes; if the processes fail, they can recover by replaying these transactions. These transactions are called metalog data. If the NVRAM gets corrupted somehow, use the clear nvr command to erase it and reboot the chassis.
Mode	priv-exec
Security Role(s)	network-technician, network-engineer, storage-engineer, or crypto-officer
Syntax	clear nvr [reload]   reload (optional) causes the switch to come back online after halting. If you omit this option, the switch halts until you manually restore power.
Default(s)	None
Valid Platforms	ARX-500, ARX-2000, or ARX-4000
Guidelines	The CLI prompts you with a warning before it clears the NVRAM. Enter yes to continue, then enter your username at the next prompt. The switch then halts. If you omitted the reload option, you must turn the power back on to restore the ARX to service.
Important: This causes namespace corruption in a running switch, in addition to a service interruption. Only use this command on the advice of F5 personnel.
	The following events are appropriate for clearing the NVRAM: When the system is first booted. This brings the NVRAM battery online for the first time, so there may some garbled data and pre-startup ECC errors. After a hardware failure where the NVRAM got corrupted with ECC errors. Use the show chassis [nvram] command to check for non-recoverable ECC errors. (Optional) After clearing all namespaces with delete startup-config and rebooting. This eliminates stale namespace data in the NVRAM.
Sample	bstnA# clear nvr reload   WARNING WARNING WARNING WARNING WARNING WARNING WARNING WARNING   This will erase the non-volatile RAM (NVRAM).   The effects are: All pending namespace transactions will be lost. Any data that is in transition may become corrupted. The chassis will reload immediately after clearing the NVRAM. This should only be done on a switch that has been completely unconfigured and removed from the network, or on the advice of technical support.   Are you sure you want to clear non-volatile RAM and reload the system? [yes/no] yes Please enter your userid to confirm clearing the non-volatile RAM: admin   % INFO: Success clearing non-volatile RAM. Rebooting system....     System is resetting. ...
Related Commands	delete startup-config

Purpose	Use the clock set command to set the time and/or date at the ARX.
Mode	priv-exec
Security Role(s)	network-technician, network-engineer, storage-engineer, or crypto-officer
Syntax	clock set HH:MM:SS clock set HH:MM:SS mm/dd/yyyy   HH:MM:SS is the time (for example, 06:00:00). Enter the local time, not the UTC time. mm/dd/yyyy (optional) sets the date (for example, 12/31/2003 for the 31st of December, 2003).
Default(s)	If you omit the date specification, the date is unchanged.
Guidelines	Several processes, including those for RON, redundancy, and policy, have clock-dependant algorithms that can be confused by a major change in time. In general, you should avoid this command and use an NTP server instead (see below). For this reason, the CLI prompts for confirmation before changing the time; enter yes to proceed. This command is unnecessary if you use the ntp server command to synchronize the time to an accurate time source. An NTP server overrides the time you set with this command. For the reason stated above, NTP is strongly recommended. Use the show clock command to view the current time and date setting.
Samples	bstnA# clock set 11:00:00 Changing the time may have an adverse impact on the switch.   Are you sure? [yes/no] yes sets the clock to 11 AM, local time.   bstnA# clock set 23:30:00 Changing the time may have an adverse impact on the switch.   Are you sure? [yes/no] yes sets the clock to 11:30 PM.   bstnA# clock set 23:30:00 10/24/2004 Changing the time may have an adverse impact on the switch.   Are you sure? [yes/no] yes sets the clock to 11:30 PM on October 24, 2004.
Related Commands	ntp server show clock

Purpose	Use the clock timezone command to set the time zone at the ARX.
Mode	cfg
Security Role(s)	network-engineer or crypto-officer
Syntax	clock timezone region city clock timezone time-zone-name clock timezone offset   region (1-64 characters) is the continent or ocean of the closet major city. Use <Tab> to see a list of possible options. city (1-64 characters) is the closet major city. As above, use <Tab> to see a list of possible options. time-zone-name (1-64 characters) is the name of the local time zone, if known (for example, EDT, EST, or CDT). The CLI uses this to look up the region and city. Many time-zone names are ambiguous; for example, CST maps to Central Standard Time, China Standard Time, and Australian Central Standard Time. The CLI chooses a region and city based on the current customer base. You can use show clock to see the chosen region and city. offset (optional; -1400 to 1200) is the offset from Coordinated Universal Time (UTC), in hours and minutes (for example, five hours back is -0500 and 7.5 hours forward is 0730). As with the time-zone-name, the CLI uses this to look up the region and city. Many offsets are ambiguous, too; they essentially choose a longitude, and many longitudes cross through multiple cities with different time-keeping rules. The CLI chooses a region and city based on the current customer base. After you set this number, you can use show clock to see the time zone that corresponds to the offset.
Default(s)	None
Guidelines	A drastic clock change may have an adverse effect on policy or a number of other time-dependent applications. The CLI issues a warning before changing the time; enter yes to continue. Use the show clock command to view the current time, date, and time zone settings.
Samples	bstnA# clock timezone America New_York Changing the time may have an adverse impact on the switch.   Are you sure? [yes/no] yes sets the time zone to that of New York City in the U.S.   bstnA# clock timezone EDT ... sets the time zone to Eastern Daylight Time.   bstnA# clock timezone +0900 ... sets the time zone to 9 hours East of the Prime Meridian.
Related Commands	show clock

Purpose	Use the dual-reboot command to simultaneously reboot both peers in a redundant pair. Use this command only on the advice of F5 Support.
Mode	priv-exec
Security Role(s)	network-engineer, storage-engineer, or crypto-officer
Syntax	dual-reboot
Default(s)	None
Guidelines
Important: This causes a service outage.
	The CLI prompts for confirmation before rebooting both peers. Enter yes to proceed. This command does not work on a standalone switch, where you can use reload to reboot.
Sample	prtlndB# dual-reboot   This command initiates a simultaneous reboot of both chassis in the redundant pair.   Do you wish to proceed? [yes/no] yes   06-16 16:02:36 Rebooting: Dual reboot request was issued ...
Related Commands	reload

Purpose	A hostname is set for the ARX as part of the initial boot process. Use the hostname command to rename the ARX.
Mode	cfg
Security Role(s)	network-engineer or crypto-officer
Syntax	hostname name   name (up to 32 characters) is the hostname that you choose for the ARX. Use only alpha-numeric characters (0-9, a-z, A-Z), hyphens (-), and/or periods (.), as specified in RFC 1035.
Default(s)	None
Guidelines	The hostname appears in the CLI prompt; consequently, this command changes the prompt. All ARXes in your RON should have unique hostnames. The hostname is case-sensitive: BSTNA is a different hostname than bstnA. This is not the fully-qualified domain name (FQDN) for the ARX; use the ip domain-list command to set one or more domains for the switch. To create a login message for administrators, use the login-banner command.
Sample	bstnA(cfg)# hostname usaax11 usaax11(cfg)# changes the name of the current switch to usaax11.
Related Commands	show hostname ip domain-list login-banner

Purpose	After an administrator accesses the CLI or the GUI, a configurable text string appears. You can use the login-banner command to create or edit this text string. The no login-banner command removes the text string.
Mode	cfg
Security Role(s)	network-engineer or crypto-officer
Syntax	login-banner post-auth {message | configs msg-file} no login-banner   message (1-2000 characters) is the string to show after a successful authentication. Quote this string if it contains any spaces. configs msg-file (1-1024 characters) selects a file in the configs directory and uses its text. Use the show configs command for a list of files in the configs directory, and you can use the copy command to download a file to that directory. This file should be no more than 768 bytes.
Default(s)	None
Guidelines	The login banner can contain access rules and/or a broadcast message to all ARX administrators. In a redundant pair of ARX peers, the login banner is unique for each chassis; use this command on both peers if you want a login banner in each.
Samples	bstnA(cfg)# login-banner post-auth Running-config last saved 1/7 by J. User uses an informational message as a login banner.   bstnA(cfg)# login-banner post-auth configs banner.txt uses a file in the configs directory, banner.txt.
Related Commands	hostname

Purpose	The ARX-VE installation requires a datastore where the ARX stores important files, including its metalog data. Namespace software records important information in the metalog, possibly to be used later for a failure recovery. Namespace performance may suffer unless the latency to this metalog datastore is 400 micro-seconds or less. Use the probe metalog latency command to measure the latency between the ARX-VE and its datastore.
Mode	priv-exec
Security Role(s)	crypto-officer or storage-engineer
Syntax	probe metalog latency
Default(s)	None
Valid Platforms	ARX-VE only
Guidelines	Use this command after installing the ARX-VE, to confirm that the latency between the ARX-VE is sufficiently small to ensure good performance. This runs a series of I/O operations and measures the latency from each, then it shows the following values: I/O Count is the number of I/O operations that the CLI ran. Latency (usecs) is the average latency for all of those I/O operations, in micro-seconds. If the latency is consistently greater than 400 micro-seconds, we recommend re-installing the ARX-VE and choosing another datastore. 250 micro-seconds or less is recommended for best performance, if that latency is feasible. The ARX-VE Installation Guide contains instructions for installing the ARX-VE. The show redundancy metalog command shows similar statistics, but it applies to all platforms except the ARX-VE. The ARX-1500 and ARX-2500 store their metalog data on their internal disks. On those platforms, you can use the show metalog usage command to see the usage statistics for the internal metalog driver. On all platforms, the namespace software keeps metalog read/write statistics. You can use the show statistics metalog command to see these metalog-usage statistics from a namespace-software perspective.
Sample	stkbrgA# probe metalog latency   Statistics:   I/O Count Latency (usecs) --------- --------------- 1000 340   measures and displays the latency between the current ARX-VE and its metalog datastore. This latency is acceptable.
Related Commands	show redundancy metalog show metalog usage show statistics metalog

Purpose	Use the reload command to reboot the ARX. The ARX then comes up with the current armed software release. (By default, the armed release is the currently-running release; you can change it to a new release with the boot system command.)
Mode	priv-exec
Security Role(s)	network-technician, network-engineer, storage-engineer, or crypto-officer
Syntax	reload [collect-diags] [reason]   collect-diags (optional) causes a diagnostic-collection process before the reload. This is useful for capturing the state of the ARX in case of a failure that requires further diagnosis. reason (optional, 1-255 characters) is a comment you can enter to appear in syslog. This is useful when reviewing the logs during testing and diagnostics.
Default(s)	None
Guidelines	The following prompt appears for confirmation: Reload the entire chassis? [yes/no/diags] Enter yes to reboot. Enter diags if you want to collect diagnostic information and then reboot. This is equivalent to using the collect-diags option in the command. The collected information is a subset of the information captured by the standard collect state command. After the ARX reloads, use collect diags to gather other relevant information (along with the data collected before reboot) and upload the full diagnostic package to F5 Support. To power off the system and prepare it for a planned power outage, you can use the shutdown command.
Guidelines: Other Applications	This command can be the final step for upgrading software on the switch. Use reload to restart all modules after you use boot system to arm the switch with a new release file. You can use show boot or show version to verify that the switch is armed with the desired release file. If someone deleted the full configuration (with delete startup-config) before running this command, all configuration changes are lost after the ARX reloads. The CLI warns you of this and prompts for confirmation; you can enter no and run restore startup-config to preserve your configuration. To remove all configuration parameters, enter yes.
Samples	bstnA# reload   Reload the entire chassis? [yes/no/diags] yes ... reloads the ARX, perhaps to complete a software upgrade.   bstnA# reload collect-diags   Reload the entire chassis? [yes/no] yes ... collects diagnostic-state information and then reloads the ARX. After the reboot, this next command uploads that state information along with additional diagnostics: bstnA# collect diag-info ftp://jpublic:jpwd@ftp.wwmed.com/diags   Collect diagnostic information? [yes/no] yes ...
Related Commands	collect boot system show boot shutdown restore startup-config

Purpose	The resource profile of an ARX is the allocation of its processes amongst its CPU cores, where each CPU core is dedicated to one process type: system processes, fastpath processes, or volume-group processes. Software Release 6.2.0 introduced an optimized resource profile for the ARX-2500. An ARX-2500 with an earlier software release retains the legacy profile. The new, optimized profile is recommended. Use the no resource-profile legacy command to upgrade the resource profile on the current chassis. On the advice of F5 personnel only, you can use resource-profile legacy to return to the legacy profile.
Mode	cfg
Security Role(s)	crypto-officer or network-engineer
Syntax	no resource-profile legacy resource-profile legacy
Default(s)	resource-profile legacy after an upgrade from a pre-6.2.0 release. no resource-profile legacy for any ARX-2500 shipped with 6.2.0 or a later release.
Valid Platforms	ARX-2500 only
Guidelines	After you use this command, you must reload the ARX-2500 for the change to take effect. If you have a redundant pair of ARX-2500 devices (see redundancy), run this command on both peers and then use the dual-reboot command to reboot both of them at once. The above is also true if you replay a running-config script with the resource-profile legacy setting. (One method of replaying a running-config is to save the file on the ARX-2500 and use the run command.) After replaying the config script, you must reload the ARX-2500 for resource-profile legacy to take effect. The optimized resource profile assigns 3 cores, each running on separate hardware, to fastpath processes. It assigns 3 more to volume-group processing, and the remaining 2 cores to system processes. The legacy resource profile assigns 4 cores to fastpath processes, 2 on one hardware module and 2 on another. The cores share their hardware resources in this configuration. The legacy profile also assigns 2 more to volume-group processes and the final 2 cores to system processes. You can use the show processors command to see the current resource profile on your chassis.
Sample	stoweA(cfg)# no resource-profile legacy stoweA(cfg)# end stoweA# reload   Reload the entire chassis? [yes/no/diags] yes ...   upgrades the current ARX-2500, stoweA, to an optimized resource profile. This resource profile is generally recommended.
Related Commands	reload dual-reboot show processors

Purpose	Use the show baudrate command to show the baud rate for the Console (serial) interface.
Mode	(any)
Security Role(s)	crypto-officer, storage-engineer, network-engineer, network-technician, or operator
Syntax	show baudrate
Guidelines	The serial interface is the port labeled Console on the front panel.
Sample	bstnA# show baudrate The serial port baud rate is 9600.
Related Commands

Purpose	Use the show chassis command to display chassis, disk, slot, module, port, and/or temperature information.
Mode	(any)
Security Role(s)	crypto-officer, storage-engineer, network-engineer, network-technician, or operator
Syntax	show chassis [chassinfo | private-subnet | diskuse | slotinfo | moduleinfo | temperature | metalog | nvr | summary]   chassinfo | ... | nvr is an optional choice to focus on one group of chassis tables. If you omit this, the command shows all groups. chassinfo - specifies chassis-related tables (as opposed to slot- or module-related) with high-level environment, disk, and power supply information. private-subnet - displays the private subnet that the switch uses for inter-process communication in the chassis. Every chassis in the RON (see ron tunnel) must have a unique private subnet. diskuse - displays disk usage and directories on the system drive. slotinfo - focuses on the slots. moduleinfo - shows model information and firmware versions for each module. temperature - specifies a table of sensor temperatures. metalog - is only available on the ARX-1500 and ARX-2500. This option shows the statistics for metalog-driver software on this chassis. The metalog driver records important recovery data for namespace software, and (in a redundant pair) copies the data to the peer ARX. nvr - is only available on the ARX-500, ARX-2000, and ARX-4000. This option shows the NVRAM-battery state and whether or not there are any ECC errors. The ARX-1500 and ARX-2500 store their metalog data on the RAID instead of the NVRAM; use the metalog option (above) to monitor the metalog-protection mechanism for those device types. summary - shows a summary of the chassis state.
Guidelines	The show chassis command displays several tables. You can focus on a smaller group of tables by using one of the optional keywords. Each group of tables is described in its own section, below. These tables only appear if they are relevant to the current chassis type.
Guidelines: chassinfo	The chassinfo section contains the following tables: Identification the hostname and the Universally-Unique ID (UUID) for the chassis. Use hostname to change the hostname. You can only change the UUID through the initial-startup script. Chassis shows the chassis type, a model number, hardware version (where applicable), and the serial number. Chassis Environment contains the base MAC address for all modules (for a chassis with multiple modules, the individual modules MACs appear in moduleinfo), power status, fan status, and chassis temperature: Power can be Online, Online Partial (one power supply is working, the other is absent), or Failed Partial (one is working, the other failed). Fan(setting) shows the fan status and its speed setting. The fan status can be Online, Not Present, Fault (the fan tray failed), or Ctr Fail (the control to the fan-tray failed). The speed setting is in parentheses, and is high, medium, low, or Unk (unknown). The temperature setting(s) next are customized for certain chassis types: System Temp., CPU Temp. and CPU show the ambient chassis temperature, the temperature of the CPU chip, and the current CPU speed. This appears only for the platforms that support both ambient and CPU temperature readings (such as the ARX-2500). The System Temp can be Normal, Too high, or Failed (temperature monitoring failed), followed by both temperatures in Celsius. The CPU speed is relevant because these chassis types automatically reduce the CPU speed if the temperature is too high. This shows the current CPU speed followed by an indication of whether or not the speed has been reduced; (Normal) means that the CPU is running at 100%, a percentage (such as 85%) indicates that the CPU has been throttled back. Temperature appears for other chassis types. This is the same as the System Temp. described above. Power Details appears for the ARX-1500, ARX-2000, ARX-2500, and ARX-4000, which have redundant power supplies. This has one row for each power supply showing the power-supply state (Online, Absent, or Failed). The ARX-1500 and ARX-2500 each have redundant power supplies, A and B. They are accessible from the back of the chassis, on the left side. Each power supply has a plug for its power cable. The ARX-2000 also has redundant power supplies, 1/1 (on top) and 1/2 (under 1/1). They are accessible from the back of the chassis, on the right side. Each power supply has a plug for its power cable. The ARX-4000 has redundant power supplies in both the control plane and the dataplane; these are numbered 1/1 and 1/2 for the control plane (in the top half of the chassis) and 2/1 and 2/2 for the data plane (on the bottom half). All power supplies are accessible from the back of the chassis, on the right side. Each power supply has a plug for its power cable.
Guidelines: private-subnet	This shows the VLAN (where applicable; for example, the ARX-VE uses only VLAN 1 and the ARX-1500 and ARX-2500 have no private VLAN, so this does not appear for those platforms), Subnet, and Subnet Mask for the private subnet on this chassis. You set this when you install the switch. You can reset it with ip private vlan or ip private subnet reassign. This subnet must be unique for all switches in a Resilient Overlay Network (RON); see ron tunnel for more information about a RON.
Guidelines: diskuse	The first three tables only appear for a chassis with replaceable disks (any platform except the ARX-500 or the ARX-VE). The SATA Drive Details table appears for the ARX-500. The Disk Usage table appears for all chassis types. Logical Disk Details shows the status of the RAID as a single, logical disk. Disk is always 1. This represents the single, logical disk comprised of the disks in the table below. Status is Optimal (both disks are working), Degraded (one disk failed or is degraded), Verifying n% (someone issued the raid verify command to verify disk integrity; the percentage shows the progress of the verification test), or Failed. Verification Mode is Manual or Automatic, as set by the raid verification-mode command. Verification Rate is the percentage of CPU that the RAID can use for verifying a disk. You can change this for manual verifications with raid verification-rate. Disk Details shows the location and size of each disk, disk state, the data-transfer rate, and the model number. Disk indicates the location of the physical disk: Bay 1 is on top of Bay 2 in all chassis types with replaceable disks. Size is the full capacity of the disk. State is Online, Degraded, (the disk may fail soon), Rebuild n% (someone used raid rebuild to add the disk to the RAID; the percentage shows the progress of the rebuild), Not Present, Failed, or Unknown. Transfer Rate is the current throughput on the disks bus channel. This is negotiated at startup between the disk controller and the disks themselves. The next table shows the maximum rate allowed by the controller. Model is the specific model number of the disk drive. RAID Controller Details displays the current RAID settings. Rebuild Rate is the percentage of CPU that the RAID can use for rebuilding a disk. You can change this with raid rebuild-rate. Max Transfer Rate is the maximum throughput allowed on the disks bus channel. Firmware is firmware version running on the disk controller. RAID Alarm is Enabled or Disabled. You can disable the alarm with the raid silence command. SATA Drive Details appears for an ARX-500 with a Serial ATA (SATA) disk drive. Firmware is firmware version running on the disk. Model and Serial identify the disk drive. Disk Usage shows the switchs software directories and their total space (in MB), used space (MB), free space (MB), and used percentage (%).
Guidelines: slotinfo	Slot Environment, the only table in the slotinfo group, shows each slots contents and status: Slot is the location of the module in the chassis. This is1 (the control plane on the top half) or 2 (the data plane on the bottom) for the ARX-4000. It is always 1 for the ARX-500 or ARX-2000. Type is ACM (for the control plane on top) or NSM (for the data plane on the bottom) on the ARX-4000. For the ARX-500 or ARX-2000, the single slot contains an ACM. State is the current state of the module. This is one of the module states documented for the show version command; see Guidelines: Module States. Power can be Online, Degraded, or Failed. Temperature is the aggregate of all temperature-sensor readings in the module. This is either Normal or Too High, along with the current temperature range on the module. NVR Battery appears for the NSM on the ARX-4000 or the ACM on the ARX-500 or ARX-2000. This is the battery status for Non-Volatile RAM (NVRAM). The possible values in this field are Good, Missing, Charging, Testing, Degraded, or Failed. The NVRAM stores transaction logs from the ACM, which are critical for failure recovery. The battery provides extra protection for these logs. Contact F5 Support if the status is Missing, Degraded, or Failed; you may need a battery upgrade. Drive appears only for the ACM. This shows the drive type (LSI, IDE, or SATA) and status for the internal disk(s). The possible status values are Good, Degraded, Error, or Unknown. If the status is Degraded or Error, replace the drive (for an ARX-1500, ARX-2000, ARX-2500, or ARX-4000) and/or contact F5 personnel (for an ARX-500). An Unknown status would likely be caused by an error in the drive-detection software. The ARX-VE has no hardware, so this option generates no output when you run it on that platform. This option also generates no output when you run it on the ARX-1500 or the ARX-2500.
Guidelines: Port Media Details Table	Port Media Details only appears in the summary view (without any options) for the platforms that support 10G optics. These are the ARX-2500 and the ARX-4000. Each of these platforms supports up to two transceivers. Each row shows the following details about one of the transceivers: Slot/Port, also identified on the front panel, identify the transceivers port, Type, is the particular transceiver model, Vendor shows the manufacturer of the transceiver, and Status, which is Good, Bad, Present, Not Present, Absent, or Unknown.
Guidelines: moduleinfo	The VM Information table only appears for the ARX-VE, which is a Virtual Appliance (VA, which is similar to a VM): vMAC Address is the virtual MAC address assigned to the ARX-VE. Adapter describes the network controller used by the ARX-VE. Module is the heading for several tables with details of each module. The first table describes the hardware in each module: Slot is the modules slot number. Ports is the number of ports on the module. Procs is the number of processors. Card is the card type: SCM_40, NSM, NSM_TX/FX, ASM/ASM_FC, or ACM. This does not appear on the ARX-VE. Hardware only appears for the ARX-VE. This describes the CPU and memory resources reserved for the ARX-VE. Xeon is the CPU speed for all Xeon processors (used in every module except the NSM) and memory that is allocated to each Xeon processor. This does not appear on the ARX-VE. Sibyte is the CPU speed for all SiByte processors (used on the NSM and standalone ACMs) and the memory allocated to each SiByte complex. Each SiByte complex has two MIPS-processor cores. This does not appear for the ARX-VE, ARX-1500, or ARX-2500; none of these systems contain SiByte processors. Serial is the modules serial number. This does not appear for the ARX-VE, ARX-1500, or ARX-2500; for those systems, refer to the overall chassis serial number in the show chassis chassinfo output. The second table shows the range of MAC addresses assigned to the module and its current hardware revision (the major-revision letter and minor-revision number, along with any Rework or Deviation on the module). For the ARX-1500 and ARX-2500, this shows the BIOS version. This table does not appear for the ARX-VE. The final tables do not appear for the ARX-VE, ARX-1500, or ARX-2500. The third table displays the revisions for the Complex Programmable Logic Devices (CPLDs) on the module, the Reset CPLD, the Keeper CPLD, the Power CPLD (ARX-4000 only), and the MUX CPLD (also ARX-4000 only): The Reset CPLD coordinates hardware resets when the chassis powers up. The Keeper CPLD, in conjunction with an FPGA, ensures that all client-transaction logs are stored safely in NVRAM before the chassis powers down. The Power CPLD (ARX-4000 only) coordinates the distribution of power from multiple power supplies to the chassis components. The MUX CPLD (ARX-4000 only) multiplexes status signals from various internal components and sends a unified signal to the NVR FPGA (described below). This also activates/deactivates various LEDs on the external panels. The BIOS Version appears for the control plane (or ACM) on the ARX-500 and the ARX-4000.
Guidelines: moduleinfo (cont.)	The next table shows versions for bootstrap, diagnostics, and boot-loader firmware. These components manage the modules boot process: the bootstrap software starts the hardware, then the diagnostics run to verify the hardware functions, and finally the boot-loader loads and starts all of the system software. These come bundled with each software release; to install the versions that came with the latest release, use the firmware upgrade command. The final table presents FPGA information, which varies from platform to platform: ARX-4000 and ARX-2000 - the table contains the versions of the LBA FPGA and the NVR FPGA. The LBA (Load-Balancing Algorithm) FPGA merges inbound packets from the external interfaces to the NSM cores. The NVR FPGA manages the NVR, monitors chassis status through the MUX CPLD, and runs a watchdog process that reboots the chassis in the event of a serious failure. ARX-500 - the versions for one FPGA and the boot-related firmware on the NSM processors. The FPGA is a hybrid of the NVR and MTL FPGAs.
Guidelines: temperature	Temperature Details shows temperature-sensor information from each module. For the ARX-1500 and ARX-2500, the table shows the following fields: Slot is always 1. Module is always ACM. System Temp. shows the ambient chassis temperature in Celsius. CPU Temp. shows the temperature of the CPU chip in Celsius. CPU shows the current CPU speed. These chassis types automatically reduce the CPU speed if the temperature is too high. This field shows the current CPU speed followed by an indication of whether or not the speed has been reduced; (Normal) means that the CPU is running at 100%, a percentage (such as 85%) indicates that the CPU has been throttled back. Fan Status shows the fan status and its speed setting. The fan status can be Online, Not Present, Fault (the fan tray failed), or Ctr Fail (the control to the fan-tray failed). The speed setting is in parentheses, and is high, medium, low, or Unk (unknown). For all other hardware platforms, each processor has one temperature sensor positioned near the processor. The sensor takes its own local reading for the ambient temperature of the processor, and it takes a remote reading from the processor itself. The remote reading is the temperature of the processors silica.
Guidelines: metalog	Metalog Usage shows the statistics for metalog usage on this chassis. Status is the status of the metalog driver software, which writes metalog packets to an internal NFS export and duplicates them to a twin driver in the redundant peer (if there is one). The possible options are Standalone (there is no redundant peer), Active (the driver is duplicating all metalog packets to the redundant peer), and Standby (the driver is receiving all metalog packets from the Active peer). Statistics is a table with metalog-usage statistics: I/O Count is the number of metalog packets sent to local storage (and remote storage, if this is the Active chassis in a redundant pair). Retransmit Count only increments on the Active peer in a redundant pair. This is the number of metalog transmissions to the Standby peer that required a retry. Hourly Latency (usecs) is the average latency in micro-seconds between the ARX and its local metalog storage. This number is updated once per hour. On the Active peer, this is the longer of two events that occur in parallel: writing the data to the local partition and writing the same data to the Standby peers partition. You can use show metalog usage to show all of the hourly metalog statistics since the last ARX reboot. The clear metalog usage command clears these statistics and restarts them at 0 (zero). This output only appears on a chassis with an internal metalog driver, but namespace software keeps metalog read/write statistics on all chassis types. On any platform, you can use the show statistics metalog command to see these read/write statistics from a namespace perspective.
Guidelines: NVR	The NVR table shows the following information about the state of the hardware that protects Non-Volatile RAM: NVR Battery is the battery status for Non-Volatile RAM (NVR or NVRAM). The possible values in this field are Good, Missing, Charging, Testing, Degraded, or Failed. The NVRAM stores transaction logs from the control plane, called metalog data, which are critical for failure recovery. The battery provides extra protection for these logs in the event of a power outage. ECC State is the state of the Error-Correction Circuitry (ECC). The ECC checks all data as it is read from NVRAM, and generates errors if it detects any corruption. This can be No Error, Pending, Non-Correctable Error, or Unknown. A Non-Correctable Error state is serious; contact F5 personnel if you see this. NVR Size (MB) is the size of the NVRAM region, in MegaBytes. The ARX-VE has no NVRAM hardware, so this option generates no output when you run it on that platform. The nvr option does not even appear on the ARX-1500 and ARX-2500, which also do not support NVRAM hardware.
Samples	Figure 5.1 on page 5-26, Figure 5.2 on page 5-27, Figure 5.3 on page 5-30, Figure 5.4 on page 5-31, Figure 5.5 on page 5-31, and Figure 5.6 on page 5-33 show sample output for the show chassis command on the ARX-4000, ARX-2500, ARX-1500, ARX-VE, ARX-2000, and ARX-500 respectively.
Related Commands	show processors

Purpose	Use the show clock command to see the current time/date setting on the ARX.
Mode	(any)
Security Role(s)	crypto-officer, storage-engineer, network-engineer, network-technician, or operator
Syntax	show clock
Guidelines	The ARX has a separate clock in each module, synchronized internally through NTP. The clock display is from the ACM, which has the master clock for all processes in the switch. Use the clock set command to reset the clock. Use the clock timezone command to reset the time zone. Use the ntp server command to synchronize the clock with an external NTP server.
Sample
stoweA# show clock Local time: Mon 03 Nov 2008 01:48:45 AM EST -0500 America New_York Universal time: Mon 03 Nov 2008 06:48:45 AM UTC
Related Commands	clock set clock timezone ntp server

Purpose	Use the show hostname command to see the ARXs hostname.
Mode	(any)
Security Role(s)	crypto-officer, storage-engineer, network-engineer, network-technician, or operator
Syntax	show hostname
Guidelines	To set the hostname, use the cfg-mode hostname command.
Sample	bstnA(cfg)# show hostname bstnA bstnA(cfg)#
Related Commands	hostname

Purpose	The show memory usage command shows usage statistics for ARX memory.
Mode	(any)
Security Role(s)	crypto-officer, storage-engineer, network-engineer, network-technician, or operator
Syntax	show memory usage [report]   report (optional) causes the CLI to create a report instead of showing output on the command line. The CLI shows the report name after you type the command. The report is named memory_usage_yyyymmddHHMMSS.rpt, where yyyymmddHHMMSS is the date and time when the report was created. Use show reports to list all reports and view the reports contents.
Platforms	ARX-1500 and ARX-2500
Guidelines	The output contains a table with 3-hour samples of memory usage, where the most-recent sample is at the top. Every row of the table shows the memory usage for one 3-hour sample: Date MM/DD is the month and day of the 3-hour sample. Time Interval is the start time and end time for the 3-hour sample. %Memory shows the low, average (Avg), and high percentages of memory used during the sample period. Use the show processors usage command to show similar statistics for all processors on the switch; for other platform types, such as the ARX-2000, this also includes memory-usage statistics. The show system tasks command shows the currently-running tasks on one or more processors.
Samples	stoweA# show memory usage shows the memory-usage statistics for all processors on an ARX-2500. See Figure 5.7 on page 5-38 for sample output.   canbyA# show memory usage report   Scheduling report: memory_usage_201103220344.rpt canbyA# sends the processor-usage statistics for an ARX-1500 to a report. See Figure 5.8 on page 5-38 for a sample report.
Related Commands	show processors usage show system tasks

Purpose	Namespace software and network software each record important log information, called metalog data, to be shared with the ARX devices redundant peer. This metalog data facilitates a failover from the active ARX to its backup ARX. The ARX-1500 and ARX-2500 each store this data on internal disk partitions, one partition per volume group plus one partition per fastpath processor. The show metalog usage command shows usage statistics for these metalog-storage partitions.
Mode	(any)
Security Role(s)	crypto-officer, storage-engineer, network-engineer, network-technician, or operator
Syntax	show metalog usage [report]   report (optional) causes the CLI to create a report instead of showing output on the command line. The CLI shows the report name after you type the command. The report is named metalog_usage_yyyymmddHHMMSS.rpt, where yyyymmddHHMMSS is the date and time when the report was created. Use show reports to list all reports and view the reports contents.
Valid Platforms	ARX-1500 and ARX-2500
Guidelines	The output contains one table per metalog partition. At the top of each table is the following label: Metalog Usage for Disk Partition id used by {Volume-Group n | Fastpath slot.proc} Where Disk Partition id shows the ID of the internal-disk partition to store this metalog data. Volume-Group n is the volume group that stores its metalog information on partition id. The show volume-group command lists all volume groups on the chassis. Fastpath slot.proc indicates that the fastpath (or network) processor at slot.proc is using this internal partition to store its metalog data. The show processors command lists all processors on the chassis and shows which of them run the Fastpath (network) processes.
Guidelines (Cont.)	Each table shows 1-hour samples of memory usage, where the oldest sample is at the top. Every row of the table shows the metalog-partition usage for a single one-hour sample: Date is the month and day of the sample. Time Interval is the start time and end time for the sample. I/O Count is the number of metalog packets sent to the local partition. If this ARX is in a redundant pair, this is the sum of the packets sent to the local partition and the duplicate packets sent to the partition on the backup peer. You can use the show redundancy command to check the redundancy status of this chassis. Retransmit Count only increments on the active peer in a redundant pair. This is the number of metalog transmissions to the backup peer that required a retry. Latency (usecs) is the minimum, maximum, and average latency in micro-seconds between the ARX and its local metalog partition. These numbers are updated once per hour. On the active peer in a redundant pair, this is the longer of two events that occur in parallel: writing the data to the local partition and writing the same data to the backup peers partition. The ARX keeps these statistics from the most-recent time it has booted. You can use the clear metalog usage command to clear these statistics immediately. The show redundancy metalog command shows similar statistics, but it applies to all platforms (except the ARX-VE). To find similar statistics on the ARX-VE platform, use the probe metalog latency command. On all platforms, the namespace software keeps metalog read/write statistics. You can use the show statistics metalog command to see these metalog-usage statistics from a namespace-software perspective.
Samples	stoweA# show metalog usage shows the metalog-usage statistics for all processors on an ARX-2500. See Figure 5.9 on page 5-41 for sample output.   canbyA# show metalog usage report   Scheduling report: metalog_usage_201104110152.rpt canbyA# sends the metalog-usage statistics for an ARX-1500 to a report. See Figure 5.10 on page 5-41 for a sample report.
Related Commands	clear metalog usage show processors probe metalog latency show statistics metalog show redundancy metalog

Purpose	Use the show processors command to list the processors (CPUs) installed on the ARX.
Mode	(any)
Security Role(s)	crypto-officer, storage-engineer, network-engineer, network-technician, or operator
Syntax	show processors
Guidelines: Output on the ARX-1500, ARX-2500, and ARX-VE	The ARX-1500 and ARX-2500 use a multi-core processor, where each core is primarily dedicated to either network (fastpath) processing, storage (volume-group) processing, or CLI/GUI (system-management) processing. The output for this command shows two tables to describe the current state of these processor cores. The first table shows the role and CPU usage of each core, where each core appears on a separate row. The ARX-1500 uses fewer cores than the ARX-2500, and the ARX-VE has one: Proc is in processor.core format. The processor is always 1, and the core number identifies the particular core. Role is either Fastpath (network processing), Volume-Group (storage-related processing), or System (CLI, GUI, and other management processing). This indicates the type of process that primarily runs on this core. CPU1M is the average CPU usage over the last 60 seconds. This number is a percentage. CPU5M is the average CPU usage over the last 5 minutes. As above, this is a percentage. The second table shows a summary for the entire processor. This table only appears on the ARX-1500 and ARX-2500: Up Time is time since the last reboot. You can use the reload command to manually reboot. For the ARX-VE, you can also reboot from your VM-client console. Memory (MB) is a heading for the following processor-memory measures, in MegaBytes: Total is the processors total memory. Free is the processors available memory. Swap (MB) is a heading for similar swap-space measures, also in MegaBytes. This is space on the internal hard disk that is used as a memory region when free memory is low: Total is the processors total swap space. Free is the processors available swap space.
Guidelines: Output on Other Platforms	For the other platforms (not the ARX-1500, ARX-2500, or ARX-VE), the output is a table with one row per processor. Each row contains the following fields: Proc shows the slot location of the processor in slot.processor format. Processor 1.1 is the management processor for all platforms. Module is the processors module type (ACM only on the ARX-500 or ARX-2000; ACM or NSM on the ARX-4000).
	State is the current processor state: Up Reset - should appear very briefly, just before Boot. Boot - the processor is running its diagnostic tests, invoked during boot. Init - the processor passed its diagnostic tests and is being provisioned. Waiting - the processor is waiting for configuration parameters before it can begin processing. If all NSM and/or ACM processors are in the Waiting state, they require proper configuration for the interfaces. Minimally, each interface must be started with no shutdown (cfg-if-gig), and each NSM processor requires a proxy-IP address (see ip proxy-address). Downloading - if (during Init) the processor discovers that it needs new software, it enters this state to fetch and install the software. Unknown - the CLI cannot ascertain the processors state. Standby - appears for an NSM processor that failed over to a peer processor and then came back online. The peer processor is now handling this processors traffic, and this processor is in a hot-standby state. If the peer processor fails, this processor takes control. The nsm recovery command configures the NSM processors to go into this state if they experience a failure. NSM processors also go into this state after a full-chassis failover (you prepare an ARX for failovers with the redundancy command). Failed FW Upgrade - indicates that the module is upgrading its firmware. You can start a firmware upgrade after installing a software release with new firmware; see the documentation for the firmware upgrade command. FW Upgrade Failed - means that the module failed an attempted firmware upgrade. Call F5 Support if you see this state.
	Up Time is time since the last reboot. Use the reload command to reboot. Memory (MB) is a heading for the following processor-memory measures, in MegaBytes: Total is the processors total memory. Free is the processors available memory. CPU1M is the current CPU usage in a 1-minute period. CPU5M is the current CPU usage in a 5-minute period.
Guidelines: Related Commands	Use the show system tasks command to view the tasks that are currently running on one or more processors. For statistics on CPU and memory usage over time, use the show processors usage command.
Samples	stoweA> show processors shows the processors on an ARX-2500. See Figure 5.11 on page 5-45 for sample output.   stkbrgA# show processors shows the processors on an ARX-VE. See Figure 5.12 on page 5-45 for sample output.   bstnA# show processors shows the processors on an ARX-4000. See Figure 5.13 on page 5-46 for sample output.   prtlndA# show processors shows the processors on an ARX-2000. See Figure 5.14 on page 5-46.
Related Commands	show chassis show system tasks show processors usage nsm recovery resource-profile

Purpose	The show processors usage command shows usage statistics for the processors (CPUs) installed on the ARX.
Mode	(any)
Security Role(s)	crypto-officer, storage-engineer, network-engineer, network-technician, or operator
Syntax	show processors usage show processors usage {slot.processor | all} [report]   slot.processor (optional) specifies one processor. slot is the slot number. processor is the processor number. Use the show processors command to show all processors and their associated slot.processor IDs. all (optional) specifies all processors. report (optional) is only an option if you select one processor or use the all keyword. This causes the CLI to create a report instead of showing output on the command line. The CLI shows the report name after you type the command. The report is named processor_usage_yyyymmddHHMMSS.rpt, where yyyymmddHHMMSS is the date and time when the report was created. Use show reports to list all reports and view the reports contents.
Guidelines	The output contains a table for each chosen processor. Each table shows 3-hour samples of CPU usage, with the most-recent sample at the top. The tables are labeled as follows: Processor Usage for slot.proc appears for each processor on most platforms, and Processor Usage for slot.proc role appears instead on the ARX-1500 and ARX-2500. The role describes the types of processes that used the CPU cycles in the table: FastPath is for network-related processes, similar to those that run on the NSM in other platforms. These are also called data plane processes. Volume-Group is for storage-related processes, such as managed-volume processes and the policy engine. System is for the CLI and GUI (or manager) processes, and other processes related to system administration.
Guidelines (Cont.)	Every row of the table shows the CPU usage for one 3-hour sample: Date is the month and day of the 3-hour sample. Time Interval is the start time and end time for the 3-hour sample. %CPU shows the low, average (Avg), and high percentages of CPU cycles used during the sample period. %Memory shows the same measures for memory. This does not appear in the output for the ARX-1500 or ARX-2500; you can use show memory usage to get these measures on either of those platforms. %Swap shows the percentages for swap-space usage. An ACM only uses swap space when a large portion of standard memory is used up. On the ARX-1500 and ARX-2500, this command omits the %Swap table. Use the show processors command to show the current state of all processors on the switch. The show system tasks command shows the currently-running tasks on one or more processors.
Samples	bstnA# show processors usage shows the processor-usage statistics for all processors on an ARX-4000. See Figure 5.15 on page 5-48 for sample output.   canbyA# show processors usage shows the processor-usage statistics for all processors on an ARX-1500. See Figure 5.16 on page 5-50 for sample output.   bstnA# show processors usage 1.1 report   Scheduling report: processor_usage_201104010144.rpt sends the processor-usage statistics to a report. See Figure 5.17 on page 5-51 for a sample report.
Related Commands	show processors show system tasks show memory usage

Purpose	Use the show uptime command to see how long the system has been up since the last reboot.
Mode	(any)
Security Role(s)	crypto-officer, storage-engineer, network-engineer, network-technician, or operator
Syntax	show uptime
Guidelines	This command displays the length of time since the last reboot in weeks, days, hours, and minutes, as shown in the sample below.
Sample	bstnA> show uptime bstnA uptime is 0 weeks, 0 days, 0 hours, 27 minutes.
Related Commands	show processors show version

Purpose	Use the show version command to display the installed-software versions and a summary of the chassis configuration and state.
Mode	(any)
Security Role(s)	crypto-officer, storage-engineer, network-engineer, network-technician, or operator
Syntax	show version
Guidelines: Release Table	Running Release is the software version that is currently running. This appears in the following format: release-file : Version version-num (build-date) username where release-file is in the local releases directory, which you can see with the show releases command. Armed Release is the software to be loaded on the next reboot, if any. This appears in the same format as the Running Release. Use boot system to arm the switch with a new release file. Use reload to reboot and put the new release file into service. Backup Release is the software release that was running prior to the current release, if any. F5 personnel can roll the switch back to this release if needed.
Guidelines: System Configuration Table	System Configuration is a table of module information for the hardware platforms, one row per module. Slot is only 1 for all chassis except the ARX-4000, which has a second slot devoted to data-plane processes. Admin is enabled. ModuleType is ACM (which runs management processes, control-plane processes, and possibly data-plane processes) or NSM (which exclusively runs data-plane processes). ModuleState values appear in Guidelines: Module States, below. FW Upgrade is enabled or disabled. If enabled, a chassis-software upgrade automatically upgrades the modules firmware. To enable this feature, contact F5 personnel. To install firmware manually, after a software upgrade, use the firmware upgrade command. For the ARX-VE, ARX-1500, and ARX-2500, the System Configuration table contains a single row showing how long it has been since the last reboot.
Guidelines: Resource Table	The Resource table only appears for the ARX-500, ARX-2000, or ARX-4000 platforms. This table shows the high-level state of the switch, and whether it supports packet forwarding (like a MAC bridge) or not (like an end station). State is Up or an error message. If there is an error, use show chassis for details. Forwarding is Enabled (meaning the ARX can forward packets from one client/server port to another, performing the functions of a MAC bridge) or Disabled. You can set this with the switch-forwarding enable command.
Guidelines: Module States	The ModuleState field can contain any of the following values: Online Empty Removed - the slot previously had a module, but it has been removed.
	Discovery - the chassis is finding all module states, very early in the boot process. Boot - the module is running its diagnostic tests, invoked during boot. Init - the module passed its diagnostic tests and is provisioning its internal processors. Downloading - if (during Init) the module discovers that it needs new software, it enters this state to fetch and install the software. Online Partial - at least one processor is up, but not all of them are online yet. If a processor does not come up after 5 minutes, this changes to Failed Partial state. Failed Partial - at least one processor is up, but at least one processor failed. Failed Offline - applies to the network processors. This indicates that the ACM has not provided the network processors with important configuration parameters, so the processors cannot come online. Any of the following issues can result in this state on an ARX-500, ARX-2000, or ARX-4000: The NVRAM battery failed on the ACM. Use show chassis nvr to confirm this; if the issue persists, contact F5 Support. The NVRAM is not up yet. As above, you should contact F5 Support if the NVRAM issue persists.
	Poweroff - the slot has no power. FW Upgrade - the module is installing new firmware from the installed software release. The firmware upgrade command starts a firmware installation. FW Upgrade Failed - a firmware upgrade failed on this module.
Related Commands	boot system show releases reload

Purpose	Use the shutdown command to halt the ARX, perhaps from a remote location. This gracefully stops all power on the system.
Mode	priv-exec
Security Role(s)	crypto-officer, storage-engineer, network-engineer, or network-technician
Syntax	shutdown
Default(s)	None.
Platforms	ARX-500, ARX-2000, ARX-4000, or ARX-VE
Guidelines	This command prepares the ARX for a planned power outage. After you run this command on one of the hardware platforms, you have up to 72 hours before the battery drains for the Non-Volatile RAM (NVRAM). The NVRAM is memory on the ACM that stores all database transactions for the namespace processes; if the processes fail, they can recover by replaying these transactions. This is called metalog data. A managed volume requires its metalog data when it starts up. You must manually power on the chassis to restore it to service. If you restore power after the NVRAM battery drains, all of the managed volumes on the ARX must re-import. The CLI warns you that you must manually restore power to the chassis; enter yes to proceed with the power-off sequence. You can restore power on site by flipping the power switch or pushing the power button. Refer to the Hardware Installation Guide for your chassis to find the location of the power button or switch. The ARX-VE is a software-only platform that runs as a Virtual Appliance (VA, similar to a VM); use your VM client to restart the ARX-VE. The ARX-VE has no NVRAM hardware, and stores its metalog data in one of the hypervisors disk partitions. A re-import of managed volumes is therefore unnecessary for the ARX-VE, no matter how long it is shut down. (The same is true of the ARX-1500 and ARX-2500, which store their metalog data on their internal disk drives.) You can use the reload command to reboot the ARX. To clear the NVRAM (in case of an unrecoverable corruption), use clear nvr.
Sample	provB# shutdown   This command turns off the chassis and powers it down. You will need to manually restore power to return the chassis to service. Are you sure? [yes/no] yes shuts down an ARX named provB.
Related Commands	reload clear nvr