WX Stack Implementation Guide - Juniper Networks · 2017. 3. 1. · • The WX100 stack does not support IPsec. However, SSL encryption is available with the optional encryption license

IMPLEMENTATION GUIDE

Copyright © 2009, Juniper Networks, Inc. 1

WX STACK IMPLEMENTATION GUIDE

Although Juniper Networks has attempted to provide accurate information in this guide, Juniper Networks does not warrant or guarantee the accuracy of the information provided herein. Third party product descriptions and related technical details provided in this document are for information purposes only and such products are not supported by Juniper Networks. All information provided in this guide is provided “as is”, with all faults, and without warranty of any kind, either expressed or implied or statutory. Juniper Networks and its suppliers hereby disclaim all warranties related to this guide and the information contained herein, whether expressed or implied of statutory including, without limitation, those of merchantability, fitness for a particular purpose and noninfringement, or arising from a course of dealing, usage, or trade practice.

2 Copyright © 2009, Juniper Networks, Inc.

IMPLEMENTATION GUIDE - WX Stack Implementation Guide

Table of Contents

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Target Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Design Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Bandwidth . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Tunnel Capacity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

High Availability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Scalability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Stack Deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Tunnel Distribution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Community . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Community Size . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Licensing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Limitations/Caveats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7

Implementation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7

Software Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7

Hardware Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7

Implementation Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7

Steps to Implement a WX Stack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7

For the Stack Master (WX100): . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7

For Stack Clients: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7

Stack to Stack Implementation Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

For Stack Clients on Either End: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Stack to Standalone Client Implementation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10

Steps to Implement a WX Stack to Standalone WX Series Clients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10

For the Stack Master (WX100): . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10

For Stack Clients: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10

Verification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Migration of Devices To and From Stacks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Adding a Client to an Existing Stack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Disconnecting a Client from a Stack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Returning a WX100 Stack Server to Standalone Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Connecting to Stack Clients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Log Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Rebalance Tunnels Across Client Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

About Juniper Networks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13



Table of Figures

Figure 1: WX Stack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Figure 2: Stack to stack topology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Figure 3: Configuring WX100 tunnels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Figure 4: Stack to branches topology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10

Figure 5: Viewing system log for registration password mismatch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12



Introduction

Juniper Networks® delivers a wide-area application acceleration solution with the Juniper Networks WXC Series

Application Acceleration Platforms. Deployed at the data center and branch offices, the WXC Series enables network

administrators to optimize existing WAN links and deliver fast application response. The WXC Series integrates several

technologies including advanced compression, sequence caching, TCP, and application-specific acceleration along

with bandwidth management to accelerate overall WAN performance.

The WXC Series can be used in a stack configuration to increase the capacity and number of compression tunnels

beyond the limits of a single WXC Series device. This document details the implementation of Juniper Networks WX

Stack for deployment in larger scale WAN topologies.

Scope

The solution presented in this document details the implementation of a Juniper Networks WXC Stack configuration

to offer a solution to optimize and accelerate WAN traffic for networks requiring greater bandwidth. Currently, the

highest capacity WXC Series appliance provides up to 45 megabits per second (Mbps) of optimized WAN bandwidth.

Networks requiring WXC Series optimization beyond the limits of a standalone appliance can use the WXC Series stack

presented here.

Target Audience

This document is intended for network design, operation engineers, and implementation partners that support

networks requiring high capacity optimized WAN connectivity.

Design Considerations

A WX Stack consists of a Juniper Networks WX100 Application Acceleration Platform acting as a controller or stack

master, along with one to six individual Juniper Networks WXC500 Application Acceleration Platform devices or Juniper

Networks WXC590 Application Acceleration Platform devices acting as stack clients to form a single WX Stack. Only

the WXC500 or WXC590 devices are supported as stack clients. Stack clients must be the same WXC Series model

(either WXC500 or WXC590) within a single stack.

Figure 1: WX Stack

Bandwidth

The WX Stack solution allows for a WAN acceleration solution to scale up to OC-3 (155 Mbps) rates using a WX100

controller and three WXC590 stack clients. The total stack bandwidth does not increase beyond the 155 Mbps

