sdx 5 - docs.citrix.com · 6 sdx 5.6 citrix® repeater for netscaler® sdx is a high-performance...

SDX 5.6

2015-03-01 03:41:54 UTC

© 2015 Citrix Systems, Inc. All rights reserved. Terms of Use | Trademarks | Privacy Statement

http://www.citrix.com/about/legal/legal-notice.html

http://www.citrix.com/about/legal/brand-guidelines.html

http://www.citrix.com/about/legal/privacy.html

Contents

SDX 5.6.......................................................................................................... 6

SDX 5.6............................................................................................. 7

Release Notes ............................................................................... 8

About Repeater 500/1000 for NetScaler SDX ..................................... 9

Differences Between Repeater and Repeater for SDX........................... 10

About This Release.................................................................... 11

Known Issues ........................................................................... 12

Hardware Installation ...................................................................... 13

Introduction to the Hardware Platforms........................................... 14

Common Hardware Components .............................................. 15

Ports.......................................................................... 16

Field Replaceable Units ................................................... 18

Power Supply .......................................................... 19

Solid-State Drive ...................................................... 23

Hard Disk Drive ........................................................ 25

Hardware Platforms ............................................................. 26

Citrix Repeater 310/500/1000 on SDX .................................. 27

Citrix Repeater 1500/2000 on SDX....................................... 29

Summary of Hardware Specifications......................................... 31

Preparing for Installation ............................................................ 34

Before you Begin................................................................. 35

Preparing the Site and Rack.................................................... 36

Cautions and Warnings .......................................................... 38

Installing the Hardware .............................................................. 40

Rack Mounting the Appliance .................................................. 41

Installing and Removing 1G SFP Transceivers ............................... 46

Installing and Removing 10G SFP+ Transceivers ............................ 49

Install Fiber Patch Cable in Ports 10/3 and 10/4 ........................... 51

Connecting the Cables .......................................................... 53

2

Switching on the Appliance .................................................... 55

Lights Out Management Port of the Repeater on SDX Appliance .............. 56

Initial Configuration ........................................................................ 59

Configuration Requirements......................................................... 60

Initial Configuration through the Management Service User Interface ....... 61

Configuring the LOM Port ............................................................ 63

Getting Started with the Management Service User Interface ...................... 64

Logging on to the Management Service User Interface.......................... 65

Provisioning a NetScaler Instance and the Repeater Instances ................ 66

Administration .............................................................................. 67

Introduction ............................................................................ 68

Load Balancing......................................................................... 71

Managing the Home Page ............................................................ 74

Managing and Monitoring the SDX Appliance...................................... 76

Modifying the Network Configuration of the SDX Appliance .............. 77

Changing the Password of the Default User Account....................... 78

Viewing the SSL Certificate on the Management Service.................. 79

Modifying the Time Zone on the Appliance.................................. 80

Modifying System Settings ...................................................... 81

Restarting the Appliance ....................................................... 82

Shutting Down the Appliance .................................................. 83

Managing Interfaces ............................................................. 84

Display the Mapping of Virtual Interfaces on the VPX Instance tothe Physical Interfaces on the NetScaler SDX Appliance 86

Assigning a MAC Address to an Interface ............................... 88

Configuring Clock Synchronization ............................................ 91

Viewing the Properties of the SDX Appliance ............................... 94

Viewing Real-Time Appliance Throughput ................................... 97

Viewing Real-Time CPU and Memory Usage ................................. 98

Viewing CPU Usage for All Cores .............................................. 99

SNMP ............................................................................... 100

SNMP Trap Destinations ................................................... 101

Downloading MIB Files ..................................................... 102

Configuring the Management Service .............................................. 103

Managing Client Sessions ....................................................... 104

Configuring User Accounts...................................................... 105

Restarting the Management Service .......................................... 107

Upgrading the Management Service .......................................... 108

3

Uploading the Management Service Build and DocumentationFiles .......................................................................... 109

Upgrading the Management Service to a Later Version 111

Upgrading the XenServer Software............................................ 112

Uploading the XenServer Build Files..................................... 113

Upgrading the Software ................................................... 114

Backing Up and Restoring the Configuration Data of the SDX Appliance 115

Performing a Factory Reset .................................................... 116

Removing Management Service Files ......................................... 118

Generating a Tar Archive for Technical Support............................ 119

Provisioning the NetScaler Instance................................................ 120

Creating Admin Profiles......................................................... 121

Uploading NetScaler .Xva Images ............................................. 123

Adding a NetScaler Instance ................................................... 125

Provisioning the Repeater Instances ............................................... 127

Uploading Repeater .Xva Images .............................................. 128

Adding a Repeater Instance .................................................... 129

Configuring and Managing the NetScaler Instance ............................... 131

Saving the Configuration........................................................ 132

Upgrading a NetScaler Instance ............................................... 133

Uploading NetScaler Resources .......................................... 134

Managing a NetScaler Instance ................................................ 136

Removing NetScaler Instance Files............................................ 137

Configuring and Managing the Repeater Instances............................... 138

Configuring a Repeater Instance .............................................. 139

Upgrading a Repeater instance ................................................ 140

Managing a Repeater Instance ................................................. 141

Monitoring the NetScaler Instance.................................................. 142

Viewing the Properties of the NetScaler Instance .......................... 143

Viewing the Running and Saved Configuration of a NetScaler Instance 144

Pinging a NetScaler Instance................................................... 145

Tracing the Route of a NetScaler Instance................................... 146

Rediscovering a NetScaler Instance........................................... 147

Monitoring the Repeater Instance .................................................. 148

Viewing the Properties of the Repeater Instances ......................... 149

Viewing the Running and Saved Configuration of a Repeater Instance 152

Pinging a Repeater Instance ................................................... 153

Tracing the Route of a Repeater Instance ................................... 154

4

Rediscovering Instance.......................................................... 155

Using Logs to Monitor Operations and Events..................................... 156

Viewing Audit Logs............................................................... 157

Viewing Task Logs ............................................................... 159

Viewing Events ................................................................... 161

5

6

SDX 5.6

Citrix® Repeater for NetScaler® SDX is a high-performance WAN accelerator for busydatacenters that combines multiple virtual instances of the Repeater appliance with asingle virtual instance of the NetScaler load-balancer, providing the performance ofmultiple Repeater appliances in a single package. Combining the virtual Repeaters with aNetScaler allows great flexibility in deployment. Through the use of the on-boardNetScaler, the virtual Repeaters can be dedicated individually to specific WAN traffic orused in a load-balanced configuration.

About This ReleaseThis is the initial release of the Repeater for SDX hardware and software. For a summary ofthe updates, see the Citrix Repeater for NetScaler SDX Release Notes - Repeater Release5.6.3/NetScaler Release 9.3.

Note: The product documentation you are looking for is not yet in eDocs (this site) andstill resides in the Citrix Knowledge Center. For links to documentation in the CitrixKnowledge Center, go to: http://support.citrix.com/pages/docs/

Important: When you click this link you will leave this site. We recommend that youbookmark this site so you can easily return to it.

http://support.citrix.com/pages/docs/

7

Release Notes

Repeater for NetScaler SDX is an appliance containing multiple virtual Repeater WANaccelerators controlled by a single virtual NetScaler load balancer. This combinationprovides a high-performance WAN accelerator for busy datacenters.

The Repeater for NetScaler SDX hardware is a high-performance 2U server with twoavailable 10 Gbps ports and ten 1 Gbps ports. The Repeater instances are all managedindependently, and the NetScaler instance can apportion WAN traffic between them in anyway desired, for maximum flexibility.

The two models are:

• Repeater 500 for NetScaler SDX 11505, which supports three Repeater instances andWAN speeds of up to 500 Mbps.

• Repeater 1000 for NetScaler SDX 13505, which supports six Repeater instances and WANspeeds of up to 1 Gbps.

The two models share an identical hardware platform, allowing a Repeater 500 to beupgraded to a Repeater 1000, by using Citrix’ “Pay-as-You-Grow” licensing model.

The Repeater instances run Repeater release 5.6.3, while the NetScaler instance runsNetScaler release 9.3.e.

8

Release Notes



The two models are:





9

About Repeater 500/1000 for NetScalerSDX



The two models are:





10

Differences Between Repeater andRepeater for SDX

New Features for Repeater for SDX• Multiple virtual Repeater instances.

• Load balancing through a virtual NetScaler instance.

• Faster hardware platform.

• SSD-based disks for maximum compression performance.

• 10 Gbps interfaces.

Repeater Features Not Supported on Repeater forSDX

Some features of the Repeater appliances are not supported in Repeater SDX. Theseinclude:

• Group mode.

• WCCP mode.

• Hardware bypass mode.

• Repeater high-availability mode (HA)(NetScaler HA is supported.)

• The Repeater Plug-in.

11

About This Release

This is the initial release of the Repeater for SDX hardware and software.

Installation and Configuration• See the Citrix Repeater 500/1000 for NetScaler SDX 11505/13505 Quick Start Guide for

initial installation instructions (physical and electrical installation up to the point ofusing the management interface).

• See the Citrix Repeater for SDX Administration Guide for additional configuration.

See also:

• Branch Repeater Family User’s Guide, rel. 5.5-5.7.

• NetScaler family product documentation.

12

Known Issues

Issues are listed in reverse numerical order (newest items first).

• 261943:

Description: If the Repeater “reset to factory defaults” feature is used, the SNMPconfiguration used by the service VM is lost, and the service VM is unable to completean inventory of the Repeater instance.

Recommended action: Do not use the Repeater’s “reset to factory defaults” feature.Delete the instance and create a new one instead.

• 261662:

Description: If a Repeater instance is created with a name that contains one or morespace characters, the name cannot be modified.

Recommended action: Use names that do not contain spaces.

• 261628:

Description: After upgrading multiple Repeater instances to a new version of theRepeater VM, sometimes an instance does not restart automatically.

Recommended action: Start the instance manually from the service VM.

• 260049:

Description: After deleting a Repeater instance, the SDX appliance must be restartedfor the change to be implemented reliably. This reboot must take place before anyadditional configuration is performed.

Recommended action: Always reboot the SDX appliance after deleting a Repeaterinstance. (Deleting an instance is rarely necessary).

• 260023:

Description: If the network parameters of a newly created Repeater instance arechanged before the service VM has completed its inventory, a deadlock may occur. Inthat event, the deadlock can be fixed only by deleting and recreating the Repeaterinstance.

Recommended action: Do not configure a Repeater instance through its browser-basedinterface or command-line interface until after the inventory is complete. This processtakes about seven minutes. The inventory is complete when the service VM shows agreen status for both the “VM state” and “Instance state” of the Repeater VM. Expandthe instance to verify that the “Status” line shows “Inventory from BR InstanceCompleted.”

13

Hardware Installation

The following sections describe the hardware installation for all Repeater on SDX hardwareplatforms.

Introduction to the Hardware Platforms Describes the Repeater on SDX hardwareplatforms and provides detailedinformation about each platform and itscomponents.

Preparing for Installation Describes how to unpack the Repeater onSDX appliance and prepare the site andrack for installing the appliance. Lists thecautions and warnings that you shouldreview before you install the appliance.

Installing the Hardware Describes the steps to install the rails,mount the hardware, connect the cables,and turn on the appliance.

14

Introduction to the Hardware Platforms

Citrix Repeater on SDX appliances are the highest-performing products in Citrix BranchRepeater Product line. The appliances achieve this performance by combining a NetScalerVPX load balancer with three to eight Repeater instances, all in a single high-performanceserver that meets the needs of busy datacenters.

15

Common Hardware Components

Each platform has front panel and back panel hardware components. The front panel has anLCD display and an RS232 serial console port. The number, type, and location ofports—copper Ethernet, copper and fiber 1G SFP and 10G SFP+—vary by hardware platform.The back panel provides access to the fan and the field replaceable units (power supplies,and solid-state and hard-disk drives).

The front panel of the Command Center appliance has RS232 serial ports and10/100/100Base-T copper Ethernet ports. The back panel provides access to the powersupply, fan, CompactFlash card, and hard-disk drive.

16

Ports

Note: Some Repeater on SDX appliances do not require SFP transceivers.

Ports are used to connect the appliance to external devices. Citrix Repeater on SDXappliances support RS232 serial ports, 10/100/1000Base-T copper Ethernet ports, fiber 1GSFP ports and 10-gigabit fiber SFP+ ports. All Citrix Repeater on SDX appliances have acombination of some or all of these ports. For details on the type and number of portsavailable on your appliance, see the section describing that platform.

RS232 Serial PortThe RS232 serial console port on the front panel of eachthe appliance provides a connectionbetween the appliance and a computer, allowing direct access to the appliance for initialconfiguration or troubleshooting.

All hardware platforms ship with an appropriate serial cable used to connect your computerto the appliance. For instructions on connecting your computer to the appliance, seeInstalling the Hardware.

Copper Ethernet PortsThe copper Ethernet ports installed on the appliances are standard RJ45 ports.

10/100/1000BASE-T port

The 10/100/1000BASE-T port has a maximum transmission speed of 1 gigabit per second,ten times faster than the other type of copper Ethernet port.

To connect any of these ports to your network, you plug one end of a standard Ethernetcable into the port and plug the other end into the appropriate network connector.

Note: These ports are not used in the current release.

Management PortsManagement ports are standard copper Ethernet ports (RJ45), which are used for directaccess to the appliance for system administration functions.

Note: Use the management port numbered 0/1 to get direct access to the appliance.

1G SFP and 10G SFP+ PortsA 1G SFP port can operate at a speed of 1 Gbps. It accepts either a copper 1G SFPtransceiver, for operation as a copper Ethernet port, or a fiber 1G SFP transceiver foroperation as a fiber optic port.

The 10G SFP+ ports are high-speed ports that can operate at speeds of up to 10 Gbps. Youneed a fiber optic cable to connect to a 10G SFP+ port.

LED Port-Status IndicatorsThe port LEDs show whether the link is established and traffic is flowing through the port.For information about the LED indicators for each card type, see Networking BypassAdapters.

Ports

17

http://www.silicom-usa.com/10_Gigabit_Ethernet_Bypass_Networking_Server_Adapters

http://www.silicom-usa.com/10_Gigabit_Ethernet_Bypass_Networking_Server_Adapters

18

Field Replaceable Units

Citrix Repeater on SDX field replaceable units (FRU) are components that can be quicklyand easily removed from the appliance and replaced by the user or a technician at theuser's site. The FRUs in a Citrix Repeater on SDX appliance can include DC or AC powersupplies, and solid-state and hard-disk drives.

Note: By default the appliance ships with AC power supplies. DC power supply isorderable.

19

Power Supply

Citrix Repeater on SDX appliances are configured with dual power supplies but can operatewith only one power supply. The second power supply serves as a backup.

For power-supply specifications, see Hardware Platforms, which describes the variousplatforms and includes a table summarizing the hardware specifications.

The MPX 7500 appliance ships with a dual power supply configuration, including twostandard power cords that each have a NEMA 5-15 plug for connecting to the power outleton the rack or in the wall.

Table 1. LED Power Supply Indicators

Power Supply Type LED Color LED Indicates

AC OFF No power to any powersupply.

Flashing RED No power to this powersupply.

Flashing GREEN Power supply is in standbymode.

GREEN Power supply is functional.

RED Power supply failure.

DC OFF No power to any powersupply.


Flashing BLUE Power supply is in standbymode.

BLUE Power supply is functional.

RED Power supply failure.Table 2. LED Power Supply Indicators

Power Supply Type LED Color LED Indicates

AC OFF No power to any powersupply.


Flashing GREEN Power supply is in standbymode.

GREEN Power supply is functional.

RED Power supply failure.

Electrical Safety Precautions for Power SupplyReplacement

• Make sure that the appliance has a direct physical connection to earth ground duringnormal use. When installing or repairing an appliance, always connect the groundcircuit first and disconnect it last.

