Citrix ByteMobile T1010, ByteMobile T1100, ByteMobile T1200 Installation, Configuration And Administration

T-Series Traffic Director Install, Admin & Config Guide

SAFETY NOTICE

The product described in this document has safety considerations. Before installing or maintaining this product, please read the instructions in the “Safety Information” section on page iii. Failure to follow the safety instructions in this document may result in injury to self and others, or may cause property damage.

ByteMobile T1000 Traffic Director

Installation, Configuration, and Administration Guide Model T1010, T1100 and T1200

Release 1.0 Rev. H

Document Part Number: 707-00045-00

Printed: June 18, 2013

or reproduced in whole or in part, be copied, photocopied, translated, or reduced to any electronic medium or machine readable form without prior consent, in writing, from Citrix Systems, Inc.

Printed in the United States of America.

Disclaimer

The information in this document is subject to change without notice and should not be construed as a commitment by Citrix Systems, Inc. Citrix assumes no responsibility for any errors that may appear in this document.

Trademarks

Citrix, ByteMobile, the ByteMobile logo, Smart Capacity, Smart Capacity at the Core, Macara, Monaco, Unison, Media Fidelity, Web Fidelity, and Dynamic Interleaving are trademarks of Citrix Systems, Inc., or a subsidiary thereof, and are or may be registered in the U.S. Patent and Trademark Offi ce and other countries. All other trademar ks are the prop erty of their respective owners.

Safety

Before using the information in this document and the product it supports, read the information in this section, and the “Technical Assistance” section on page xix.

Before Installing

Before installing this product, read the Safety Information.

Antes de instalar este produto, leia as Informações de Segurança.

Safety Information

Læs sikkerhedsforskrifterne, før du installerer dette produkt. Lees voordat u dit product installeert eerst de veiligheidsvoorschriften. Ennen kuin asennat tämän tuotteen, lue turvaohjeet kohdasta Safety Information. Avant d'installer ce produit, lisez les consignes de sécurité. Vor der Installation dieses Produkts die Sicherheitshinweise lesen.

Prima di installare questo prodotto, leggere le Informazioni sulla Sicurezza.

Les sikkerhetsinformasjonen (Safety Information) før du installerer dette produktet.

Antes de instalar este produto, leia as Informações sobre Segurança.

T-Series Traffic Director Installation, Configuration and Administration Guide iii

Antes de instalar este producto, lea la información de seguridad. Läs säkerhetsinformationen innan du installerar den här produkten.

Safety Statements

These statements provide the caution and danger information used in this documentation.

Important: Each caution and danger statement in this documentation is labeled with a

number. This number is used to cross reference an English-language caution or danger statement with translated versions of the caution or danger statement in the Safety Information document.

For example, if a caution statement is labeled “Statement 1,” translations for that caution statement are in the Safety Information document under “Statement 1.”

Be sure to read all caution and danger statements in this documentation before you perform the procedures. Read any additional safety information that comes with your system or optional device before you install the device.

Statement 1

Danger:

iv T-Series Traffic Director Installation, Configuration and Administration Guide

Electrical current from power, telephone, and communication cables is hazardous.

To avoid a shock hazard:

• Do not connect or disconnect any cables or perform installation, maintenance,

or reconfiguration of this product during an electrical storm.

• Connect all power cords to a properly wired and grounded electrical outlet.

• Connect to properly wired outlets any equipment that will be attached to this

product.

• When possible, use one hand only to connect or disconnect signal cables.

• Never turn on any equipment when there is evidence of fire, water, or structural

damage.

• Disconnect the attached power cords, telecommunications systems, networks,

and modems before you open the device covers, unless instructed otherwise in the installation and configuration procedures.

• Connect and disconnect cables as described in the following table when

Class 1 Laser Product Laser Klasse 1 Laser Klass 1 Luokan 1 Laserlaite Appareil A Laser de Classe 1

installing, moving, or opening covers on this product or attached devices.

To Connect: To Disconnect:

1. Turn OFF all power sources and

equipment to be attached to this product.

2. Attach all cables to the devices.

3. Attach signal cables to the

connectors.

4. Attach power cords to power

sources. For DC systems, ensure correct polarity of -48VDC connections: RTN is (+) and

-48VDC is (-). Earth ground should use a two-hole lug for safety.

5. Turn ON all the power sources.

1. Turn OFF all power sources and

equipment to be attached to this product.

• For AC systems, remove all power

cords from the shelf power receptacles or interrupt power at the ac power distribution unit.

• For DC system systems, disconnect

DC power sources at the breaker panel or by turning off the power source, then remove the DC cables.

2. Remove the signal cables from the

connectors.

3. Remove all cables from the devices

Statement 3

Caution: When laser products (such as CD-ROMs, DVD drives, fiber optic devices, or

transmitters) are installed, note the following:

Danger:

T-Series Traffic Director Installation, Configuration and Administration Guide v

• Do not remove the covers. Removing the covers of the laser product could result in

exposure to hazardous laser radiation. There are no serviceable parts inside the device.

• Use of controls or adjustments or performance of procedures other than those

specified herein might result in hazardous radiation exposure.

Some laser products contain an embedded Class 3A or Class 3B laser diode. Note the following:

Laser radiation when open. Do not stare into the beam, do not view directly with optical instruments, and avoid direct exposure to the beam.

Statement 8

Caution: Never remove the cover on a power supply or any part that has the

following label attached.

Hazardous voltage, current, and energy levels are present inside any component that has this label attached. There are no serviceable parts inside these components. If you suspect a problem with one of these parts, contact a service technician.

Statement 12

Caution: The following label indicates a hot surface nearby.

Statement 13

Danger:

Overloading a branch circuit is potentially a fire hazard and a shock hazard under certain conditions. To avoid these hazards, ensure that your system electrical requirements do not exceed branch circuit protection requirements. Refer to the information that is provided with your device for electrical specifications.

Statement 29 (DC Models Only)

Caution: This equipment is designed to permit the connection of the earthed conductor of

the DC supply circuit to the earthing conductor at the equipment. If this connection is made, all of the following conditions must be met:

vi T-Series Traffic Director Insta llation, Configuration and Administration Guide

• This equipment shall be connected directly to the DC supply system earthing

electrode conductor or to a bonding jumper from an earthing terminal bar or bus to which the DC supply system earthing electrode conductor is connected.

• This equipment shall be located in the same immediate area (such as, adjacent

cabinets) as any other equipment that has a connection between the earthed conductor of the same DC supply circuit and the earthing conductor, and also the point of earthing of the DC system. The DC system shall not be earthed elsewhere.

• The DC supply source shall be located within the same premises as this equipment.

• Switching or disconnecting devices shall not be in the earthed circuit conductor

between the DC source and the point of connection of the earthing electrode conductor.

Statement 31

Danger:

Electrical current from power, telephone, and communication cables is hazardous.

To avoid a shock hazard:

• Do not connect or disconnect any cables or perform installation, maintenance,

or reconfiguration of this product during an electrical storm.

• Connect all power cords to a properly wired and grounded electrical outlet.

• Connect to properly wired outlets any equipment that will be attached to this

product.

• When possible, use one hand only to connect or disconnect signal cables.

• Never turn on any equipment when there is evidence of fire, water, or structural

damage.

• Disconnect the attached power cords, telecommunications systems, networks,

and modems before you open the device covers, unless instructed otherwise in the installation and configuration procedures.

• Connect and disconnect cables as described in the following table when

installing, moving, or opening covers on this product or attached devices.

T-Series Traffic Director Installation, Configuration and Administration Guide vii

To Connect: To Disconnect:

OFF

1. Turn OFF all power sources and

equipment to be attached to this product.

2. Attach all cables to the devices.

3. Attach signal cables to the

connectors.

4. Attach power cords to power

sources. For DC systems, ensure correct polarity of -48VDC connections: RTN is (+) and

-48VDC is (-). Earth ground should use a two-hole lug for safety.

5. Turn ON all the power sources.

Statement 33

1. Turn OFF all power sources and

equipment to be attached to this product.

• For AC systems, remove all power

cords from the shelf power receptacles or interrupt power at the ac power distribution unit.

• For DC system systems, disconnect

DC power sources at the breaker panel or by turning off the power source, then remove the DC cables.

2. Remove the signal cable s from the

connectors.

3. Remove all cables from the devices

Caution:

This device does not provide a power control button. Removing power supply modules or turning off the unit does not turn off the electrical current supplied to the device. The device also might have more than one power cord. T o r emove all electrical current from the device, ensure that all power cords are disconnected from the power source.

T1000 DC Power Option:

T1000 AC Power Option:

1 2

viii T-Series Traffic Director Installation, Configuration and Administration Guide

Statement 34

Caution:

To reduce the risk of electric shock or energy hazards:

• This equipment must be installed by trained service personnel in a

restricted-access location, as defined by the NEC and IEC 60950-1, First Edition, The Standard for Safety of Information Technology Equipment.

• Connect the equipment to a properly grounded safety extra low voltage

(SELV) source. A SELV source is a secondary circuit that is designed so that normal and single fault conditions do not cause the voltages to exceed a safe level (60 V direct current).

• Incorporate a readily available approved and rated disconnect device in

the field wiring.

• See the specifications in the product documentation for the required

circuit-breaker rating for branch circuit overcurrent protection.

• Use copper wire conductors only. See the specifications in the product

documentation for the required wire size.

• See the specifications in the product documentation for the required

torque values for the wiring-terminal nuts.

Fiber Optic Safety Information, Statement 1

Danger:

T-Series Traffic Director Installation, Configuration and Administration Guide ix

Hazardous Radiation Fiber optic products use laser radiation with the potential to cause injury. Uncovered ports may release this radiation. Avoid direct exposure to laser radiation. Do not stare into the beam, and do not view directly with optical instruments. Do not remove any protective shields on fiber optic transceiver modules.

x T-Series Traffic Director Installation, Configuration and Administration Guide

Safety Information

Before Installing iii Safety Statements iv

About This Guide

Objective xv Audience xv Organization xvi T-Series Related Documents xvi Unison Related Documents xvii Citrix NetScaler Documents xvii Revision History xvii Document Conventions xviii Notices and Statements in this Document xix Documentation Feedback xix Technical Assistance xix

Table of Contents

Chapter 1 Introduction

Traffic Director Architecture 1-2 Product Capabilities 1-4 Hardware Overview 1-8 Common Hardware Features 1-11

Chapter 2 Installing the T1000

Overview of Installing T1000 2-1 Cautions and Warnings 2-2 Preparing for Installation 2-4 Handling Static-Sensitive Devices 2-6 Unpacking the Shipping Container 2-7

T-Series Traffic Director Installation, Configuration and Administration Guide xi

Contents

Rack Mounting the T1000 2-8 Making Data Plane Connections 2-11 Making Management Connections 2-18 Connecting and Disconnecting AC Power 2-19 Connecting and Disconnecting DC Power 2-22 Accessing and Configuring the Management Plane 2-29 Accessing and Configuring the LOM Port 2-31

Chapter 3 Basic T1000/Unison Load-Balancing Configuration

Physical Integration of T1000 with Unison 3-2 Managing Configurations 3-3 Assigning VLANs, IP Addresses, and Ports 3-4 Configuring T1000 Basic Functions 3-8 Configuring T1000 Data Plane for Layer-2 an d La ye r- 3 3-11 Configuring T1000 Load Balancing 3-17 Configuring Health Checks and Redundancy 3-22 Configuring Source NAT (SNAT) 3-26 Configuring Security 3-27 Testing with Network Diagnostic and Shell Tools 3-29

Chapter 4 Dynamic Routing Protocol Configuration for T1000/Unison

Overview 4-1 OSPF Protocol and Setup 4-1 OSPF Configuration 4-2

Chapter 5 Administration

Using the T1000 Command Line Interface (CLI) 5-1 Using the T1000 Graphical User Interface (GUI) 5-2 Lights-Out Management 5-4 Upgrading the T1000 Operating System 5-4 Installing/Upgrading T1000 License 5-7 Authentication and Authorization 5-9 Configuring SNMP 5-15 Collecting Real-Time Statistics from the CLI 5-23 Advanced Administration 5-23

Appendix A T1000 Specifications

Environmental Specifications A-1 Power Characteristics A-2 Physical Characteristics A-3 Regulatory Compliance A-4

xii T-Series Traffic Director Installation, Configuration and Administration Guide

Appendix B Replacement Parts

Replaceable Components List B-1 Replacing an AC Power Supply B-2 Replacing a DC Power Supply B-4

Appendix C Legal Notices

Legal Notice C-1 Trademarks C-2 Third-Party Disclosures C-2 Important Notes C-2 Product Recycling and Disposal C-3 Battery Return Program C-3 Electronic Emission Notices C-4

Index

Contents

T-Series Traffic Director Installation, Configuration and Administration Guide xiii

Contents

xiv T-Series Traffic Director Installation, Configuration and Administration Guide

About This Guide

We are pleased that you have chosen the Bytemobile T1000 Traffic Director. As a network element in the T-Series architecture, the T1000 Traffic Director intelligently load balances traffic for Smart Capacity™ solutions on Bytemobile’s Unison™ platform. The high-performance T1000 enables operators to efficiently and cost-effectively manage explosive growth in data traffic while delivering a high-quality experience to their subscribers.

The T1000 Traffic Director can also provide advanced routing capabilities and load balancing for the Bytemobile T3100 Adaptive Traffic Manager.

Note: This manual uses the generic term “T1000” to refer to all hardware models of

Objective

Audience

the T1000 Traffic Director, including the T1010, T1100, and T1200. Specific model names are used only when necessary.

This manual describes how to install, configure, operate and maintain the T1000 Traffic Director. Before completing the steps in this manual, read the safety instructions at the beginning of this document.

This manual is intended for personnel who have been qualified to install and maintain T1000 systems. Readers should be familiar with installing hardware and software in a network operations center or in a mobile operator data center.

T-Series Traffic Director Installation, Configuration and Administration Guide xv

About This Guide

Organization

This document is organized as follows:

Chapter Description

Safety Information All hardware-related safety information. Read this

section before installing the hardware maintenance.

T1000 or performing

Chapter 1, “Introduction” Overview of Chapter 2, “Installing the T1000” Complete hardware installation procedures. Also

includes racking instructions and management plane configuration.

Chapter 3, “Basic T1000/Unison Load-Balancing Configuration”

Chapter 4, “Dynamic Routing Protocol Configuration for T 1000/Unison”

Chapter 5, “Administration” Provides procedures for logging on to the

Appendix A, “T1000 Specifications” Hardware specifications for the Appendix B, “Replacement Parts” List of replacement parts for

Appendix C, “Legal Notices” Legal notices, copyrights, third-party software

Describes how to configure Layer-2 and Layer-3 networking features of the configure the platform traffic.

Describes how to configure T1000 network features to support dynamic routing protocols such as OSPF on Unison deployments.

CLI and GUI. Also describes how to integrate the SNMP management features for monitoring performance and managing alarms and events.

replacement instructions where appropriate.

disclosures, and other legal information.

T1000 features and architecture.

T1000, and how to

T1000 to load-balance Unison

T1000

T1000 platform.

T1000. Includes

T-Series Related Documents

The ByteMobile T-Series documentation set includes the following components:

• T3100 Architecture Overview

• T3100 Hardware Installation Guide

• T3100 Network Configuration Guide

• T3100 Network Configuration Worksheet

• T3100 Application Conf iguration Guid e

• T3100 CLI Reference

• T3100 System Administration Guide

• T3100 Web GUI Reference

• T3100 Field Replacement Unit (FRU) QuickStart Guides

• T3100 Alarms and Troubleshooting Guide

• T3100 Safety and Notices Guide

xvi T-Series Traffic Director Installation, Configuration and Administration Guide

• T2100 Installation, Configuration and Administra tion Guide

• T1000 Installation, Configuration and Administra tion Guide

• T-Series EMS Installation Guide and Reference

Consult the latest release notes for important information not contained in the documentation set, such as resolved issues, known issues, and operating considerations.

Note: Manuals and release notes may be superseded by revised versions. ByteMobile

recommends visiting support.bytemobile.com for the latest releases of all customer documents.

Unison Related Documents

The Bytemobile Unison documentation set includes the following components.

• Unison Architecture Overview

• Unison OSN Configuration Guide

• Unison Policy Manager Guide

Unison Related Documents

• Unison KPI Tool Guide

• Unison Web Proxy Log File Specification

• Unison Media Proxy Log File Specification

• Unison OSN Disk Partitioning Spreadsheet

• Unison OSN Hardware Sizing Calculator

Citrix NetScaler Documents

The T1000 uses a common technology platform developed for the Citrix NetScaler appliance. Certain configuration and administration features are shared by both the T1000 and by the NetScaler.