provided with three stack clients since this is the capacity limit for the WX100 stack server.

To WAN

To LAN

To WAN

To LAN



Tunnel Capacity

A second advantage to a WX Stack is to scale beyond the tunnel capacity for any single WX Series device. For large

WXC Series deployments with many remote sites connecting to a data center, the single WXC Series device limit of 140

tunnels may be insufficient. A stack deployment can scale the number of tunnels at a hub to 840 tunnels as indicated

in tables 1 and 2 below.

High Availability

As WXC Stacks are deployed in critical, high capacity junctures, having redundancy can be advantageous. A simple

form of high availability (HA) within a stack is to add an extra stack client for HA that will serve in case of a single

stack client failure. For example, a stack with two WXC590 clients operating on a 100 Mbps WAN connection would be

limited to 45 Mbps of WAN optimization if one of the stack clients were to fail. By employing a third WXC Series as an

HA stack client, WAN optimization is uncompromised. If the third WXC Series client acts as an HA stack client, it will

take over if either one of the operating stack clients fails.

Scalability

The tables below details stack capacity and scaling using WXC500 and WXC590 clients for bandwidth and tunnels in both

HA and non-HA deployments. The columns specifying HA provides scalability capacities when a stack client has failed.

Table 1: WX Stack Scalability with WXC500 Clients

NUMBER OF WXC500

CLIENTS

MAX TUNNEL COUNT MAX WAN LINK SPEED

(MBPS)

MAX TUNNEL COUNT

WITH HA

MAX WAN LINK SPEED

WITH HA

1 50 20 NA NA

2 100 45 50 20

3 150 70 100 45

4 200 95 150 70

5 250 120 200 95

6 300 155 250 120

Table 2: WX Stack Scalability with WXC590 Clients

NUMBER OF WXC590

CLIENTS

MAX TUNNEL COUNT MAX WAN LINK SPEED

(MBPS)

MAX TUNNEL COUNT

WITH HA

MAX WAN LINK SPEED

WITH HA

1 140 45 NA NA

2 280 100 140 45

3 420 155 280 100

4 560 155 420 155

5 700 155 560 155

6 840 155 700 155

Stack Deployment

WX Stacks can be deployed in the network in either inline or packet-intercept (off-path) modes. Inline mode has the

advantage of simple deployment with fail-to-wire bypass in case of WX100 failure. Packet-intercept mode allows for

redirection of specific traffic to only optimize traffic requiring WAN acceleration. Refer to the Physical Interface Module

(PIM) design guide for further information on packet-intercept mode.



Tunnel Distribution

For standalone Juniper Networks WX Series /WXC Series Application Acceleration Platforms deployments, a single

compression tunnel is created between two WX Series/WXC Series devices across a WAN link. Similarly, a WX Stack

will create a single tunnel between the WX Stack and a standalone WX Series/WXC Series.

In an HA topology, when connecting site A that has a single WX Stack to site B, which has a HA pair of standalone WX

Series/WXC Series devices, the WX Stack will create a single tunnel to each WX Series/WXC Series device. Thus, site

A’s WX Stack will create two tunnels: one to each HA WX Series/WXC Series device at site B.

For a stack-to-stack deployment, one tunnel can be formed per stack client to increase the bandwidth between the

stacks. For example, there can be three tunnels with three stack clients.

Within a stack, new tunnels are created amongst the stack clients in a round-robin manner with the stack client that

has the fewest tunnels assigned to the new tunnel.

Flow

For stack-to-stack multi-tunnel deployments, flows are distributed among the client tunnels through round-robin based on an

internal hash of source IP address, destination IP address, source port number, and destination port number.

As stacks create tunnels between individual stack clients, individual flows are constrained to the maximum capacity of

a single client, such as 45 Mbps if using WXC590s as stack clients. While the WX100 can support a maximum of OC-3

speed, or 155 Mbps, any flow cannot be greater than the capacity of the stack client.

Community

The WX Stack needs to be in a WX Series community to form tunnels to other WX Series devices. The community

topology choices for a WX Stack are hub, mesh, and point-to-point.

• Hub–The WX Stack should be specified as a hub if it is at a data center and all other WX Series devices in the