• Always unplug any appliance before performing repairs or upgrades.

• Never touch a power supply when the power cord is plugged in. As long as the powercord is plugged in, line voltages are present in the power supply even if the powerswitch is turned off.

Replacing an AC Power SupplyReplace an AC power supply with another AC power supply. All power supplies must be ofthe same type (AC or DC).

Note: You can replace one power supply without shutting down the appliance, providedthe other power supply is working.

To install or replace an AC power supply on a Citrix Repeater on SDX appliance

1. Align the semicircular handle perpendicular to the power supply. Loosen thethumbscrew and press the lever toward the handle and pull out the existing powersupply, as shown in the following figure.

Figure 1. Removing the Existing AC Power Supply

2. Carefully remove the new power supply from its box.

3. On the back of the appliance, align the power supply with the power supply slot.

4. Insert the power supply into the slot and press against the semicircular handle until youhear the power supply snap into place.

Power Supply

20

Figure 2. Inserting the Replacement AC Power Supply

5. Connect the power supply to a power source. If connecting all power supplies, plugseparate power cords into the power supplies and connect them to separate wallsockets.

Note: Repeater on SDX appliances emit a high-pitched alert if one power supply fails or ifyou connect only one power cable to an appliance in which two power supplies areinstalled. To silence the alarm, press the small red button on the back panel of theappliance. The disable alarm button is functional only when the appliance has two powersupplies.

Replacing a DC Power SupplyReplace a DC power supply with another DC power supply. All power supplies must be ofthe same type (AC or DC).

Note: You can replace one power supply without shutting down the appliance, providedthe other power supply is working.

To install or replace a DC power supply on a Citrix Repeater on SDX appliance

1. Loosen the thumbscrew and press the lever towards the handle and pull out the existingpower supply, as shown in the following figure.

Figure 3. Removing the Existing DC Power Supply2. Carefully remove the new power supply from its box.

3. On the back of the appliance, align the power supply with the power supply slot.

4. Insert the power supply into the slot while pressing the lever towards the handle. Applyfirm pressure to insert the power supply firmly into the slot.

Power Supply

21

Figure 4. Inserting the Replacement DC Power Supply5. When the power supply is completely inserted into its slot, release the lever.

6. Connect the power supply to a power source. If connecting all power supplies, plugseparate power cords into the power supplies and connect them to separate wallsockets.

Note: Repeater on SDX appliances emit a high-pitched alert if one power supply fails or ifyou connect only one power cable to an appliance in which two power supplies areinstalled. To silence the alarm, press the small red button on the back panel of theappliance. The disable alarm button is functional only when the appliance has two powersupplies.

Power Supply

22

23

Solid-State Drive

A solid-state drive (SSD) is a high-performance data storage device that stores data insolid-state flash memory.

Replacing a Solid-State DriveThe Repeater on SDX software is stored on the solid-state drive (SSD).

To replace a solid-state drive

1. Locate the SSD on the back panel of the appliance. Push the safety latch of the drivecover to the right or down, depending on the platform, while pulling out on the drivehandle to disengage. Pull out the faulty drive.

Figure 1. Removing the Existing Solid-State Drive

2. Verify that the replacement SSD is the correct type for the platform.

3. Pick up the new SSD, open the drive handle fully to the left or up, and insert the driveinto the slot as far as possible. To seat the drive, close the handle flush with the rear ofthe appliance so that the drive locks securely into the slot.

Important: When you insert the drive, make sure that the Citrix product label is atthe top if the drive is inserted horizontally or at the right if the drive is insertedvertically.

Figure 2. Inserting the Replacement Solid-State Drive

4. Turn on the appliance.

5. Log on to the default IP address by using a web browser, or connect to the serialconsole by using a console cable, to perform the initial configuration.

Solid-State Drive

24

25

Hard Disk Drive

The NetScaler and Branch Repeater virtual machines are hosted on the hard-disk drive. Thehard disk drive contains user monitored data. It is mounted as /var.

Replacing a Hard Disk DriveVerify that the replacement hard disk drive is the correct type for the Repeater on SDXplatform.

To install a hard disk drive

1. Shut down the appliance.

2. Locate the hard disk drive on the back panel of the appliance.

3. Disengage the hard disk drive by pushing the safety latch of the drive cover to the rightor down, depending on the platform, while pulling out on the drive handle todisengage. Pull out the faulty drive.

Figure 1. Removing the Existing Hard Disk Drive

4. Pick up the new disk drive, open the drive handle fully to the left, and insert the newdrive into the slot as far as possible. To seat the drive, close the handle flush with therear of the appliance so that the hard drive locks securely into the slot.

Important: When you insert the drive, make sure that the Citrix product label is atthe top.

Figure 2. Inserting the Replacement Hard Disk Drive

5. Turn on the appliance.

26

Hardware Platforms

The Repeater on SDX hardware platforms offer a wide range of features, communicationports, and processing capacities. All platforms have multicore processors.

27

Citrix Repeater 310/500/1000 on SDX

Citrix Repeater 310/500/1000 on SDX are 2U appliances. Each model has two 6-coreprocessors for a total of 12 physical cores (24 cores with hyper-threading), and 48 gigabytes(GB) of memory. The Citrix Repeater 310/500/1000 on SDX have a bandwidth of 310Mbps,500Mbps, and 1Gbps, respectively.

The following figures shows the front panel of the Citrix Repeater 310/500/1000 on SDXappliance.

Figure 1. Citrix Repeater 310/500/1000 on SDX, front panel (without FTW cards)

Figure 2. Citrix Repeater 310/500/1000 on SDX, front panel (with FTW cards)

The Citrix Repeater 310/500/1000 on SDX appliances have the following ports:

• 10/100Base-T copper Ethernet Port (RJ45), also called LOM port. You can use this portto remotely monitor and manage the appliance independently of the appliance'ssoftware.

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

• RS232 serial console port.

• Two 10/100/1000Base-T copper Ethernet management ports (RJ45). These ports areused to connect directly to the appliance for system administration functions.

• Network Ports

• Repeater 310/500/1000 on SDX (without FTW cards). Eight 1G SFP ports and four10G SFP+ ports.

• Repeater 310/500/1000 on SDX (with FTW cards). Eight 1G copper Ethernet portsand four 10G ports.

The following figure shows the back panel of the Citrix Repeater 310/500/1000 on SDXappliance.

Figure 3. Citrix Repeater 310/500/1000 on SDX, back panel

The following components are visible on the back panel of the Citrix Repeater310/500/1000 on SDX appliance:

• Four 600 GB removable solid-state drives, which store the appliance's compressionhistory. The 256 GB solid-state drive below the hard disk drive stores the appliance'ssoftware.

• USB port (reserved for a future release).

• A 1 TB removable hard disk drive.

• Power switch, which turns off power to the appliance, just as if you were to unplug thepower supply. Press the switch for five seconds to turn off the power.

• Disable alarm button. This button is functional only when the appliance has two powersupplies.

Press this button to stop the power alarm from sounding when you have plugged theappliance into only one power outlet or when one power supply is malfunctioning andyou want to continue operating the appliance until it is repaired.

• Dual power supplies (either AC or DC), each rated at 850 watts, 100-240 volts.

Citrix Repeater 310/500/1000 on SDX

28

29

Citrix Repeater 1500/2000 on SDX

Citrix Repeater 1500/2000 on SDX are 2U appliances. Each model has two 6-core processorsfor a total of 12 physical cores (24 cores with hyper-threading), and 96 gigabytes (GB) ofmemory. The Citrix Repeater 1500/2000 on SDX have a bandwidth of 1.5Gbps and 2Gbpsrespectively.

The following figure shows the front panel of the Citrix Repeater 1500/2000 on SDXappliance.

Figure 1. Citrix Repeater 1500/2000 on SDX, front panel

The Citrix Repeater 1500/2000 on SDX appliance has the following ports:

• 10/100Base-T copper Ethernet Port (RJ45), also called LOM port. You can use this portto remotely monitor and manage the appliance independently of the appliance'ssoftware.

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

• RS232 serial console port.

• Two 10/100/1000Base-T copper Ethernet management ports (RJ45). These ports areused to connect directly to the appliance for system administration functions.

• Eight 10G ports.

The following figure shows the back panel of the Citrix Repeater 1500/2000 on SDXappliance.

Figure 2. Citrix Repeater 1500/2000 on SDX, back panel

The following components are visible on the back panel of the Citrix Repeater 1500/2000 onSDX appliance:

• Six 600 GB removable solid-state drives, which store the appliance's compressionhistory. The 256 GB solid-state drive next to the power supplies store the appliance'ssoftware.

• USB port (reserved for a future release).

• Power switch, which turns off power to the appliance, just as if you were to unplug thepower supply. Press the switch for five seconds to turn off the power.

• A 1 TB removable hard disk drive.

• Disable alarm button. This button is functional only when the appliance has two powersupplies.

Press this button to stop the power alarm from sounding when you have plugged theappliance into only one power outlet or when one power supply is malfunctioning andyou want to continue operating the appliance until it is repaired.

• Dual power supplies (either AC or DC), each rated at 650 watts, 100-240 volts.

Citrix Repeater 1500/2000 on SDX

30

31

Summary of Hardware Specifications

The following tables summarize the specifications of the Citrix Repeater on SDX hardwareplatforms.

Table 1. Citrix Repeater on SDX Appliances

CitrixRepeater310 on SDX


CitrixRepeater1000 onSDX

CitrixRepeater1500 onSDX


Platform Performance

Bandwidth 310 Mbps 500 Mbps 1.0 Gbps 1.5 Gbps 2.0 Gbps

Maximum HDXsessions

750 1,200 2,500 3,500 5,000

Total sessions 40,000 60,000 120,000 20,000 160,000

AccelerationPlug-in CCUs

1,100 1,800 3,000 3,600 4,800

Hardware Specifications

Processor Dual IntelE5645

Dual IntelE5645

Dual IntelE5645

Dual IntelX5680

Dual IntelX5680

Total disk space 3.2 TB 3.2 TB 3.2 TB 4.2 TB 4.2 TB

SSD (dedicatedcompressionhistory)

2 TB 2 TB 2 TB 3 TB 3 TB

HDD 1 TB 1 TB 1 TB 1 TB 1 TB

RAM 48 GB 48 GB 48 GB 96 GB 96 GB

Networkinterfaces

4 x 10GigESX and 8 x1GigE TXBypass

4 x 10GigESX and 8 x1GigE TXBypass*

4 x 10GigESX and 8 x1GigE TXBypass*

8 x10GigESR Bypass

8 x10GigESR Bypass

*See Citrix Repeater 310/500/1000 on SDX.

Transceiversupport

10GigESFP+; SR,LR

10GigESFP+; SR,LR

10GigESFP+; SR,LR

N/A N/A

Note: Some Repeater on SDX appliances do not have SFP transceivers and bypasscards.

Power supplies 2 2 2 2 2

Physical Dimensions

Rack units 2 2 2 2 2

System width EIA 310-D,IEC 60297,DIN 41494SC48D rackwidth withmountingbrackets

EIA 310-D,IEC 60297,DIN 41494SC48D rackwidth withmountingbrackets




System depth 25.4"/64.5cm

25.4"/64.5cm

25.4"/64.5cm

25.4"/64.5cm

25.4"/64.5cm

System weight 46 lbs (20.9kg)

46 lbs (20.9kg)

46 lbs(20.9 kg)

49 lbs (22.2kg)

49 lbs (22.2kg)

Shippingdimensions andweight

37” x 24”by 11”

59 lbs

94 x 61 x 28cm

26.8 kg

37” x 24”by 11”

59 lbs

94 x 61 x28 cm

26.8 kg

37” x 24”by 11”

59 lbs

94 x 61 x28 cm

26.8 kg

37” x 24”by 11”

61 lbs

94 x 61 x 28cm

27.7 kg

37” x 24”by 11”

61 lbs

94 x 61 x 28cm

27.7 kg

Environmental and Regulatory

Input voltageand frequencyranges

100-240VAC

47-63 Hz

100-240VAC

47-63 Hz

100-240VAC

47-63 Hz

100-240VAC

47-63 Hz

100-240VAC

47-63 Hz

Powerconsumption

650 watts2,200 BTUper hour.





Operatingtemperature

32–104° F

0–40° C

32–104° F

0–40° C

32–104° F

0–40° C

32–104° F

0–40° C

32–104° F

0–40° C

Operatingaltitude

0–4921'

(1,500 m)

0–4921'

(1,500 m)

0–4921'

(1,500 m)

0–4921'

(1,500 m)

0–4921'

(1,500 m)

Non-operatingtemperature

-4–140° F

20–60° C

-4–140° F

20–60° C

-4–140° F

20–60° C

-4–140° F

20–60° C

-4–140° F

20–60° C

Allowed relativehumidity

5%-95%, non-condensing





Safetycertifications

UL, TUV-C UL, TUV-C UL, TUV-C UL, TUV-C UL, TUV-C

Electromagneticemissionscertificationsandsusceptibilitystandards

FCC (Part15 Class A),DoC,

CE, VCCI,CNS,AN/NES


CE, VCCI,CNS,AN/NES

FCC (Part15 ClassA), DoC,

CE, VCCI,CNS,AN/NES


CE, VCCI,CNS,AN/NES


CE, VCCI,CNS,AN/NES


32

Environmentalcompliance

RoHS, WEEE RoHS,WEEE

RoHS,WEEE

RoHS, WEEE RoHS, WEEE


33

34

Preparing for Installation

Before you install your new appliance, carefully unpack your appliance and make sure thatall parts were delivered. Once you are satisfied that your appliance has been delivered toyour expectations, verify that the location where the appliance will be installed meetstemperature and power requirements and that the server cabinet or floor-to-ceiling cabinetis securely bolted to the floor and has sufficient airflow.

Only trained and qualified personnel should install, maintain, or replace the appliance, andefforts should be taken to ensure that all cautions and warnings are followed.

35

Before you Begin

Verify that the following components and accessories are included:

• One NetScaler SDX 11505, 13505, 17555, or 19555 appliance

• One accessory kit that contains:

• One short patch cable kit consisting of two 10G SFP+ transceivers and an opticalcable.

• Two power cables

Note: Make sure that a power outlet is available for each cable.• One standard 4-post rail kit

Note: If the kit that you received does not fit your rack, contact your Citrix salesrepresentative to order the appropriate kit.

Note: Other than the two transceivers in the 10G SFP+ patch cable kit, 1G SFP and 10GSFP+ transceivers are sold separately. Contact your Citrix sales representative to ordertransceivers for your appliance. Only transceivers supplied by Citrix are supported on theappliance.

36

Preparing the Site and Rack

There are specific site and rack requirements for the Repeater on SDX appliance. You mustmake sure that adequate environmental control and power density are available. Racksmust be bolted to the ground, have sufficient airflow, and have adequate power andnetwork connections. Preparing the site and rack are important steps in the installationprocess and help ensure a smooth installation.

Site RequirementsThe appliance should be installed in a server room or server cabinet with the followingfeatures:

Environment control

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 21degrees C/70 degrees F at altitudes of up to 2100 m/7000 ft, or 15 degrees C/60 degreesF at higher altitudes, a humidity level no greater than 45 percent, and a dust-freeenvironment.

Power density

Wiring capable of handling at least 4,000 watts per rack unit in addition to power needsfor the CRAC.

Rack RequirementsThe rack on which you install your appliance should meet the following criteria:

Rack characteristics

Racks should be either integrated into a purpose-designed server cabinet or be thefloor-to-ceiling type, bolted down at both top and bottom to ensure stability. If you havea cabinet, it should be installed perpendicular to a load-bearing wall for stability andsufficient airflow. If you have a server room, your racks should be installed in rowsspaced at least 1 meter/3 feet apart for sufficient airflow. Your rack must allow your ITpersonnel unfettered access to the front and back of each server and to all power andnetwork connections.