Citrix provides a documentation website (http://support.citrix.com/proddocs/topic/netscaler/ns-gen-netscaler93-wrapper-con.html) with a searchable database of documents that are also intended to support T1000 deployments. In particular, the following sections are applicable to T1000:

• Administration

• Reference Material (includes Command Reference Guide, Log Message Reference,

and SNMP OID Reference)

Revision History

Bytemobile periodically releases updated versions of manuals to address known issues with the product, to correct errors, and to document features introduced in service pack releases. The revision level and document release date are noted on the front cover.

This document has the following revision history (earlier revisions not shown):

• Rev. G: Seventh revision of this document. Has the following changes:

T-Series Traffic Director Installation, Configuration and Administration Guide xvii

About This Guide

– Updated rear panel view of the T1200. See “Model T1200 Hardware” on page 1-11. – Updated rear panel views of the T1200 for ac and dc power connection in Chapter 2,

“Installing the T1000.”

– Updated the set lb vserver command in the procedure outlined in “Configuring

Minimum Servers and Backup Path” on page 3-24.

– Revised procedure for “Configuring Source NAT (SNAT)” on page 3-26. – Added example to “Configuring Health Monitors” on page 3-22. – Added additional information about configuring per-node weights to “Creating

Services” on page 3-19.

– Added additional procedure for binding the management IP address to a

VLAN/interface in “Setting Management IP Address” on page 3-8.

• Rev. H (DRAFT PENDING): Seventh revision of this document. Has the following

changes:

– Updated the heat and power output specifications of the T1200 in Appendix A,

“T1000 Specifications.”

– Updated the description of the number of power cords supplied with the AC power

T1200 in Chapter 2, “Installing the T1000.” The T1200 ships with 4 cords and not 2, as previously indicated.

– Procedures previously available only to support personnel, such as “Upgrading the

T1000 Operating System” on page 5-4, have been added to the standard edition of

this document. The support-only edition of this document has been deprecated.

Document Conventions

This document uses the following conventions:

Convention Description

boldface Commands, keywords, user inputs, and menu choices.

italic Directory paths, file names, syntax items (parameters) that must

[ ] Keywords or arguments that appear within square brackets are

{ x | x | x } A choice of keywords (represented by x) appears in braces

^ or Ctrl Represent the key labeled Control. For example, when you read

screen font

boldface screen font

be replaced with specific values, emphasis on new terms, and publication titles.

optional. Square brackets also indicate default responses to system prompts.

separated by vertical bars. You must select one.

^D or Ctrl-D, you should hold down the Control key while you press the D key.

Examples of information displayed on the screen. Examples of information that you must enter.

< > Nonprinting characters, such as passwords, appear in angled

brackets.

xviii T-Series Traffic Director Installation, Configuration and Administration Guide

Notices and Statements in this Document

The caution and danger statements in this document are also in the separate multilingual Safety Guide. Each statement is numbered for reference to the corresponding statement in the Safety Information document. The following notices and statements are used in this document:

Note: These notices provide important tips, guidance, or advice.

Important: These notices provide information or advice that might help you avoid

inconvenient or problem situations.

Attention: These notices indicate possible damage to programs, devices, or data. An

attention notice is placed just before the instruction or situation in which damage could occur.

Notices and Statements in this Document

Caution: These statements indicate situations that can be potentially hazardous to you. A

caution statement is placed just before the description of a potentially hazardous procedure step or situation.

Danger:

These statements indicate situations that can be potentially lethal or extremely hazardous to you. A danger statement is placed just before the description of a potentially lethal or extremely hazardous procedure step or situation.

Documentation Feedback

Bytemobile is committed to continuously improving the technical accuracy and usability of its product documentation. If you have suggestions, comments, or corrections, please send them to techpubs@bytemobile.com. Your comments will help improve the next version of the manual.

Technical Assistance

ByteMobile Technical Services for customers focuses on four areas: Professional Services, Solutions Engineering, Customer Support, and Education Services. These services are provided by an experienced team of data networking and support services professionals.

• Professional Services at professional_services@bytemobile.com are provided for

network design, deployment, and documentation. Customized professional services are also available in areas such as security monitoring and application verification.

• Solutions Engineering Servic es at solutions_engineering@bytemobile.com are

provided for custom feature development, third-party software integration and certification, new hardware platform certification and user-interface customization.

T-Series Traffic Director Installation, Configuration and Administration Guide xix

About This Guide

• Customer Support Services at support@bytemobile.com are available worldwide, on

a 24x7x365 basis for ByteMobile commercial customers with maintenance contracts in place.

• Education Services, at training@bytemobile.com, offer a curriculum of technical

training courses. Delivery methods include Classroom Training, Virtual Classroom Training, and Web Based Training. Education Services can tailor classroom training to meet individual customer and deployment requirements.

You can also find information about ByteMobile Technical Services at www.bytemobile.com.

xx T-Series Traffic Director Installation, Configuration and Administration Guide

1. Introduction

Introduction

The T1000 Traffic Director is a high-performance application delivery controller providing 100% availability for applications delivered through Bytemobile's Unison platform or Bytemobile’s T3100 Adaptive Traffic Management System. The T1000 integrates with these Bytemobile's platforms to deliver superior Smart Capacity application performance, reduce the time for putting into service new or replacement application servers and lower the operational complexity for a mobile-core Bytemobile deployment. By providing a guaranteed, unified package, Bytemobile offers a single vendor for all design, implementation and problem resolution.

The T1000 is a series of hardware platforms that includes the T1010, T1100 and T1200, with a capacity range from 2 Gbps up to 100 Gbps, and configurations that include up to 24 high-speed optical ports. To address growth in subscriber traffic, each model can increase capacity through software licenses. Figure 1-1 shows a front view of the T1100, the mid-range model of the T1000 Series.

Figure 1-1 T1000-Series Traffic Director

With extensive Layer 4 to 7 capabilities, the T1000 supports multiple policies for switching subscriber flows across Smart Capacity applications and platforms for security, legacy value-added services and emerging value-added services offered in conjunction with content partners. Mobile network planners can immediately add capacity without having to provision new hardware modules to scale traffic requirements.

This chapter provides an overview of the T1000 Traffic Director. It includes the following sections:

• “Traffic Director Architecture” on page 1-2

T-Series Traffic Director Installation, Configuration and Administration Guide 1-1

Chapter 1 Introduction

• “Product Capabilities” on page 1-4

• “Hardware Overview” on page 1-8

• “Common Hardware Features” on page 1-11

Traffic Director Architecture

The primary purpose of the Bytemobile T1000 Traffic Director is to provide L4 load balancing across multiple, parallel traffic-processing blades, such as OSNs in a Bytemobile Unison deployment. See Figure 1-2.

Figure 1-2 Architecture of Typical Unison Deployment with T1000

The Unison platform is typically placed inline within a carrier's network, with subscriber traffic being processed only by the OSNs (CSMs are responsible for management and control plane traffic). Each OSN has two interfaces on the data plane for redundancy. Subscriber-side and Internet-side traffic will be handled on separate VLANs.

The T1000 performs firewall load balancing (FWLB)

, to transparently load balance data plane traffic across OSNs in the direction of the Internet. Traffic passes through the OSNs and transparently maintains its Layer 3 information. The T1000 exposes a single IP address

1. The T1000 also supports server load balancing for deployments wh ere the Unison platform is not operating in a transparent mode (for example, as a WAP Gateway or with a NonInline architecture that employs optimization clients).

1-2 T-Series Traffic Director Installation, Configuration and Administration Guide

(or multiple, as necessary) as the destination for this traffic. The T1000 uses session persistency to ensure that traffic returning from the Internet is routed back to the same OSN

from which it originated. The T1000 performs its load balancing function across multiple ingress and egress VLANs.

HTTP-based health-checking ensures that traffic will not be routed to unavailable nodes. In the event of a full cluster failure, the T1000 can route traffic to a backup Internet path.

To ensure there is no single point of failure within the Unison cluster, Bytemobile suggests deploying two T1000s in an active/failover fashion. The T1000 provides redundancy support with both soft and hard failover. Soft failover events include scheduled maintenance or other reasons. For hard failover (caused by link or hardware failure), the T1000 redundancy mechanism ensures that service disruption is minimized and user experience is maintained.

Sizing a T1000/Unison Deployment

The T1000 Traffic Director is available in a range of hardware variations to support different processing and network connection needs. These include the T1010, T1100, and the T1200.

Each T1000 provides from 2 Gbps to 100 Gbps of non-blocking throughput (depending on hardware model). The end-to-end throughput of a T1 000 d eploymen t with U nison will be limited by the maximum capacity of a single application blade (OSN), which ranges from 400 Mbps when used to perform lossy media optimization, up to 1 Gbps if only lossless media and web-only optimizations are applied.

Traffic Director Architecture

The throughput measurement for a Unison cluster includes calculations for both ingress and egress traffic passing through the load balancer. In other words, data moving from the Internet to the subscriber must enter and exit the Unison cluster, traversing the T1000 twice. Therefore, if the Unison cluster replaces a router handling 10Gbps of throughput, the load balancer should be sized to handle 20 Gbps of through put.

A second sizing factor to consider is the number and type of data ports. The Unison data plane may employ port trunking to increase throughput; a two-port trunk configuration doubles the required number of T1000 ports on the subscriber and Internet sides. Support for the optional T2100 Content Accelerator (video cache) may also require additional ports. See “T1000 Hardware Specifications and Options” on page 1-6 for the available port configurations.

Sizing T1000/T3100 Deployments

The Bytemobile T3100 Adaptive Traffic Manager includes an integrated load-balancing function. When used in combination with T3100, the T1000 extends its advanced routing protocol support to the T3100 data plane. For example, when used with the T1000, th e T3100 can support routing protocols such as Open Shortest Path First (OSPF) and Border Gateway Protocol (BGP).

Sizing considerations for a T1000/T3100 deployment a re similar to a T1 000/Unison deployment.

T-Series Traffic Director Installation, Configuration and Administration Guide 1-3

Chapter 1 Introduction

Each T1000 provides from 2 Gbps to 100 Gbps of non-blocking throughput (depending on hardware model). The end-to-end throughput of a T1000 deployment with T3100 will be limited by the maximum capacity of a single application blade (ASM), which ranges from 400 Mbps when used to perform lossy media optimization, up to 1 Gbps if only lossless media and web-only optimizations are applied.

The throughput measurement for a T3100 cluster includes calculations for both ingress and egress traffic passing through the LIMs. In other words, data moving from the Internet to the subscriber must enter and exit the T3100, traversing the T1000 twice. Therefore, if the T3100 replaces a router handling 10Gbps of throughput, the T1000 should be sized to handle 20Gbps of throughput.

A second sizing factor to consider is the number and type of data ports. The T3100 data plane may employ port trunking to increase throughput; a two-port trunk configuration doubles the required number of T1000 ports on the subscriber and Internet sides. Support for the optional T2100 Content Accelerator (video cache) may also require additional ports. See “T1000 Hardware Specifications and Options” on page 1-6 for the available port configurations.

Product Capabilities

The T1000 combines a rich feature set with industrial-strength reliability, making it an optimal choice for mobile network load-balancing requirements.

Load Sensitive Traffic Distribution

An intelligent health check mechanism accurately determines when applications blades (such as Unison OSNs) are reaching specified thresholds. This innovative mechanism avoids the latency inherent in existing health check algorithms which predict server load or CPU utilization. As a result, the T1000 ensures subscriber traffic is directed to the right Unison OSN or T3100 application module, preventing packet loss and ensuring maximum availability of Smart Capacity applications.

Note: This feature is available in ByteMobile T3100 Release 7.0 and higher.

Intelligent Overload Protection

The T1000 determines which application blades are at or beyond a specified load threshold. It then limits traffic to these blades while maintaining active subscriber sessions on them. This capability enables the T1000 to manage traffic spikes effectively.

Carrier-Grade Redundancy

The T1000 can be configured redundantly, with state synchronization between two units to ensure that applications are always available. The platform is NEBS Level 3-compliant, with redundant fans and AC or DC power supplies.

1-4 T-Series Traffic Director Installation, Configuration and Administration Guide

High Performance

The T1000 supports the scaling of bi-directional subscriber traffic from 2 Gbps up to 100 Gbps. This enables operators to meet the most demanding core network capacity requirements and reduce the load balancer footprint required to scale Bytemobile Smart Capacity solutions. Depending on hardware model, capacity can be added incrementally through software key licenses. The configuration of multiple T1000 units in a virtual system provides linear scalability to hundreds of Gbps. This lowers capital and operating costs over the lifetime of the deployment, while ensuring the availability of capacity to meet subscriber demand.

Deployment Flexibility

• Layer 4 load balancing through Layer 7 content switching – The T1000 enables

operators to switch subscriber sessions among applications running inline on Bytemobile systems and applications running on other platforms for va lue-add ed services and security.

• IPv4/v6 networking - The T1000 allows in tegration of Bytemobile platforms with

IPv6 networks. It supports an IPv4/v6 dual stack and offers IPv6 network address translation (NAT) at scale.

Product Capabilities

• Standards-based networking – The T1000 supports industry-standard routing

protocols such as OSPF and BGP, as well as Layer 2 VLAN tagging, for ready integration with existing mobile packet core or data center environments.

T1000 Software Packages

Bytemobile offers the T1000 in standard and optional feature packages. These packages are offered in a software-based licensing configuration that does not require additiona l hardware modification. Refer to the following table.

Table 1-1 Standard and Optional Software Packages

Capability

L4 load balancing (see “Layer 4 to 7 Traffic

Management” on page 1-7)

L7 content switching (see “Layer 7 Content

Switching” on page 1-7)

NAT Yes Yes DoS attack defense Yes Yes IPv6 Support Yes Yes

Standard Package

Yes Yes

Advanced Package

Configuration and Management Yes Yes Dynamic routing Yes Yes L7 Content filtering Yes DNS Caching Yes Surge protection Yes

T-Series Traffic Director Installation, Configuration and Administration Guide 1-5

Chapter 1 Introduction

Standard

Capability

Package

SSL offload Yes AppExpert Rate Control Yes Web 2.0 Yes Priority Queuing Yes

T1000 Hardware Specifications and Options

The T1000 has the following standard and optional hardware configurations and specifications:

Table 1-2 Hardware Specifications

Specification T1010 T1100 T1200

Throughput Processor Intel E3-1275 Dual Intel X5680 Dual Intel X5680 Memory Data Plane Ports:

10GBASE-X SFP+

2 - 8 GBps 10 - 50 Gbps 40 - 100 Gbps

32 GB 48 GB 96 GB none

8 or 16

Advanced Package

Data Plane Ports:

6none12

1000BASE-X SFP Data Plane Ports:

1GB RJ-45

Management Plane Ports:

6 none none

122 10/100/1000BASE-T, RJ45

Lights-Out Management

1 (LOM) Ports: 10/100BASE-T, RJ-45

Transceiver Support

1GE SFP: SX, LX 10GE SFP+: (Refer to the NetScaler

documentation for a complete, build-specific list of supported transceivers.)

NEBS-Chassis Power Supplies

Yes

Dual

AC Power Specification • 100-240VAC

full range, 47-63 Hz

1GE SFP: SX, LX

SR, LR, DAC, 1GE Copper SFP

10GE SFP+:

SR, LR, DAC, 1GE Copper SFP

• 100-240VAC

full range, 47-63 Hz

• 100-240VAC

full range, 47-63 Hz

• 450w, 1536

BTU/Hr

1-6 T-Series Traffic Director Installation, Configuration and Administration Guide

• 850w, 2219

BTU/Hr

• TBD

Product Capabilities

Specification T1010 T1100 T1200

DC Power Specification

Height 1U 2U 2U Width Standard Rack Depth 24 in 28 in 28 in Weight 32 lbs (14.5 kg) 49 lbs (22.2 kg) 49 lbs (22.2 kg) Operating Temperature 0-40°C Allowed relative humidity 5%-95%, non-condensing Safety certification UL, TUV-C Electromagnetic FCC (Part 15 Class A),DoC, CE, VCCI, CNS, AN/NES Hazardous Substances RoHS

• -56.7 to -40

VDC

• 18A-9A

• 450w, 1536

BTU/Hr

T1000 Technical Specifications

The T1000 software offers the following standard and optional feature specifications.

• -56.7 to -40

VDC

• 18A-9A

• 850w, 2219

BTU/Hr

• -56.7 to -40

VDC

• TBD

Layer 4 to 7 Traffic Management

• Algorithms: Load-Sensitive Traffic Distribution, Round Robin, Least Packets, Least

Bandwidth, Least Connections, Response Time, Hashing (URL, Domain, Source IP, Destination IP, and Custom ID), SNMP-pro vided me tric

• Session persistence: Source IP, cookie, server, group, SSL session, Token-based,

JSESSIONID.

• Server monitoring: Ping, TCP, URL, ECV, scriptable health checks, Dynamic Server

Response Time.

• Link load balancing.

Layer 7 Content Switching

Policies: URL, URL Query, URL Wildcard, Domain, Source/Destination IP, HTTP Header, Custom, HTTP and TCP Payload Values, UDP.

Application Security

• DoS attack defense: Continue service to legitimate users while protecting against

attacks such as: SYN Flood, HTTP DoS and Ping of Death. ICMP and UDP rate control. HTTP and TCP session rate control.

• DNS: DNS proxy and caching. Authoritative DNS. DNS Signing.

T-Series Traffic Director Installation, Configuration and Administration Guide 1-7

Chapter 1 Introduction

• Network Address Translation (NAT): Source address NAT , destination address NAT,

User Interface

• Graphical application visualizer.

• Secure web-based GUI.

• CLI, Telnet, SSH, Console.

• Real-time performance dashboard.

Network Integration

• Layer 2 Routing:

IPv4/IPv6 NAT.

– Static routes, monitored static routes, weighted static routes – OSPF, RIP1/2, BGP – VLAN 802.1Q – Link Aggregation 802.3ad – IPv6/ IPv4 gateway

• High Availability – Active/Passive – Active/Active – VRRP – ECMP – Connection Mirroring

Hardware Overview

The following T1000 hardware models are presented here:

• Model T1010

• Model T1100

• Model T1200

1-8 T-Series Traffic Director Installation, Configuration and Administration Guide

Model T1010 Hardware

The T1010 front panel is shown in Figure 1-3, and the rear panel is shown in Figure 1-4.

Figure 1-3 T1010 Front Panel

Figure 1-4 T1010 Rear Panel

Hardware Overview

Each T1010 has front panel and back panel hardware components. The front panel has an LCD display with keypad, a lights-out management port (LOM), RS-232 console port, standard Ethernet management port, a set of six (6) 1G SFP data plane ports, and a set of six (6) 1G RJ45 Ethernet ports. The back panel provides access to the power supplies, fans, hard disk drives, and a USB port.

T-Series Traffic Director Installation, Configuration and Administration Guide 1-9

Chapter 1 Introduction

Model T1100 Hardware

The T1100 front panel is shown in Figure 1-5, and the rear panel is shown in Figure 1-6. The T1100 is available in two configurations: the first with eight SFP+ ports, and a second higher-capacity model with sixteen SFP+ ports.

Figure 1-5 T1100 Front Panel (8-Port and 16-Port Configurations)

Figure 1-6 T1100 Rear Panel

Each T1100 has front panel and back panel hardware components. The front panel has an LCD display with keypad, a lights-out management port (LOM), RS-232 console port, two Ethernet management ports, a set of eight (8) or sixteen (16) 10G SFP+ data plane ports. The back panel provides access to the power supplies, fans, hard disk drives, and a USB port.

1-10 T-Series Traffic Director Installation, Configuration and Administration Guide

Model T1200 Hardware

The T1200 front panel is shown in Figure 1-7, and the rear panel is shown in Figure 1-8.

Figure 1-7 T1200 Front Panel

Figure 1-8 T1200 Rear Panel

Common Hardware Features

Each T1200 has front panel and back panel hardware components. The front panel has an LCD display with keypad, a lights-out management port (LOM), RS-232 console port, two Ethernet management ports, a set of twelve (12) 1G SFP data plane ports and twenty-four (24) 10G SFP+ data plane ports. The back panel provides access to the power supplies, fans, hard disk drives, and a USB port.

Common Hardware Features

LCD Display

The LCD display on the front of every T1000 displays messages about the current operating status of the T1000. These messages communicate whether your T1000 has started properly and is operating normally. If the T1000 is not operating normally, the LCD displays troubleshooting messages.

The LCD displays real-time statistics, diagnostic information, and active alerts. The dimensions of the LCD limit the display to two lines of 16 characters each, causing the displayed information to flow through a sequence of screens. Each screen shows information about a specific function.

T-Series Traffic Director Installation, Configuration and Administration Guide 1-11

Chapter 1 Introduction

The LCD has a neon backlight. Normally, the backlight glows steadily. When there is an active alert, it blinks rapidly. If the alert information exceeds the LCD screen size, the backlight blinks at the beginning of each display screen. When the T1000 shuts down, the backlight remains on for one minute and then automatically turns off.

There are nine types of display screens on the LCD display. The first two screens in the following list, the booting screen and the startup screen, appear when your T1000 is starting up. The other screens, except the out-of-service screen, can appear while the T1000 is operating. They show configuration information, alerts, HTTP information, network traffic information, CPU load information, and port information for your T1000.

Booting Screen

The booting screen is displayed immediately after the T1000 is turned on. The first line displays the hardware platform, as shown in the following figure.

Figure 1-9 LCD Booting Screen

To view the model number from the command line, type show license. Scroll to the end of the command output to view the model number.

Startup Screen

The startup screen is displayed for a few seconds after the T1000 successfully begins operation. The first line displays the hardware platform, and the second line displays the software version and build number, as shown in the following figure.

Figure 1-10 LCD Startup Screen

Out-of-Service Screen

The out-of-service screen is displayed when the T1000 has undergone a controlled shutdown, as shown in the following figure.

1-12 T-Series Traffic Director Installation, Configuration and Administration Guide

Common Hardware Features

Figure 1-11 LCD Out-of-service Screen

Configuration Screen

The first line displays the T1000 status (STA, PRI, or SEC) and uptime. STA indicates that the T1000 is in standalone mode, PRI indicates that the T1000 is a primary node in a high availability (HA) pair, and SEC indicates that the T1000 is a secondary node in an HA pair. T1000 uptime is displayed in HH:MM format. The second line displays the IP address of the T1000, as shown in the following figure.

Figure 1-12 LCD Configuration Screen

Alert Screen

An unknown alert is displayed differently than a known alert, as shown in the following figures. In either case, the first line displays the T1000 status (STA, PRI, or SEC). STA indicates that the T1000 is in standalone mode, PRI indicates that the T1000 is a primary node in a high availability (HA) pair, and SEC indicates that the T1000 is a secondary node in an HA pair. The second line displays the IP address of the T1000.

Figure 1-13 LCD Known Alert Screen

Figure 1-14 LCD Unknown Alert Screen

T-Series Traffic Director Installation, Configuration and Administration Guide 1-13

Chapter 1 Introduction

HTTP Statistics Screen.

The first line displays the rate of HTTP GETS per second. The second line displays the rate of HTTP POSTS per second, as shown in the following figure.

Figure 1-15 LCD HTTP Statistics Screen

Network Traffic Statistics Screen.

The first line displays the rate at which data is received, in megabits per second. The second line displays the rate of data transmission, in megabits per second, as shown in the following figure.

Figure 1-16 LCD Network Traffic Statistics Screen

CPU Load, Memory, and Connections Screen

The first line displays CPU utilization and memory utilization as percentages. The second line displays the ratio of the number of server connections to the number of client connections.

Note: If the number of server or client connections exceeds 99,999, the number is

displayed in thousands, indicated by the letter K.

Figure 1-17 LCD CPU Load, Memory, and Connections Screen

Port Information Screen

The S row displays port speed, flow control, and duplex information. The R row displays megabits received per second on the interface. The first port in each row is the management port.

1-14 T-Series Traffic Director Installation, Configuration and Administration Guide

Common Hardware Features

Figure 1-18 Port Information

The following table defines the various abbreviations and symbols that appear in the S row of the port information screen.

Table 1-3 Port Abbreviations and Symbols for S Row

S row abbreviation/symbol Indicates

A rate of 10 megabits per second, full duplex mode, and flow control OFF.

A rate of 100 megabits per second, full duplex mode, and flow control OFF.

A rate of 1 gigabit per second, full duplex mode, and flow control OFF.

A rate of 10 gigabits per second, full duplex mode, and flow control OFF.

A disconnected port.

NOTE: The R row does not display

an abbreviation or symbol for a disconnected port.

Receive flow control regardless of speed or duplex mode.

Transmit flow control regardless of speed or duplex mode.

Receive and transmit flow control regardless of speed or duplex mode.

A rate of 10 megabits per second, half duplex mode, and flow control OFF.

T-Series Traffic Director Installation, Configuration and Administration Guide 1-15

Chapter 1 Introduction

The following table defines the various abbreviations and symbols that appear in the R row of the port information screen.

Table 1-4 Port Abbreviations and Symbols for R Row

S row abbreviation/symbol Indicates

A rate of 100 megabits per second, half duplex mode, and flow control OFF.

A rate of 1 gigabit per second, half duplex mode, and flow control OFF.

R row abbreviation/symbol Indicates

The port is disabled.

Ports

Receive speed is about 10% of line speed.

Receive speed is about 50% of line speed.

Receive speed is about 75% of line speed.

Receive speed is about 100% of line speed.

Ports are used to connect the T1000 to external devices. All models of T1000 support RS232 serial ports and 10/100/1000Base-T copper Ethernet ports for management plane connections. Depending on the model, the T1000 supports one or more of the following: 10/100/1000Base-T copper Ethernet ports, 1-gigabit SFP ports, or 10-gigabit SFP+ ports

RS232 Serial Port

The RS232 serial console port on the front panel of the T1000 provides a connection between the T1000 and a computer, allowing direct access to the T1000 for initial configuration or troubleshooting.

All hardware platforms ship with an appropriate serial cable used to connect your computer to the T1000.

1-16 T-Series Traffic Director Installation, Configuration and Administration Guide

Common Hardware Features

Management Ports

Management ports are standard copper Ethernet ports (RJ45) that are used for direct access to the T1000 for system administration functions. These are type 10/100/1000BASE-T . This port has a maximum transmission speed of 1 gigabit per second. To connect any of these ports to your network, plug one end of a standard Ethernet cable into the port and plug the other end into the appropriate network conn ector.

1 Gbps SFP Ports

The SFP ports are high-speed ports that can operate at speeds up to 1 Gbps. You need an appropriate SFP transceiver to connect to these ports, allowing the use of either fiber or copper cables.

Refer to the Product Specifications and the NetScaler documentation for a build-specific list of supported transceivers and cable types.

10 Gbps SFP+ Ports

The SFP+ ports are high-speed ports that can operate at speeds of 10 Gbps. You need an appropriate SFP+ transceiver to connect to these ports, allowing the use of either fiber or copper cables. If the other end of the cable is attached to a 1GE SFP port, the 10GE SFP+ port automatically negotiates to match the speed of the 1GE SFP port.

Refer to the Product Specifications and the NetScaler documentation for a build-specific list of supported transceivers and cable types.

Port Status Indicators

The port LEDs show whether the link is established and traffic is flowing through the port. The following table describes the LED indicators for each port. There are two LED indicators for each port type.

T-Series Traffic Director Installation, Configuration and Administration Guide 1-17

Chapter 1 Introduction

Table 1-5 LED Port Status Indicators

Port Type

SFP (1 Gbps) and SFP+ (10 Gbps)

LED Location

Left Link/

LED Function LED Color

Off No link.

LED Indicates

Activity

Solid green Link is

established but no traffic is passing through the port.

Blinking green

Traffic is passing through the port.

Right Speed Off No

connection.

Solid green Traffic rate of

10 gigabits per second.

1-18 T-Series Traffic Director Installation, Configuration and Administration Guide

Common Hardware Features

Port Type

Management (RJ45)

LED Location

LED Function LED Color

LED Indicates

Left Speed Off No

connection, or a traffic rate of 10 megabits per second (Mbps).

Green Traffic rate of

100 Mbps.

Amber Traf fic rate of

1 gigabit per second.

Right Link/

Off No link.

Activity

Solid yellow Link is

established but no traffic is passing through the port.

Blinking yellow

Traffic is passing through the port.

Power Supply

The T1000 ships with a dual power supply, configured for either AC or DC power. The AC configuration includes two standard power cords that each have a NEMA 5-15 plug for connecting to the power outlet on the rack or in the wall.

For power-supply specifications, see “T1000 Hardware Specifications and Options” on page 1-6, which describes the various platforms and includes a table summarizing the hardware specifications.

Note: If you suspect that a power-supply fan is not working, please see the description

of your platform. On some platforms, what appears to be the fan does not turn, and the actual fan turns only when necessary.

For each power supply, a bi-color LED indicator shows the condition of the power supply.

T-Series Traffic Director Installation, Configuration and Administration Guide 1-19

Chapter 1 Introduction

Table 1-6 LED Power Supply Indicators

Power Supply Type LED Color LED Indicates

AC OFF No power to any power

supply.

Flashing RED No power to this power

supply.

Flashing GREEN Power supply is in

standby mode.

GREEN Power supply is

functional.

RED Power supply failure.

DC OFF No power to any power

supply.

Flashing RED No power to this power

supply.

Compact Flash Card

The CompactFlash card contains the operating system. CompactFlash is mounted as /flash.

Solid-State Drive

The solid-state drive contains the operating system. It is mounted as /flash. On certain systems, the solid-state drive replaces the hard-disk drive.

Hard Disk Drive

The hard disk drive contains logs and other data file s such as user data. On certain systems, a 128 GB solid-state drive replaces the HDD. Both types of drive have the same functionality and support the same software releases. It is mounted as /var.

Flashing BLUE Power supply is in

standby mode.

BLUE Power supply is

functional.

RED Power supply failure.

1-20 T-Series Traffic Director Installation, Configuration and Administration Guide

2. Installation

Installing the T1000

This T1000 installation procedure begins with an overview of the installation process and continues with safety information, racking instructions, network and power connection, and finally initial configuration. It has the following sections:

• Overview of Installing T1000

• Cautions and Warnings

• Preparing for Installation

• Handling Static-Sensitive Devices

• Unpacking the Shipping Container

• Rack Mounting the T1000

• Making Data Plane Connections

• Making Management Connections

• Connecting and Disconnecting AC Power

• Connecting and Disconnecting DC Power

• Accessing and Configuring the Management Plane

• Accessing and Configuring the LOM Port

Note: The T1000 is a series of hardware platforms that includes the T1010, T1100 and

T1200. This manual uses the generic term “T1000” to refer to all hardware models of the T1000 Traffic Director, including the T1010, T1100, and T1200. Specific model names are used only when necessary.

Overview of Installing T1000

This section provides a high-level overview of the T1000 installation procedure. If you have previously installed T1000 systems, use the following steps as a guideline. If you have not installed a T1000 before, read the steps in detail before performing the installation procedures.

Step 1 Review “Cautions and Warnings” on page 2-2.

T-Series Traffic Director Installation, Configuration and Administration Guide 2-1

Chapter 2 Installing the T1000

Step 2 Review the site requirements and shipment contents. See “Preparing for Installation” on

page 2-4

Step 3 Unpack the shipping container. See “Unpacking the Shipping Container” on page 2-7. Step 4 Rack-mount the T1000. See “Rack Mounting the T1000” on page 2-8. Step 5 Connect cables. These cabling steps may be performed in any order (depending on

deployment schedule):

a. Connect data cables between the T1000 and the adjacent network device(s). See “Making

Data Plane Connections” on page 2-11.

b. Connect the management plane of the T1000 to operator’s management network. See

“Making Management Connections” on page 2-18. Local management may also be

performed from a console connection, which is also performed in this step.

c. See “Connecting and Disconnecting AC Power” on page 2-19 or “Connecting and

Disconnecting DC Power” on page 2-22.

Step 6 Perform the initial setup and configuration. See “Accessing and Configuring the

Management Plane” on page 2-29.

Step 7 Support users may configure and use the LOM port. See “Accessing and Configuring the

LOM Port” on page 2-31.

Cautions and Warnings

Electrical Safety Precautions

Basic electrical safety precautions should be followed to protect yourself from harm and the T1000 from damage.

• Be aware of the location of the emergency power off (EPO) switch so that if an

electrical accident occurs, you can quickly remove power to the T1000.

• Remove all jewelry and other metal objects that might come into contact with power

sources or wires before installing or repairing the T1000. When you touch both a live power source or wire and ground, any metal objects can heat up rapidly, and may cause burns, set clothing on fire, or fuse the metal object to an exposed terminal.

• Use a regulating uninterruptible power supply (UPS) to protect the T1000 from

power surges and voltage spikes, and to keep the T1000 operating in case of power failure.

• Never stack the T1000 on top of any other server or electronic equipment.

• All T1000s are designed to be installed on power systems that use TN earthing. Do

not install your device on a power system that uses either TT or IT earthing.

• Make sure that the T1000 has a direct physical connection to the earth during normal

use. When installing or repairing an T1000, always make sure that the ground circuit is connected first and disconnected last.

• Make sure that a fuse or circuit breaker no larger than 120 VAC, 15 A U.S. (240

VAC, 16 A internatio nal) is used on all current-ca rrying conductors on the p ower system to which your T1000s are connected.

2-2 T-Series Traffic Director Installation, Configuration and Administration Guide

Cautions and Warnings

• Do not work alone when working with high voltage components.

• Always disconnect the T1000 from power before removing or installing any

component. When disconnecting power, you should first shut down the T1000 and then unplug the power cords of all the power supply units connected to the T1000. As long as the power cord is plugged in, line voltages may be present in the power supply, even when the power switch is OFF.

• Do not use mats designed to decrease static electrical discharge as protection from

electrical shock. Instead, use rubber mats that have been specifically designed as electrical insulators.

• Make sure that the power source can handle the T1000's maximum power

consumption rating with no danger of an overload. Always unplug any T1000 before performing repairs or upgrades.

• Do not overload the wiring in your server cabinet or on your server room rack.

• During thunderstorms, or anticipated thunderstorms, avoid performing any hardware

repairs or upgrades until the danger of lightning has passed.

• When you dispose of an old T1000 or any components, follow any local and national

laws on disposal of electronic waste.

• To prevent possible explosions, replace expired batteries with the same model or a

manufacturer-recommended substitute and follow the manufacturer’ s instructions on battery replacement.

• Never remove a power supply cover or any sealed part that has the following label:

T1000 Precautions

• Determine the placement of each component in the rack before you install the rail.

• Install the heaviest component first at the bottom of the rack, and then work upward.

Distribute the load on the rack evenly. An unbalanced rack is hazardous.

• Allow the power supply units to cool before touching them.

• Install the equipment near a socket outlet for easy access.

• Mount equipment into a rack with sufficient airflow for safe operation.

• For a closed or multi-unit rack assembly, the ambient operating temperature of the

rack environment may be greater than the ambient temperature of the room. Therefore, consider the lowest and highest operating temperatures of the equipment when making a decision about where to install the T1000 in the rack.

T-Series Traffic Director Installation, Configuration and Administration Guide 2-3

Chapter 2 Installing the T1000

Rack Precautions

• Make sure that the leveling jacks on the bottom of the rack are fully extended to the

floor, with the full weight of the rack resting on them.

• For a single-rack installation, attach a stabilizer to the rack.

• For a multiple-rack installation, couple (attach) the racks together.

• The handles on the left and right of the front panel of the T1000 should only be used

for extending the T1000 out of the rack. These handles should not be used for mounting the T1000 on the rack. Rack-rail hardware described later should be used instead.

Preparing for Installation

Note: The site should have been selected and prepared already by working with a

Bytemobile deployment engineer. This guide only reviews the site requirements.

Install the T1000 in a location that meets the requirements outlined in this section:

• Site Requirements

• System Reliability Guidelines

• Power Requirements

Site Requirements

Caution TO BE INSTALLED ONLY IN RESTRICTED ACCESS AREAS.

(Dedicated Equipment Rooms, Equipment Closets, or the like) in accordance with Articles 110-16, 110-17, and 110-18 of the National Electrical Codes, ANSI/NFPS No.70.

The T1000 must be installed in an area that meets the following requirements:

• See the environmental specifications defined in the T1000 spec ifications document.

The site should have an air conditioner, preferably a dedicated computer room air conditioner (CRAC), capable of maintaining the cabinet or server room at a temperature of no more than 21 degrees C/70 degrees F at altitudes up to 2100 m/7000 ft, or 15 degrees C/60 degrees F at higher altitudes, a humidity level no greater than 45 percent, and a dust-free environment.

• Two AC or DC (depending on shelf type) power sources within 2 meters

(approximately 6.6 feet). Wiring should be capable of handling at least 4,000 watts per rack unit in addition to power needs for the CRAC.

• The rack in which the T1000 will be installed must be groun ded (preferabl y to a

protective earth ground).

2-4 T-Series Traffic Director Installation, Configuration and Administration Guide

• For proper ventilation, install the T1000 in a rack that has an open back.

• A T1010 weighs 14.5 kg (3 2 lb), a T1100 weighs 22 kg (49 lb), and a T1200 weig hs

38.5 kg (85 lb). Observe the following precautions and guidelines (particularly if your rack has an open back or open sides):

– Before attempting to rack-mount, first make sure the selected rack can support at

least three times the weight of the T1000.

– Bolt the rack to the floor and brace the top of the rack to the wall. – Provide sufficient vertical space in the rack before beginning the installation of the

T1000.

• Provide a minimum of 609 mm (24 inches) of space behind the rack for system

maintenance.

• Install patch panels and cable management brackets in the rack for easier cable

management.

System Reliability Guidelines

To help ensure proper system cooling and system reliability, make sure that the following requirements are met:

Preparing for Installation

• Each of the power-supply bays has a power supply installed in it.

• There is adequate space around the T1000 to allow the cooling system to work

properly. Leave approximately 50 mm (2.0 in.) of open space around the front and rear. Do not place objects directly in front of or behind the unit.

Power Requirements

The T1000 system provides two separate AC or DC power connections on the rear panel. Each side should be attached to a separate power circuit to provide maximum power fault tolerance.

Shipment Contents

The T1000 system is shipped in a single container. The complete system has been tested to ensure that all components are operational.

The shipping container will include the following:

• Fully-tested T1000 with installed components.

• One RJ-45 to DB-9 adapter.

• One 6 ft RJ-45/DB-9 cable.

• The AC Power T1010 and T1100 will include (2x) power cables. The AC Power

T1200 will include (4x) power cables.

• DC power models will include no power cables. Power cables must be supplied by

customer.

• One mounting rail kit.

T-Series Traffic Director Installation, Configuration and Administration Guide 2-5

Chapter 2 Installing the T1000

Items Provided by Customer

In addition to the items included in the box with your new T1000, you will need the following items to complete the installation and initial configuration process.

• Network cables and SFP transceiver modules for each port you will connect to your

network.

• One available network port on your network switch or hub for each T1000 network

port you want to connect.

Note: Transceiver modules are sold separately. Refer to the Product Specifications and

the Citrix NetScaler documentation for a build-specific list of supported transceivers and cable types.

Contact your Bytemobile sales representative to order transceiver modules for your T1000.

• A computer to serve as a management workstation

Handling Static-Sensitive Devices

Attention: Static electricity can damage electronic devices. To avoid damage, keep

static-sensitive devices in their static-protective packages until you are ready to install them.

ESD is the release of stored static electricity that can damage electronic circuits. Static electricity is often stored in your body and discharged when you come in contact with an object with a different potential. An ESD wrist strap safely channels the electricity from your body to a proper ground (such as the T1000 unit).

Use an ESD wrist strap whenever you are working on the T1000 unit, especially when you handle modules other devices. To work properly, the wrist strap must have good contact at both ends (touching your skin at one end and connected to the ESD connector on the front or back of the T1000 unit). To reduce the possibility of electrostatic discharge, observe the following precautions:

• Limit your movement. Movement can cause static electricity to build up around you.

• Handle the device carefully, holding it by its edges or its frame.

• Do not touch solder joints, pins, or exposed circuitry.

• Do not leave the device where others can handle and damage it.

• While the device is still in its static-protective package, touch it to an unpainted

metal part of the T1000 unit for at least 2 seconds. This drains static electricity from the package and from your body.

2-6 T-Series Traffic Director Installation, Configuration and Administration Guide

• Remove the device from its package and install it directly into the T1000 unit

without setting down the device. If it is necessary to set down the device, place it back into its static-protective package. Do not place the device on the T1000 unit or on a metal surface.

• Take additional care when you handle devices during cold weather. Heating reduces

indoor humidity and increases static electricity.

Unpacking the Shipping Container

The T1000 shipping container is designed for easy system removal. Follow the steps described below.

Step 1 Move the shipping container as close as possible to final operating location. Step 2 Cut the strapping around the box with a pair of scissors or other sharp instrument. Be careful

not to pierce the cardboard.

Step 3 Remove the T1000 from the styrofoam pac king material and plastic bag. Locate the

accessory package inside the container and set aside.

Step 4 Ensure the racking system has been installed as described in “Rack Mounting the T1000” on

page 2-8.

Unpacking the Shipping Container

Step 5 Lift the T1000 shelf into place on the rack. Use the following guidel ines whenever you lift

the T1000:

• Two or more people are recommended for lifting the unit.

• Ensure that your footing is solid. Balance the weight of the unit between your feet.

• Lift the T1000 slowly — never move suddenly or twist your body as you lift.

• Keep your back straight and lift with your legs, not your back. If you must bend

down to lift the shelf, bend at the knees, not at the waist, to reduce the strain on your lower back.

• Avoid gripping connectors or switches when lifting.

Step 6 Complete the rack mounting procedure described in “Rack Mounting the T1000” on

page 2-8.

Step 7 Place all packing materials in the shipp ing box and store the box for po ssible future use.

T-Series Traffic Director Installation, Configuration and Administration Guide 2-7

Chapter 2 Installing the T1000

Rack Mounting the T1000

The T1000 can be installed in standard server racks that conform to EIA-310-D specification. The T1000 ships with a set of rails, which you must install before you mount the T1000. The only tools that you need for installing a T1000 are a Phillips screwdriver and a flathead screwdriver.

Each T1000 ships with a mounting rail kit that contains two rail assemblies, one for the left side and the other for the right side of the T1000, and screws to attach the rails. An assembly consists of an inner rail and a rack rail.

Note: The same rail kit is used for both square-hole and round-hole racks. There are

specific instructions for threaded, round-hole racks, described below.

Perform the following tasks to mount the T1000:

• Remove the inner rails from the rail assembly.

• Attach the inner rails to the T1000.

• Install the rack rails on the rack.

• Install the T1000 in the rack.

Before beginning the rack mounting procedure, review “Cautions and Warnings” on page 2-2.

Removing the Inner Rails from the Rail Assembly

Step 1 Place the rail assembly on a flat surface. Step 2 Slide out the inner rail toward the front of the assembly. Step 3 Depress the latch until the inner rail comes all the way out of the rail assembly. Step 4 Repeat steps 1 through 3 to remove the second inner rail.

Attaching the Inner Rails to the T1000

Step 1 Position the right inner rail behind the handle on the right side of the T1000. Step 2 Align the holes on the rail with the corresponding holes on the side of the T1000. Step 3 Attach the rail to the T1000 with the provided screws: 5 per side as shown in the following

figure.

Note: The following figure shows the T1100 hardware model. Procedure and rail

location are similar for T1010 and T1200 models.

2-8 T-Series Traffic Director Installation, Configuration and Administration Guide

Figure 2-1 Attaching Inner Rails

Rack Mounting the T1000

Step 4

Repeat steps 1 through 3 to install the left inner rail on the other side of the T1000.

Installing the Rack Rails on the Rack

Step 1 If you have a round-hole, threaded rack, skip to step 3. Step 2 Install square nut retainers into the front post and back post of the rack as shown in the

following figures. Before inserting a screw, be sure to align the square nut with the correct holes. The three holes are not evenly spaced.

Figure 2-2 Installing Retainers into the Rack Posts

Step 3

T-Series Traffic Director Installation, Configuration and Administration Guide 2-9

Install the adjustable rail assembly into the rack as shown in the following figures. Use a screw to lock the rear rail flange into the rack. With the screw securing the rail in place, you can optionally remove the latching spring.

Chapter 2 Installing the T1000

For round-hold, threaded racks, remove the studs and discard. Secure the rail to the rack by using the flathead screws that were holding the studs in place. For square-hole and round-hole non-threaded racks, insert studs into hole in the rear of the rack.

Figure 2-3 Installing the Rail Assembly to the Rack

Installing the T1000 in the Rack

Step 1 Align the in ner rail s, attached to the T1000, with the rack rails. Step 2 Slide the T1000 into the rack rails, keeping the pressure even on both sides. Step 3 Verify that the T1000 is locked in place by pulling it forward out of the rack.

Note: The following figure shows the T1100 hardware model. Procedure and rail

location are similar for T1010 and T1200 models.

2-10 T-Series Traffic Director Installation, Configuration and Administration Guide

Figure 2-4 Rack Mounting the T1000

Making Data Plane Connections

The T1000 has a set of of RJ45, SFP, and/or SFP+ ports that are used to connect the T1000 data plane to intermediate switches. Refer to the following table and figure:

Ports T1010 T1100 T1200

Data Plane Ports: 1G RJ45 Data Plane Ports:

1000BASE-X SFP Data Plane Ports:

10GBASE-X SFP+

6 none none 6none12

none

8 or 16

T-Series Traffic Director Installation, Configuration and Administration Guide 2-11

Chapter 2 Installing the T1000

Figure 2-5 Data Plane Ports for T1010, T1100 and T1200

T1010

6 RJ45 Ports 6 SFP Ports

T1100

8 SFP+ Ports

T1100 Extended

16 SFP+ Ports

RJ45 RJ45 RJ45 RJ45 RJ45 RJ45

SFP

SFP SFP SFP SFP SFP

10/1

10/2 10/3 10/4

SFP+

10/5 10/6 10/7 10/8

10/3

10/2

10/1

SFP+

10/7

10/6

10/5

SFP+

10/11

10/10

10/9

10/15

10/14

10/13

SFP+

10/4

10/8

10/11

10/16

SFP

SFP+

SFP

SFP+

10/17 10/18 10/19 10/20

SFP+

10/21 10/22 10/23 10/24

T1200

12 SFP Ports 24 SFP+ Ports

SFP

SFP+

SFP

SFP+

1/1

1/5

1/9

10/1

10/5

10/9

1/2

1/6

1/10

10/2

1/3

1/7

1/4

1/11

1/8

1/12

10/3 10/4

10/6 10/7 10/8

10/10 10/11 10/12

10/13 10/14 10/15 10/16

SFP and SFP+ accommodate multiple connection types. See figure below.

Note: Transceiver modules are sold separately. Refer to the Product Specifications and

the Citrix NetScaler documentation for a build-specific list of supported transceivers and cable types.

Contact your Bytemobile sales representative to order transceiver modules for your T1000.

2-12 T-Series Traffic Director Installation, Configuration and Administration Guide

Making Data Plane Connections

Protective Cap

Fiber Optic Cable

Remove Plugs

Optical Transceiver

Installing a Optical Transceiver and Fiber Optic Cable

Ethernet Transceiver

RJ-45 Ethernet Cable

Wire Handle

Installing Ethernet Transceiver and RJ-45 Cable

Direct Attach Cable

Release T ab

Installing a Direct Attach Cable

Wire Handle

Port

Figure 2-6 Making Network Connections to the SFP/SFP+ Ports

The following connections to the T1000 SFP+ data plane ports are supported (depending on model):

• 10 Gb Ethernet over fiber optic cables. Requires one 10 Gb SFP+ transceiver module

per port. Distances up to 10 km are supported.

• 1 Gb Ethernet over copper cables. Requires one 1 Gb SFP transceiver module per

port. Distances up to 100 m using category 5 twisted-pair copper cabling.

• 10 Gb Ethernet via SFP+ direct-attach cable (DAC). No transceiver module required.

Distances up to 5 m supported.

The following connections to the T1000 SFP data plane ports are supported (depending on model):

• 1 Gb Ethernet over copper cables. Requires one 1 Gb SFP transceiver module per

port. Distances up to 100 m using category 5 twisted-pair copper cabling.

The following topics describe how to install and remove connections for each of the cable types.

• “SFP/SFP+ Port and Cable Installation Guidelines” on page 2-14

• “Using a Direct-Attach Cable” on page 2-14

• “Using a Fiber Cable and Transceiver” on page 2-15

• “Using an Ethernet Cable and Transceiver” on page 2-16

T-Series Traffic Director Installation, Configuration and Administration Guide 2-13

Chapter 2 Installing the T1000

SFP/SFP+ Port and Cable Installation Guidelines

Before installing or removing network connections on the T1000 SFP and/or SFP+ ports, note the following:

Attention: Static electricity can damage the T1000 unit and associated devices. To avoid

damage, keep static-sensitive devices in their static-protective packages until you are ready to install them.

• To reduce the possibility of electrostatic discharge, observe the following

precautions:

– Handle the device carefully, holding it by its edges or its frame. Do not touch solder

joints, pins, or exposed printed circuitry. Do not leave the device where others can handle and damage it.

– While the device is still in its static-protective package, touch it to an unpainted

metal surface of the T1000 or an unpainted metal surface on any other grounded rack component in the rack that you are installing the device in for at least 2 seconds. This drains static electricity from the package and from your body.

– Remove the device from its package and install it directly into the T1000 without

setting down the device. If it is necessary to set down the device, put it back into its static-protective package. Do not place the device on the T1000 or on a metal surface.

– Take additional care when you handle devices during cold weather. Heating reduces

indoor humidity and increases static electricity.

• SFP components have an integral guide key that is designed to prevent you from

inserting the modules and connectors incorrectly.

• Use minimal pressure when you insert the module into the port. Forcing the module

into the port can cause damage to the module or the module port.

• You must first insert the transceivers into the SFP ports before connecting cables to

the transceivers.

• You must remove cables from the transceivers before you remove the transceivers

from the SFP ports.

Using a Direct-Attach Cable

The direct attach cable (DAC) is a hot-pluggable unit, meaning that it can be installed and removed at any time while the T1000 is operational. No transceivers are necessary.

To install the DAC, complete the following steps:

Step 1 Review the guidelines in “SFP/SFP+ Port and Cable Installation Guidelines” on page 2-14. Step 2 Remove the protective cap from the SFP port on the T1000, and store the cap in a safe place. Step 3 Touch the static-protective package that contains the DAC to an unpainted metal surface of

the shelf or an unpainted metal surface on any other grounded rack component in the rack in which you are installing the DAC for at least 2 seconds.

Step 4 Remove the DAC from its static-protective pac kage and store the p ackage in a safe place.

2-14 T-Series Traffic Director Installation, Configuration and Administration Guide

Making Data Plane Connections

Step 5 Insert the DAC connector into the SFP port until it clicks into place. See Figure 2-6. To

avoid damage to DAC, follow these guidelines:

• Leave enough slack in the cable so that it does not bend to a radius of less than 25

mm (1 in.) when components or cables are moved or shifted.

• Route the cable away from places where it can be snagged by other devices in the

rack.

• Do not overtighten the cable straps or bend the cables to a radius of less than 25 mm

(1 in.).

• Do not put excess weight on the cable at the connection point. Make sure that the

cable is well supported.

To remove the DAC, complete the following steps:

Step 1 Grasp the release tab on the DAC and gently pull the DAC from the port. Step 2 Protect the unconnected end of the DAC, or the entire DAC, by placing it in a sta tic

protective package.

Step 3 Replace the protective cap on the SFP port.

Using a Fiber Cable and Transceiver

The fiber transceiver module is a hot-pluggable unit, meaning that it can be installed and removed at any time while the unit is operational. The module provides two fiber-optic cable connectors for connecting to external ports.

Danger:

Fiber Optic Hazardous Radiation (Fiber Optic Statement 1) Fiber optic products use laser radiation with the potential to cause injury. Uncovered ports may release this radiation. Avoid direct exposure to laser radiation. Do not stare into the beam, and do not view directly with optical instruments. Do not remove any protective shields on fiber optic transceiver modules.

To install the module and cables, complete the following steps:

metal surface of the shelf or an unpainted metal surface on any other grounded rack component in the rack in which you are installing the module for at least 2 seconds.

Step 4 Remove the transceiver module from its static-protective package and store the package in a

safe place.

T-Series Traffic Director Installation, Configuration and Administration Guide 2-15

Chapter 2 Installing the T1000

Step 5 Insert the transceiver module into the SFP por t until it clicks into place. See Figure 2-6. Step 6 Remove the protective caps from the end of the fiber optic cable. Step 7 Gently slide the fiber optic cable into the port on transceiver module until it clic ks into

place. See Figure 2-6. To avoid damage to fiber optic cables, follow these guidelines:

• Do not route the cable along a folding cable-management arm.

• Leave enough slack in the cable so that it does not bend to a radius of less than 38

mm (1.5 in.) when components or cables are moved or shifted.

• Route the cable away from places where it can be snagged by other devices in the

rack.

• Do not overtighten the cable straps or bend the cables to a radius of less than 38 mm

(1.5 in.).

• Do not put excess weight on the cable at the connection point. Make sure that the

cable is well supported.

To remove the module and cables, complete the following steps:

Step 1 Squeeze the release tabs and gently pull the fiber optic cable from the transceiver module. Step 2 Replace the protective caps on the ends of the fiber optic cable. Step 3 Unlock the transceiver module by pu lling the wire h and le straight ou t. Step 4 Grasp the wire handle and pull the transceiver module out of the port. Step 5 Replace the protective caps on the transceiver module and the SFP port. Step 6 Place the transceiver module in to a static-protective package.

Using an Ethernet Cable and Transceiver

The Ethernet transceiver module is a hot-pluggable unit, meaning that it can be installed and removed at any time while the unit is operational. The module provides a standard RJ-45 port.

To install the module and cables, complete the following steps:

metal surface of the shelf or an unpainted metal surface on any other grounded rack component in the rack in which you are installing the module for at least 2 seconds.

Step 4 Remove the transceiver module from its static-protective package and store the package in a

safe place.

Step 5 Insert the transceiver module into the SFP por t until it clicks into place. See Figure 2-6.

2-16 T-Series Traffic Director Installation, Configuration and Administration Guide

Making Data Plane Connections

Step 6 Insert the RJ-45 Ethernet cable into the port on the transc eiver module. See Figure 2-6.

To remove the module and cables, complete the following steps:

Step 1 Squeeze the release tab on the Ethernet cable an d gently pull the cable from the transceiver

module.

Step 2 Unlock the transceiver module by pulling the wire handle straight ou t. Step 3 Grasp the wire handle and pull the transceiver module out of the port. Step 4 Place the transceiver module into a static-prote ctive package.

T-Series Traffic Director Installation, Configuration and Administration Guide 2-17

Chapter 2 Installing the T1000

Making Management Connections

Use the following procedures to connect the T1000 to management functions.

Connecting the Management Plane

Step 1 Insert the RJ-45 connector on one end of your Ethernet cable into one of the managemen t

plane ports on the front panel of the T1000, as shown in Figure 2-7.

Figure 2-7 Management Connections

Step 2 Step 3 Verify that the LED glows amber when the connection is established. See “Accessing and

Insert the RJ-45 connector on the other end into the target device, such as a router or switch.

Configuring the Management Plane” on page 2-29 for procedures to make access and

configure the management ports.

Connecting the Console Cable

You can use the console cable to connect your T1000 to a computer or terminal, from which you can configure the T1000. Alternatively, you can use a computer connected to the network. Before connecting the console cable, configure the computer or terminal to support

2-18 T-Series Traffic Director Installation, Configuration and Administration Guide

Connecting and Disconnecting AC Power

VT100 terminal emulation, 9600 baud, 8 data bits, 1 stop bit, parity, and flow control set to NONE. Then connect one end of the console cable to the RS232 serial port on the T1000 and the other end to the computer or terminal.

Step 1 Insert the DB-9 connector at the end of the cable into the console port that is located on the

front panel of the T1000 as shown in Figure 2-7.

Step 2 To use a cable with an RJ-45 converter, insert the optional converter provided into the

console port and attach the cable to it.

Step 3 Insert the RJ-45 connector at the other end of the cable into the serial port of the computer or

terminal.

Connecting the LOM Port

The T1000 includes a lights-out management (LOM) port that is used for support purposes.

Step 1 Insert the RJ-45 connector on one end of your Ethern et cable into o ne of th e LOM port o n

the front panel of the T1000, as shown in Figure 2-7.

Step 2 Insert the RJ-45 connector on the other end into the target device, such as a router or switch. Step 3 By design, the LOM port does not have LEDs to verify connectivity. You must verify the

connection using a terminal device. See “Accessing and Configuring the LOM Port” on page 2-31.

Connecting and Disconnecting AC Power

This section describes how to connect and disconnect power to a T1000 configured with AC power. This section has the following topics:

• “Before you Begin AC Power Connection” on page 2-19

• “Connecting an AC Shelf to Power” on page 2-21

• “Turning On AC Power to the System” on page 2-22

• “Turning Off AC Power to the System” on page 2-22

For procedures related to DC power, see “Connecting and Disconnecting DC Power” on page 2-22.

Note: The T1000 includes two power supplies, but fu nction s pro perly with a sing le

power supply. Bytemobile recommends connecting both power supplies (to independent power sources) for redundancy.

Before you Begin AC Power Connection

Before you begin the power connection/disconnection proced ures, note the follo wing:

• Review the safety warnings at the beginning of this document, and below.

T-Series Traffic Director Installation, Configuration and Administration Guide 2-19

Chapter 2 Installing the T1000

• Review the electrostatic discharge (ESD) guidelines in “Handling Static-Sensitive

Devices” on page 2-6.

• Review the AC power specifications in “T1000 Hardware Specifications and

Options” on page 1-6

• The T1000 unit has a power switch on the rear of the panel. Review the instructions

in “T urning On AC Power to the System” on page 2-22 and “Turning On AC Power to

the System” on page 2-22 for additional precautions related to enabling and disabling

power.

• The T1000 automatically shuts down if the total power consumption exceeds the

total power supply output capacity.

Caution:

Statement 5: The power control button on the T1000 does not turn off the electrical current supplied to the device. The device also might have more than one power cord. To remove all electrical current from the device, ensure that all power cords are disconnected from the power source.

Caution Statement 8:

Never remove the cover on a power supply or any part that has the following label attached.

2-20 T-Series Traffic Director Installation, Configuration and Administration Guide

Connecting an AC Shelf to Power

The T1000 with AC option has two AC-power C20 input connectors. Two (2x) C20/C19 type AC jumper cords are supplied with the AC power unit. To supply power to the T1000 unit, connect one end of each power cord to a power connector on the rear of the T1000 and the other end of each power cord to a 120-240 volt 20 amp power distribution unit or appropriate electrical outlet. Use a regulating uninterruptible power supply (UPS) to protect the T1000 from power surges and voltage spikes, and to keep the T1000 operating in case of power failure. See the following figure.

Figure 2-8 Connecting AC Power

Connecting and Disconnecting AC Power

Use the following procedure to connect the AC shelf to power:

Step 1 Isolate the power supply to ensure that the power supply cables are not energized. Use an

appropriate lockout/tagout procedure to ensure that the power supply cables are not accidentally energized during the installation procedure.

Step 2 Connect the power cables to both power connectors.

T-Series Traffic Director Installation, Configuration and Administration Guide 2-21

Chapter 2 Installing the T1000

Turning On AC Power to the System

The T1000 unit has a power switch located on the rear panel. See Figure 2-8 above. When properly energized, the LCD panel on the front of the T1000 will illuminate.

Turning Off AC Power to the System

If you need to shut down the T1000 to mov e it or to p erfor m maintenan ce, y ou mu st ma ke sure all the processes in the system are shut down properly.

Follow the steps below to power off the system:

Step 1 Log on to the system CLI or GUI and access the shutdown function to power-off the T1000.

All processes are shut down gracefully before power to the T1000 is switched off.

Step 2 Turn off AC power to the circuits that are providing power to the T1000. Step 3 Disconnect the power cables from the rear of the T1000. See Figure 2-8.

Caution:

Connecting and Disconnecting DC Power

Attention: Only trained service personnel other than Bytemobile service technicians are

authorized to install and remove the -48 volt DC power supply, and make the connections to and disconnections from the -48 volt DC power source. Bytemobile service technicians are not certified or authorized to install or remove the -48 volt power cable. The customer is responsible for ensuring that only trained service personnel install or remove the -48 volt power c able.

This section describes how to connect and disconnect power to a T1000 shelf configured with DC power. This section has the following topics:

• “Before you Begin DC Power Connection” on page 2-23

2-22 T-Series Traffic Director Installation, Configuration and Administration Guide

Connecting and Disconnecting DC Power

• “Connecting a DC Shelf to Power” on page 2-27

• “Turning On DC Power to the System” on page 2-28

• “Turning Off DC Power to the System” on page 2-28

For procedures related to AC power, see “Connecting and Disconnecting AC Power” on page 2-19.

Note: The T1000 includes two power supplies, but fu nction s pro perly with a sing le

power supply. Bytemobile recommends connecting both power supplies (to independent power sources) for redundancy.

Before you Begin DC Power Connection

Before you begin the power connection/disconnection proced ures, note the follo wing:

• Review the safety warnings in this document.

• Review the electrostatic discharge (ESD) guidelines earlier in this document.

• Review the DC power specifications in the T1000 specifications document.

• The following guidelines are provided for connecting to the -48 V DC power source.

It is the customer’s responsibility to supply the necessary power cable.

– Intrabuilding Cabling: The intrabuilding port(s) of the equipment or subasse mbly

is suitable for connection to intrabuilding or unexposed wiring or cabling only. The intrabuilding port(s) of the equipment or subassembly MUST NOT be metallically connected to interfaces that connect to the OSP or its wiring. These interfaces are designed for use as intrabuilding interfaces only (Type 2 or Type 4 ports as described in GR-1089-CORE, Issue 5). They require isolation from the exposed OSP cabling. The addition of Primary Protectors is not sufficient protection in order to connect these interfaces metallically to OSP wiring.

– Common Bonding Network: The T1000 is intended for installation into a Common

Bonding Network (CBN).

– Grounding and Bonding Conductor Specification: Use 10 A WG Conductor IE: 8

AWG. The actua l wire gauge and terminal s ize wi l l be d e te rm in ed by the current draw and the length of wire run or as specified by the customer premises guidelines. Conductor must be copper (aluminum not allowed). Use Panduit part number LCA10-10F single-hole compression lug. (UL Listed). Use lock washer to ensure antirotation. Apply antioxidant coating to conductor before crimping on the listed single hole compression lug.

– Overcurrent Protection: The power source must have a minimum of 30 A

overcurrent protection. See article 240, paragraph 3, table 310-16 of the National Electric Code for more information about electrical wiring requirements.

– The DC-power inputs are configured for DC isolated return (DC-I). The DC

RETURN (RTN) terminal or conductor is not connected to the equipment frame or the grounding means of the equipment.

– The overc urrent protective device or circuit breaker must be accessible to service

personnel to prevent the power from being turned on by someone other than the technician servicing the T1000 unit.

T-Series Traffic Director Installation, Configuration and Administration Guide 2-23

Chapter 2 Installing the T1000

– Flexible DC wiring is recommended to allow for minimum bend radius. – Torque the #4-40 ground lug retention nuts on the power supply bracket to 4.7 inch

lbs. Torque the #8-32 ground lug retention nut on the rear panel to 17.8 inch lbs.

– For more information, see Safety Statement 34 below.

Caution:

Statement 29

This equipment is designed to permit the connection of the earthed conductor of the DC supply circuit to the earthing conductor at the equipment. If this connection is made, all of the following conditions must be met:

• This equipment shall be connected directly to the DC supply system earthing

electrode conductor or to a bonding ju mp er from an earthing terminal bar or bus to which the DC supply system earthing electrode conductor is connected.

• This equipment shall be located in the same immediate area (such as, adjacent

• The DC supply source shall be located within the same premises as this equipment.

• Switching or disconnecting devices shall not be in the earthed circuit conductor

between the DC source and the point of connection of the earthing electrode conductor.

2-24 T-Series Traffic Director Installation, Configuration and Administration Guide

Connecting and Disconnecting DC Power

Danger:

Statement 31 Electrical current from power, telephone, and communication cables is hazardous. To avoid a shock hazard:

• Do not connect or disconnect any cables or perform installation, maintenance,

or reconfiguration of this product during an electrical storm.

• Connect all power cords to a properly wired and grounded electrical outlet.

• Connect to properly wired outlets any equipment that will be attached to this

product.

• When possible, use one hand only to connect or disconnect signal cables.

• Never turn on any equipment when there is evidence of fire, water, or

structural damage.

• Disconnect the attached power cords, telecommunications systems, networks,

and modems before you open the device covers, unless instructed otherwise in the installation and configuration procedures.

• Connect and disconnect cables as described below when installing, moving, or

opening covers on this product or attached devices.

To connect:

1. Turn OFF all power sources and equipment to be attached to this product.

2. Attach all cables to the devices.

3. Attach signal cables to the connectors.

4. Attach power cords to power sources. For DC systems, ensure correct pola rity of

-48VDC connections: RTN is (+) and -48VDC is (-). Earth ground should use a two-hole lug for safety.

5. Turn ON all the power sources.

To disconnect:

1. Turn OFF all power sources and equipment to be attached to this product.

2. Disconnect DC power sources at the breaker panel or by turning off the power

source, then remove the DC cables.

3. Remove the signal cables from the connectors.

4. Remove all cables from the devices

T-Series Traffic Director Installation, Configuration and Administration Guide 2-25

Chapter 2 Installing the T1000

OFF

Caution:

Statement 33 This device provides a power control button. Removing power supply modules or using the power control button does not turn off the electrical current supplied to the device. The device also might have more than one power cord. T o r emove all electrical current from the device, ensure that all power cords are disconnected from the power source.

DC Power Option:

Statement 34 To reduce the risk of electric shock or energy hazards:

• This equipment must be installed by trained service personnel in a

restricted-access location, as defined by the NEC and IEC 60950-1, First Edition, The Standard for Safety of Information Technology Equipment.

• Connect the equipment to a properly grounded safety extra low voltage

(SELV) source. A SELV source is a secondary circuit that is designed so that normal and single fault conditions do not cause the voltages to exceed a safe level (60 V direct current).

• Incorporate a readily available approved and rated disconnect device in the

field wiring.

• See the specifications in the product documentation for the required

circuit-breaker rating for branch circuit overcurrent protection.

• Use copper wire conductors only. See the specifications in the product

documentation for the required wire size.

• See the specifications in the product documentation for the required torque

values for the wiring-terminal nuts.

2-26 T-Series Traffic Director Installation, Configuration and Administration Guide

Connecting and Disconnecting DC Power

Connecting a DC Shelf to Power

Attention: Only trained service personnel are authorized to make the connections to and

disconnections from the DC power source. Bytemobile service technicians are not certified or authorized to install or remove the DC power cables. The customer is responsible for ensuring that only trained service personnel install or remove the DC power cables.

The T1000 with DC option has three DC-power terminal connectors on each power supply: one for -48 V DC, one for RETURN (RTN), and one for connecting the safety ground wire. See the following figure.

Figure 2-9 Connecting DC Power

Note: Wire colors in the above figure are for illustration purposes only. Follow the

wire color guidelines for your facility and local electrical code.

Use the following procedure to connect the DC shelf to power:

T-Series Traffic Director Installation, Configuration and Administration Guide 2-27

Chapter 2 Installing the T1000

Step 1 Isolate the power supply to ensure that the power supply cables are not energized. Use an

appropriate lockout/tagout procedure to ensure that the power supply cables are not accidentally energized during the installation procedure.

Step 2 Connect the wires to the appropriate terminals. Torque the #4-40 wiring-terminal screws to

0.5 to 0.6 newton-meters (4.4 to 5.1 inch-pounds). Torque the #8-32 ground lug retention nut on the rear panel to 2.0 to 2.4 newton-meters (17 to 20 inch-pounds)

Turning On DC Power to the System

The T1000 unit has a power switch located on the rear panel. See Figure 2-9 above. When properly energized, the LCD panel on the front of the T1000 will illuminate.

Turning Off DC Power to the System

Attention: Only trained service personnel are authorized to make the connections to and

If you need to shut down the T1000 to mov e it or to p erfor m maintenan ce, y ou mu st ma ke sure all the processes in the system are shut down properly.

Follow the steps below to power off the system:

Step 1 Log on to the system CLI or GUI and access the shutdown function to power-off the T1000.

All processes are shut down gracefully before power to the T1000 is switched off.

Step 2 Turn off DC power to the circuits that are providing power to the T1000. Isolate the power

supply to ensure that the power supply cables are not energized. Use an appropriate lockout/tagout procedure to ensure that the power supply cables are not accidentally energized during the disconnect procedure.

Step 3 Disconnect the power cables from the rear of the T1000. See Figure 2-9.

2-28 T-Series Traffic Director Installation, Configuration and Administration Guide

Accessing and Configuring the Management Plane

OFF

Caution:

Statement 5: The power control button on the device and the power switch on the power supply do not turn off the electrical current supplied to the device. The device also might have more than one power cord. To remove all electrical current from the device, ensure that all power cords are disconnected from the power source.

DC Power Option:

Accessing and Configuring the Management Plane

After you have installed the T1000 in a rack and applied power, you are ready to perform the initial configuration of the management plane.

To perform the initial configuration, you can use the LCD keypad or the setup wizard. You can access the setup wizard from any computer that is on the same network as the new T1000. However, because this method uses the T1000 default IP address, you must install and configure one T1000 at a time. If you want to configure a new T1000 from a remote network, or if you want to install multiple T1000s and then configure them without using the console port, you can use Dynamic Host Configuration Protocol (DHCP) to assign each new T1000 an IP address at which you can access the T1000 for remote configuration.

After you complete the initial management plane configuration, you can configure secure access to your T1000. As a result, you are no longer prompted for a password when logging on. This is especially helpful in environments for which you would otherwise have to keep track of a large number of passwords.

Using the LCD Keypad

When you first install the T1000, you can configure the initial settings by using the LCD keypad and display module on the front panel.

The configuration file (ns.conf) should contain the following command and default values.

set ns config -IPAddress 192.168.100.1 -netmask 255.255.0.0

The LCD keypad has the following functions:

T-Series Traffic Director Installation, Configuration and Administration Guide 2-29

Chapter 2 Installing the T1000

Table 2-1 LCD Key Functions

Key Function

Moves the cursor one digit to the left. > Moves the cursor one digit to the right. ^ Increments the digit under the cursor. v Decrements the digit under the cursor.

. Processes the information, or terminates the

configuration, if none of the values are changed. This key is also known as the ENTER key.

You are prompted to enter the subnet mask, T1000 IP address (NSIP), and gateway in that order respectively . The subnet mask is associated with both the NSIP and default gateway IP address. The NSIP is the IPv4 address of the T1000. The default gateway is the IPv4 address for the router, which will handle external IP traffic that the T1000 cannot otherwise route. The NSIP and the default gateway should be on the same subnet.

If you enter a valid value for the subnet mask, such as 255.255.255.224, you are prompted to enter the IP address. Similarly, if you enter a valid value for the IP address, you are prompted to enter the gateway address. If the value you entered is invalid, the following error message appears for three seconds, where xxx.xxx.xxx.xxx is the IP address you entered, followed by a request to re-enter the value.

Invalid addr! xxx.xxx.xxx.xxx

If you press the ENTER (.) key without changing any of the digits, the software interprets this as a user exit request.The following message will be displayed for three seconds.

Exiting menu... xxx.xxx.xxx.xxx

If all the values entered are valid, when you press the ENTER key, the following message appears.

Values accepted, Rebooting...

The subnet mask, NSIP, and gateway values are saved in the configuration file.

Using the Setup Wizard

To configure the T1000 by using the Setup Wizard in the configuration utility, you need an administrative computer configured on the same network as the T1000. To run the configuration utility, the Java RunTime Environment (JRE) version 1.4.2_04 or later must be installed on the workstation or laptop. You can use the Setup Wizard to configure the following initial settings on the T1000:

• System IP address and subnet mask

• Subnet or Mapped IP address and subnet mask

• Host name

• Default gateway

2-30 T-Series Traffic Director Installation, Configuration and Administration Guide

Accessing and Configuring the LOM Port

• Time zone

• Licenses

• Administrator password

Important: Before running the Setup Wizard, you should obtain your licenses from the

Bytemobile and put them in a location on your computer or another device where you can access them from your Web browser during configuration.

Note: If the T1000 is configured with the default IP address, licenses are not installed

on the T1000, or the mapped or subnet IP address is not configured, the configuration utility automatically opens the Setup Wizard when you log on to the T1000.

To configure initial settings by using the Setup Wizard:

Step 1 In a Web browser, type: http://192.168.100.1

Note: The operating system is preconfigured with a default IP address and associated

netmask. The default IP address is 192.168.100.1 and the default netmask is

255.255.0.0.

Step 2 In User Name and Password, type the administrator credentials.

Note: The T1000 default username is nsroot and the default password is nsroot.

Change these values as soon as possible.

Step 3 In Start in , select Configuration, and then click Login. Step 4 In the Setup Wizard, click Next, and then follow the instructions in the wizard.

Note: T o prevent an attacker from breaching your ability to send packets to the T1000,

choose a non-routable IP address on your organization's LAN as your T1000 IP address.

Step 5 You have now completed initial configuration of your T1000.

Accessing and Configuring the LOM Port

The T1000 has an Intelligent Platform Management Interface (IPMI) also known as the Lights out Management (LOM) port on the front panel. Using LOM, you can remotely monitor and manage the T1000 independently of the operating system. You can remotely change the IP address, power cycle the T1000, and perform a code dump by connecting to the T1000 through the LOM port.

T-Series Traffic Director Installation, Configuration and Administration Guide 2-31

Chapter 2 Installing the T1000

By connecting the LOM port over a dedicated channel that is separate from the data or management channel, you can make sure that connectivity to the T1000 is maintained even if those networks are down.

Configuring the LOM Port

For initial configuration of the LOM port, connect to the port's default IP address and change it to the address that you want to use for remote monitoring and management. Also specify the administrator credentials and the network settings.

Note: The LEDs on the LOM port are nonoperational by design.

Step 1 In a Web browser, type the IP address of the LOM port. For initial configuration, type the

port’s default address: http://192.168.1.3.

Step 2 In the User Name and Password boxes, type the administrator credentials. You can obtain

the initial user name and password from Bytemobile.

Step 3 In the Menu bar, click Configuration. Step 4 Under Options, click Network and type values for the following parameters:

• IP Address—The IP address of the LOM port.

• Subnet Mask—The mask used to define the subnet of the LOM port.

• Default Gateway—The IP address of the router that connects the T1000 to the

network.

Step 5 Click Save.

Using the LOM to Power Cycle the T1000

You can remotely turn off the T1000 and turn it back on. The result is similar to pressing the power button on the back panel of the T1000 for less than four seconds. The operating system performs a graceful shutdown. All operations on the T1000 are stopped, no new connections to the client or server are accepted, and all the existing connections are closed.

Step 1 In a Web browser, type the IP address of the LOM port. Step 2 In the User Name and Password boxes, type the administrator credentials. Step 3 In the Menu bar, click Remote Control. Step 4 Under Options, click Power Control, and then click Power Cycle Server. Step 5 Click Perform Action.

Using the LOM to Perform a Core Dump

If the T1000 fails or becomes unresponsive, you can remotely perform a core dump. This procedure has the same effect as pressing the NMI button on the back panel of the T1000.

2-32 T-Series Traffic Director Installation, Configuration and Administration Guide

Accessing and Configuring the LOM Port

T-Series Traffic Director Installation, Configuration and Administration Guide 2-33

Chapter 2 Installing the T1000

2-34 T-Series Traffic Director Installation, Configuration and Administration Guide

3. Basic Load Balancing Configuration

Basic T1000/Unison Load-Balancing

Configuration

The procedures in this chapter describe how to configure the data plane of the T1000 Traffic Director to distribute and process subscriber traffic in a Bytemobile Unison deployment.

This chapter has the following sections:

• Physical Integration of T1000 with Unison

• Managing Configurations

• Assigning VLANs, IP Addresses, and Ports

• Configuring T1000 Data Plane for Layer-2 and Layer-3

• Configuring T1000 Load Balancing

• Configuring Health Checks and Redundancy

• Configuring Source NAT (SNAT)

• Configuring Security

• Testing with Network Diagnostic and Shell Tools

T-Series Traffic Director Installation, Configuration and Administration Guide 3-1

Chapter 3 Basic T1000/Unison Load-Balancing Configuratio n

Physical Integration of T1000 with Unison

The Bytemobile Unison cluster supports on a variety o f x 86-based hard ware p latform s running the Solaris operating system (refer to the Unison Architecture Overview for a list of supported platforms). The T1000 Traffic Director offers flexible integration options for all supported Unison hardware. Figure 3-1 shows a typical Unison deployment running on an IBM BladeCenter® shelf.

Figure 3-1 Typical Physical Connections to T1000 and Unison Cluster

In this deployment, one or more BladeCenter shelves house enough application blades (OSNs) to process subscriber traffic. Two blades in the deployment are reserved for Control and State Module (CSM) blades, which process management and control plane traffic. The

3-2 T-Series Traffic Director Installation, Configuration and Administration Guide

Managing Configurations

CSM blades do not process subscriber data traffic. A set of integrated 1/10Gb switch modules integrated into the BladeCenter shelf direct (but do not load balance) traffic across the OSN blades.

The OSN blades of the Unison cluster sit directly in the data path of the network, between the wireless-side router (such as a GGSN) and an Internet-side gateway. Each OSN has two interfaces on the data plane for redundancy. VLANs separate the subscriber-side and Internet-side traffic.

In a typical Unison deployment, the OSNs will be configured for zone-based operation. With zones, each application blade runs two instances of the OSN software in virtualized Solaris containers (Zone 0 and Zone 1, as shown). Therefore, each application blade will have four interfaces (two OSNs and two interfaces per OSN).

As shown in Figure 3-1, a redundant pair of T1000s connect to the wireless-side router, Internet-side router, and to the Unison cluster via a Layer 2 switch (or a pair of switches for redundancy). Both 1Gb and 10Gb connections are supported, using fiber optic cable an d a n appropriate SFP+ transceiver.

The T1000 supports two-port link-aggregation control protocol (LACP) on 10Gb trunk connections. More ports can be added per trunk to support extra throughput (up to 50 Gb) and redundancy requirements.

The T1000 performs firewall load balancing (FWLB), to transparently load balance data plane traffic across OSNs in the direction of the Internet. Traffic passes through the OSNs and transparently maintains its Layer 3 information. The T1000 exposes a single IP address (or multiple, as necessary) as the destination for this traffic. The T1000 uses session persistency to ensure that traffic returning from the Internet is routed back to the same OSN from which it originated.

The T1000 also supports optional server load balancing (SLB) in deployments where the Unison cluster does not function in a transparent, inline mode, but instead has a specific routable IP address. For example, if Unison WAP Gateway functions are deployed, or NonInline mode is used with optimization clients, the Unison cluster will have a specific IP address requiring server load balancing.

Connecting Network Cables to T1000

The T1000 has a set of of SFP and/or SFP+ ports that are used to connect the T1000 data plane to intermediate switches. For more information, refer to Chapter 2, “Installing the

T1000”.

Managing Configurations

The T1000 offers a range of commands that allow you to set, save, view, cancel, and compare configurations. You should become fa miliar with these commands before continuing with the configuration process.

Important: You must use the save ns config command to apply pending configurations to

the current T1000 configuration.

• All configurations should be performed from the active T1000 in a high-availability

group. You will be informed of the T1000 status when you log on to the CLI.

T-Series Traffic Director Installation, Configuration and Administration Guide 3-3

Chapter 3 Basic T1000/Unison Load-Balancing Configuratio n

• To apply the pending configuration to the T1000, use the save ns config command.

The configuration will be saved to the ns.conf file in flash memory. If the T1000 is part of a high-availability group, this command also copies the new configuration to the standby T1000.

• To cancel the current configuration, use the clear ns config command.

• To display the information pertaining to the configuration that has been applied to

the system, including pending settings that have not yet been saved to the system's ns.conf file using the save config command, use show ns runningConfig.

• To display the last saved configuration, use the show ns ns.conf command.

Assigning VLANs, IP Addresses, and Ports

The T1000 offers different deployment models to support a variety of network architectures. The information in this section applies to basic load balancing, with the T1000 processing all Unison (non-bypassed) traffic originating from and returning to subscribers.

Refer to the following topics:

• “IP Addresses for Basic Load Balancing” on page 3-5

• “IP Addresses for High Availability” on page 3-6

• “VLAN Assignments” on page 3-6

• “Interface (Port) Assignments and Trunking” on page 3-7

3-4 T-Series Traffic Director Installation, Configuration and Administration Guide

Assigning VLANs, IP Addresses, and Ports

IP Addresses for Basic Load Balancing

In basic deployment mode, the T1000 processes all Unison traffic originating from and

returning to subscribers. See Figure 3-2 for a typical arrangement

of data plane IP

addresses (management and control IP addresses are not shown).

Note: IP addresses and VLAN IDs in this document are for example purposes only.

Use appropriate values for your network deployment.

Figure 3-2 Typical IP Addresses and VLAN IDs

In this example, IP addresses are assigned as follows:

• Each application blade has two (2) IP addresses in the data plane (management and

control traffic will require additional interfaces). The OSNs in this example are “zoned,” meaning that two instances of OSN run on each blade. Each zone has two interfaces for redundancy. Ingress and egress traffic are each handled on separate interfaces. Note that a typical Unison deployment may have many OSN blades — in some cases, over 100 blades.

• The T1000 has four (4) IP addresses in the data plane.

• A second T1000 has an identical data plane IP address configuration.

• T1000 supports link local (169.254.x.x, as shown) or private (for examp le, 10 .x.x .x )

IP addresses.

1. Figure 3-2 presents a typical Unison deployment with a single ingress/egress VLAN. Note that the T1000 is not restricted to a single VLAN. Multiple ingress and egress VLANs may be configured in accordance to the instructions in this guide, typically by copy/pasting the relevant commands to accommodate for the extra VLANs

T-Series Traffic Director Installation, Configuration and Administration Guide 3-5

Chapter 3 Basic T1000/Unison Load-Balancing Configuratio n

IP Addresses for High Availability

Bytemobile recommends a high availability (HA) deployment model with two T1000s, as shown in Figure 3-2. One T1000 works as the primary node accepting all connections, while the second T1000 works as a standby node. If the primary T1000 (known as T1000-1, or preferr ed master) fails, the secondary T1000 (T1000-2) takes over. Failure may be triggered by any of the following events:

• Failure of a next-hop router.

• Failure of an external port or link.

• Failure of the primary T1000 itself.

The secondary T1000 monitors the primary by sending periodic healthcheck messages to determine whether the primary T1000 is accepting connections. If a healthcheck fails, the secondary node retries the connection for a specified period, after which it determines that the primary T1000 is not functioning normally. The secondary T1000 then takes over for the primary (a process called failover). After a failover, all subscriber and server connections must be reestablished, but session persistence rules are maintained as they were before the failover.

In a high availability deployment, the primary T1000 “owns” all virtual IP addresses. When a failover occurs, the secondary T1000 becomes primary and then uses gratuitous ARP (GARP) to advertise the floating IP addresses acquired from the offline T1000. Without additional configuration, the new primary T1000 will use the MAC addresses of its own interfaces.

In some instances, certain devices will not accept the GARP messages generated by the T1000. As a result some external devices will retain the IP to MAC mapping of the offline T1000, resulting in loss of service. To address this problem, you may configure identical virtual MAC (VMAC) addresses on both T1000s. Therefore, when failover occurs, ARP tables on external devices do not need to be updated.

When a failover is triggered, T1000-2 will be declared master in the case of a failure that affects only T1000-1. Once the failure is addresses, a voluntary failback is triggered, and T1000-1 is declared master again.

VLAN Assignments

Note: IP addresses and VLAN IDs in this document are for example purposes only.

Use appropriate values for your network deployment.

In a load balancing deployment, VLANs separate ingress, egress, and management traffic. The sample network in Figure 3-2 uses the following VLAN IDs:

• Ingress VLANs: – VLAN ID 100 is the OSN ingress VLAN. It is configured on the T1000 ports as

well as all OSN internal ports. Also used for blade healthcheck purposes.

– VLAN ID 151 is the T1000 ingress VLAN. It is configured on the T1000 ports and

on the wireless-side router.

3-6 T-Series Traffic Director Installation, Configuration and Administration Guide

Assigning VLANs, IP Addresses, and Ports

• Egress VLANs: – VLAN ID 200 is the OSN egress VLAN. It is configured on the T1000 ports as well

as all OSN internal ports.

– VLAN ID 251 is the T1000 e gress VLANs. It is configured on the T1000 ports and

on the Internet-side router.

• Management and Other VLANs (not shown in Figure 3-2): – VLAN ID 130 is for T1000 management and high availability purposes. – VLAN ID 66 is for internal communicatio n between OSN and CSM blades. – VLAN ID 131 is for OAM connectivity to the operator management network.

Interface (Port) Assignments and Trunking

The T1000 uses an interface/index method for specifying ports. The two management ports are referenced as Interface 0/1 and Interface 0/2

. The data plane ports are referenced as

follows:

• T1010: Interface 1/1 to 1/6 (Ethernet) and 1/7 to 1/12 (1 GE SFP)

• T1010 (8-Port):Interface 10/1 to Interface 10/8 (10GE SFP+)

• T1100 (16-Port): Interface 10/1 to Interface 10/16 (10GE SFP+)

• T1200: Interface 1/1 to 1/12 (1GE SFP) and 10 /1 to 1 0/24 (10 GE SFP+)

The examples in this chapter use the following interface (port) assignments:

• Interface 10/1 and 10/2 will be reserved for communication with the Unison blade

switch.

• Interface 10/3 will be reserved for ingress VLAN 151.

• Interface 10/4 will be reserved for egress VLAN 251.

T1000 ports support the link aggregation control protocol (LACP) for trunking. In this example, Interface 10/1 and 10/2 will be trunked to the blade switch. After LACP configuration these trunked ports will be referenced as Interface LA/1.

Additional trunks may be added on any T1000 interface to increase throughput capacity.

Note: If using the T1010 (which has only 1GE interfaces), substitute the appropriate

interfaces as appropriate. For example, use interface 1/7 instead of 10/1.

1. The T1010 has only one management port, referenced as Interface 0/1.

T-Series Traffic Director Installation, Configuration and Administration Guide 3-7

Chapter 3 Basic T1000/Unison Load-Balancing Configuratio n

Configuring T1000 Basic Functions

This section is an extension of the installation steps described in “Accessing and

Configuring the Management Plane” on page 2-29. These are basic functions such as

management IP address, default route, host name, licensing, and NTP configuration.

Step 1 Set management IP address. See “Setting Management IP Address” on page 3-8. Step 2 Set a default route for the management network. See “Setting Default Route” on page 3-8. Step 3 Set the T1000 hos t name. “Setting Host Name” on pa ge 3-9. Step 4 Request a license from Bytemobile support and install it. See “Requesting a License” on

page 3-9.

Step 5 Verify the operating system version. See “Verifying Operating System” on page 3-9. Step 6 Configure an NTP server. See “Configuring NTP” on page 3-9.

T1000 configuration tasks are typically carried out through either the command line interface (CLI) via SSH or the graphical user interface (GUI). See “Using the T1000

Command Line Interface (CLI)” on page 5-1 or “Using the T1000 Graphical User Interface (GUI)” on page 5-2 for more information. Certain configurations, such as management IP

address, can only be performed from the CLI. Configurations in this manual are presented using only the CLI.

Setting Management IP Address

Note: Basic functionality can also be configured by using the config ns command

(management IP address, VLAN, and timezone). The config ns command launches a menu-driven system that simplifies the configuration process.

The following example shows how to configure the management IP, the hostname of the T1000, the default route and a new password for administrator (nsroot)

> set ns config -ipaddress 10.8.130.31 -netmask 255.255.255.0 Done > save ns config Done

One may optionally bind the management IP address to a specific VLAN and interface. Link aggregates (LACP or static trunks) are both supported for this purpose:

> set ns config -nsvlan <positive_integer> -ifnum <interface_name> [-tagged ( YES | NO )]

Done

After configuring management IP address, it is recommended that you create new users, and change passwords for all users. For more information, see “Configuring Users and Groups” on page 5-9.

Setting Default Route

The following example shows how to set the default route:

3-8 T-Series Traffic Director Installation, Configuration and Administration Guide

> add route Network 0.0.0.0 0.0.0.0 10.8.130.254 Done > save ns config Done

Setting Host Name

The following example shows how to configure the hostname of the T1000:

> set ns hostName T1000-1 Done > save ns config Done > reboot

Requesting a License

Request a license from Bytemobile Support. You will be required to provide the following information for the license:

• Network Architecture.

• License Model (based on number of subscribers, amount of data, enforcement type).

Configuring T1000 Basic Functions

• Optional features purchased by the customer.

• Host ID and hardware type.

To retrieve the T1000 Host ID:

> shell root@T1000-1#lmutil lmhostid -ether The FLEXnet host ID of this machine is "123456789ABCDEF"

Verifying Operating System

The T1000 will be shipped with an appropriate operating system image. You should verify the version prior to continuing.

To display OS version from the CLI:

> show ns version NetScaler NSX.X: Build 60.3007.e.nc, Date: Feb 28 2013, 09:05:58

Ensure both T1000s have the same image. Also ensure that the installed version matches or is greater than the Build 60.3007.e.n c v ersion men tio ned above .

If the OS version is lower than the recommended value, contact Bytemobile Support. To upgrade the OS, see “Upgrading the T1000 Operating System” on page 5-4.

Configuring NTP

The following example shows how to configure a primary and a secondary NTP server and set the poll period from 64 to 1024 seconds. Use values appropriate to your network.

Note: NTP transactions occur on the management interface. Ensure the management

network is configured and operational. See “Accessing and Configuring the

Management Plane” on page 2-29.

T-Series Traffic Director Installation, Configuration and Administration Guide 3-9

Chapter 3 Basic T1000/Unison Load-Balancing Configuratio n

To configure NTP from the CLI:

> add ntp server 10.20.30.40 -minpoll 6 -maxpoll 10 Done > set ntp server 10.20.30.40 -preferredNtpServer YES Done > add ntp server 11.21.31.41 -minpoll 6 -maxpoll 10 Done > enable ntp sync Done

3-10 T-Series Traffic Director Installation, Configuration and Administration Guide

Configuring T1000 Data Plane for Layer-2 and Layer-3

The procedures in this section describe how to configure Layer-2 and Layer-3 of the T1000 data plane in preparation for the load balancing configuration. The general configuration sequence is as follows:

Step 1 Configure network interfaces (ports). See “Configuring Network Interfaces ” on page 3-12. Step 2 Create a trunk (LACP) interface on the ports connected to the Unison blade switch.

Optionally create a trunk interface for any other ports that required higher capacity. See

“Configuring Trunking” on page 3-14.

Step 3 Add VLAN IDs, and bind those VLANs to the interfaces created in the previous step. See

“Configuring VLANs” on page 3-14.

Step 4 Configure IP addresses as a routable destin ation for subscriber ingress traffic. See

“Configuring IP Addresses” on page 3-1 5.

Step 5 Bind VLANs to IP Addresses. See “Binding VLANs to IP Addresses” on page 3-15. Step 6 Add routes from the T1000 to next-hop gateways. See “Adding Routes” on page 3-16. Step 7 Optionally, configure Policy Based Routing (PBR). See “Configuring Policy Based Routing

(PBR)” on page 3-16.

T-Series Traffic Director Installation, Configuration and Administration Guide 3-11

Chapter 3 Basic T1000/Unison Load-Balancing Configuratio n

Configuring Network Interfaces

“Interface” refers to the physical network connections on the front panel of the T1000. The configurations in this section enable and disable the required interfaces and set interface properties.

The following example shows how to configure the network interfaces of T1000 using th e set interface command. The set interface command has the following general syntax for this purpose:

set interface if/index [-speed speed] [-haMonitor (ON | OFF)]

[-tagall (ON | OFF)] [-lacpMode lacpMode] [-lacpKey positive_integer] [-lacpPriority positive_integer] [-lacpTimeout (LONG | SHORT)] [-ifAlias string] [-throughput positive_integer] [-bandwidthHigh positive_integer [-bandwidthNormal positive_integer]]

Using the example configuration:

>set interface 10/1 -tagall ON -throughput 0 -bandwidthHigh 0 -bandwidthNormal 0 Done >set interface 10/2 -tagall ON -throughput 0 -bandwidthHigh 0 -bandwidthNormal 0 Done >set interface 10/3 -tagall ON -throughput 0 -bandwidthHigh 0 -bandwidthNormal 0 Done >set interface 10/4 -tagall ON -throughput 0 -bandwidthHigh 0 -bandwidthNormal 0 Done

To disable unused ports, use the set interface command as follows:

>set interface 10/7 -haMonitor OFF -tagall ON -state DISABLED -throughput 0

-bandwidthHigh 0 Done

Use the show interface command to display the current configuration. For example:

> show interface

1) Interface 0/1 (Gig Ethernet 10/100/1000 MBits) #8 flags=0xc021 <ENABLED, UP, UP, autoneg, HAMON, 802.1q> MTU=1514, native vlan=1, MAC=00:25:90:64:ba:86, uptime 14h23m23s Requested: media AUTO, speed AUTO, duplex AUTO, fctl OFF, throughput 0 Actual: media UTP, speed 1000, duplex FULL, fctl OFF, throughput 1000

2) Interface 0/2 (Gig Ethernet 10/100/1000 MBits) #9 flags=0x4001 <ENABLED, DOWN, down, autoneg, 802.1q> MTU=1514, native vlan=1, MAC=00:25:90:64:ba:87, downtime 203h16m39s Requested: media AUTO, speed AUTO, duplex AUTO, fctl OFF, throughput 0