community will form tunnels to it.

• Mesh–This option is used if the WX Series devices are fully or partially meshed.

• Point-to-point–This should be selected if connecting two WX Series stacks between two data centers.

Note: A WX Stack cannot be specified as a spoke.

Community Size

A WX Series community size must be specified when defining the community parameters. The community size

parameter optimizes the limited internal memory to better allocate tunnels. When deploying a stack, the WX Series

community size is determined by the specific stack client model used. The WX100 Series stack master calculates

community size based on the WXC Series client model connected to the server and calculates the maximum

community size as if six clients were connected to the stack master.

The community size options available are:

WXC500 clients

• Small community–Up to 60 devices

• Large community–Up to 300 devices

WXC590 clients

• Small community–Up to 384 devices

• Large community–Up to 840 devices

Licensing

The only required license on the WX Stack is the WAN speed license on the WX100. WX Stack clients do not require

any additional license.

Note: If SSL encryption (WX Series 5.6 or later) is required on the stack, the encryption license needs to be applied to

the WX100.



Limitations/Caveats

• The WX100 stack does not support IPsec. However, SSL encryption is available with the optional encryption license.

• Single flows are constrained to maximum capacity of the single client (45 Mbps for each WXC590 client).

• A WX100 in stack mode does not support tunnel switching.

- Tunnel switching is a feature that allows a WX Series device to compress data for every WX Series in the network

without having to form a tunnel to each remote WX Series device.

Implementation

Software Requirements

Recommended software versions for deploying a WX Stack are the latest versions of either 5.4.x or 5.6.x. If the WX100

and stack clients are running 5.4.4 or later, the WX Series will upgrade stack clients to the same software version that

is running on the WX100. A WX Stack is upgraded by simply upgrading the WX100 since it will push the upgrade to the

stack clients.

Hardware Requirements

Stack master: WX100

Stack clients:

• Can be either WXC500 or WXC590 devices.

• All stack clients must be the same model. WXC500 and WXC590 clients cannot be mixed.

• Juniper Networks WXC2600 Application Acceleration Platform and WXC3400 Application Acceleration Platform

cannot be used as stack clients.

Implementation Guidelines

Steps to Implement a WX Stack

For the Stack Master (WX100):

1. Upgrade WX100 to WX operating system (WXOS) 5.4.4. or later.

2. Connect to WX100 through a console and use Quick Setup to configure basic networking and interface parameters.

3. Log in to the WX100 and configure the following to set the WX100 as a stack server:

config stack-group set host-session clients-only

4. If using WXC Series devices as clients, configure the following to allow the WX100 to use the disks of the

WXC Series clients:

config stack-group set sequence-mirror-server on

For Stack Clients:

1. Upgrade WXC Series devices to WXOS 5.4.4 or later.

2. Connect to each client device and run Quick Setup to configure a temporary IP address for management. Once

configured as a stack client, the WX100 will change the configured IP to internal IPs.

3. Log in to each client and enter the following commands:

config stack-group set client-mode-on commit save-configreboot



Type “y” to confirm save and the reboot.

Note: A reboot of the stack client is required to change its operation from a standalone WXC Series device to a

stack client.

4. A reboot of the stack client is required to change its operation from a standalone WXC Series device to a

stack client.

5. For each client device, connect a straight-through cable from the client’s local port to one of the ports numbered

1 to 6 on the WX100. The client ID will correspond to the WX100 port it is connected to.

6. All further configurations for the stack are done on the WX100 stack master.

Stack to Stack Implementation Example

Figure 2: Stack to stack topology

Figure 1 depicts the use case of stack implementation between two LAN. This deployment scenario fits into data

center design.

Perform the following for each Stack Master (WX100) on either end to realize this deployment:

1. Upgrade WX100 to WXOS 5.4.4. or later.

2. Connect to WX100 through console and use quick setup to configure basic networking and interface parameters.

3. Configure WX Series topology as point-to-point.

a. Within Web UI, configure this in Device Setup > Advanced > Topology.

4. Log in to the WX100 CLI and configure the following:

a. config stack-group set host-session clients-only