Power connections

At minimum, two standard power outlets per unit.

Network connections

At minimum, fourone Ethernet connections per rack unit.

Space requirements

Two empty rack units for Repeater on SDX appliances.

One empty rack unit for the Citrix Command Center MPX 7500 appliance.

Note: You can order the following rail kits separately.

• Compact 4-post rail kit, which fits racks of 23 to 33 inches.

• 2-post rail kit, which fits 2-post racks.

Preparing the Site and Rack

37

38

Cautions and Warnings

Electrical Safety PrecautionsBasic electrical safety precautions should be followed to protect yourself from harm andthe appliance from damage.

• Be aware of the location of the emergency power off (EPO) switch, so that you canquickly remove power to the appliance if an electrical accident occurs.

• Use a regulated, uninterruptible power supply (UPS) to protect the appliance frompower surges and voltage spikes, and to keep the appliance operating in case of powerfailure.

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

• Always disconnect the appliance from power before removing or installing anycomponent. First shut down the appliance, and then unplug the power cords of all thepower supply units. As long as the power cord is plugged in, line voltages can bepresent in the power supply, even when the power switch is OFF.

• Do not use mats designed to decrease static electrical discharge as protection fromelectrical shock. Instead, use rubber mats that have been specifically designed aselectrical insulators.

• Make sure that the power supply cords include grounding plugs and are plugged intogrounded electrical outlets.

• Make sure that the power source can handle the appliance's maximum powerconsumption rating with no danger of an overload.

• A reliable ground must be maintained at all times. Therefore, the rack should begrounded. Pay particular attention to power supply connections other than the directconnection to the branch circuit (for example, connections to power strips).

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

• Install the heaviest appliance 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 and hard drives to cool before touching them.

• Install the equipment near an electrical outlet for easy access.

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

• For a closed or multiple-unit rack assembly, the ambient operating temperature of therack environment might be greater than the ambient temperature of the room.Therefore, consider the lowest and highest operating temperatures of the equipmentwhen making a decision about where to install the appliance in the rack.

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.

• Always make sure that the rack is stable before extending a component from the rack.

• Extend only one component at a time. Extending two or more simultaneously mightcause the rack to become unstable.

• The handles on the left and right of the front panel of the appliance should be usedonly for extending the appliance out of the rack. Do not use these handles for mountingthe appliance on the rack.

Cautions and Warnings

39

40

Installing the Hardware

After you have determined that the location where you will install your appliance meets theenvironmental standards and the server rack is in place according to the instructions, youare ready to install the hardware. After you mount the appliance, you are ready to connectit to the network, to a power source, and to the console terminal that you will use forinitial configuration. To complete the installation, you turn on the appliance. Be sure toobserve the cautions and warnings listed with the installation instructions.

41

Rack Mounting the Appliance

Most appliances can be installed in standard server racks that conform to EIA-310-Dspecification. The appliances ship with a set of rails, which you must install before youmount the appliance. The only tools that you need for installing an appliance are a Phillipsscrewdriver and a flathead screwdriver.

Caution: If you are installing the appliance as the only unit in the rack, mount it at thebottom. If the rack contains other units, make sure that the heaviest unit is at thebottom. If the rack has stabilizing devices available, install them before mounting theappliance.

Citrix Repeater on SDX appliance requires two rack units.

Each appliance ships with a mounting rail kit that contains two rail assemblies, one for theleft side and the other for the right side of the appliance, and screws to attach the rails. Anassembly consists of an inner rail and a rack rail. The supplied rail kit is 28 inches long (38inches extended). Contact your Citrix sales representative to order a 23-inch (33 inchesextended) rail kit.

Note: The same rail kit is used for both square-hole and round-hole racks. See figure 4 forspecific instructions for threaded, round-hole racks.

To mount the appliance, you must first install the rails and then install the appliance in therack.

Perform the following tasks to mount the appliance:

• Remove the inner rails from the rail assembly.

• Attach the inner rails to the appliance.

• Install the rack rails on the rack.

• Install the appliance in the rack.

To remove the inner rails from the rail assembly1. Place the rail assembly on a flat surface.

2. Slide out the inner rail toward the front of the assembly.

3. Depress the latch until the inner rail comes all the way out of the rail assembly.

4. Repeat steps 1 through 3 to remove the second inner rail.

To attach the inner rails to the appliance1. Position the right inner rail behind the handle on the right side of the appliance.

2. Align the holes on the rail with the corresponding holes on the side of the appliance.

3. Attach the rail to the appliance with the provided screws: 5 per side, as shown in thefollowing figure.

Figure 1. Attaching inner rails

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


42

To install the rack rails on the rack1. If you have a round-hole, threaded rack, skip to step 3.

2. Install square nut retainers into the front post and back post of the rack as shown in thefollowing figures. Before inserting a screw, be sure to align the square nut with thecorrect hole for your appliance. The three holes are not evenly spaced.

Figure 2. Installing Retainers into the Front Rack Posts Figure 3. Installing Retainers intothe Rear Rack Posts

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


43

Figure 4. Installing the Rail Assembly to the Rack


44

To install the appliance in the rack1. Align the inner rails, attached to the appliance, with the rack rails.

2. Slide the appliance into the rack rails, keeping the pressure even on both sides.

3. Verify that the appliance is locked in place by pulling it all the way out from the rack.

Figure 5. Rack Mounting the Appliance


45

46

Installing and Removing 1G SFPTransceivers

Note: Some Repeater on SDX appliances do not require SFP transceivers.

A Small Form-Factor Pluggable (SFP) is a compact transceiver that can operate at speeds ofup to 1 gigabit per second and is available in both copper and fiber types. Inserting a 1GSFP copper transceiver converts the 1G SFP port to a 1000BASE-T port. Inserting a 1G SFPfiber transceiver converts the 1G SFP port to a 1000BASE-X port. Auto-negotiation isenabled by default on the 1G SFP port into which you insert your 1G SFP transceiver. Assoon as a link between the port and the network is established, the speed and mode arematched on both ends of the cable.

Caution: Repeater on SDX appliances do not support 1G SFP transceivers from vendorsother than Citrix Systems. Attempting to install third-party 1G SFP transceivers on yourRepeater on SDX appliance voids the warranty.

Insert 1G SFP transceivers into the 1G SFP ports on the front panel of the appliance.Frequent installation and removal of transceivers shortens their life span. Follow theremoval procedure carefully to avoid damaging the 1G SFP transceiver or the appliance.

Caution: Do not install the transceivers with the cables attached. Doing so can damagethe cable, the connector, or the optical interface of the transceiver.

To install a 1G SFP transceiver1. Remove the 1G SFP transceiver carefully from its box.

Danger: Do not look directly into fiber optic transceivers or cables. They emit laserbeams that can damage your eyes.

2. Align the 1G SFP transceiver to the front of the 1G SFP transceiver port on the frontpanel of the appliance, as shown in the following figure.

Note: The illustration in the following figures might not represent your actualappliance.

Figure 1. Installing a 1G SFP transceiver

3. Hold the 1G SFP transceiver between your thumb and index finger and insert it into the1G SFP transceiver port, pressing it in until you hear the transceiver snap into place.

4. Lock the transceiver.

5. Verify that the LED is green and blinks twice, which indicates that the transceiver isfunctioning correctly.

6. If you are using a fiber 1G SFP transceiver, do not remove the dust caps attached to thetransceiver and the cable until you are ready to insert the cable.

Installing and Removing 1G SFP Transceivers

47

To remove a 1G SFP transceiver1. Disconnect the cable from the 1G SFP transceiver. If you are using a fiber optic cable,

replace the dust cap on the cable before putting it away.


2. Unlock the 1G SFP transceiver.

3. Hold the 1G SFP transceiver between your thumb and index finger and slowly pull it outof the port.

4. If you are removing a fiber 1G SFP transceiver, replace the dust cap before putting itaway.

5. Put the 1G SFP transceiver into its original box or another appropriate container.

Installing and Removing 1G SFP Transceivers

48

49

Installing and Removing 10G SFP+Transceivers

Note: Some Repeater on SDX appliances do not require SFP+ transceivers.

A 10-Gigabit Small Form-Factor Pluggable (SFP+) is a compact optical transceiver that canoperate at speeds of up to 10 gigabits per second. Autonegotiation is enabled by default onthe 10G SFP+ ports into which you insert your 10G SFP+ transceiver. As soon as a linkbetween the port and the network is established, the mode is matched on both ends of thecable and for 10G SFP+ transceivers, the speed is also autonegotiated.

Caution: Repeater on SDX appliances do not support 10G SFP+ transceivers provided byvendors other than Citrix Systems. Attempting to install third-party 10G SFP+ transceiverson your Repeater on SDX appliance voids the warranty.

Insert the 10G SFP+ transceivers into the 10G SFP+ ports on the front panel of theappliance. Frequent installation and removal of transceivers shortens their life span. Followthe removal procedure carefully to avoid damaging the transceiver or the appliance.

Caution: Do not install the transceivers with the cables attached. Doing so can damagethe cable, the connector, or the optical interface of the transceiver.

To install a 10G SFP+ transceiver1. Remove the 10G SFP+ transceiver carefully from its box.

Danger: Do not look directly into fiber optic transceivers and cables. They emit laserbeams that can damage your eyes.

2. Align the 10G SFP+ transceiver to the front of the 10G SFP+ transceiver port on thefront panel of the appliance.

3. Hold the 10G SFP+ transceiver between your thumb and index finger and insert it intothe 10G SFP+ transceiver port, pressing it in until you hear the transceiver snap intoplace.

4. Move the locking hinge to the DOWN position.

5. Verify that the LED is green and blinks twice, which indicates that the transceiver isfunctioning correctly.

6. Do not remove the dust caps attached to the transceiver and cable until you are readyto insert the cable.

To remove a 10G SFP+ transceiver1. Disconnect the cable from the 10G SFP+ transceiver. Replace the dust cap on the cable

before putting it away.


2. Unlock the 10G SFP+ transceiver by moving the locking hinge to the UP position.

3. Hold the 10G SFP+ transceiver between your thumb and index finger and slowly pull itout of the port.

4. Replace the dust cap on the transceiver before putting it away.

5. Put the 10G SFP+ transceiver into its original box or another appropriate container.

Installing and Removing 10G SFP+ Transceivers

50

51

Install Fiber Patch Cable in Ports 10/3and 10/4

On a Repeater on SDX appliance, ports 10/3 and 10/4 must be connected with the providedcable as shown in the following figure.

F i g

u r e 1 . I n s t a l l i n g t h e P a t c h C a b l e

To install the patch cable1. Connect the LC-to-LC cable to the ports as shown in the figures above.

2. Install one end of the cable into port 10/3.

3. Install the other end of the cable into port 10/4.

Install Fiber Patch Cable in Ports 10/3 and 10/4

52

53

Connecting the Cables

When the appliance is securely mounted on the rack, you are ready to connect the cables.Ethernet cables and the optional console cable are connected first. Connect the powercable last.

Danger: Before installing or repairing the appliance, remove all jewelry and other metalobjects that might come in contact with power sources or wires. When you touch both alive power source or wire and ground, any metal objects can heat up rapidly and causeburns, set clothing on fire, or fuse the metal object to an exposed terminal.

Connecting the Appliance to the NetworkBefore connecting the appliance to your network, connect to only the management port(port 0/1) for initial configuration. The appliance does not have a hardware bypass mode,so attempting to use an unconfigured unit in inline mode on a production networkinterrupts traffic.

To set up the initial configuration, you can connect a laptop computer to the managementport with an Ethernet cable. (For a laptop with only a 100 Mbps Ethernet port, use across-over cable.)

Figure 1. Connecting a Citrix SDX applianceto the network

Warning: Connecting multiple network ports to the same switch or VLAN can result in anetwork loop.

By default, the ports on the SDX appliance are configured to use Ethernet autonegotiation.When you install an appliance for the first time, be sure to configure your other equipmentto use auto-negotiation for the port that is connected to your appliance. After initial logonand configuration, you can choose to disable auto-negotiation.

Connecting the Console CableYou can use the console cable to connect your appliance to a computer or terminal, fromwhich you can configure the appliance. Alternatively, you can use a computer connected tothe network. Before connecting the console cable, configure the computer or terminal tosupport VT100 terminal emulation, 9600 baud, 8 data bits, 1 stop bit, parity, and flowcontrol set to NONE. Then connect one end of the console cable to the RS232 serial port onthe appliance and the other end to the computer or terminal.

To connect the console cable to a computer or terminal1. Insert the DB-9 connector at the end of the cable into the console port that is located

on the front panel of the appliance, as shown in the following figure.

Figure 2. Inserting a console cable

Note: To use a cable with an RJ-45 converter, insert the optional converter providedinto the console port and attach the cable to it.

2. Insert the RJ-45 connector at the other end of the cable into the serial port of thecomputer or terminal.

Connecting an SDX Appliance to a Power SourceThe Repeater on SDX appliance has two power supplies, with one serving as a backup. Aseparate ground cable is not required, because the three-prong plug provides grounding.Power up the appliance by installing one or both power cords.

Figure 3. Connecting a Citrix SDXappliance to a power source

Connecting the Cables

54

55

Switching on the Appliance

After you have installed the appliance in a rack and connected the cables, verify that thepower cable is properly connected. If you have installed a second power supply, make surethe second cable is connected to an outlet for a different circuit than the first. Afterverifying the connections, you are ready to switch on the appliance.

To switch on the appliance1. Verify that the appliance is connected through a console or Ethernet port. This will

ensure that you can configure the appliance after it is switched on.

2. Press the ON/OFF toggle power switch on the back panel of the appliance.

Caution: Be aware of the location of the emergency power off (EPO) switch, so that if anelectrical accident occurs you can quickly remove power from the appliance.

56

Lights Out Management Port of theRepeater on SDX Appliance

The Repeater on SDX appliances have an Intelligent Platform Management Interface (IPMI),also known as the Lights out Management (LOM), port on the front panel of the appliance.By using the LOM, you can remotely monitor and manage the appliance, independently ofthe Repeater on SDX software. You can remotely change the IP address, perform differentpower operations, and obtain health monitoring information of the appliance by connectingto the appliance through the LOM port.

By connecting the LOM port over a dedicated channel that is separate from the datachannel, you can make sure that connectivity to the appliance is maintained even if thedata network is down.

Accessing the LOM Port by using a Web BrowserBy using a web browser you can remotely log on to the LOM port to obtain informationabout the appliance and perform different operations on the appliance.

To access the LOM by using a web browser

1. In a web browser, type the IP address of the LOM port. For initial configuration, typethe port’s default address: http://192.168.1.3

2. In the User Name and Password boxes, type the administrator credentials. You canobtain the initial user name and password from your sales representative or from CitrixCustomer Service.

Configuring the LOM PortFor initial configuration of the lights-out management (LOM) port, connect to the port'sdefault IP address and change it to the address that you want to use for remote monitoringand management. Also specify the administrator credentials and the network settings.

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

To Configure the NetScaler LOM Port1. Connect the NetScaler LOM port to a management workstation or network.

2. In a web browser, type: http://192.168.1.3.

Note: The NetScaler LOM port is preconfigured with the IP address 192.168.1.3 andsubnet mask 255.255.255.0.

3. In the User Name box, type nsroot.

4. In the Password box, type nsroot.

5. In the Configuration tab, click Network and type values for the following parameters:

• IP Address—IP address of the LOM port.

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

• Default Gateway—IP address of the router that connects the LOM port to thenetwork.

6. Click Save.

Power Cycling the ApplianceYou can remotely turn off the appliance and turn it back on. The result is similar to pressingthe power button on the back panel of the appliance for less than four seconds.

To power cycle the appliance1. In a web browser, type the IP address of the LOM port.

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

3. In the Menu bar, click Remote Control.

