01: Supplement to the CLI Guide
The maximum value/length of one line including Command Line and optional parameters that can be input is 1022 characters
02: Check for Memory Leaks
When a memory leak occurs, the SLB function will be affected if the memory usage rate reaches 83% in APV. While for AG, to check at what percentage of memory usage does it become unstable, please check "current" in show tech for memory usage:
<<<< Network Memory Statistics >>>>
*** 26888/87667/114555/860385 mbufs in use (current/cache/total/max)
If it exceeds 85% of the max, it will become unstable, so please reboot the device after reaching about 80%.
03: System Tune tcpidle Command
By changing system tune tcpidle, it will affect the TCP communication for all functions of AG. However, there is no effect on UDP communication. How to check the effect of system tune tcpidle on TCP communication using real values.
To see all TCP session statistics; You need to check the number of USED for "TCP pcb" LIMIT displayed by the show memory command. Please adjust the system tune tcpidle value so that this value does not reach MAX.
#show memory
ITEM SIZE LIMIT USED FREE REQUESTS
TCP pcb: 520, 955299, 2, 208, 373097
LIMIT, USED, FREE, and REQUESTS are all counts. The unit of SIZE is byte.
04: Effects of turning off the monitor function
AG regularly acquires the memory status inside the chassis, but if you set the monitor off, the log collection will be stopped. You will no longer be able to track usage trends. Although you will no longer be able to track memory changes, you will be able to check the memory status at the time of snapshot acquisition, CLI operation logs, HA logs, and login session statistics from the snapshot, so please consider that you will not be able to check memory and process change information.
05: For failure analysis / Obtaining Debug Monitor file
After an unexpected hang-up occurs, it may be necessary to obtain the Debug Monitor file in order to obtain logs to identify the cause the next time the same problem occurs. In such a case, please perform the following operations to obtain and send the Debug Monitor file.
01: debug monitor on
02: Wait for issue to re-occur
03: Once issue re-occurred (After the problem occurs, restart the AG, it is OK to restart the AG)
04: debug monitor off
05: debug monitor export ftp <user name> <IP address>
06: ARP retention time
ARP retention time is 20 minutes.
07: Points to note when updating the OS when the AG-OS version difference is large
After updating from AG 9.4.0.470 to 9.4.0.484, we have confirmed cases where the disabled AAA OAuth registration command is enabled by default.
08: Migration of settings from unbranded AG series to AGv5 series
All AG v5 series (including AG100v5) require AG 9.4.0.233 or higher. There is no issue in restoring backup files obtained from non-v5 AG devices to the AG v5 series.
09: AG MIB Tips
Only the extended MIB provided by Array Networks is supported, and the standard MIB is not supported.
10: AG-OS file name format
Please refer to the following when changing the file name. If the file formats below do not match, the update may fail to start when updating AG-OS. The format of the AG-OS file name is as follows:
ArrayOS-<Release type>_AG_X_X_X_XXX_XX.array # XX should be version number.
<Release type> should be one of the following strings:
Rel|Beta|Alpha