5. If using WXC Series devices as clients, configure the following:

a. config stack-group set sequence-mirror-server on

6. When implementing connectivity between two identically sized WXC Series stacks (two or more clients each),

configure multiple tunnels between the WX100 stack servers to increase throughput between the stacks. Up to six

tunnels can be configured–one for each client in the stack. Configure the following:

a. Through the Web UI, this is configured under Device Setup > Advanced > WX100 Tunnels in the navigation pane.

b. Enter the remote IP address and number of tunnels (two to six). The same number of tunnels should be

configured on either stack.

c. Click Add and then Submit to activate the changes.

WX Stack

WX100

WX Stack

WX10090

Mbps90

MbpsLAN LAN

DATA CENTER 2DATA CENTER 1

WAN



Figure 3: Configuring WX100 tunnels

For Stack Clients on Either End:

1. Upgrade WX Series devices to WXOS 5.4.4 or later.

2. Connect to each client device and run quick setup to configure a temporary IP address for management. Once



config stack-group set client-mode-oncommitsave-config

Type “y” to confirm save and the reboot.

4. For each client device, connect a straight-through cable from the client’s local port to one of the ports numbered 1 to

6 on the WX100. The client ID will correspond to the WX100 port it is connected to.



Stack to Standalone Client Implementation

Figure 4: Stack to branches topology

Steps to Implement a WX Stack to Standalone WX Series Clients

For the Stack Master (WX100):

1. Upgrade WX100 to WXOS 5.4.4. or later.

2. Connect to WX100 through a console and use Quick Setup to configure basic networking and interface parameters.

3. Configure WX Series topology as hub.

a. Within the Web UI, configure this in Device Setup > Advanced > Topology.

4. Log in to the WX100 CLI and configure the following:

config stack-group set host-session clients-only

5. If using WXC Series devices as clients, configure the following:

config stack-group set sequence-mirror-server on

For Stack Clients:

1. Upgrade WX Series devices to WXOS 5.4.4 or later.

2. Connect to each client device and run Quick Setup to configure a temporary IP address for management. Once



config stack-group set client-mode-oncommitsave-configreboot

WX Stack

WX100

WXC Series

WXC2600

90Mbps

20Mbps

10 Mbps

20 Mbps

LAN

LAN

DATA CENTER

BRANCH N

WANWXC Series

WXC2600LAN

BRANCH 2

LAN

BRANCH 1

J Series/ISM200



Type “y” to confirm the save and reboot.

4. For each client device, connect a straight-through cable from the client’s local port to one of the ports numbered

1 to 6 on the WX100. The client ID will correspond to the WX100 port it is connected to.

Verification

The WX Stack operation can be displayed with the show stack-group CLI command:

WX100-172.19.59.155# show stack-group Client mode: off

STACK CONFIGURATION:

Port Status Model Disk Status # Tunnels OUT INMaster Active WX-100 OK 0 0 1 Active WXC-590 OK 1 1 2 Active WXC-590 OK 1 1...

The following endpoints have been configured for multiple tunnels:

Endpoint Max Tunnels 30.1.1.2 2host-session: clients-onlysequence-mirror-server: on

The output lists the following:

• Status for each stack device

• Model type for the stack master and each client

• Number of outbound and inbound tunnels for each client

• Endpoints that are configured for multiple tunnels

Migration of Devices To and From Stacks

Adding a Client to an Existing Stack

An existing WX Stack can be expanded by simply connecting a new WX Series client to a WX100 client port. As the

new WX Series client will not have any existing tunnels, manual tunnel redistribution should be performed using the

steps given in the troubleshooting section below.

Disconnecting a Client from a Stack

If a stack client needs to be removed from a stack, the stack client has to be returned to factory default settings using

the following steps:

1. Disconnect the cable connecting the stack client from the WX100 stack server.

2. Reload factory default settings by connecting to the console port of the stack client and entering the

following command:

load-config factory-default

3. Perform manual tunnel redistribution as detailed in the troubleshooting section below.

As the client has been reset to factory default, it can be redeployed as a normal WX Series device.



Returning a WX100 Stack Server to Standalone Operation