4. Under Options, click Power Control, and then click Power Cycle System.

5. Click Perform Action.

Accessing the Appliance by using the AccessConsole

The LOM port allows you to remotely access and manage the appliance by logging on to aredirected console.

To access the appliance by using the access console

1. In a web browser, type the IP address of the LOM port.


Lights Out Management Port of the Repeater on SDX Appliance

57

http://192.168.1.3/


4. Under Options, click Console Redirection.

5. Click Launch Console, and then click Yes.

6. Type the administrator credentials for the appliance.

Obtaining Health Monitoring InformationYou can log on to the LOM port to view the health information about the appliance. Allsystem sensor information, such as system temperature, CPU temperature, status of fanand power supplies, appears on the sensor readings page.

To obtain health monitoring information

1. In a web browser, type the IP address of the LOM port.


3. In the Menu bar, click System Health.

4. Under Options, click Sensor Readings.

Power Control Operations using the LOM PortYou can remotely perform different power control operations, such as restarting theappliance, performing a graceful shutdown, and performing a forced shutdown, by using theLOM port.

To perform power control operations

1. In a web browser, log on to the LOM port by using the administrator credentials.


3. Under Options, click Power Control, and then select one of the following options:

• Reset System—Restart the appliance.

• Power Off System – Immediate—Disconnect power to the appliance withoutshutting down the appliance.

• Power On System—Turn on the appliance.

• Power Cycle System—Turn off the appliance, and then turn it back on.4. Click Perform Action.

Lights Out Management Port of the Repeater on SDX Appliance

58

59

Initial Configuration

After you have installed your appliance in a rack, you are ready to perform the initialconfiguration. To perform the initial configuration, you can use the Management Serviceuser interface or the serial console. You can access the Management Service user interfacefrom any computer that is on the same network as the new SDX appliance. If you do nothave a computer on the same network, use the serial console to perform the initialconfiguration of the SDX appliance.

For initial configuration, use nsroot as both the administrative user name and the password.Citrix recommends that, as soon as you complete the initial configuration, you change theroot-user password.

60

Configuration Requirements

Branch Repeater for SDX contains a Xen hypervisor, a NetScaler SDX virtual machine, and upto six Repeater VPX virtual machines for load-balanced WAN acceleration. The hypervisorand the virtual machines will each have their own IP address on the management network,which is reached through the management Ethernet port 0/1 (on the front panel). The mainmanagement UI is called the “Service management VM console” and is used to create andmanage the NetScaler and Repeater instances.

The Service management VM console has a default IP address for initial configuration. If youwant to be able to manage Repeater SDX remotely, change these addresses to match yournetwork.

Determine the following information for performing the initial configuration.

• NetScaler SDX IP address and subnet mask: This IP address is used to accesstheNetScaler SDX Management virtual machine (SVM).

• Service management VM console IP address.

• Default gateway: The IP address of the router that forwards traffic out of theappliance's subnet.

• Root password: The root user (nsroot) has full administrative privileges on theappliance. Citrix recommends that you change the password from its default value afterinitial configuration.

61

Initial Configuration through theManagement Service User Interface

To set up the appliance by using the Management Service user interface, connect a

workstation or laptop to the same network as the appliance.

To change the management port's IP configuration

1. Using an Ethernet cable, connect a laptop or other computer with a Web browser tointerface 0/1 on Repeater SDX.

2. Set the laptop’s IP address for its Ethernet port to 192.168.100.100.

3. Open a browser and type: http://192.168.100.1

Note: The NetScaler SDX Management Service is preconfigured with the IP address192.168.100.1 and the XenServer hypervisor is preconfigured with the IP address192.168.100.2.

4. In the User Name box, type nsroot.

5. In the Password box, type nsroot.

6. In the navigation pane, click System.

7. In the details pane, under System Administration, click Network Configuration and entervalues for the following parameters:

• Interface*—The management interface that connects the appliance to amanagement workstation or network. Possible values: 0/1, 0/2. Default: 0/1.

• XenServer IP Address*—The IP address of the XenServer.

• Management VM IP Address*—The IP address that is used to access the ManagementService by using a Web browser. The XenServer IP address and Management ServiceIP address should be in the same subnet.

• Netmask*—The mask used to define the subnet in which the SDX appliance islocated.

• Gateway*—The IP address of the router that forwards traffic out of the appliance'ssubnet.

• DNS Server—The IP address of the DNS server.

*A required parameter8. Click OK, and then click Close.

9. To confirm that the SDX appliance is configured correctly, you can either ping the newManagement Service IP address or use the new IP address to open the user interface ina browser.

Note: After changing the network configuration, close all browser instances and opena new browser instance to access the appliance.

Initial Configuration through the Management Service User Interface

62

63

Configuring the LOM Port

For initial configuration of the lights-out management (LOM) (Lights-Out Management) port,connect to the port's default IP address and change it to the address that you want to usefor remote monitoring and management. Also specify the administrator credentials and thenetwork settings.

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

To configure the LOM port

1. In a web browser, type the IP address of the LOM port. For initial configuration, typethe port’s default address: http://192.168.1.3

2. In the User Name and Password boxes, type the administrator credentials. You canobtain the initial user name and password from your sales representative or from CitrixCustomer Service.

3. In the Menu bar, click Configuration.

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 LOM port to

the network.5. Click Save.

64

Getting Started with the ManagementService User Interface

To begin configuring, managing, and monitoring the appliance, the Management Service,the Repeater instances and the virtual instance, you need to connect to the ManagementService user interface by using a browser, and then provision the virtual instance on theappliance.

• Logging on to the Management Service VM User Interface

• Provisioning a NetScaler Instance and the Repeater instances

65

Logging on to the Management ServiceUser Interface

You can connect to the Management Service user interface by using one of the followingsupported browsers:

• Internet Explorer

• Google Chrome

• Apple Safari

• Mozilla Firefox

To log on to the Management Service user interface1. In your Web browser address field, type one of the following:

http://Management Service IP Address

or

https://Management Service IP Address

2. On the Login page, in User Name and Password, type the user name and password ofthe Management Service. The default user name and password are nsroot and nsroot.However, Citrix recommends that you change the password after initial configuration.For information about changing the nsroot password, see Changing the Password of theDefault User Account.

3. Click Show Options, and then do the following:

a. In the Start in list, select the page that must be displayed immediately after you logon to the user interface. The available options are Home, Monitoring,Configuration, Documentation, and Downloads. For example, if you want theManagement Service to display the Configuration page when you log on, selectConfiguration in the Start in list.

b. In Timeout, type the length of time (in minutes, hours, or days) after which youwant the session to expire. The minimum timeout value is 15 minutes.

The Start in and Timeout settings persist across sessions. Their default values arerestored only after you clear the cache.

4. Click Login to log on to the Management Service user interface.

66

Provisioning a NetScaler Instance and theRepeater Instances

You can provision a NetScaler instance on the SDX appliance by using the ManagementService. The license does not allow provisioning of multiple NetScaler instances.

You must also provision one or more Repeater instances on the SDX appliance by using theManagement Service VM. The number of instances that you can install depends on thelicense you have purchased. The Service VM does not allow you to add more instances thanare allowed by your license.

For information about provisioning a NetScaler instance, see Provisioning the NetScalerInstance.

For information about provisioning the Repeater instances, see Provisioning the RepeaterInstances.

67

Administration



The two models are:





68

Introduction

Citrix® Repeater for NetScaler® SDX is a high-performance WAN accelerator for busydatacenters that combines multiple virtual instances of the Repeater appliance with asingle virtual instance of the NetScaler load-balancer, providing the performance ofmultiple Repeater appliances in a single package. Combining the virtual Repeaters with aNetScaler allows great flexibility in deployment. Through the use of the on-boardNetScaler, the virtual Repeaters can be dedicated individually to specific WAN traffic orused in a load-balanced configuration.

The SDX appliance includes a management Service VM that controls the basic networkconfiguration of the unit and manages the virtual machines. It provides a user interface(HTTP and HTTPS modes) and an API to configure, manage, and monitor the appliance, theService VM, the NetScaler instance, and the Repeater instances.

The NetScaler instance and the Repeater instances each have their own browser-based userinterfaces that are used for configuration. The management Service VM contains links tothese user interfaces.

Repeater for SDX combines a NetScaler virtual machine and 3-6 Repeater VPX virtualmachines running Repeater release 5.6 , as shown in Figure 1. Management functions for allvirtual machines use the management subnet that is mapped to port 0/1 on the SDXappliance. The Repeater virtual machines are mapped internally through the NetScalervirtual machine to 10 Gbps port 10/4.

Figure 1. Repeater for SDX block diagram.

Summary of Configuration Steps1. Physical/electrical installation (see the Citrix Repeater on NetScaler SDX Quick Start

Guide).

2. Configure the management interface (see the Citrix Repeater on NetScaler SDX QuickStart Guide).

3. Create NetScaler and Repeater virtual instances (this document).

4. Configure the NetScaler instance to load-balance Repeater Traffic.

Repeater FunctionalityThe Repeater virtual machines are fully independent of one another and can thus bededicated to different tasks in addition to being used in a load-balanced configuration. Forexample, in a unit with three Repeater instances, one could be devoted to traffic from asingle large partner site, while the other two could load-balance the remaining trafficbetween them.

For instances that are used together, maintaining consistency is best done through the useof Citrix Command Center.

Introduction

69

Features of the Repeater Instances

• Each instance is a Repeater VPX 5.6 6.0 virtual machine.

• Each instance supports WAN speeds up to 500 Mbps, with an aggregate bandwidth limitof 500 Mbps for the Repeater 500 for SDX and 1 Gbps for the Repeater 1000 for SDX.

• Deployment modes: Always “one-armed” internally, but the SDX as a whole can bedeployed in inline or virtual inline mode.

• SSD-based disks are used for maximum performance.

• See the Branch Repeater Family User’s Guide, rel. 5.5-5.7 for more information onRepeater VPX instances.

TopologyExternally, Repeater SDX can be used inline with the WAN or in a routed mode that workslike Repeater’s virtual inline mode. Because Repeater SDX lacks hardware bypass support,routed mode is more reliable. (Unlike other Repeater hardware, since Repeater SDX will notpass traffic between bridged ports before the unit is configured.)

To set up Repeater LAN/WAN connectivity

1. Connect Repeater SDX to your WAN router using a fibre port; for example, port 10/2.

2. If using inline mode, also connect Repeater SDX to your LAN using (for example) port10/1.

Repeater SDX’s 1 Gbps fibre ports can be substituted for the 10 Gbps ports, if desired.

Note: Because Repeater SDX does not have hardware bypassing, installing the applianceinline with your WAN will cause a service outage until the unit is fully configured, soplacing the unit inline with production links should be done last.

High Availability

Repeater SDX can be used with NetScaler HA. If the NetScaler instance on one SDX unitfails, or if there is a hardware failure, the other SDX unit will take over. Within an SDX unit,the failure of a Repeater instance will lead to that units’ traffic being forwarded withoutacceleration. Unlike the other Repeater appliances, is no synchronization between theRepeater instances on the two SDX units.

Internal Topology

Internally, the Repeater instances are connected to the NetScaler instance through aninternal virtual network, such as vlan 1000, and traffic is routed to them through NetScalercommands. All instances can be attached to the same internal virtual network. From theRepeater point of view, this means that the Repeaters are running in virtual inline modeand the “Return to Ethernet Sender” option must be selected (this is the default). Also,bridging need not be enabled on the Repeater instances.

Introduction

70

71

Load Balancing

The NetScaler virtual machine uses rules to decide which Repeater instances will handlewhich connections. These rules are fully user-configurable to match the needs of anindividual site, and should follow the guidelines below.

Bypass Non-Accelerable TrafficTraffic that is not a candidate for acceleration should bypass the Repeater instances tominimize the load on the Repeaters and the latency of the traffic.

If the Repeater SDX is on the server side of the connection (as it generally is when it isacting as the hub of a hub-and-spoke network where all the spokes are smaller units),connections are initiated on the client (spoke) side and pass through a client-side Repeateror Branch Repeater unit before reaching Repeater SDX. The client-side unit attaches“Repeater options” to the TCP header of the first packet of the connection, the SYNpacket. This identifies the connection as accelerable, so rules that detect the absence ofsuch headers will identify traffic that should bypass the Repeater instances.

For example, the “-listenpolicy” option of the “add lb vserver” command can test for thepresence or absence of Repeater headers:

–listenpolicy client.tcp.options.type_name(REPEATER).exists

–listenpolicy client.tcp.options.type_name(REPEATER).exists.NOT

Because traffic originating locally does not have Repeater headers until it passes through aRepeater instance, the decision of whether to send it to a Repeater instance or not must bebased on other information, information already present in the packet. Non-TCP trafficshould always be bypassed. Traffic sent to destinations known not to be serviced byRepeaters should be bypassed. The rest should be sent to a Repeater instance. Ideally, itshould be sent to the same instance that handles connections in the reverse direction.

Load-Balance Repeater TrafficThe main considerations of Repeater load-balancing are:

• An affinity should be maintained between a local Repeater instance and the remoteunit, because compression performance relies on the amount of shared compressionhistory between the two units. An unfamiliar partner has no compression history andthus performs little compression. Thus, all traffic from a given remote Branch Repeatershould pass through the same local Repeater SDX instance. This can be assignedmanually using the management IP address of the remote Repeater, which is includedin the TCP options, using a “-listenpolicy” option on the “add lb vserver” statementthat includes a test like this (assuming the remote Repeater has a management IP of10.10.10.10):

–listenpolicy (client.tcp.options.type_name(REPEATER).exists

&& client.tcp.repeater_option.ip.eq(10.10.10.10))

• Each instance should handle roughly the same amount of remote bandwidth. Forexample, if one instance handles remote units adding up to 200 Mbps and anotherinstance is handling remote units adding up to only 10 Mbps of bandwidth, this would beunbalanced.

• Each instance should handle roughly the same amount of demand in terms ofconnections and users.

Sample NetScaler Load-Balancing ConfigurationFor the example below, the NetScaler instance uses the following IP addresses:

• 10.102.78.69 (Management)

• 152.168.2.1 (LAN /Servers network)

• 192.168.2.2 (WAN network)

• 142.1.1.1 (communication to the accelerated ports of the Repeater instances)

There are two Repeater instances in this example:

• Repeater-1 instance has apA IP: 142.1.1.2

• Repeater-2 instance has apA IP: 142.1.1.4

// Enable the NetScaler features

enable ns feature LB

enable ns mode FR L3 USIP MBF Edge USNIP PMTUD

// Add the ACL policy, to make sure that only TCP traffic is send to Repeaters and all thenon-TCP traffic is bypassed.

add ns acl acl1 ALLOW -protocol TCP -priority 10

add ns acl acl2 BRIDGE -priority 20

apply ns acls

// Add the forwarding session to send traffic directly to a physical server if a virtual serveris DOWN or the listen policy does not match; 152.168.2.x network is the server side LANnetwork.

add forwardingSession fw1 152.168.2.0 255.255.255.0

add ns ip 192.168.2.2 255.255.255.0 -vServer DISABLED



Load Balancing

72

set lb parameter -preferDirectRoute NO

set l3param -forwardICMPFragments eNABLED

add service s3 142.1.1.2 ANY * -cltTimeout 14400 -svrTimeout 14400

add service s4 142.1.1.4 ANY * -cltTimeout 14400 -svrTimeout 14400

add lb vserver v3 ANY * * -persistenceType NONE -Listenpolicy "SYS.VSERVER(\"v3\").STATE.EQ(UP)&&((CLIENT.TCP.OPTIONS.TYPE_NAME(REPEATER).EXISTS&&(CLIENT.TCP.REPEATER_OPTION.IP.EQ(132.1.1.2)||CLIENT.TCP.REPEATER_OPTION.IP.EQ(10.102.78.231)))||(CLIENT.IP.DST.IN_SUBNET(172.168.2.0/24)))" -Listenpriority 1 -m MAC -cltTimeout 14400 -l2Conn ON