3) Interface 10/1 (10G Ethernet, no SFP+ found) #0 flags=0x400c021 <ENABLED, UP, BOUND to LA/1, UP, autoneg, 802.1q> LACP <Active, Long timeout, key 1, priority 32768> MTU=1514, MAC=00:1b:21:cf:18:20, uptime 14h23m21s Requested: media AUTO, speed AUTO, duplex AUTO, fctl OFF, throughput 0 Actual: media FIBER, speed 10000, duplex FULL, fctl OFF, throughput 10000

4) Interface 10/2 (10G Ethernet, no SFP+ found) #2 flags=0x400c021 <ENABLED, UP, BOUND to LA/1, UP, autoneg, 802.1q> LACP <Active, Long timeout, key 1, priority 32768> MTU=1514, MAC=00:1b:21:cf:13:70, uptime 14h23m22s

3-12 T-Series Traffic Director Installation, Configuration and Administration Guide

Configuring T1000 Data Plane for Layer-2 and Layer-3

Requested: media AUTO, speed AUTO, duplex AUTO, fctl OFF, throughput 0 Actual: media FIBER, speed 10000, duplex FULL, fctl OFF, throughput 10000

5) Interface 10/3 (10G Ethernet, no SFP+ found) #4 flags=0xc023 <ENABLED, UP, UP, autoneg, HAMON, 802.1q, tagall> MTU=1514, native vlan=1, MAC=00:1b:21:cf:14:08, uptime 14h23m22s Requested: media AUTO, speed AUTO, duplex AUTO, fctl OFF, throughput 0 Actual: media FIBER, speed 10000, duplex FULL, fctl OFF, throughput 10000 VMAC=00:00:5e:00:01:0a

