Filter
Top Products
AT-TQ2403 Management Software User's Guide 211
static-c
hannel 36
channel 36
Property Value
---------------------------------------------------------------------------------
tx-power 100
tx-rx-status up
beacon-interval 100
rts-threshold 2347
fragmentation-threshold 2346
super-ag no
atheros-xr no
load-balance-disassociation-utilization 0
load-balance-disassociation-stations 0
load-balance-no-association-utilization 0
ap-detection off
station-isolation off
frequency 5180
wme off
rate-limit-enable off
rate-limit 50
rate-limit-burst 75
Get Status on Events
AT-TQ2403# get log-entry
number priority time daemon message
------------------------------------------------------------------------------------------------------
1 info Jan 1 00:04:51 login[289] root login on `ttyS0'
2 notice Jan 1 00:02:07 syslog Device boot up
3 info Jan 1 00:02:06 dropbear[277] Not forking
Get Status on Persistence
If Persistence is enabled, all logs become persistent and are written to NVRAM and after a reboot, all
logs are recoverable from your system. Non-persistent logs are only kept during the run-time period.
Therefore, if Persistence is disabled and you reboot the access point, all non-persistent logs will be lost.
To determine the status of Persistence, use the following CLI command:
AT-TQ2403# get log persistence
no
Enable or Disable Persistence
In the above example Persistence is disabled. Suppose you want to enable Persistence to ensure that logs
are written to NVRAM. Use the following command to enable Persistence:
AT-TQ2403# set log persistence on
Alternatively, if you wanted to disable Persistence, use the following CLI command:
AT-TQ2403# set log persistence off
Specify the Severity of Messages to be Displayed in the Event Log
The purpose of severity configuration is to filter or limit the security messages that are displayed in the
Event log. It is unlikely that you will want to see a list of all messages. Those of less severity or significance
can be filtered using the Severity Configuration feature.