// 132.1.1.2 is the Branch Office (1) Repeater apA IP and

// 10.102.78.231 is the Branch Office Repeater Primary IP

// 172.168.2.0 is the Branch office (1) client network

add lb vserver v4 ANY * * -persistenceType NONE -Listenpolicy "SYS.VSERVER(\"v4\").STATE.EQ(UP)&&((CLIENT.TCP.OPTIONS.TYPE_NAME(REPEATER).EXISTS&&(CLIENT.TCP.REPEATER_OPTION.IP.EQ(133.1.1.2)||CLIENT.TCP.REPEATER_OPTION.IP.EQ(10.102.78.235)))||(CLIENT.IP.DST.IN_SUBNET(172.168.3.0/24)))" -Listenpriority 2 -m MAC -cltTimeout 14400 -l2Conn ON

bind lb vserver v3 s3

bind lb vserver v4 s4

save config

Load Balancing

73

74

Managing the Home Page

The Management Service Home page provides you with a high-level view of theperformance of the SDX appliance and the instances provisioned on your appliance. SDXappliance, Repeater Instance and instance information is displayed in gadgets that you canadd and remove depending on your requirement.

The following gadgets are available on the Home page by default.

System Resources

Displays the total number of CPU cores, total number of SSL chips, number of free SSLchips, total memory, and free memory on the appliance.

System CPU | Memory Usage (%)

Displays the percentage of CPU and memory utilization of the appliance in graphicalformat.

System Throughput (Mbps)

Displays the total throughput of the SDX appliance for incoming and outgoing traffic in agraph that is plotted in real time and updated at regular intervals.

Repeater Instances

Displays the properties of the Repeater instances. The properties displayed are Name,VM State, Repeater State, IP address, and CPU and memory usage.

NetScaler Instances

Displays the properties of the NetScaler instances. The properties displayed are Name,VM State, Instance State, IP Address, Rx (Mbps), Tx (Mbps), HTTP Req/s, and CPU Usage(%) and Memory Usage (%).

Note: On first log on, the Home page does not display any data related to theNetScaler or Repeater instances because you have not provisioned any instances onyour appliance.

You can do the following on the Home page:

View and hide NetScaler instance details

You can view and hide the details of a particular instance by clicking the name of theinstance in the Name column. You can also click Expand All to expand all the instancenodes and Collapse All to collapse all the instance nodes.

Add and remove gadgets

You can also add gadgets to view additional system information.

To add these gadgets, click the arrow (<<) button at the top right corner of the Homepage, enter keywords in the search box, and then click Go. The allowed characters are:a-z, A-Z, 0-9, ^, $, *, and _. Click Go without typing any characters in the search box todisplay all the gadgets that are available. After the gadget is displayed, click Add todashboard.

Currently, you can add the following gadgets to the Home page:

Hypervisor Details

The Hypervisor Details gadget displays details about XenServer uptime, edition,version, iSCSI Qualified Name (IQN), product code, serial number, build date, andbuild number.

Licenses

The Licenses gadget displays details about the SDX hardware platform, the maximumnumber of instances supported on the platform, the maximum supported throughputin Mbps, and the available throughput in Mbps.

If you remove a gadget that is available on the Home page by default, you can add itback to the Home page by performing a search for the gadget, as described earlier.

Managing the Home Page

75

76

Managing and Monitoring the SDXAppliance

After your SDX appliance is up and running, you can perform various tasks to manage andmonitor the appliance from the Management Service user interface.

77

Modifying the Network Configuration ofthe SDX Appliance

You can modify the network configuration details that you provided for the SDX applianceduring initial configuration.

To modify the network configuration of the SDXappliance


2. In the System pane, under Setup Appliance, click Network Configuration.

3. In the Modify Network Configuration dialog box, specify values for the followingparameters:

• Interface*—The interface through which clients connect to the Management Service.Possible values: 0/1, 0/2. Default: 0/1.

• XenServer IP Address*—The IP address of the XenServer.

• Management Service IP Address*—The IP address of the Management Service.

• Netmask*—The netmask for the subnet in which the SDX appliance is located.

• Gateway*—The default gateway for the network.

• DNS Server—The IP address of the DNS server.* A required parameter

4. Click OK.

78

Changing the Password of the DefaultUser Account

The default user account provides complete access to all features of the Citrix SDXappliance. Therefore, to preserve security, the nsroot account should be used only whennecessary, and only individuals whose duties require full access should know the passwordfor the nsroot account. Citrix recommends changing the nsroot password frequently. If youlose the password, you can reset the password to the default by reverting the appliancesettings to factory defaults .

You can change the password of the default user account in the Users pane. In the Userspane, you can view the following details:

Name

Lists the user accounts configured on the SDX appliance.

Permission

Displays the permission level assigned to the user account.

To change the password of the default user account1. On the Configuration tab, in the navigation pane, expand System, and then click Users.

2. In the Users pane, click the default user account, and then click Modify.

3. In the Modify System User dialog box, in Password and Confirm Password, enter thepassword of your choice.

4. Click OK.

79

Viewing the SSL Certificate on theManagement Service

The Management Service uses an SSL certificate for secure client connections. You can viewthe details of this certificate, such as validity status, issuer, subject, days to expire, validfrom and to dates, version, and serial number.

To view the SSL certificate on the ManagementService


2. In the System pane, click View SSL Certificate. The certificate details are displayed.

80

Modifying the Time Zone on theAppliance

You can modify the time zone of the Management Service and the Xen Server. The defaulttime zone is UTC.

To modify the time zone on the appliance1. On the Configuration tab, in the navigation pane, click System.

2. In the System pane, under System Settings, click Change Time Zone.

3. In the Modify Time Zone dialog box, select a time zone from the list, and then click OK.

81

Modifying System Settings

For security reasons, you can specify that the Management Service and a NetScaler VPXinstance should communicate with each other only over a secure channel. You can alsorestrict access to the Management Service user interface. Clients can log on theManagement Service user interface only by using https.

To modify system settings1. On the Configuration tab, in the navigation pane, click System.

2. In the System pane, under System Settings, click Change System Settings.

3. In the Modify System Settings dialog box, select https from the list.

4. Optionally, to restrict secure-only access to the Management Service, select SecureAccess only.

5. Click OK.

82

Restarting the Appliance

The Management Service provides an option to restart the SDX appliance. During therestart, the appliance shuts down all hosted instances, and then restarts XenServer. WhenXenServer restarts, it starts all hosted instances along with the Management Service.

To restart the appliance1. On the Configuration tab, in the navigation pane, click System.

2. In the System pane, click Reboot Appliance.

83

Shutting Down the Appliance

You can shut down the SDX appliance from the Management Service.

To shut down the appliance1. On the Configuration tab, in the navigation pane, click System.

2. In the System pane, click Shutdown Appliance.

84

Managing Interfaces

The SDX appliance has 16 interfaces: two 1 Gbps management interfaces, eight 1 Gbpsgeneral-purpose interfaces, and four 10 Gbps SFP+ interfaces.

Two of the SFP+ interfaces must be connected together (10/3 and 10/4) with the providedpatch cable as described in the Repeater for NetScaler SDX Quick Start Guide. In addition,these must be assigned their roles in the Service Management VM.

In the Interfaces pane, you can view the following interface settings for each interface onthe SDX appliance:

Interface

The interface ID.

State

State of the interface. UP indicates that the interface is receiving traffic normally, whileDOWN indicates a network issue because of which the interface is unable to send orreceive traffic.

Assign roles to Ports 10/3 and 10/41. On the Configuration tab, in the navigation pane, expand System, and then click

Interfaces.

2. In the System pane, click Change System Settings.

3. Set the Reserved Interface field to 10/3.

4. Set the Load-Balancing Interface field to 10/4.

5. Click OK.

To configure an interface1. On the Configuration tab, in the navigation pane, expand System, and then click

Interfaces.

2. In the Interfaces pane, click the interface that you want to configure, and then clickModify.

3. In the Modify Interface dialog box, under Link Speed and Flow Control, specify valuesfor the following parameters:

• Auto Negotiation*—Specifies whether auto-negotiation is enabled on the interface.Possible values: ON, OFF. Default: OFF.

• Speed*—Specifies the Ethernet speed for the interface, in Mbps. Possible values: 10,100, 1000, and 10000.

• Duplex*—Specifies the duplex setting for the interface. Possible values: FULL, HALF,NONE. Default: NONE.

• Flow Control Auto Negotiation*—Specifies whether auto-negotiation is performedfor flow control parameters.

• Rx Flow Control*—Specifies whether or not Rx flow control is enabled.

• Tx Flow Control*—Specifies whether or not Tx flow control is enabled.* A required parameter

4. Click OK, and then click Close.

To reset the parameters of an interface to their defaultvalues

1. On the Configuration tab, in the navigation pane, expand System, and then clickInterfaces.

2. In the Interfaces pane, click the interface that you want to reset, and then click Reset.

Managing Interfaces

85

86

Display the Mapping of Virtual Interfaceson the VPX Instance to the PhysicalInterfaces on the NetScaler SDXAppliance

If you log on to the NetScaler virtual instance, the configuration utility and the commandline interface display the mapping of the virtual interfaces on the instance to the physicalinterfaces on the appliance.

After logging on to the NetScaler VPX instance, in the configuration utility, navigate toNetwork, and then click Interfaces. The virtual interface number on the instance and thecorresponding physical interface number on the appliance appear in the Description field,as shown in the following figure:

Figure 1. Mapping the Virtual Interfaces to the Physical Interfaces in the ConfigurationUtility

In the above example, the virtual interface 10/3, on the NetScaler VPX instance, is a 10Ginterface and is mapped to physical interface (PF) 10/4 on the NetScaler SDX appliance.

In the NetScaler command line interface, type the show interface command. Forexample:

> show interface 1) Interface 10/3 (10G VF Interface, PF 10/4) #2 flags=0xe460 <ENABLED, UP, UP, HAMON, 802.1q> MTU=1500, native vlan=1, MAC=6e:b6:f5:21:5d:db, uptime 43h03m35s Actual: media FIBER, speed 10000, duplex FULL, fctl NONE, throughput 10000 RX: Pkts(2547925) Bytes(287996153) Errs(0) Drops(527183) Stalls(0) TX: Pkts(196) Bytes(8532) Errs(0) Drops(0) Stalls(0) NIC: InDisc(0) OutDisc(0) Fctls(0) Stalls(0) Hangs(0) Muted(0) Bandwidth thresholds are not set. ...

Display the Mapping of Virtual Interfaces on the VPX Instance to the Physical Interfaces on the NetScaler SDX Appliance

87

88

Assigning a MAC Address to an Interface

If, while you are provisioning a NetScaler instance on an SDX appliance, XenServerinternally assigns a MAC address to a virtual interface associated with that instance, thesame MAC address might be assigned to a virtual interface associated with another instanceon the same appliance or on another appliance. To prevent assignment of duplicate MACaddresses, you can enforce unique MAC addresses.

There are two ways of assigning a MAC address to an interface:

1. Assign a base MAC address and a range to an interface: The Management Service assignsa unique MAC address by using the base address and range.

2. Assign a global base MAC address: A global base MAC address applies to all interfaces.The Management Service then generates the MAC addresses for all interfaces. If you setthe global base MAC address, the range for a 1G interface is set to 8 and the range for a10G interface is set to 64. See the following table for sample base MAC addresses if theglobal base MAC address is set to 00:00:00:00:00:00.

Table 1. Example of Base MAC Addresses Generated from a Global Base MAC Address

Physical Interface Base MAC Address

0/1 00:00:00:00:00:00

0/2 00:00:00:00:00:08

1/1 00:00:00:00:00:10

1/2 00:00:00:00:00:18

1/3 00:00:00:00:00:20

1/4 00:00:00:00:00:28

1/5 00:00:00:00:00:30

1/6 00:00:00:00:00:38

1/7 00:00:00:00:00:40

1/8 00:00:00:00:00:48

10/1 00:00:00:00:00:50

10/2 00:00:00:00:00:90The base MAC address for the management ports is for reference only. The ManagementService generates MAC addresses, on the basis of the base MAC address, for 1/x and 10/xports only.

Note: You cannot assign a base MAC address to a channel.

To set the base MAC address for an interface andgenerate a range of MAC addresses

1. On the Configuration tab, navigate to System > Interfaces and select the interface forwhich you want to set the MAC address.

2. In the Modify Interface dialog box, select Add MAC Address, and then set the followingparameters:

• Add MAC Address—Assign a base MAC address to the interface. If you do not selectthis option, XenServer assigns a MAC address to the virtual interface.

• Base MAC Address—Enter the base MAC address. The Management Service uses thisaddress to generate a MAC address for a virtual interface associated with aninstance.

• Range—Specify the MAC addresses allowed for the virtual interfaces that areassigned to this physical interface. These MAC addresses cannot be assigned to anyother physical interface. For example, on a 1G interface, if the base MAC address is00:00:00:00:00:00 and range is set to 8, a MAC address between 00:00:00:00:00:00and 00:00:00:00:00:08 cannot be assigned to another physical interface. Maximumlimit for a 1G interface is 8. Maximum limit for a 10G interface is 64.

3. To apply MAC addresses according to the base MAC address, click Apply MAC Address.All the virtual instances associated with this interface are restarted.


To set the global base MAC address and generate thebase MAC address for all interfaces

1. On the Configuration tab, navigate to System > Interfaces, and then click Set GlobalBase MAC Address.

2. In the Generate MAC Address dialog box, in the Base MAC Address text box, type thebase MAC address.

3. Click Apply MAC Address. All the virtual instances provisioned on the appliance arerestarted.

4. Click Generate, and then click Close.


89

To assign a MAC address to an interface1. In the Provision NetScaler Wizard or the Modify NetScaler Wizard, on the Network

Settings page, in the Select Modelist, choose one of the following options:

• Default—XenServer assigns a MAC address.

• Custom—SDX Administrator assigns a MAC address. The SDX administrator can usethis setting to override the generated MAC address.

• Generated— Generate a MAC address by using the base MAC address set earlier.2. If you select Custom, enter a MAC Address.

3. Follow the instructions in the wizard.

4. Click Finish, and then click Close.


90

91

Configuring Clock Synchronization

You can configure your NetScaler SDX appliance to synchronize its local clock with aNetwork Time Protocol (NTP) server. As a result, the clock on the SDX appliance has thesame date and time settings as the other servers on your network. The clocksynchronization configuration does not change if the appliance is restarted, upgraded, ordowngraded. However, the configuration does not get propagated to the secondaryNetScaler instance in a high availability setup.

The clock is synchronized immediately if you add a new NTP server or change any of theauthentication parameters. You can also explicitly enable and disable NTP synchronization.

Note: If you do not have a local NTP server, you can find a list of public, open access,NTP servers at the official NTP site, http://www.ntp.org. Before configuring yourNetScaler to use a public NTP server, be sure to read the Rules of Engagement page (linkincluded on all Public Time Servers pages).

http://www.ntp.org/

To configure an NTP server1. In the navigation pane, expand System, and then click NTP Servers.

2. In the details pane, do one of the following:

• To add a new NTP server, click Add.

• To modify settings for an existing NTP server, select the NTP server, and then clickOpen.

3. In the Create NTP Server or Configure NTP Server dialog box, set the followingparameters:

• Server Name/IP Address*—The domain name of the NTP server or the IP address ofthe NTP server. The name or IP address cannot be changed for an existing NTPserver.

• Minimum Poll Interval— The minimum number of seconds after which the NTPserver must poll the NTP messages, expressed as a power of 2. Minimum value: 4(2^4=16 seconds). Maximum value: 6 (2^6=64 seconds). Default: 6 (2^6=64 seconds).