6) Interface 10/4 (10G Ethernet, no SFP+ found) #6 flags=0xc023 <ENABLED, UP, UP, autoneg, HAMON, 802.1q, tagall> MTU=1514, native vlan=1, MAC=00:1b:21:cf:13:9c, uptime 14h23m24s Requested: media AUTO, speed AUTO, duplex AUTO, fctl OFF, throughput 0 Actual: media FIBER, speed 10000, duplex FULL, fctl OFF, throughput 10000 VMAC=00:00:5e:00:01:0a

7) Interface 10/5 (10G Ethernet, fiber SFP+, 1/10 Gbits) #5 flags=0x4001 <disabled, DOWN, down, autoneg, 802.1q, tagall> MTU=1514, native vlan=1, MAC=00:1b:21:cf:18:21, downtime 203h16m39s Requested: media AUTO, speed AUTO, duplex AUTO, fctl OFF, throughput 0

8) Interface 10/6 (10G Ethernet, fiber SFP+, 1/10 Gbits) #5 flags=0x4001 <disabled, DOWN, down, autoneg, 802.1q, tagall> MTU=1514, native vlan=1, MAC=00:1b:21:cf:13:71, downtime 203h16m39s Requested: media AUTO, speed AUTO, duplex AUTO, fctl OFF, throughput 0

