-
Getting Started with NetScaler
-
Deploy a NetScaler VPX instance
-
Optimize NetScaler VPX performance on VMware ESX, Linux KVM, and Citrix Hypervisors
-
Apply NetScaler VPX configurations at the first boot of the NetScaler appliance in cloud
-
Configure simultaneous multithreading for NetScaler VPX on public clouds
-
Install a NetScaler VPX instance on Microsoft Hyper-V servers
-
Install a NetScaler VPX instance on Linux-KVM platform
-
Prerequisites for installing NetScaler VPX virtual appliances on Linux-KVM platform
-
Provisioning the NetScaler virtual appliance by using OpenStack
-
Provisioning the NetScaler virtual appliance by using the Virtual Machine Manager
-
Configuring NetScaler virtual appliances to use SR-IOV network interface
-
Configure a NetScaler VPX on KVM hypervisor to use Intel QAT for SSL acceleration in SR-IOV mode
-
Configuring NetScaler virtual appliances to use PCI Passthrough network interface
-
Provisioning the NetScaler virtual appliance by using the virsh Program
-
Provisioning the NetScaler virtual appliance with SR-IOV on OpenStack
-
Configuring a NetScaler VPX instance on KVM to use OVS DPDK-Based host interfaces
-
-
Deploy a NetScaler VPX instance on AWS
-
Deploy a VPX high-availability pair with elastic IP addresses across different AWS zones
-
Deploy a VPX high-availability pair with private IP addresses across different AWS zones
-
Protect AWS API Gateway using the NetScaler Web Application Firewall
-
Configure a NetScaler VPX instance to use SR-IOV network interface
-
Configure a NetScaler VPX instance to use Enhanced Networking with AWS ENA
-
Deploy a NetScaler VPX instance on Microsoft Azure
-
Network architecture for NetScaler VPX instances on Microsoft Azure
-
Configure multiple IP addresses for a NetScaler VPX standalone instance
-
Configure a high-availability setup with multiple IP addresses and NICs
-
Configure a high-availability setup with multiple IP addresses and NICs by using PowerShell commands
-
Deploy a NetScaler high-availability pair on Azure with ALB in the floating IP-disabled mode
-
Configure a NetScaler VPX instance to use Azure accelerated networking
-
Configure HA-INC nodes by using the NetScaler high availability template with Azure ILB
-
Configure a high-availability setup with Azure external and internal load balancers simultaneously
-
Configure a NetScaler VPX standalone instance on Azure VMware solution
-
Configure a NetScaler VPX high availability setup on Azure VMware solution
-
Configure address pools (IIP) for a NetScaler Gateway appliance
-
Deploy a NetScaler VPX instance on Google Cloud Platform
-
Deploy a VPX high-availability pair on Google Cloud Platform
-
Deploy a VPX high-availability pair with external static IP address on Google Cloud Platform
-
Deploy a single NIC VPX high-availability pair with private IP address on Google Cloud Platform
-
Deploy a VPX high-availability pair with private IP addresses on Google Cloud Platform
-
Install a NetScaler VPX instance on Google Cloud VMware Engine
-
-
Solutions for Telecom Service Providers
-
Load Balance Control-Plane Traffic that is based on Diameter, SIP, and SMPP Protocols
-
Provide Subscriber Load Distribution Using GSLB Across Core-Networks of a Telecom Service Provider
-
Authentication, authorization, and auditing application traffic
-
Basic components of authentication, authorization, and auditing configuration
-
Web Application Firewall protection for VPN virtual servers and authentication virtual servers
-
On-premises NetScaler Gateway as an identity provider to Citrix Cloud
-
Authentication, authorization, and auditing configuration for commonly used protocols
-
Troubleshoot authentication and authorization related issues
-
-
-
-
-
-
Configure DNS resource records
-
Configure NetScaler as a non-validating security aware stub-resolver
-
Jumbo frames support for DNS to handle responses of large sizes
-
Caching of EDNS0 client subnet data when the NetScaler appliance is in proxy mode
-
Use case - configure the automatic DNSSEC key management feature
-
Use Case - configure the automatic DNSSEC key management on GSLB deployment
-
-
-
Persistence and persistent connections
-
Advanced load balancing settings
-
Gradually stepping up the load on a new service with virtual server–level slow start
-
Protect applications on protected servers against traffic surges
-
Retrieve location details from user IP address using geolocation database
-
Use source IP address of the client when connecting to the server
-
Use client source IP address for backend communication in a v4-v6 load balancing configuration
-
Set a limit on number of requests per connection to the server
-
Configure automatic state transition based on percentage health of bound services
-
-
Use case 2: Configure rule based persistence based on a name-value pair in a TCP byte stream
-
Use case 3: Configure load balancing in direct server return mode
-
Use case 6: Configure load balancing in DSR mode for IPv6 networks by using the TOS field
-
Use case 7: Configure load balancing in DSR mode by using IP Over IP
-
Use case 10: Load balancing of intrusion detection system servers
-
Use case 11: Isolating network traffic using listen policies
-
Use case 12: Configure Citrix Virtual Desktops for load balancing
-
Use case 13: Configure Citrix Virtual Apps and Desktops for load balancing
-
Use case 14: ShareFile wizard for load balancing Citrix ShareFile
-
Use case 15: Configure layer 4 load balancing on the NetScaler appliance
-
-
-
Export management logs directly from NetScaler to Splunk
-
Export audit logs and events directly from NetScaler to Splunk
-
-
-
-
Authentication and authorization for System Users
-
-
-
Configuring a CloudBridge Connector Tunnel between two Datacenters
-
Configuring CloudBridge Connector between Datacenter and AWS Cloud
-
Configuring a CloudBridge Connector Tunnel Between a Datacenter and Azure Cloud
-
Configuring CloudBridge Connector Tunnel between Datacenter and SoftLayer Enterprise Cloud
-
Configuring a CloudBridge Connector Tunnel Between a NetScaler Appliance and Cisco IOS Device
-
CloudBridge Connector Tunnel Diagnostics and Troubleshooting
This content has been machine translated dynamically.
Dieser Inhalt ist eine maschinelle Übersetzung, die dynamisch erstellt wurde. (Haftungsausschluss)
Cet article a été traduit automatiquement de manière dynamique. (Clause de non responsabilité)
Este artículo lo ha traducido una máquina de forma dinámica. (Aviso legal)
此内容已经过机器动态翻译。 放弃
このコンテンツは動的に機械翻訳されています。免責事項
이 콘텐츠는 동적으로 기계 번역되었습니다. 책임 부인
Este texto foi traduzido automaticamente. (Aviso legal)
Questo contenuto è stato tradotto dinamicamente con traduzione automatica.(Esclusione di responsabilità))
This article has been machine translated.
Dieser Artikel wurde maschinell übersetzt. (Haftungsausschluss)
Ce article a été traduit automatiquement. (Clause de non responsabilité)
Este artículo ha sido traducido automáticamente. (Aviso legal)
この記事は機械翻訳されています.免責事項
이 기사는 기계 번역되었습니다.책임 부인
Este artigo foi traduzido automaticamente.(Aviso legal)
这篇文章已经过机器翻译.放弃
Questo articolo è stato tradotto automaticamente.(Esclusione di responsabilità))
Translation failed!
Export management logs directly from NetScaler to Splunk
You can now export management logs (non-packet engine logs) on a category basis such as shell
, access
, and nsmgmt
logs from NetScaler to industry standard log aggregator platforms such as Splunk. Using the visualization tools at Splunk, you can get meaningful insights about the exported data.
There are multiple ways to export management logs from NetScaler to Splunk. You can either configure Splunk as an HTTP server or a syslog server. In the HTTP server configuration, you can use the HTTP event collector to send management logs over HTTP (or HTTPS) directly to the Splunk platform from your NetScaler. In the syslog server configuration, management logs are sent as syslog payloads from NetScaler to Splunk.
Export management logs to Splunk configured as an HTTP server
To configure the export of management logs you must perform the following steps:
- Configure an HTTP event collector on Splunk.
- Create a collector service and a time series analytics profile on NetScaler.
Note:
- Management logs are not supported for non-time series profiles.
- Management logs are not exported out of secondary nodes by default. Use time series over NSIP (
set appflow param -timeseriesovernsip enabled
) when the destination is reachable using NSIP and secondary export is required.
Configure an HTTP event collector on Splunk
You can forward management logs to Splunk by configuring an HTTP event collector. Configuring the HTTP event collector involves creating an authentication token and associating an event index with the token where events are sent, and setting the HTTP port number.
For information on how to configure the HTTP event collector, see the Splunk documentation.
Once you have configured the HTTP event collector, copy the authentication token and save it for reference. You need to specify this token while configuring the analytics profile on NetScaler.
Configure a time series analytics profile on NetScaler using the CLI
Do the following to export NetScaler management logs to Splunk.
-
Create a collector service for Splunk.
add service <collector> <splunk-server-ip-address> <protocol> <port>
Example:
add service splunk_service 10.102.34.155 HTTP 8088
In this configuration:
-
ip-address
: Splunk server IP address. -
collector-name
: Name of the collector. -
protocol
: Specify the protocol as HTTP or HTTPS -
port
: Port number.
-
-
Create a time series analytics profile.
add analytics profile `profile-name` -type time series -managementlog <management-log-type> -collectors `collector-name` -analyticsAuthToken `auth-tocken`-analyticsEndpointContentType `Application/json` -analyticsEndpointMetadata `meta-data-for-endpoint` -analyticsEndpointUrl `endpoint-url`
Example:
add analytics profile managementlogs_profile -type timeseries -managementlog ACCESS -collectors splunk -analyticsAuthToken "Splunk 1234-5678-12345" -analyticsEndpointContentType "application/json" -analyticsEndpointMetadata '{"source":"netscaler","sourcetype:"mgmtlog","index":"ns-mgmtlog-index"}' -analyticsEndpointUrl "/services/collector/event"
In this configuration:
-
managementlog
: Types of management logs that you must export. The following options are available:-
ALL
: Includes all categories of management and host logs. -
SHELL
: Includesbash.log
andsh.log
. -
Access
: Includes logs such asauth.log
,nsvpn.log
,vpndebug.log
,httpaccess.log
,httperror.log
,httpaccess-vpn.log
, andhttperror-vpn.log
. -
NSMGMT
: Includesns.log
andnotice.log
. -
NONE
: None of the logs are exported.
-
-
analyticsAuthToken
: Specify the authentication token to be included in the authorization header with the prefix “Splunk” while sending logs to Splunk. This token is the authentication token created on the Splunk server while configuring the HTTP event collector. -
analyticsEndpointContentType
: Format of the logs. -
analyticsEndpointMetadata
: Meta data that is endpoint specific. Management logs use HEC format as documented at Format events for HTTP Event Collector. The payload format is as follows:{ "host": "<hostname set on the box by default>", "event": { "Loglevel": <int>, "Managementlog string": <string>, "Message Name": <string>, "Module Name": <string> } } <!--NeedCopy-->
HEC format defines several meta fields that can be included in the payload other than the actual event including host, index, source, sourcetype, and so on.
By default, NetScaler uses the FreeBSD host name as “host” and does not set any fields such as index, source, sourcetype in the payload. This setting can be changed by explicitly providing the required fields in
-analyticsEndpointMetadata
.For example, using
'{"host":"my-netscaler","index":"my-splunk-index","sourcetype":"managementlog","source":"netscaler"}'
as-analyticsEndpointMetadata
crafts the below payload for every log:{ "host": "my-netscaler", "index": "my-splunk-index", "sourcetype": "managementlog", "source": "netscaler", "event": { "Loglevel": <int>, "Managementlog string": <string>, "Message Name": <string>, "Module Name": <string> } } <!--NeedCopy-->
Notice how the
host
is overwritten. (This behavior might not be desirable when logs are sent from both primary and secondary nodes because both carry the same host name. In this scenario, it is preferable not to configure the host inanalyticsEndpointMetadata
so that the FreeBSD host names are used by the respective nodes.)Also, notice that the fields index, sourcetype, source are added to the payload.
Note:
Ensure that
-analyticsEndpointMetadata
is a proper JSON. -
analyticsEndpointUrl
: Location in the endpoint to export logs.
Note:
You can modify the time series analytics profile parameters using the
set analytics profile
command. -
-
Verify the analytics profile configuration using the
show analytics profile
command.# show analytics profile splunkexport 1) Name: audit_profile Collector: splunk Profile-type: timeseries Output Mode: avro Metrics: DISABLED Schema File: schema.json Metrics Export Frequency: 30 Events: DISABLED Auditlog: DISABLED Serve mode: Push Authentication Token: <auth-tocken> Endpoint URL: /services/collector/event Endpoint Content-type: Application/json Endpoint Metadata: Event: Reference Count: 0 Managementlog: ACCESS
Once the configuration is successful, the management logs are sent as HTTP payloads to Splunk and you can view it on the Splunk application user interface.
Configure a time series analytics profile on NetScaler using the GUI
Perform the following steps:
- Create a collector service.
- Navigate to Traffic Management > Load Balancing > Services and click Add.
- On the Load Balancing Service page, enter the details in the required fields, click OK and then click Done.
-
Create a time series analytics profile.
- Navigate to System > Profiles > Analytics Profiles and click Add.
-
On the Create Analytics Profile page, provide the following details:
- Enter a name for the profile.
- From the Collectors list, select the service that you created.
- Select a TIME SERIES from the Type list.
- Enter the Analytics Auth Token that you received from Splunk with the prefix “Splunk”.
- Enter the details for Analytics Endpoint URL, Analytics Endpoint Content Type, and Analytics Endpoint Metadata.
- Select the Management Logs that you want to export and also the Output Mode in which you want to export.
- Click Create.
Export management logs to Splunk configured as a syslog server
To configure the export of management logs, you must perform the following steps:
Step 1: Configure Splunk as an external syslog server
You can forward management logs to Splunk by configuring an external syslog server on Splunk.
For information on how to configure the syslog port, see the Splunk documentation. Once you have configured the syslog port, save it for reference. You need to specify this port while configuring the audit syslogaction
on NetScaler.
Step 2: Create an audit syslog action
For information on the steps to create an audit syslog action on NetScaler with the management log option, see Configure syslog audit action.
Step 3: Create a syslog audit policy
For information on the steps to create a syslog audit policy with the syslog action, see Configure syslog audit policy.
Step 4: Bind audit log policy
For information on how to bind audit log policy, see Bind audit log policy.
Additional information
This section provides more information on the three types of logs specified in this topic:
-
shell
logs: Includesbash.log
andsh.log
. -
access
logs: Includeshttpaccess.log
,httperror.log
,httpaccess-vpn.log
,httperror-vpn.log
,vpndebug.log
,nsvpn.log
, andauth.log
. -
nsmgmt
logs: Includesnotice.log
, andns.log
(only includes non-packet engine logs).
Troubleshoot issues related to management logs export
For troubleshooting tips related to management logs export, see Troubleshoot issues related to management logs.
Share
Share
This Preview product documentation is Cloud Software Group Confidential.
You agree to hold this documentation confidential pursuant to the terms of your Cloud Software Group Beta/Tech Preview Agreement.
The development, release and timing of any features or functionality described in the Preview documentation remains at our sole discretion and are subject to change without notice or consultation.
The documentation is for informational purposes only and is not a commitment, promise or legal obligation to deliver any material, code or functionality and should not be relied upon in making Cloud Software Group product purchase decisions.
If you do not agree, select I DO NOT AGREE to exit.