• Maximum Poll Interval— The maximum number of seconds after which the NTPserver must poll the NTP messages, expressed as a power of 2. Minimum value: 10(2^10=1024 seconds). Maximum value: 17 (2^17=36 hours). Default : 10 (2^10=1024seconds).

• Key Identifier—The key to be used for the specified server. This key identifiershould be added to the list of Trusted Key IDs in the Authentication Parameters.Minimum value: 1. Maximum value: 65534.

Note: Do not add if Autokey is selected.

• Autokey—Use the Autokey protocol for the specified server.

• Preferred—Synchronize with this server first. Applicable if more than one server isconfigured.

*A required parameter

4. Click Add, and then click Close.

5. In the details pane, verify that the settings displayed for the NTP server that you justcreated are correct.

To enable NTP synchronization1. In the navigation pane, expand System, and then click NTP Servers.

2. In the details pane, click NTP Synchronization.

3. In the NTP Synchronization dialog box, select Enable NTP Sync.



92

To modify Authentication options1. In the navigation pane, expand System, and then click NTP Servers.

2. In the details pane, click Authentication Parameters.

3. In the Modify Authentication Options dialog box, set the following parameters:

• Authentication—Enable NTP authentication. Possible values: YES, NO. Default: YES.

• Trusted Key IDs—The trusted key IDs. While adding an NTP server, you select a keyidentifier from this list. Minimum value: 1. Maximum value: 65534.

• Revoke Interval—The interval between re-randomization of certain cryptographicvalues used by the Autokey scheme, as a power of 2, in seconds. Default value: 17(2^17=36 hours).

• Automax Interval—The interval between regeneration of the session key list usedwith the Autokey protocol, as a power of 2, in seconds. Default value: 12 (2^12=1.1hours).



93

94

Viewing the Properties of the SDXAppliance

You can view system properties such as the number of CPU cores , total available memoryand free memory, and various product details on the Configuration tab.

To view the properties of the SDX appliance, click the tab.

You can view the following information about system resources, Hypervisor, License, andSystem:

System Resources

Total Memory (GB)

Total appliance memory in gigabytes.

Free Memory (GB)

Free appliance memory in gigabytes.

Hypervisor Information

Uptime

Time since the appliance was last restarted, in number of days, hours, and minutes.

Edition

The edition of XenServer that is installed on the SDX appliance.

Version

The version of XenServer that is installed on the SDX appliance.

iSCSI IQN

The iSCSI Qualified Name.

Product Code

Product code of XenServer.

Serial Number

Serial number of XenServer.

Build Date

Build date of XenServer.

Build Number

Build number of XenServer.

Supplemental Pack

Version of the supplemental pack installed on the SDX appliance.

License Information

Platform

Model number of the hardware platform, based on the installed license.

System Information

Platform

Model number of the hardware platform.

Product

Type of NetScaler product.

Build

NetScaler release and build running on the SDX appliance.

IP Address

IP address of the Management Service.

Host ID

XenServer host ID.

System ID

XenServer system ID.

Serial Number

XenServer serial number.

System Time

System time displayed in Day Month Date Hours:Min:Sec Timezone Year format.

Uptime

Time since the Management Service was last restarted, in number of days, hours, andminutes.

BIOS version

BIOS version.

Viewing the Properties of the SDX Appliance

95

Viewing the Properties of the SDX Appliance

96

97

Viewing Real-Time Appliance Throughput

The total throughput of the SDX appliance for incoming and outgoing traffic is plotted inreal time in a graph that is updated at regular intervals. By default, throughputs for bothincoming and outgoing traffic are plotted together on the graph.

To view the throughput of the SDX appliance, on the Monitoring tab, in the navigation pane,expand Monitoring, and then click Throughput.

98

Viewing Real-Time CPU and MemoryUsage

You can view a graph of CPU and memory usage of the appliance. The graph is plotted inreal time and updated at regular intervals.

To view the CPU and memory usage of the SDX appliance, on the Monitoring tab, in thenavigation pane, expand Monitoring, and then click CPU / Memory Usage.

99

Viewing CPU Usage for All Cores

You can view the usage of each CPU core on the SDX appliance.

The CPU Core Usage pane displays the following details:

Core Number

The CPU core number on the appliance.

Physical CPU

The physical CPU number of that core.

Hyper Threads

The hyper threads associated with that CPU core.

Instances

The instances that are using that CPU core.

Average Core Usage

The average core usage, expressed as a percentage.

To view the CPU usage for all the cores on the SDX appliance, on the Monitoring tab, in thenavigation pane, expand Monitoring, and then click CPU Core Usage.

100

SNMP

You can use Simple Network Management Protocol (SNMP) to configure the SNMP agent onthe Citrix® NetScaler® appliance to generate asynchronous events, which are calledtraps.You can configure a Simple Network Management Protocol (SNMP) agent on theNetScaler SDX appliance to generate asynchronous events, which are called traps. The trapsare generated whenever there are abnormal conditions on the NetScaler SDX appliance. Thetraps are then sent to a remote device called a trap listener, which signals the abnormalcondition on the NetScaler SDX appliance. Or, you can query the SNMP agent forSystem-specific information from a remote device called an SNMP manager. The agent thensearches the management information base (MIB) for the data requested and sends the datato the SNMP manager.

The SNMP agent on the NetScaler can generate traps compliant with SNMPv1 and SNMPv2only. For querying, the SNMP agent supports SNMP version 1 (SNMPv1), SNMP version 2(SNMPv2), and SNMP version 3 (SNMPv3).

The following figure illustrates a network with a NetScaler SDX appliance that has SNMPenabled and configured. In the figure, each SNMP network management application usesSNMP to communicate with the SNMP agent on the NetScaler SDX appliance. The SNMPagent searches its management information base (MIB) to collect the data requested by theSNMP Manager and provides the information to the application.

Figure 1. NetScaler SDX Appliance Supporting SNMP

101

SNMP Trap Destinations

The SNMP agent on the SDX appliance generates traps that are compliant with SNMPv2 only.The supported traps can be viewed in the SDX MIB file. You can download this file from theDownloads page in the SDX user interface.

To add an SNMP trap destination1. On the configuration tab, in the navigation pane, expand System, and then click SNMP

Trap Destinations.

2. In the SNMP Trap Destinations pane, click Add.

3. In the Add SNMP Trap Destinations dialog box, specify values for the followingparameters:

• Destination Server—IPv4 address of the trap listener to which to send the SNMP trapmessages.

• Port—UDP port at which the trap listener listens for trap messages. Must match thesetting on the trap listener, or the listener drops the messages. Minimum value: 1.Default: 162.