9) Interface 10/7 (10G Ethernet, fiber SFP+, 1/10 Gbits) #5 flags=0x4001 <disabled, DOWN, down, autoneg, 802.1q, tagall> MTU=1514, native vlan=1, MAC=00:1b:21:cf:14:09, downtime 203h16m39s Requested: media AUTO, speed AUTO, duplex AUTO, fctl OFF, throughput 0

10) Interface 10/8 (10G Ethernet, no SFP+ found) #7 flags=0xc021 <ENABLED, UP, UP, autoneg, HAMON, 802.1q, tagall> MTU=1514, native vlan=1, MAC=00:1b:21:cf:13:9d, uptime 14h23m18s Requested: media AUTO, speed AUTO, duplex AUTO, fctl OFF, throughput 0 Actual: media FIBER, speed 10000, duplex FULL, fctl OFF, throughput 10000

11) Interface LA/1 (802.3ad Link Aggregate) #11 flags=0x4100c023 <ENABLED, UP, AGGREGATE, UP, HAMON, 802.1q, tagall> MTU=1514, native vlan=1, MAC=02:1b:21:cf:18:20, uptime 14h23m19s Requested: media NONE, speed NONE, duplex NONE, fctl NONE, throughput 0 Actual: throughput 20000 LA mode: AUTO 10/1: FIBER-10000-FULL-OFF UP 14h23m21s 10/2: FIBER-10000-FULL-OFF UP 14h23m22s VMAC=00:00:5e:00:01:0a

