You can apply any jetPACK in any order but be careful not to use a jetPACK with the same Virtual IP address. This action will cause a duplicate IP address in the configuration. If you do this by mistake, you can change this in the GUI.
· Navigate to Advanced > Update Software
· Configuration Section
· Upload New Configuration or jetPACK
· Browse for jetPACK
· Click Upload
· Once the browser screen turns white, please click refresh and wait for the Dashboard page to appear
Creating a jetPACK
One of the great things about jetPACK is that you can create your own. It may be that you have created the perfect config for an application and want to use this to several other boxes independently.
· Start by copying the current configuration from your existing ALB-X
o Advanced
o Update Software
o Download Current Configuration
· Edit this file with Notepad++
· Open a new txt document and call it “yourname-jetPACK1.txt”
· Copy all the relevant sections from the config file to “yourname-jetPACK1.txt”
· Save once complete
IMPORTANT: Each jetPACK is split into different sections, but all jetPACKs must have #!jetpack at the top of the page.
The sections that are recommended for editing/copying are listed below.
Section 0:
#!jetpack
This line needs to be at the top of the jetPACK, or your current configuration will be overwritten.
Section1:
[jetnexusdaemon]
This section contains global settings that, once changed, will apply to all services. Some of these settings can be changed from the web console, but others are only available here.
Examples:
ConnectionTimeout=600000
This example is the TCP timeout value in milliseconds. This setting means that a TCP connection will be closed after 10 minutes of inactivity
ContentServerCustomTimer=20000
This example is the delay in milliseconds between content server health checks for custom monitors such as DICOM
jnCookieHeader=”MS-WSMAN”
This example will change the name of the cookie header used in persistent load balancing from the default “jnAccel” to “MS-WSMAN”. This particular change is needed for Lync 2010/2013 reverse proxy.
Section 2:
[jetnexusdaemon-Csm-Rules]
This section contains the custom server monitoring rules that are typically configured from the web console here.
Example:
[jetnexusdaemon-Csm-Rules-0]
Content=”Server Up”
Desc=”Monitor 1″
Method=”CheckResponse”
Name=”Health Check- Is Server Up”
Url=”HTTP://demo.jetneus.com/healthcheck/healthcheck.html”
Section 3:
[jetnexusdaemon-LocalInterface]
This section contains all the details in the IP Services section. Each interface is numbered and includes sub-interfaces for each channel. If your channel has a flightPATH rule applied, then it will also contain a Path section too.
Example:
[jetnexusdaemon-LocalInterface1]
1.1=”443″
1.2=”104″
1.3=”80″
1.4=”81″
Enabled=1
Netmask=”255.255.255.0″
PrimaryV2=”{A28B2C99-1FFC-4A7C-AAD9-A55C32A9E913}”
[jetnexusdaemon-LocalInterface1.1]
1=”>,””Secure Group””,2000,”
2=”192.168.101.11:80,Y,””IIS WWW Server 1″””
3=”192.168.101.12:80,Y,””IIS WWW Server 2″””
AddressResolution=0
CachePort=0
CertificateName=”default”
ClientCertificateName=”No SSL”
Compress=1
ConnectionLimiting=0
DSR=0
DSRProto=”tcp”
Enabled=1
LoadBalancePolicy=”CookieBased”
MaxConnections=10000
MonitoringPolicy=”1″
PassThrough=0
Protocol=”Accelerate HTTP”
ServiceDesc=”Secure Servers VIP”
SNAT=0
SSL=1
SSLClient=0
SSLInternalPort=27400
[jetnexusdaemon-LocalInterface1.1-Path]
1=”6″
Section 4:
[jetnexusdaemon-Path]
This section contains all the flightPATH rules. The numbers must match what has been applied to the interface. In the example above, we see that flightPATH rule “6” has been applied to the channel, including this as an example below.
Example:
[jetnexusdaemon-Path-6]
Desc=”Force to use HTTPS for certain directory”
Name=”Gary – Force HTTPS”
[jetnexusdaemon-Path-6-Condition-1]
Check=”contain”
Condition=”path”
Match=
Sense=”does”
Value=”/secure/”
[jetnexusdaemon-Path-6-Evaluate-1]
Detail=
Source=”host”
Value=
Variable=”$host$”[jetnexusdaemon-Path-6-Function-1]
Action=”redirect”
Target=”HTTPs://$host$$path$$querystring$”
Value=
