jetPACK

jetPACK

jetPACKs are a unique method of instantly configuring your edgeNEXUS Accelerating Load Balancer for specific applications. These easy-to-use templates come pre-configured and fully-tuned with all of the application-specific settings that you need in order to enjoy optimised service delivery from your Load Balancer. This page is split in to the following sections. Some of the jetPACKs use flightPATH to manipulate the traffic, you must have a flightPATH license for this particular element to work. To find out if you have a license for flightPATH please refer to the License page

This page is split in to the following sections

Download a jetPACK

Each of the jetPACKS below have been created with the following generic details. If you wish to customise these generic jetPACKs then carry out a search and replace for your VIP address and Content Server Addresses.

jetPACK1 will install virtual interface (or channel) 1 with VIP =1.1.1.1 – Content Server1= 11.11.11.11 or 21.21.21.21 and Content Server2= 12.12.12.12 or 22.22.22.22
jetPACK2 will install virtual interface (or channel) 2 with VIP= 2.2.2.2 – Content Server1= 11.11.11.11 or 21.21.21.21 and Content Server2= 12.12.12.12 or 22.22.22.22
jetPACK3 will install virtual interface (or channel) 3 with VIP= 3.3.3.3 – Content Server1= 11.11.11.11 or 21.21.21.21 and Content Server2= 12.12.12.12 or 22.22.22.22
jetPACK4 will install virtual interface (or channel) 4 with VIP= 4.4.4.4 – Content Server1= 11.11.11.11 or 21.21.21.21 and Content Server2= 12.12.12.12 or 22.22.22.22

Right click on a jetPACK link below and Save Link as… a jetPACKName.txt file in your chosen location

Web Services

[su_row]
[su_column size=”1/4″]Normal HTTP

[/su_column]
[su_column size=”1/4″]SSL Offload

[/su_column]
[su_column size=”1/4″]SSL Re-Encryption

[/su_column]
[su_column size=”1/4″]SSL Passthrough

[/su_column]
[/su_row]

Microsoft Remote Desktop

[su_row][su_column size=”1/2″]RDP

[/su_column]
[su_column size=”1/2″]RDP (NLA enabled)

[/su_column]
[/su_row]

Microsoft Exchange

[su_row][su_column size=”1/2″]Exchange 2010

[/su_column]
[su_column size=”1/2″]Exchange 2013

[/su_column]
[/su_row]

Microsoft Lync 2010/2013

[su_row][su_column size=”1/4″]Reverse Proxy

[/su_column]
[su_column size=”1/4″]Front End

[/su_column]
[su_column size=”1/4″]Edge Internal

[/su_column]
[su_column size=”1/4″]Edge External

[/su_column][/su_row]

DICOM – Digital Imaging and Communications in Medicine

Oracle – E-Business Suite

VMware Horizon View

[su_row][su_column size=”1/2″]Connection Servers – SSL Offload

[/su_column]
[su_column size=”1/2″]Security Servers – SSL Re-Encryption

[/su_column]
[/su_row]

Global Settings

GUI Secure Port 443 – this jetPACK will change you secure GUI port from 27376 to 443. https://x.x.x.x
GUI Timeout 1 day – the GUI will request you to input your password every 20 minutes. This will increase that request to 1 day
ARP Refresh 10 – during a failover between HA appliances this will increase the number of Gratuitous ARP’s to assist the switches during the transition

back

Apply a jetPACK

Please apply a jetPACK to the first available interface. If the first virtual interface is already configured, apply jetPACK2.
If you apply jetPACK1 to an ALB-X that already has virtual interface 1 configured it will over-write the details of this interface with the contents of the jetPACK.

Navigate to Advanced–>Update Software

  • Configuration Section
  • Upload New Configuration
  • Browse for jetPACK
  • Click Upload
  • Once the browser screen turns white please click refresh and wait for the Dashboard page to appear

back

Create a jetPACK

One of the great things about jetPACKs is that you can create your own. It may be that you want to replicate some settings from one box to the next or you wish to create a jetPACK for your specific application to roll out to the rest of the business.

  • Start by copying the current configuration from your existing ALB-X
    • Advanced
    • Update Software
    • Download Current Configuration
    • Click Hear to download the ALB-X.conf file
  • Edit this fIle with Notepad
  • Open up 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 #!update at the top of the page.

The sections that are recommended for editing/copying are listed below.

Section 0:

#!update

This needs to be at the top of the jetPACK or your current configuration will be over written.

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 is the tcp timeout value in miliseconds. This particular setting means that a tcp connection will be closed after 10 minutes of inactivity

ContentServerCustomTimer=20000
This is delay in milliseconds between content server health checks for custom monitors such as DICOM

jnCookieHeader=”MS-WSMAN”
This 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 normally 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 of the details in the IP Services section. Each interface is numbered and contains subinterfaces 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 of the flightPATH rules. It is important that the numbers match what has been applied to the interface. In the example above we see that flightPATH rule “6” has been applied to the channel so we will include 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=

back

CONTACT US

We're not around right now. But you can send us an email and we'll get back to you, asap.

Sending

Log in with your credentials

or    

Forgot your details?