12) Interface LO/1 (Loopback interface) #10 flags=0x20008021 <ENABLED, UP, UP> MTU=1514, native vlan=1, MAC=00:25:90:64:ba:86, uptime 203h16m39s

T-Series Traffic Director Installation, Configuration and Administration Guide 3-13

Chapter 3 Basic T1000/Unison Load-Balancing Configuratio n

Configuring Trunking

A trunk interface binds two or more interfaces together for increased bandwidth over a link and/or increased fault tolerance. The T1000 divides traffic equally between the interfaces.

Use the set interface, set channel, and set lacp commands to create a trunk (LACP) interface on the ports connected to the Unison blade switch.

The following example shows how to use set interface to apply LACP mode and assign an LACP key to the interfaces that will be trunked together:

>set interface 10/1 -tagall ON -lacpMode ACTIVE -lacpKey 1 -throughput 0

-bandwidthHigh 0 -bandwidthNormal 0

Done >set interface 10/2 -tagall ON -lacpMode ACTIVE -lacpKey 1 -throughput 0

-bandwidthHigh 0 -bandwidthNormal 0

Done

The set channel command configures the trunk port. It has the following syntax:

set channel id [-state {ENABLED | DISABLED}] [-speed speed] [-flowControl

flowControl] [-haMonitor {ON | OFF}] [-tagall {ON | OFF}] [-ifAlias string] [-throughput positive_integer] [-bandwidthHigh positive_integer [-bandwidthNormal positive_integer]]

