Activating the NG-WAF generates the Log

Product Discussions ADC - Application Delivery
1

I am enabling NG_WAF on my V-port, adding the command generates the following LOG:

A10(config-slb vserver-vport)ng-waf
Warning: Can’t find ng-waf log. Some errors may not be detected.

It is understood that once this command is executed and traffic is generated to the Virtual Server, this should be reported in the NG-WAF console, but it does not have the expected result, given this log.

I would appreciate any comments.

2

What version of ACOS are you running? Can you check the NGWAF status with:

show ng-waf status

You can also check the NGWAF stats from the CLI with:

show ng-waf virtual_server_name vPort#

Can you also check the system log for WAF events / errors with:

sh log | i WAF

3

Hi Mdunn
Thank you for answering my question, according to the previous review, I note that the NGWAF is configured correctly.

I share with you the Logs, but however in my fastly platform the agent is not reported, nor do I see any data.

A10Serenity#sh ng-waf status
Agent Version: 4.62.0

NGWAF status:
Current status: RUNNING
Agent name: A10Serenity-shared
Access key ID: 06b58xxxxxxxxxxxxxx
Secret access key: i5cmkxxxxxxxxxxxxxx
Cache entries: 0
Tracked custom signals: 0

A10Serenity#show ng-waf VS_NGWAF 80
Requests
Received 18
Forwarded 18

En los logs no se genera ningu error, por lo contrario sale licencia valida, y reinicio exitoso

image.png
image.png1722×559 30.8 KB

4

Hello Harold,

I think you need to enter the site to be able to check the agent installed.

5

Hi matanza

What verifications should I perform?

6

Within the Dashboard:

image.png
image.png207×181 10.5 KB

You can see your sites. You need to enter the one you used to enter the agent keys into the ADC.

#license-manager ng-waf-module access-key-id
secret-access-key

7

Hi Matance

I have verified these keys and even made an update in my platform and it still does not appear. currently I only have one site.

My A10

image.png
image.png614×160 4.42 KB

my keys in fastly

image.png
image.png681×219 10.4 KB

8

Do you have any internet filtering in place? Please confirm that the these domains are reachable via port 443 outbound. This can be either the data plane or management plane depending on your configuration:

dl.signalsciences.netc.signalsciences.netwafconf.signalsciences.netsigsci-agent-wafconf.s3.amazonaws.comsigsci-agent-wafconf-us-west-2.s3.amazonaws.com

Can you also check the system log for WAF events / errors with:

sh log | i WAF