If all clients are disconnected from a stack and the WX100 stack server is to be used as a standalone device, enter

the following:

config stack-group set host-session server onlyconfig stack-group set sequence-mirror-server off

Troubleshooting

Connecting to Stack Clients

Log files are maintained on both the stack master and stack clients. Connect to stack clients individually to access

client system logs.

Note: Connecting to individual stack clients should only be done when directed by the JTAC to do so.

To access the CLI on individual stack clients through SSH, use the following format:

SSH to: <IP address of stack server>:2000x where x is the client (1 through 6).

To access Web UI on a stack client:

https://<server-ip>:<client port> where client port is 30000+Client Id (Client Id between 1 and 6).

Log Files

Viewing the log files in the Web UI is the quickest way to troubleshoot common issues. Log files can be accessed under

Admin > Tools > Display System Log or Flow Diagnostics.

Figure 5: Viewing system log for registration password mismatch



Rebalance Tunnels Across Client Devices

If a stack client reboots or if a new stack client is added, tunnels will not be evenly distributed across the stack clients.

Client tunnel distribution can be seen using the show stack-group CLI command on the stack server.

Note: As this will cause a service interruption, this activity should be performed during a maintenance window.

1. Disable compression and decompression on the WX100. Click Compression, clear the two check boxes at the top of

the Endpoints page, and click Submit.

2. Verify that all tunnels are down on Compression > Basic > Endpoints page.

3. When all the tunnels are down, enter the following CLI commands (skip the second command if the server does not

have WXC Series clients):

reset stack-group tunnel-lb-inforeset stack-group tunnel-pref-infoset stack-group tunnel-lb-pkt-count offcommit

4. On the Endpoints page, select the Enable this device to COMPRESS check box, and click Submit.

5. Verify that all tunnels are established.

6. Select the Enable this device to DECOMPRESS check box, and click Submit.

7. Enter the following commands to re-enable load balancing by packet count:

set stack-group tunnel-lb-pkt-count on commit

Summary

The solution presented in this document described the implementation of a Juniper Networks WX Stack configuration

to optimize and accelerate WAN traffic for networks that require greater bandwidth.

This networking solution allows you to scale WAN and application acceleration to support bandwidth and tunnels

beyond the limitations of a standalone WXC Series device.

8010063-001-EN Dec 2009

Copyright 2009 Juniper Networks, Inc. All rights reserved. Juniper Networks, the Juniper Networks logo, Junos, NetScreen, and ScreenOS are registered trademarks of Juniper Networks, Inc. in the United States and other countries. All other trademarks, service marks, registered marks, or registered service marks are the property of their respective owners. Juniper Networks assumes no responsibility for any inaccuracies in this document. Juniper Networks reserves the right to change, modify, transfer, or otherwise revise this publication without notice.

EMEA Headquarters

Juniper Networks Ireland

Airside Business Park

Swords, County Dublin, Ireland

Phone: 35.31.8903.600

EMEA Sales: 00800.4586.4737

Fax: 35.31.8903.601

APAC Headquarters

Juniper Networks (Hong Kong)

26/F, Cityplaza One

1111 King’s Road

Taikoo Shing, Hong Kong

Phone: 852.2332.3636

Fax: 852.2574.7803

Corporate and Sales Headquarters

Juniper Networks, Inc.

1194 North Mathilda Avenue

Sunnyvale, CA 94089 USA

Phone: 888.JUNIPER (888.586.4737)

or 408.745.2000

Fax: 408.745.2100

www.juniper.net

To purchase Juniper Networks solutions,

please contact your Juniper Networks

representative at 1-866-298-6428 or

authorized reseller.

Printed on recycled paper



About Juniper Networks

Juniper Networks, Inc. is the leader in high-performance networking. Juniper offers a high-performance network

infrastructure that creates a responsive and trusted environment for accelerating the deployment of services and

applications over a single network. This fuels high-performance businesses. Additional information can be found at

www.juniper.net.

Documents

WX Stack Implementation Guide - Juniper Networks · 2017. 3. 1. · • The WX100 stack does not support IPsec. However, SSL encryption is available with the optional encryption license