Using the example configuration:

>set channel LA/1 -tagall ON -throughput 0 -bandwidthHigh 0 -bandwidthNormal 0 Done

The set lacp command configures the LACP system priority for the trunk, using integers from 1 to 65335. It has the following syntax:

set lacp -sysPriority positive_integer

Using the example configuration:

>set lacp -sysPriority 32768 Done

Configuring VLANs

The example deployment in this chapter uses eight VLANs in total: four ingress and four egress.

Use the add vlan command to add the VLANs, and the bind vlan command to bind a VLAN to an interface. These commands have the following syntax:

To add a VLAN ID:

add vlan id [-aliasName string]

To bind a VLAN to an interface:

bind vlan id [-ifnum interface_name ... [-tagged]]

3-14 T-Series Traffic Director Installation, Configuration and Administration Guide

Configuring T1000 Data Plane for Layer-2 and Layer-3

Ingress VLANs are configured on the appropriate ports communicating with wireless router and OSN ingress interfaces. Using the example configuration:

>add vlan 100 Done >add vlan 151 Done >bind vlan 100 -ifnum LA/1 -tagged Done >bind vlan 151 -ifnum 10/3 -tagged Done

Egress VLANs are configured on the appropriate ports communicating with internet router and OSN egress interfaces. Using the example configuration:

>add vlan 200 Done >add vlan 251 Done >bind vlan 200 -ifnum LA/1 -tagged Done >bind vlan 251 -ifnum 10/4 -tagged Done

Configuring IP Addresses

Refer to “Assigning VLANs, IP Addresses, and Ports” on page 3-4 for information on how to assign IP addresses. The T1000 requires one or more Subnet IP addresses (SNIPs). A Subnet IP enables the T1000 to connect to a subnet which is different than that of the NSIP address. For the sample network in Figure 3-2, four (4) SNIPs must be configured in T1000 in order to connect to the four subnets (wireless side, osn ingress side, osn egress side, internet side).

Use the add ns ip command as follows to configure IP addresses:

add ns ip IPAddress netmask -vServer DISABLED

Using the example configuration:

>add ns ip 172.16.112.101 255.255.255.0 -vServer DISABLED Done >add ns ip 169.254.0.100 255.255.255.0 -vServer DISABLED Done >add ns ip 169.254.64.100 255.255.255.0 -vServer DISABLED Done >add ns ip 172.16.113.101 255.255.255.0 -vServer DISABLED Done

Binding VLANs to IP Addresses

After configuring the VLANs and IP addresses, you must bind the VLANs to the IP addresses.

Use the bind vlan command with the following syntax to bind VLAN IDs to IP addresses:

bind vlan id -IPAddress ip_addr netmask

Using the example configuration:

T-Series Traffic Director Installation, Configuration and Administration Guide 3-15

Chapter 3 Basic T1000/Unison Load-Balancing Configuratio n

>bind vlan 100 -IPAddress 169.254.0.100 255.255.255.0 Done >bind vlan 200 -IPAddress 169.254.64.100 255.255.255.0 Done >bind vlan 151 -IPAddress 172.16.112.101 255.255.255.0 Done >bind vlan 251 -IPAddress 172.16.113.101 255.255.255.0 Done

Adding Routes

The T1000 requires routes to next-hop gateways on the wireless and Internet sides of the network.

Use the add route command to add routes from the T1000 to the next hop gateways. The

add route command has the following basic syntax:

add route network netmask gateway

Using the example configuration:

>add route 10.200.0.0 255.254.0.0 172.16.112.65 Done >add route 192.168.40.0 255.255.255.0 172.16.113.65 Done

Configuring Policy Based Routing (PBR)

The T1000 has a policy based routing (PBR) feature that is typically used to simplify routing decisions. In most Unison deployments routing decisions are keyed against the incoming VLAN. For example, in the reference outlined in Figure 3-2:

• Incoming traffic on ingress VLAN 151 is routed towards the 172.16.113.65 router on

egress VLAN 251.

• Incoming traffic on egress VLAN 251 is routed towards the 172.16.112.65 router on

ingress VLAN 151.

The benefits of PBR are more obvious in an actual deployment rather than the example configuration outlined in this guide. Specifically, in case of multiple client subnets (sometimes a dozen or more), a small set of PBR entries may substitute a number of static routes (one per client subnet), simplifying both the routing logic and the T1000 configuration.

Using the example configuration:

> add ns pbr pbr_ingress ALLOW -vlan 151 -nextHop 172.16.113.65 -priority 99 Done > add ns pbr pbr_egress ALLOW -vlan 251 -nextHop 172.16.112.65 -priority 100 Done > apply ns pbrs Done

3-16 T-Series Traffic Director Installation, Configuration and Administration Guide

Configuring T1000 Load Balancing

Once basic L3 configuration is defined, the load balancing configuration can be created. The T1000 offers two different load balancing modes for use with the Unison platform:

• The T1000 performs firewall load balancing (FWLB), to transparently load balance

data plane traffic across OSNs in the direction of the Internet. Traffic passes through the OSNs and transparently maintains its Layer 3 information. The T1000 exposes a single IP address (or multiple, as necessary) as the destination for this traffic. The T1000 uses session persistency to ensure that traffic returning from the Internet is routed back to the same OSN from which it originated.

• The T1000 also supports optional server load balancing (SLB) in deployments

where the Unison cluster does not function in a transparent, inline mode, but instead has a specific routable IP address. For example, if Unison WAP Gateway functions are deployed, or NonInline mode is used with optimization clients, the Unison cluster will have a specific IP address requiring server load balancing.

The general configuration sequence is as follows:

Step 1 Enable the load balancing feature. See “Enabling Load Balancing and Config uring

Operating Modes” on page 3-17.

Configuring T1000 Load Balancing

Step 2 Each OSN in the Unison cluster is considered a “server” from the perspective of the load

balancer. Add the ingress interfaces to a server configuration for each OSN. You will also need to add the T1000 egress interfaces as servers. See “Adding Servers” on page 3-18.

Step 3 Create services for load balancing. The config uration proc ess is different depending on the

required load balancing mode (firewall or server). See “Creating Services” on page 3-19.

Step 4 Define virtual servers and then bind the servers to the services defined in the previous step.

The configuration process is different depending on the required load balancing mode (firewall or server). See “Creating Services” on page 3-19.

Enabling Load Balancing and Configuring Operating Modes

A load balancing setup includes a virtual load-balancing server and multiple load-balanced application servers (OSN application blades). The virtual server receives incoming client requests, uses the load balancing algorithm to select an application server, and forwards the requests to the selected application server.

The following configurations enable the load balancing feature, specify the global use of client source IP, and disable the “prefer direct route” mode:

>enable ns feature LB Done >enable ns mode FR L3 USIP MBF Edge USNIP PMTUD Done >set lb parameter -preferDirectRoute NO Done >set lb parameter -vServerSpecificMac ENABLED

Done

>set l4param -l2ConnMethod Vlan Done > set rsskeytype -rsstype SYMMETRIC Done

T-Series Traffic Director Installation, Configuration and Administration Guide 3-17

Chapter 3 Basic T1000/Unison Load-Balancing Configuratio n

Note: Changing the rsskeytype parameter requires a reboot of the T1000 unit in order

to be applied properly. One may postpone the reboot action until the remaining configuration of the unit is also complete. Make sure that a save config command is issued if you would like to reboot at this point.

Adding Servers

Each OSN in the Unison cluster is considered a “server” from the perspective of the T1000. You must add the OSN ingress and T1000 egress interfaces as servers.

Use the add server command to add the OSN ingress interfaces and T1000 egress interfaces as servers. For this purpose, the syntax of the command is as follows:

add server name IPAddress

Using the example configuration, add the OSN ingress interfaces. Three OSNs are shown — you must repeat for every OSN in the cluster.

>add server OSN1-ingress 169.254.0.1 Done >add server OSN2-ingress 169.254.0.2 Done >add server OSN3-ingress 169.254.0.3 Done

Using the example configuration, add the Internet-side router interfaces.

>add server server1 172.16.113.65 Done

3-18 T-Series Traffic Director Installation, Configuration and Administration Guide

Creating Services

After the load balancing feature is enabled, at least one service must be created for each application server that is to be included in your load balancing setup. The following examples show how to define services per server for firewall or server load balancing.

To create services for Firewall Load Balancing from the CLI:

The add service command has the following general syntax:

add service name {IP | serverName} serviceType port [-clearTextPort port]

[-cacheType cacheType] [-maxClient positive_integer] [-healthMonitor {YES | NO}] [-maxReq positive_integer] [-cacheable {YES | NO}] [-cip {ENABLED | DISABLED} [cipHeader]] [-usip {YES | NO}] [-useproxyport {YES | NO}] [-sc {ON | OFF}] [-sp {ON | OFF}] [-rtspSessionidRemap {ON | OFF}] [-cltTimeout secs] [-svrTimeout secs] [-serverID positive_integer] [-CKA {YES | NO}] [-TCPB {YES | NO}] [-CMP {YES | NO}] [-maxBandwidth positive_integer] [-accessDown {YES | NO}] [-monThreshold positive_integer] [-state {ENABLED | DISABLED}] [-downStateFlush {ENABLED | DISABLED}] [-tcpProfileName string] [-httpProfileName string] [-hashId positive_integer] [-comment string

Configuring T1000 Load Balancing

] [-appflowLog {ENABLED | DISABLED}]

