byrsapty
b0e4095cae
8 new rules (vendor=a10) wired into Network Equipment Parsing: LSN TCP/Session/ICMP per-user quota exceeded (critical - real service impact, drops new connections for that subscriber), BGP-4-MAXPFX prefix-limit warning, and admin session open/close/timeout/auth-success (aXAPI and CLI both covered by one pattern each). Unlike the CSV-report-derived rules, these are built directly from real captured A10 log output the user provided, so confidence is higher - closer to the accel-ppp rules' provenance. Multi-entry LSN lines (several 'ip(count)' pairs in one quota-exceeded message) only have their first pair extracted into fields; the full list stays in the raw message. Not live-verified - the user is bringing the target system up themselves this time rather than through the test container used earlier in this branch of work.
5 lines
960 B
JSON
5 lines
960 B
JSON
{
|
|
"title": "a10_lsn_tcp_quota_exceeded",
|
|
"description": "A10 ACOS LSN (Large Scale NAT/CGNAT): a subscriber hit their per-user TCP session quota - real service impact (new TCP connections for that user get dropped until it frees up). Built from real captured A10 syslog output. Note: a line can list multiple 'ip(count)' pairs (one per affected user in that batch) - this rule captures only the first for triage; the full list stays in the raw message.",
|
|
"source": "rule \"a10_lsn_tcp_quota_exceeded\"\nwhen\n contains(to_string($message.message), \"LSN: TCP user-quota exceeded\")\nthen\n set_field(\"vendor\", \"a10\");\n set_field(\"event_type\", \"lsn_tcp_quota_exceeded\");\n set_field(\"severity_tag\", \"critical\");\n let m = regex(\"User\\\\(Count\\\\) (\\\\S+)\\\\((\\\\d+)\\\\)\", to_string($message.message), [\"ip\",\"count\"]);\n set_field(\"lsn_user_ip\", m[\"ip\"]);\n set_field(\"lsn_user_count\", to_long(m[\"count\"]));\nend"
|
|
}
|