• Community—Password (string) sent with the trap messages, so that the trap listenercan authenticate them. Can include letters, numbers, and hyphen (-), period (.)hash (#), space ( ), at (@), equals (=), colon (:), and underscore (_) characters.

Note: You must specify the same community string on the trap listener device, orthe listener drops the messages. Default: public.

4. Click Add, and then click Close. The SNMP trap destination that you added appears inthe SNMP Traps pane.

To modify the values of the parameters of an SNMP trap destination, in the SNMP TrapDestinations pane, select the trap destination that you want to modify, and then clickModify. In the Modify SNMP Trap Destination dialog box, modify the parameters.

To remove an SNMP trap, in the SNMP Trap Destinations pane, select the trapdestination that you want to remove, and then click Delete. In the Confirm messagebox, click to remove the SNMP trap destination.

102

Downloading MIB Files

You must download the following file before you start monitoring a NetScaler SDXappliance.

SDX-MIB-smiv2.mib. This file is used by SNMPv2 managers and SNMPv2 trap listeners.

The file includes a NetScaler enterprise MIB that provides NetScaler SDX-specific events.

To download MIB files1. Log on to the Downloads page of the NetScaler SDX appliance user interface.

2. Under SNMP Files, click SNMP v2 - MIB Object Definitions. You can open the file by usinga MIB browser.

103

Configuring the Management Service

The Management Service lets you manage client sessions and perform configuration tasks,such as creating and managing user accounts and tweaking backup and pruning policiesaccording to your requirements. You can also restart the Management Service and upgradethe version of the Management Service. You can further create tar files of the ManagementService and the XenServer and send them to technical support.

104

Managing Client Sessions

A client session is created when a user logs on to the Management Service. You can view allthe client sessions on the appliance in the Sessions pane.

In the Sessions pane, you can view the following details:

User Name

The user account that is being used for the session.

IP Address

The IP address of the client from which the session has been created.

Port

The port being used for the session.

Login Time

The time at which the current session was created on the SDX appliance.

Last Activity Time

The time at which user activity was last detected in the session.

Session Expires In

Time left before session expiry.

To view client sessions, on the Configuration tab, in the navigation pane, expand System,and then click Sessions.

To end a client session, in the Sessions pane, click the session you want to remove, andthen click End Session.

You cannot end a session with the client that initiated that session.

105

Configuring User Accounts

A user logs on to the SDX appliance to perform appliance management tasks. To allow auser to access the appliance, you must create a user account on the SDX appliance for thatuser. (Note: the Repeater virtual machines use their own user accounts, managed on theindividual Repeater virtual machines). Users are authenticated locally, on the appliance.

Important: The password applies to the SDX appliance, Management Service, andXenServer. Do not change the password directly on the XenServer.

To configure a user account1. In the navigation pane, expand System, and then click Users. The Users pane displays a

list of existing user accounts, with their permissions.

2. In the Users pane, do one of the following:

• To create a user account, click Add.

• To modify a user account, select the user, and then click Modify.3. In the Create System User or Modify System User dialog box, set the following

parameters:

• Name*—The user name of the account. The following characters are allowed in thename: letters a through z and A through Z, numbers 0 through 9, period (.), space,and underscore (_). Maximum length: 128. You cannot change the name.

• Password*—The password for logging on to the appliance.

• Confirm Password*—The password.

• Permission*—The user's privileges on the appliance. Possible values:

• Superuser—The user can perform all administration tasks related to theManagement Service.

• Readonly—The user can only monitor the system and change the password ofthe account.

Default: superuser.*A required parameter

4. Click Create or OK, and then click Close. The user that you created is listed in the Userspane.

To remove a user account1. On the Configuration tab, in the navigation pane, expand System, and then click Users.

2. In the Users pane, select the user account, and then click Delete.

3. In the Confirm message box, click OK.

Configuring User Accounts

106

107

Restarting the Management Service

You can restart the Management Service from the System pane. Restarting the ManagementService does not affect the working of the instances. The instances continue to functionduring the Management Service restart process.

To restart the Management Service1. On the Configuration tab, in the navigation pane, click System.

2. In the System pane, under System Administration, click Reboot Management Service.

108

Upgrading the Management Service

The process of upgrading the Management Service involves uploading the build file of thetarget build and the documentation file to the SDX appliance, and then upgrading theManagement Service.

109

Uploading the Management Service Buildand Documentation Files

You can upload the Management Service build and documentation files from a clientcomputer to the SDX appliance. You can also download build and documentation files to alocal computer as a backup.

To upload the Management Service build file1. In the navigation pane, expand Management Service, and then click Software Images.

2. In the Software Images pane, click Upload.

3. In the Upload Management Service Software Image dialog box, click Browse, navigate tothe folder that contains the build file, and then double-click the build file.

4. Click Upload.

To create a backup by downloading a ManagementService build file

1. In the Software Images pane, select the file you want to download, and then clickDownload.

2. In the message box, from the Save list, select Save as.

3. In the Save As message box, browse to the location where you want to save the file,and then click Save.

To upload the Management Service documentationfile

1. In the navigation pane, expand Management Service, and then click Software Images.

2. In the Software Images pane, on the Documentation Files tab, click Upload.

3. In the Upload Management Service Documentation File dialog box, click Browse,navigate to the folder that contains the documentation file, and then double-click thefile.

4. Click Upload.

To create a backup by downloading a ManagementService documentation file




Uploading the Management Service Build and Documentation Files

110

111

Upgrading the Management Service to aLater Version

After you have uploaded the Management Service image to the SDX appliance, use thisimage to upgrade the version of the Management Service. The Management Service willrestart after the upgrade. Restarting the Management Service does not affect yourNetScaler VPX instances and the appliance.

To upgrade the Management Service1. In the navigation pane, click System.

2. In the System pane, under System Administration, click Upgrade Management Service.

3. In the Upgrade Management Service dialog box, in Software Image, select the softwareimage file to which you want to upgrade the Management Service.

4. In Documentation File, select the documentation file you want to use for the upgrade.

5. Click OK.

112

Upgrading the XenServer Software

You need to upgrade to to configure VLAN filtering on an interface assigned to a NetScalerinstance. The process of upgrading the XenServer software involves uploading the build fileof the target build to the Management Service, and then upgrading the XenServer software.

113

Uploading the XenServer Build Files

You can upload the XenServer build files from a client computer to the SDX appliance. Youcan also download the build files to a local computer as a backup.

To upload the XenServer build file1. In the navigation pane, expand Management Service, and then click XenServer Files.

2. In the details pane, click the ISO Images tab, and then click Upload.

3. In the Upload XenServer ISO Image File dialog box, click Browse, navigate to the folderthat contains the build file, and then double-click the build file.

4. Click Upload.

To create a backup by downloading a XenServer buildfile

1. In the details pane, click the ISO Images tab, select the file you want to download, andthen click Download.



114

Upgrading the Software

You can upgrade to the latest version of the XenServer software. The upgrade process maytake up to 20 minutes. Before upgrading the software, upload the ISO image file to theappliance. The current version of the software is displayed in the Upgrade XenServer dialogbox.

To upgrade the XenServer software1. In the navigation pane, click System.

2. In the details pane, click Upgrade XenServer.

3. In the Upgrade XenServer dialog box, select the Image file from the list.


115

Backing Up and Restoring theConfiguration Data of the SDX Appliance

The backup policy runs at 00:30 A.M. every day. You do not have to wait until midnight forcreating a backup file. You can create a backup file at any time if, for example, you wantto immediately back up changes to the configuration.

You can use the backup file to restore the configuration data on the appliance. You canrestore the configuration data of the XenServer, Management Service, and all the NetScalerinstances, only the NetScaler instances, or selected NetScaler instances.

To perform an immediate backup1. In the navigation pane, expand Management Service, and then click Backup Files.

2. In the Backup Files pane, click Back Up.

3. In the Confirm dialog box, click Yes. This process may take a few minutes, dependingon the amount of data to be backed up.

To restore the configuration1. In the navigation pane, expand Management Service, and then click Backup Files.

2. In the Backup Files pane, click Restore.

3. In the , select one of the following:

• Restore Appliance—Restores the XenServer, Management Service, and all theNetScaler instances.

Note: Perform a Factory Reset before selecting this option.

• All instances—Restores all the NetScaler instances.

• Specific instances—Restores only the selected NetScaler instances.4. Click Close.

116

Performing a Factory Reset

Before performing a factory reset, back up all the data stored on the appliance, includingthe settings of the accelerator and the NetScaler instance. Citrix recommends that youstore the files outside the appliance. Performing a factory reset terminates all currentclient sessions with the Management Service, so you have to log back on to the ManagementService for any additional configuration tasks. When you are ready to restore the appliance,import the backup files by using the Management Service.

You also have the option to reset while retaining the current IP addresses of theManagement Service and XenServer or to reset with the default IP addresses of theManagement Service and XenServer. In either case, the software automatically performsthe following actions:

• Deletes NetScaler and acceleratorinstances.

• Deletes SSL certificate and key files.

• Deletes license and technical archive files.

• Deletes the NTP configuration on the appliance.

• Restores the time zone to UTC.

• Restores prune and backup policies to their default settings.

• Deletes the Management Service image and documentation files.

• Deletes the NetScaler image and documentation files.

• Deletes all XVA images except the last image file that was accessed on the appliance.

• Restores default interface settings.

• Restores the default configuration of the appliance, including default profiles, users,and system settings.

• Restores default IP addresses for XenServer and the Management Service.

• Restores default passwords for XenServer and the Management Service.

• Restarts the Management Service.

You can also perform a pseudo-factory reset that retains the currently running managementservice and its IP addresses, rather than reverting to the factory-installed managementservice. A pseudo-factory reset is recommended when the need to perform a reset is notcaused by a problem with the management service itself.

To perform a factory reset1. In the navigation pane, expand Management Service, and then click Backup Files.

2. In the Backup Files pane, click Factory Reset.

3. In the Factory Reset dialog box, select the type of reset from the following options:

• Reset (Without Network Configuration)—Retain the IP addresses of the ManagementService and XenServer.

• Reset (With Network Configuration)—Management Service and XenServer restartwith the default IP addresses.

• Appliance Reset—The appliance settings are restored to the default factorysettings, such as default IP addresses for Management Service and XenServer. Noinstances are installed, and only the default SSL certificate is available on theappliance.


5. When the reset is complete, log in with default credentials and run the configurationwizard.

To perform a pseudo-factory reset1. On Configuration > NetScaler > Instance, delete the NetScaler instance.

2. On Configuration > CloudBridge > Accelerator, delete the accelerator master instance.

3. On Configuration > CloudBridge > Instances, delete all the accelerator instances.

4. Log out.

5. Log in with default credentials and run the configuration wizard.

Performing a Factory Reset

117

118

Removing Management Service Files

You can remove any unneeded Management Service build and documentation files from theSDX appliance.

To remove a Management Service file1. On the Configuration tab, in the navigation pane, expand Management Service, and

then click the file that you want to remove.

2. In the details pane, select the file name, and then click Delete.

119

Generating a Tar Archive for TechnicalSupport

You can use the Technical Support option to generate a tar archive of data and statistics forsubmission to Citrix technical support. This tar can be generated for the ManagementService or the XenServer, or for both at the same time. You can then download the file toyour local system and send it to Citrix technical support.

In the Technical Support pane, you can view the following details.

Name

The name of the tar archive file. The file name indicates whether the tar is for theManagement Service or the XenServer.

Last Modified

The date when this file was last modified.

Size

The size of the tar file.

To generate the tar archive for technical support1. On the Configuration tab, navigate to Diagnostics > Technical Support.

2. In the details pane, from the Action list, select Generate Technical Support File.

3. In the Generate Technical Support File dialog box, from the Mode list, select whetheryou want to archive data of XenServer, Management Service, Appliance (includingXenServer and Management Service), Instances, or Appliance (including instances).

4. Click OK.

To download the tar archive for technical support1. In the Technical Support pane, select the technical support file that you want to

download.

2. From the Action list, select Download. The file is saved to your local computer.

120

Provisioning the NetScaler Instance

You can provision the NetScaler instance on the SDX appliance through the ManagementService. Repeater for SDX supports a single NetScaler instance.

To provision the NetScaler instance on the SDX appliance, first, you need to define anadmin profile to attach to the NetScaler instance. This profile specifies the user credentialsthat are used by the Management Service to provision the NetScaler instance and later, tocommunicate with the instance to retrieve configuration data. You can also use the defaultadmin profile. Next, you need to upload the .xva image file to the Management Service.After uploading the .xva file, you can begin adding NetScaler instance using theManagement Service. The Management Service implicitly deploys the NetScaler instance onthe SDX appliance and then downloads configuration details of the instances.

Note: An .xva image file based on the NetScaler 9.3 release is available on the SDXappliance when it ships from the factory.

121

Creating Admin Profiles

Admin profiles specify the user credentials that are used by the Management Service whenprovisioning the NetScaler instances, and later when communicating with the instances toretrieve configuration data. The user credentials specified in an admin profile are also usedby the client when logging on to the NetScaler instances through the CLI or theconfiguration utility.

The default admin profile for an instance specifies a user name of nsroot, and thepassword is also nsroot. This profile cannot be modified or deleted. However, you shouldoverride the default profile by creating a user-defined admin profile and attaching it to theinstance when you provision the instance. The Management Service administrator candelete a user-defined admin profile if it is not attached to any NetScaler instance.

Important:

Do not change the password directly on the NetScaler VPX instance. If you do so, theinstance becomes unreachable from the Management Service. To change a password, firstcreate a new admin profile, and then modify the NetScaler instance, selecting this profilefrom the Admin Profile list.

To change the password of NetScaler instance in a high availability setup, first change thepassword on the instance designated as the secondary node, and then change the passwordon the instance designated as the primary node. Remember to change the passwords onlyby using the Management Service.

To create an admin profile1. On the Configuration tab, in the navigation pane, expand NetScaler Configuration, and

then click Admin Profiles.

2. In the Admin Profiles pane, click Add.

3. In the Create Admin Profile dialog box, set the following parameters:

• Profile Name*—Name of the admin profile. The default profile name is nsroot. Youcan create user-defined profile names.

• User Name—User name used to log on to the NetScaler instance. The user name ofthe default profile is nsroot and cannot be changed.

• Password*—The password used to log on to the NetScaler instance. Maximum length:31 characters.

• Confirm Password*—The password used to log on to the NetScaler instance.* A required parameter

4. Click Create, and then click Close. The admin profile you created appears in the AdminProfiles pane.

If the value in the Default column is true the default profile is the admin profile. Ifthe value is false, a user-defined profile is the admin profile.

If you do not want to use a user-defined admin profile, you can remove it from theManagement Service. To remove a user-defined admin profile, in the Admin Profilespane, select the profile you want to remove, and then click Delete.

Creating Admin Profiles

122

123

Uploading NetScaler .Xva Images

You have to upload the NetScaler .xva files on the SDX appliance before provisioning theNetScaler instances. You can also download an .xva image file to a local computer as abackup. The .xva image file format is: NSVPX-XEN-ReleaseNumber-BuildNumber_nc.xva

Note: By default, an .xva image file based on the NetScaler 9.3 release is available onthe SDX appliance.

In the NetScaler XVA Files pane, you can view the following details.

Name

Name of the .xva image file. The file name contains the release and build number. Forexample, the file name NSVPX-XEN-9.3-25_nc.xva refers to release 9.3 build 25.

Last Modified

Date when the .xva image file was last modified.

Size

Size, in MB, of the .xva image file.

To upload a NetScaler .xva file1. On the Configuration tab, in the navigation pane, expand NetScaler Configuration, and

then click XVA Files.

2. In the pane, click Upload.

3. In the Upload NetScaler Instance XVA dialog box, click Browse and select the XVA imagefile that you want to upload.

4. Click Upload. The XVA image file appears in the NetScaler XVA Files pane after it isuploaded.

To create a backup by downloading a NetScaler .xvafile

1. In the NetScaler Build Files pane, select the file that you want to download, and thenclick Download.

2. In the File Download message box, click Save.


Uploading NetScaler .Xva Images

124

125

Adding a NetScaler Instance

When you add NetScaler instances from the Management Service, you need to providevalues for some parameters, which the Management Service implicitly configures on theNetScaler instances.

Note: For a high availability setup (active-active or active-standby), Citrix recommendsthat you configure the two NetScaler instances on different SDX appliances. Make surethat the instances in the setup have identical resources, such as CPU, memory,interfaces, packets per second (PPS), and throughput.

Name*

The host name assigned to the NetScaler instance.

IP Address*

The NetScaler IP (NSIP) address at which you access a NetScaler instance formanagement purposes. A NetScaler instance can have only one NSIP. You cannot removean NSIP address.

Netmask*

The subnet mask associated with the NSIP address.

Gateway*

The default gateway that you must add on the NetScaler instance if you want accessthrough SSH or the configuration utility from an administrative workstation or laptop thatis on a different network.

XVA File*

The .xva image file that you need to provision. This file is required only when you add aNetScaler instance.

Description

Add a description or comments related to the administrator profile.

CPU

Assign a dedicated core or cores to the instance or the instance shares a core with otherinstance(s).

Reboot affected Instances if CPU cores are reassigned

Restart the instances on which CPU cores are reassigned to avoid any performancedegradation.

Allowed VLANs

Specify a list of VLAN IDs that can be associated with a NetScaler instance.

NSVLAN

A VLAN to which the subnet of the NetScaler management IP (NSIP) address is bound. TheNSIP subnet is available only on interfaces that are associated with the NSVLAN. Selectthis check box if your deployment requires that the NSIP not be accessible through anyinterface other than the one you select in the VLAN Settings dialog box. This settingcannot be changed after the NetScaler instance is provisioned.

Note:

• HA heartbeats will be sent only on the interfaces that are part of the NSVLAN.

• You can configure an NSVLAN only from VPX XVA build 9.3-53.4 and later.

Important: If NSVLAN is not selected, running the "clear config full" command on theVPX instance deletes the VLAN configuration.

To provision a NetScaler instance1. On the Configuration tab, in the navigation pane, expand NetScaler Configuration, and

then click Instances.

2. In the NetScaler Instances pane, click Add.

3. In the Provision NetScaler Wizard follow the instructions on the screen.

4. Click Create, and then click Close. The provisioning progress and any failures, such asfailure to assign a virtual function to the VPX instance, are displayed.

To modify the values of the parameters of a provisioned NetScaler instance, in theNetScaler Instances pane, select the instance that you want to modify, and then clickModify. In the Modify NetScaler Wizard, modify the parameters.

Note: If you modify the VLAN enforcement interfaces, memory, and feature license,parameters, the NetScaler instance implicitly stops and restarts to bring theseparameters into effect.

You cannot modify the Image and User Name parameters.

If you want to remove a NetScaler instance provisioned on the SDX appliance, in theNetScaler Instances pane, select the instance that you want to remove, and then clickDelete. In the Confirm message box, click Yes to remove the NetScaler instance.

To modify the values of the parameters of a provisioned NetScaler instance, in theInstances pane, select the instance you want to modify, and then click Modify. In theModify NetScaler Instance dialog box, modify the parameters described in the aboveprocedure. If you modify the following parameters: VLAN enforcement parameters,interfaces, or feature license, the NetScaler instance implicitly stops and restarts to bringthese parameters into effect.

Adding a NetScaler Instance

126

127

Provisioning the Repeater Instances

Provisioning Repeater instances is similar to provisioning the NetScaler instance, with thefollowing major differences:

• Multiple instances are supported.

• Admin profiles are not used.

Before adding a Repeater instance, you have to upload a Repeater .xva file to the SDXappliance .

128

Uploading Repeater .Xva Images

You need to have a Repeater.xva file on the SDX appliance before provisioning the Repeaterinstances. The .xva image file format is: Citrix Branch Repeater VPX Release Number -BuildNumber.xva

Note: By default, an .xva image file is installed on the SDX appliance at the factory.

In the Repeater XVA Files pane, you can view the following details:

• Name - Name of the .xva image file.

• Last Modified - Date when the .xva image file was last modified.

• Size - Size of the .xva image file.

To upload a Repeater .xva file1. On the Configuration tab, in the navigation pane, expand Repeater Configuration, and


2. In the XVA Files pane, click Upload.

3. In the Upload Instance XVA dialog box, click Browse to select the XVA

4. Click Upload to start uploading the file to the SDX appliance. The XVA image fileappears in the XVA Files pane after it is uploaded.

If you no longer want to use an .xva image file, you can remove it from the SDXappliance.

To remove a Repeater .xva file1. On the Configuration tab, in the navigation pane, expand Repeater Configuration, and


2. In the XVA Files pane, click the .xva image file that you want to remove, and then clickDelete.

3. In the Confirm message box, click Yes to remove the .xva image file. The file isremoved from the appliance database.

129

Adding a Repeater Instance

Note: In normal deployments, use the Repeater Provisioning Wizard instead of addinginstances one by one.

When you add Repeater instances from the Service VM, you need to provide values for thefollowing parameters, which the Service VM implicitly configures on the NetScalerinstances.

• Name* - The host name assigned to the NetScaler instance.

• IP Address* - The Repeater management IP address.

• Netmask* - The subnet mask associated with the management IP address.

• Gateway* - The default gateway for the subnet containing the management IP address.

• Image* - The .xva image file that you need to provision.

Figure 1. To provision a Repeater instance

1. On the Configuration tab, in the navigation pane, expand Repeater Configuration, andthen click Instances.

2. In the Instances pane, click Add.

3. In the Create Repeater Instance dialog box, specify values for the following parameters.

• Name*

• IP Address*

• Netmask*

• Gateway*

• Description

4. Click Create, and then click Close. The Repeater instance you provisioned appears inthe Repeater Instances pane.

5. Wait until the Status field reports “Inventory from BR instance completed.” This takesabout seven minutes per instance. Attempting to configure and instance before theinventory is complete may require that you delete the instance and start over. Both the“VM State” and “Instance State” indicators should be green before you proceed.

* A required parameter

To modify the values of the parameters of a provisioned instance, in the Repeater Instancespane, select the instance you want to modify, and then click Modify. In the Modify RepeaterInstance dialog box, modify the parameters described in the above procedure.

If you want to remove a Repeater instance provisioned on the SDX appliance, in theRepeater Instances pane, select the instance you want to remove, and then click Delete. Inthe Confirm message box, click Yes to remove the NetScaler instance.

Adding a Repeater Instance

130

131

Configuring and Managing the NetScalerInstance

After you have provisioned the NetScaler instance on your appliance, you can perform thefollowing tasks to configure and manage these instances.

• Save the Configuration

• Install SSL Certificates

• Upgrade a NetScaler Instance

• Manage a NetScaler Instance

• Apply the Administration Configuration

132

Saving the Configuration

You can save the running configuration of the NetScaler instance from the ManagementService.

To save the configuration on a NetScaler instance1. On the Configuration tab, in the navigation pane, click NetScaler.

2. In the details pane, under NetScaler Configuration, click Save Configuration.

3. In the Save Configuration dialog box, in Instance IP Address, select the IP addresses ofthe NetScaler instances whose configuration you want to save.


133

Upgrading a NetScaler Instance

The process of upgrading the NetScaler instance involves uploading the build file and thedocumentation file of the target build to the SDX appliance, and then upgrading theNetScaler instance.

134

Uploading NetScaler Resources

You have to upload the NetScaler software images to the SDX appliance before upgradingthe NetScaler instance. Citrix recommends that you upload the latest documentation filealong with the image file. You can also download the image and documentation files to alocal computer as a backup. For installing a new instance, you need the NetScaler XVA file.

In the NetScaler Software Images pane, you can view the following details.

Name

Name of the NetScaler instance software image file. The file name contains the releaseand build number. For example, the file name build-9.3-53.5_nc.tgz refers to release 9.3build 53.5 .

Last Modified

Date when the file was last modified.

Size

Size, in MB, of the file.

To upload a NetScaler software image1. In the navigation pane, expand NetScaler, and then click Software Images .

2. In the Software Images pane, click Upload.

3. In the Upload NetScaler Software Image dialog box, click Browse and select theNetScaler image file that you want to upload.

4. Click Upload. The image file appears in the NetScaler Software Images pane.

To create a backup by downloading a NetScaler buildfile




To upload a NetScaler documentation file1. In the navigation pane, expand NetScaler, and then click Software Images.

2. In the Software Images pane, on the Documentation Files tab, click Upload.

3. In the Upload NetScaler Documentation File dialog box, click Browse and select theNetScaler documentation file you want to upload.

4. Click Upload. The documentation file appears in the Documentation Files pane.

To create a backup by downloading a NetScalerdocumentation file

1. In the Documentation Files pane, select the file you want to download, and then clickDownload.



To upload a NetScaler XVA file1. In the navigation pane, expand NetScaler, and then click Software Images.

2. In the Software Images pane, on the XVA Files tab, click Upload.

3. In the Upload NetScaler XVA File dialog box, click Browse and select the NetScalerXVAfile you want to upload.

4. Click Upload. The XVA file appears in the XVA Files pane.

To create a backup by downloading a NetScaler XVAfile

1. In the XVA Files pane, select the file you want to download, and then click Download.



Uploading NetScaler Resources

135

136

Managing a NetScaler Instance

The Management Service lets you perform the following operations on the NetScalerinstance, both from the NetScaler Instances pane in the Configuration tab and in theNetScaler Instances gadget on the Home page.

Start a NetScaler Instance

Start any NetScaler instance from the Management Service user interface. When theManagement Service UI forwards this request to the Management Service, it starts theNetScaler instance.

Shut down a NetScaler instance

Shut down any NetScaler instance from the Management Service user interface. Whenthe Management Service UI forwards this request to the Management Service, it stops theNetScaler instance.

Reboot a NetScaler instance

Restart the NetScaler instance.

Delete a NetScaler instance

If you do not want to use a NetScaler instance, you can delete that instance by using theManagement Service. Deleting an instance permanently removes the instance and itsrelated details from the database of the SDX appliance.

To start, stop, delete, or restart a NetScaler instance1. On the Configuration tab, in the navigation pane, click NetScaler Instances.

2. In the NetScaler Instances pane, select the NetScaler instance on which you want toperform the operation, and then click Start or Shut Down or Delete or Reboot.

3. In the Confirm message box, click Yes.

137

Removing NetScaler Instance Files

You can remove any NetScaler instance files, such as XVAs, builds, documentation, SSL keysor SSL certificates, from the appliance.

To remove NetScaler instance files1. On the Configuration tab, in the navigation pane, expand NetScaler Configuration, and

then click the file that you want to remove.

2. In the details pane, select the file name, and then click Delete.

138

Configuring and Managing the RepeaterInstances

After you have provisioned Repeater instances on your appliance, you can perform thefollowing tasks to configure and manage these instances.

• Configuring a Repeater Instance.

• Upgrading a Repeater Instance.

• Managing a Repeater Instance.

139

Configuring a Repeater Instance

Once a new instance has been installed, configure it as follows:

1. Go to the NetScaler SDX > Repeater Configuration > Instances pane.

2. Click on the instance name to show configuration details.

3. Wait for “Status” to report “Inventory from BR instance completed.” The inventory steptakes approximately seven minutes to complete.

4. Click on the “IP Address” field to go to the Repeater instance’s UI page.

5. Log into the Repeater with the default administrator credentials (login >admin,password > password).

6. On the “Configure Settings: IP Address” page, assign an IP address, netmask, andgateway to accelerated bridge apA. This is necessary for load-balancing. Save thechanges and restart the Repeater software when prompted.

140

Upgrading a Repeater instance

The process of upgrading a Repeater instance involves either uploading a new virtualmachine image (xva file) or upgrading the Repeater software within the virtual machine.

See Basic Configuration.

Note: To prevent any loss of the configuration when upgrading the Repeater virtualmachine, save the Repeater configuration using the “Save/Restore Configuration” featureof the Repeater’s management interface.

http://support.citrix.com/proddocs/topic/sdx-56/br-initial-config-wrapper-con.html

141

Managing a Repeater Instance

The management service VM lets you perform the following operations on the Repeaterinstance, both from the Repeater Instances pane in the Configuration tab and in theRepeater Instances gadget on the Home page.

• Start a Repeater Instance - Starts a Repeater VM.

• Shut down a NetScaler instance - Shut down a Repeater VM.

• Reboot a NetScaler instance - Restart the Repeater VM.

• Delete a NetScaler instance - Removes a Repeater VM.

To start, stop, delete, or restart a Repeater instance1. On the Configuration tab, in the navigation pane, click Repeater Instances.

2. In the Repeater Instances pane, select the Repeater instance on which you want toperform the operation, and then click Start or Shut Down or Delete or Reboot.


4. After deleting a Repeater instance, the SDX unit must be rebooted.

142

Monitoring the NetScaler Instance

A high-level view of the performance of the appliance and the NetScaler VPX instanceprovisioned on the appliance are displayed on the Monitoring page of the ManagementService user interface. After provisioning and configuring the NetScaler instance, you canperform various tasks to monitor the NetScaler instance.

143

Viewing the Properties of the NetScalerInstance

The Management Service user interface displays the list and description of the NetScalerVPX instance provisioned on the SDX appliance. Use the NetScaler Instances pane to viewdetails, such as the instance name and IP address, CPU and memory utilization, number ofpackets received and transmitted on the instance, and the throughput and total memoryassigned to the instance.

Clicking the IP address of the NetScaler VPX instance opens the configuration utility (GUI) ofthat instance in a new tab or browser.

To view the properties of the NetScaler Instance1. On the Configuration tab, in the left pane, expand NetScaler Configuration, and then

click Instances.

Note: You can also view the properties of a NetScaler VPX instance from the Hometab.

2. In the NetScaler Instance pane, you can view the details for the NetScaler instance

3. Click the arrow next to the name of a NetScaler instance to view the properties of thatinstance, or click Expand All to view the properties of all the NetScaler instances.

144

Viewing the Running and SavedConfiguration of a NetScaler Instance

By using the Management Service you can view the currently running configuration of theNetScaler instance. You can also view the saved configuration of a NetScaler instance andthe time when the configuration was saved.

To view the running and saved configuration of theNetScaler instance

1. On the Configuration tab, in the left pane, expand NetScaler Configuration, and thenclick Instances.

2. In the NetScaler Instances pane, click the NetScaler instance for which you want toview the running or saved configuration.

3. To view the running configuration, click Running Configuration, and to view the savedconfiguration, click Saved Configuration.

4. In the NetScaler Running Config window or the NetScaler Saved Config window, you canview the running or saved configuration of the NetScaler instance.

145

Pinging a NetScaler Instance

You can ping a NetScaler instance from the Management Service to check whether thedevice is reachable.

To ping a NetScaler instance1. On the Configuration tab, in the left pane, expand NetScaler Configuration, and then

click Instances.

2. In the NetScaler Instances pane, click the NetScaler instance you want to ping, and thenclick Ping. In the Ping message box, you can view whether the ping is successful.

146

Tracing the Route of a NetScaler Instance

You can trace the route of a packet from the Management Service to a NetScaler instanceby determining the number of hops used to reach the instance.

To trace the route of a NetScaler instance1. On the Configuration tab, in the left pane, expand NetScaler Configuration, and then

click Instances.

2. In the NetScaler Instances pane, click the NetScaler instance you want to trace, andthen click TraceRoute. In the Traceroute message box, you can view the route to theNetScaler.

147

Rediscovering a NetScaler Instance

You can rediscover a NetScaler instance when you need to view the latest state andconfiguration of a NetScaler instance.

During rediscovery, the Management Service fetches the configuration. By default, theManagement Service schedules devices for rediscovery once every 30 minutes.

To rediscover a NetScaler instance1. On the Configuration tab, in the left pane, expand NetScaler Configuration, and then

click Instances.

2. In the NetScaler Instances pane, click the NetScaler instance you want to rediscover,and then click Rediscover.


148

Monitoring the Repeater Instance

After provisioning and configuring the Repeater instances, you can perform simplemonitoring through the service VM, which will reveal whether the Repeater instance isrunning or not, and give some statistics about it.

More detailed monitoring is done through the browser-based UI of the individual Repeaterinstances, using their Management IP addresses. See the Branch Repeater Family User’sGuide, rel. 5.5-5.7, for complete information on the Repeater instances and user interface.

• Viewing the Properties of the Repeater Instances.

• Viewing the Running and Saved Configuration of Repeater Instances.

• Pinging Repeater Instances.

• Tracing the Route of Repeater Instances.

• Rediscovering Repeater Instances.

149

Viewing the Properties of the RepeaterInstances

The service VM user interface displays the list and description the Repeater Instancesinstance provisioned on the SDX appliance. Use the Repeater Instances Instance pane toview details, such as the instance name and IP address, CPU and memory utilization,number of packets received and transmitted on the instance, and the throughput and totalmemory assigned to the instance.

Clicking the IP address of the Repeater instance opens the configuration utility (GUI) of thatinstance in a new tab or browser.

To view the properties of the Repeater Instances1. On the Configuration tab, in the left pane, expand Repeater, and then click Instances.

Note: You can also view the properties of Repeater instances from the Home tab.

2. In the Repeater Instances pane, you can view the following details for the Repeaterinstances:

• Name - The host name assigned to the Repeater instance while provisioning.

• VM State - The state of the virtual machine.

• Instance State - The state of the Repeater instance.

• IP Address - The IP address of the instance. Clicking the IP address opens the GUI ofthis instance in a new tab or browser.

• CPU Usage (%) - The percentage of CPU utilization on the Repeater.

• Memory Usage (%) - The percentage of memory utilization on the Repeater.3. Click the arrow next to the name of a Repeater instance to view the properties of that

instance, or click Expand All to view the properties of all the Repeater instances. Youcan view the following properties:

• apA IP Address - The address of the accelerated bridge.

• apA Gateway - The gateway used by the accelerated bridge.

• Total Memory (MB) - The memory allocated to the virtual machine.

• Total Memory - RAM allocated to the instance.

• Version - Repeater version, build number, and build date.

• Uptime. Time since the last reboot.

• Operating Status. Status of the virtual machine.

• Accelerated Connections. The current number of accelerated connections.

• Unaccelerated Connections. The current number of unaccelerated connections.

• Connected Plugins - The number of Repeater Plug-ins that currently have an opensignaling connection. (Not supported on this release.)

• Max. Plugins - The maximum number of Plug-ins supported by the license andarchitecture of the instance. (Not supported on this release.)

• Bandwidth Limit (kbps) - The current send bandwidth limit of the Repeaterinstance.

• Bandwidth Mode - Shows the state of the hardboost/softboost and fullbandwidth/partial bandwidth modes.

Viewing the Properties of the Repeater Instances

150

• Host Name - The host name of the instance.

• Total Memory (GB) - The total memory being assigned to the instance.

• Status - The status of the operations being performed on an instance, such as statusof whether inventory from the instance is completed or whether reboot is inprogress.

Viewing the Properties of the Repeater Instances

151

152

Viewing the Running and SavedConfiguration of a Repeater Instance

By using the service VM you can view the currently running configuration of the NetScalerinstance. You can also view the saved configuration of the NetScaler instance and the timewhen the configuration was saved.

To view the running and saved configuration of aRepeater Instance

1. On the Configuration tab, in the left pane, expand Repeater, and then click Instances.

2. In the Repeater Intances pane, click the NetScaler instance for which you want to viewthe running or saved configuration.

3. To view the running configuration, click Running Configuration, and to view the savedconfiguration, click Saved Configuration.

4. In the Repeater Running Config window or the Repeater Saved Config window, you canview the running or saved configuration of the Repeater instance.

153

Pinging a Repeater Instance

You can ping a Repeater instance from the service VM to check whether the device isreachable.

To ping a Repeater instance1. On the Configuration tab, in the left pane, expand Repeater Configuration, and then

click Instances.

2. In the Repeater Configuration pane, click the Repeater instance you want to ping, andthen click Ping. In the Ping message box, you can view whether the ping is successful.

154

Tracing the Route of a Repeater Instance

You can trace the route of a packet from the service VM to a Repeater Instances instance bydetermining the number of hops used to reach the instance.

To trace the route of a Repeater instance1. On the Configuration tab, in the left pane, expand Repeater Configuration, and then

click Instances.

2. In the Repeater Instances pane, click the Repeater instance you want to trace, and thenclick TraceRoute. In the Traceroute message box, you can view the route to theinstance.

155

Rediscovering Instance

You can rediscover a Repeater instance when you need to view the latest state andconfiguration of a Repeater instance.

During rediscovery, the service VM fetches the configuration. By default, the service VMschedules devices for rediscovery once every 30 minutes.

To rediscover a Repeater instance1. On the Configuration tab, in the left pane, expand Repeater, and then click Instances.

2. In the Repeater Instances pane, click the instance, and then click Rediscover.


156

Using Logs to Monitor Operations andEvents

Use audit and task logs to monitor the operations performed on the Management Serviceand on the NetScaler instance. You can also use the events log to track all events for tasksperformed on the Management Service and the XenServer.

157

Viewing Audit Logs

All operations performed by using the Management Service are logged in the appliancedatabase. Use audit logs to view the operations that a Management Service user hasperformed, the date and time of each operation, and the success or failure status of theoperation. You can also sort the details by user, operation, audit time, status, and so on byclicking the appropriate column heading.

Pagination is supported in the Audit Log pane. Select the number of records to display on apage. By default, 25 records are displayed on a page.

To view audit logs1. In the navigation pane, expand System, and then click Audit.

2. In the Audit Log pane, you can view the following details.

User Name

The Management Service user who has performed the operation.

IP Address

The IP address of the system on which the operation was performed.

Port

The port at which the system was running when the operation was performed.

Resource Type

The type of resource used to perform the operation, such as xen_vpx_image andlogin.

Resource Name

The name of the resource used to perform the operation, such as vpx_image_nameand the user name used to log in.

Audit Time

The time when the audit log was generated.

Operation

The task that was performed, such as add, delete, and log out.

Status

The status of the audit, such as Successful or Failed.

Message

A message describing the cause of failure if the operation has failed and the status ofthe task, such as Done, if the operation was successful.

3. To sort the logs by a particular field, click the heading of the column.

Viewing Audit Logs

158

159

Viewing Task Logs

Use task logs to view and track tasks, such as upgrading instances and installing SSLcertificates, that are executed by the Management Service on the NetScaler instances. Thetask log lets you view whether a task is in progress or has failed or has succeeded.

Pagination is supported in the Task Log pane. Select the number of records to display on apage. By default, 25 records are displayed on a page.

To view the task log1. In the navigation pane, expand Diagnostics, and then click Task Log.

2. In the Task Log pane, you can view the following details.

ID

The auto-generated ID assigned to a task. For a task performed on multipleinstances, such as installing SSL certificate or upgrading instances, a single unique IDis generated in the task log.

Name

The name of the task that is being executed or has already been executed.

Status

The status of the task, such as In progress, Completed, or Failed.

Executed By

The Management Service user who has performed the operation.

Start Time

The time at which the task started.

End Time

The time at which the task ended.

Viewing Task Device LogsUse task device logs to view and track tasks being performed on each NetScaler instance.The task device log lets you view whether a task is in progress or has failed or hassucceeded. It also displays the IP address of the instance on which the task is performed.

To view the task device log1. In the navigation pane, expand Diagnostics, and then click Task Log.

2. In the Task Log pane, double-click the task to view the task device details.

3. In the Task Device Log pane, to sort the logs by a particular field, click the heading ofthe column.

Viewing Task Command LogsUse task command logs to view the status of each command of a task executed on aNetScaler instance. The task command log lets you view whether a command has beensuccessfully executed or has failed. It also displays the command that is executed and thereason why a command has failed.

To view the task command log1. In the navigation pane, expand Diagnostics, and then click Task Log.

2. In the Task Log pane, double-click the task to view the task device details.

3. In the Task Device Log pane, double-click the task to view the task command details.

4. In the Task Command Log pane, to sort the logs by a particular field, click the headingof the column.

Viewing Task Logs

160

161

Viewing Events

Use the Events pane in the Management Service user interface to monitor the eventsgenerated by the Management Service for tasks performed on the Management Service.

To view the events1. On the Monitoring tab, in the left pane, expand Monitoring, and then click Events.

2. In the Events pane, you can view the following details.

Severity

The severity of an event, which could be critical, major, minor, clear, orinformation.

Source

The IP address on which the event is generated.

Date

The date when the event is generated.

Category

The category of event, such as PolicyFailed and DeviceConfigChange.

Message

The message describing the event.

3. To sort the events by a particular field, click the heading of the column.

sdx 5 - docs.citrix.com · 6 sdx 5.6 citrix® repeater for netscaler® sdx is a high-performance...

Documents