The following example uses the sample configuration to add the appropriate services (service type ANY).

> add serviceGroup ingress_osn_service ANY -maxClient 0 -maxReq 0 -cip DISABLED

-usip YES -useproxyport NO -cltTimeout 120 -svrTimeout 120 -CKA NO -TCPB NO -CMP NO

Done > bind serviceGroup ingress_osn_service OSN1-ingress [-weight <positive_integer>] Done > bind serviceGroup ingress_osn_service OSN2-ingress [-weight <positive_integer>] Done > bind serviceGroup ingress_osn_service OSN3-ingress [-weight <positive_integer>] Done > add service server1service server1 ANY * -gslb NONE -maxClient 0 -maxReq 0 -cip

DISABLED -usip YES -useproxyport NO -sp OFF -cltTimeout 120 -svrTimeout 120 -CKA NO -TCPB NO -CMP NO

Done

The optional [-weight <positive_integer>] parameter allows for integer values in the [1 ... 100] range and should only be used in non-uniform Unison clusters — for example, a mixed cluster with both IBM HS22 and HS23 blades. Its purpose is to reflect the relevant traffic handling capability of the respective node.

Note that the relevant ratio depends not only on the hardware mix but additional parameters like traffic profile, optimizations applied, subscriber device mix, and so on. In case of a mixed Unison cluster one should use the Bytemobile capacity calculator to gauge the respective capacity of each hardware node, then adjust the weights configured on the T1000.

T-Series Traffic Director Installation, Configuration and Administration Guide 3-19

Chapter 3 Basic T1000/Unison Load-Balancing Configuratio n

To create services for Server Load Balancing from the CLI:

Server load balancing pools typically listen to specific service ports. For instance, a pool of HTTP servers typically handles requests to port 8080 (TCP port configured as explicity-proxy port on the OSN) while a pool of HTTP proxy servers typically handles request to port 3128.

The following example applies server load balancing to port 8080 of the OSN ingress servers, and applies server load balancing to the T1000 egress servers.

>add service ingress1proxy OSN1-ingress HTTP 8080 -gslb NONE -maxClient 0 -maxReq 0 -cip DISABLED -usip YES -useproxyport NO -sp OFF -cltTimeout 180 -svrTimeout 360

-CKA NO -TCPB NO -CMP NO

Done >add service ingress2proxy OSN2-ingress HTTP 8080 -gslb NONE -maxClient 0 -maxReq

0 -cip DISABLED -usip YES -useproxyport NO -sp OFF -cltTimeout 180 -svrTimeout 360

-CKA NO -TCPB NO -CMP NO

Done >add service ingress3proxy OSN3-ingress HTTP 8080 -gslb NONE -maxClient 0 -maxReq

0 -cip DISABLED -usip YES -useproxyport NO -sp OFF -cltTimeout 180 -svrTimeout 360

-CKA NO -TCPB NO -CMP NO

Done >add service server1service server1 ANY * -gslb NONE -maxClient 0 -maxReq 0 -cip

DISABLED -usip YES -useproxyport NO -sp OFF -cltTimeout 120 -svrTimeout 120 -CKA NO -TCPB NO -CMP NO

Done

Creating Virtual Servers

After creating services, a virtual server must be created to accept traffic for the load balanced servers. The following examples show how to defines services per server for firewall or server load balancing.

To create virtual servers for Firewall Load Balancing from the CLI:

For firewall load balancing, the add lb vserver has the following syntax for adding a virtual server:

add lb vserver name serviceType [(IPAddress port [-range positive_integer]) |

(-IPPattern ippat -IPMa sk ipmask)] [-persistenceType persistenceType] [-lbMethod lbMethod] [-Listenpolicy expression] [-m m] [-cltTimeout secs] [-l2Conn {ON | OFF}]

The following example creates a pair of virtual servers for the two ingress interfaces, using the roundrobin load balancing method.

> add lb vserver Ingress ANY * * -persistenceType SOURCEIP -lbMethod ROUNDROBIN

-timeout 30 -Listenpolicy "CLIENT.VLAN.ID.EQ(151)" -Listenpriority 1 -m MAC

-cltTimeout 120 -l2Conn ON

Done > add lb vserver Egress ANY * * -persistenceType SOURCEIP -lbMethod ROUNDROBIN

-Listenpolicy "CLIENT.VLAN.ID.EQ(200)" -Listenpriority 2 -m MAC -cltTimeout 120

-l2Conn ON

Done

The T1000 supports advanced listen policies. For example, if one wants to push just HTTP and ICMP traffic to the Unison cluster, while bypassing the rest of the traffic adjust the ingress vserver listen policy accordingly. For example (optional):

3-20 T-Series Traffic Director Installation, Configuration and Administration Guide

Configuring T1000 Load Balancing

> add lb vserver Ingress ANY * * -persistenceType SOURCEIP -lbMethod ROUNDROBIN

-timeout 30 -Listenpolicy "CLIENT.VLAN.ID.EQ(151) && (CLIENT.TCP.DSTPORT.EQ(80) || CLIENT.IP.PROTOCOL.EQ(ICMP))" -Listenpriority 1 -m MAC -cltTimeout 120 -l2Conn ON

Done

Use the bind lb vserver command to bind the virtual servers to the physical services. The bind lb vserver has the following syntax for this purpose:

bind lb vserver name serviceName

For example:

> bind lb vserver Ingress ingress_osn_service Done > bind lb vserver Egress server1service Done

To create virtual servers for server load balancing from the CLI:

For server load balancing, the add lb vserver has the following syntax for adding a virtual server:

add lb vserver name serviceType [{IPAddress port} [-persistenceType

persistenceType] [-cltTimeout secs] [-l2Conn {ON | OFF}]

The following example creates a virtual server as an HTTP proxy:

>add lb vserver proxy HTTP 12.13.14.15 3128 -persistenceType NONE -cltTimeout 180

-l2Conn ON

Done

Use the bind lb vserver command to bind the virtual servers to the physical services. The bind lb vserver has the following syntax for this purpose:

bind lb vserver name serviceName

For example:

>bind lb vserver proxy ingress1proxy Done >bind lb vserver proxy ingress2proxy Done >bind lb vserver proxy ingress3proxy Done

T-Series Traffic Director Installation, Configuration and Administration Guide 3-21

Chapter 3 Basic T1000/Unison Load-Balancing Configuratio n

Configuring Health Checks and Redundancy

Once load balancing is configured, the T1000s require additional configurations to monitor the health of the OSNs, to define a minimum operating threshold, and to specify the T1000 failover behavior for redundancy.

• “Configuring Health Monitors” on page 3-22

• “Configuring Minimum Servers and Backup Path” on page 3-24

• “Configuring Failover Redundancy” on page 3-24

• “Configuring Route Monitors in HA Mode” on page 3-25

Configuring Health Monitors

The T1000 provides health monitors to verify the proper operation of OSN servers. A health monitor typically tests a device for an expected response within a specified time interval and marks it as unhealthy in case of a failure. The sample configuration defines an HTTP health check at port 5100 with these options:

• The health check is performed every 5 seconds.

• Three consecutive failed health check attempts are required before declaring a

previously healthy server as inoperative

• One consecutive successful health check attempts are required before declaring a

previously inoperative server as healthy

• The duration for which the system waits to make the next probe once the service is

marked as down is 30 seconds.

The add lb monitor has the following syntax for this purpose.

add lb monitor monitorName type [-respCode int[-int] ...] [-httpRequest string]

[-LRTM {ENABLED | DISABLED}] [-destIP ip_addr] [-destPort port ]

For example, to add the health monitor to the ingress ports of all the OSNs in the sample configuration (Unison Release 6.0 or higher only

>add lb monitor "Watchdog Port 5100" HTTP -respCode 200 -httpRequest "HEAD /"

-LRTM ENABLED -destPort 5100

Done

Another less typical example is the requirement for a passthrough monitor that can verify the L3 health of both the ingress and egress interfaces of an OSN:

> add lb monitor passthrough-icmp PING -LRTM DISABLED -destIP 169.254.64.100

-transparent YES

Done

1. For Unison releases prior to 6.0, HTTP Request "GET /\r\nJunk:" must be used in place of

"HEAD /". This workaround is required because T1000 appends HTTP/1.0 onto the string,

causing the watchdog process to always return 200.

3-22 T-Series Traffic Director Installation, Configuration and Administration Guide

Configuring Health Checks and Redundancy

After adding the health monitors, you must use the bind lb monitor command to bind each monitor to the relevant services. The bind lb monitor command has the following syntax:

bind lb monitor monitorName {{ serviceName [-state {ENABLED | DISABLED}]

[-weight positive_integer]} | {{serviceGroupName [-state {ENABLED | DISABLED}] [-weight positive_integer]} | {-metric string -metricThreshold positive_integer [-metricWeight positive_integer]}}}

For firewall load balancing, use ARP to monitor the Internet-side services and the newly created monitors for each of the ingress interfaces:

> bind lb monitor "Watchdog Port 5100" ingress_osn_service Done > bind lb monitor arp server1service Done > bind lb monitor "Watchdog Port 5100" ingress3proxy Done > bind lb monitor "Watchdog Port 5100" ingress2proxy Done > bind lb monitor "Watchdog Port 5100" ingress1proxy Done

T-Series Traffic Director Installation, Configuration and Administration Guide 3-23

Chapter 3 Basic T1000/Unison Load-Balancing Configuratio n

Configuring Minimum Servers and Backup Path

When a configured percentage of services bound to a virtual server have failed, it is desirable to have all subsequent client requests sent to a backup virtual server. If the remaining services cannot handle the load, it is typically better to bring down the entire virtual server and send all client requests to a backup virtual server.

The following procedures describe how to bypass the cluster in a Firewall Load Balancing setup if less than two of three OSN blades are healthy.

Adjust the vserver listen policy to factor in the total cluster health threshold. The cluster health threshold is calculated by subtracting one from the minimum servers, then rounding up. For example in a 3-OSN cluster where at least two nodes should remain active at any given time, the cluster health threshold percentage is 34% (1/3 = 33.3%)

> set lb vserver Ingress -listenpolicy "CLIENT.VLAN.ID.EQ(151) && (SYS.VSERVER(\"Ingress\").HEALTH.GT(34))"

Done

Configuring Failover Redundancy

The T1000 pair exposes a single Layer-3 virtual IP address to next hop routers, allowing for redundancy and failover. One T1000 is designated the primary and the other is the secondary.

The configuration in this section assumes the following:

• There are two T1000 load balancers for the Unison cluster.

• The basic management configuration has been performed on both T1000s (see

Chapter 2, “Accessing and Configuring the Management Plane.”

• All data plane cabling has been installed on both T1000s.

• The primary T1000 has been fully configured using the procedures in this document.

Use the add HA node and set HA node commands to configure the T1000 for High Availability. These commands have the following syntax:

add HA node id IPAddress

set HA node [-haStatus haStatus] [-haSync {ENABLED | DISABLED}] [-haProp

{ENABLED | DISABLED}] [-helloInterval msecs] [-deadInterval secs] [-failSafe {ON | OFF}]

The helloInterval is the interval in milliseconds at which the heartbeat messages are sent to the peer node. The heartbeat messages are UDP packets sent to port 3003 of the other node in an HA pair. Values for the hello interval must be in the range 200ms to 1000ms. The default hello interval is 200ms. The deadInterval is the time interval in seconds after which the peer node is marked DOWN if heartbeat packets are not received. The default dead interval is 3s. Values must be in the range 3s to 60s.

For example:

>add HA node 1 10.8.130.32 Done

1. Failover redundancy requires up to 20Mbps of traffic under standard operations for synchronization of the load balancer persistence table.

3-24 T-Series Traffic Director Installation, Configuration and Administration Guide

Configuring Health Checks and Redundancy

>set HA node -haStatus ENABLED Done >set HA node -helloInterval 200 -deadInterval 3 Done >set HA node -haSync ENABLED Done

The following extra configuration is required only for the T1000-2, which is by default the secondary:

>add HA node 1 10.8.130.31 Done >set HA node -helloInterval 200 -deadInterval 3 Done >set HA node -haSync ENABLED Done

T1000s on Separate Networks

If the nodes in an HA pair reside on two separate networks, the primary and secondary node must have independent network configurations. This means that nodes on different networks cannot share entities such as MIPs, SNIPs, VLANs and routes. This type of configuration, where the nodes in an HA pair have different configurable parameters, is known as Independent Network Configuration (INC) or Symmetric Network Configuration (SNC). As in configuring HA nodes in the same subnet, to configure HA-INC nodes you log on to each of the two T1000 appliances and add a remote node representing the other appliance. For instance, if NSIP address of T1000-2 is 192.168.1.100, you can configure HA-INC as follows:

>add HA node 1 192.168.1.100 -inc ENABLED Done >set HA node -haStatus ENABLED Done >set HA node -helloInterval 200 -deadInterval 3 Done >set HA node -haSync ENABLED Done

Note: Verify L3 connectivity between the two nodes to ensure that heartbeat packets

are sent and received successfully.

Configuring Route Monitors in HA Mode

An additional requirement that frequently applies to a pair of T1000 units configured for high-availability (active-failover) is to have them respond to external router failures. For example, assuming the reference deployment in Figure 3-2, consider the following sequence of events:

1. T1000-1 is primary, T1000-2 is secondary.

2. A failure of some sorts interrupts the communication of T1000-1 with th e next hop

wireless router at 172.16.112.65.

3. The secondary T1000-2 could theoretically communicate with the wireless router

since the relevant Layer-2 path is intact.

T-Series Traffic Director Installation, Configuration and Administration Guide 3-25

Chapter 3 Basic T1000/Unison Load-Balancing Configuratio n

The above sequence of events would effectively cause the cluster to be inoperable. Wireless clients are unreachable, since the active T1000 cannot communicate to them, and there is no hard failure that would result in a failover event to T1000-2 and restore said communication.

This issue can be alleviated with the introduction of route monitors and associating them with the HA node status.

First, introduce one route monitor for each of the next hop routers. In most cases next-hop routers will disallow or throttle ICMP messages so an ARP monitor is recommended:

> add route 172.16.112.0 255.255.255.0 172.16.112.65 -msr ENABLED -monitor arp Done > add route 172.16.113.0 255.255.255.0 172.16.113.65 -msr ENABLED -monitor arp Done

Afterwards, bind these to monitors to the HA node status:

> bind HA node -routeMonitor 172.16.112.0 255.255.255.0 Done > bind HA node -routeMonitor 172.16.113.0 255.255.255.0 Done

These commands will allow the primary T1000 to constantly monitor the next hop routers. In case of a failure to communicate with any of them a failover event will be initiated to the secondary unit.

Configuring Source NAT (SNAT)

The T1000 allows for source NAT (SNAT) of traffic in order to change the subscriber's private IP address/port into a public IP address/port for packets leaving the network, preventing Internet servers from responding directly to the clients. Specifically, when the T1000 receives a request from the client, and if the client IP address in the request is defined for SNAT, the system translates the source IP address of the incoming packet to the SNAT address, which will be one of the configured egress IP addresses.

Note: This SNAT configuration supports only L3-L4, and will work with TCP and

UDP protocols. It does not support any application layer features that require L7 NAT intelligence.

SNAT configuratio n leverages the net profile and vserver features of the T1000. The following configuration enables SNAT for all client traffic, mapping the 256K private IP address range (10.200.0.0/15) to sixteen public IP addresses (172.16.113.(1-16)). This configuration has the following steps:

1. Create a net profile that maps to the public IPs you want to use.

2. Bind net profile to the existing egress-side service.

3. Create bypass ingress-side-vserver.

This steps are described in the sections that fo llow.

3-26 T-Series Traffic Director Installation, Configuration and Administration Guide

Citrix ByteMobile T1010, ByteMobile T1100, ByteMobile T1200 Installation, Configuration And Administration

Specifications and Main Features

Frequently Asked Questions

User Manual

T-Series Traffic Director Install, Admin & Config Guide

Safety

Before Installing

Safety Statements

Statement 1

Statement 3

Statement 8

Statement 12

Statement 13

Statement 29 (DC Models Only)

Statement 31

Statement 33

Statement 34

Fiber Optic Safety Information, Statement 1

Table of Contents

About This Guide

Objective

Audience

Organization

T-Series Related Documents

Unison Related Documents

Citrix NetScaler Documents

Revision History

Document Conventions

Notices and Statements in this Document

Documentation Feedback

Technical Assistance

1. Introduction

Traffic Director Architecture

Sizing a T1000/Unison Deployment

Sizing T1000/T3100 Deployments

Product Capabilities

Load Sensitive Traffic Distribution

Intelligent Overload Protection

Carrier-Grade Redundancy

High Performance

Deployment Flexibility

T1000 Software Packages

T1000 Hardware Specifications and Options

T1000 Technical Specifications

Layer 4 to 7 Traffic Management

Layer 7 Content Switching

Application Security

User Interface

Network Integration

Hardware Overview

Model T1010 Hardware

Model T1100 Hardware

Model T1200 Hardware

Common Hardware Features

LCD Display

Booting Screen

Startup Screen

Out-of-Service Screen

Configuration Screen

Alert Screen

HTTP Statistics Screen.

Network Traffic Statistics Screen.

CPU Load, Memory, and Connections Screen

Port Information Screen

Ports

RS232 Serial Port

Management Ports

1 Gbps SFP Ports

10 Gbps SFP+ Ports

Port Status Indicators

Power Supply

Compact Flash Card

Solid-State Drive

Hard Disk Drive

2. Installation

Overview of Installing T1000

Cautions and Warnings

Electrical Safety Precautions

T1000 Precautions

Rack Precautions